Upgrading a PPM Server Cluster

To upgrade a PPM server cluster, Tomcat clustering technology requires parameters that are specific to the cluster, as well as parameters that are specific to each node in the cluster. Without this configuration, all nodes would use the same default port configuration, which can lead to server startup failure or other problems.

Note: Make sure that you set the cluster-specific and the server-specific parameters before you begin the upgrade process. The Installation and Administration Guide provides information on all of the server configuration parameters required for server cluster setup.

To upgrade a PPM server cluster:

  1. Make sure that you have set up a shared folder to give all nodes in the cluster access to the server.conf file. (See "Task 13: Setting Up a Shared Folder for a Server Cluster" in Preparing to Upgrade.)

  2. Stop all nodes in the cluster.

    Note: For information on how to stop and start a PPM Server, see the Installation and Administration Guide.

  3. Perform the upgrade on the primary node in the cluster. (See Upgrading On a Windows System and Upgrading On a UNIX System.)

    Note: When you run the upgrade on the first server, both the file system and the database portions of the upgrade are executed.

  4. If the nodes in the server cluster are hosted on multiple machines, run the upgrade on each host machine, one at a time.

    After you configure the first server to include all additional nodes,

    1. Copy the entire <PPM_Home>/ directory from machine1 to machine2, to the BASE_PATH defined in the @node directive.

    2. Zip the file, send it using FTP, and then unzip it at the destination.

    3. After you copy the file, change the directory to <PPM_Home>/ on the new machine, and then rename the <PPM_Home>/server/node1 directory to <PPM_Home>/server/node2.

      The server name must match the value set for the KINTANA_SERVER_NAME parameter.


      The directories on machine1 could be:

          + server/
          + node1

      The directories on machine2 could be:

          + server/
          + node2
    4. Put a new license on machine2, as required by the new IP address.

      Run kUpdateHtml.sh on both host machines to apply the server.conf changes.

    5. Repeat step a through step d on each of the remaining host machines in the cluster.

    Note: This upgrades only the file system on subsequent machines, without upgrading the PPM database schema.

  5. Restart the nodes, one node at a time.

    Caution: Make sure that you wait until each node is fully started before you start the next node.

Note: You can define all nodes (clustering ports and node-specific configuration settings) in a single server.conf file, even if they are distributed among different machines. Each node configuration correctly reflects the same information. This allows scripts such as kStatus.sh to gather information from all the nodes in the cluster, and not just the nodes that reside on the machine from which you run the script. You can reuse this server.conf file on other machines with nodes that are part of the same cluster. This assumes that you modify the machine-specific server configuration parameter values.

For detailed information about server cluster configurations, see the Installation and Administration Guide.