Installing Small Deployment Windows for version 4.6

This topic describes how to install all the Small Deployment products from start to finish on nine VMs that are dedicated to BMC Cloud Lifecycle Management. 

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

The following video (7:56) lists installation best practices. It also shows you how to run the gpedit and regedit utilities, as well as how to test your network for proper connectivity. 

 https://youtu.be/p99dEjT_YiE

  1. Prepare the installer and product host requirements for Windows
  2. Carefully review the planning spreadsheet so that you can enter accurate values in the installer for each product.
  3. Review the known and corrected installation issues to avoid potential problems during installation.
  4. For BMC Cloud Lifecycle Management version 4.6, if the installed Java version on your computer is earlier than 1.7.0_55, upgrade the Oracle JRE to version Oracle/Zulu JRE 1.8 or later only for AR System Server - Cloud Portal Database, BMC Remedy Mid Tier, and Atrium Web Services. For other components such as Cloud Platform Manager, Cloud Portal AR Extensions, CLM Self-Check Monitor, Cloud Portal Web Application, upgrade the Oracle JRE to version Oracle/Zulu JRE 1.8 if you plan to use a public JRE instead of the bundled JRE option.
  5. 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.

To launch the installer and pre-analyze your environment

As part of the upgrade 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. If one or more products fail the pre-analyzer check, you must fix the underlying problems before you can continue with the upgrade.

  1. Launch the install planner.  
     
  2. Pre-analyze your environment. 

    Note

    The install planner runs a utility that pre-checks your environment and generates an HTML report that checks your environment and lists recommendations to fix it. 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. For a detailed PreAnalyzer Execution Report, see PreAnalyzer checks.

  3. When all the products on the target server have passed the pre-analyzed check, click Next to continue. 
     
  4. When the deployment confirmation panel appears, review the summary of the host settings.
  5. Click Next to continue the installation. 
    The Installation Progress panel appears. The installer stages products into the Currently Installing and Upcoming Installs trees.

    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.

  6. 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 - Primary

The following video (10:02) describes how to install the AR System server used as the foundation of BMC Cloud Lifecycle Management. It also runs through the post-installation configuration. 

 https://youtu.be/-A1Zh0ehb6Y

Note

Before you begin:

  1. On the Welcome panel, click Next
    The installer copies files to the target host.
  2. 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. 
  3. 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. 
  4. Select the Remote Destination Directory of the target host, and then click Next
    The default is C:\Program Files\BMC Software.
  5. Enter the 64-bit JRE directory (for example, C:\Program Files\Java\jre), and then click Next
  6. Enter the AR System Server user and database credentials, and then click Next
  7. 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.
  8. Enter the credentials for the DBMS administrator, and then click Next.
  9. Review the AR System Server database file (ARSys) and log file (ARSysLog) names for the AR System server database (ARSystem), and then click Next
  10. Enter the passwords for DSO, Application Server, and Mid Tier administration, and then click Next
  11. Review the Normalization Engine (9555) and Atrium Plugin (9556) ports, and then click Next.
  12. 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.
  13. 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. 
  14. Review the Tomcat installation directory, and then click Next
    The default is C:\Program Files\Apache Software Foundation\Tomcat6.0
  15. 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.
  16. Review the workspace folder for BMC Remedy Development Studio, and then click Next
    The default is C:\Program Files\BMC Software\Developer Studio.
  17. 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. 
  18. 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. 
  19. Enter a valid AR System server license key and then click Next.
  20. When you are prompted that the AR System server is successfully licensed, click Next.
    The installer cleans up temporary files on the target host.  
  21. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  22. Continue with installing the Enterprise Mid-Tier.

To install the Enterprise Mid-Tier

