Stop, Start, and Restart Extract Service
The Extract Service is fully integrated into the Engine Manager ProcessGuard and may be stopped, started and restarted using the emshell commands from the eagle/eaglemgr directory:
Stop the Extract Service:
./stop starweb extractservicelb extractserviceworker
Restart the Extract Service:
./restart starweb extractservicelb extractserviceworker
Start the Extract Service:
./start starweb extractservicelb extractserviceworker
Uninstall the Extract Service
To return to the original state of the instance:
- Run the command:
cd ~/eagle/eaglemgr./stop starweb extractservicelb extractserviceworker messagecenter - Restore the files from the backup files previously created:
- /eagle/eaglemgr/config/processguard.xml
- /eagle/estar/tpe/cfg/system.xml (or eagle/cfg/system.xml)
- /eagle/estar/tpe/cfg/msgcenter/msgservice.ini
- /eagle/estar/tpe/cfg/tpeserver.ini
- In the eagle/eaglemgr folder execute the following commands:
- /eagle/eaglemgr/config/processguard.xml
- /eagle/estar/tpe/cfg/system.xml (or eagle/cfg/system.xml)
- /eagle/estar/tpe/cfg/msgcenter/msgservice.ini
- /eagle/estar/tpe/cfg/tpeserver.ini
- In the eagle/eaglemgr folder execute the following commands:
./restart emshell
./restart starweb mcprocessor
./restart starweb mcreader
./restart starweb tpeserver
./status starweb
After completing these steps, the list of services will no longer contain the "extractservice": 
It is also possible to check that the Extract Service is stopped by executing a grep command:
ps -ef | grep extract
If the grep command produces a row similar to the example below appears, it means that the process was not stopped and needs to be killed using the kill command. For example, if the output is as shown in the image below use the kill command:
The command to run is (with 3241 representing the process id):
kill -9 3241
Run the above command for each of the java processes displayed by the ps command.
On this page
toc