How To Start Elasticsearch In Windows 10

How-to: Installing and configuring Elasticsearch

Introduction

This document describes the installation and configuration of Elasticsearch, which are recommended to exist performed past a consultant. This document contains the following sections:

• Requirements
• Installing Elasticsearch
• Installing Ingest-attachment
• Migrating from version 2.iv.five to version 6.vi.2
• Indexing existing feeds
• Security
• Disaster recovery

Requirements

• Java Virtual auto (JVM) is installed. Version 7 is recommended.
• A memory of non more than 64GB.

Return to top

Installing Elasticsearch

There are two ways to install Elasticsearch. Y'all can perform a standard installation during the installation or update of Exact Synergy Verbal Enterprise production update 260 or higher. To install Elasticsearch on multiple servers, you will have to perform the installation and configuration manually.

Standard installation

When installing or updating Verbal Synergy Enterprise production update 260 or higher, a bulletin volition exist displayed for you lot to indicate whether you lot want to install Elasticsearch. By installing Elasticsearch, the default single-node Elasticsearch is installed on the web server where the update or installation is performed. For security reasons, the installed Elasticsearch mode tin just connect to the web server locally. When Exact Synergy Enterprise is running on a spider web server farm, information technology is recommended to set up Elasticsearch with multiple nodes for ameliorate operation. For more information on the transmission ready of Elasticsearch clustering, meet https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html.

Notation: If yous are already using Elasticsearch for searching with the All option (meet How-to: Installing and configuring Search All feature), it is not necessary to reinstall Elasticsearch for searching the feeds. In this case, the message is non displayed during the update or installation and you tin continue to index the existing feeds.

Transmission installation

Notation: It is recommended to install Elasticsearch on a separate server.

1. Download the elasticsearch-vi.6.two null file.
2. Unzip the file, preferably to a directory that can be hands accessed due to control line interactions.
3. Change the names of the cluster and node for the Elasticsearch node by going to the installation directory of Elasticsearch. This step is recommended to avert any replication of indexes and data if in that location is another Elasticsearch with the same name running on the network.
4. Open up the config folder, then open up the elasticsearch.yml configuration file with Notepad. See the post-obit case on the naming of the cluster and node:



5. Beginning the Elasticsearch service. This can be performed via the control prompt or through a Windows service. By using the command prompt, you must manually start Elasticsearch every time you restart your PC. Hence, it is recommended to perform this via a Windows service, so that Elasticsearch can be started automatically when y'all restart your PC.

a. Via control prompt

• Become to the Windows control prompt.
• Become to the installation folder where you have unzipped the file.
• Run "bin\elasticsearch.bat".
• Elasticsearch has now started and the window should remain open.

Note: If the message "JAVA_HOME environs variable must be set!" is displayed, yous will have to starting time set the environment. For more information, come across How-to: Setting JAVA_HOME environment variable.

b. Via Windows service

• Go to the Windows command prompt.
• Become to the installation folder where you have unzipped the file.
• Run "elasticsearchservice.bat install".
• The service will exist installed. One time completed, the window tin exist closed. You can go to Windows Administrative Tools ? Services to check if the Elasticsearch service has started.
• Customize the properties of the service so that information technology will automatically showtime when Windows starts.

Note: If the bulletin "JAVA_HOME environs variable must exist set!" is displayed, yous volition have to first set the surround. For more information, run into How-to: Setting JAVA_HOME environment variable.

6. Brand sure the arrangement is running Elasticsearch. To exercise then, open up a browser (preferably Chrome) and type the URL of the Elasticsearch installation, including port 9200. For instance: "http://domain.com:9200". The search engine will return the following result:

Render to acme

Installing Ingest-attachment

1. Go to the Windows command prompt (as an administrator).
2. Run "c:\elasticsearch-half dozen.6.2\bin>elasticsearch-plugin install ingest-attachment".
3. Type "Y" to continue with the installation.

Notation: If yous are performing the ElasticSearch service via the command prompt, you need to run the "bin\elasticsearch.bat" control again later the installation. Whereas, if you are performing the service via the Windows service, y'all will need to restart the Windows service to ensure the ingest attachment is used.

Return to summit

Migrating from version 2.4.5 to version 6.6.2

1. Create an instance on a new service or server for the new ElasticSearch version.
2. Perform the installation of the new version in the machine.
3. Run the Exact.Search.Tool.exe application with the existing ElasticSearch URL.
4. In the application, click on the Settings Editor tab, and then consign the settings.
5. Next, click the Synonyms tab and copy the existing synonyms into a document file.
6. Click the Noise words tab and copy the noise words into a certificate file.
7. Click the Home tab and under the Server info section, click Modify to change the existing ElasticSearchURL to the URL of the new version to rebuild the alphabetize.
8. Click the Settings Editor tab, and so import the settings that were previously exported.
9. Click the Synonyms tab and copy the existing synonyms from the document file.
10. Click the Noise words tab and copy the existing synonyms from the certificate file.
11. Upon completion, in Verbal Synergy Enterprise, go to Modules ? System ? Setup ? Settings - General ? All.
12. Update the ElasticSearchURL setting to the new version.
13. Perform IISreset on the Exact Synergy Enterprise server.
14. Decommission the service or server of the one-time ElasticSearch version.

