Switch between Stand-Alone and Server Cluster configurations

If you upgrade a stand-alone instance of OpenText PPM, and you later determine that a server cluster configuration better meets the needs of your organization, you can switch to a clustered server setup. Conversely, if you have configured a server cluster for a test or development instance and you determine that a stand-alone setup would be adequate for your immediate needs, you can transition to a stand-alone deployment. This section provides instructions for performing both of these transitions.

In this topic:

Switch from Server Cluster to Stand-Alone Configuration

If you plan to migrate data from a Production instance to a Development, Test, or Sandbox instance, and you do not want to migrate all the cluster configurations, you can switch from a server cluster to a stand-alone deployment.

To switch from a server cluster configuration to a stand-alone configuration:

1. Stop all PPM Servers. (For instructions, see Start and stop the PPM Server on a single-server system.)

2. Remove the additional node configuration from the server.conf file.
3. Remove the additional node file system from <PPM_Home>/server.

4. Run the kUpdateHtml.sh script.

5. After the script run is completed, run the kStart.sh script to start the PPM Server.

Back to top

Switch from Stand-Alone to a Server Cluster Configuration

To switch from a stand-alone to a server cluster deployment:

1. Stop the PPM Server. (See Start and stop the PPM Server on a single-server system.)

2. Make sure that the following server cluster-related parameter is in the server.conf file (located in the <PPM_Home> directory), and that it is uncommented:

   • APP_SERVER_UIL2_BINDING_PORT

3. Save and close the server.conf file.

4. Complete the PPM Server cluster environment setup as described in Configure a server cluster.

5. Run the kUpdateHtml.sh script.

6. After you complete the server cluster setup, follow the steps described in Verifying Successful Cluster Configuration.

Back to top