Upgrading compact deployment for version 4.6

This topic shows you how to perform a "live" upgrade in your production environment. In this scenario, you do not take your environment off-line during the upgrade.

To be specific, the topic guides you through a Compact Deployment 1 AR System server upgrade in the Windows environment from 4.1 to 4.6. Since there are only slight variations between the various deployment types, you can use these instructions, for example, when upgrading Compact or Medium deployments. 

Note

In version 4.6, only Compact, Small, and Medium deployments are supported.

Note

Before you start the upgrade from 4.1 to 4.6, you might be surprised that you don't have to upgrade every product in the environment.

Since this topic documents a Windows/SQL Server upgrade, the procedures in this topic differ slightly from a Linux/Oracle upgrade. The documentation tries to point out differences between the two environments. Nevertheless, you should always follow the prompts in the installer. If you see differences between the installer and the documentation, please enter a review comment at the bottom of the topic, and BMC will update the documentation accordingly.

This topic includes the following sections:

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

Before you begin

  • Update the customer range field IDs before you start upgrading. Otherwise, the upgrade will likely fail.
  • 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.
  • 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.
  • 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.
  • 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).

To launch the upgrade and pre-analyze the currently installed products.

  1. Download the BMC Cloud Lifecycle Management solution, as instructed in Downloading the installation files.
  2. Launch the install planner. 
    For detailed instructions, see Launching the upgrade and pre-analyzing the currently installed products.  
  3. Pre-analyze your environment. 
    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 detailed instructions, see To upgrade and pre-analyze the installed products.
  4. When all the products on the target server have passed the pre-analyzed check, click Next to continue. 
  5. When the deployment confirmation panel appears, review the summary of the host settings.
  6. 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

  7. Select the first product to upgrade from the Currently Installing tree and click Next.

To upgrade Enterprise Mid-Tier on Enterprise-AR

Note

The 4.6 upgrade does not affect the Enterprise AR System server because it is already version 8.1.01, so the install planner skips the server upgrade.

In this session, you upgrade the BMC AR System Mid-Tier to version 8.1.02 to replace the 8.1.01 version that was part of SSI stack. You also replace Tomcat 6 with Tomcat 7. These newer versions improve security and performance 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. Review the 64-bit Oracle JRE 1.7 directory– for example, C:\Program Files\Java\jre7 – and then click Next.
  4. In the Mid-Tier Tomcat Installation Configuration panel, select Yes (the default) to disable Tomcat 6.0 and install Tomcat 7.0. 
    If you click No, Tomcat 7.0 is not installed and you can manually install it later. 
  5. Review the Tomcat configuration parameters for initial memory (1024 MB), maximum memory (1024 MB), the HTTP port (8080), and then click Next.
  6. Preview the Mid Tier version listed (8.1.02), and then click Install
    The installer makes no other changes to the AR System products. 

  7. If you see a recommendation about CPU clock speed on your VM, you can safely ignore it. Click Next to continue with the installation.  
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
    You can continue with AR Post Install Configuration. 

To configure AR Post Installation on Enterprise-AR

  1. On the AR Post Install Configuration Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
  4. In the Installation Summary panel, review the AR Post Install Configuration installation log and then click Done to finish the upgrade. 
    Next you start configuring the BMC Mid-Tier post installation.

To upgrade the Mid-Tier

In this session, you upgrade the BMC AR System Mid-Tier to version 8.1.02. You also replace Tomcat 6 with Tomcat 7. These newer versions improves security and performance. 

  1. On the BMC Mid-Tier Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. Review the Oracle 1.7 JRE 64-bit settings (for example, C:\Program Files\Java\jre7), and then click Next.
  4. In the Mid-Tier Tomcat Installation Configuration panel, select Yes (the default) to disable Tomcat 6.0 and install Tomcat 7.0. 
    If you click No, Tomcat 7.0 is not installed and you can manually install it later. 
  5. Review the Tomcat configuration parameters for initial memory (1024 MB), maximum memory (1024 MB), the HTTP port (8080), and then click Next.
  6. Preview the Mid Tier version listed (upgraded to 8.1.02), and then click Install

  7. Review the clock speed warning – this messaged is informational only – and then click Next
  8. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  9. Continue with the BMC Mid-Tier Post Install Configuration.
  10. Monitor the progress of the other product upgrades if you are upgrading them in parallel. 

