Installing Small Deployment Linux for version 4.5

This topic describes how to install Small Deployment from start to finish on eleven VMs that are dedicated to BMC Cloud Lifecycle Management. This installation also includes how to install the new 4.5.00 CLM Self-Check Monitor and CLM Portal Web Application, which are optional Control Tier products.

Note

Do not run the installer on the same VM where you install the products. Use a separate VM. You can recover this VM later, after you finish the cloud installation.

Since there are only slight variations between the various deployment types, you can use these instructions, for example, with Medium deployments. The major differences are additional products you can install on the Workload Tier for High-Availability (HA) environments.

This topic includes the following sections:

Before you begin

Prepare the installer host requirements for Linux.
Prepare the product requirements for Linux hosts.
Remove the RSCD agent and RSCD package from the Linux hosts.
For example:
rpm -e BladeLogic_RSCD_Agent-version.x86_64
rpm -e BladeLogic_RSCD_Agent-8.5.01-218.x86_64
Carefully review the planning spreadsheet so that you can enter accurate values in the installer for each product.
Review the known and corrected installation issues to avoid potential problems during installation.

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 hostnames during product select in the Host Information panel. Enter all IP addresses or all hostnames, but do not combine them.
Some special characters create problems during installation. For more information, see Restricting the use of certain characters in passwords.
- For BMC Network Automation, do not use special characters except an underscore (_). When you create a keystore password, do not use an ampersand (&).
- For 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.

Download the BMC Cloud Lifecycle Management solution, as instructed in Downloading the installation files.
Launch the installer by double-clicking the setup.sh file.
On the Welcome page, click Next.
Review the license agreement, click I agree to the terms of license agreement, and then 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 then 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, review the location on the host where you want to install the planner, and then click Next.
Accept the default value (/opt/bmc/Planner) if you do not require a specific location for the installation files.
On the Installation Preview panel, review the planner information, and then click Install.
On the NSH panel, review the installation location, and then click Next.
The default location is /opt/bmc/NSH. Otherwise, navigate to the directory where you want to install NSH.
On 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. For more information, see Integrating brownfield BMC Remedy AR System applications.
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 Small Deployment.
For more information, see deployment template for other types to implement.
Click Next.
The Deployment Tier Selection panel appears. You can install products in the Control Tier, Workload Tier, or both tiers.
Select Control Tier, and then click Next.
Note

Small Deployment does not require any products on the Workload Tier; therefore, in this session we selected only the Control Tier. You can create another session later if you want to install optional products from the Workload Tier to use in HA environments.
The Host Information for a Small Deployment panel appears for the Control Tier.
Enter the target hosts for products used in a Small Deployment cloud environment.
Ping the target hosts to make sure that they are valid. You can also enter IP addresses. But do not mix-and-match hostnames and IP addresses. Enter one or the other, but not both.
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.
Enter the operating system user credentials and passwords for the target hosts, and then click Next.
You can apply the same credentials for all target hosts, as shown below.
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.
In the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
You can enter a different directory, for example, data1. Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
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.

Click Next to continue the installation.
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 Install	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. 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.

To install BMC AR System Server - Cloud Portal and Database - Primary

Note

Before you begin:

Obtain an AR System license key.
Install 64-bit Oracle JRE 1.7 on the target host and make sure that the target host is using the correct JRE. Do not install Oracle JRE 1.8 or greater!
Review the Oracle database requirements.
1. Make sure that your Oracle instance is started.
2. Make sure that your REDO log is 1GB minimum.
Start the rpcbind service on the product host.

On the Welcome panel, click Next.
The installer copies files to the target host.
On the Alternate Remote Staging Directory panel, enter an alternate directory (for example, data1) if you need additional space to perform the installation, and then click Next.
By default, the alternate directory is /tmp unless you specified otherwise.
Take a VM snapshot of the target host, and then click Next.
Tip

These snapshots are incredibly important if you encounter an error. You can revert to the saved snapshot, fix the problem, and then continue with the installation.

When the installer prompts you to start and stop the rpcbind service, manually perform the instructions in a command line before you continue with installation.

