Sentinel Agents
A Sentinel Agent is a small process that can start and stop Apama correlators and IAF adapters on the host where it is running. EMM starts and stops components on a particular host in a platform independent way by interacting with the Sentinel Agent running on that host. Therefore, a Sentinel Agent must be running on any machine where you intend to manipulate Apama components using EMM.
On Windows and UNIX, the Sentinel Agent can be started in one of these ways:
By starting the service. To do so, you must have administrator (Windows) or root (UNIX) privileges.
Before you can start the service, you first have to add it with the following command:
apama_services -add -s sentinel
After the service has been added, you can start it with the following command:
apama_services -start -s sentinel
You can stop the service with the following command:
apama_services -stop -s sentinel
You can uninstall the service with the following command:
apama_services -delete -s sentinel
By starting the executable. If you do not want to use the service, you can also start the Sentinel Agent executable manually. Running it from the Apama Command Prompt ensures that the environment variables are set correctly. See
Setting up the environment using the Apama Command Prompt. To start the executable, run
sentinel_agent.exe (Windows) or
sentinel_agent (UNIX) and pass command line arguments to it. See
Sentinel Agent options for further information.
Important! If you install the Sentinel Agent as a service or run it by starting the executable, you are responsible for stopping and/or uninstalling it before running the Software AG Uninstaller.
Any information written to stdout or stderr by components started with a Sentinel Agent will be logged in the Agent's log directory in files called <component-type>-<PID>-std{out,err}.log on UNIX and <component-type>-<num>-std{out,err}.log on Windows, where <PID> is the process ID and <num> is an integer number. Valid component types are correlator and adapter. The stdout / stderr logs will be deleted by Sentinel when the relevant component is stopped if they are empty (which should normally be the case).