Starting and stopping product components and services

Sometimes you might need to start or stop any of the  Platform components and services. The following procedures detail how to start and stop services:

In these instructions, AO_HOME represents the installation directory for the  component, such as the CDP, HA-CDP, AP, LAP, OCP, repository, or dashboards.

Note

If you are using an external Remedy Single Sign-On (Remedy SSO or RSSO) service for authentication, ensure that the Remedy SSO service is running before starting .

Starting and stopping the repository

Use these instructions to start and stop the repository. If you are using the embedded Remedy Single Sign-On, when you start and stop the repository, you start and stop the Remedy SSO version installed with the repository.

Starting the repository

You can set the repository to start automatically after installation finishes, or you can use the procedure appropriate for the operating system where the repository is installed to start it.

To start the repository on a Windows computer

  1. Select Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Repository service and select Start.

To start the repository on a Linux or UNIX computer

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

Stopping the repository

Sometimes, you might need to stop the processes for maintenance or any other purposes. You can use the procedure appropriate for the operating system where the repository is installed to stop the repository processes.

To stop the repository on a Windows computer

  1. Select Settings > Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Repository service and select Stop.

To stop the repository on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the AO_Home/bin directory for the CDP installation.
  3. Type sh AO_HOME/bin/server.sh stop 
    Tomcat displays messages indicating that the server stopped.

Starting and stopping the CDP, AP, or LAP

Use these instructions to start and stop the CDP, AP, or LAP.

 If you are using the embedded Remedy Single Sign-On, when you start and stop the CDP, you start and stop the Remedy SSO version installed with the CDP.

Starting the CDP, AP, or LAP

The configuration distribution peer (CDP) must be running for you to use Grid Manager. You can set the CDP to start automatically after installation finishes, or you can use the procedure appropriate for the operating system where the CDP is installed to start it. You use the same approach to start APs and LAPs.

To start the CDP on a Windows computer

  1. Select Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the appropriate service (in the following list) and select Start.
    • CDP service: BMC Atrium Orchestrator Configuration Distribution Peer
    • AP service: BMC Atrium Orchestrator Activity Peer
    • LAP service: BMC Atrium Orchestrator Lightweight Activity Peer

To start the CDP, 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, AP, or LAP installation.
  3. Type sh AO_HOME/bin/server.sh start
    Tomcat displays messages indicating that the server started.

    Tips

    If the CDP, AP, or LAP 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.

Stopping the CDP, AP, or LAP

Although the CDP must be running for you to use Grid Manager, you might need to stop the processes. You can use the procedure appropriate for the operating system where the CDP is installed to stop the CDP processes. You use the same approach to start APs and LAPs.

To stop the CDP, AP, or LAP on a Windows computer

  1. Select Settings > Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click  appropriate service (in the following list) and select Stop.
    • CDP service: BMC Atrium Orchestrator Configuration Distribution Peer
    • AP service: BMC Atrium Orchestrator Activity Peer
    • LAP service: BMC Atrium Orchestrator Lightweight Activity Peer

To stop the CDP, 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 installation.
  3. Type sh AO_HOME/bin/server.sh stop
    Tomcat displays messages indicating that the server stopped.

Starting and stopping the OCP

Use these instructions to start and stop the OCP.

Starting the OCP

Use the procedure appropriate for the operating system where the OCP is installed to start the OCP.

To start the OCP on a Windows computer

  1. Select Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Operator Control Panel service and select Start.

To start the OCP on a Linux or UNIX computer

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

Stopping the OCP

Use the procedure appropriate for the operating system where the OCP is installed to stop the OCP.

To stop the OCP on a Windows computer

  1. Select Settings > Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Operator Control Panel  service and select Stop.

To stop the OCP on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the AO_Home/bin directory for the OCP installation.
  3. Type sh AO_HOME/bin/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 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 .

Similarly, 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 .

Starting and stopping the dashboards

Use these instructions to start and stop the dashboards.

Starting the dashboards

Use the procedure appropriate for the operating system where the dashboards are installed to start them.

To start the dashboards on a Windows computer

  1. Select Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Dashboard Server service and select Start.

To start the dashboards  on a Linux or UNIX computer

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

Stopping the dashboards

Use the procedure appropriate for the operating system where the dashboards are installed to stop them.

To stop the dashboards on a Windows computer

  1. Select Settings > Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the BMC Atrium Orchestrator Dashboard Server service and select Stop.

To stop the dashboards on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the AO_Home/bin directory for the dashboard installation.
  3. Type sh AO_HOME/bin/server.sh stop
    Tomcat displays messages indicating that the server stopped.

Starting and stopping Remedy Single Sign-On

The way that you start and stop Remedy Single Sign-On depends on the type of Remedy SSO instance you are using.

Starting and stopping an embedded Remedy SSO instance

If you installed the embedded version of Remedy SSO with the  components, starting and stopping the server for the associated component (repository, CDP, or HA-CDP) also stops the embedded Remedy SSO. Use the instructions on this page to start and stop those components.

Starting and stopping an external Remedy SSO instance

To start Remedy Single Sign-On on a Windows computer

  1. Select Settings > Control Panel > Administrative Tools > Services to open the Services window.
  2. Right-click the <Remedy_SSO Tomcat> service and select Start (replace <Remedy_SSO Tomcat> with the name of the Remedy SSO Tomcat service).

To start Remedy Single Sign-On on a Linux or UNIX computer

  1. Open a terminal on the computer.
  2. Change to the RSSO_Home/bin directory for the Remedy Single Sign-On installation (RSSO_Home represents the Remedy SSO installation directory).
  3. Type RSSO_HOME/bin/startup-tomcat.sh 
    Tomcat displays messages indicating that Remedy Single Sign-On started.

Starting and stopping the Cassandra database

Use the procedure appropriate for the operating system where the dashboards are installed to stop them.

To start the Cassandra database on Windows

  1. Go to command prompt and run the following command:

    powershell Set-ExecutionPolicy Unrestricted
  2. Go to AO_HOME/cassandra/bin file.
  3. (Windows) Run the cassandra.bat file.
    (Linux) Run the cassandra file. Cassandra database is started.

    If the job data is not displayed even after restarting the cassandra database, verify if the installation path as specified while installing the CDP contains any spaces. Run the following command to restart the cassandra database.

    <AO_HOME/cassandra/bin> cassandra.bat legacy

To stop the Cassandra database on Windows

Before stopping the Cassandra database, you must ensure that the process ID in the pid.txt file for Cassandra matches the process ID for the java process running from the CDP installation directory.

  1. On the server where the CDP is running, go to the Task Manager and locate the java process.
  2. Copy the java process ID and then go to <AO_HOME>\BAO\CDP\cassandra and open the pid.txt file.
  3. If the process ID in the pid.txt file does not match the java process ID, change the process ID to match the java process ID.
  4. From the command prompt, run the following command to stop the Cassandra database:

    <AO_HOME/cassandra/bin>stop-server.bat -p ..\pid.txt -f
Was this page helpful? Yes No Submitting... Thank you

Comments