Installation components and configuration changes
...
MC2 deployments includes the following components:
...
...
| title | MC2 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 |
...
After the install of MC2, the database is updated to reflect the installed eagle EagleML/MC2 versions.
...
| title | Image |
|---|
...
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.
...
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
Code Block language text ./stop starweb extractserviceworker extractservicelb kafkaservice redisserver redssentine
...