Installing Compact Deployment Windows for version 4.6

This topic describes how to install Compact Deployment. You can install Compact Deployment with only one required computer.  

Before you begin

1. Prepare the installer and product host requirements for Windows. For more information, see System requirements for Windows.
2. Carefully review the planning spreadsheet.
3. 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

1. On the Welcome panel, click Next. 
   The installer copies files to the target host.
   
2. If the Alternate Remote Staging Directory panel appears, enter an alternate directory if you need additional space to perform the installation (for example, E:\TEMP), and then click Next.  
3. 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.  
4. 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. 
5. Select the Remote Destination Directory of the target host, and then click Next. 
   The default is C:\Program Files\BMC Software. 
6. Review the 64-bit JRE path detected by the installer (for example, C:\Program Files\Java\jre8), and then click Next. 
7. Review the AR System Server user and database credentials, enter the database instance name (for example, the host name), and then click Next. 
   
   

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

   
   

9. Enter the credentials for the DBMS administrator (for example, sa/password), and then click Next.
10. Enter the AR System Server database name (by default, ARSystem), database file (by default, ARSys), and log file (by default, ARSysLog) information, and then click Next. 
11. Enter the passwords for DSO, Application Server, and Mid Tier administration, and then click Next. 
12. Review the Normalization Engine (by default 9555) and Atrium Plugin (by default 9556) ports, and then click Next. 
13. Review the Flashboard (by default 1099) and Email Engine (by default 1100) RMI ports with their RPC program numbers (by default 0), and then click Next. 
14. Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next. 

15. Specify the Tomcat installation directory, and then click Next. 
    The default is C:\Program Files\Apache Software Foundation\Tomcat6.0. 

    Note

    If you change the directory, do not use non-ASCII characters. This is a Tomcat limitation.  
16. 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.
17. Specify the workspace folder for BMC Remedy Development Studio, and then click Next. 
    The default is C:\Program Files\BMC Software\Developer Studio.
18. 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.
     
19. 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.   
20. Enter a valid AR System server license key, and then click Next. 
    For more information, see License keys and requirements for AR System servers.
21. When you are prompted that the AR System server is successfully licensed, click Next.
    The installer cleans up temporary files on the target host.  
22. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
23. Continue with configuring the AR System server post-installation steps. 

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\jre8 – 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

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, back up your database, and then click Next.
3. 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.
4. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
5. (optional) Log on to the AR System server to verify that it is running. 
   For example:
   http://<midTier>:<port>/arsys
   http://vw-sjc-lab:8080/arsys 
6. Continue with installing Atrium Core - Web Registry Components.

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

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

4. Review the Tomcat ports to use with the Atrium Web Services, enter the path to the 64-bit JRE, and then click Next.
5. 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.
6. When the installation is finished, review the install log and then click Done.
7. 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. 

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, back up your database, and then click Next.
   The installer looks up the remote GUID for BMC Server Automation. 
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 password for the BMC Server Automation database, and then click Next.
5. Enter and confirm the DBA user and password for the BMC Server Automation database.
6. Create a BladeLogic user password, review the other settings, and then click Next.
7. Create a certificate password to use SSL, and then click Next.
8. Create a file server for BladeLogic storage, and then click Next.
9. Enter the maximum JVM heap size for the Application Server, and then click Next. 
   The default is 6144 MB.  
10. (Optional) Specify the SMTP and SNMP servers, and then click Next.
11. 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.  
12. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
    
13. Continue with installing the BMC Server Automation Console.

To install 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, back up your database, 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, back up your database, and then click Next.

   Note

   If the BladeLogic client or any NSH scripts are running, stop them before you start the installation to prevent locked-file failures. 
3. For version 4.6 and later, enter and confirm the password of the special clmsystemuser that you created during AR System post-install configuration, 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 BMC Atrium Single Sign-On.

To install BMC Atrium Orchestrator Access Manager and Repository

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, back up your database, 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 settings for the Access Manager HTTP port (9090 by default) and Shutdown port (9005 by default), and then click Next.
5. Review the Access Manager communication settings, and then click Next.
6. Review the products and versions listed in the post-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 – Configuration Distribution Peer

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, back up your database, 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\CDP.
4. Review the settings of the CDP HTTP port (28080 by default), and then click Next.
5. Enter the SSO password for the primary CDP peer, review the other settings, and then click Next. 
   Make sure that the host uses a FQDN.
6. (Optional) To create a secondary CDP peer for HA environments:
   1. Click Secondary CDP.
   2. Enter the FQDN of the secondary host.
   3. Click Next.
       
7. Click Advanced Options, enter a FQDN for the CDP host, and then click Next.
8. Review the products and versions listed in the installation preview, and then click Install.
9. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
10. Continue with installing BMC Cloud Lifecycle Management Content.

