Installing a CDP

This topic describes how to use the GUI installation program to install a configuration distribution peer (CDP). During installation of a CDP, the installation program searches for and uses the configuration settings for the repository.

Note

If you are installing a non-English version of the Operator Control Panel, you must install it separately from the CDP. You must install the non-English OCP and CDP on separate Tomcat servers.

Before you begin

If you are using the external Remedy Single Sign-On authentication system, you must have already installed it and it must be running.
The repository must be installed and running.

You must have completed the CDP installation worksheet.

You must be logged on as an administrator and have administrator rights for the computer on which you install the CDP.
- On Microsoft Windows, you must have administrator permissions.
- On Linux and Solaris, any non-root user with write permission to the /opt/bmc directory can perform the installation.
  On Linux and Solaris, the non-root user must also have permission to run the following commands:
- - dmidecode -t 1 | grep Manufacturer
  - lsb_release -d

Ensure that you have the lsb_release command in the /usr/bin directory and that you can run it. Use the steps for your operating system.
- Red Hat Linux 7 machines:
1. 1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
    which lsb_release
    For example,
    [root@localHost ~]# which lsb_release
    If it is available, you will see the following response:
    /usr/bin/lsb_release
  2. If the command is available, verify that you can run it using the following command:
    lsb_release -d
    For example,
    [root@localHost ~]# lsb_release -d
    If it runs correctly, you will see a response similar to the following:
    Description: Red Hat Enterprise Linux Server release 7.0 (Maipo)
    
    or...
    If the command is not available, copy it from a RHEL6 machine to the RHEL7 machine as follows:
    1. Navigate to the /usr/bin directory and run the scp command to copy the lsb_release command from the RHEL6 machine to the RHEL7 machine.
      scp lsb_release root@<rhel7MachineHostname/IPaddress>:/usr/bin/
    2. On the RHEL7 machine, repeat steps a and b to verify that the command is in the /usr/bin directory and that you can run it.
- SUSE Linux machines:
1. 1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
    which lsb_release
    For example,
    [root@localHost ~]# which lsb_release
    If it is available, you will see the following response:
    /usr/bin/lsb_release
  2. If the command is available, verify that you can run it using the following command:
    lsb_release -d
    For example,
    [root@localHost ~]# lsb_release -d
    If it runs correctly, you will see a response similar to the following:
    Description: SUSE Linux Enterprise Server 11 (x86_64)
    or....
    If the command is not available, download it from the internet or from your operating system vendor's website.
You must have exited all other programs.

Related topics

Where to find more information

System requirements

Deployment use cases

Preparing for installation

CDP installation worksheet

Installing

Upgrading

If a problem occurs

Where to find more information

Troubleshooting the installation

Installation log files

To install a CDP

Navigate to and start the installation program for your operating system. See Performing the installation for the installation program names.
On the splash screen, select the language in which to view the installation program, and click OK.
On the Welcome to TrueSight Orchestration panel, review the information, and click Next.
On the license agreement panel, select I agree to the terms of the license agreement; then click Next.
On the Installation Type panel, select Install new Orchestrator components, and click Next.
Using the installation worksheet, fill in the settings to install the CDP.
The installation program verifies the communication with the repository. If it detects any invalid or conflicting information, the installation process halts and an error message describes the problem. The installation process resumes after you provide valid values.
Review the information on the Installation Choices Summary panel, and click Copy Text to Clipboard to copy the summary of the connection details for further use.
Click Install.
On the Installation Summary panel, perform one of the following actions:
- To exit the installation program, click Done.
- To review the BAO_install_log.txt file, click View Log, and then click Done to exit the installation program.
Note

Cassandra database is installed out-of-the-box when you install the CDP or HA-CDP components. Cassandra database stores data for the jobs running on the Grid. This data is displayed on the Job List and Job View tabs on the Health Dashboard. For more information, see Apache Cassandra database.

Verify the CDP and embedded RSSO installation

To ensure that the CDP and embedded RSSO (if you chose this option) were installed successfully, use the instructions in Verifying a peer or embedded RSSO installation.

You can use the following user credentials to log into the CDP:

User name: aoadmin
Password: admin123

You can use the following user credentials to log into RSSO:

User name: Admin
Password: RSSO#Admin#

Note

If you are using Internet Explorer 8.0 or later, ensure that you add the URL for the TrueSight Orchestration Grid Manager in the trusted sites of the browser.
After you install all TrueSight Orchestration components and verify that they are successfully installed, BMC recommends that you change the passwords. See Creating and managing local users and roles in Remedy Single Sign-On for details.
If you are using embedded RSSO as an authentication system, ensure that you perform the post-installation tasks for embedded RSSO. For more information, see Configuring a fail-safe enterprise service bus after installation.

Adjust Default group permissions

After installing the primary CDP, the Default role has full access to the repository and to the grid, just as the AoAdmin role. Edit the Default role to remove the following permissions: Development Studio, Grid Administration, and Grid Management.

Warning

You must remove these permissions from the Default role so that all users do not have administrative permission.

See Assigning grid permissions for instructions on how to remove permissions.

Linux steps to support dmidecode

If you are installing in a Linux environment, you must complete the following instructions after the installation.

Add the path to the dmidecode executable location to the user's environment under which the TrueSight Orchestration service is running.
This supports running the dmidecode to gather operating system information by the Health dashboard.
To do this, edit the .bashrc file located in the $HOME directory and add the path.
For example, if the TrueSight Orchestration service is running under a user account called "tso", edit bao's .bashrc file and add the following lines:
set PATH=${PATH}:/usr/sbin export PATH
As root user, run the following command to update permissions so that non-root users can run the dmidecode command:
chmod g+s /usr/sbin/dmidecode
Restart the TrueSight Orchestration service (see Starting and stopping product components and services).

Where to go from here

You can install any of the following:

If you are using the embedded RSSO service, after installing your TrueSight Orchestration components you must complete the steps in Configuring a fail-safe enterprise service bus after installation.