Novell SENTINEL 6.1 SP2 - 02-2010 User Manual page 31

You might need to update all the machines (which have components affected by the hostname
change) before you restart Sentinel service on any machine.
Scenario 1: Change in Sentinel Database Hostname
In this scenario, the affected components are DAS and SDM. So you might need to
Update the DAS

Update SDM

The configuration file enables DAS to connect to the database. So, you need to update the
configuration files to update DAS.
To update DAS:
1 Login to the machine where DAS is installed as esecadm (on UNIX), or as an administrator (on
Windows).
2 Stop the Sentinel Services running on the machine.
3 Go to ESEC_HOME\bin:
 On Unix, type the command cd $ESEC_HOME/bin
 On Windows, type the command cd /d %ESEC_HOME%\bin
4 Update DAS configuration files on Unix and Windows using the following commands.
 On Unix, execute
 On Windows, execute
You require the Database Hostname to login to SDM. To login to SDM, you might need to update
the Database Hostname in SDM login window.
To Update SDM
1 Open Sentinel Data Manager.
2 In the login window, provide details of the Database, new hostname and other required details.
3 Click Connect.
Scenario 2: Change in Sentinel Communication Server Hostname
In this scenario, the affected components are Communication Server, DAS, Correlation Engine,
Sentinel Collector Manager and Sentinel Control Center. So you might need to
Update the Communication Server

Update DAS, Correlation Engine, Sentinel Collector Manager, Sentinel Control Center

You might need to re-install the Communication Server to update the Hostname change.
To re-install Communication Server:
1 Login as root (Unix) or administrator (Windows) on the system where the Communication
Server is installed.
./dbconfig -a ../config -h <new DB hostname>
.\dbconfig -a ..\config -h <new DB hostname>
.
.
Sentinel Control Center 31