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 all OpenPages application servers, including the deployment manager (if applicable).  See Stopping application servers for details.
3. On each reporting server in your deployment stop the IBM Cognos service.  See Starting and stopping the Cognos services for details.
4. If your deployment includes a Global Search server stop the global search services.  See Start or stop the global search services for details.
5. If your deployment includes a workflow server stop the IBM Business Process Manager services, including the deployment manager.

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 [db] section with the new hostname of the database server, and save the file.

Update the Hostname on the Database Server

Follow the steps provided in Changing hostname of the DB2 server to update the hostname on the database server.

Update the Hostname on the Deployment Manager Server

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>/temp/perlinstall/install.properties in a text editor, where <OP_HOME> is the location of your OpenPages installation.  Update the following properties using the new database server hostname, and save the file.
   • OP_JDBC_DB_URL
   • DATABASE_SERVER_NAME
2. Open the file <OP_HOME>/aurora/conf/aurora.properties in a text editor.  Update the following properties using the new database server hostname, and save the file.
   • database.HOSTNAME
   • database.URL
3. If the deployment manager is on a different computer than the database server, uncatalog and re-catalog the DB2 node:
   1. If you are using Microsoft Windows, start the DB2 command line processor.  Open a command prompt and run db2cmd.
   2. Determine the name of the DB2 node <node_name> by running the following command and examining the output: 

      db2 list node directory show detail

   3. Uncatalog the node by running the commands 

      db2 uncatalog node <node_name>
db2 terminate

      where <node_name> is the name of the cataloged DB2 node.

   4. Re-catalog the node by running the commands 

      db2 catalog tcpip node <node_name> remote <hostname> server <service_name|port_number>
      db2 terminate

      where <node_name> is the name of the cataloged DB2 node, <hostname> is the new hostname of the database server, and <service_name|port_number> is the connection info for DB2 on the database server (the default port value is 50000).

4. Start the deployment manager by running the command 

   <DMGRProfileHome>/bin/startManager.sh|.bat

   where <DMGRProfileHome> is the directory containing the deployment manager profile.

5. Go to the IBM WebSphere Integrated Solutions Console for the OpenPages Deployment Manager server:

   For example, http://<server_name>:<port>/ibm/console

   Where <server_name> is the name of the deployment manager server and <port> is the WebSphere port that is assigned during the WebSphere installation. The default port value is 9060.

6. Log on to the IBM WebSphere Integrated Solutions Console with an administrator account.
7. Navigate to Resources > JDBC > Data sources > CWTxDataSourceXA
8. Update the Server name property using the new database server hostname.
9. Click Apply, then click Save.

Update the Hostname on Each Application Server

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

1. Open the file <OP_HOME>/aurora/conf/aurora.properties in a text editor.  Update the following properties using the new database server hostname, and save the file.
   • database.HOSTNAME
   • database.URL
2. Open the file <OP_HOME>/installer/deploy.properties in a text editor.  Update the host property under the [db] section with the new hostname of the database server, and save the file.
3. If the application server is on a different computer than the database server, uncatalog and re-catalog the DB2 node:
   1. If you are using Microsoft Windows, start the DB2 command line processor.  Open a command prompt and run db2cmd.
   2. Uncatalog the node by running the commands 

      db2 uncatalog node <node_name>
db2 terminate

      where <node_name> is the name of the cataloged DB2 node.

   3. Re-catalog the node by running the commands 

      db2 catalog tcpip node <node_name> remote <hostname> server <service_name|port_number>
      db2 terminate

      where <node_name> is the name of the cataloged DB2 node, <hostname> is the new hostname of the database server, and <service_name|port_number> is the connection info for DB2 on the database server (the default port value is 50000).

4. 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 following properties using the new database server hostname, and save the file.
      • OP_JDBC_DB_URL
      • DATABASE_SERVER_NAME
   2. 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.

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

5. If your OpenPages version is 8.2 or higher, perform the following steps:

   1. 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, where <OP_HOME>  is the location of your OpenPages installation.  Update the property op.jdbc.host using the new database server hostname, and save the file.

   2. Start the OpenPages application servers.

Update the Hostname on Each Reporting Server

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

1. If the hostname of the database server hosting the IBM Cognos Content Store has changed, open <COGNOS_HOME>/configuration/cogstartup.xml in a text editor, where <COGNOS_HOME> is the location of your IBM Cognos Analytics installation.  Update the connection information for the IBM Cognos Content Store database, and save the file.
2. If the reporting server is on a different computer than the database server, uncatalog and re-catalog the DB2 node:
   1. If you are using Microsoft Windows, start the DB2 command line processor.  Open a command prompt and run db2cmd.
   2. Uncatalog the node by running the commands 

      db2 uncatalog node <node_name>
db2 terminate

      where <node_name> is the name of the cataloged DB2 node.

   3. Re-catalog the node by running the commands 

      db2 catalog tcpip node <node_name> remote <hostname> server <service_name|port_number>
      db2 terminate

      where <node_name> is the name of the cataloged DB2 node, <hostname> is the new hostname of the database server, and <service_name|port_number> is the connection info for DB2 on the database server (the default port value is 50000).

3. Start the IBM Cognos service.  See Starting and stopping the Cognos services for details.
4. Open a browser window and log on to the reporting portal as a user with administrative privileges.  By default, the URL is http://<server_name>/ibmcognos, where <server_name> is the host name of the reporting server.
5. Click Manage, then Administration console.
6. Click the Configuration tab, then click OpenPages DataSource under Data Source Connections.
7. Click the Set Properties icon.
8. Under the JDBC tab edit the Server name property using the new database server hostname, and click OK. 
9. Click OK again.

Update the Hostname on the Global Search Server

If your deployment includes a Global Search server, perform the following steps on your Global Search server:

1. Open the file <SEARCH_HOME>/opsearchtools/openpages_search.properties in a text editor, where <SEARCH_HOME> is the location of your Global Search installation.  Update the property OPSearchTool.DatabaseHostName using the new database server hostname, and save the file.
2. Start the global search services.  See Start or stop the global search services for details.

Update the Hostname on the Workflow Server

If your OpenPages version is prior to 8.2 and your deployment includes a workflow server, perform the following steps on your workflow server:

1. Start the IBM BPM deployment manager by running the command 

   <BPM_HOME>/profiles/<DmgrProfile>/bin/startManager.sh|.bat

   where <BPM_HOME> is the location of your IBM Business Process Manager installation, and <DmgrProfile> is the name of the deployment manager profile.

2. If the hostname of the database server hosting the IBM Business Process Manager databases has changed, update the data source information in IBM BPM.  See Updating IBM BPM data sources for details.
3. Open the file <OP_BPM_INTEGRATION_HOME>/installBPMIntegrationConfig.sh|.cmd in a text editor, where <OP_BPM_INTEGRATION_HOME> is the directory containing the integration files for OpenPages and IBM BPM.  Update the property jdbcUrl using the new OpenPages database server hostname, fill in the password properties, and save the file.
4. Run the integration script for OpenPages and IBM BPM.  See Running the integration script for details.