A Sentinel Server is made up of the following components:
Communication Server
Correlation Engine
DAS
Collector Manager
Any combination of the above components can be installed in a particular Sentinel Server.
In a distributed installation of Sentinel, it is likely that there will be more than one machine with a Sentinel Server running on it. In this case, all of the Sentinel Servers work together to provide the complete Sentinel functionality.
NOTE:At most one Communication Server and DAS component can be installed across all Sentinel Servers in a distributed Sentinel installation. On the other hand, multiple instances of Correlation Engine and Collector Managers are allowed.
When a Sentinel Server is started or stopped, all components installed in that Sentinel Server are also started or stopped. To start or stop a particular component on a Sentinel Server, use the Servers View under the Admin tab in Sentinel Control Center.
You need to start or stop a Sentinel Server because of the following routine maintenance:
Upgrades
Patches
Hotfixes
Log into the machine where the Sentinel Server you want to start is installed as the Sentinel Administrator operating system user (by default esecadm).
Go to the $ESEC_HOME/bin directory.
Run the following command:
./sentinel.sh start
Click Start > Settings > Control Panel.
Double-click Administrative Tools.
Double-click Services.
In the Services window, highlight Sentinel.
Right-click >Start or click Start in the tool bar.
Log into the machine where the Sentinel Server you want to stop is installed as the Sentinel Administrator operating system user (by default esecadm)
Go to the $ESEC_HOME/bin directory.
Run the following command:
./sentinel.sh stop
Click Start > Settings > Control Panel.
Double-click Administrative Tools.
Double-click Services.
In the Services window, highlight Sentinel.
Right-click >Stop or click Stop in the tool bar.