In this session, you install the 8.1.02 version of the BMC AR System Mid-Tier to replace the 8.1.01 version that is installed as part of the SSI stack. This newer version improves security with the Cloud Portal and Database server. 

  1. On the Welcome panel, click Next
    The installer copies files to the target host.
  2. Take a VM snapshot of the target host, and then click Next
  3. Enter the 64-bit JRE directory– for example, C:\Program Files\Java\jre – and then click Next.
  4. Review the Tomcat configuration parameters for initial memory (1536 MB), maximum memory (2048 MB), the HTTP port (8080), and then click Next
  5. Preview the Mid Tier version listed, and then click Install

    Note

    The Enterprise Mid Tier installation does not affect the other AR System products that are already installed.
  6. If you see a recommendation about CPU clock speed on your VM, you can safely ignore it. Click Next to continue with the installation.  
  7. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  8. Continue with configuring AR post-installation. 

To continue AR System Post Install Configuration

In addition to the regular AR System configuration, you also apply several important hotfixes to the AR System installation. 

Note

Stop and disable both the IP Helper and Proxy web service on the EAR Primary and Secondary host before you execute AR Post Install Configuration. Otherwise, the installation fails.
  1. In the Welcome panel, click Next to continue.
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next.
  3. 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.
  4. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  5. Continue with installing AR System Mid-Tier.

To install the AR System Mid-Tier

The following video (4:00) describes how to install the Mid Tier.  

 https://youtu.be/FYYR15GT1Jg

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

  • Before you begin, review the JRE version as mentioned on the System requirements for Windows page.
  • 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..
  1. On the Welcome panel, click Next
    The installer copies files to the target host.
  2. Take a VM snapshot of the target host, and then click Next
  3. Review the Remote Destination Directory of the target host, and then click Next
    The default is C:\Program Files\BMC Software\ARSystem.
  4. Review the 64-bit JRE directory detected by the installer (for example, C:\Program Files\Java\jre), and then click Next.
  5. 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
  6. Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next.
  7. Review the Tomcat installation directory, and then click Next
    The default is C:\Program Files\Apache Software Foundation\Tomcat7.0.
  8. Review the Tomcat configuration parameters for initial memory (2048 MB), maximum memory (2048 MB), the HTTP port (8080), and then click Next
  9. Review the Preference, Home Page, and Data Visualization settings, and then click Next
    These settings should all point to the same BMC AR System Server - Cloud Portal and Database host.  
  10. 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. 
  11. When the installer prompts you with a warning about CPU clock speed on your VM, click Next to continue with the installation.  
    This warning is general-purpose information and you can safely ignore it.  
  12. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  13. Continue with the BMC Mid-Tier Post Install Configuration.

To continue BMC Mid-Tier Post Install Configuration

This procedure applies several important hotfixes to the Mid Tier installation. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next.
  3.  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.
  4. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  5. Continue with installing the Atrium Core – Web Registry Components.

To install Atrium Core – Web Registry Components

The following video (2:48) describes how to install the Atrium Core – Web Registry Components used with BMC Cloud Lifecycle Management. 

 https://youtu.be/7XS40QonSas

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. Take a VM snapshot of the target host and the BMC AR System Server - Cloud Portal and Database server, and then click Next
  3. Review the Remote Destination Directory of the target host, and then click Next
    The default is C:\Program Files\BMC Software\Atrium Web Registry.
  4. Enter the system user (for example, clmsystemuser) and password for the BMC AR System Server - Cloud Portal and Database, and then click Next
  5. 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.  
  6. Review the Tomcat details, and then click Next
    For example, review the Tomcat HTTP (8080) and HTTPS (7776) ports, and the the 64-bit JRE path.
  7. 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.
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  9. Continue with the Atrium Web Services post-install configuration. 

To continue Atrium Web Services Post Install Configuration 

This procedure applies several important hotfixes to the Atrium Web Services installation. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next.
  3.  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.
  4. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
     
  5. Continue with installing the BMC Server Automation - App Server & Console.

To install BMC Server Automation – App Server & Console

The following video (6:34) describes how to install the BMC Server Automation components. 

 https://youtu.be/C0e5boYrSlY

Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available.

Warning

