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:
- CLM Self-Check Monitor
- BMC Network Automation
- Mid Tier
- Atrium Web Registry
- Cloud Portal and Database
- Platform Manager (OSGi)
- BMC Atrium Orchestrator
- BMC Server Automation and PXE
- Cloud Portal Web Application
Start order
You must start the services in the following order:
- BMC Server Automation and PXE
- BMC Atrium Orchestrator
- Cloud Portal and Database
- Platform Manager (OSGi)
- Atrium Web Registry
- Mid Tier
- BMC Network Automation
- Cloud Portal Web Application
- 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
BMC Cloud Lifecycle Management applications | Script |
---|---|
RSCD Agent (on each VM) |
|
BMC Remedy AR System – Cloud Portal and Database |
|
BMC Server Automation (clm-bsa) |
|
BMC Atrium Orchestrator (clm-bao) |
|
BMC Remedy Mid Tier |
|
Atrium Core Web Registry Components/Atrium Web Services |
|
BMC Network Automation (clm-bna) |
|
BMC Cloud Platform Manager (OSGi) (clm-pm) |
|
Cloud Portal Web Application |
|
CLM Self-Check Monitor |
|
Comments
Log in or register to comment.