Planning your installation

Before you start installing the BMC Cloud Lifecycle Management solution, you must gather information about the required parameters that the installer prompts for each product. You can then review the installation timing of each product to plan for the installation.

Note

If any of your hosts accidentally crashes after you install a product successfully, you must reinstall the product on the same host or a different host. However, the installer does not allow you to perform such an installation because the registry file contains a successfully installed status for the product. To reinstall the product on the same host or on a different host, contact BMC Customer Support.

The following sections explain how you can plan for the BMC Cloud Lifecycle Management solution installation:

Gathering information for the installation

Use the planning spreadsheet to help prepare input values for the installer. To avoid installation errors, refer to the spreadsheet when you run the installation.

Note

This planning spreadsheet replaces the installation worksheets found in the separate product installation guides.

To plan for your installation using the spreadsheet:

  1. Depending on your environment, download and open the planning spreadsheet:

    CLM version and operating systemSpreadsheet link

    CLM 4.6 for Linux

     CLM 4.6.x Planning Spreadsheet Linux.xlsm

     CLM 4.6 for Windows

     CLM 4.6.x Planning Spreadsheet Windows.xlsm

  2. To prepare for the installer prompts, enter your selections and parameter values in the Value column with the help of your DBA or system administrator.
  3. Launch the BMC Cloud Lifecycle Management installer.
  4. Start installing a product, based on the installation order.
  5. Copy parameter values from the spreadsheet and paste them into the product fields in the installer.

Installation timing

The following table lists the estimated installation timing of all products within the BMC Cloud Lifecycle Management solution. You can use this information for planning your installation of the solution.

Note

The installation timing varies, based on the hardware configuration and system performance of the installer host and the product target hosts.

Product

Installation timing on Microsoft Windows
(hh:mm)

Installation timing on Linux
(hh:mm)

BMC AR System Server - Cloud Portal and Database

01:17

01:10

AR Post Install Configuration00:0600.04

BMC Remedy AR System Mid Tier

00:41

00:15

BMC Atrium Core Web registry

00:40

00:23

BMC Server Automation Application Server00:3400:11
BMC Server Automation Console (BladeLogic)00:2000:10
BMC Server Automation Post Install Configuration00:4700:38

BMC Server Automation – File server

00:02

00:02

BMC Atrium Orchestrator Access Manager and Repository00:2200:11
BMC Atrium Orchestrator CDP00:1500:13
BMC Cloud Lifecycle Management Content00:2000:13
BMC Server Automation Console (AO)00:1900:19
Atrium Orchestrator Post Install Configuration00:0300:03

Cloud Database Extensions

00:38

00:25

BMC Network Automation

00:40

00:20

BMC Network Automation – Device agent

00:07

00:07

Cloud Platform Manager

00:40

00:13

Cloud Extensions and Platform Manager
(Compact Deployment)
01:5102:46

Cloud Portal AR Extensions

00:37

00:55

CLM Self-Check Monitor00:0400:03
Cloud Portal Web Application00:0400:02

PXE server

00:08

00:08

Enabling logs if you run into problems

Note

  • These steps are optional and you should only perform them on an "as needed" basis, because they can slow down the AR System server response time during installations or upgrades.
  • The AR System must be installed before you can perform this procedure.
  1. Log on to the AR System server.
    http://<hostname:<port>/arsys 
  2. Open the AR System Administration Console (select Applications > AR System Administration > AR System Administration Console).
  3. Open the Server Information window (select System > General > Server Information).
  4. Click the Log Files tab. 
  5. Enable the following logs:
    • API Log
    • Escalation Log
    • Filter Log
    • SQL Log
    • Plug-in Log
  6. Click Apply and Save.

Related topics

System requirements
Port mappings

Was this page helpful? Yes No Submitting... Thank you

Comments