×
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
 
 
  •  
BMC Cloud Lifecycle Management 4.5 ... Upgrading In-Place upgrade

End-to-end upgrade process - 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 in the Windows environment from 3.1 to 4.5 or later. But you can use the procedure explained in this section to upgrade 3.x or 4.x as well. 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

Since this topic documents a Windows/SQL Server upgrade, the procedures and screenshots 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.

Except when you upgrade BMC AR System Server & IT Service Mgt. Suite - Primary (Enterprise-AR) and BMC AR System Server - Cloud Database Primary (Cloud-AR), 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

  • If you are running an environment with two AR System servers (Enterprise-AR and Cloud-AR), use the 2AR1AR utility to merge the servers into one AR System server before you start the upgrade. For more information, see Merging two AR System servers into one AR System server.
  • 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 the same VM to install earlier versions of BMC Cloud Lifecycle Management, perform the following tasks before you run the 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 and BMC ProactiveNet products is not supported in version 4.5 or later and cannot be upgraded with the install planner. 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 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 Reducing installation time by installing products in parallel.

  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.

  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.

  11. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance.
  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.


    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.
    Since this example is based on the Small Deployment template, select No (I have an Enterprise-AR and a Cloud-AR server), and then click Next. If you had Compact Deployment or RDS stacks, you would select Yes, I have only one BMC AR System server.
  15. In the Select Deployment Template panel, select the template that matches your requirements (for example, Small Deployment), and click Next.
  16. In the Deployment Tier Selection panel, select Control Tier to install the products in that tier, and click Next.
    The options are:
    • Control Tier
    • Workload Tier
    • Both 
       
    The default is Both, but this example only upgrades products in the Control Tier. The Host Information for a Small Deployment panel appears for the Control Tier.

  17. 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, only the product hosts currently used in your environment. 

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

  18. When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel.

    Note

    After integration, you can review the product versions before and after the upgrade.

  19. Click Next.

  20. In the Select Deployment Type panel, select Upgrade to Cloud Lifecycle Management 4.5.00, and click Next.
    All product hosts that you integrated with your BMC Cloud Lifecycle Management solution by running the installer are 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. 
     

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.
  3. When the deployment confirmation panel appears, review the summary of the host settings.

  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.

  5. Click Next.
    The Upgrade Progress panel is displayed and 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.

  6. Take a VM snapshot and database backup, as prompted by the installer.
  7. If these services are running (for example, because you are in a HA environment), manually stop the MAS, PXE Server, and Advance Repeater services, and then click Next.
  8. At the prompts, review the installation inputs, and then click Next.
    Use your planning spreadsheet to guide you through the upgrade.
  9. In the Installation Preview panel, review the information and then click Install to start the upgrade.
  10. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.

  11. Click Next to upgrade the BSA Server Automation Console.

  12. Take a VM snapshot and database backup.
  13. In the Installation Preview panel, review the features to be installed and then click Install to start the upgrade.
  14. If you are prompted to configure your machine to run in unrestricted mode, manually perform the task and then click Next. 
  15. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
  16. Click Next to configure the post-installation upgrade.
  17. Take a VM snapshot and database backup.
  18. Enter the RBACAdmin and BLAdmin passwords, and then click Next.
  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 progress of the current session and your overall progress, and then click Next.
  23. Review the installation log and then click Done to end this session. 
  24. 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.
  3. If prompted, 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.
  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.
  6. Take a VM snapshot and database backup, and then click Next.
  7. Review the Access Manager Communication Settings, and then click Next.
  8. On the Installation Preview panel, review the Access Manager and Repository settings, and then click Install.
  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.
  10. In the Installation Summary panel, review the Access Manager and Repository installation log and then click Done to finish the upgrade.
  11. On the BMC Atrium Orchestrator CDP Welcome panel, click Next.
  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.
  15. Review the CDP peer settings, and then click Next.
  16. Review the repository communication settings, and then click Next.
  17. On the Installation Preview panel, review the information for BMC Atrium Orchestrator CDP, and then click Install.
  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.
  19. In the Installation Summary panel, review the CDP installation log and then click Done to finish the upgrade.
  20. On the BMC Cloud Lifecycle Management Content Welcome page, click Next.
  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.
  24. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
  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.
  27. On the BMC Server Automation Console Welcome page, click Next.
  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.
  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.
  32. On the Atrium Orchestrator Post Install Configuration Welcome page, click Next.
  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.
  34. In the Installation Summary panel, review the Atrium Orchestrator Post Install Configuration installation log and then click Done to finish the upgrade.
  35. Review the progress of the current session and your overall progress, and then click Next.
  36. Review the installation log and then click Done to end this session.
  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.

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

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel. Make sure that you select that you use one or more AR System servers in your environment.
  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.
  3. If prompted, 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.
  5. On the Enterprise-AR Welcome page, click Next.
  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. 
  7. Review the Oracle 1.7 JRE settings, and then click Next.
  8. Review the portmapper information, and then click Next.
  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#.
  10. On the AR System Server information panel, enter the AR Server password, and then click Next.
  11. On the Installation Preview panel, review the Enterprise-AR Server information, and then click Install.
  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.
  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.
  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.
  17. On the BMC Atrium Core Welcome page, click Next.
  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.
  20. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
  21. 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; in the BMC IDD Lab environment, the BMC Atrium Core upgrade took about 2 hours. 
     
  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.
  23. 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. 
  24. On the BMC Atrium Integrator Welcome page, click Next.
  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.
  27. On the Installation Preview panel, review the BMC Atrium Integrator information, and then click Install.
  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.
  29. In the Installation Summary panel, review the BMC Atrium Integrator installation log and then click Done to finish the upgrade.

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

  31. Take a VM snapshot and database backup, and then click Next.
  32. 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.
  33. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
  34. 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.

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

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

  37. On the AR Post Install Configuration Welcome page, click Next.
  38. Take a VM snapshot and database backup, and then click Next.
  39. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
  40. 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.
  41. On the Cloud Database Primary Welcome page, click Next.
  42. Take a VM snapshot and database backup, and then click Next.
  43. Review the Oracle 1.7 JRE settings (for example, C:\Program Files\Java\jre7), and then click Next.
  44. Review the portmapper information, and then click Next.
  45. 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#.
  46. On the AR System Server Administrator information panel, review the settings, and then click Next.
  47. On the Installation Preview panel, review the Cloud Database Primary information, and then click Install.
  48. Review the validation warnings, and then click Next.
  49. In the License Information panel, enter the AR Server License Key, and then click Next.
  50. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue.
  51. 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.
  52. 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.
  53. On the BMC Atrium Core Welcome page, click Next.
  54. Take a VM snapshot and database backup, and then click Next.
  55. On the AR System Server information panel, review the settings, and then click Next.
  56. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
  57. 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.
  58. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade.
  59. On the AR Post Install Configuration Welcome page, click Next.
  60. Take a VM snapshot and database backup, and then click Next.
  61. On the BMC Remedy AR System Server User Inputs panel, review the settings, and then click Next.
  62. 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.
  63. 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.
  64. On the DSO Mapping Welcome page for the Enterprise-AR server, click Next.
  65. Take a VM snapshot and database backup, and then click Next.
  66. On the BMC Remedy AR System Server User Inputs panel, review the settings on the Enterprise-AR server, and then click Next.
  67. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next.
  68. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.
  69. 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.
  70. 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.
  71. On the DSO Mapping Welcome page for the Cloud-AR server, click Next.
  72. Take a VM snapshot and database backup, and then click Next.
  73. On the BMC Remedy AR System Server User Inputs panel, review the settings on the Cloud-AR server, and then click Next.
  74. On the BMC Atrium Core DSO Information panel, enter the DSO password, review the remaining settings, and then click Next.
  75. On the Atrium DSO Mapping Summary panel, review the information, and then click Install.
  76. 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.
  77. In the next Atrium DSO Mapping Summary panel, review the Atrium DSO Mapping Summary installation log and then click Done to finish the upgrade.
  78. 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.
  79. Review the final installation log and then exit the installer and end this session. 
  80. 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.
  3. If prompted, 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.
  5. On the BMC Mid-Tier Welcome page, click Next.
  6. Take a VM snapshot and database backup, and then click Next.
  7. Review the Oracle 1.7 JRE settings (for example, C:\Program Files\Java\jre7), and then click Next.
  8. On the Installation Preview panel, review the information, and then click Install.
  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.
  11. Review the progress of the current session and your overall progress, and then click Next.
  12. Review the installation summary log and then click Done to exist the installer and end the session.