[root@vl-aus-csm-dv02 opt]# service rpcbind stop
Stopping rpcbind:                                          [  OK  ]
[root@vl-aus-csm-dv02 opt]# rpcbind -i
[root@vl-aus-csm-dv02 opt]# service rpcbind status
rpcbind (pid 21452) is running...

In the Language Selection panel, specify the language selection. and then click Next.
The default is English, which significantly speeds up installation. You can also select All Languages, which includes all supported languages – English, German, Spanish, French, Italian, Japanese, Korean, Simplified Chinese, and Portuguese Brazilian.
Select the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc. Make sure that you enter a directory with enough space to perform the installation. For example, you might select /data1 because /opt (the default) does not have enough space.
Enter the 64-bit Oracle JRE 1.7 directory – for example, /usr/java/jre1.7.0_67 – and then click Next.
On the AR System Server Database Platform Information panel, enter the Database Client Home Path (for example, /data1/oracle/product/11.2.0), and then click Next.

Enter the user and database credentials to access the Oracle database that is used with the AR System server.
Open the tnsnames.ora file on the database VM to locate the Oracle Connection Identifier (ORA112DB) and the Oracle SID (ORA112DB).

# tnsnames.ora Network Configuration File: /data1/oracle/product/11.2.0/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
ORA112DB =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = vl-aus-csm-dv02.bmc.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = ORA112DB)
    )
  )

Enter the database host name and database credentials from the tnsnames.ora file, and then click Next.
Review the AR System Server administrator credentials (by default, Demo/no password), and then click Next.
Note

You cannot modify the Administrator Name, Password, and TCP Port values because the database is imported during installation. After installation, you can update these values as needed.
Enter the credentials for the DBMS administrator (for example, system and the password), and then click Next.
Review the AR System Server database file (ARSys), temporary tablespace (ARTMPSPC), and temporary datafile (artmp) for the AR System server database (ARSystem), and then click Next.
Enter the passwords for DSO, Application Server, and Mid Tier administration, and then click Next.
Review the Normalization Engine (9555) and Atrium Plugin (9556) ports, and then click Next.
Review the AR System Server RMI ports, and then click Next.
The Flashboards RMI port is 1099 and the RPC program number is 0. The Email Engine RMI port is 1100 and the RPC program number is 0.
Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next.
Note

To increase performance, the Small Deployment includes a separate Tomcat instance later in the installation series. The Tomcat servlet you are currently installing is part of the BMC AR System Server – Cloud Portal and Database stack. Use it to license the AR System server; you can also use it for troubleshooting. You can disable it later when you finish installing the entire cloud solution.
Review the Tomcat installation directory, and then click Next.
The default is /opt/apache/tomcat6.0. To stay consistent, this example installs Tomcat in /data1/apache/tomcat6.0.
Review the Tomcat configuration parameters, and then click Next.
By default, the Tomcat initial memory pool is 1536, the maximum memory pool is 2048, and the HTTP port is 8080.
Review the products and versions listed in the BMC AR System Server – Cloud Portal and Database Stack, and then click Install.
The installer copies the stack installer files to the target host and starts the installation process.
Review any validation warnings that appear, make any necessary changes to the target host, and then click Next.
Warning

Not all of these warnings are information only. During different installations in the BMC IDD lab environment at various times, changes were made to the JRE path, temp space, system libraries, the Oracle character sets, the Oracle UNICODE settings, the amount of memory on the target host, or the Redo log size, as shown in the following 4.1.00 screenshot. Make sure that you read the installation prerequisites carefully before you start installation!

The following information-only warnings appear in an environment that is properly configured:
Enter a valid AR System server license key and then click Next.
When you are prompted that the AR System server is successfully licensed, click Next.
The installer clean up temporary files on the target host.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with configuring the AR System server post-installation steps.

To configure AR post-installation

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
Enter the AR System Server user inputs (for example, Demo/no password), and then click Next.
The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
Continue with installing the AR System Mid-Tier.

To install the AR System Mid-Tier

In this session, you install a separate instance of the BMC AR System Mid-Tier to improve performance with the Cloud Portal and Database server.

