Elastic search installation

In order for being able to use the Indexed search that is built on a platform from Elastic search you need to do some installation work:

1.  Start by deciding on what network server you want use for the installation. We recommend that you do not make the search installation on the same server where NSP resides as the search server demands quite some resources.

2.  Install the latest version of Java JDK on the chosen server.

3.  Using an MSI-package from Elastic, see below, you install a database that holds the Indexed content of what you in NSP mark for search access. It also installs a search engine on the server.

In one of the MSI-steps you have to define what ports to use. These ports are to be set in NSP database global settings keys (see next list items).

4.  Activate the function in NSP using the following scripts:

exec app.spSetGlobalSetting @key ='FullTextSearchServerType' , @value = 'elastic'

exec app.spSetGlobalSetting @key ='FullTextSearchServerUrlWithPort' , @value = 'Searchpath:Portnr'

Or, if Elastic Search and NSP is installed on same server, enter this value instead:

 exec app.spSetGlobalSetting @key ='FullTextSearchServerUrlWithPort' , @value = 'http://localhost:Portnr'

exec app.spSetGlobalSetting @key ='ElasticSearchEnabled' , @value = 'true'

5.  Activate a unique prefix value for each NSP instance:

The same Elastic Search server can handle multiple NSP instances, for example both a test and a production environment. For each instance you need to insert a “prefix value”  in the database settings. The prefix value must be lowercase without spaces and special characters, e g like nsp76, name75, etc. All instances of NSP on the same elastic server must have unique prefix value otherwise data will be mixed.

If you continue to use elastic server for one NSP instance only you don´t need to insert the prefix value.

Insert the prefix in NSP using the following script:

exec app.spSetGlobalSetting 'ElasticIdentityPrefix', 'prefixvalue'