Reconfiguring Sentinel's references to the database server

During the lifetime of a Sentinel deployment it is almost inevitable that an IP address for a critical server will change. For many of the components this is a trivial issue but to change the IP address of the server hosting the database there are some specific steps which must be followed. Doing otherwise will prevent archival of events after they are processed, correlated, and displayed in real-time by the components that work in real-time (Sentinel Control Center, Correlation Engine, etc.).

To update the configuration on the Sentinel server there are two steps. First run the 'dbconfig' script in $ESEC_HOME/sentinel/config (.bat on windows, .sh on Unix and Linux).

If all references to the database server are not updated in $ESEC_HOME/configuration.xml those may need to be done manually.