External web server, multiple machines

In a server cluster, a <PPM_Home> directory must reside on each machine, each with a server running against the same database.

To set up a cluster with an external Web server on multiple machines:

Install the PPM Server on the first machine in the cluster and configure it so that it is integrated with an external Web server.

Note: For information about how to configure a machine for integration with an external Web server, see Configure an external web server. For information on how to integrate the PPM Server with an external Web server, see.Integrate an external web server with a PPM Server.
Stop the PPM Server. (See Start and stop the PPM Server on a single-server system.)
Stop the external Web server.
Make sure that the common directories that the servers use (<PPM_Home>/logs, <PPM_Home>/reports, <PPM_Home>/attachments, and <PPM_Home>/transfers) are shared.

Note: Set the permissions for the shared directories so that users of each machine in the cluster can read from and write to them.
Modify the workers.properties file to include relevant information about the nodes in the cluster. (See Configure the Workers Properties file.)
Modify the server.conf file to include an @node directive for each node in the cluster, including those hosted on different machines.
If the nodes in the cluster are running on different machines, specify the SERVER_NAME=<Host_Name> server configuration directive for each @node section.
Note: You must specify the BASE_LOG_DIR, REPORT_DIR, ATTACHMENT_DIRNAME, and TRANSFER_PATH. The rest of the log directories are derived from these four directories. Consider specifying these before the first @node so that you do not have to specify them in each and every @node section.

On a Windows system, you must use the UNC format. You cannot use the local shared drive letter. Use forward slashes.

Example
```
//<Host_Name>/<Drive_Letter><Path>)
```
To enable a node to share these directories, you must start the PPM Windows services using the OpenText PPM user account that has read and write permission on the shared host.

//com.kintana.core.server.TRANSFER_PATH=//kiwi/e$/PPM_Prod/transferpath

On a UNIX system, you must NFS-mount the shared directories locally with the same directory structure.
In the server.conf file, before the first @node directive, add the cluster-specific parameters listed in Server parameters required for server clustering.
After each @node directive, do the following:
1. Set values for the parameters listed in Table 1. Server configuration parameters affected by clustering (External Web Server, Multiple Machines column). The values should be the same for all nodes in the cluster.
2. Add and specify unique values for the parameters described in Table 3. Required node-specific parameter for multiple nodes on a single host. (For your convenience, PPM provides port set values that you can use for up to five separate nodes in a cluster. These port sets are listed in Sample Port Sets.)
To apply the changes to all nodes on the machine that are part of the cluster, from <PPM_Home>/bin, run kUpdateHtml.sh.
After you configure the first server to include all additional nodes, copy the entire <PPM_Home>/server directory from machine1 to machine2, to the BASE_PATH defined in the @node directive.
Zip the file, send it using FTP, and then unzip it at the destination.
After you copy the file, change the directory to <PPM_Home>/server on the new machine, and then rename the node1 directory to node2.
The server name must match the value set for the KINTANA_SERVER_NAME parameter.

Example

The directories on machine1 could be:
```
<PPM_Home>
    + server/
    + node1
```
The directories on machine2 could be:
```
<PPM_Home>
    + server/
    + node2
```
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.
Start the PPM Server using the Windows service.

In a multiple-machine configuration, you must generate the services on all machines running Windows.
Generate a new service for the new node, as follows:
1. Open a command prompt, and then change to the <PPM_Home>\bin directory.
2. Run ksvc.exe, as follows:
```
ksvc install <PPM_Server_Name> -kh <PPM_Home> -jh <JAVA_HOME>
```
  Note: The value of <PPM_Server_Name> is the same as the value set for the KINTANA_SERVER_NAME parameter in the server.conf file.
  
  To create a Windows service for the nodes in a cluster, run ksvc.exe for each node in the cluster.
  
  Examples:
```
ksvc install <Node1_Name> -kh <PPM_Home> -jh <JAVA_HOME>
```
```
ksvc install <Node2_Name> -kh <PPM_Home> -jh <JAVA_HOME>
```
```
ksvc install <Node3_Name> -kh <PPM_Home> -jh <JAVA_HOME>
```

Note: The keys in the security directory are required to read encrypted values in server.conf and the database. The same keys must be present on all nodes in the cluster.