Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Manually stopping and starting components of Cloud Lifecycle Management

In most environments, use the CLM Self Checker to stop and restart BMC Cloud Lifecycle Management component services, as described in Monitoring BMC Cloud Lifecycle Management health with the CLM Self Checker. However, this approach does not work in HA environments or with older versions of BMC Cloud Lifecycle Management (before 4.5.x).

Note

Verify that all Cloud Lifecycle Management processes are stopped, if you need to shut down the virtual machines.

To ensure that your cloud environment is working properly, you must stop and restart the services in the following order.

Stop order

You must stop the services in the following order:

  1. CLM Self-Check Monitor
  2. BMC Network Automation
  3. Mid Tier
  4. Atrium Web Registry 
  5. Cloud Portal and Database
  6. Platform Manager (OSGi)
  7. BMC Atrium Orchestrator
  8. BMC Server Automation and PXE
  9. Cloud Portal Web Application

Start order

You must start the services in the following order:

  1. BMC Server Automation and PXE
  2. BMC Atrium Orchestrator
  3. Cloud Portal and Database
  4. Platform Manager (OSGi)
  5. Atrium Web Registry
  6. Mid Tier
  7. BMC Network Automation
  8. Cloud Portal Web Application
  9. CLM Self-Check Monitor

Cloud Lifecycle Management application start and stop scripts for Linux

You can start and stop individual BMC Cloud Lifecycle Management applications for Linux with the following scripts. 

Note

For Windows applications, go to Control Panel > Administrative Tools > Services to stop or start services. 
BMC Cloud Lifecycle Management applicationsScript
RSCD Agent (on each VM)
/etc/init.d/rscd start
/etc/init.d/rscd stop
BMC Remedy AR System – Cloud Portal and Database
/opt/bmc/ARSystem/bin/
./arsystem stop
./arsystem start
BMC Server Automation (clm-bsa)
/etc/init.d/blappserv start
/etc/init.d/blappserv stop
BMC Atrium Orchestrator (clm-bao)
/opt/bmc/ao-platform/amrepo/bin/bao.sh
start
/opt/bmc/ao-platform/amrepo/bin/bao.sh
stop
/opt/bmc/ao-platform/cdp/bin/bao.sh
start
/opt/bmc/ao-platform/cdp/bin/bao.sh
stop

BMC Remedy Mid Tier

/opt/apache/tomcat7.0/bin/startup.sh
/opt/apache/tomcat7.0/bin/shutdown.sh
Atrium Core Web Registry Components/Atrium Web Services
/opt/apache/tomcat7.0/bin/startup.sh
/opt/apache/tomcat7.0/bin/shutdown.sh
BMC Network Automation (clm-bna)
/etc/init.d/enatomcat start
/etc/init.d/xinetd restart
BMC Cloud Platform Manager (OSGi) (clm-pm)
/etc/init.d/bmccsm stop
/etc/init.d/bmccsm start
/etc/init.d/BMCQuickStart stop
/etc/init.d/BMCQuickStart start 

Cloud Portal Web Application

/opt/bmc/CloudPortalWebApplication/tomcat/bin/startup.sh
/opt/bmc/CloudPortalWebApplication/tomcat/bin/shutdown.sh

CLM Self-Check Monitor

/opt/bmc/selfchecker/tomcat/bin/startup.sh
/opt/bmc/selfchecker/tomcat/bin/shutdown.sh


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.

Comments