Steps

Prerequisite Steps

1. Ensure that all servers in the OpenPages deployment can successfully connect to the new hostname.  See Configuring the hosts file for details.
2. Stop OpenPages node and application server processes on the server with the changed hostname.  See Stopping application servers for details.
3. Make sure the OpenPages deployment manager is running (if applicable).

Update the Hostname on the Installation Server

Perform the following steps on the installation server:

1. Open the file <OPInstallerHome>/src/deployment/<deployment_name>/deploy.properties in a text editor, where <OPInstallerHome> is the location of the installer files and <deployment_name> is the name of your deployment in the OpenPages Installer.

2. Update the host property under the [app.serverX] section (where X is the index of the application server that has changed) with the new hostname of the application server, and save the file.

Update the Hostname on the Deployment Manager Server

Note: Only perform these steps if the hostname of the admin application server (Application Server #1) has changed, and if your OpenPages version is prior to 8.2.

Perform the following steps on the server hosting the OpenPages deployment manager:

1. Open the file <OP_HOME>/aurora/conf/aurora.properties in a text editor, where <OP_HOME> is the location of your OpenPages installation.  Update the property url.service.host using the new application server hostname, and save the file.

Update the Hostname on the Application Server

Perform the following steps on the application server with the changed hostname:

1. Open the file <OP_HOME>/installer/deploy.properties in a text editor.  Update the host property under the [app.serverX] section (where X is the index of the application server that has changed) with the new hostname, and save the file.
2. If the application server operating system is Linux or AIX, and the OpenPages database type is DB2, open the file <OP_HOME>/aurora/bin/db2stats/CollectSchemaStatistics.sh in a text editor.  Update the hostname following the argument OP_HOSTNAME= using the new hostname, and save the file.

3. If the OpenPages storage directory is located on the application server and is shared with other servers in your deployment, follow the steps under Additional Information for Updating the OpenPages Storage Directory Location.

4. Perform one of the following steps based on whether you are using a load balancer for your application servers:

   1. If you are using a load balancer for your application servers, update the configuration of your load balancer with the new application server hostname and restart it.  For example, if you use IBM HTTP Server to load balance your application servers, you must update the plugin files that were created for the web server (see Configuring IBM HTTP Server to load balance application servers for details).

   2. If you are not using a load balancer for your application servers, follow the steps under Additional Information for Updating the OpenPages Application URL.

5. If your OpenPages version is prior to 8.2, perform the following steps:

   1. Open the file <OP_HOME>/temp/perlinstall/install.properties in a text editor, where <OP_HOME> is the location of your OpenPages installation.  Update the property OP_HOST using the new hostname, and save the file.

   2. For each server <ServerName> in the node, open the file <OP_HOME>/temp/wasconfig/<CellName>.<ServerName>.config.props in a text editor, where <CellName> is the name of your OpenPages cell.  Update the property HOST using the new hostname, and save the file.

   3. Open the file <OP_HOME>/aurora/conf/aurora.properties in a text editor.  Update the property url.service.host using the new hostname, and save the file.

   4. For each server <ServerName> in the node, open the file <OP_HOME>/aurora/conf/<ServerName>-server.properties in a text editor.  Update the following properties using the new hostname, and save the file.
      • dmgr.hostname
      • jms.providerurl
      • jta.providerurl
      • security.providerurl
      • service.client.providerurl
      • url.repositoryService
      • url.service.clientapi
      • url.service.host
      • url.service.repository
      • url.service.rule
      • url.service.security
      • url.service.sitegenerator
      • url.service.transformation
      • webclient.http.server.name
   5. For each server <ServerName> in the node, open the file <OP_HOME>/aurora/conf/<ServerName>-sosa.properties in a text editor.  Update the property openpages.service.host using the new hostname, and save the file.
   6. Open the file <OP_HOME>/bin/ObjectManager.properties in a text editor.  Update the property openpages.service.host using the new hostname, and save the file.
   7. Open the file <OP_HOME>/bin/RunTool.sh|.cmd in a text editor.  Update the hostname following the argument -CCBootstrapHost= using the new hostname, and save the file.
   8. Run the sequence of commands 

      <WAS_HOME>\bin\wsadmin.bat -user <admin_username> -password <admin_password> -lang jython -conntype soap -host <DmgrHost> -port <DmgrSoapPort>
      AdminTask.changeHostName('-hostName <NewHostName> -nodeName <NodeName>')
      AdminConfig.save()
      exit

      where <WAS_HOME> is the installation location of IBM WebSphere Application Server, <admin_username> is the WAS admin username, <admin_password> is the WAS admin password, <DmgrHost> is the hostname of the deployment manager, <DmgrSoapPort> is the SOAP port of the deployment manager, <NewHostName> is the new hostname of the deployment manager, and <NodeName> is the name of the OpenPages node on the application server.

   9. Sync the application node by running the command 

      <OP_HOME>/profiles/<NodeName>/bin/syncNode.sh|.bat <DmgrHost> <DmgrSoapPort>

      where <NodeName> is the name of the OpenPages node on the application server, <DmgrHost> is the hostname of the deployment manager, and <DmgrSoapPort> is the SOAP port number of the deployment manager.

   10. Start the OpenPages node and application servers.  See Starting application servers for details.

6. If your OpenPages version is 8.2 or higher, perform the following steps:
   1. For each vertical cluster member <ServerName>, open the file <OP_HOME>/aurora/conf/<ServerName>-server.properties in a text editor.  Update the property webclient.http.server.name using the new hostname, and save the file.
   2. Open the file <OP_HOME>/bin/openpages-tools-client.properties in a text editor.  Update the property rest.url.path using the new hostname, and save the file.
   3. If working with the admin application server (Application Server #1), then for each vertical cluster member <ServerName> on the application server, open the file <OP_HOME>/wlp-usr/servers/<ServerName>/bootstrap.properties in a text editor.  Update the property op.jms.host using the new hostname, and save the file.
   4. Start the OpenPages application servers.

Update the Hostname on Each Reporting Server

Perform the following steps on each reporting server in your deployment:

1. Update the IBM Cognos Application Firewall settings with the new application server hostname.  See Adding OpenPages GRC Platform servers to the Cognos Application Firewall safe list for details.