Installation components and configuration changes

After the All Services package (MC2) is deployed, the following configuration changes appear in the system .

Installed MC2 components

MC2 deployments includes the following components:

Component	Installed Path	Shared/Local
extractservice	${EAGLE_APP_TO_ROOT}/estar/tpe/servers/eaglemc2s/eaglemc2s-${version}.jar	local
kafkaservice	${EAGLE_APP_TO_ROOT}/estar/tpe/servers/kafkaservice/*	local
Redisserver	${EAGLE_APP_TO_ROOT}/estar/tpe/servers/redis/*	local
pypy	${EAGLE_APP_TO_ROOT}/estar/tpe/pypy/*	local
pyruleservice	${EAGLE_APP_TO_ROOT}/estar/tpe/dynamic/pyrules/*	shared

Configuration changes

The MC2 installer also modifies certain configurations to enable the deployed services.

Configuration	Config file path	Note
processguard.xml	${EAGLE_APP_TO_ROOT}/eaglemgr/config/	V15 and lower
processguard_custom.xml	${EAGLE_APP_TO_ROOT}/eaglemgr/config/	V17 only

Database changes

After the install of MC2, the database is updated to reflect the installed eagle EagleML/MC2 versions.

Uninstall Steps

In the event that the All Services package is desired to be uninstalled or made inactive, a manual process is required. These manual steps are required to update, disable and/or clean up some or all installed components.

The components defined in the install above may be deployed either together with EagleML (deploy by selecting all-services or all-services-without-overlay), or separately after EagleML is installed (extractservice, kafkaservice, redis, ...). To uninstall MC2 after it was deployed, execute the following steps manually to disable and clean up current deployed MC2 components.

Step 1: Determine the number of nodes in the region

From the region's front-end, determine how many app servers. To disable mc2, login to each app server and execute steps 2 to 6.

Step 2: Stop running services

Go to ${EAGLE_APP_TO_ROOT}/eaglemgr

Execute the following command

./stop starweb extractserviceworker extractservicelb kafkaservice redisserver redssentine

Step 3: Update the configurations to disable MC2 Services

Go to ${EAGLE_APP_TO_ROOT}/eaglemgr/config
Edit the processguard_custom.xml (V 17) or processguard.xml (V15 or lower) from the configuration location above and save the changes
Disable the MC2 services by changing enabled="yes" to enabled="no". Examples below:

<?xml version="1.0" encoding="UTF-8"?>
<processguard_custom version="1.1">
  <aliases>
...
  </aliases>
  <rules>
	...
    <rule component="system" enabled="yes" executable="java" installation_types="THICK" name="perfmon_service" resolvebyargs="yes">
		...
    </rule>
	<rule component="system" enabled="yes" executable="java" installation_types="THICK" name="eaglefilesystem" resolvebyargs="yes">
		...
	</rule>
	<rule component="system" enabled="no" installation_types="THICK" name="extractservicelb" path="$(ATPE_FOLDER)/java/bin/java" resolvebyargs="yes">
		...
	</rule>
	<rule component="system" enabled="no" installation_types="THICK" name="extractserviceworker" path="$(ATPE_FOLDER)/java/bin/java" resolvebyargs="yes">
		...
	</rule>
	<rule component="starweb" enabled="no" installation_types="THICK" name="redisserver" path="servers/redis/redis-server" resolvebyargs="no">
		...
	</rule>
	<rule component="starweb" enabled="no" installation_types="THICK" name="redissentinel" path="servers/redis/redis-sentinel" resolvebyargs="no">
		...
	</rule>
	<rule component="system" enabled="no" installation_types="THICK" name="kafkaservice" path="$(ATPE_FOLDER)/java/bin/java" resolvebyargs="yes">
		...
	</rule>
	<rule component="system" enabled="no" installation_types="THICK" name="kafkaservice" path="$(ATPE_FOLDER)/java/bin/java" resolvebyargs="yes">
		...
	</rule>
  </rules>
</processguard_custom>

Step 4: Restart services

Go to ${EAGLE_APP_TO_ROOT}/eaglemgr
Restart the emshell by executing the following command,

./restart emshell

Step 5: Validate services are up without any disabled services

Go to ${EAGLE_APP_TO_ROOT}/eaglemgr
Restart emshell by executing following command

./status starweb

After the restart, none of the disabled services should appear in the status. If the status display as below, you have successfully disabled/removed MC2.

|----------------------------------------------------------------------------|
|-------------------- Services & Engines Restart utility --------------------|
|--------------------------- version 2013.4.5.73 ----------------------------|
|----------------------------------------------------------------------------|
|---------------------- Asking process(es) status... ------------------------|
[14:11:41.137]  Status:
[14:11:41.137]  +-----------------+--------+-------------+---------+---------+----------+----------+--------------------+
[14:11:41.137]  |       Rule name |    PID |      Status | CPU (%) | VM (MB) | RSS (MB) | Revivals |     Internal state |
[14:11:41.137]  +-----------------+--------+-------------+---------+---------+----------+----------+--------------------+
[14:11:41.137]  |     mcprocessor |  48105 |     Running |       0 |    4752 |     4233 |        1 |                N/A |
[14:11:41.137]  |     mcprocessor | 127264 |     Running |       0 |    2290 |     1744 |        1 |                N/A |
[14:11:41.137]  |        mcreader | 117872 |     Running |       1 |     779 |      125 |        0 |                N/A |
[14:11:41.137]  |    schprocessor | 110934 |     Running |       0 |     908 |      572 |        0 |                N/A |
[14:11:41.137]  |    schprocessor | 110954 |     Running |       0 |     907 |      564 |        0 |                N/A |
[14:11:41.137]  |       schreader | 111108 |     Running |       0 |     409 |      141 |        0 |                N/A |
[14:11:41.137]  |   jmsbroker_dis |        | Not running |         |         |          |          |                    |
[14:11:41.137]  |      rt_service | 117925 |     Running |       0 |    2712 |     1022 |        0 |                N/A |
[14:11:41.137]  | perfmon_service | 110491 |     Running |       0 |    2128 |       75 |        0 |                N/A |
[14:11:41.137]  |    loadbalancer | 111328 |     Running |       0 |     279 |       22 |        0 |                N/A |
[14:11:41.137]  |       tpeserver | 111356 |     Running |       0 |     296 |       79 |        0 | initialized (100%) |
[14:11:41.137]  |     nasdaqifsvc | 111415 |     Running |       0 |     175 |        2 |        0 |                N/A |
[14:11:41.137]  +-----------------+--------+-------------+---------+---------+----------+----------+--------------------+
[14:11:41.137]  Exiting with code 0

Step 6: Clean up the installed components (Optional/Advanced)

As an optional step, if desired to remove any files, navigate to the installed location of each component and remove either individual files or the directory permanently from the disk (Location at table above).

For components installed in a shared path, the files only need to be removed once from the mounted drive.

For components installed in a local path, it is necessary to login to each node of the region and repeat steps 2 to 6.

Step 7: Clean up the database MC2 versions (Optional/Advanced)

After the deactivation / uninstall is completed, remove all installed / referenced MC2 components version entries from the database from the install date.

Uninstall MC2