End-to-end in-place 2AR upgrade 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 Small Deployment 2 AR System server (Enterprise-AR and Cloud-AR) upgrade in the Windows environment from 3.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

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 an underscore (_)
    • 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 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 or BMC ProactiveNet; you can download the installation files from EPD with assistance from BMC Customer Support. 
  • Before you upgrade BMC Remedy IT Service Management Suite, review the CPU and RAM recommendations on the BMC Remedy IT Service Management documentation portal. 
  • 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 BMC Server Automation

Note

Upgrading the BMC Server Automation components in BMC Cloud Lifecycle Management 4.6 takes place in two stages. First, you upgrade the application server and console to 8.6.01. Second, the installer prompts you to upgrade 8.7.00 (patch 1). 
  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. Review the Upgrade Progress panel, which shows you the overall status of the upgrade progress.
    In these steps, you are upgrading the BBSA application server to version 8.6.01. 

    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. Take a VM snapshot and database backup, as prompted by the installer.
  4. 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.
  5. At the prompts, review the original installation inputs, and click Next.
    Use your planning spreadsheet to guide you through the upgrade.
  6. In the Installation Preview panel, review the information and then click Install to start the upgrade.
  7. In the Installation Summary panel, review the installation log and then click Done to finish the application server upgrade.
  8. Click Next to upgrade the BMC Server Automation Console to version 8.6.01. 

    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.
  9. Take a VM snapshot and database backup, and then click Next
  10. In the Installation Preview panel, review the features to be installed and then click Install to start the upgrade.
  11. If you are prompted to configure your machine to run in unrestricted mode, manually perform the task and then click Next
  12. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  13. Click Next to upgrade the BBSA Application Server to 8.7.00.256.
  14. Take a VM snapshot and database backup, and then click Next
  15. 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
  16. At the prompts, review the original installation inputs, and then click Next.
    Use your planning spreadsheet to guide you through the upgrade.
  17. In the Installation Preview panel, review the information and then click Install to start the upgrade to 8.7.00 (patch 1).
  18. In the Installation Summary panel, review the installation log and then click Done to finish the application server upgrade to 8.7.00 (patch 1).
  19. Click Next to upgrade the BMC Server Automation Console to version 8.7.00 (patch 1). 

    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.
  20. Take a VM snapshot and database backup, and then click Next
  21. In the Installation Preview panel, review the features to be installed and then click Install to start the console upgrade.
  22. If you are prompted to configure your machine to run in unrestricted mode, manually perform the task and then click Next
  23. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  24. Click Next to configure the post-installation upgrade.
  25. Take a VM snapshot and database backup.  
  26. Enter the RBACAdmin and BLAdmin passwords, and then click Next.
  27. The installer prompts you to log on to the BBSA Console with the defaultProfile authentication login.
  28. 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 and continue with the upgrade.  
  29. In the BMC Server Automation User Information panel, enter and confirm the BLGuest password, and then click Next.
  30. In the Installation Preview panel, review the features to be installed and click Install to start the upgrade.
  31. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  32. Review the installation log and then click Done to end this session. 
  33. Before you start the BMC Atrium Orchestrator 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 Atrium Orchestrator - Configuration Distribution Peer 

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

  1. On the Access Manager and Repository Welcome page, click Next.
    Review the information carefully, especially the steps you must perform before you upgrade AMREPO in a HA environment.
  2. Take a VM snapshot and database backup, and then click Next
  3. Review the Access Manager Communication Settings, and then click Next.
  4. On the Installation Preview panel, review the Access Manager and Repository settings, and then click Install.
  5. In the Installation Summary panel, review the Access Manager and Repository installation log and then click Done to finish the upgrade.
  6. On the BMC Atrium Orchestrator CDP Welcome panel, click Next.
  7. Take a VM snapshot and database backup, and then click Next
  8. Review the remote installation directory, and then click Next.
    The default is C:\Program Files\BMC Software\AO-Platform\CDP
  9. Review the CDP HTTP port (28080 by default) and shutdown port (28005 by default), and then click Next.
  10. Review the CDP peer settings, and then click Next
  11. Review the repository communication settings, and then click Next.
  12. On the Installation Preview panel, review the information for BMC Atrium Orchestrator CDP, and then click Install.
  13. In the Installation Summary panel, review the CDP installation log and then click Done to finish the upgrade.
  14. On the BMC Cloud Lifecycle Management Content Welcome page, click Next.
  15. Take a VM snapshot and database backup, and then click Next
  16. Review the remote installation directory, and then click Next.
    The default is C:\Program Files\BMC Software\AO-Content
  17. In the Repository Communication Settings panel, enter the repository password (by default, admin123), and then click Next.
  18. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
  19. Review the validation warnings, and then click Next
  20. 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. 
  21. On the BMC Server Automation Console Welcome page, click Next.
  22. Take a VM snapshot and database backup, and then click Next
  23. On the Installation Preview panel, review the information for the BMC Server Automation Console, and then click Install.
  24. If you are prompted to configure your machine to run in unrestricted mode, manually perform the task and then click Next
  25. In the Installation Summary panel, review the BMC Server Automation Console installation log and then click Done to finish the upgrade.
  26. On the Atrium Orchestrator Post Install Configuration Welcome page, click Next.
  27. Take a VM snapshot and database backup as a precaution (even though the installer does not prompt you to).
  28. On the AO Adapters Selection Preview Panel, review the adapters in your installation (for example, the ARS Adapter and BladeLogic Adapter) that you must manually configure after the upgrade is finished, and then click Install.
  29. In the Installation Summary panel, review the Atrium Orchestrator Post Install Configuration installation log and then click Done to finish the upgrade.
  30. Manually activate the BMC Atrium Orchestrator adapters.

