Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

End-to-end process for upgrading Small Deployment - In-Place strategy

This topic shows you how to perform a "live" upgrade in your production environment. 

To be specific, the topic guides you through a Small Deployment upgrade from 3.1 to 4.x. But you can use the procedure explained in this section to upgrade 2.1.x, 3.x, or 4.0 to 4.x. Since there are only slight variations between the various deployment types, you can use these instructions, for example, when upgrading Medium or Large deployments. 

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

Except for the BMC AR System Server & IT Service Mgt. Suite - Primary (Enterprise-AR) and BMC AR System Server - Cloud Database Primary (Cloud-AR) products, upgrade only one product at a time, based on the best practice upgrade sequence that BMC recommends. Because certain products are dependent on other products, you cannot upgrade all products at the same time.

Before you begin

Note

  • 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.
  • If you used this VM to install earlier versions of BMC Cloud Lifecycle Management, perform the following tasks before you run the 4.1 upgrade.
    1. Uninstall the install planner.
    2. Back up or delete the C:\Windows\ProductRegistry.xml file.
    3. Delete %temp% files.
  • 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.

To start the installer and integrate the products

  1. Download the BMC Cloud Lifecycle Management solution from the EPD site.
  2. Start the installer:
    • On Microsoft Windows, double-click the setup.cmd file.

    • On Linux, launch the installer by using Xmanager.
      With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

      You can also use VConsole to launch the installer.

    • To start the installer without dependencies, see Installing products without checking dependencies.
  3. In the lower right corner of the Welcome page, click Next.
  4. Review the license agreement, click I agree to the terms of the license agreement, and then click Next.
  5. On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the upgrade.
    InstallPrereQs.png

  6. Select the I have read the prerequisites check box and click Next.
    (optional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product upgrades.  

    If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.

  7. On the Directory Selection panel, navigate to the location on the host where you want to install the planner and click Next.
    The default location is C:\Program Files\BMC Software\Planner.
  8. On the Installation Preview panel, review the information and click Install.
  9. If NSH is not installed, the system prompts you to install it.
    The default location is C:\Program Files\BMC Software\NSH. 
  10. In the Select Installation Type panel, select Upgrade and then click Next.
    SelectInstallType.png
  11. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance. 
    UpgradeDisclaimer.png
  12. Click I agree to the terms of the disclaimer, and then click Next. 

  13. On the BMC Installation Registry panel, select if you have a backup registry to use or if you are integrating from scratch, and then click Next. 

    The backup registry lists the target hosts and which products were installed on them. This example does not have an registry available to simplify the upgrade process. If you do not have a registry, you must compile your own list of target hosts.

    UpgradeRegistry.png
    For more information, see deployment template for other types to implement.

  14. In the BMC AR System Configuration panel, the installer asks if you use one or more AR System servers in your environment.
    Select No (I have an Enterprise-AR and a Cloud-AR server), and then click Next.

    2ARs.png
  15. In the Select Deployment Template panel, select the template that matches your requirements. 
    For example, Small Deployment. 
    DeploymentType.png
  16. Click Next. The Deployment Tier Selection panel appears. You can upgrade products in the Control Tier, products in the Workload Tier, or products in both tiers.
    UpgradeDeploymentTier.png 
  17. Select Control Tier, and then click Next. 
    The default is Both, but this example only upgrades products in the Control Tier.
    DeploymentTier.png
    The Host Information for a Small Deployment panel appears for the Control Tier.

  18. Enter all the product hosts in your environment, and then click Next.
    The installer validates all the hosts on the Control Tier, to ensure a successful integration. You do not need to enter a host name in every field on this panel, just the product hosts currently used in your environment. 

    The Host Information panel performs the integration that, in earlier releases, was a pre-upgrade procedure.

    2ARHostInformation.jpg

     

  19. When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel. 
    IntegrationSummary.jpg
  20. Click Next.
     The Select Deployment Type panel is displayed, as shown in the following screenshot.
    SelectDeploymentType.png

  21. Choose Upgrade to Cloud Lifecycle Management 4.1.00, and then click Next.
     All product hosts that you integrated with your BMC Cloud Lifecycle Management solution by running the installer are now visible in the Host Information panel. If the host name or the product that you chose for upgrade is incorrect, click Previous to correct the information. 
    The installer lists the products that you must upgrade in the order that you must upgrade them. Products that you need to upgrade are displayed with a blue arrow next to the host name. In this example, upgrade BMC Server Automation - App Server & Console first, Atrium Orchestrator - Configuration Distribution Peer second, and so on. 

    UpgradeOrder.jpg

To upgrade BMC Server Automation

  1. Clear all the other products except BMC Server Automation - App Server & Console, and then click Next.

    Upgrade no more than two products in a session. In this example, upgrade only BMC Server Automation - App Server & Console in this first session. Upgrade other products in subsequent sessions.

  2. Enter the operating system user credentials and passwords for the target host, and then click Next. 
    The installer validates the credentials, upgrades the RSCD Agent on the target host, and performs additional upgrade actions.
    OSLogon.jpg 
  3. When the deployment confirmation panel appears, review the summary of the host settings.
    BSASummary.jpg
  4. (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.
    image2014-2-24 14:50:31.png 

  5. Click Next.
    The Upgrade Progress panel is displayed, which shows you the overall status of the upgrade progress.

    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.

    BSAWelcome.jpg

  6. Take a VM snapshot and database backup, as prompted by the installer.
    BSAsnapshot.jpg
  7. If you are upgrading a HA environment, stop the MAS, PXE Server, and Advance Repeater services, and then click Next. 
    StopServices.jpg 
  8. At the prompts, review the installation inputs, and then click Next.
    Use your planning spreadsheet to guide you through the upgrade.
    BSAcredentials.jpg 
  9. In the Installation Preview panel, review the information and then click Install to start the upgrade. 
    BSApreview.jpg 
  10. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    BSAupgradesummary.jpg

  11. On the VM where you upgraded BMC Server Automation, manually migrate the BladeLogic application server database data.
    For specific data migration instructions, see To run database migration and SQL update.
    RunMigration.png

    The external-files.zip needed for migration is located in the ..Applications\BL-OpsManager\Common folder on the installer host.

  12. Return to the installation host and upgrade the BSA Server Automation Console by clicking Next. 
    UpgradeBSAconsolewelcome.jpg
  13. Take a VM snapshot and database backup. 
  14. In the Installation Preview panel, review the features to be installed and then click Install to start the upgrade. 
    BSAConsolePreview.jpg 
  15. If you are prompted to configure your machine to run in unrestricted mode, manually perform the task and then click Next. 
  16. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    BSAConsoleSummary.jpg
  17. Click Next to configure the post-installation upgrade. 
    BSApostinstallupgradewelcome.jpg
  18. Take a VM snapshot and database backup. 
  19. Enter the RBACAdmin and BLAdmin passwords, and then click Next. 
    BSAuserpasswords.jpg 
  20. In the BMC Server Automation User Information panel, enter and confirm the BLGuest password, and then click Next. 
    BLGuest.jpg 
  21. In the Installation Preview panel, review the features to be installed and click Install to start the upgrade. 
    BSApostinstallupgradepreview.jpg 
  22. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    BSASummaryPostInstall.jpg
  23. Review the progress of the current session and your overall progress, and then click Next.
    BSAupgradeprogress.jpg
  24. Review the installation log and then click Done to end this session. 
  25. 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.

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. In the Host Information for an Upgrade Deployment panel, clear all the remaining products except Atrium Orchestrator - Configuration Distribution Peer, and then click Next.
    AOHostInformation.jpg 
  3. Enter the operating system user credentials and passwords for the target host, and then click Next.
  4. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    AOSummary.jpg 
  5. 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.
    AMREPOwelcome.jpg 
  6. Take a VM snapshot and database backup, and then click Next.
  7. Review the Access Manager Communication Settings, and then click Next.
    AMREPOcommsettings.jpg 
  8. On the Installation Preview panel, review the Access Manager and Repository settings, and then click Install.
    AMREPOpreview.jpg 
  9. Review the list of upgraded configuration files in the Access Manager and Repository upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    AMREPOconfigfiles.jpg 
  10. In the Installation Summary panel, review the Access Manager and Repository installation log and then click Done to finish the upgrade.
    AMREPOsummary.jpg 
  11. On the BMC Atrium Orchestrator CDP Welcome panel, click Next.
    CDPwelcome.jpg 
  12. Take a VM snapshot and database backup, and then click Next.
  13. Review the remote installation directory, and then click Next.
    The default is C:\Program Files\BMC Software\AO-Platform\CDP. 
  14. Review the CDP HTTP port (28080 by default) and shutdown port (28005 by default), and then click Next.
    CDPwebserver.jpg 
  15. Review the CDP peer settings, and then click Next. 
    CDPpeersettings.jpg 
  16. Review the repository communication settings, and then click Next.
    RepCommSettings.jpg 
  17. On the Installation Preview panel, review the information for BMC Atrium Orchestrator CDP, and then click Install.
    CDPinstallpreview.jpg 
  18. Review the list of upgraded configuration files in the CDP upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CDPconfigfiles.jpg 
  19. In the Installation Summary panel, review the CDP installation log and then click Done to finish the upgrade.
    CDPinstallsummary.jpg 
  20. On the BMC Cloud Lifecycle Management Content Welcome page, click Next.
    ContentWelcome.jpg 
  21. Take a VM snapshot and database backup, and then click Next.
  22. Review the remote installation directory, and then click Next.
    The default is C:\Program Files\BMC Software\AO-Content. 
  23. In the Repository Communication Settings panel, enter the repository password (typically admin123), and then click Next.
    AOrepcommsettings.jpg 
  24. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
    AOContentPreview.jpg 
  25. Review the validation warnings, and then click Next. 
  26. 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.  
    Contentinstallsummary.jpg 
  27. On the BMC Server Automation Console Welcome page, click Next.
    BSAConsoleWelcomeAO.jpg 
  28. Take a VM snapshot and database backup, and then click Next.
  29. On the Installation Preview panel, review the information for BMC Server Automation Console, and then click Install.
    AOBSAConsole.jpg 
  30. Review the validation warnings, and then click Next.
  31. In the Installation Summary panel, review the BMC Server Automation Console installation log and then click Done to finish the upgrade.
    BSAConsoleAOSummary.jpg 
  32. On the Atrium Orchestrator Post Install Configuration Welcome page, click Next.
    AOpostinstallconfig.jpg 
  33. 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. 
    AOadapters.jpg
  34. In the Installation Summary panel, review the Atrium Orchestrator Post Install Configuration installation log and then click Done to finish the upgrade.
    AOpostinstallconfigsummary.jpg 
  35. Review the progress of the current session and your overall progress, and then click Next.
    AOoverallprogress.jpg 
  36. Review the installation log and then click Done to end this session. 
    AOinstallsummary.png 
  37. Manually activate the BMC Atrium Orchestrator adapters.
  38. Start a new session to upgrade Enterprise-AR and Cloud-AR. You can also exit the installer. 

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, for example, BMC Action Request, BMC Atrium Core, BMC Service Request Management, DSO mappings, and so on. 

Note

Before you start the upgrade:

  • Install Oracle 1.7 JRE 64-bit on Enterprise-AR and Cloud-AR.
  • Use the Best Practice Conversion Utility (BPCU) to create overlays in BMC Service Request Management to preserve your customizations.

By default, the installer skips BMC IT Service Management and BMC Service Level Management during upgrade.

After you upgrade BMC Atrium Core on Enterprise-AR, immediately apply hotfix KA414865 that installs the BMC Atrium 8.x UI files.

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the remaining products except BMC AR System Server & IT Service Mgt. Suite - Primary and BMC AR System Server - Cloud Database Primary, and then click Next.
    EARhostinformation.jpg 
  3. Enter the operating system user credentials and passwords for the Enterprise-AR and Cloud-AR target hosts, and then click Next.
    You can apply the same credentials to both hosts, if applicable. 
  4. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    EARsummary.jpg 
  5. On the Enterprise-AR Welcome page, click Next.
    EARWelcome.jpg 
  6. 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.  
    EARsnapshot.jpg 
  7. Review the Oracle 1.7 JRE settings, and then click Next.
  8. Review the portmapper information, and then click Next.
    EARportmapper.jpg 
  9. 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#.
    EARDBinformation.jpg 
  10. On the AR System Server information panel, enter the AR Server password, and then click Next.
    EARadmininformation.jpg 
  11. On the Installation Preview panel, review the Enterprise-AR Server information, and then click Install.
    EARpreview.jpg 
  12. Review the validation warnings, and then click Next.
  13. In the License Information panel, enter the AR Server License Key, and then click Next.
    EARlicense.jpg 
  14. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue.
  15. Review the list of upgraded configuration files in the Enterprise-AR upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    EARconfigfiles.jpg 
  16. In the Installation Summary panel, review the AR Server installation log and then click Done to finish the upgrade.
     Next upgrade BMC Atrium Core. 
    EARupgradesummary.jpg 
  17. On the BMC Atrium Core Welcome page, click Next.
    AtriumWelcome.jpg 
  18. Take a VM snapshot and database backup, and then click Next.
  19. On the AR System Server information panel, review the settings, and then click Next.
    ACARServer.jpg 
  20. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
    AtriumPreview.jpg 
  21. Review the Web Services Registry and Atrium Core Web Services warnings, and then click Next.
    The Atrium Core installation continues. Upgrading the Product Catalog and other Atrium components can take quite some time to complete; in the BMC IDD Lab environment, the BMC Atrium Core upgrade took about 2 hours. 
    ACWSwarnigns.jpg 
  22. Review the list of upgraded configuration files in the BMC Atrium Core upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    AtriumCoreconfigfiles.jpg 
  23. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade.
    AtriumCoreinstallsummary.jpg
    Next upgrade BMC Atrium Integrator.  
  24. On the BMC Atrium Integrator Welcome page, click Next.
    AtriumIntegratorWelcome.jpg 
  25. Take a VM snapshot and database backup, and then click Next.
  26. On the AR System Server User Inputs panel, review the settings, and then click Next.
    AIARinputs.jpg 
  27. On the Installation Preview panel, review the BMC Atrium Integrator information, and then click Install.
    AIpreview.jpg 
  28. Review the list of upgraded configuration files in the Atrium Integrator upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    AIupgradeconfigfiles.jpg 
  29. In the Installation Summary panel, review the BMC Atrium Integrator installation log and then click Done to finish the upgrade.
    AtriumIntegratorInstallSummary.jpg
  30. Install the BMC Atrium 8.x UI files (hotfix KA414865).
    1. Extract the CLM-4.1-AtriumFilesforUI.zip file to the computer system where you run your web browser.
      Create a temporary directory, and extract the following ZIP files into the temporary directory:
      • atrium-dvm-AtriumWidget.zip
      • atrium-dvm-AtriumWidget-3p.zip
      • atrium-dvm-AtriumWidget-resources.zip
    2. Use the following URL to open the Data Visualization System Files in your web browser:
      http://<MidTierHost>:<PORT>/arsys/forms/<AR_SERVER_HOST>/Data+Visualization+System+Files
      http://vw-sjc-bsm-dv12:8080/arsys/forms/vw-sjc-bsm-dv05/Data+Visualization+System+Files 
    3. Enter a wildcard (%) into the Request ID field and then click Search to display the Data Visualization System files.
      DataVisualizationFiles.png 
    4. Back up existing ZIP files by selecting the attachment file and then clicking Save to Disk. Save the backups in a different directory than where you downloaded the hotfix.
      SaveToDisk.png 
    5. Select the existing attachment file and then click Delete. 
    6. Immediately replace the attachment file by clicking the empty space and then clicking Add. Select the replacement attachment and then click OK. 
    7. After you replace each ZIP file, immediately click Save in the upper-left of the browser window. Perform these steps for the other two attachment files. 
    8. Log out of the web browser and close all open sessions of Atrium Core Console.
    9. Open the Mid Tier VM to clean up the Apache Tomcat service.
    10. Stop the Apache Tomcat service.
    11. Delete the <AR Install Directory>/midtier/dvModule/ folder. 
    12. Delete the <AR Install Directory>/midtier/WEB-INF/atriumDeploymentPackages folder. 
    13. Delete the <AR Install Directory>/midtier/WEB-INF/AtriumWidget* folders.
    14. Delete the <AR Install Directory>/midtier/WEB-INF/lib/atrium-dvm-* files. 
    15. Delete the <AR Install Directory>/midtier/WEB-INF/lib/atrium-submodule-* files. 
    16. Restart the Apache Tomcat service.
    17. Log on to the Mid Tier and open the BMC Atrium Core Console to download and deploy the new files. 
  31. On the BMC Service Request Management Welcome page, click Next.
    SRMwelcome.jpg 
  32. Take a VM snapshot and database backup, and then click Next.
  33. 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 BPCU utility to create overlays as instructed before you continue. 
    SRMoverlays.jpg 
  34. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
    SRMinputs.jpg 
  35. 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; in the BMC IDD Lab environment, the upgrade took about 2 hours. 
    SRMpreview.jpg 
  36. Review the list of upgraded configuration files in the BMC Service Request Management upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    SRMconfigfiles.jpg 
  37. In the Installation Summary panel, review the BMC Service Request Management installation log and then click Done to finish the upgrade.
    Next you configure AR System post-installation on the Enterprise-AR server. 
    SRMsummary.jpg 
  38. On the AR Post Install Configuration Welcome page, click Next.
    ARPostInstallwelcome.jpg 
  39. Take a VM snapshot and database backup, and then click Next.
  40. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
    ITSMuserinputs.jpg 
  41. Review the list of upgraded configuration files in the post installation upgrade for Enterprise-AR, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    ARpostinstallconfigfiles.jpg 
  42. 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. 
    ARpostinstallsummary.jpg 
  43. On the Cloud Database Primary Welcome page, click Next.
    CARwelcome.jpg 
  44. Take a VM snapshot and database backup, and then click Next.
  45. Review the Oracle 1.7 JRE settings, and then click Next.
  46. Review the portmapper information, and then click Next.
    CARportmapper.jpg 
  47. 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#.
    CARdatabase.jpg 
  48. On the AR System Server Administrator information panel, review the settings, and then click Next.
    CARadministrator.jpg 
  49. On the Installation Preview panel, review the Cloud Database Primary information, and then click Install.
    CARpreview.jpg 
  50. Review the validation warnings, and then click Next.
  51. In the License Information panel, enter the AR Server License Key, and then click Next.
    CARlicense.jpg 
  52. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue.
  1. Review the list of upgraded configuration files in the Cloud Database Primary upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CARconfigfiles.jpg 
  2. 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. 
    CARsummary.jpg
  3. On the BMC Atrium Core Welcome page, click Next.
    CARatriumwelcome.jpg 
  4. Take a VM snapshot and database backup, and then click Next.
  5. On the AR System Server information panel, review the settings, and then click Next.
    CARAtriuminputs.jpg 
  6. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
    CARAtriumPreview.jpg 
  7. Review the list of upgraded configuration files in the Atrium Core upgrade with Cloud-AR, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CARAtriumconfigfiles.jpg 
  8. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade. 
    CARAtriumSummary.jpg 
  9. On the AR Post Install Configuration Welcome page, click Next.
    CARpostinstallwelcome.jpg 
  10. Take a VM snapshot and database backup, and then click Next.
  11. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
    CARpostinstallinputs.jpg 
  12. Review the list of upgraded configuration files in the post installation upgrade with Cloud-AR, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CARpostinstallconfigfiles.jpg 
  13. 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. 
    CARpostinstallsummary.jpg 
  14. On the DSO Mapping Welcome page for the Enterprise-AR server, click Next.
    EARDSOmappings.jpg 
  15. Take a VM snapshot and database backup, and then click Next.
  16. On the BMC Remedy AR System Server User Inputs panel, review the settings on the Enterprise-AR server, and then click Next.
    EARDSOinputs.jpg 
  17. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next. 
    EARDSOpassword.jpg 
  18. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.
    EARmappingsummary.jpg 
  19. Review the list of upgraded configuration files in the Enterprise-AR DSO upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    EARDSOconfigfiles.jpg 
  20. 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. 
    EARDSOmappingsummary.jpg 
  21. On the DSO Mapping Welcome page for the Cloud-AR server, click Next.
    CARDSOwelcome.jpg 
  22. Take a VM snapshot and database backup, and then click Next.
  23. On the BMC Remedy AR System Server User Inputs panel, review the settings on the Cloud-AR server, and then click Next.
    CARDSOinputs.jpg 
  24. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next.
    CARDSOpassword.jpg 
  25. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.
    CARDSOsummary.jpg 
  26. Review the list of upgraded configuration files in the Cloud-AR DSO upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CARDSOconfigfiles.jpg 
  27. In the next Atrium DSO Mapping Summary panel, review the Atrium DSO Mapping Summary installation log and then click Done to finish the upgrade.
    CARDSOsummarymapping.jpg 
  28. Review the progress of the current session and your overall progress, and then click Next. 
    You successfully upgraded the Enterprise-AR and Cloud-AR servers. 
    EARCARsummary.jpg 
  29. Review the final installation log and then click Done to exit the installer and end this session. 
  30. Start a new session to upgrade the AR System Mid-Tier.

To upgrade the Mid-Tier

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the other options except AR System Mid-Tier, and then click Next.
    MTHostInfo.jpg 
  3. Enter the operating system user credentials and passwords for the target host, and then click Next.
  4. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    MidTierUpgradeSummary.jpg 
  5. On the BMC Mid-Tier Welcome page, click Next.
    MTwelcome.jpg 
  6. Take a VM snapshot and database backup, and then click Next.
  7. Review the Oracle 1.7 JRE settings, and then click Next.
  8. On the Installation Preview panel, review the information, and then click Install.
    MTPreview.jpg 
  9. Review the clock speed warnings – these are informational only – and then click Next. 
  10. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    MTinstallsummary.jpg 
  11. Review the progress of the current session and your overall progress, and then click Next.
    MTsummary.jpg 
  12. Click Upgrade to Cloud Lifecycle Management 4.1.00 to upgrade BMC Atrium Core – Web Registry Components.
    Or click Exit the Installation to exit the installer and end the session.

To upgrade BMC Atrium Core – Web Registry Components

  1. In the installer, clear all the remaining options except Atrium Core – Web Registry Components, and then click Next.
    ACWSHostInfo.jpg 
  2. Enter the operating system user credentials and passwords for the target host, and then click Next. 
  3. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    ACWSdeploymentsummary.jpg 
  4. On the Atrium Core - Web Registry Components Welcome page, click Next.
    ACWSwelcome.jpg 
  5. Take a VM snapshot and database backup, and then click Next.
  6. On the BMC AR System Server & IT Service Mgt Suite - Primary Information panel, review the settings, and then click Next.
    ACWSAR.jpg 
  7. On the Web Service Registry Information panel, enter the admin password (for example, admin), review the other settings, and then click Next.
    ACWSpassword.jpg 
  8. On the Installation Preview panel, review the BMC Atrium Core – Web Registry Components information, and then click Install.
    ACWSpreview.jpg 
  9. In the Installation Summary panel, review the BMC Atrium Core – Web Registry Components installation log and then click Done to finish the upgrade.
    ACWSinstallsummary.jpg 
  10. Review the progress of the current session and your overall progress, and then click Next.
    ACWSprogress.jpg 
  11. Review the final installation log and then click Done to exit the installer and end this session. 
  12. Start a new session to upgrade BMC Network Automation.

To upgrade BMC Network Automation

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the remaining options except BMC Network Automation, and then click Next.
    BNAHostInformation.jpg 
  3. Enter the operating system user credentials and passwords for the target host, and then click Next.
  4. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    BNAsummary.jpg 
  5. On the BMC Network Automation Welcome page, click Next.
    BNAwelcome.jpg 
  6. Take a VM snapshot and database backup, and then click Next.
  7. In the OS User Account Information panel, review the settings, and then click Next. 
    BNAos.jpg
  8. In the Database Information panel, review the settings, and then click Next. 
    BNAdb.jpg 
  9. In the Memory and System Options panel, review the settings, and then click Next. 
    BNAmemory.jpg 
  10. In the CSM Integration Information panel, review the integration settings, and then click Next. 
    You can integrate new CSM artifacts as needed. If you select this option, the installer overwrites the existing artifacts during the upgrade. 
    BSAcsmintegration.jpg 
  11. On the Installation Preview panel, review the BMC Network Automation information, and then click Install.
    BNApreview.jpg 
  12. Review the list of upgraded configuration files in the BMC Network Automation upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    BNAconfigfiles.jpg 
  13. In the Installation Summary panel, review the BMC Network Automation installation log and then click Done to finish the upgrade.
    BNAinstallsummary.jpg 
  14. Review the progress of the current session and your overall progress, and then click Next.
    BNAprogressinstallsummary.jpg 
  15. Click Upgrade to Cloud Lifecycle Management 4.1.00 to upgrade the remaining products in one final session.
    Or click Exit the Installation to exit the installer and end the session.

To upgrade Cloud Database Extensions

This session upgrades Cloud Database Extensions, Cloud Platform Manager, and Cloud Portal AR Extensions. You also migrate data for the cloud core components.

  1. Clear all the remaining options except Cloud Database Extensions, and then click Next.
    CloudDBExtHostInformation.jpg 
  2. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    CloudDBExtSummary.jpg 
  3. On the Cloud Database Extensions Welcome page, click Next.
    CloudDBExtwelcome.jpg
  4. Take a VM snapshot and database backup, and then click Next.
  5. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
    CloudDBExtinputs.jpg
  6. On the Installation Preview panel, review the Cloud Database Extensions information, and then click Install.
    CloudDBExtPreview.jpg
  7. In the Installation Summary panel, review the Cloud Database Extensions installation log and then click Done to finish the upgrade.
    CloudDBExtinstallsummary.jpg
  8. Review the progress of the current session and your overall progress, and then click Next.
    CloudDBExtProgress.jpg
  9. Review the installation log and then click Done to end this session. 

Now upgrade Cloud Platform Manager.

To upgrade Cloud Platform Manager

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the remaining options except Cloud Platform Manager, and then click Next.
    PMhostinfo.jpg 
  3. Enter the operating system user credentials and passwords for the target host, and then click Next.
  4. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    PMsummary.jpg 
  5. On the Cloud Platform Manager Welcome page, click Next.
    PMwelcome.jpg 
  6. Take a VM snapshot and database backup, and then click Next.
  7. Enter the Oracle 1.7 JRE path – for example, C:\Program Files\Java\jre7 – and then click Next.
    You can also use the bundled JRE.  
  8. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
    PMinputs.jpg 
  9. 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\. 
  10. 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.  
    PersistenceMgr.jpg 
  11. Review the Core Cloud Service Details, and then click Next.
    CoreCloudDetails.jpg 
  12. On the Resource Manager details panel, enter the BBNA, BLAdmin, BBSA, BLGuest, and  AO Server (by default, admin123) passwords, and then click Next.
    ResourceMgrDetails.jpg
  13. Review the Service Health details, and then click Next. 
    ServiceHealth.jpg 
  14. 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. If you select Yes now, the next panel prompts you for the BMC Database Automation (BDA) Manager host name, user, and password.
    DBaaS.jpg 
  15. If you selected Yes in the Configure BDA for BMC Cloud Lifecycle Management panel, enter the BMC Database Automation details (for example, the host name, user, and password), and then click Next. 
    BDAdetails.jpg 
  16. 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. If you select Yes now, the next panel prompts you for the vCloud server name, administrator, password, and so on.
    vCloud.jpg 
  17. If you selected Yes in the Configure Vmware vCloud Director Provider for BMC Cloud Lifecycle Management panel, enter the vCloud details (for example, the server name, version, administrator user, and password), and then click Next. 
    vCloudDetails.jpg 
  18. On the Installation Preview panel, review the Cloud Platform Manager information, and then click Install.
    PlatformMgrPreview.jpg
  19. Review the list of upgraded configuration files in the Cloud Platform Manager upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    PMconfigfiles.jpg 
  20. In the Installation Summary panel, review the Cloud Platform Manager installation log and then click Done to finish the upgrade.
    PMinstallsummaruy.jpg
  21. Review the progress of the current session and your overall progress, and then click Next.
    PMprogress.jpg
  22. Click Upgrade to Cloud Lifecycle Management 4.1.00 to upgrade Cloud Portal AR Extensions.
    Or click Exit the Installation to exit the installer and end the session.

To upgrade Cloud Portal AR Extensions

  1. On the Host Information for an Upgrade Deployment panel, make sure that Cloud Portal AR Extensions is selected, and then click Next.
    CloudPortalARExthostinformation.jpg 
  2. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
    CloudPortalARExtSummary.jpg 
  3. On the Cloud Portal AR Extensions Welcome page, click Next.
    CloudPortalARExtwelcome.jpg 
  4. Take a VM snapshot and database backup, and then click Next.
  5. Enter the Oracle 1.7 JRE path – for example, C:\Program Files\Java\jre7 – and then click Next.
  6. On the BMC AR System Server & IT Service Mgt Suite user inputs panel, review the settings, and then click Next.
    CloudPortalARExtinputs.jpg 

  7. In the Cloud Vista cross launch panel, select Yes to enable integration between Cloud Vista and BMC ProactiveNet Central Server during the upgrade.
    By default, the No option is selected in the installer. 

    Do not select Yes unless you already installed and upgraded BMC ProactiveNet Central Server.

    CrossLaunch.jpg

  8. If you selected Yes in the Cloud Vista cross launch panel, specify the BMC ProactiveNet Central Server details (for example, host name and port), and then click Next. 
    Only BMC customers who purchased and manually installed standalone BMC ProactiveNet Central Server can integrate BPPM as a brownfield product with BMC Cloud Lifecycle Management. 
    BPPMcentralserver.jpg 
  9. On the Installation Preview panel, review the Cloud Portal AR Extensions information, and then click Install.
    CloudPortalARExtPreview.jpg 
  10. Review the list of upgraded configuration files in the Cloud Portal AR Extensions upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Preparing for upgrade.
    CloudPortalARExtconfigfiles.jpg 
  11. In the Installation Summary panel, review the Cloud Portal AR Extensions installation log and then click Done to finish the upgrade.
    CloudPortalARExtInstallSummary.jpg 

The Cloud Upgrade Migration Welcome panel appears under the Cloud Portal AR Extension node.

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.
    CloudUpgradeMigrationWelcome.jpg 
  2. Take a VM snapshot and database backup, and then click Next.
    CloudUpgradeMigrationSnapshot.jpg 
  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.
    cloudadmincredentials.jpg

  1. On the Cloud Upgrade Migration - Task Inputs panel, enter the full path to the Amazon Web Services (AWS) account information file, and then click Next.
    You should have downloaded the credentials.csv file that contains User Name, Access Key Id, and Secret Access Key from Amazon. Its format should look like the following sample: 

    jstamps IKEAIP4FORD5KJSJS57Q suQ01rEATmoreGritsxYxiSVbreakOFn/1zZenBB

    AWS_credentials.jpg 

  2. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, specify the AR System administrator credentials. 
    ITSMuserinputsdatamigration.jpg 
  3. Click Next.
    The data migration process begins.
  4. When the data migration is successfully finished, review the information, and then click Done. 
    DataMigrationInstallSummary.jpg 
  5. Review the progress of the current session and your overall progress, and then click Next.
    DataMigrationProgress.jpg 
  6. Click Exit the Installation to exit the installer and then click Next to end the session.
  7. In the final Installation Summary panel, review the log and then click Done to exit. 
    FinalUpgradeSummary.jpg 

Where to go from here

  1. When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
  2. Apply the following hotfixes/patches after you install or upgrade version 4.1.00:
    Synchronize-Virtual-Cluster-or-SOI-causes-VMs-to-be-decommissioned—Patch 4 is required. If you do not apply this patch the agent runs out of Java heap memory and thereby results in BMC Cloud Lifecycle Management erroneously decommissioning VMs on that cluster.
    • 000110488—This hotfix provides missing files necessary for using a currency other than USD.
    • 000111195—This hotfix updates field values that are displayed blank for Cloud Platform and Installable Resources in Service Designer and is required for all BMC Cloud Lifecycle Management deployments. QM001858190/QM001876321 in BMC Cloud Lifecycle Management 4.1 Patch 3 fixes this issue. For details, see Known and corrected issues.
    • 000031574—This hotfix applies only if you have BMC Capacity Optimization deployed in your environment.
    • 000107519—This hotfix is required for all BMC Cloud Lifecycle Management deployments.
  3. Perform the post-upgrade configuration tasks.

Related topic

End-to-end process for upgrading Compact Deployment 4.0 to 4.x - In-Place strategy

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*