To install BMC Cloud Lifecycle Management 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, back up your database, 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 for the Repository User (AoAdmin), and then click Next. 
   The default repository password for the BMC Atrium Orchestrator Grid Manager  is admin123.
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 configuring Atrium Orchestrator post-installation.

To continue Atrium Orchestrator Post Install Configuration

1. In the Welcome panel, click Next to continue.
2. Specify the settings to enable the ARS Adapter, and then click Next.
   The orchestrationuser and password are defined by default; you cannot modify them.
3. 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.
4. (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.
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 BMC Network Automation.

To install BMC Network Automation

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, back up your database, 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 OS user account, for example, bna_user.
      For BMC Network Automation, do not use any special characters except an underscore (_). 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 an underscore (_).
   3. Enter the name of the Windows computer. Do not enter an IP address or a FQDN. 
   4. Click Next.
5. Specify the web server information, and then click Next. 
   If you do not want to redirect HTTP requests to HTTPS, clear the redirect check box.
   
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. (Optional) Enter additional database URL options. 
   4. 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. Modify the information to generate the HTTPS certificate for your organization, and then click Next.
   The keystore password is defined, by default, as changeit. 
   
9. 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.
    
10. Enter the settings to enable Atrium Orchestrator integration:
    
    1. Enter the user name and password (by default, 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. Create an AO user password. 
    6. Click Next.
       
11. Enter the settings to enable CMDB integration (clmsystemuser and password), and then click Next. 
    
12. Enter the settings to integrate BMC Network Automation with Cloud Lifecycle Management, and then click Next. 
    You create a csm user name, and then you create and confirm the password. 
    
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 with installing Cloud Extensions & Platform Manager.

To install Cloud Extensions and Platform Manager

1. In the Welcome panel, click Next to continue. 
   The installer copies files to the target server, verifies free space, and so on.
2. If the Alternate Remote Staging Directory panel is displayed, enter an alternate directory if you need additional space to perform the installation, and then click Next.
   For example, select E:\TEMP if C:\Windows\TEMP (the default) does not have enough space. 
3. Take a VM snapshot of the target host, back up your database, and then click Next. 
4. Specify the directory of the AR extensions, and then click Next. 
   The default is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement.
5. Select the bundled JRE for easier configuration with SSL and HTTPS, and then click Next.
   You can also enter the 64-bit JRE path (for example, C:\Program Files\Java\jre8).
6. Specify the user inputs to the AR System server (for example, clmsystemuser and password), and then click Next.
7. Specify an unused TCP port (9899 by default) for the Java plugin server, and then click Next. 
8. Specify a password for the cloud administrator (clmadmin), 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. 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. 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. 

12. Specify the OSGi port (9443) and protocol (the 4.6.00 default is https), and then click Next. 

    To deploy the product in HTTP mode, enter http. The pre-populated OSGi Port is 7070. 
13. 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.

14. In the Custom CA Certificate Configuration panel, review the information, 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 have already installed the third-party certificate on the target host.
15. In the Tomcat Web Server Certificate Information panel, modify the information information for your organization, and then click Next.
16. Click Next to accept the Platform Manager host. 
    You cannot modify these settings.
17. Review the web server URL (for example, http://webserver:8080), and then click Next. 
    Do not enter the full Mid Tier URL.
18. 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.
19. Specify the correct database timezone under Persistence Manager details, and then click Next. 
20. Review the core cloud services details, and then click Next. 
21. Enter the Resource Manager details:
    
    1. Enter the BBNA provider password (sysadmin, by default).
    2. Enter the BLAdmin password. 
    3. Enter the BLGuest password.
    4. Enter the Atrium Orchestrator callout provider password (by default, admin123).
    5. Click Next.
22. Review the SMTP Configuration details, and then click Next.
23. 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.
24. If you selected Yes in the Configure BDA for BMC Cloud Lifecycle Management panel, enter the BMC Database Automation details, and then click Next.
25. Click No (the default) to disable the VMware vCloud Director Provider, and then click Next. 
    You can still configure vCloud later after you finish the Compact Deployment installation. If you select Yes now, the next panel prompts you for the vCloud server name, administrator, password, and so on.
26. 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.
27. Review the products and versions listed in the installation preview, and then click Install.
28. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
29. Review the Compact Deployment installation summary and then click Next.
    
30. Review the installation log, and then click Done to exit the installer.
    You have successfully installed the BMC Cloud Lifecycle Management Compact Deployment.

Where to go from here

1. If Cloud Extensions and Platform Manager are installed on SSL with a third-party certificate using the bundled JRE, import the certificate into the JRE of the Cloud Portal and Database AR System. For more information, see Enabling SSL HTTPS on Windows non-CLM applications.

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. Verifying the installation