To upgrade Enterprise-AR and Cloud-AR

In this session, you upgrade the Enterprise-AR and Cloud-AR stacks. This session can take several hours to complete, since you are upgrading multiple products on both hosts, for example, BMC Action Request, BMC Atrium Core, BMC Service Request Management, DSO mappings, and so on. If you are familiar with CLM installs or upgrades, you can perform these steps in parallel. 

Note

  • Before you start the upgrade:
    • Install Oracle 1.7 JRE 64-bit on Enterprise-AR and Cloud-AR.
    • Stop or temporarily disable services that take up CPU and memory and slow down the upgrade. These include Apache Tomcat, Windows Update, Java processes run by browsers, McAfee Audit Manager Service, and so on. You can restart or enable them later when you finish the upgrade.
  • By default, the installer skips BMC IT Service Management and BMC Service Level Management during upgrade.
  1. On the Enterprise-AR Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next.
    Review the other instructions as they apply to your environment, for example, if you must stop the services on the secondary AR System Server.   
  3. Review the Oracle 1.7 JRE 64-bit settings, and then click Next.
  4. Review the portmapper settings, and then click Next.
  5. On the User and Database Information panel, enter and confirm the ARAdmin password, and then click Next.
    By default, the ARAdmin password is AR#Admin#.
  6. On the AR System Server information panel, enter the AR Server password, and then click Next.
  7. On the Installation Preview panel, review the Enterprise-AR Server information, and then click Install.
  8. (Optional) Select BMC Remedy Action Request System under BMC AR System Server - Cloud Database Primary and run the Cloud AR upgrade in parallel.
  9. Review the validation warnings, and then click Next.
  10. In the License Information panel, enter the AR Server License Key, and then click Next.
  11. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue upgrading BMC Atrium Core.

To upgrade BMC Atrium Core on Enterprise-AR

  1. In the Installation Summary panel, review the AR Server installation log and then click Done to finish the upgrade.
    Next upgrade BMC Atrium Core.
  2. On the BMC Atrium Core Welcome page, click Next.
  3. Take a VM snapshot and database backup, and then click Next
  4. On the AR System Server information panel, review the settings, and then click Next.
  5. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
  6. Review the warnings, fix any problems (for example, increase the memory on your VM), and then click Next.
    The Atrium Core installation continues. Upgrading the Product Catalog and other Atrium components can take quite some time to complete, depending on how much memory you have on your system.
  7. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade.
    Next upgrade BMC Atrium Integrator. 

To upgrade BMC Atrium Integrator on Enterprise-AR

  1. On the BMC Atrium Integrator Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the AR System Server User Inputs panel, review the settings, and then click Next.
  4. On the Installation Preview panel, review the BMC Atrium Integrator information, and then click Install.
  5. In the Installation Summary panel, review the BMC Atrium Integrator installation log and then click Done to finish the upgrade.
    Now you can can upgrade BMC Service Request Management.

To upgrade BMC Service Request Management on Enterprise-AR

  1. On the BMC Service Request Management Welcome page, click Next.

  2. Take a VM snapshot and database backup, and then click Next
  3. In the AR System Overlays Feature panel, review the information, and then click Next.
    If you want to preserve your customizations after the upgrade, use the Creating overlays with BPCU for existing customizations as instructed before you continue.
  4. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
  5. On the Installation Preview panel, review the Service Request Management information, and then click Install.
    Upgrading BMC Service Request Management can take quite some time to complete, depending on how much memory you have on your system.
  6. In the Installation Summary panel, review the BMC Service Request Management installation log and then click Done to finish the upgrade.
    Next, you install the Enterprise Mid-Tier. 

To upgrade Enterprise Mid-Tier on Enterprise-AR

In this session, you upgrade the 8.1.02 version of the BMC AR System Mid-Tier to replace the 8.1.01 version that was upgraded as part of SSI stack. You also replace Tomcat 6 with Tomcat 7. These newer versions improves 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.
    Next, you configure AR System post-installation on the Enterprise-AR server.

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 upgrading the Cloud-AR server.

To upgrade Cloud-AR

  1. On the Cloud Database Primary 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. Review the portmapper information, and then click Next.
  5. On the User and Database Information panel, enter and confirm the CARAdmin password, and then click Next.
    By default, the CARAdmin password is AR#Admin#.
  6. On the AR System Server Administrator information panel, review the settings, and then click Next.
  7. On the Installation Preview panel, review the Cloud Database Primary information, and then click Install.
  8. Review the validation warnings, and then click Next.
  9. In the License Information panel, enter the AR Server License Key, and then click Next.
  10. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue.
  11. In the Installation Summary panel, review the Cloud Database Primary installation log and then click Done to finish the upgrade.
    Next upgrade BMC Atrium Core on the Cloud-AR server.