Before you begin, install 64-bit Oracle JRE 1.7 on the target host.
When you are completely finished with this installation session, you can disable the Mid Tier instance running on the BMC AR System Server - Cloud Portal and Database host..

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only AR System Mid-Tier, and then click Next.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
On the Welcome panel, click Next.
The installer copies files to the target host.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
Review the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/ARSystem.
Enter the 64-bit Oracle JRE 1.7 directory detected by the installer – for example, /usr/java/jdk1.7.0_75/jre7 – and then click Next.
In the AR System Server List panel, enter the name of the BMC AR System server, the Mid Tier password that you created previously, and then click Next.
Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next.
Review the Tomcat installation directory, and then click Next.
The default is /opt/apache/tomcat6.0.
Review the Tomcat configuration parameters for initial memory (2048 MB), maximum memory (2048 MB), the HTTP port (8080), and then click Next.
Review the Preference, Home Page, and DVM Server settings, and then click Next.
These settings should all point to the BMC AR System Server - Cloud Portal and Database host.
Preview the products and versions listed, and then click Install.
The installer copies a zip file to the target host, unzips it, and starts the installation.
If you see a recommendation about CPU clock speed on your VM, you can safely ignore it. Click Next to continue with the installation.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Modify Existing Deployment and then click Next to continue with installing the Atrium Core – Web Registry Components.

To install Atrium Core – Web Registry Components

Before you begin, install 64-bit Oracle JRE 1.7 on the target host.

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Atrium Core – Web Registry Components, and then click Next.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host and the BMC AR System Server - Cloud Portal and Database server, and then click Next.
Review the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/Atrium Web Registry.
Enter the information for the BMC AR System Server - Cloud Portal and Database (for example, Demo/no password), and then click Next.
Specify Yes to install the Tomcat servlet that is used with the Atrium Web Services, and then click Next.
Atrium Web Services require their own Tomcat installation. Do not use the Tomcat servlet installed with the Mid Tier or the BMC AR System Server - Cloud Portal and Database stack.
Review the Tomcat details, and then click Next.
For example, review the Tomcat HTTP (8080) and HTTPS (7776) ports, and the the 64-bit Oracle 1.7 JRE path (for example, /usr/java/jdk1.7.0_75/jre/bin).
Review the products and versions listed in the installation preview, and then click Install.
The installer copies the web registry installer files to the target host and starts the installation process.
Review any validation warnings that appear, and then click Next to continue with the installation.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Modify Existing Deployment and then click Next to continue with installing the BMC Server Automation - App Server & Console.

To install BMC Server Automation – App Server & Console

Before you begin installing BMC Server Automation – Application Server & Console:

Install 64-bit Oracle JRE 1.7 on the target host.
Make sure that the Oracle instance is running.
Ensure that port 9700 is available on the host on which you want to install the product. For example, enter the following command to verify is port 9700 is busy:
```
netstat -anp | grep 9700
```

Installing BMC Server Automation – Application Server & Console includes the following components:

BMC Server Automation Application Server (this procedure)
BMC Server Automation Console (BladeLogic content)
BMC Server Automation Post Install Configuration

In this installation example, we are skipping the optional BSA - File Server deployment on another VM. You can install it later, if needed.

Continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only BMC Server Automation - App Server & Console, and then click Next.
On the Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, the App Server & Console would be installed in /data1/bmc/bladelogic.
Take a VM snapshot of the target host, and then click Next.
Select the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/bladeLogic. Make sure that you enter a directory with enough space to perform the installation.
Enter the Oracle instance ID, DBA user, and password for the Oracle database.
BLADE is the default Oracle instance ID on the panel. But you must use the actual Oracle instance ID that is listed in tnsnames.ora, for example, ORA112DB.
If you select Oracle Service, you can also enter Advanced Connection Settings.
Create a bladelogic password, review the Oracle settings, and then click Next.
Create a certificate password to use SSL, and then click Next.
Create a file server for BladeLogic storage, and then click Next.
Enter the maximum JVM heap size for the Application Server, and then click Next.
The default is 6144 MB.
(Optional) Specify the SMTP and SNMP servers, and then click Next.
Review the products and versions listed in the BMC Server Automation Application Server installation preview, and then click Install.
The installer copies the installer files to the target host, installs the database schema, and then installs the application.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
Continue with installing the BMC Server Automation Console.

To install the BMC Server Automation Console (BladeLogic content)

