Switching Between Stand-Alone and Server Cluster Configurations
If you upgrade a stand-alone instance of 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.
Note: For information about server clustering, see Server Cluster Configurations (Recommended).
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:
-
Stop all PPM Servers. (For instructions, see Start and stop the PPM Server on a single-server system.)
- Remove the additional node configuration from the
server.conf
file. - Remove the additional node file system from
<PPM_Home>/server
. -
Run the
kUpdateHtml.sh
script. -
After the script run is completed, run the
kStart.sh
script to start the PPM Server.
Note: For information about server clustering, see Server Cluster Configurations (Recommended).
To switch from a stand-alone to a server cluster deployment:
-
Stop the PPM Server. (See Start and stop the PPM Server on a single-server system.)
-
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
-
-
Save and close the
server.conf
file. -
Complete the PPM Server cluster environment setup as described in Configure a server cluster.
- Run the
kUpdateHtml.sh
script. -
After you complete the server cluster setup, follow the steps described in Verifying Successful Cluster Configuration.