Page tree

This page describes how to start Access Manager, CDP, and other BMC Atrium Orchestrator services, such as the OCP.

Both the CDP and Access Manager must be running for you to use Grid Manager. You can set the CDP and Access Manager to start automatically after installation finishes, or you can use these procedures to start them.

The procedures for starting the BAO services depend on the operating system where they are installed.

To start the CDP, Access Manager, OCP, or other services on a Windows computer

  1. Select Control Panel > Administrative Tools > Services to open the Services window.
  2. Perform the appropriate action:

    To start the CDP

    Right-click the BMC Atrium Orchestrator Configuration Distribution Peer service and select Start.

    To start an APRight-click the BMC Atrium Orchestrator Activity Peer service and select Start.
    To start an LAPRight-click the BMC Atrium Orchestrator Lightweight Activity Peer service and select Start.

    To start Access Manager

    Right-click the BMC Atrium Orchestrator Access Manager and Repository service and select Start.

    To start the OCPRight-click the BMC Atrium Orchestrator Operator Control Panel service and select Start.

To start Access Manager on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the AO_Home/bin directory for the Access Manager installation.
  3. Type sh ./server.sh start
    Tomcat displays messages indicating that the server started.

To start the CDP, OCP, AP, or LAP on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the AO_Home/bin directory for the CDP, OCP, AP, or LAP installation.
  3. Type sh ./server.sh start
    Tomcat displays messages indicating that the server started.

    Tip

    If Access Manager, the CDP, or another component does not start properly, consider the following tips:

    • If you see a message saying that the server is not found, ensure that you are in the correct directory.
    • Check the grid.log file for a port conflict. If there is a port conflict, edit the AO_Home/tomcat/conf/server.xml file to change the port to an available port. Then try to restart the service.

If the OCP is installed in the same location as the CDP, AP, or LAP, when you run the server.sh start command, the OCP and other component (for example, the CDP) will both be started. If you want to start only one component, use the Tomcat instructions  Start an Existing Application Open link .

Related topic

Stopping the Access Manager, CDP, and other BAO services

5 Comments

  1. Hi,

    Can you please update the instructions for starting and stopping just the OCP service?

    1. You start and stop the OCP service (as well as services for other BAO components) in almost the same way as the CDP. I've updated the pages to add that information. Thank you for your comment and pointing this out.

  2. Thanks for upadting the windows section of starting and stopping. It becomes really trciky when restarting the OCP service in Linux since the script name is the same for restarting CDP and OCP and sometimes we end up restarting CDP if just OCP is down. Can you update the Linux section also?

    1. Hi Saravanan,

      Thanks for your feedback. I've requested information from the team and will update the page when I have it.

    2.