Rehosting Administration Services when the host name is changed
When DB2, Registry Services, Administration Services, and Administration Services UI are deployed on the same server, how to rehost Administration Services when the host name is changed?
To rehost Administration Services, perform the following steps:
- Update the new host name in WebSphere Application Server profile.
Administration Services is deployed on WebSphere Application Server full profile, perform the steps as described in Changing host names.
If Administration Services is deployed on WebSphere Application Server liberty profile, perform the following steps:
- Edit the bootstrap.properties file located in the JazzSM_ Home\servers\JazzSM_liberty\ directory, and update the default.host property with the new host name value.
- Edit the server.xml file located in the WAS_Liberty_Home\wlp\templates\servers\defaultServer\ directory and update the http Endpoint element's host attribute with the new host name value.
- Reconfigure the JDBC data source used by Registry Services as follows:
- In the WebSphere administrative console, select Resources > JDBC > Data sources > frs_datasource > Custom properties.
- Select the Show all data source properties check box.
- Update data source serverName with the new value. For more information about how to update data source properties, see WebSphere Application Server data source properties.
- Reconfigure the host name in DB2. For more information, see http://www-01.ibm.com/support/docview.wss?uid=swg21258834.
Note: This step is not required when DB2 has been set up on a remote server.
- Update the following properties with the new host name value in the CLI.properties file, which is located in the Registry_Home\etc directory.
- Set the public URL of Registry Services to use the new host name in existing reference links.
frs.bat config -set public.url=https://NewHostName:16311
- Before you run this command, ensure that the values for the following properties in the CLI.properties file that is in the Registry_home\etc directory are correct: database user ID (ds.jdbc.user) and database password (ds.jdbc.password).
- This step is not required when Registry Services database has been set up on a remote server, and unless the host name of the server on which Registry Services is hosted has changed.
- Run remapURL Registry Services CLI command for the Provider Registry and Resource Registry.
frs.bat|sh remapUrl -registryType provider -patternRule https://OldHostName:16311 -replacementValue https://NewHostName:16311
frs.bat|sh remapUrl -registryType resource -patternRule https://OldHostName:16311 -replacementValue https://NewHostName:16311
Note: Before you run this command, ensure that the values for the following WebSphere Application Server properties in the CLI.properties file that is in the Registry_home\etc directory are correct: application user ID (appserver.user) and password (appserver.password).
- Update the host name in the serviceProvider.properties file that is located in the JazzSM_Home/admin/etc/ConfigServiceProvider/conf/ directory.
- Update the host name in the adminservicesgui.properties file that is located in the JazzSM_Home/admin_ui/etc/AdminServicesGUI/conf/ directory.
- Restart the application server.
- Stop the server. Go to the
/profile/bindirectory and run stopServer.bat
On Windows systems: stopServer.bat server_name
On UNIX systems: ./stopServer.sh server_name
- Start the server. Go to the
/profile/bindirectory, and run startServer.bat
On Windows systems: startServer.bat server_name
On UNIX systems: ./startServer.sh server_name
- Stop the server. Go to the
More support for:
Jazz for Service Management
Software version: 1.1
Operating system(s): AIX, Linux, Windows
Reference #: 1627548
Modified date: 20 February 2014