To configure the BMC Mid-Tier post installation

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 upgrading Cloud Database Extensions.

To configure Atrium Web Services post installation

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

Note

If you are upgrading from version 4.5.00 to 4.6.00, the installer applies important Tomcat fixes to Atrium Web Services. Otherwise, the underlying version of Atrium Web Services remains the same. 

  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 upgrading BMC Server Automation.

To upgrade BMC Server Automation

  1. (Linux only) In the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next
    Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.

  2. Click Next.
    The Upgrade Progress panel is displayed, which shows you the overall status of the upgrade progress.
    In these steps, you are upgrading the BBSA application server to version 8.7.00.256. 

    Tip

    If you do not see any progress with the status bar, make sure that the product you are upgrading is selected under the Currently Upgrading section on the left navigation pane.

  3. Review the welcome information, and then click Next.
  4. Take a VM snapshot and database backup, as prompted by the installer.
  5. If the MAS, PXE Server, and Advance Repeater services are running (for example, because you are in a HA environment), manually stop them, and then click Next.
  6. At the prompts, review the original installation inputs, and then click Next.
    Use your planning spreadsheet to guide you through the upgrade.
  7. In the Installation Preview panel, review the information and then click Install to upgrade the Application Server to version 8.7.00.256.
  8. In the Installation Summary panel, review the installation log and then click Done to finish the application server upgrade.
  9. Review the welcome information, and then click Next to upgrade the BMC Server Automation Console to version 8.7.00. 

    Note

    Before you upgrade the console, make sure that the JRE in the NSH directory on the target host is not being used by another other process, for example, Application server, Bladelogic Process Spawner, RCP Console, RSCD Agent, NSH process, and so on.
  10. Take a VM snapshot and database backup, and then click Next
  11. In the Installation Preview panel, review the features to be installed and then click Install to start the upgrade.
  12. Review the Application Server validation warning, and then click Next
    This warning is benign – in the previous steps, you just upgraded the server to its correct version and patch level. 
     
  13. In the Installation Summary panel, review the installation log and then click Done.
  14. Review the welcome information, and then click Next to configure the post-installation upgrade.
  15. Take a VM snapshot and database backup, and then click Next
    Stop the BSA client if it is running.
  16. Enter the RBACAdmin and BLAdmin passwords, and then click Next.
  17. The installer prompts you to log on to the BBSA Console with the defaultProfile authentication login.
  18. Manually perform the following verification steps:
    1. Go to the BMC Server Automation host.
    2. Log on to the application server with the console (for example, with the BLAdmin user).
      Use the defaultProfile for authentication.
       
    3. If you are successful, exit the console.
    4. Click Next in the install planner continue with the upgrade.  
  19. In the BMC Server Automation User Information panel, enter and confirm the BLGuest password, and then click Next.
  20. In the Installation Preview panel, review the features to be installed and click Install to start the upgrade.
  21. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  22. Review the installation log and then click Done to end this session. 
  23. Before you start another upgrade:
    1. Manually upgrade the Virtual Center (VC) agent.
    2. Manually upgrade the BMC RSCD Agent on the source VM Template.
      After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.