In this step, you are installing the BladeLogic content for the BMC Server Automation Console. Later you install the Atrium Orchestrator content for the BMC Server Automation Console.

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, the BMC Server Automation Console would be installed in /data1/bmc/bladelogic.
Take a VM snapshot of the target host, and then click Next.
Review the products and versions listed in the BMC Server Automation Console installation preview, and then click Install.
The installer copies the installer files to the target host and then installs the console.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
Continue with configuring the BMC Server Automation post-installation.

To configure the BMC Server Automation post-installation

Before you start:

Make sure that the AR System server is started.
If port 9700 is in use, open the /etc/services file and comment out the following lines:
```
board-roar	9700/tcp	#Board M.I.T. Service
board-roar	9700/tcp	#Board M.I.T. Service
```

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
Take a VM snapshot of the target host, and then click Next.
Enter the login and password to connect to the BMC AR System Server - Cloud Portal and Database, and then click Next.
Create the RBACAdmin and BLAdmin passwords, and then click Next.
In the BMC Server Automation User Information panel, create the BLGuest password, and then click Next.
Review the products and versions listed in the post-installation preview, and then click Install.
The installer performs the post-installation configuration to the Operations Manager application server and other related operations.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, the post-installation stage would be configured in /data1/bmc/bladelogic.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Done to exit the installer.
Continue with installing BMC Atrium Orchestrator Access Manager and Repository (AMREPO).

To install Atrium Orchestrator AMREPO

Before you begin installing AMREPO, install 64-bit Oracle JRE 1.7 on the target host.

Note

Installing BMC Atrium Orchestrator includes the following components::

BMC Atrium Orchestrator Access Manager and Repository (this procedure)
BMC Atrium Orchestrator CDP
BMC Cloud Lifecycle Management Content
BMC Server Automation Console (AO content)
Atrium Orchestrator Post Install Configuration

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Atrium Orchestrator – Configuration Distribution Peer, and then click Next.
On the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space. For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
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.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, the post-installation stage would be configured in /data1/bmc/ao-platform/amrepo.
Take a VM snapshot of the target host, and then click Next.
Specify the directory of BMC Atrium Orchestrator, and then click Next.
The default is /opt/bmc/ao-platform/amrepo.
Review the Access Manager HTTP port (9090 by default) and shutdown port (9005 by default), and then click Next.
On the Access Manager Communication Settings panel, review the Web Server Port Number (9090, the same as the HTTP port) and Communications Port (61616), and then click Next.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with installing Atrium Orchestrator CDP.

To install Atrium Orchestrator CDP

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, the post-installation stage would be configured in /data1/bmc/ao-platform/cdp.
Take a VM snapshot of the target host, and then click Next.
Specify the directory of BMC Atrium Orchestrator CDP, and then click Next.
The default is /opt/bmc/ao-platform/cdp.
Review the Access Manager HTTP port (28080 by default) and shutdown port (28005 by default), and then click Next.
Enter the certificate holder password for the CDP peer, review the other settings, and then click Next.
Review the repository communication settings, and then click Next.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with installing Atrium Orchestrator CDP.

To install the Atrium Orchestrator Content

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
Review the directory of Atrium Orchestrator Content, and then click Next.
The default is /opt/bmc/ao-content.
Review the Repository Communication Settings, enter the repository password (by default, admin123), and then click Next.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with configuring the Atrium Orchestrator post-installation.

To install the BMC Server Automation Console on the BAO target host

This procedure installs the BMC Server Automation Console on the BMC Atrium Orchestrator target host.

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
Specify the directory of the BMC BladeLogic Server Automation Console on the BAO target host, and then click Next.
The default is /opt/bmc/bladelogic.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with configuring the Atrium Orchestrator post-installation.

To configure Atrium Orchestrator post-installation

In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
Review the settings to enable the ARS Adapter, and then click Next.
The orchestrationuser user name and password (aouser) are defined by default and you cannot modify them.
Specify the BLAdmin password (used to log on to the BSA Console), review the remaining settings, and then click Next.
The BLAdmins user role and BLAdmin user name are entered by default.
Specify the settings to enable the Net App Adapter, and then click Next.
If you do not need the Net App Adapter or you are not running a Net App server, disable the setting and continue with configuration.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Modify Existing Deployment and then click Next to continue with installing BMC Network Automation.