To upgrade BMC Atrium Core on Cloud-AR

  1. On the BMC Atrium Core Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the AR System Server information panel, review the settings, and then click Next.
  4. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
  5. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade.

To configure AR Post Installation on Cloud-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 upgrade the DSO mappings on the Enterprise-AR server.

To upgrade the DSO mappings on Enterprise-AR

  1. On the DSO Mapping Welcome page for the Enterprise-AR server, 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 on the Enterprise-AR server, and then click Next.
  4. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next.
  5. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.   
  6. In the next Atrium DSO Mapping Summary panel, review the Atrium DSO Mapping Summary installation log and then click Done to finish the upgrade.
    Next upgrade the DSO mappings on the Cloud-AR server.

To upgrade the DSO mappings on Cloud-AR

  1. On the DSO Mapping Welcome page for the Cloud-AR server, click Next.

    Note

    The installer also loads the AR System Mid-Tier and Atrium Core - Web Registry Components into the Currently Upgrading tree. If you are comfortable installing products in parallel, you can start upgrading them as well. 
  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 on the Cloud-AR server, and then click Next.
  4. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next.
  5. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.
  6. In the Cloud-AR Atrium DSO Mapping Summary panel, review the Atrium DSO Mapping Summary installation log and then click Done to finish the upgrade.
  7. Continue the session by upgrading the AR System Mid-Tier.
    If you are upgrading products in parallel, the installer loads Cloud Database Extensions into the Currently Upgrading tree and is available for you to start upgrading.

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. You can also upgrade Atrium Core - Web Registry Components in parallel. 

  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 by configuring the BMC Mid-Tier post installation.
  10. Monitor the progress of the other product upgrades (for example, Atrium Core - Web Registry Components or Cloud Database Extensions) 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 installing the Atrium Core – Web Registry Components.

To upgrade BMC Atrium Core – Web Registry Components

In this example, you are upgrading the Mid-Tier, Cloud-AR DSO Mapping, and Atrium Core - Web Registry Components in parallel. 

  1. On the Atrium Core - Web Registry Components Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the BMC AR System Server & IT Service Mgt Suite - Primary Information panel, review the settings, and then click Next.
  4. On the Web Service Registry Information panel, enter the admin password (for example, admin), review the other settings, and then click Next.
  5. On the Installation Preview panel, review the BMC Atrium Core – Web Registry Components information, and then click Install.
  6. In the Installation Summary panel, review the BMC Atrium Core – Web Registry Components installation log and then click Done to finish the upgrade.
  7. Continue with configuring Atrium Web Services post installation. 
  8. Monitor the progress of the other product upgrades if you are upgrading them in parallel. In this example, the installer loads BMC Network Automation into the Currently Upgrading tree as the next (and only) product to upgrade.
     

To configure Atrium Web Services post installation

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

To upgrade Cloud Database Extensions

In this example, you are upgrading the Mid-Tier, Atrium Core - Web Registry Components, and Cloud Database Extensions in parallel. 

  1. On the Cloud Database Extensions Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next
  3. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
  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 (for example, Atrium Core - Web Registry Components) if you are upgrading them in parallel. When it finishes, start upgrading BMC Network Automation. 

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 Cloud Platform Manager. 

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.
  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, 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. (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

  7. Review the Platform Manager Host Panel details. and then click Next.

  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.
    • Page not found for multiexcerpt macro.
    The page: 2020-06-08_05-43-05_End-to-end upgrade process - In-Place strategy was not found. Please check/update the page name used in the 'multiexcerpt-include' macro.

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. If you are migrating from 3.1.x to 4.x and AWS is available in the stack, the Cloud Upgrade Migration - Task Inputs panel appears. Enter the full path to the Amazon Web Services (AWS) account information .csv file, and then click Next.

    Note

    The .csv file must contain values for the AWS ACCOUNT_NAME, AWS ACCESS_KEY, and the AWS SECRET_ACCESS_KEY. ACCOUNT_NAME is the AWS account name registered in BMC Cloud Lifecycle Management. For multiple AWS accounts, add new row entries to the .csv file.
    Save this file on the Platform Manager server. In the input file, provide the full path of this file in the migration utility.
  5. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, review the AR System administrator credentials. 

  6. Click Next.
    The data migration process begins.
  7. (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.
       
    3. Click the embedded links to review additional details about the migration.  

  8. 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.
  9. Review the progress of the current session and your overall progress, and then click Next.
  10. (optional) After you successfully finish the upgrades, install CLM Self-Check Monitor and Cloud Portal Web Application. For more information, see:
  11. In the final Installation Summary panel, review the log and then click Done to exit.

Where to go from here

  1. (OptionalMerge your two AR System servers into one AR System server after upgrade
  2. 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.
  3. When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
  4. 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
  5. 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.

  6. Perform the post-upgrade configuration tasks.

Related topic

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

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

Comments