Launching the installer and pre-analyzing your environment

This topic describes how to launch the installer and pre-analyze your environment to ensure a successful installation. First, the install planner strictly enforces the install and upgrade flow so that you install individual components in a required sequence. Second, it monitors your RSCD/NSH communication while install/upgrade of individual components and inform user accordingly. This will prevent unwanted exceptions or failure during install/upgrade and installation. Third, the install planner provides all related steps and suggestions to the user whenever possible instead of re-directing user to documentation.

This topic contains the following information

Preanalyzing your environment

The Preanalyzer utility provides a proactive way to keep install planner flow smooth during new installations and upgrades. Pre-analyzing your environment consists of a number of checks that are required to install or upgrade successfully the BMC Cloud Lifecycle Management products. For example, the Preanalyzer checks to see if your AR system meets recommended value for CPU and Disk. In case of upgrade, you can analyze your environment without downtime. The Preanalyzer performs the following tasks:

Checks your environment for possible errors.
Automates important pre-checks of your environment.
Generates a "report card" of your environment that provides a high-level overall status of the target servers.
Generates an HTML report that checks your environment and lists recommendations to fix it (for example, correct versions of JREs, operating systems, RPMs, correct AR System license check, host connectivity, and many more).
Integrates all BMC Cloud Lifecycle Management components.
Lets you easily restart the install planner if the install or upgrade fails due to environment or unknown issues.
Upgrades your environments reliably.

Before you begin

Review the product host requirements for your platform. See System-requirements
Log on to the computer as the user provided in the installer and verify the user's profile.
If you do not verify this information, the product installations might not launch properly. For example:
- Windows – If the user is Administrator, the profile must be C:\Users\Administrator.
- Linux – If the user is root, the profile must be /root.
(Windows only) Stop and disable both the IP Helper and Windows HTTP Proxy web service on the target hosts before you start installation. Otherwise, the installations fail.

Note

If you are performing a fresh installation on Microsoft Windows with a remote database, the validation check for remote database fails. The suggestion that is displayed by the installer to fix the failure incorrectly shows the DB host name instead of the AR System host name.

To work around the issue, execute \\AR_server_name from the database server. This enables you to successfully connect to the AR System server.

To launch the installer

Note

Accept the default values in the installer unless you have a good reason to change them.
Do not mix and match IP addresses and host names during product selection in the Host Information panel. Enter all IP addresses or all host names, but do not combine them.
To avoid problems if the VLAN and IP addresses of the hosts are changed, use host names. Any underlying changes to the VLAN or IP addresses are then transparent.
In passwords, some special characters create problems during installation. For more information, see Restricting the use of certain characters in passwords.
- For TrueSight Network Automation (formerly called BMC Network Automation), do not use special characters, except underscore (_). When you create a keystore password, do not use an ampersand (&).
- For TrueSight Server Automation (formerly called BMC Server Automation), do not use #.
- For Platform Manager, CLM Self-Check Monitor, and Cloud Portal Web Application, do not use an ampersand (&) when you create a keystore password.
- With Linux, do not use @.

Download the BMC Cloud Lifecycle Management solution, as instructed in Downloading-the-installation-files.
To start the installer, perform the following steps based on your operating system:
1. (Windows) From the command prompt, go to Planner > Windows > Disk 1.
2. (Linux) From the shell prompt, go to Planner\Linux\Disk1.
  On Linux, launch the installer by using Xmanager to start the ./setup.sh command.
  With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.
