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

This topic show you how to upgrade 4.0 Compact Deployment to 4.x.  

• • Before you begin
  • To launch the installer
  • To upgrade BMC Server Automation
  • To upgrade BMC Atrium Orchestrator Access Manager and Repository
  • To upgrade Atrium Orchestrator - Configuration Distribution Peer
  • To upgrade BMC Cloud Lifecycle Management Content (AO)
  • To upgrade Atrium Orchestrator Post Install Configuration
  • To upgrade BMC Network Automation
  • To upgrade Cloud Extensions & Platform Manager
  • Where to go from here

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

Before you begin

• Review Preparing-for-upgrade.
• 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. 
• Do not run the installer on the Compact Deployment host where you upgrade the products; use a separate VM. You can recover this VM later, after you finish the upgrade.
• 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.
• Review the known and corrected installation issues to avoid potential problems during upgrade.
  
• Accept the default values in the installer unless you have a good reason to change them.
• On-board at least one tenant in BMC Cloud Lifecycle Management before you start upgrading. 

To launch the installer

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

1. • On Linux, launch the setup.sh 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.

2. On the Welcome page, click Next. 
3. Review the license agreement, click I agree to the terms of the license agreement, and then click Next.
4. On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the upgrade. 

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

    

6. 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 /opt/bmc/Planner (Linux) or C:\Program Files\BMC Software\Planner (Windows). 
7. On the Installation Preview panel, review the planner information, and then click Install.
8. On the NSH panel, review the installation location, and then click Next.
   The default location is /opt/bmc/NSH (Linux) or C:\Program Files\BMC Software\NSH (Windows).
9. In the Select Installation Type panel, select Upgrade and then click Next.
    
10. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance. 
     
11. Click I agree to the terms of the disclaimer, and then click Next. 

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

    Note

    The backup registry lists the target hosts and which products were installed on them. 

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

13. In the BMC AR System Configuration panel, the installer prompts you if you use only one AR System server in your environment.
    Select Yes (I have only one BMC AR System server), and then click Next.
    
    
14. In the Select Deployment Template panel, select Compact Deployment. 
    For more information, see deployment template for other types to implement.
    
15. Click Next.
    The Host Information for Compact Deployment panel appears. 
16. Enter the Compact Deployment host name, and then click Next. 
    The installer validates the host, to ensure a successful integration, and begins integrating the products. When the installer finishes, review the products, versions, and hosts listed in the Integration Summary panel. 
     
17. When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel.
     
18. Click Next.
    The Select Deployment Type panel is displayed, as shown in the following screenshot.
    

19. Choose Upgrade to Cloud Lifecycle Management 4.1.00, and then click Next.

    Note

    Make sure that all products are selected for upgrade. Upgrading one product at a time is not supported. 

    If the host name 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 must 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. 
     

20. Enter the operating system credentials for your VM and then click Next.
    The installer upgrades the RSCD Agent. 
     
21. In the summary panel, review the host information, and then click Next. 
     

Now upgrade BMC Server Automation - App Server & Console.

To upgrade BMC Server Automation

Make sure that the BMC Server Automation Console is closed before you start the upgrade. 

1. When the Upgrade Progress panel is displayed, review 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.

   

2. On the BMC Server Automation - App Server & Console Welcome page, click Next. 
3. Take a VM snapshot and database backup, as prompted by the installer.
    
4. Review the BMC Server Automation - App Server & Console credentials, and then click Next. 
   
5. On the Installation Preview panel, review the information for  BMC Server Automation - App Server & Console, and then click Install to start the upgrade.
   
6. Click Install to start the upgrade. 
7. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
   

8. On the VM where you upgraded BMC Server Automation, manually migrate the SQL update scripts and then start the BladeLogic Application Server. 

   Note

   When you upgrade 4.0 to 4.x, you do not need to run the entire database migration; you only need to run the SQL update. For instructions, see To run database migration and SQL update.

9. Return to the installation host and upgrade the BSA Server Automation Console by clicking Next. 
   
10. Take a VM snapshot and database backup, and then click Next. 
    
11. On the Installation Preview panel, review the information for  BMC Server Automation Console, and then click Install to start the upgrade.
    
12. If you see validation warnings, review the information, and then click Next. 
    These warnings are benign and you can safely ignore them.
     
13. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    
14. In the BMC Server Automation Post Install Configuration Welcome panel, configure the post-installation upgrade by clicking Next. 
    
15. Take a VM snapshot and database backup, and then click Next. 
    
16. Enter the RBACAdmin and BLAdmin passwords, and then click Next. 
    
17. In the BMC Server Automation User Information panel, enter and confirm the BLGuest password, and then click Next. 
    
18. On the Installation Preview panel, review the information for post-install configuration, and then click Install to start the upgrade.
    
19. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    
20. Manually upgrade the Virtual Center (VC) agent.
21. 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.
22. Continue by upgrading the Atrium Orchestrator - Configuration Distribution Peer application.

To upgrade BMC Atrium Orchestrator Access Manager and Repository

In this session, you upgrade BMC Atrium Orchestrator Access Manager and Repository (AMREPO).

1. On the AMREPO Welcome page, click Next.
   If you are using a HA environment, stop the CDP service on the BMC Atrium Orchestrator HA host before you continue with the AMREPO upgrade.
   
2. Take a VM snapshot and database backup, and then click Next.
   
3. In the Access Manager Communication Settings panel, review the port details, and then click Next.
    
4. On the Installation Preview panel, review the AMREPO information, and then click Install.
   
5. Review the list of upgraded configuration files in the AMREPO upgrade, and then click Next. 
   These files are important if you want to preserve customizations. For a complete list, see Prerequisites for upgrade.
    
