End-to-end in-place BMC Cloud Lifecycle Management upgrade

This topic guides you through a Small Deployment upgrade. Since there are only slight variations between the various deployment types, you can use these instructions when upgrading a Medium deployment also. 

Starting 4.7, you cannot upgrade all BMC products required for the solution by using the BMC Cloud Lifecycle Management installer. Products that must be upgraded using the standalone installers (shipped with the BMC Cloud Lifecycle Management installer) are described in the Upgrading BMC Products manually table in this topic. After upgrading the products manually, you can use the steps provided in this topic to upgrade the rest of the products using the BMC Cloud Lifecycle Management installer. 

This topic includes the following sections:

• • Before you begin
  • Upgrading BMC products manually
  • Applying patches and hotfixes for BMC Remedy AR System
  • Upgrading BMC Cloud Lifecycle Management – Small or Medium Deployment
  • Where to go from here

The installer guides you step-by-step through the upgrade process, including the configuration of dependent products.

Before you begin

• Download the BMC Cloud Lifecycle Management installation files. See Downloading-the-installation-files.
• 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.

• If you used the same VM to install earlier versions of BMC Cloud Lifecycle Management, perform the following tasks before you run the 4.6 upgrade.
  1. Uninstall the install planner.
  2. Back up or delete the C:\Windows\ProductRegistry.xml file.
  3. Delete %temp% files.

• On Windows hosts, delete old files from the C:\Windows\Temp folder.
• Accept the default values in the installer unless you have a good reason to change them.
• Do not mix IP addresses and hostnames during product select in the Host Information panel. Enter all IP addresses or all hostnames, but do not combine them.
• Some special characters create problems during installation. For more information, see Restricting the use of certain characters in passwords.
  • For BMC Network Automation, do not use special characters except _. 
  • For BMC Server Automation, do not use #. 
• Make sure that you take snapshots of your VM when the installer prompts you. These snapshots are valuable if you encounter an error during the upgrade. You can save an enormous amount of time by simply reverting to the saved snapshot, fixing the problem, and then continuing with the upgrade. 
• Review the known and corrected installation issues to avoid potential problems during upgrade.
• Prepare the installation environment. For example, delete all the files from the C:\Windows\Temp folder, make sure that the installer can connect to all the targets, and so on.
  • System-requirements-for-Windows
    
  • System-requirements-for-Linux
    
• TrueSight Operations Management and BMC ProactiveNet products are not supported in the 4.6 release and cannot be upgraded with the 4.6 installer. You must use the standalone installer to manually upgrade TrueSight Operations Management or BMC ProactiveNet; you can download the installation files from EPD with assistance from BMC Customer Support. 

• On-board at least one tenant in BMC Cloud Lifecycle Management before you start upgrading. 
• If you want to onboard existing VMs or if you have already onboarded VMs, any service offerings that you want to use or have already used for the VM must include a requestable offering.
• If you plan to upgrade Platform Manager using HTTPS/SSL with third-party certificates, import RootCA.crt into the Planner JRE (for example, <Planner_Install_Directory>\Planner\windows\Disk1\files\jre\lib\security).

Upgrading BMC products manually

Starting this release, you must upgrade to the compatible versions of BMC products required for the solution before upgrading the BMC Cloud Lifecycle Management components. 

After successfully upgrading to the BMC products, ensure that the services are up and running 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 hotfixes, 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.

Upgrading BMC Cloud Lifecycle Management – Small or Medium Deployment

Now that you have upgraded all the BMC products required for the solution, you can now run the BMC Cloud Lifecycle Management installer for upgrading the cloud components. 

1. Download the BMC Cloud Lifecycle Management solution, as instructed in Downloading-the-installation-files.
2. On the host where the installation files are downloaded, go to the location and run the setup.exe file to launch the installer.
3. On the Welcome screen, click Next and accept the license agreement. 
   The Installation Prerequisites screen displays the steps required to complete the installation. 
4. Select the I have read the prerequisites check box and click Next.
5. 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. 
6. Choose the install type as Upgrade, which is applicable to Compact, Small, and Medium deployments, then read the disclaimer, and click Next. 
7. Choose deployment template as Small Deployment, and one of the following deployment tiers based on your requirement:
   • Control Tier
   • Workload Tier
   • Both: Upgrades products in both Control and Workload Tiers.

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

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

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

11. After the PreAnalyzer report shows that all products are passed, click Next.
    You have completed integrating BMC products in the solution.
    The status shows the BMC products integrated with the BMC Cloud Lifecycle Management solution and their current version. For CLM components, the current version is 4.6.07.  
12. To continue installing other CLM components, on the Deployment Type panel, choose Upgrade to Cloud Lifecycle Management 4.7.00 and click Next.
13. Select the check boxes against the following products and enter the host names, wherever applicable:
    
    • Cloud Database Extensions
    • Platform Manager
    • Cloud Portal AR Extensions
    • Cloud SelfChecker
    • Cloud Portal Web Application
    • AR Post Installation
    • TrueSight Server Automation Post Installation

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

    Note

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

    As a precaution for recovering in case of failed installation, take a VM snapshot of the target host before every product installation. After every product is installed successfully, it is displayed in the Success tab. For any warnings and failures, check the respective tabs. 

    On the Upgrade Progress panel, the overall progress percentage, and the status of the product installation is displayed.

15. Provide the user inputs whenever prompted by the installer, and click Next to continue installing the selected products. 

    Consult the following table to provide inputs for the products during the upgrade:

    Product	User input fields	Notes
    AR Post installation on BMC AR System – Cloud Portal and Database Primary	BMC Remedy AR System Server User Inputs: - Administrator Name - Administrator Password - TCP Port - Server Name Alias
    TrueSight Orchestration – BMC Cloud Lifecycle Management Content	Remote destination directory
    	Repository Communication Settings: - Web Server Protocol - Host Name - Web Server Port Number - Repository User - Password	Provide the configuration settings where TrueSight Orchestration repository is installed.
    Cloud Database Extensions	Remote Destination Directory
    	BMC Remedy AR System – Cloud Portal and Database user inputs: - AR System Server Administrator Name - AR System Server Administrator Password - AR System Server TCP Port - AR System Server Name Alias
    Cloud Platform Manager	Java Information Panel	- If you have installed Cloud Platform Manager in a HA environment, upgrade only the Cloud Platform Manager – Primary server - 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 user inputs: - AR System Server Administrator Name - AR System Server Administrator Password - AR System Server TCP Port - AR System Server Name Alias
    	(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 the upgrade. This secret key is automatically generated.
    	Platform Manager Configuration Directory
    	Deploy Cloud Portal Web Application on Platform Manager	If Yes, provide: - 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.
    	Persistence Manager Details: - Dataset ID - Dataset Mask - Max number of connections - Database AR Server Timezone
    	Core Cloud Service Details: - Cache - Session Manager Service - Jetty Service - Cloud Manager Service - Logging Service
    	Certificate Inputs	If Enforce Certificate Validation is true, provide all certificate details.
    	SMTP configuration details: - SMTP host name - SMTP server password - SMTP port - Sender's email address
    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 user inputs: - AR System Server Administrator Name - AR System Server Administrator Password - AR System Server TCP Port - AR System Server Name Alias
    	(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
    (Optional) CLM Self-Check Monitor	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.
    	Certificate Inputs
    (Optional) Cloud Portal Web Application	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.
    	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

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

Where to go from here

1. Inform your user community to flush the cache on their browsers.
   Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers.
2. When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
3. Perform the post-upgrade configuration tasks.