Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Verifying the BMC Atrium Orchestrator installation

After installing BMC Atrium Orchestrator, perform the following verification tasks.

To review the BMC Atrium Orchestrator installation log files

  1. If you just completed installing BMC Atrium Orchestrator and the installer prompts you to view the installation log, click View Log and skip to step 3.
  2. If you already exited the installation host, perform the following steps:
    1. Log on to the BMC Atrium Orchestrator host computer.
    2. Locate the installation directory for your operating system.

      Location of installation log files


      Default installation log location

      Red Hat Linux


      Microsoft Windows


    3. Open the log file that corresponds to the installation type, as shown in the following table:

      Installation log file names

      Installation type

      Installation log file name

      Platform and all components included in the installation

      Includes installation information for the Access Manager, repository, configuration distribution peer (CDP), and all optional components such as secondary peers

      BMC Atrium Orchestrator Development Studio

      Includes the installation information for BMC Atrium Orchestrator Development Studio

      BMC Atrium Orchestrator content

      Includes all installed content: adapters, modules, and run books
      When you use the content installation program to install a predefined workflow for a BMC solution, the log files are created in <installationFolder>\import-logs.

  3. Search the log files to verify that they contain no SEVERE error messages.


    The BAO_install_log.txt log file contains the following known SEVERE error message. You can disregard this message because it does not cause any issues with the installation.

    * (Windows) The Windows service name is defined on this system ,Detail=AO-CDP
    * (Linux) Could not run command because target file does not exist
  4. Scroll to the end of the file to locate the success message.


    BMC Atrium Orchestrator install succeeded.

    If no error messages were reported, the installation was successful and you can skip the rest of the procedures in this topic.

  5. For all error, (including SEVERE) messages, perform the following procedures:
  6. If a SEVERE error message was reported, additionally perform the steps documented in the Resolving product installation issues on target hosts topic.

To verify that the BMC Atrium Orchestrator services are running

From a BMC Atrium Orchestrator server host:

  • (Windows) Verify that the following services are running:
    • BMC Atrium Orchestrator Access Manager and Repository
    • BMC Atrium Orchestrator Configuration Distribution Peer
  • (Linux) Verify that the following processes are running:
    • amrepo
    • cdp


      # ps -ef | grep amrepo
      # ps -ef | grep cdp

      If either of these processes is not running, you can attempt to start them by using one of the following commands:

      • /opt/bmc/ao-platform/amrepo/bin/server.sh start
      • /opt/bmc/ao-platform/cdp/bin/server.sh start

To verify that BMC Atrium Orchestrator Grid Manager starts

  1. In a web browser, launch Grid Manager by using the following format to type the URL: http://<hostnameOrIpAddress>:<webServerPort>/baocdp
    • <hostnameOrIpAddress> is the IP address or host name used to install the CDP.
    • <webServerPort> is the port value entered during the installation. The default port is 28080.


      To launch the Grid Manager, enter the following URL:

      The Access Manager logon page is displayed.

  2. Log on to Grid Manager.
    You can use the following default credentials to start Grid Manager:



    User name




  3. On the Status tab, verify that Grid CDP1 appears with the green, "Fully Running" status.

    With BMC Cloud Lifecycle Management installer, you can enable ARSAdapter, BladeLogic, and NetAppActor adapters. If you enabled other adapters, they should also appear on the Status tab.

    If any of your enabled adapters do not appear in this list, you can check the following log files for errors:
    • <installationLocation>/ao-platform/cdp/tomcat/logs/catalina.out
    • <installationLocation>/ao-platform/cdp/tomcat/logs/grid.out

To manually configure adapters

If you did not configure adapters as part of the BMC Atrium Orchestrator post-install configuration steps, perform the following steps:

  1. Log into your BMC Atrium Orchestrator installation using the following link:
    The Grid Manager screen is displayed.
  2. Go to Manage > Adapters.
  3. Select the following adapters:
    • bmc-adapter-amazon-ec2-actor
    • bmc-adapter-bmc-server-automation
    • bmc-adapter-netapp-storage-actor
    • ro-adapter-command-line
    • ro-adapter-file
    • ro-adapter-remedy-actor
  4. Click Add to Grid.
    The adapter will now be added to the grid.
  5. Click Configure in the Name column for each of the above adapters.

    Adapter Name

    Parameter and value

    Additional configuration steps

    Remedy Actor

    Name: ARS Adapter
    Target: BMC AR System Server – Cloud Portal and Database host
    UserName: orchestrationuser
    Password: aouser

    Not required.

    BladeLogic Adapter

    Name: BladeLogic Adapter
    Initial command: nsh
    Prompt: %
    Executable directory: C:\Program Files\BMC Software\BladeLogic\NSH\bin
    Script directory: C:\Program Files\BMC Software\BladeLogic\NSH\scripts
    Script executable: nsh
    Jython executable: bljython
    Authentication mechanism: SRP 
    ProfileName: testProfile
    SRP User Name: BLAdmin
    SRP Password: <password specified during BBSA AppServer and Console install for BLAdmin>
    Default User Role: BLAdmins
    Install Certificate: yes
    Install Certificate Prompt: ?[yes|no]:

    To add the profile to the BBSA Appserver, perform the following steps:

    1. On the BMC Atrium Orchestrator host, navigate to the NSH folder.
    2. Run the following command: cd /opt/bmc/bladelogic/8.1/NSH/bin/blcred authprofile -add -profile testProfile -host <BBSA hostname>:10840 -type srp -username BLAdmin -password <BLAdmin password>

    NetApp Actor

    Name: NetApp Adapter
    Target: Enter the target hostname / IPAddress
    Username: <username>
    Passsword: <password>
    Protocol: http
    Port: 8088

    Not required.

  6. Provide the required information as listed in table. 
    For example, enter the information for the ARS Adapter, and then click OK.

    Adapters that you configured appear as blue in the table:

  7. Go to Manage > Peers.
  8. Select the required Peer, for example CDP1 and click Edit selected Peer (Pencil icon) on the right.
  9. Click Enable and select the available adapters.
  10. Select an available adapter from the list (for example, ARS Adapter), click OK, and wait for a few minutes. 
  11. Add all the adapters to the grid. 
  12. Click the Status tab on the top of the screen.Select the GRID link on the top of the table, as shown in the screenshot below.

    For each of the adapters listed in the table a green button should be displayed, indicating that the adapters are running.

Related topic

Verifying the installation

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.