Configuring NCM SP with Elastic Search

Prerequisites

Perform M&R 7.3.0.5 installation successfully.

Procedure

Navigate to /opt/APG/bin/ directory.
Open the /etc/sysctl.conf file.
Add the following line:
```
vm.max_map_count=262144
```
Open the /etc/security/limits.conf file.

Add the following line for the user:

In this example, the user is apg.

apg hard nofile 65536
apg soft nofile 65536
apg hard nproc 65536
apg soft nproc 65536

Save the file.
To install the Elastic Search cluster package, invoke the following command:
```
./manage-modules.sh install elasticsearch-cluster
```
When you are prompted for the IP address, provide the M&R host IP address. In the more entries option, select no unless Elastic Search needs to be configured in the cluster mode.

To verify the changes, type the following command:

su apg -c 'ulimit -n -u'

Following is the output:

open files                      (-n) 65536
max user processes              (-u) 65536

In /opt/APG/Databases/Elasticsearch/Default/conf/elasticsearch.yml file, add the following entry:
```
bootstrap.seccomp: false
script.max_compilations_per_minute: 120
```
In elasticsearch.yml file, add the above line at the end.
Restart Elastic Search server.

Ensure that, Elastic Search server is running.

Create a resource for each newly added elastic search database. Perform this operation every time a new Elastic Search node is added to the environment to scale-out backends.

For example, to create a database resource:

In Linux:

./bin/manage-resources.sh create dba/ES-NCM-JOBS '{ "type": "elasticsearch", "datasource": { "hosts": ["http://<Elastic Search Server IP Address>:9200"],"prefix": "/ncm*"},"settings": {"mapping": "ES-NCM-JOBS.xml"},"disabled": false }'

In Windows:

APG PATH\bin\manage-resources.cmd create dba/ES-NCM-JOBS '{ "type": "elasticsearch", "datasource": { "hosts": ["http://<Elastic Search Server IP Address>"],"prefix": "/ncm*"},"settings": {"mapping": "ES-NCM-JOBS.xml"},"disabled": false }'

Note: You need to specify the IP address for <Elastic Search Server>.

Restart the Tomcat service.