To install BMC Network Automation

Before you begin installing BMC Network Automation:

Make sure that the Oracle instance is running.
Install 64-bit Oracle JRE 1.7 on the target host.

Continue to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only BMC Network Automation, and then click Next.
On the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space. For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
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.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space. Then, BMC Network Automation would be installed in /data1/bmc/bca-networks.
Take a VM snapshot of the target host, and then click Next.
Specify the directory of the BMC Network Automation data, and then click Next.
The default is /var/bca-networks-data.
Create the OS User Account to the BMC Network Automation server:
1. Enter a user account to the database, for example, bna_user.
  For BMC Network Automation, do not use any special characters except _. Do not use a dash (for example, bna-user).
2. Enter a password and then confirm it.
  For BMC Network Automation, do not use any special characters except _.
3. Enter the name of the Unix group, for example, bna_group.
  For BMC Network Automation, do not use any special characters except _.
4. Click Next.
Specify the web server information, and then click Next.
The default HTTPS port number is 11443 and the default HTTP port is 9595. You can clear the redirect check box, if you do not want to redirect HTTP requests to HTTPS.
Enter the settings for the database administrator:
1. On Linux OS, use Oracle database only.
2. Enter the existing Oracle SID (for example, ORA112DB) from the tnsnames.ora file.
3. Create a new database user account and password (for example, bna_user).
  Warning
  
  Do not use the existing system database user.
4. (Optional) For Advanced Connection Settings, use this field if you are using Oracle RAC. Otherwise, skip this option.
5. Click Next.
Enter the settings for the database administrator to create the database and database user:
1. Enter the DBA user name and password. The installer defaults to the Oracle system administrator.
2. Enter the name of the database datafile with the correct .dbf extension. For example:
  /data1/oracle/product/oradata/ORA112DB/BNA_data.dbf
  Note
  
  Verify that the database file folders exist before you start the installation.
3. Click Next.
Review the information to generate the HTTPS certificate, and then click Next.
The keystore password is typically already defined.
Enter the amount of memory that the software allocates and holds upon startup, and then click Next.
You can also specify additional startup options for the application. The FAQ and Knowledge Base articles might recommend additional startup options to solve issues unique to your environment. For example, if running on a headless server (no graphics card or monitor), you might have to specify -Djava.awt.headless=true for all the features of application to work properly in your environment.
Enter the settings to enable Atrium Orchestrator integration:
1. Enter the user name and password (for example, admin/admin123).
2. Enter the grid name, for example, BNA_GRID.
3. (Optional) Enable continuous compliance for network automation and create a Remedy user name.
  This setting is disabled by default.
4. Create an AO user account, for example, ao_adapter.
5. Create an AO user password.
6. Click Next.
Enter the settings to enable CMDB integration, and then click Next.
Enter the settings to integrate BMC Network Automation with Cloud Lifecycle Management.
Virtual Data Center creation is enabled by default. Do not disable this setting!
1. Enter a CSM user name and password.
2. Click Next.
Specify the directory of BMC Network Automation, and then click Next.
The default is /opt/bmc/bca-networks.
Review the products and versions listed in the installation preview, and then click Install.
Review any validation warnings that appear, fix them if necessary, and then click Next.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
Continue by installing Cloud Database Extensions.

To install Cloud Database Extensions

Before you begin, install 64-bit Oracle JRE 1.7 on the target host.

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Cloud Database Extensions, and then click Next.
In the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
You can enter a different directory, for example, data1. Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory (for example, data1) if you need additional space to perform the installation, and then click Next.
By default, the alternate directory is /tmp unless you specified otherwise.
Take a VM snapshot of the target host, and then click Next.
Select the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/BMCCloudLifecycleManagement. Make sure that you enter a directory with enough space to perform the installation.
Specify the user inputs to the AR System server (for example, Demo and no password), and then click Next.
Review the products and versions listed in the installation preview, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Modify Existing Deployment and then click Next to continue with installing the Platform Manager.

To install Cloud Platform Manager

Note

