Install external Operations Orchestration

Install Operations Orchestration to the correct version and patch level.

If you are using an existing installation of Operations Orchestration, verify that the correct versions of patches and updates have been applied. See the Codar System and Software Support Matrix for version requirements.

If you are using an earlier version of Operations Orchestration:

You must upgrade the HPE Operations Orchestration to supported version given in Codar System and Software Support Matrix before installing Codar.

After upgrading Operations Orchestration to the supported version, update it by following the instructions below.
Caution: The Codar Installer installs an Embedded Operations Orchestration new instance during a new Codar 1.90 installation. The installer will also uninstall the same Embedded Operations Orchestrationinstance, regardless of whether it was loaded into a default or non-default installation path.

Configure an internal user

This internal user is used to configure Operations Orchestration for HCM ARA. This step is required if you are going to integrate Operations Orchestration with HCM ARA using the installer.

To configure an internal user, do the following:

  1. Log in to the existing Operations Orchestration Central.
  2. Click the System Configuration button.
  3. Select Security > Internal Users.
  4. Click the Add (+) icon.
  1. Enter the following information:

    Field Recommended value
    User Name admin
    Password cloud
    Roles ADMINISTRATOR, SYSTEM_ADMIN
  2. Click Save.

Export Operations Orchestration root certificate

Export the Operations Orchestration certificate from the Operations Orchestration truststore.

If Operations Orchestration and HCM ARA are not installed on the same system, copy the certificate to the HCM ARA system. This certificate will be imported into the HCM ARA truststore by the HCM ARA installer. SSL must be configured between HCM ARA and Operations Orchestration.

For example, do the following:

  1. On the system running Operations Orchestration, open a command prompt and change to the directory where Operations Orchestration is installed.
  2. Run the following command:

    For Operations Orchestration 10.21 on Windows:
    .\java\bin\keytool -export -alias tomcat -file C:\oo.cer -keystore .\Central\var\security\key.store -storepass <password>

    For Operations Orchestration 10.21 on Linux:
    ./java/bin/keytool -export -alias tomcat -file /tmp/oo.cer -keystore ./Central/var/security/key.store -storepass <password>

    where C:\oo.cer and /tmp/oo.cer are examples of file names and locations used to store the exported root certificate (you can choose a different file name and location).

  3. If Operations Orchestration is not running on the same system as Application Release Automation, copy oo.cer from the Operations Orchestration system to the system running Application Release Automation.