Installing Small Deployment Windows for version 4.7

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. 

In this version, you can no longer install all BMC products using the Install Planner. You must install all the BMC products using the standalone installers shipped with the BMC Cloud Lifecycle Management installer before you run it. This topic also lists the BMC products in the order of installation and provides references to install the products. 

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

1. Prepare the installer and product and installer host requirements for Windows. 
   See Preparing to run the installer on a Windows computer
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. 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.
   
5. BMC recommends using a separate host for each of the product that is installed as a part of BMC Cloud Lifecycle Management installer except for few exceptions where a product must be installed on the same host as its dependent product. For example, 
   
   • Cloud Database Extensions and Cloud Portal AR Extensions must be installed on BMC AR System Server - Cloud Portal and Database – Primary.
   • Cloud Portal AR Extensions - Secondary must be installed on BMC AR System Server - Cloud Portal and Database – Secondary.
6. Review the Component BMC product service pack and patch levels topic and download the installers for all BMC products. 
   See Downloading the installation files. 
7. Take snapshots of the host after each component is installed to recover if the installation fails.
8. Review log files for each component after the installation is complete. In case of errors, do not proceed with the subsequent installation. 
9. Make sure that you install the hotfix for the Installation Planner. For details, see Hotfix for the Installation Planner .

Installing BMC products manually

You must install the compatible versions of the BMC products in the specified order manually before installing the CLM components: 

Applying patches and hotfixes for BMC Remedy AR System

Before applying the patches and hot fixes, ensure the following: 

• You have installed a supported browser version on the BMC AR System - Cloud Portal and Database host. 
• Perform the steps provided in the Knowledge Article:
  KA 000163473: Unable to deploy ITSM 18.05 Patch 5 using AR System Deployment Management Console  

To apply patches or hot fixes, do these: 

1. Log on to BMC AR System - Cloud Portal and Database host and apply the patches and hotfixes in the following order:

   • <Extracted_Installer_ZIP>/Applications/Patches/ARSystem

   • < Extracted_Installer_ZIP >/Applications /Patches/ITSM

   • < Extracted_Installer_ZIP >/Applications/Patches/SRM

   • < Extracted_Installer_ZIP>/Applications/Hotfix/ARSystem

   • < Extracted_Installer_ZIP >/Applications/Hotfix/AtriumCore
     For more information, see  Applying a patch .

2. After successfully applying the patches and fixes, do these steps to replace the AR uninstaller.jar file:
   1.  Rename <ARSystem_Installation_Directory>/UninstallBMCARSystem/uninstaller.jar to <ARSystem_Installation_Directory>/UninstallBMCARSystem/uninstaller_backup.jar
   2. Copy <Installer>/Applications/ Hotfix/ARSystem/Jar/uninstaller.jar to <ARSystem_Installation_Directory>/UninstallBMCARSystem.

Installing BMC Cloud Lifecycle Management for a Small Deployment

Now that you installed the compatible BMC products manually, and ensured that they are up and running, you can run the installer. The installer enables you to integrate with all the BMC products that you installed initially and installs the CLM components. 

1. On the host where the installation files are downloaded, go to the location and run the setup.cmd file to launch the installer.
2. On the Welcome screen, click Next and accept the license agreement. 
   The Installation Prerequisites screen displays the steps required to complete the installation. 
3. Select the I have read the prerequisites check box and click Next.
4. On the Directory Selection panel, ensure that you specify a directory on the host which fulfills the size requirements and click Next.
   If TrueSight Server Automation Network Shell (NSH) component is not detected on the server, the Install Planner installs it before continuing with the installation. If required, change the location where NSH is to be installed. 
5. Choose the install type as Install, which is applicable to both Small and Medium deployments, then read the disclaimer, and click Next. 
6. Choose deployment template as Small Deployment, and one of the following deployment tiers based on your requirement:
   • Control Tier
   • Workload Tier
   • Both: Installs products in both Control and Workload Tiers.

7. In the Host information for Small Deployment panel, select the check boxes and provide the host names for products installed in the Installing BMC Products manually section and click Next. 

   Caution

   You must only provide host names for the products installed. Do not provide the host names for the products not already in your environment as the installer does not install any other BMC product.

   The installer validates the information before continuing with the installation. 

8. In the operating system credentials panel, enter the user name and password for each host in the deployment. 
   If you are using the same credentials for each host, select the Apply the same credentials check box.
   The installer uses this information to detect NSH hosts and install RSCD agents on the host. 
   Depending on the deployment option, this step may take a while to complete. 
