Install an Additional Orchestrator › Prerequisites to Installing an Orchestrator

Prerequisites to Installing an Orchestrator

You can install an Orchestrator in the environment with the Domain Orchestrator or in a separate environment. Before installing an Orchestrator, perform the following prerequisites:

Follow these steps:

1. Identify a host for the Orchestrator 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.
2. Verify that the host for the Orchestrator has a supported JDK, and if missing, download it.

   See JDK Prerequisites.

3. Have at hand the certificate password used for the Domain Orchestrator. This password controls access to the keys used to encrypt passwords and other critical data.

   Important! You cannot successfully install another Orchestrator without this password.

4. Identify the type of databases for the CA Process Automation data stores. Consider the following factors:
   • Each Orchestrator must have its own Runtime data store.
   • An Orchestrator can share the Library data store of the Domain Orchestrator or have its own Library data store. All Orchestrators in the same environment typically share the same Library data store
   • Typically, all Orchestrators in the Domain use the Reporting data store created for the Domain Orchestrator.
5. Prepare the database servers.
   • See Database Server Prerequisites.
   • A database server must meet platform and hardware requirements. See the Database Server component in the following two topics:
     • Platform Support and Requirements for CA Process Automation Components.
     • Hardware Requirements.
6. Evaluate the need for a load balancer for this Orchestrator. CA Process Automation supports the following methods of balancing clustered Orchestrators.

   Note: We recommend a hardware load balancer. See F5 Load Balancer Prerequisites. If this is not possible, we recommend NGINX as the software load balancer of choice. NGINX for UNIX is highly scalable. NGINX for Windows can support up to 300 agents using simplified communication. See NGINX Load Balancer Prerequisites.

7. If you plan to cluster this Orchestrator using NGINX, take the following additional steps:
   1. Navigate to and open the pam-server.conf file.
   2. Find the #Define node1 line. (The node1 data refers to the Orchestrator node that is installed first.)
   3. Insert the following, where the jetty_server_port is the value configured at installation for Server Port. Typically, the values are 80 for simplified communication or 7003 if agents that connect to this Orchestrator use deprecated communication.

      // node1 is the worker node name
      upstream node1{
        # Define node1
        server node1_hostname:jetty_server_port max_fails=3 fail_timeout=3s;
      }     
      

   4. Inside Server tag create following entries:

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

8. Identify a time server (NTP server). Configuring all Orchestrators to use the same external time server (or local time server) is the best way to ensure synchronization.
9. Ensure that the following are started before browsing to CA Process Automation to begin the installation of an Orchestrator:
   • CA EEM.
   • The load balancer, if used.
   • The Domain Orchestrator service.
   • The database server that hosts the databases you plan to use for the Runtime data store and optionally, a separate Repository (or Library) data store.