Integrate with Operations Orchestration

Complete the following tasks to configure Operations Orchestration to integrate with Codar:

Note In the following instructions, CSA_HOME is the directory in which Codar is installed and ICONCLUDE_HOME is where you installed Operations Orchestration.

Be sure all the latest patches for Operations Orchestration have been installed. See the Codar System and Software Support Matrix.

Add JRE to system path

The flows that are imported require that a JRE be included in the system path on the system running Codar.

To add a JRE to the system path on Windows, complete the following steps:

  1. Open the Environment Variables dialog:

    1. Right-click Computer and select Properties.
    2. Select Advanced System Settings.
    3. Click Environment Variables.
  2. Select the Path system variable.
  3. Click Edit.

  4. At the end of the value for Variable value, add a semicolon (;) and the following path:

    If Operations Orchestration and Codar are installed on the same system:

    ICONCLUDE_HOME\java\bin

    or

    If Operations Orchestration and Codar are installed on different systems:

    CSA_JRE_HOME\bin

  5. Click OK and close all windows.

To add a JRE to the system path on Linux, complete the following steps:

Open a shell and enter one of the following commands:

  • If Operations Orchestration and Codar are installed on the same system, enter this command:

    export PATH=$PATH:$ICONCLUDE_HOME/java/bin

  • If Operations Orchestration and Codar are installed on different systems, enter this command:

    export PATH=$PATH:$CSA_JRE_HOME/bin

Note By setting the system path, all applications (that require a JRE) use the JRE that is installed with Operations Orchestration or Codar (depending on the path you configured and if it is the only path or the first path set to a JRE in the system path). If you need to run another JRE with an application, you must type in the relative path to that JRE in order to run it (for example, when you configure TLS).

Install Codar content pack

If Codar and Operations Orchestration are running on different systems, copy the CSA_HOME\CSAKit-4.5\OO Flow Content\10X\oo10-csa-cp-4.50.0000.jar file from the Codar system to the Operations Orchestration system (where CSA_HOME is the directory in which Codar is installed).

Configure internal users

Internal users can be used to configure Operations Orchestration for Codar.

To configure an internal user, complete the following steps:

  1. Log in to Operations Orchestration Central.

  2. Click the System Configuration button.
  3. Select Security > Internal Users.
  4. Click the Add (+) icon.

  5. Enter the following information:

    Field Recommended value
    User Name codaroouser
    Password cloud
    Roles ADMINISTRATOR, SYSTEM, ADMIN

    The codaroouser user is used to import the Operations Orchestration flows. When importing flows, this user is configured in the Operations Orchestration input file used by the process definition tool.

  6. Click Save.
  7. Click the Add button.

  8. Enter the following information:

    Field Recommended value
    User Name admin
    Password cloud
    Roles ADMINISTRATOR, SYSTEM, ADMIN

    The admin user is used with Single Sign-On. When Operations Orchestration is launched from the Codar Console, this user allows access to Operations Orchestration without having to log in. If you are using topology designs, the admin user can also be used for provisioning topology designs.

  9. Click Save.
  10. Log out of Operations Orchestration Central and log back in as the codaroouser.

Deploy content packs required by Codar

To deploy content packs required by Codar, complete the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the Content Management button.
  3. Click the Content Packs tab.
  4. Click the Deploy New Content icon.
  5. In the Deploy New Content dialog, click the Add files for deployment icon.
  6. Click the Deploy New Content icon.
  7. Click the Add files for deployment icon.

  8. Navigate to the CSA_HOME/CSAKit-4.5/OOFlowContent/10X directory, select all content packs to be deployed, and click Open.

  9. Click Deploy.

    The deployment may take a few minutes and the dialog will show a progress bar.

  10. When the deployment succeeds, click Close to close the dialog.

Set up system accounts for Codar content pack