Do not install the 64-bit JRE on the Windows target host. An external JRE is not required—the JRE is already embedded with the product. Installing an external JRE confuses the installation. Specifically, the database configuration does not work in the post-installation configuration. You will successfully finish the first two installations, but the post-installation configuration will fail.

 

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

This installation example skips the optional BSA - File Server deployment on another VM. You can install it later, if needed.

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 

  2. Take a VM snapshot of the target host, and then click Next.
  3. Select the Remote Destination Directory of the target host, and then click Next
    The default is C:\Program Files\BMC Software\BladeLogic.
  4. Enter the DBA user (sa) and password for the BMC Server Automation database.
  5. Create a bladelogic password, and then click Next.
  6. Create a certificate password to use with HTTPS and SSL (for example, changeit), and then click Next.
  7. Create a file server for BladeLogic storage, and then click Next
  8. Enter the maximum JVM heap size for the Application Server, and then click Next
    The default is 6144 MB.  
  9. (Optional) Specify the SMTP and SNMP servers, and then click Next.
  10. 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. 
  11. In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
  12. Continue with installing the BMC Server Automation Console.

To install the BMC Server Automation Console (BladeLogic content)

Here 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. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next.
  3. 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. 
  4. In the Installation Summary panel, review the installation log, and then click Done to finish the installation.
  5. Continue with configuring the BMC Server Automation post-installation.

To continue BMC Server Automation Post Install Configuration

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.  
  2. Take a VM snapshot of the target host, and then click Next.
  3. Enter the system user (clmsystemuser) and password to connect to the BMC AR System Server - Cloud Portal and Database, and then click Next.
  4. Create the RBACAdmin and BLAdmin passwords, and then click Next.
  5. In the BMC Server Automation User Information panel, create the BLGuest password, and then click Next.
  6. 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. 
  7. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  8. Continue with installing Cloud Database Extensions.

To install Cloud Database Extensions

The following video (1:54) describes how to install the Cloud Database Extensions. 

 https://youtu.be/nTlaXOMI2Dk

  1. In the Welcome panel, click Next to continue.
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next
  3. Review the directory of the database extensions, and then click Next
    The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement.
  4. Enter the system user (clmsystemuser) and password to BMC AR System Server - Cloud Portal and Database, and then click Next.
  5. Review the products and versions listed in the installation preview, and then click Install.
  6. In the Installation Summary panel, review the installation log and then click Done to finish the installation.  
  7. Continue by installing BMC Atrium Orchestrator Access Manager and Repository.

To install Atrium Orchestrator AMREPO

The following video (9:28) describes how to install the BMC Atrium Orchestrator components. 

 https://youtu.be/IogLJiVoBnY

Note

Installing the BMC Atrium Orchestrator includes the following components:

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.

  2. Take a VM snapshot of the target host, and then click Next. 

  3. Specify the directory of BMC Atrium Orchestrator, and then click Next. 
    The default is C:\Program Files\BMC Software\AO-Platform\AMREPO.

  4. Review the Access Manager HTTP port (9090 by default) and shutdown port (9005 by default), and then click Next.

  5. 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.

  6. Review the products and versions listed in the installation preview, and then click Install.

  7. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 

  8. Continue with installing Atrium Orchestrator CDP.

To install Atrium Orchestrator CDP

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next
  3. Review the directory of BMC Atrium Orchestrator CDP, and then click Next
    The default is C:\Program Files\BMC Software\AO-Platform\CDP.
  4. Review the CDP HTTP port (28080 by default) and shutdown port (28005 by default), and then click Next.
  5. Enter the certificate holder password for the CDP peer, review the other settings, and then click Next.
  6. Review the repository communication settings, and then click Next.
  7. Review the products and versions listed in the installation preview, and then click Install.
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  9. Continue with installing BMC Cloud Lifecycle Management Content.

