Stopping the Access Manager, CDP, and other BAO services
This page describes how to stop Access Manager, CDP, and other BMC Atrium Orchestrator services, such as the OCP.
Although both the CDP and Access Manager must be running for you to use Grid Manager, you might need to stop the processes. You can use these procedures to stop the Access Manager and CDP processes. The procedures for stopping the CDP and Access Manager depend on the operating system where they are installed.
To stop the CDP, AP, LAP, Access Manager, OCP on a Windows computer
- Select Control Panel > Administrative Tools > Services to open the Services window.
Perform the appropriate action:
To stop the CDP
Right-click the BMC Atrium Orchestrator Configuration Distribution Peer service and select Stop.
To stop an AP
Right-click the BMC Atrium Orchestrator Activity Peer service and select Stop.
To stop an LAP
Right-click the BMC Atrium Orchestrator Lightweight Activity Peer service and select Stop.
To stop Access Manager and the Repository
Right-click the BMC Atrium Orchestrator Access Manager and Repository service and select Stop.
To stop the OCP
Right-click the BMC Atrium Orchestrator Operator Control Panel service and select Stop.
To stop Access Manager on a Linux or UNIX computer
- Open a terminal on the computer.
- Change to the AO_Home/bin directory for the Access Manager installation. Type sh ./server.sh stop
Tomcat displays messages indicating that the server stopped.
To stop the CDP, OCP, AP, or LAP on a Linux or UNIX computer
- Open a terminal on the computer.
- Change to the AO_Home/bin directory for the CDP, OCP, AP, or LAP installation.
- Type sh ./server.sh stop
Tomcat displays messages indicating that the server stopped.
If the OCP is installed in the same location as the CDP, AP, or LAP, when you run the server.sh stop command, the OCP and other component (for example, the CDP) will both be stopped. If you want to stop only one component, use the Tomcat instructions Stop an Existing Application.
Related topic