Set up system accounts for the Codar content pack by completing the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the Content Management button.
  3. Select Configuration Items > System Accounts.
  4. Click the Add (+) icon.

  5. Enter the following information if it is not already configured:

    Field Recommended value
    System Account Name CSA_REST_CREDENTIALS
    User Name ooInboundUser
    Passwords cloud

    Note The User Name configured for the CSA_REST_CREDENTIALS System Account setting must match the Override Value (Operations Orchestration version 10.21) configured for the CODAR_OO_USER System Property setting.

  6. Click Save.
  7. Click the Add icon.

  8. Enter the following information if it is not already configured:

    Field Recommended value
    System Account Name CSA_SERVICEMANAGER_CREDENTIALS
    User Name falcon
    Passwords <leave_blank>_
  9. Click Save.

Set up system properties forCodar content pack

Set up the following system properties for the Codar content pack by completing the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the Content Management button.
  3. Select Configuration Items > System Properties.
  4. Click the Add icon.

  5. Enter the following information if it is not already configured:

    Field Recommended value
    Name CSA_REST_URI
    Override Value https://<codar_hostname>:8444/csa/rest
  6. Click Save.

Configure Single Sign-On between Codar and Operations Orchestration

If Single Sign-On was enabled during installation of Codar, Single Sign-On can be configured between Codar and Operations Orchestration. Configuring Single Sign-On allows you to launch Operations Orchestration from the Codar Console without having to log in to Operations Orchestration.

Codar provides an out-of-the-box user (admin) and password (cloud) and, earlier in this guide, you configured an internal user for Operations Orchestration with the same username and password. When Single Sign-On is configured between Codar and Operations Orchestration, this user can be used for single sign-on. That is, if you are logged in to Codar as the admin user, you can launch Operations Orchestration from the Cloud Service Management Console and not have to log in to Operations Orchestration.

You can also configure LDAP users for single sign-on. In order to enable single sign-on for LDAP users, you must either configure Codar and the embedded Operations Orchestration to use the name LDAP source or, if Codar and the embedded Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the Codar user must be signed to the Codar Administrator or Service Operations Manager role and the embedded Operations Orchestration user must be assigned any role that allows flows to be viewed.

Note In order to use Single Sign-On between Codar and Operations Orchestration, the systems on which Codar and Operations Orchestration are installed must be in the same domain.

Configure and enable Single Sign-On

To configure and enable Single Sign-On on Operations Orchestration, complete the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the System Configuration button.
  3. Select Security > SSO.
  4. Select the Enable check box.
  5. Enter the InitString. This is the value to which the crypto InitString attribute is set in the CSA_HOME\jboss-as\standalone\deployments\csa.war\WEB-INF\hpssoConfiguration.xml file. For example, if the entry in the file is cryptoInitString="lOJisF9Slbf79hmLsd", copy lOJisF9Slbf79hmLsd to this field. This string is used to encrypt and decrypt the LWSSO_COOKIE_KEY cookie that is used to authenticate the user for single sign-on.
  6. Enter the Domain. This is the domain name of the network of the servers on which Codar and Operations Orchestration are installed.
  7. Click Save.
Configure LDAP users for single sign-on

In order to enable single sign-on for LDAP users, you must either configure Codar and Operations Orchestration to use the same LDAP source or, if Codar and Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the Codar user and the Operations Orchestration user must be assigned any role that allows flows to be viewed.

For more information on configuring LDAP in Operations Orchestration, see the Operations Orchestration Central Help.

Note One of the LDAP servers must be set to default in Operations Orchestration so that Codar can launch the Operations Orchestration page. Otherwise, an "access denied" error occurs.

To configure LDAP for Operations Orchestration complete the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the System Configuration button.
  3. Select Security > LDAP.
  4. Enter the information to configure LDAP.
  5. Click Save.

Configure secure connection between Codar and Operations Orchestration

If you integrated with Operations Orchestration using the installer (during the installation or upgrade process), you do not need to configure a secure connection (it has already been configured).

Send Help Center feedback