The purpose of this document is to explain the steps needed in order for IM to run properly after changing the server name or after switching hosts.
This document refers to changing the server name. If the IP address was used in the configuration files, it too might need to be changed.
Changing the Identity Manager Server Name
This example assumes the following system configuration is installed (your configuration may vary):
Application Server: Jboss SiteMinder Policy Server User Interface on IIS 6.0 WebAgent (if installed) on IIS 6.0
Changing the WebAgent or Servet Filter Agent smhost configuration files
Modify the Agent objects (if SiteMinder server name was changed)
Modify the Application Server Plugin
JBOSS - Modify the Jakarta Plugin for IIS
- Modify the file workers.properties, located in Plugin folder (for example: c:\ISAPI).
- Change the field worker.jboss.host to the IM server name
WebLogic - Modify WLS Plugin on IIS
- Verify correct appserver(s) IP address(es) and port(s) are specified iisproxy.ini.
WebLogic - Modify WLS plugin on Apache
- Verify the correct application server is specified in the httpd.conf file, located in APACHE_HOME\conf\httpd.conf
Modify the server name in Identity Manager
Restart JBoss (or WebLogic) server.
Configuration change testing:Login to the environment and create a new user.
Modify the server name in eTrust Admin
If provisioning is configured in the IM environment, the IM server name should be modified in the IM extensions for eTrust Admin:
Test this change by creating a user in CA Admin and making sure it was created in IM.