Prerequisites to Installing a Cluster Node for an Orchestrator

Add a Node to an Additional Orchestrator › Prerequisites to Installing a Cluster Node for an Orchestrator

Prerequisites to Installing a Cluster Node for an Orchestrator

You can install a cluster node for an Orchestrator. A cluster node extends the processing power of an Orchestrator and therefore can improve performance. A cluster node shares the same data stores that were configured for the other existing nodes which are a part of the Orchestrator cluster.

Before installation, perform the following prerequisites:

Follow these steps:

Identify a host for the Orchestrator cluster node that meets platform and hardware requirements. See the Orchestrator component in the following two topics:
- Platform Support and Requirements for CA Process Automation Components.
- Hardware Requirements.
Verify that the host for this cluster node is in the same subnet as the other existing nodes which are a part of the Orchestrator.
Verify that the host for this cluster node is in the same timezone as the other existing nodes which are a part of the Orchestrator.
Verify that the host for this cluster node has a supported JDK, and if missing, download it.
See JDK Prerequisites.
If the host for this cluster node is running a recent version of a Windows operating system, review the User Account Control option (in the Control Panel, User Accounts). If this option is turned on, clear the check box and reboot this server.
If the Orchestrator was configured with an F5 load balancer, add this node to the load balancer.
See Create an F5 Node for Each Cluster Node.

If this is the first node, see F5 Load Balancer Prerequisites.
If the Orchestrator was configured with an Apache load balancer, add this node to the load balancer.
1. Navigate to apache_install_location\conf.
2. Open the workers.properties file.
3. Uncomment the following lines under Define Node 2 in worker.properties file.
```
worker.node2.port=8009
```
```
worker.node2.host=hostname
```
```
worker.node2.type=ajp13
```
```
worker.node2.lbfactor=1
```
4. Change hostname to the host name of the server where the Orchestrator node is being installed.
5. Add “node2” to the worker.loadbalancer.balance_workers= line under Load-balancing behavior. The entry resembles the following:
```
worker.loadbalancer.balance_workers=node1,node2
```
  Note: For third and subsequent nodes, follow the same instructions, but substitute the correct node number for node2, for example, node3 or node4.
6. Restart Apache.

If the Orchestrator was configured with an NGINX load balancer, add this node to the load balancer.

Navigate to and open the pam-server.conf file.
Find the #Define node2 line. (The node1 data refers to the first Orchestrator node; skip sections that refer to node1.)

Insert the following

# Define node2
  server node2_hostname:jetty_server_port max_fails=3 fail_timeout=3s;
}

Note: The jetty server port is the “Server Port” value supplied during installation of the first node of the Domain Orchestrator. Enter 80 for simplified communication or enter 7003 for deprecated communication.

Inside server tag create following entries:

Server{
     location = /ws {
...
                // node2 is the upstream name provided above               
                proxy_pass http://node2;                                                           
                }  
     location /ws/node2/ {
                // node2 is the upstream name provided above               
                proxy_pass http://node2;                                           
                }
}