To install the Atrium Orchestrator Content

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next.
  3. Review the directory of BMC Cloud Lifecycle Management Content, and then click Next
    The default is C:\Program Files\BMC Software\AO-Content.
  4. Review the Repository Communication Settings, enter the repository password (by default, admin123), and then click Next.
  5. Review the products and versions listed in the installation preview, and then click Install.
  6. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  7. Continue with installing the BMC Server Automation Console on the BMC Atrium Orchestrator target host.

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. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.  
  2. Take a VM snapshot of the target host, and then click Next
  3. Specify the directory of BMC BladeLogic Server Automation Console, and then click Next
    The default is C:\Program Files\BMC Software\BladeLogic.
  4. Review the products and versions listed in the installation preview, and then click Install.
  5. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  6. Continue with configuring the Atrium Orchestrator post-installation.

To continue Atrium Orchestrator Post Install Configuration

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. (Optional) Even though the installer does not prompt you to take a VM snapshot of the target host, take a snapshot anyway as a safety measure, then click Next
  3. Review the settings to enable the ARS Adapter, and then click Next
    The orchestrationuser user name is defined by default and you cannot modify it.
  4. Specify the BLAdmin SRP password, review the remaining settings, and then click Next
    The BLAdmins user role and BLAdmin user name are entered by default. 
  5. 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.
  6. Review the products and versions listed in the installation preview, and then click Install.
  7. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  8. Continue by installing BMC Network Automation.

To install BMC Network Automation

The following video (7:42) describes how to install BMC Network Automation. 

 https://youtu.be/VarCdRasy_Q

Note

On new Windows installations of BMC Network Automation where BMC now supports MS SQL Server 2014, the installation fails if you do not specify the highest value of the data file path or log file path available. Enter the highest version of the path, for example:

  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_data.mdf (as the data file path)
  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_log.ldf (as the log file path)

Note

If you install BMC Network Automation anywhere other than the C: drive, the path cannot include any spaces. For example:
F:\Program Files\BMC Software\BCA-Networks 
  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the target host, and then click Next
  3. Specify the directory of the BMC Network Automation data, and then click Next
    The default is C:\BCA-Networks-Data.
  4. Specify the OS User Account to the BMC Network Automation server:
    1. Enter a user account to the database, for example, bna_user
      Some characters are not allowed; for example, do not use a dash (bna-user). 
    2. Enter a password and then confirm it.
    3. Enter the name of the Windows computer host. Do not enter an IP address or a FQDN.
    4. Click Next.
  5. 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.
  6. 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), or create a new database user account. 
    3. Click Next
  7. 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\MSSQL11.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\MSSQL11.MSSQLSERVER\MSSQL\DATA\BNA_log.ldf 
    4. Click Next
  8. Enter the information to generate the HTTPS certificate for your organization, and then click Next.
    Update the keystore password as needed. By default, the password is changeit
  9. Review 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.
  10. Enter the settings to enable Atrium Orchestrator integration:
    1. Enter the user name (for example, admin) and password (for example, admin123) .
    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. Click Next.
  11. Enter the password of the system administrator (clmsystemuser) to enable CMDB integration, and then click Next
  12. Enter the settings to integrate BMC Network Automation with Cloud Lifecycle Management, and then click Next
  13. Specify the directory of BMC Network Automation, and then click Next
    The default is C:\Program Files\BMC Software\BCA-Networks.
  14. Review the products and versions listed in the installation preview, and then click Install
  15. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  16. Continue by installing Cloud Platform Manager.

To install Cloud Platform Manager

The following video (9:11) describes how to install the Platform Manager. 

 https://youtu.be/7ZEvPsouOes

Note

