Installing Compact Deployment

This topic describes how to install Compact Deployment. In the 4.0 release, Compact Deployment replaces the 3.x Proof of Concept deployment. You can install Compact Deployment with only one required computer.

Note

The target VM used in this procedure is a Windows Server 2008 R2 64-bit VM with 16 GB RAM and 100 GB hard disk. Installing Compact Deployment took approximately 7 hours to complete in the BMC IDD lab. You significantly speed up installation if the installer host and the target host are in the same subnet.

Before you begin

Prepare the installer host requirements for your platform:
- Windows
- Linux
Review the product host requirements for your platform:
- Windows
- Linux
Carefully review the planning spreadsheet.

To launch the installer

Note

Accept the default values in the installer unless you have a good reason to change 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 _.
- For BMC Server Automation, do not use #.
- With Linux, the @ character generally causes problems.

Download the BMC Cloud Lifecycle Management solution, as instructed in the Obtaining and dowloading.
Go to Planner > Windows > Disk 1.
Start the installer:
- On Microsoft Windows, double-click the setup.cmd file.
- On Linux, launch the installer by using Xmanager.
  With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.
  Tip
  
  You can also use VConsole to 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, review the location on the host where you want to install the planner, and then click Next.
Accept the default value (C:\Program Files\BMC Software\Planner) if you do not require a specific location for the installation files.
On the Installation Preview panel, review the planner 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. 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. 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. 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 Compact Deployment.
For more information, see Sizing Windows for other types to implement.
Click Next.
The Host Information panel appears, as displayed in the following figure.
Enter the single target host used for Compact Deployment and then click Next.
Make sure that the target host is a valid one.
Enter the operating system user credentials and passwords for the target host.
The installer copies files to the target host, deploys the RSCD Agent on the target host, and performs additional installation actions.
When the deployment confirmation panel appears, review the summary of the host settings.

Click Next to continue the installation.
The Installation Progress panel appears. The installer stages products into the Currently Installing and Upcoming Installs trees.

Currently Installing

Product does not depend on other products to install.

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 BMC AR System Server - Cloud Portal and Database from the Currently Installing tree and click Next.

To install BMC AR System Server – Cloud Portal and Database

Install Oracle JRE 1.7 on the target host before you begin.

Note

Installing BMC AR System Server - Cloud Portal and Database took 1 hour and 21 minutes in the BMC IDD lab.

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 (for example, E:\TEMP, as shown below), and then click Next.
Take a VM snapshot of the target host, back up your database, and then click Next.
These snapshots are important if you encounter an error.
Specify the language selection. and then click Next.
The default is English. 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 C:\Program Files\BMC Software.
Review the Oracle JRE 1.7 64-bit path detected by the installer – for example, C:\Program Files\Java\jre7 – and then click Next.
Review the AR System Server user and database credentials, enter the database instance name, and then click Next.
Enter the AR System Server administrator credentials, and then click Next.
Enter the credentials for the DBMS administrator, and then click Next.
Enter the AR System Server database file (by default ARSys) and log file (by default ARSysLog) information, and then click Next.
Enter the passwords for DSO, Application Server, and Mid Tier administration, and then click Next.
Review the Normalization Engine (by default 9555) and Atrium Plugin (by default 9556) ports, and then click Next.
Review the Flashboard (by default 1099) and Email Engine (by default 1100) RMI ports with their Program Numbers (by default 0), and then click Next.
Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next.
Specify the Tomcat installation directory, and then click Next.
The default is C:\Program Files\Apache Software Foundation\Tomcat6.0.
Specify 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.
Specify the workspace folder for BMC Remedy Development Studio, and then click Next.
The default is C:\Program Files\BMC Software\Developer Studio.
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.
When the installer prompts you with validation warnings, review them, and then click Next.
These warnings are general-purpose information and you can safely ignore them. The installer continues the installation process.
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 cleans 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 System post-installation

Note

Configuring AR System post-installation took about 9 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Review 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 Atrium Core - Web Registry Components.

To install Atrium Core – Web Registry Components

Note

