In this scenario, the affected components are Communication Server, DAS, Correlation Engine, Sentinel Collector Manager and Sentinel Control Center. So you may need to
Update the Communication Server
Update DAS, Correlation Engine, Sentinel Collector Manager, Sentinel Control Center
You may have to re-install the Communication Server to update the Hostname change.
To re-install Communication Server:
Login as root (Unix) or administrator (Windows) on the system where the Communication Server is installed.
Run Sentinel Uninstaller. In the Select components to Uninstall window, select Communication Server and deselect all other options.
Follow instructions in Uninstalling Sentinel in Sentinel 6.0 Installation Guide as required and complete uninstallation.
Click Finish.
Insert (and mount, on Solaris/Linux only) the Sentinel Installer CD.
Run the setup file. In the Select components to Install window, select Communication Server only.
Follow the instructions in Installing Sentinel 6.0 in Sentinel 6.0 Installation Guide as required and complete installation.
Reboot the system.
The configuration file that connects the Communication Server and Sentinel processes needs to be updated. You may have to perform the steps given below on all machines with DAS, Correlation Engine, Collector Manager, and Sentinel Control Center installed.
To update DAS, Correlation Engine, Collector Manager, and Sentinel Control Center:
Go to ESEC_HOME/config/ and edit configuration.xml.
Replace the four occurrences of the Communications Server Hostname with the new Hostname.
Save and exit the configuration.xml file.
IMPORTANT:
After the steps mentioned above are performed, restart the Sentinel Services for the changes to take affect.