When you install the Platform Manager with Small and 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 JRE on the target host if you want to use an external JRE. Otherwise, you should use the bundled JRE. This option applies to the CLM Core components, Cloud Portal AR Extensions, Self-Checker Monitor, and Cloud Portal Web Application. Review the JRE version as mentioned on the System requirements for Windows page.
  • 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).
  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.

  2. Take a VM snapshot of the target host and the BMC Server Automation host, and then click Next. 
  3. At the NSH panel, review the directory settings (by default, C:\Program Files\BMC Software\NSH) and then click Next. 
    NSH is required so that the Platform Manager and the Self-Check Monitor can verify and use network settings. 
  4. Review the Remote Destination Directory of the target host, and then click Next.
    The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement.
  5. Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next
    You can also enter the directory path to an external 64-bit JRE directory – for example, C:\Program Files\Java\jre8
  6. Enter the password of the BMC AR System Server - Cloud Portal and Database system user (clmsystemuser), and then click Next
    The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
  7. Review the directory of the Platform Manager configuration files, and then click Next
    The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration.
  8. Review the OSGi port (9443) and protocol (the default is https), and then click Next
      Page not found for multiexcerpt macro.
    The page: Installing Compact Deployment Windows was not found. Please check/update the page name used in the 'multiexcerpt-include macro.
  9. (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).
  10. (Optional) In the Configuration Inputs panel, review the self-check monitor URL and session timeout, 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.
  11. In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
    The NO option creates a self-signed certificate.

    Note

    If you select YES, you must already have created the keystore and installed the third-party certificate on the target host, and you must provide the location of a third-party certificate and password. For more information, see Using CLM applications with third-party Certification Authority certificates.
  12. In the Tomcat Web Server Certificate Information panel, update the information to create a self-signed certificate for your organization.
    1. In the Common Name (CN) field, enter the FQDN for your host under Common Name (CN).
    2. In the State Name (S) field, enter the full name of the state or province and not its abbreviation (California, not CA).  
    3. (optional) Modify the keystore password. The default keystore password is changeit
    4. Click Next.
  13. 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.
  14. Review the Persistence Manager details, and then click Next.
    Make sure that you set the correct time zone for your AR System server.
  15. Review the core cloud service details, and then click Next.
  16. Enter the Resource Manager details:
    1. Enter the BBNA provider password (by default, sysadmin).
    2. Enter the BLAdmin password. 
    3. Enter the BLGuest password.
    4. Enter the Atrium Orchestrator callout provider password (by default, admin123).
    5. Click Next.
  17. Review the SMTP Configuration details, and then click Next
  18. 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 Small Deployment. If you select Yes now, the next panel prompts you for the BMC Database Automation (BDA) Manager host name, user, and password
  19. (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.
  20. 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 Small Deployment. If you select Yes now, the next panel prompts you for the vCloud server name, administrator, password, and so on.
  21. (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.
  22. 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.
  23. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  24. If you installed using HTTPS and you created self-signed certificates, import the SSL certificates, as described in To import self-signed certificates for new 4.5.x installations.
    Otherwise, disregard this step.  

  25. Continue by installing Cloud Portal AR Extensions.

To install Cloud Portal AR Extensions

The following video (5:07) describes how to install the Cloud Portal AR Extensions. 

 https://youtu.be/0hQTnHj9Ovs

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. Take a VM snapshot of the BMC AR System Server - Cloud Portal and Database target host, and then click Next.
  3. Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next
    You can also enter the directory path to an external 64-bit JRE directory – for example, C:\Program Files\Java\jre8
  4. Enter the password to the system user (clmsystemuser) of the BMC AR System Server - Cloud Portal and Database, and then click Next
    The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
  5. 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. 
  6. Enter a super user password, and then click Next.
    Make sure this password matches the password you created during the Platform Manager installation.
  7. Specify a password for the cloud administrator (clmadmin), and then click Next.
  8. Specify the password for the Atrium Orchestrator CDP host (by default, admin123), and then click Next.
  9. (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.

  10. (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.
  11. Review the Platform Manager Host Panel details. and then click Next.
  12. Specify the web server URL (for example, http://webserver:8080), and then click Next
    Do not use the Mid Tier URL.
  13. 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.

  14. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  15. Continue by installing the optional CLM Self-Check Monitor.  

To install CLM Self-Check Monitor

The following video (5:12) describes how to install the CLM Self-Check Monitor. 

 https://youtu.be/wNuA8gR1TfM

Note

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


  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. Take a VM snapshot of the target host, and then click Next.

  3. 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. 

  4. Select the Remote Destination Directory of the target host, and then click Next
    The default is C:\Program Files\BMC Software\SelfChecker. Make sure that you enter a directory with enough space to perform the installation.

  5. Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next
    You can also enter the directory path to an external 64-bit JRE directory – for example, C:\Program Files\Java\jre8.  
     

  6. 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.

  7. In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
    The NO option creates a self-signed certificate.
     

    Note

    If you select YES, you must already have created the keystore and installed the third-party certificate on the target host, and you must provide the location of a third-party certificate and password. For more information, see Using third-party Certification Authority certificates.
  8. In the Tomcat Web Server Certificate Information panel, update the keystore information for your organization.

    1. In the Common Name (CN) field, enter the FQDN for your host under Common Name (CN).
    2. In the State Name (S) field, enter the full name of the state or province and not its abbreviation (California, not CA). 
    3. Click Next.

  9. In the Installation Preview panel, review the information, and then click Install.

  10. 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>:5443/health

  11. 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 the "To import self-signed certificates for new 4.5 and 4.6 installations" section in Enabling SSL HTTPS on Windows non-CLM applications.
    Otherwise, disregard this step.  

  12. Continue by installing the Cloud Portal Web Application.

To install Cloud Portal Web Application

The following video (6:53) describes how to install the Cloud Portal Web Application. 

 https://youtu.be/NZaqhiv_Xrc

Note

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


  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. Take a VM snapshot of the target host, and then click Next.
  3. Select the Remote Destination Directory of the target host, and then click Next
    C:\Program Files\BMC Software\CloudPortalWeb Application. Make sure that you enter a directory with enough space to perform the installation.   

  4. Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next
    You can also enter the directory path to an external 64-bit JRE directory – for example, C:\Program Files\Java\jre8.  

  5. 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.

  6. In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
    The NO option creates a self-signed certificate.
     

    Note

    If you select YES, you must already have created the keystore and installed the third-party certificate on the target host, and you must provide the location of a third-party certificate and password. For more information, see Using third-party Certification Authority certificates.
  7. In the Tomcat Web Server Certificate Information panel, update the information to create a self-signed certificate for your organization.

    1. In the Common Name (CN) field, enter the FQDN for your host under Common Name (CN).
    2. In the State Name (S) field, enter the full name of the state or province and not its abbreviation (California, not CA). 
    3. Click Next.

  8. In the Configuration Inputs panel, enter the Platform Manager and Self-Check Monitor details, and then click Next
    The installer provides sample URLs to open the Platform Manager and Self-Check Monitor. Use the product hosts in your environment to construct the URLs. 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.  

  9. In the Installation Preview panel, review the information, and then click Install.

  10. In the Installation Summary panel, review the installation log and then click Done to finish the installation.

  11. Review the installation progress, and then click Next
  12. 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. 
  13. 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.

  14. If you installed using HTTPS and you created self-signed certificates, import the JRE_HOME/lib/security/cacerts file on the Platform Manager into the Cloud Portal Web Application JRE, as described in the "To import self-signed certificates for new 4.5 and 4.6 installations" section in Enabling SSL HTTPS on Windows non-CLM applications.
    Otherwise, disregard this step. 

  15. 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

  1. 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.

  2. Apply the following hotfixes after you install or upgrade version 4.6.00:

    • 000110488: This hotfix provides missing files necessary for using a currency other than USD.
    • 000100373: This hotfix is required if you have BMC TrueSight Capacity Optimization deployed in your environment.
    • 000113716: This hotfix is required for BMC Network Automation

  3. Apply the following hotfixes after you install or upgrade version 4.6.03:

    • 000113706: This hotfix is required if MyIT 3.1 is deployed in your environment.

    • 000100716: This hotfix is required if BMC Network Automation 8.7 is deployed in your environment.

    • 000113716: This hotfix is required if BMC Network Automation 8.8 is deployed in your environment.

  4. Verify the installation
Was this page helpful? Yes No Submitting... Thank you

Comments