For more information, see Exact search tool help file.

Render to pinnacle

Indexing existing feeds

After Elasticsearch is installed, new feeds (posts and comments in the timeline) are automatically indexed and tin be searched using the Feeds pick, available in the search box at the superlative card of your Verbal Synergy Enterprise. To ensure that the existing feeds can also be constitute, yous have to index them once.

The following steps describe the process of indexing.

1. Become to the installation directory of your ESE, and then open the bin binder.
2. Run the Exact.Search.Tool.exe file.
3. In the displayed screen, connect to the SQL server by typing the server proper noun, the database of your ESE, your username, and countersign, and so clicking Connect. Note that the information provided (excluding the password) will exist remembered when you starting time up the tool again the next fourth dimension. In one case the connectedness is established, the Home tab will be displayed by default.
4. Click the Elasticsearch tab on the left panel to display a list of supported entities in ESE which you tin can load into Elasticsearch.
5. Select the Feeds check box.
   Note: Other options and tabs are not relevant when using Elasticsearch to search for feeds. For more data near other settings in this screen, see Exact search tool help file.
6. Click Create. An indicator volition be displayed in the screen to show the creation progress.
7. Once the procedure is completed, click Cheers!.

Note: It may take some time to create the indexed data.

Return to top

Security

ESE has a complex security model and it is recommended to limit the access to the Elasticsearch servers. The connectedness from ESE to Elasticsearch makes use of the Elasticsearch REST API on port 9200. Elasticsearch can function also as a cluster (for more than information, see the Disaster recovery section). In this example, port 9300 is used for advice between the Elasticsearch nodes.

2 methods can exist used to limit access to the Elasticsearch:

1. Put the Elasticsearch nodes in a separate VLAN and only permit the Synergy Application to connect to that VLAN on port 9200, preferably through a load balancer to achieve loftier availability.
2. Using Windows Firewall, implement a set of firewall rules on the servers where Elasticsearch is running. In this case, all traffic should be blocked, except traffic originating from the ESE awarding on port 9200. The same needs to be done betwixt the ELIS server and Elasticsearch server.

Note: Port 9300 should be opened for communication between the Elasticsearch nodes.

Verify that the Elasticsearch server is only accessible from the ESE server. You can do this by contacting the Elasticsearch server from the Internet browser and come across if you go a response back. On the internet browser, go to http://<Elasticsearch>:9200 and if the firewall is however open up, y'all will receive the following message:

{
"name" : "8TfTk-0",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "LU3XpgozTem7Qg4YsgZ9KA",
"version" : {
"number" : "half-dozen.6.2",
"build_flavor" : "default",
"build_type" : "zippo",
"build_hash" : "3bd3e59",
"build_date" : "2019-03-06T15:sixteen:26.864148Z",
"build_snapshot" : faux,
"lucene_version" : "vii.half dozen.0",
"minimum_wire_compatibility_version" : "v.6.0",
"minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}

This message indicates that the Elasticsearch server is still accessible and you will take to take steps to restrict the access.

Return to top

Disaster recovery

In case of a disaster where the Elasticsearch database is corrupted or an Elasticsearch node is no longer available, there are two possible scenarios to perform a disaster recovery:

1. Employ i node for Elasticsearch — If the Elasticsearch database is corrupted, the database has to exist completely rebuilt. Follow the aforementioned procedures for the disaster recovery, equally if it is a new setup.
2. Use at to the lowest degree three nodes for Elasticsearch — Elasticsearch can also handle the disaster recovery when using 3 or more nodes. This scenario requires an additional configuration. For more information, see https://www.rubberband.co/guide/en/elasticsearch/reference/current/modules-node.html#dissever-encephalon.

Note: In instance of a disaster, using an Elasticsearch cluster with ii nodes does not add any value equally this is the aforementioned as using just one node.

Return to pinnacle

Related documents

• Exact search tool aid file
• How-to: Installing and configuring Search All feature
• How-to: Setting the surroundings for JAVA_HOME
• How-to: Uninstalling Elasticsearch

Primary Category:	Support Product Know How	Document Type:	Online help main
Category:	On-line help files	Security  level:	All - 0
Sub category:	General	Document ID:	28.132.311
Assortment:	Verbal Synergy Enterprise	Engagement:	xxx-05-2019
Release:		Attachment:
Disclaimer

Source: https://www.exactsoftware.com/docs/DocView.aspx?DocumentID=%7Baf1bb956-85ab-4433-aa58-f10f733e9215%7D

Posted by: mcleandentelf1969.blogspot.com

Share this post