9. On the PreAnalyzer panel, provide the information for each of the following products, and click Next:

   • BMC AR System – Cloud Portal Database – Primary

   • AR System Mid-Tier 

   • Atrium Web services 

   • TrueSight Server Automation – File Server (Optional) 

   • TrueSight Server Automation – Application Server Console

   • TrueSight Network Automation 

   • TrueSight Orchestration

   • PXE Server (Optional)

   • TrueSight Network Automation – Device Agent (Optional)

     Note

     You provide information in this panel only if the installer is unable to retrieve it from the product configurations.

     The installer runs the PreAnalyzer and a detailed report that shows the overall status is displayed. 
     If the PreAnalyzer report fails for a product, you must fix the issue and run the PreAnalyzer again. You can continue with the installation only after all the products pass the PreAnalyzer checks. 

10. After the PreAnalyzer report shows that all products are passed, click Next.
    You have completed integrating BMC products in the solution. The status shows that all BMC products are successfully integrated with the BMC Cloud Lifecycle Management solution. 
11. To continue installing other CLM components, on the Deployment Type panel, choose Modify Existing Deployment and click Next.
12. Choose any one tier that matches your requirement and click Next:
    • Control Tier
    • Workload Tier
    • Both: Installs products in both Control and Workload Tiers.
13. Select the check boxes against the following products and enter the host names: 

    • BMC AR System – Cloud Portal Database – Primary

    • TrueSight Server Automation – App Server Console

    • TrueSight Orchestration

    • Cloud Database Extensions

    • Platform Manager

    • Cloud Portal AR Extensions

    • SelfChecker

    • Cloud Portal Web Application

14. In the operating system credentials panel, enter the user name and password for each host in the deployment. 
    If you are using the same credentials for each host, select the Apply the same credentials check box. This information is used to detect NSH and other services on the target hosts. 
15. On the PreAnalyzer panel, provide the information for the products for which the installer could not retrieve the information, and click Next. 
    The installer runs the PreAnalyzer and a detailed report that shows the overall status is displayed. If the PreAnalyzer report fails for a product, you must fix the issue and run the PreAnalyzer again. You can continue with the installation only after all the products pass the PreAnalyzer checks.

16. After the PreAnalyzer checks pass, the installer shows a summary of the products and the host names to be installed on each tier. Verify the information, make changes if required, and click Next.

    Caution

    If you do not make any changes, the deployment is continued on the specified hosts.

    The installation progress panel shows the progress of the installation. 

    Notes

    1. As a precaution for recovering in case of failed installation, take a VM snapshot of the target host before every product installation. 

    2. After every product is installed successfully, it is displayed in the Success tab.  
       For any warnings and failures, check the respective tabs. 

