Install an Additional Orchestrator › Install an Orchestrator

Install an Orchestrator

After you install the Domain Orchestrator, you can add Orchestrators on other hosts. Each new environment needs at least one Orchestrator, but can have more than one Orchestrator. Multiple Orchestrators permit segmentation. New Orchestrators inherit CA EEM information from the Domain Orchestrator.

Before you use the following procedure, complete the prerequisites to installing an Orchestrator. For example, verify that you have a JDK installed.

Use the following process to install an Orchestrator or to upgrade an existing Orchestrator.

Follow these steps:

1. Log in to the server on which to install the new Orchestrator.
2. Browse to CA Process Automation and log in with administrator credentials. For example, log in as a member of the PAMAdmins group.
3. Click the Configuration tab and select the Installation palette.
4. Click the prerequisites link and verify that all prerequisites have been met.
5. Click Install Orchestrator.

   If you use the Firefox web browser, open it with Java Web Start Launcher (the default).

   If necessary, install the required certificate as instructed. The application downloads. The Language Selection dialog may appear in the system tray.

6. Select a language and click OK.

   The Welcome to the CA Process Automation Third-Party Installer Setup wizard page appears.

7. Click Next.
8. Accept the licensing agreement, and click Next.
9. Accept the default installation directory (install_dir) or change it, and click Next.
10. Click Next on the Prerequisites for CA Process Automation Installation page.

    The Installing JBoss page shows the progress of installing jboss-5.1.

11. Specify JDBC jars for installation in one of the following ways:
    • Leave the Use Domain check box selected and click Next. This specifies to use the JDBC jars that the Domain Orchestrator installation configured.
    • Complete the following procedure:
      1. Clear the Use Domain check box.
      2. Click Add Files.
      3. Select the database server type.
      4. Click Browse and navigate to the JDBC JAR file for the selected server type.
      5. Click Next.
12. On the confirmation screen, click Next.
13. Click Finish to advance to the CA Process Automation installer.
14. Click Next on the Welcome screen.
15. Accept the license agreement and click Next.
16. Take one of the following actions on the Java Home Directory page:
    • Click Next to accept the default.
    • Browse to the JDK location and click Next.
17. View the Domain URL, and click Next.
18. If you are not using Single Sign-on a load balancer, click Next and skip the following step.
19. Complete this page and click Next.

    Configure Single Sign-on (SSO)

    Specifies whether you are using CA SiteMinder with SSO, where the default is cleared. Selecting this option enables these fields:

    • SSO Authentication Type (Header)
    • SSO Authentication Parameter (sm-user)
    • Type of server (New Orchestrator)

    Configure Load Balancer

    Specifies whether to install this Orchestrator so it can cluster.

    Selected

    Indicates that a load balancer is configured for this Orchestrator.

    Cleared

    Indicates that no load balancer is configured for this Orchestrator.

    Load Balancer Worker Node

    Specifies the name of this node. Because this Orchestrator is the first node in this cluster, specify node1.

    Note: For nodes other than node1 (for example, node 2), see:

    • Adding a Node to the Domain Orchestrator.
    • Adding a Node to an Additional Orchestrator.

    Public Host Name

    Specifies the public host name for the Apache server, NGINX server, or the F5 server. For example:

    loadbalancerhost.mycompany.com
    

    • Set this field to the FQDN of the Apache, F5, or NGINX load balancer if you selected the Configure Load Balancer check box.

    Public Host Port Number

    If Support Secure Communication is cleared, this field specifies the HTTP port for the Public Host.

    Default

    80

    Public Host Secure Port

    If Support Secure Communication is selected, this field specifies the HTTPS port for the Public Host.

    Default

    443

    Support Secure Communication

    Specifies whether the Public Host uses HTTPS for secure communication.

    Selected

    The Public Host uses HTTPS for secure communication.

    Cleared

    The Public Host does not use HTTPS for secure communication; instead, it uses HTTP for basic communication.

20. View the Company Name, and click Next.
21. Enter the certificate password that the Domain Orchestrator uses, and click Next.

    If this certificate password is lost or forgotten, you must reinstall all Orchestrators in the CA Process Automation system and specify this certificate password, beginning with the Domain Orchestrator.

22. Specify Start Menu Folder preferences and click Next.
23. Enter the General Properties for the Orchestrator, and click Next.

    Server Host

    Specifies the FQDN of this Orchestrator.

    Display Name

    Specifies the name that the Configuration Browser displays for this Orchestrator.

    • If you do not configure a load balancer, the Display Name is the Server Host name.
    • If you configure a load balancer, the Display Name is the FQDN of the server that hosts the load balancer.

24. Accept the default or set the temporary directory in which to run scripts, then click Next.
25. Set the PowerShell run policy and click Next.
26. Enter the Repository database settings for this Orchestrator in one of the following ways:
    • To share the Repository (Library) data store that the Domain Orchestrator uses, complete the following procedure:
      1. Enter the same information that you configured for the Domain Orchestrator.
      2. Click Test Database Settings.
      3. Click Next.
    • To create a separate Repository (Library) data store for this Orchestrator, complete the following procedure:
      1. For MS SQL or MySQL, enter a unique name for the new database in the Repository database field.
      2. For Oracle, enter an existing schema in the User Name field that is different from the schema defined for the Repository data store used by the Domain Orchestrator.
      3. For MS SQL or MySQL, click Create Database to create the new database.
      4. Click Test Database Settings
      5. Click Next.
27. Enter the Runtime database settings. Each Orchestrator requires a separate Runtime data store.
    1. If the new Runtime data store resides in the same database instance as the Repository data store for this Orchestrator, click Copy from the Main Repository.
    2. If the database instance you specify hosts other Runtime data stores, proceed based on your database type.
       • For MS SQL or MySQL, enter a unique name for the new database in the Runtime database field.
       • For Oracle, create a new schema, if needed, and specify the schema in the User Name field.
    3. For MS SQL and MySQL, click Create Database.
    4. Click Test Database Settings.
    5. Click Next.
28. View Reporting Database Settings and click Next. All Orchestrators in the Domain share the same Reporting data store.
29. Click Finish.