MC2 Services Installer/DR Installer

Introduction

The MC2 Services Installer installs the MC2 services: java, python, redis, Extract Service and Eagle Kafka Service. It does not install rules or streams.

Prerequisites

1.The installer should be executed on a region with Eagle Core product installed,
so that estar/tpe/, cfg/db_connection.ini, eaglemgr/emshell.bin, and system.xml
are already present. 
2. A minimum disk free space of 5,000 MB should be available in:
${EAGLE_PATH_TO_ROOT}/estar/tpe
${EAGLE_PATH_TO_ROOT}/estar/tpe/dynamic
${EAGLE_PATH_TO_ROOT}/estar/tpe/data 
3. The minimum number of user processes limit should be set to 4096. The limit can be checked with the command:
ulimit -u
4. The installation has to be executed on each node of a multi-server installation. 

Deployment/Install Step

1. Download the installer.

The installer mc2installer.zip can be downloaded separately from
https://eagleinvsys.jfrog.io/artifactory/rd-release-cloud/com/eagleinvsys/mc2installer/mc2installer
(Starting with 2020 May Release of MC2 the DR Installer is also included in the MC2.ZIP package at:
https://eagleinvsys.jfrog.io/artifactory/rd-release-cloud/com/eagleinvsys/mc2)
2. Upload the mc2installer.zip and mc2.zip to a folder on each node of the region.
3. Unzip the mc2installer.zip. This will produce two files:
install_mc2.sh - the installer script
mc2configurator.jar - a Java program which creates MC2 services configurations.
4. Make sure the installer.sh script has execute permission:
chmod u+x install_mc2.sh
5. Set the EAGLE_PATH_TO_ROOT environment variable to the full path to the eagle/ directory that is the parent of estar/tpe, for example:
export EAGLE_PATH_TO_ROOT=/apps/eagle
6. Set the MC2_EXTRACTSERVICE_NODES environment variable to the list of nodes host names (or IP addresses) in the region on which MC2 will be running, for example:
export MC2_EXTRACTSERVICE_NODES=10.80.105.157,10.80.105.158
Alternatively the list of nodes can be specified as:

• as a full path to a file with the list of host names, one host name per line, as the second parameter to the install_mc2.sh script

• if neither MC2_EXTRACTSERVICE_NODES, nor path to the file with list of nodes is specified, the script will attempt to retrieve the list of system/cluster_servers/server nodes with type extractservice from system.xml. The cluster_servers node address attribute will be used. For example if system.xml has the following cluster_servers nodes:

<?xml version="1.0" encoding="UTF-8"?>
<system version="2.0">
<servers baseport="20000" server_type="1" starversion="Eagle_2017.2.21.0">
...
</servers>
<cluster_servers no="1" address="node1.company.com" baseport="20000">
<server type="extractservice" offset="220" />
</cluster_servers>
<cluster_servers no="2" address="node2.company.com" baseport="20000">
<server type="extractservice" offset="220" />
</cluster_servers>
</system>
The installer will use the following list to configure the REDIS and Kafka Service clusters:
node1.company.com,node2.company.com
7. If PACE Report Service should be also installed, set the MC2_INSTALL_PACEREPORTSERVICE variable to 1:
export MC2_INSTALL_PACEREPORTSERVICE=1
8. Run the install_mc2.sh script, passing the full path to the mc2 zip file as a parameter, for example:
./install_mc2.sh /apps/eagle/estar/tpe/data/msgcenter/cmw_staging_folder/mc2-2020.04.10.1.zip
The execution log will be printed to the process standard output. Errors, if any, will be printed out to the process standard error. You can redirect the output if a log file is needed.
The installer will return an exit code of 0 on success, and 1 on error. You can see the exit code with:
echo $?
9. The last 3 lines of the log should appear as below, otherwise an error has occurred
Configuration DONE!!!......
2020-04-17 15:47:37 finished mc2configurator.jar
2020-04-17 15:47:37 END   ./install_mc2.sh

Full example of commands to execute the installer:

export EAGLE_PATH_TO_ROOT=/apps/eagle
export MC2_EXTRACTSERVICE_NODES=10.80.105.157,10.80.105.158
export MC2_INSTALL_PACEREPORTSERVICE=1
./install_mc2.sh ./mc2-2020.03.31.1-1585699464486.zip > install_log.txt

Note: When the DR region becomes active and EDS is being used on the environment, please follow EDS Metadata Refresh to reinitialize the EDS metadata cache.