When you install the Platform Manager with Small or Medium deployments, you have an option to install the Cloud Portal Web Application. By default, the option is No. If you want to deploy the Cloud Portal Web Application on the Platform Manager host, select Yes. The Cloud Portal Web Application will then run on the same default port as the Platform Manager (9443). If you do not want to deploy the Cloud Portal Web Application on the Platform Manager host, select No. The installer then provides a separate node which you can use to install the Cloud Portal Web Application on a separate host.

Note

Optionally, install 64-bit Oracle JRE 1.7 on the target host if you want to use an external JRE. Otherwise, you can use the bundled JRE. This option applies to the CLM Core components, Cloud Portal AR Extensions, Self-Checker Monitor, and Cloud Portal Web Application.
Manually install BMC Server Automation Network Shell (NSH) on the Self-Check Monitor and Platform Manager hosts. Otherwise, the Restart All Components button on the CLM Self Checker Monitor is not enabled. For more information, see Configuring the StackInformation.properties file. To install NSH, you can use the NSH installer bundled with your BMC Cloud Lifecycle Management installer files (and not the directory of your installed BMC Cloud Lifecycle Management solution) in the Applications\BL-NSH directory. For more information about installing NSH, see Installing only the Network Shell (Linux and UNIX) and Installing only the Network Shell (Windows).

Continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Cloud Platform Manager, and then click Next.
On the Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host and the BMC Server Automation host, and then click Next.
Review the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/BMCCloudLifeCycleManagement.
Enter the 64-bit Oracle 1.7 JRE directory (for example, /usr/java/jdk1.7.0_75/jre7), and then click Next.
Or select the Use Bundled JRE option if you have not installed JRE separately.
Enter the BMC AR System Server - Cloud Portal and Database user inputs (for example, Demo/no password), and then click Next.
The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
Review the directory of the Platform Manager configuration files, and then click Next.
The default is /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration.
Review the OSGi host settings , and then click Next.
To deploy the product in HTTP mode, enter http. The pre-populated OSGi Port is 7070.
(Optional) If you want to deploy the Cloud Portal Web Application on the Platform Manager host, select Yes and then click Next.
The default option is No. The installer assumes that you want to install the Cloud Portal Web Application on its own target host (described in To install Cloud Portal Web Application).
(Optional) If you selected Yes, enter the Self-Check Monitor URL (typically, https://<HealthCheckVM>:8443/health) and then click Next.
If you plan to install the Self-Check Monitor and you already know the host name, enter the URL. For example:
https://<selfCheckerHost>:8443/health
If you do not plan to deploy the Self-Check Monitor at this point, proceed with the dummy values that are pre-populated. You can always change the values later in the<CLM_Install_Dir>\Platform_Manager\configuration\preferences\PreferenceGroup.json file.
Note

For Small or Medium deployments, the installer provides a node to install the CLM Self-Check Monitor on a separate host. For more information, see To install CLM Self-Check Monitor.
In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
You can chose to install using the existing self-signed certificate, or you can provide the location of a third-party certificate and password.
Note

You must copy the third-party certificate to the target host.
In the Tomcat Web Server Certificate Information panel, review the keystore information, and then click Next.
Enter a super user password to the login service, and then click Next.
You use this super user password during the Cloud Portal AR Extensions installation.
Review the Persistence Manager details, and then click Next.
Make sure that you set the correct time zone for your AR System server.
Review the core cloud service details, and then click Next.
Enter the Resource Manager details:
1. Enter the BBNA provider password (by default, sysadmin).
2. Enter the BLAdmin password that you created previously.
3. Enter the BLGuest password that you created previously.
4. Enter the Atrium Orchestrator callout provider password (by default, admin123).
5. Click Next.
Review the SMTP Configuration details, and then click Next.
Click No (the default) to disable the on-premise database as a service (DBaaS), and then click Next.
You can still configure DBaaS later after you finish installing Compact Deployment. If you select Yes now, the next panel prompts you for the BMC Database Automation (BDA) Manager host name, user, and password.
(Optional) If you selected Yes in the Configure BDA for BMC Cloud Lifecycle Management panel, enter the BMC Database Automation details, and then click Next.
Click No (the default) to disable the VMware vCloud Director Provider, and then click Next.
You can still configure vCloud later after you finish installing Compact Deployment. If you select Yes now, the next panel prompts you for the vCloud server name, administrator, password, and so on.
(Optional) If you selected Yes in the Configure Vmware vCloud Director Provider for BMC Cloud Lifecycle Management panel, enter a password, review the remaining details, and then click Next.
Review the products and versions listed in the installation preview, and then click Install.
The installer copies the web registry installer files to the target host and starts the installation process.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
If you installed using HTTPS, import the SSL certificates, as described in To import self-signed certificates for new 4.5.x installations.
Otherwise, disregard this step.
Continue by installing Cloud Portal AR Extensions.

To install Cloud Portal AR Extensions

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Cloud Portal AR Extensions, and then click Next.
On the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space. For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
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.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the BMC AR System Server - Cloud Portal and Database target host, and then click Next.
Enter the Oracle JRE 1.7 directory – for example, /usr/java/jre1.7.0_67 – and then click Next.
Or select the Use Bundled JRE option if you have not installed JRE separately.
Review the BMC AR System Server - Cloud Portal and Database user inputs (for example, Demo/no password), and then click Next.
The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
Review the TCP port (9899 by default) for the Java plugin server, and then click Next.
Make sure that the TCP port is unused and unique.
Enter a super user password, and then click Next.
Make sure this password matches the password you created during the Platform Manager installation.
Specify a password for the cloud administrator (clmadmin), and then click Next.
Specify the password for the Atrium Orchestrator CDP host (by default, admin123), and then click Next.
(Optional) In the Cloud Vista cross launch panel, select Yes to enable integration between Cloud Vista and TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server.
By default, the No option is selected in the installer.
Note

Do not select Yes unless you already installed TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server. BMC customers who purchased and manually installed standalone TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server can integrate BPPM as a brownfield product with BMC Cloud Lifecycle Management.
(Optional) If you selected Yes in the Cloud Vista cross launch panel, enter the TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server details, and then click Next.
Review the Platform Manager Host Panel details. and then click Next.
Review the web server URL (for example, http://webserver:8080), and then click Next.
Do not use the Mid Tier URL that is used to access the AR System server (for example, http://webserver:8080/arsys).
Review the products and versions listed in the installation preview, and then click Install.
The installer copies the web registry installer files to the target host and starts the installation process.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the progress of the current session and your overall progress, and then click Next.

This example showed you how to install sixteen BMC Cloud products across multiple VMs.
Click Modify Existing Deployment and then click Next to continue with installing the CLM Self-Check Monitor.

To install CLM Self-Check Monitor

Note

For Small or Medium deployments, the installer provides a node to install the CLM Self-Check Monitor on a separate host.

Before you begin, install 64-bit Oracle JRE 1.7 on the target host.

Continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only CLM Self-Check Monitor, and then click Next.
On the Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
On the NSH panel, review the installation location, and then click Next.
The default location is /opt/bmc/bladelogic/NSH. Otherwise, navigate to the directory where you want to install NSH.
Select the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/SelfChecker. Make sure that you enter a directory with enough space to perform the installation.
Enter the 64-bit Oracle JRE 1.7 directory – for example, /usr/java/jdk1.7.0_75/jre – and then click Next.
Or select the Use Bundled JRE option if you have not installed JRE separately.
Review the HTTPS or HTTP port numbers (the HTTPS default port is 8443) used to start up (8090) and shut down (8007) the Self-Check Monitor server, and then click Next.
In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
You can chose to install using the existing self-signed certificate, or you can provide the location of a third-party certificate and password.
Note

You must copy the third-party certificate to the target host.
In the Tomcat Web Server Certificate Information panel, review the keystore information, and then click Next.
In the Installation Preview panel, review the information, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
The installer constructs the URL to open the Self-Check Monitor, based on the configuration settings you entered. For example:
https://<SelfCheckerServer>:8443/health
Review the installation progress, and then click Next.
In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
If you installed using HTTPS, import the JRE_HOME/lib/security/cacerts file on the Platform Manager into the Self-Check Monitor JRE, as described in To import self-signed certificates for new 4.5.x installations.
Otherwise, disregard this step.
Continue by installing the Cloud Portal Web Application.

To install Cloud Portal Web Application

Note

For Small or Medium deployments, the installer provides a node to install the Cloud Portal Web Application on a separate host.

Before you begin, install 64-bit Oracle JRE 1.7 on the target host.

Start the installer and continue with the installation to the Host Information for a Modify Existing Deployment panel.
Clear all the remaining products, and select only Cloud Portal Web Application, and then click Next.
On the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
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.
In the Welcome panel, click Next to continue.
The installer copies files to the target server, verifies free space, and so on.
On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
For example, you might select a directory such as /data1 if /tmp (the default) does not have enough space.
Take a VM snapshot of the target host, and then click Next.
Select the Remote Destination Directory of the target host, and then click Next.
The default is /opt/bmc/CloudPortalWeb Application. Make sure that you enter a directory with enough space to perform the installation.
Enter the 64-bit Oracle JRE 1.7 directory – for example, /usr/java/jdk1.7.0_75/jre – and then click Next.
Or select the Use Bundled JRE option if you have not installed JRE separately.
Review the HTTPS or HTTP port numbers (the HTTPS default port is 8443) used to start up (9070) and shut down (9005) the Cloud Portal Web Application, and then click Next.
In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
You can chose to install using the existing self-signed certificate, or you can provide the location of a third-party certificate and password.
Note

You must copy the third-party certificate to the target host.
In the Tomcat Web Server Certificate Information panel, review the keystore information, and then click Next.
In the Configuration Inputs panel, review the Platform Manager and Self-Check Monitor details, and then click Next.
The installer constructs the URLs to open the Platform Manager and Self-Check Monitor, based on the configuration settings you entered. For example:
https://PlatformManager:9443/csm
https://SelfCheckerServer:8443/health
If you do not plan to deploy the Self-Check Monitor at this point, proceed with the dummy values that are pre-populated. You can always change the values later in the CLM_Install_Dir\Platform_Manager\configuration\preferences\PreferenceGroup.json file.
In the Installation Preview panel, review the information, and then click Install.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Review the installation progress, and then click Next.
Click Exit the Installation to close the installer and exit the program, and then click Next.
You can also click Modify Existing Deployment if you want to install an additional application, for example, a PXE server on the Workload Tier.
Review the installation summary log, and then click Done to exit the installer.
You have successfully installed the BMC Cloud Lifecycle Management Small Deployment. Copy and save the PlannerProductRegistry.xml registry file to a different location for safekeeping.
If you installed using HTTPS, import the JRE_HOME/lib/security/cacerts file on the Platform Manager into the Cloud Portal Web Application JRE, as described in To import self-signed certificates for new 4.5.x installations.
Otherwise, disregard this step.
To verify that your Cloud Portal Web Application installation was successful, open the following URL in a browser:
https://<CloudPortalWeb Applicationhost>:<port>/clmui
For example (assuming that you used the HTTPS protocol):
https://clm-aus-005289:8443/clmui

Where to go from here

If you installed Platform Manager on SSL with a third-party certificate, import the certificate into the JRE of the Cloud Portal and Database AR System. For more information, see Using CLM applications with third-party Certification Authority certificates.
Apply the following hotfixes after you install or upgrade version 4.5.00:
- 1088– This hotfix provides missing files necessary for using a currency other than USD.
- 00011110 –you have BM TrueSghtapacity Optimization deployed in your environment.
- 000090568 – This hotfix is required when Platform Manager is running on SSL and the Restart All Components option is not available in the CLM Self Checker.
- 000107881 – This hotfix is required for all BMC Cloud Lifecycle Management deployments.
Verify the installation

Installing Small Deployment Linux for version 4.5

Before you begin

To launch the installer

To install BMC AR System Server - Cloud Portal and Database - Primary

To configure AR post-installation

To install the AR System Mid-Tier

To install Atrium Core – Web Registry Components

To install BMC Server Automation – App Server & Console

To install the BMC Server Automation Console (BladeLogic content)

To configure the BMC Server Automation post-installation

To install Atrium Orchestrator AMREPO

To install Atrium Orchestrator CDP

To install the Atrium Orchestrator Content

To install the BMC Server Automation Console on the BAO target host

To configure Atrium Orchestrator post-installation

To install BMC Network Automation

To install Cloud Database Extensions

To install Cloud Platform Manager

To install Cloud Portal AR Extensions

To install CLM Self-Check Monitor

To install Cloud Portal Web Application

Where to go from here

Comments