Stopping and starting components of Cloud Lifecycle Management

This topic details the recommended order for stopping or starting virtual machines running Cloud Lifecycle Management components.

You must power off or power on the virtual machines in the following order.

One AR System server

Use the following stop and start order if you use the 4.0 single AR System architecture. 

Stop order

You must power off the virtual machines in the following order:

1. BMC Network Automation
2. Mid Tier
3. Atrium Web Registry
4. (if integrated) BMC Database Automation and/or BMC Capacity Optimization 
5. Cloud Portal and Database
6. Platform Manager (OSGi)
7. BMC Atrium Orchestrator
8. BMC Server Automation and PXE

Start order

You must power on the virtual machines in the following order:

1. BMC Server Automation and PXE
2. BMC Atrium Orchestrator
3. Platform Manager (OSGi)
4. Cloud Portal and Database
5. (if integrated) BMC Database Automation and/or BMC Capacity Optimization 
6. Atrium Web Registry
7. Mid Tier
8. BMC Network Automation

Two AR System servers

Use the following stop and start order if you still use the 2.1.x and 3.x Enterprise-AR and Cloud-AR architecture. 

Stop order

You must power off the virtual machines in the following order:

1. BMC Network Automation
2. Mid Tier
3. Atrium Web Registry 
4. (if integrated) BMC Database Automation and/or BMC Capacity Optimization 
5. Enterprise-AR 
6. Platform Manager (OSGi)
7. Cloud-AR
8. BMC Atrium Orchestrator
9. BMC Server Automation and PXE

Start order

You must power on the virtual machines in the following order:

1. BMC Server Automation and PXE
2. BMC Atrium Orchestrator
3. Cloud-AR 
4. Platform Manager (OSGi)
5. Enterprise-AR 
6. (if integrated) BMC Database Automation and/or BMC Capacity Optimization 
7. Atrium Web Registry
8. Mid Tier
9. BMC Network Automation