Tip
You can also use vConsole or Xming to launch the installer.
Ensure that the current directory is Planner\<operating _system>\Disk1 before you launch the installer.
On the Welcome page, click Next.
Review the license agreement, click I agree to the terms of license agreement, and click Next.
On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the installation.
Select the I have read the prerequisites check box and click Next.
(Optional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product installations.
Note
If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.
On the Directory Selection panel, navigate to the location on the host where you want to install the planner and click Next.
Accept the default value (for example, C:\Program Files\BMC Software\Planner for Windows or /opt/bmc/Planner for Linux) if you do not require a specific location for the installation files.
On the Installation Preview panel, review the information and click Install.
On the NSH panel, review the installation location, and then click Next.
The default location is C:\Program Files\BMC Software\NSH for Windows or /opt/bmc/Planner/NSH for Linux. Otherwise, navigate to the directory where you want to install NSH.
In the Select Installation Type panel, select Install and then click Next.

In the Select Deployment Type panel, select New Deployment and then click Next.
The following options are available:

Installer option	When to choose
New Deployment	This is the first time you are launching the BMC Cloud Lifecycle Management Installer and you have no other existing BMC products installed that you want to add to the BMC Cloud Lifecycle Management solution.
Integrate with an Existing Deployment	You have existing BMC products that you want to add to the BMC Cloud Lifecycle Management solution.
Modify Existing Deployment	You already installed one or more products in the solution. Now you want to add install additional products immediately after completing another product installation. Note: This option only appears on the BMC Cloud Lifecycle Management Installer UI when you launch the installer after completing an installation. Otherwise, the two options that are visible to you are New Deployment and Integrate with an Existing Deployment.

On the Select Deployment Template panel, choose the type of deployment template to implement.
- Small Deployment – For managing up to 10,000 devices (virtual or physical).
- Medium Deployment – For managing up to 25,000 devices (virtual or physical).
  NoteIn version 4.7, only Compact, Small, and Medium deployments are supported.
Click Next.
The Deployment Tier Selection panel appears.

Select the deployment tier based on the products that you want to install first.
You can review the products in the Control and Workload deployment tiers.

Tier name	When to choose
Control Tier	You need to install products that enable you to manage the BMC Cloud Lifecycle Management solution. For more information, see Description of BMC Cloud Lifecycle Management products.
Workload Tier	You need to scale the solution to multiple data center locations, either physical or logical.
Both	You need to install products across tiers. If you want to install all products in the same data center location or geographic location, choose this option.

Click Next.
The Host Information panel appears.
Continue the installation by pre-analyzing your environment.

To pre-analyze your environment

As part of the installation process, the installer runs a utility that pre-checks your environment and generates an HTML report that checks your environment and lists recommendations to fix it.

Review the products in the Control and Workload deployment tiers.
Enter a valid host name for each product that you want to install based on the installation order.
Products that you can install across geographical locations or for high availability (HA) display a plus sign (+) next to them. To add additional products, select Add a Node. You can also delete the host by selecting Delete this node.
Ping the target hosts to make sure that they are valid. You can also enter IP addresses. But do not mix and match host names and IP addresses. Enter one or the other, but not both. To avoid problems if the VLAN and IP addresses of the hosts are changed, use host names. Any underlying changes to the VLAN or IP addresses are then transparent.
Note
You can enter all the target hosts before you start installation. Only required products were selected. If necessary, you can install products in multiple sessions.
Click Next.
The installer validates the target hosts, detects existing RSCD versions, and performs additional verification actions.
Note
The installer returns error messages if you try to install conflicting products on the same computer. The installer also verifies the dependencies of the products and suggests other products to install. For example, you are prompted to install BMC Atrium Orchestrator Server so that you can then install Cloud Platform Manager. If the product that you selected has a dependency, click Previous and install the required product first.
Enter the operating system user names and passwords for each host in your deployment.
To use the same credentials and passwords for each host, select the Apply the same credentials check box. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions.
Note
Deployment is much faster if the installer host and the target host are in the same subnet (about 3 minutes per VM). Otherwise, this step can take quite a long time to complete. Depending on your environment, deploying the RSCD agents can take up to an hour to install per VM if you are installing across the WAN.
Click Next to continue.
The Pre-Analyzer uses the OS credentials to verify the administrator privileges. The installer deploys the BMC BladeLogic Remote System Call Daemon (RSCD) Agent on the target hosts if it does not exist.
Deploying the RSCD Agent and copying the installer files to the target hosts can take an extended period of time to perform.
When the Pre-Analyzer Product Information Panel appears, click each product tab and enter the missing inputs to ensure a successful integration.
For example, enter the database instance, database password, and the other missing inputs for the BMC AR System - Cloud Portal and Database target host. Then continue with Cloud Extensions & Platform Manager, and so on.
Click Next to execute the Pre-Analyzer.
When the Pre-Analyzer Execution Report appears, review the report card of your current installed environment.
The report provides a high-level overall status of the target servers. The following screenshot shows how every product in the target host and the install planner host have failed.
Click the link to view a detailed HTML report of the problems in your environment. For a detailed PreAnalyzer Execution Report, see PreAnalyzer checks.
Note
The HTML report lists both the reasons why your target server failed the pre-analyzer check and the suggested remediations. If one or more of the target servers fail the pre-analyzer check, you must fix the underlying problems before you can continue with the installation.
When all the products on the target server have passed the pre-analyzed check, click Next to continue.
Review the PreAnalyzer Validation panel and then click Next.
The PreAnalyzer phase is finished and you are now ready to start installation.
When the deployment confirmation panel appears, carefully review the summary of the host settings.
Make sure that the products are installed on the correct target hosts.
To change the hosts, click Previous. You cannot modify the configuration after you start the installation.
(Optional) Non-installer step: Track the progress of the installation (for example, verify whether the installation files are copied to the target host) as explained in Tracking installation progress.

Click Next.
The Installation Progress panel appears. The installer stages products into the Currently Installing and Upcoming Installs trees, and automatically selects the correct product to install in its proper order.

Currently Installing

Product does not depend on other products to install, for example, BMC AR System Server - Cloud Portal and Database - Primary.

Upcoming Installs

Product depends on other products being installed first. For example, before you can install Platform Manager - Cloud Portal, you must finish installing BMC Atrium Orchestrator Server. Other possible tasks include configuring Data Execution Prevention (DEP) to run the executable. As a result, products that have an unmet dependency remain in the Upcoming Installs tree until the installation of the product on which they depend is complete.

Tip

You can review the current progress of an installation at any time by selecting the product in the Currently Installing tree. Click View Deployment Status to review previous progress.

Select a product from the Currently Installing tree (for example, BMC AR System Server - Cloud Portal and Database - Primary) and click Next.
Tip
Do not forget to take a snapshot of your VM or back up your database when the installer prompts you.
At the prompts, enter the installation inputs for each product from your planning spreadsheet.
After you have entered the required setup information, the installer runs a validation check of your user inputs and the Installation Preview panel is displayed.
Click Install.
The installer displays the status of the installation after the installation is completed. Resolve any warning messages before you continue.
Click Next to continue installing the remaining products in the solution. Otherwise, click Exit to exit the installer.
After you exit the installer, you can resume installing remaining products at any time. If needed, you can switch installer computers.
Tip
To immediately resume installing other products in the solution after you exit the installer, launch the installer and choose Modify Existing Deployment.
After you complete the installation session, click Done and then review the summary.
Click Next.
Perform one of the following actions:

Action	Steps
Resume installation by modifying the existing deployment	Select Modify Existing Deployment (the default). Click Next to continue installing the remaining products in the solution. After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.
Exit the installation	Select Exit the installation. Click Next if you are finished. Click Done to exit the installer. After you exit the installer, you can resume installing remaining products at any time. To resume installing other products in the solution after you exit the installer, launch the installer and choose Modify Existing Deployment. After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.

Action

Steps

Resume installation by modifying the existing deployment

Select Modify Existing Deployment (the default).
Click Next to continue installing the remaining products in the solution.
After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.

Exit the installation

Select Exit the installation.
Click Next if you are finished.
Click Done to exit the installer.
After you exit the installer, you can resume installing remaining products at any time.
To resume installing other products in the solution after you exit the installer, launch the installer and choose Modify Existing Deployment.
After you complete an installation, create a snapshot of the host computer before continuing with the rest of the installation process.

Where to go from here

Excerpt named HotfixKA46 was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm47.Planning.Component-BMC-product-service-pack-and-patch-levels.WebHome.
Excerpt named HotfixKA4603 was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm47.Planning.Component-BMC-product-service-pack-and-patch-levels.WebHome.
If you encountered any errors during the installation, see troubleshooting installation issues.
If you want to install the products from another computer, see switching installer computers.