Optimizing installation time by installing products without checking dependencies

You can quickly install the entire BMC Cloud Lifecycle Managment stack by skipping the default product dependencies during installation.

To do this, you must use the setup.cmd –J release_dependencies=true (Windows) or setup.sh –J release_dependencies=true (Linux) flag when you launch the installer. The installer no longer checks any product dependencies during installation. You now can manually promote the appropriate product nodes and execute the installs. As a result, you can execute specific product installations in parallel instead of waiting for one product to finish before you launch another install. You can finish more product installations in less time and so decrease the overall deployment time.

This topic contains the following information:

Internal and external product dependencies typically used during installation

The following chart lists the internal and external product dependencies typically used during installation. For example, installing BMC Network Automation depends on finishing installations of Cloud Portal and Database - Primary, Cloud Portal and Database – Primary Post Configuration, and Atrium Core – Web Registry Components. Skipping the dependency check allows you to install products in any order. As a result, carefully follow the steps described in To install products in the proper sequence when you do not check dependencies so that you do not corrupt or crash the installation. 

This chart uses the following abbreviations:

• EAR = BMC AR System Server – Cloud Portal and Database - Primary
• AR Post = BMC AR System Server – Cloud Portal and Database – Primary Post Configuration
• AtriumWS = Atrium Core – Web Registry Components
• BSA FS = BMC Server Automation - File Server
• BSA AppSvr = BMC Server Automation - Application Server & Console
• BSA Post – BMC Server Automation - Application Server Post configuration
• AMREPO = Atrium Orchestrator - Access Manager and Repository
• CDP = Atrium Orchestrator - Configuration Distribution Peer
• Content = CLM Content
• BAO Post = BMC Atrium Orchestrator Post Configuration
• BNA = BMC Network Automation
• Cloud Extensions = Cloud Database Extensions
• Platform Mgr = Cloud Platform Manager
• Cloud Portal = Cloud Portal AR Extensions
• BNA DA = BMC Network Automation Device Agent
• BBAR = BMC Bladelogic Advanced Repeater
• PXE = PXE Server

Before you begin

• Make sure that you meet all the prerequisites for a fresh installation before you start.
• Do not run Cloud Database Extensions and Atrium Web Services in parallel, because both product point to the same AR System server. If the Cloud Database Extensions installation is in progress, the Atrium Web Services installation finds the AR System server busy and likely will fail.

To install products in the proper sequence when you do not check dependencies

1. Launch the installer.
   1. On Windows, enter setup.cmd –J release_dependencies=true.
   2. On Linux, enter setup.sh –J release_dependencies=true.
2. When you are prompted that the installer is launched with the release dependencies set to true, click Next to continue. 
    
3. Install the BMC Cloud Lifecycle Management installer on the installer host.
4. Install NSH on the installer host
5. Select New Deployment and then select the Small Deployment type.
6. Select both the Control and Workload tiers.

7. Enter the target hosts for products used in a Small Deployment cloud environment.

   Workload tier component installs are optional.
8. Install RSCD agents on all the hosts.
9. Install the Cloud Portal and Database – Primary, BMC Network Automation Device Agent, and BMC Bladelogic Advanced Repeater products in parallel.
   Because product dependencies are not being checked, the Currently Installing tree lists these three products as being concurrently installed.
   1. Enter the user inputs in the Cloud Portal and Database – Primary installation and finish the installation.
   2. Enter the user inputs in the BMC Network Automation Device Agent installation and finish the installation.
   3. Enter the user inputs in the BMC Bladelogic Advanced Repeater and finish the installation.
10. Manually promote the AR System Mid-Tier, BMC Server Automation - File Server, BMC Server Automation - Application Server & Console, and Atrium Orchestrator - Access Manager and Repository nodes from Upcoming Installs to Currently Installing.
    You now can install these products in parallel.
    1. Enter the Cloud Portal and Database – Primary host name when the AR System Mid-Tier installation prompts you.
       Even though Cloud Portal and Database – Primary is being concurrently installed, the Mid Tier installation will not check the dependencies and allows the installation to continue.
    2. After BMC Server Automation - Application Server is finished, immediately start installing BMC Server Automation Console.
    3. After Atrium Orchestrator - Access Manager and Repository is finished, immediately start and finish the following installations: 
       • Atrium Orchestrator - Configuration Distribution Peer installation.
       • CLM Content
       • BMC Server Automation Console.
11. After BMC AR System Server – Cloud Portal and Database - Primary is finished, immediately start the BMC AR System Server – Cloud Portal and Database – Primary Post Configuration.
12. After BMC AR System Server – Cloud Portal and Database – Primary Post Configuration is finished, start and finish the following installations:
    • Atrium Core – Web Registry Components
    • BMC Server Automation Post Install Configuration
    • Atrium Orchestrator Post Install Configuration
13. (optional) After BMC Server Automation Post Install Configuration is finished, install the PXE server.
14. After Atrium Core – Web Registry Components is finished, install Cloud Database Extensions and BMC Network Automation.
15. After the Cloud Database Extensions are finished, start Platform Manager.
16. After Platform Manager is finished, start Cloud Portal AR Extensions