17. On the Installation Progress panel, the installation progress shows the overall progress percentage, and the status of the product installation. 
    If user inputs are generated by the installer, verify whether all the inputs are accurate and then click Next. 
    If not generated by the installer, provide the user inputs whenever prompted by the installer, and click Next to continue installing the selected products. For example, on the BMC Action Request System User Information panel, the installer may generate the target details, however, you may need to enter the password. 

    The installer installs the products in the following order: 

    Product	User Input fields/panel	Notes
    AR Post Install on BMC AR System – Cloud Portal Database – Primary	AR System Server User Inputs (Administrator Name, Administrator Password, AR System Server, TCP Port, AR System Server Name Alias) AR System User Information (First Name, Last Name, Login ID, Password, Confirm Password)	Stop and disable both the IP Helper and Proxy web service on the Enterprise AR Primary and Secondary host before you execute the AR Post Install Configuration. Otherwise, the installation fails.
    TSSA Post Install – TrueSight Server Automation – Application Server Console	TrueSight Server Automation database information (Host name or IP, Database Port, Database Name, User Name, Password)	Ensure that all NSH processes and the TrueSight Server Automation Client on the Application Server are stopped. The database user must have DBA privileges. If port 9700 is in use, open the /etc/services file and comment out the following lines: board-roar 9700/tcp #Board M.I.T. Service board-roar 9700/tcp #Board M.I.T. Service
    	BMC Remedy AR System - Cloud Portal and Database connection parameters
    	User Passwords (RBAC Admin, BLAdmin, and Authentication Profile)
    	TrueSight Server Automation User information (user created in Application Server)
    TSO Content (BMC CLM content) – TrueSight Orchestration	Repository Communication Settings (Web Server Protocol, Host Name, Web Server Port Number, Repository User, Password)	Default port is 28080.
    Cloud Database Extensions	Remote Destination Directory
    	AR System Server Administrator Name
    	AR System Server Administrator Password
    	AR System Server TCP Port
    	AR System Server Name Alias
    Cloud Platform Manager	Destination Directory Remote Destination Directory
    	Java Information Panel	Select the Use Bundled JRE option to simplify the SSL configuration or provide a location for an external 64-bit JRE directory.
    	BMC Remedy AR System - Cloud Portal and Database connection parameters
    	(optional) Remedy Single Sign-On Configuration - Enable RSSO	If you select Enable RSSO, provide the Remedy Single Sign-On credentials. (RSSO Service URL, Admin Username, Password, RSSO Realm, and RSSO Session Timeout (in minutes).
    	Secret Key Panel	Copy the Secret Key used for data encryption as it will be asked during installation or upgrade. This secret key is automatically generated.
    	Platform Manager Configuration Directory
    	OSGi Host Panel (Host, Port, Protocol)	OSGI will be installed on HTTPS/SSL. Change the protocol if installing on HTTP.
    	Deploy Cloud Portal Web Application on Platform Manager: Yes: Self-Check Monitor URL Session Timeout In Seconds	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.  If you selected Yes, enter the Self-Check Monitor URL (typically, https://<HealthCheckVM>:8443/health) and then click Next.  If you plan to install the Self-Check Monitor and you already know the host name, enter the URL. For example: https://<selfCheckerHost>:8443/health If you do not plan to deploy the Self-Check Monitor at this point, proceed with the dummy values that are pre-populated. You can always change the values later in the<CLM_Install_Dir>\Platform_Manager\configuration\preferences\PreferenceGroup.json file.
    	Superuser password	Password for the Login Service. You use this super user password during the Cloud Portal AR Extensions installation.
    	Persistence Manager Details (Dataset ID, Dataset Mask, Max number of connections, Database AR Server Timezone)	Make sure that you set the correct time zone for your AR System server.
    	Core Cloud Service Details (Cache, Session Manager Service, Jetty Service, Cloud Manager Service, Logging Service)
    	Resource Manager Details (BBNA Provider, BBSA Provider)	Enter the BBNA provider password (by default, sysadmin). Enter the BLAdmin password that you created previously.  Enter the BLGuest password that you created previously. Enter the Atrium Orchestrator callout provider password (by default, admin123).
    	SMTP Configuration Details (SMTP host name, port, server password, Sender's email address)
    	Configure BDA	If Yes, enter the BMC Database Automation details.
    	Configure VMware vCloud Director Provider for BMC Cloud Lifecycle Management.	If Yes, enter the password and review other information.
    Cloud Portal AR Extensions	Java Information	Select the Use Bundled JRE option to simplify the SSL configuration or provide a location for an external 64-bit JRE directory.
    	Secret Key Panel	Review or provide the secret key used for data encryption. The secret key must be the same as the key generated during the Platform Manager installation.
    	BMC Remedy AR System - Cloud Portal and Database connection parameters
    	Superuser Password Information	Enter the password provided for Cloud Platform Manager's Login Service.
    	Cloud Administrator User
    	TrueSight Orchestration Details	Enter the host, port, grid name, and administrator password for TrueSight Orchestration – CDP.
    	(Optional) Cloud Vista Cross launch	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. 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. If you selected Yes, enter the TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server details.
    	Platform Manager Host Panel
    	Mid-Tier Web Server URL	Specify the web server URL, do not use the BMC Remedy AR Mid-Tier URL.
    CLM Self-Check Monitor (Optional)	Remote Directory Selection Java Information	Select the Use Bundled JRE option to simplify the SSL configuration or provide a location for an external 64-bit JRE directory.
    	Secret Key Panel	Review or provide the secret key used for data encryption. The secret key must be the same as the key generated during the Platform Manager installation.
    	CLM Self-Check Monitor Configuration (Protocol, HTTPS Port, Tomcat Start Port, Tomcat Stop Port)	Review the HTTPS or HTTP port numbers (the HTTPS default port is 5443) used with the Self-Check Monitor server. Or select HTTP for the ports to start (8090) and stop (8007) the Self-Check Monitor
    	Certificate Inputs (TSA Certificate Path, TSA Certificate Password, TSO Certificate Path, TSO Certificate Password)
    Cloud Portal Web Application (Optional)	Remote Destination Directory Java Information	Select the Use Bundled JRE option to simplify the SSL configuration or provide a location for an external 64-bit JRE directory.
    	Port Information Panel (Protocol, HTTPS Port, Tomcat Start Port, Tomcat Stop Port)	Review the HTTPS or HTTP port numbers (the HTTPS default port is 8443) used to start the Cloud Portal Web Application, and then click Next. Or select HTTP for the ports to start (9070) and stop (9005) the Cloud Portal Web Application.
    	Configuration Inputs (Platform Manager URL, Session Timeout in seconds)	The installer constructs the URLs to open the Platform Manager and Self-Check Monitor, based on the configuration settings you entered. For example: https://PlatformManager:9443/csm https://SelfCheckerServer:5443/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.

18. After each product installation is complete, you may choose to view the logs, and then continue with the next installation. 

(Optional) Installing TrueSight Orchestration Development Studio

You install the TrueSight Orchestration Development Studio (formerly called BMC Atrium Orchestrator) manually after you install the CLM components.

For details, see  Installing TrueSight Orchestration Development Studio .

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