To upgrade BMC Atrium Core – Web Registry Components

  1. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the remaining options except Atrium Core – Web Registry Components, and then click Next.
  3. If prompted, 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.
  5. On the Atrium Core - Web Registry Components Welcome page, click Next.
  6. Take a VM snapshot and database backup, and then click Next.
  7. On the BMC AR System Server & IT Service Mgt Suite - Primary Information panel, review the settings, and then click Next.
  8. On the Web Service Registry Information panel, enter the admin password (for example, admin), review the other settings, and then click Next.
  9. On the Installation Preview panel, review the BMC Atrium Core – Web Registry Components information, and then click Install.
  10. In the Installation Summary panel, review the BMC Atrium Core – Web Registry Components installation log and then click Done to finish the upgrade.
  11. Review the progress of the current session and your overall progress, and then click Next.
  12. Review the final installation log and then click Done to exit the installer and end this session. 
  13. 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.
  3. If prompted, 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.
  5. On the BMC Network Automation Welcome page, click Next.
  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.
  8. In the Web Server Information panel, review the port values to use with BNA, and then click Next.
  9. In the Database Information panel, review the settings, and then click Next.
  10. In the Memory and System Options panel, review the settings, and then click Next.

  11. 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! 


  12. On the Installation Preview panel, review the BMC Network Automation information, and then click Install.
  13. 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.
  14. In the Installation Summary panel, review the BMC Network Automation installation log and then click Done to finish the upgrade.
  15. Review the progress of the current session and your overall progress, and then click Next.
  16. Review the install summary log and then click Done 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. Start the installer and continue to the Host Information for an Upgrade Deployment panel.
  2. Clear all the remaining options except Cloud Database Extensions, and then click Next.
  3. When the deployment confirmation panel appears, review the summary of the host settings, and then click Next.
  4. On the Cloud Database Extensions Welcome page, click Next.
  5. Take a VM snapshot and database backup, and then click Next.
  6. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
  7. On the Installation Preview panel, review the Cloud Database Extensions information, and then click Install.
  8. In the Installation Summary panel, review the Cloud Database Extensions installation log and then click Done to finish the upgrade.
  9. Review the progress of the current session and your overall progress, and then click Next.
  10. Review the installation log and then click Done to end this session.  
  11. Go to the next procedure, and 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.
  3. If prompted, 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.
  5. On the Cloud Platform Manager Welcome page, click Next.
  6. Take a VM snapshot and database backup, and then click Next.
  7. 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.7 (for version 4.5). 
  8. On the BMC AR System Server - Cloud Database user inputs panel, review the settings, and then click Next.
  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\configuration. 
  10. Review the OSGi port settings, and then click Next.
  11. On the Deploy UI on Platform Manager panel, select Yes if you want to deploy the new UI on the Platform Manager host, and then click Next. 
    The default option is No. 

  12. 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.
  13. 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. 
  14. Review the Core Cloud Services Details, and then click Next.
  15. On the Resource Manager details panel, enter the BBNA, BLAdmin, BBSA, BLGuest, and  AO Server (by default, admin123) passwords, and then click Next.
  16. Review the SMTP Configuration details, and then click Next.
  17. (Optional) 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.
  18. 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. 
  19. 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.
  20. 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.
  21. On the Installation Preview panel, review the Cloud Platform Manager information, and then click Install.
  22. 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.
  23. In the Installation Summary panel, review the Cloud Platform Manager installation log and then click Done to finish the upgrade.
  24. Review the progress of the current session and your overall progress, and then click Next.
  25. Review the installation summary log and then click Done to exit the installer and end the session.

To upgrade Cloud Portal AR Extensions

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

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

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

  11. 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. 
    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.  
  8. Review the progress of the current session and your overall progress, and then click Next. 
  9. Click Exit the Installation to exit the installer and then click Next to end the session.
    Or click Modify Existing Deployment to install additional products or to upsize the deployment type (for example, from Small to Medium). For more information, see Changing or upsizing deployment types.
  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. When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
  2. MultiExcerpt named HotfixKA46 was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro
  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

Was this page helpful? Yes No Submitting... Thank you
Last modified by Lisa Greene on Mar 06, 2017
4_5 4_6

Comments

Log in or register to comment.

In-Place upgrade
Migrating data for the cloud core components
© Copyright 2023 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.