6. In the Installation Summary panel, review the AMREPO installation log and then click Done to finish the upgrade.
   
7. Manually activate the BMC Atrium Orchestrator adapters.
8. Continue by upgrading BMC Atrium Orchestrator - Configuration Distribution Peer (CDP).

To upgrade Atrium Orchestrator - Configuration Distribution Peer

In this session, you upgrade BMC Atrium Orchestrator CDP.

1. On the CDP Welcome page, click Next.
   
   
2. Take a VM snapshot and database backup, and then click Next.
    
3. Review the remote installation directory, and then click Next.
   The default is /u01/bmc/ao-platform/cdp (Linux) or C:\Program Files\BMC Software\AO-Platform\CDP (Windows).
4. In the Configuration Distribution Peer (CDP) Web Server settings panel, review the HTTP port (28080) and Shutdown port (28005), and then click Next. 
    
5. In the Configuration Distribution Peer Settings panel, review the information, and then click Next.
    
6. In the Repository Communication Settings panel, review the port details, and then click Next.
   
7. On the Installation Preview panel, review the CDP information, and then click Install.
   
8. 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 Prerequisites for upgrade.
   
9. In the Installation Summary panel, review the CDP installation log and then click Done to finish the upgrade.
   
10. Continue by upgrading BMC Cloud Lifecycle Management Content.
    

To upgrade BMC Cloud Lifecycle Management Content (AO)

In this session, you upgrade BMC Cloud Lifecycle Management Content.

1. On the Welcome page, click Next.
   
2. Take a VM snapshot and database backup, and then click Next.
   
3. Review the remote installation directory, and then click Next.
   The default is /u01/bmc/ao-content (Linux) or C:\Program Files\BMC Software\AO-Content (Windows).
4. In the Repository Communication Settings panel, enter the repository password (by default, admin123), and then click Next.
   
5. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
   
6. Review the validation warnings, and then click Next. 
   These warnings are benign and you can safely ignore them. 
    
7. In the Installation Summary panel, review the BMC Cloud Lifeycle Management Content installation log and then click Done to finish the upgrade.
   
8. Continue by upgrading Atrium Orchestrator Post Install Configuration.

To upgrade Atrium Orchestrator Post Install Configuration

In this session, you upgrade Atrium Orchestrator Post Install Configuration.

1. On the Atrium Orchestrator Post Install Configuration Welcome page, click Next.
    
2. 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. 
   
3. In the Installation Summary panel, review the Atrium Orchestrator Post Install Configuration installation log and then click Done to finish the upgrade.
    
4. Manually activate the BMC Atrium Orchestrator adapters.
5. Start a new session to upgrade BMC Network Automation.

To upgrade BMC Network Automation

During an upgrade, you should not need to update most of the BMC Network Automation settings; simply review them. But you must decide whether you want to overwrite the existing BNA content or not. 

1. On the 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 Database Information panel, review the settings, and then click Next. 
    
5. In the Memory and System Options panel, review the settings, and then click Next. 
    
6. In the CSM Integration Information panel, select the Import CSM Artifacts option if you are absolutely sure that you want to overwrite the existing BNA content, and then click Next. 
   This setting overwrites existing artifacts with new pods, container blueprints, and templates. By default, the Import CSM Artifacts option is not selected and lets you preserve your customized blueprints and templates until post-migration. 
    
7. On the Installation Preview panel, review the BMC Network Automation information, and then click Install.
    
8. In the Installation Summary panel, review the BMC Network Automation installation log and then click Done to finish the upgrade.
    
9.  Continue by upgrading Cloud Extensions & Platform Manager. 

To upgrade Cloud Extensions & Platform Manager

1.  On the Cloud Extensions & Platform Manager Welcome page, click Next.
   
2. Take a VM snapshot and database backup, and then click Next.
    
3. On the Java Information panel, enter the Oracle 1.7 JRE path (for example, /usr/java/jre1.7.0), and then click Next. 
   You can also use the bundled JRE (selected by default). 
    
4. On the BMC AR System Server - Cloud Database 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 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. BMC customers who purchased and manually installed standalone BMC ProactiveNet Central Server can integrate BPPM as a brownfield product with BMC Cloud Lifecycle Management.

   

6. On the Platform Manager Configuration Directory Information panel, review the path, and then click Next. 
   The default path is /u01/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration (Linux) or C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\configuration (Windows).
    
7. 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.  
    
8. Review the Core Cloud Service Details, and then click Next.
    
9. On the Resource Manager details panel, enter the BBNA, BLAdmin, BBSA, BLGuest, and AO Server (by default, admin123) passwords, and then click Next.
    
10. Review the Service Health details, and then click Next. 
     
11. 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 click Yes now, the next panel prompts you for the BMC Database Automation (BDA) Manager host name, user, and password.
     
12. 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.
     
13. On the Installation Preview panel, review the Cloud Extensions & Platform Manager information, and then click Install.
     
14. Review the list of upgraded configuration files in the Cloud Extensions & Platform Manager upgrade, and then click Next. 
    These files are important if you want to preserve customizations. For a complete list, see Prerequisites for upgrade.
     
15. In the Installation Summary panel, review the Cloud Extensions & Platform Manager installation log and then click Done to finish the upgrade.
     
16. Review the installation summary, and then click Next.
     
17. Click Exit the Installation to close the installer and exit the program, and then click Next. 
     
18. On the Installation Summary panel, review the installation log, and then click Done to exit the installer. 
    You have successfully upgraded the Compact Deployment stack. 
    
    
    

Where to go from here

1. When you finish upgrading all the BMC Cloud Lifecycle Management products, verify that the upgrade was successful.
2. Perform the post-upgrade configuration tasks.