To upgrade BMC Network Automation

  1. On the BMC Network Automation Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. In the OS User Account Information panel, review the settings, and then click Next.
  4. In the Web Server Information panel, review the Tomcat port values to use with BNA, and then click Next.
  5. In the Database Information panel, review the settings, and then click Next.
  6. In the Memory and System Options panel, review the settings, and then click Next.
  7. In the CSM Integration Information panel, review the integration settings, and then click Next

    Note

    You can integrate new CSM artifacts as needed. If you select this option, the installer overwrites the existing artifacts during the upgrade. Most customers should not select this option during the upgrade! 
  8. On the Installation Preview panel, review the BMC Network Automation information, and then click Install.
  9. In the Installation Summary panel, review the BMC Network Automation installation log and then click Done to finish the upgrade.
  10. Continue by upgrading AR Post Install Configuration.

To upgrade Cloud Database Extensions

  1. On the Cloud Database Extensions Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. In the Java Information panel, review the settings and then click Next
    Using the default bundled JRE simplifies SSL configuration, among other advantages. You can also enter the directory path to an external 64-bit Oracle 1.8 JRE 64-bit directory, for example, C:\Program Files\Java\jre8.
  4. On the Installation Preview panel, review the Cloud Database Extensions information, and then click Install.
  5. In the Installation Summary panel, review the Cloud Database Extensions installation log and then click Done to finish the upgrade.
  6. Monitor the progress of the other product upgrades if you are upgrading them in parallel. 

To upgrade BMC Atrium Orchestrator components

In this session, you upgrade BMC Cloud Lifecycle Management Content and the BMC Server Automation Console that runs on the BAO host.

Note

The 4.6 upgrade does not affect Access Manager and Repository (AMREPO) and Configuration Distribution Peer (CDP), so the install planner skips the AMREPO and CDP upgrades.
  1. On the BMC Cloud Lifecycle Management Content Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. Review the remote installation directory, and then click Next.
    The default is C:\Program Files\BMC Software\AO-Content
  4. In the Repository Communication Settings panel, enter the repository password (by default, admin123), and then click Next.
  5. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
  6. Review the validation warnings, and then click Next
  7. In the Installation Summary panel, review the BMC Cloud Lifeycle Management Content installation log and then click Done to finish the upgrade.
    You now are ready to upgrade the BMC Server Automation Console that is installed on the BAO host. 
  8. On the BMC Server Automation Console Welcome page, click Next.
  9. Take a VM snapshot and database backup, and then click Next
  10. On the Installation Preview panel, review the information for the BMC Server Automation Console, and then click Install.
  11. Review the Application Server validation warning, and then click Next
    This warning is benign – in previous upgrade steps, you just upgraded the BSA Application Server to its correct version and patch level. 
     
  12. In the Installation Summary panel, review the BMC Server Automation Console installation log and then click Done to finish the upgrade.
  13. Monitor the progress of the other product upgrades if you are upgrading them in parallel. 