Installing Atrium Core - Web Registry Components took 1 hour and 7 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Review the primary information for AR System Server - Cloud Portal and Database (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 Tomcat ports to use with the Atrium Web Services, and then click Next.
Enter the password for the UDDI registry information (for example, admin), and then click Next.
Review the products and versions listed in the Web Registry Components installation preview, and then click Install.
The installer copies the web registry installer files to the target host and starts the installation process.
When the installation is finished, review the install log and then click Done.
Continue with installing BMC Server Automation - App Server & Console.

To install BMC Server Automation – App Server & Console

In this session, you install BMC Server Automation Application Server, BMC Server Automation Console, and BMC Server Automation Post Install Configuration.

Note

Installing all the BMC Server Automation products took 1 hour and 26 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Select the Remote Destination Directory of the target host, and then click Next.
The default is C:\Program Files\BMC Software\BladeLogic.
Enter the DBA user and password for the BMC Server Automation database.
Enter a BladeLogic password, review the other 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 2048 MB.
(optional) Specify the SMTP and SNMP servers, and then click Next.
Review the products and versions listed in the BMC Server Automation 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

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, back up your database, 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.
Review the DEP message, and then click Next.
Adding the application to DEP is recommended. The installer continues the installation.
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

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, back up your database, and then click Next.
Review the settings that connect the AR System server to the Cloud Portal, 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.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with installing BMC Atrium Access Manager and Repository.

To install BMC Atrium Access Manager and Repository

Note

Installing the BMC Atrium Orchestrator products (BMC Atrium Orchestrator Access Manager and Repository, Atrium Orchestrator CDP, BMC Cloud Lifecycle Management Content, and Atrium Orchestrator Post Install Configuration) took approximately 40 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Specify the directory of BMC Atrium Orchestrator, and then click Next.
The default is C:\Program Files\BMC Software\AO-Platform\AMREPO.
Review the settings for the Access Manager HTTP port (9090 by default) and shutdown port (9005 by default), and then click Next.
Review the Access Manager communication settings, and then click Next.
Review the products and versions listed in the post-installation preview, and then click Install.
Review the DEP message, and then click Next.
Adding the application to DEP is recommended. The installer continues the installation.
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 – Configuration Distribution Peer

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, back up your database, and then click Next.
Specify the directory of BMC Atrium Orchestrator, and then click Next.
The default is C:\Program Files\BMC Software\AO-Platform\CDP.
Review the settings of the CDP 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.
Review the DEP message, and then click Next.
Adding the application to DEP is recommended. The installer continues the installation.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with installing BMC Cloud Lifecycle Management Content.

To install BMC Cloud Lifecycle Management Content

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, back up your database, and then click Next.
Review the directory of BMC Cloud Lifecycle Management Content, and then click Next.
The default is C:\Program Files\BMC Software\AO-Content.
Enter the password for the Repository Communication Settings, and then click Next.
The default repository password for the BCM Atrium Orchestrator Grid Manager is admin123.
Review the products and versions listed in the installation preview, and then click Install.
Review the DEP message, and then click Next.
Adding the application to DEP is recommended. The installer continues the installation.
In the Installation Summary panel, review the installation log and then click Done to finish the installation.
Continue with configuring Atrium Orchestrator post-installation.

To configure Atrium Orchestrator post-installation

In the Welcome panel, click Next to continue.
Specify the settings to enable the ARS Adapter, and then click Next.
The orchestrationuser and password is defined by default; you cannot modify it.
Specify the settings to enable the BladeLogic Adapter, and then click Next.
The BLAdmins role and BLAdmin user name are entered by default. Enter the BLAdmin SRP password.
(optional) Specify the settings to enable the Net App Adapter, and then click Next.
If you do not need the Net App Adapter, 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.
Continue with installing BMC Network Automation.

To install BMC Network Automation

Note

Installing BMC Network Automation took 55 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Specify the directory of the BMC Network Automation data, and then click Next.
The default is C:\BCA-Networks-Data.
Specify the OS User Account to the BMC Network Automation server:
1. Enter a OS user account, 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 Windows computer. Do not enter an IP address or a FQDN.
4. Click Next.
Specify the web server information, and then click Next.
You can clear the redirect check box, if you do not want to redirect HTTP requests to HTTPS.
Enter the database information for the BMC Network Automation server:
1. Click Create New Database and enter a database name, for example, bna. The installer creates a database during the installation.
2. Enter the database user (for example, sa, as shown in this example), or create a new database user account.
3. Click Next.
Enter the settings for the database administrator:
1. Enter the DBA user name and password.
2. Enter the name of the database datafile with the correct .mdf extension. For example:
  C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\BNA_data.mdf
3. Enter the name of the database datafile with the correct .ldf extension. For example:
  C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\BNA_log.ldf
4. Click Next.
Enter information to generate the HTTPS certificate, and then click Next.
Make sure that you created a keystore password.
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 at BMC Customer Support 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.
Specify the required (for example, enter admin as the password) or optional settings for the UDDI registry, and then click Next.
Enter the settings to enable Atrium Orchestrator integration:
1. Enter the user name and password (for example, admin).
2. Enter the grid name, for example, BNA_GRID.
3. (optional) Enable continuous compliance for network automation. 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, and then click Next.
Specify the directory of BMC Network Automation, and then click Next.
The default is C:\BCA-Networks.
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 Cloud Portal Platform Manager AR Extensions.

To install Cloud Extensions & Platform Manager

Note

Installing Cloud Extensions & Platform Manager took 1 hour and 51 minutes in the BMC IDD lab.

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, back up your database, and then click Next.
Specify the directory of the AR extensions, and then click Next.
The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement.
Specify the Oracle JRE 1.7 path (for example, C:\Program Files\Java\jre7), and then click Next.
You can also use the bundled JRE.
Specify the user inputs to the AR System server (for example, Demo and no password), and then click Next.
Specify an unused TCP port (9899 by default) for the Java plugin server, and then click Next.
Specify a password for the cloud administrator (clmadmin), and then click Next.
(optional) In the Cloud Vista cross launch panel, select Yes to enable integration between Cloud Vista and BMC ProactiveNet Central Server.
By default, the No option is selected in the installer.
Note

Do not select Yes unless you already installed BMC ProactiveNet Central Server. BMC customers who purchased and manually installed standalone BMC ProactiveNet Central Server can integrate BPPM as a brownfield product with BMC Cloud Lifecycle Management.
Specify the directory of the Platform Manager configuration files, and then click Next.
The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration.
Specify the OSGi port (7070) and protocol, and then click Next.
Click Next to accept the Platform Manager host.
You cannot modify these settings.
Review the web server URL (for example, http://webserver:8080), and then click Next.
Do not enter the full Mid Tier URL.
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.
Specify the correct database timezone under Persistence Manager details, and then click Next.
Review the core cloud service details, and then click Next.
Enter the Resource Manager details:
1. Enter the BBNA provider password.
2. Enter the BLAdmin password.
3. Enter the BLGuest password.
4. Enter the Atrium Orchestrator callout provider password (by default, admin123).
5. Click Next.
Enter Service Health 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.
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.
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 Compact Deployment installation summary 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.
Click Done to exit the installer.

You have successfully installed the BMC Cloud Lifecycle Management Compact Deployment.