To upgrade Cloud Platform Manager

  1. On the Cloud Platform Manager Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. Review the NSH installation directory that is required for Platform Manager in version 4.6 (by default, C:\Program Files\BMC Software\NSH), and then click Next.
  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 Oracle 1.8 JRE 64-bit directory (for version 4.6– for example, C:\Program Files\Java\jre8
  5. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
  6. On the Platform Manager Configuration Directory Information panel, review the path, and then click Next
    The default path is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration
  7. Review the OSGi port settings, and then click Next
    By default, OSGi is set to the HTTP protocol on port 7070. But you can set the protocol to HTTPS on port 9443.
  8. On the Deploy Cloud Portal Web Application on Platform Manager panel, perform one of the following steps:
    1. If you do not want to deploy the new clmui (also known as the End User Portal or EUP) on the Platform Manager host, select No (the default), and click Next.
    2. (Optional) If you want to deploy the new clmui on the Platform Manager host, select Yes, enter the target host and port for the Self-Check Monitor, and then click Next
      The default URL is:
      https://<SelfChecker>:8443/health

      If you enter these Self Checker values in advance, you do not need to manually configure them later. If you do not plan to deploy the Self-Check Monitor at this point or the input details are not available to you, 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. Review the Persistence Manager details, and then click Next.
    Make sure that the proper time zone for your environment is set, for example, America/Los Angeles.
  10. Review the Core Cloud Services Details, and then click Next.
  11. On the Resource Manager details panel, enter the BBNA (by default, sysadmin), BLAdmin, BBSA, BLGuest, and  AO Server (by default, admin123) passwords, and then click Next.
  12. Review the SMTP Configuration details, and then click Next 
  13.  Click No (the default) to disable the on-premise database as a service (DBaaS) during upgrade, and then click Next
     You can still configure DBaaS later after you finish upgrading. 
    (Optional) If you select Yes, enter the BMC Database Automation details (for example, the host name, user, and password), and then click Next.   
  14. Click No (the default) to disable the VMware vCloud Director Provider during upgrade, and then click Next.
     You can still configure vCloud later after you finish upgrading. 
    (Optional) If you select Yes, enter the vCloud details (for example, the server name, version, administrator user, and password), and then click Next.
  15. On the Installation Preview panel, review the Cloud Platform Manager information, and then click Install.
  16. In the Installation Summary panel, review the Cloud Platform Manager installation log and then click Done to finish the upgrade.
  17. Continue by upgrading Cloud Portal AR Extensions. 

To upgrade Cloud Portal AR Extensions

  1. On the Cloud Portal AR Extensions Welcome page, click Next.
  2. Take a VM snapshot and database backup, 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 Oracle 1.8 JRE 64-bit directory (for version 4.6– for example, C:\Program Files\Java\jre8
  4. On the BMC AR System Server & IT Service Mgt Suite user inputs panel, review the settings, and then click Next.
  5. 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.
  6. 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.

  7. Review the Platform Manager Host Panel details. and then click Next.
    Make sure that you use the same protocol and port (for example, HTTP and 7070) that you entered during the Platform Manager upgrade. 

  8. On the Installation Preview panel, review the Cloud Portal AR Extensions information, and then click Install.

  9. In the Installation Summary panel, review the Cloud Portal AR Extensions installation log and then click Done to finish the upgrade.
    The Cloud Upgrade Migration Welcome panel appears under the Cloud Portal AR Extension node.
  10. If you upgraded Platform Manager on HTTPS/SSL, see the following instructions:

    Note

    Make sure that you import the certificate on Enterprise-AR in the Java bundled at <CLM_Install_Dir>\JVM_1.8.0\lib\security\cacerts.

To run data migration after you finish upgrading

Note

Before you run data migration, review Migrating data for the cloud core components.

If you completed upgrading the Cloud Portal AR Extensions and if you have not exited the BMC Cloud Lifecycle Management Installer, perform the following steps to migrate the data:

  1. On the Cloud Upgrade Migration Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the Upgrade Migration - Cloud Administrator Credentials panel, specify the cloud administrator credentials (your clmadmin user, but not Demo or appadmin), and then click Next.
  4. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, review the AR System administrator credentials. 

  5. Click Next.
    The data migration process begins.
  6. (Optional) During migration:
    1. Click the embedded link to review a step-by-step HTML report of the data migration process.
    2. Review the Migration Status report for important details about the migration, as shown in the following screenshot:
       
    3. Click the embedded links to review additional details about the migration.  

  7. When the data migration is successfully finished, review the information, and then click Done
    You can click the embedded link to review a step-by-step HTML report of the data migration process.
  8. Review the progress of the current session and your overall progress, and then click Next.
  9. (optional) After you successfully finish the upgrades, install CLM Self-Check Monitor and Cloud Portal Web Application. For more information, see:
  10. In the final Installation Summary panel, review the log and then click Done to exit.

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

  5. Perform the post-upgrade configuration tasks.

Related topic

End-to-end in-place 2AR upgrade for version 4.6

Was this page helpful? Yes No Submitting... Thank you

Comments