Upgrading Single VM RDS 3.1 SP1 to BMC Compact Deployment

This topic show you how to upgrade the Single VM RDS Linux 3.1 SP1 deployment to 4.0.  

• • Before you begin
  • To launch the installer
  • To upgrade BMC Server Automation
  • To upgrade Atrium Orchestrator - Configuration Distribution Peer
  • To upgrade BMC AR System Server - Cloud Portal and Database
  • To upgrade BMC Network Automation
  • To upgrade Cloud Extensions & Platform Manager
  • To run data migration after you finish upgrading
  • 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 Upgrade-considerations and 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 Single VM RDS host where you upgrade the products; use a separate VM. You can recover this VM later, after you finish the upgrade.
• Review the known and corrected installation issues to avoid potential problems during upgrade.
  
• Review the operation system and log on accounts in the Single VM RDS documentation.
• 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 downloading.

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

   Success

   You can also use VConsole to launch the installer.

3. On 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.  
   

   Warning

   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 /opt/bmc/Planner.
8. On the Installation Preview panel, review the planner information, and then click Install.
9. On the NSH panel, review the installation location, and then click Next.
   The default location is /opt/bmc/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. 

    Warning

    Note

    The backup registry lists the target hosts and which products were installed on them. The Single VM RDS deployment does not include a registry available to simplify the upgrade process.

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

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 Single VM RDS host name (for example, cloudexpress), 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. Click Next.
    The Select Deployment Type panel is displayed, as shown in the following screenshot.
    

18. Choose Upgrade to Cloud Lifecycle Management 4.0.00, and then click Next.

    Warning

    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. 
     

19. Continue by upgrading BMC Server Automation - App Server & Console.

To upgrade BMC Server Automation

1. In the Host Information for an Upgrade Deployment panel, click Next to start upgrading BMC Server Automation - App Server & Console.   
2. Enter the operating system user credential and password (for example, root/x33+esaC) 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. 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 with later installations.  
    
4. When the deployment confirmation panel appears, review the summary of the host settings.
   
   

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

   Success

   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. On the Welcome page, click Next.
    
7. (optional) If you previously enabled an alternate staging directory, enter it now, and then click Next. 
    
8. Take a VM snapshot and database backup, as prompted by the installer.
   
9. Enter the BMC Server Automation - App Server & Console credentials, and then click Next. 
    
10. On the Installation Preview panel, review the information for  BMC Server Automation - App Server & Console, and then click Install to start the upgrade.
     
11. Click Install to start the upgrade. 
12. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    

13. On the VM where you upgraded BMC Server Automation, manually migrate the BladeLogic application server database data.
    For example:
    
    Use the following data migration instructions from the BMC Server Automation 8.5 documentation portal for Oracle.

     

    Success

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

14. Restart the BladeLogic services that you stopped for the data migration.
15. Return to the installation host and upgrade the BSA Server Automation Console by clicking Next. 
    
16. Take a VM snapshot and database backup, and then click Next. 
     
17. On the Installation Preview panel, review the information for  BMC Server Automation Console, and then click Install to start the upgrade.
     
18. If you see validation warnings, review the information, and then click Next. 
    The warning is benign because the Application Server is being upgraded to the same version.
     
19. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    
20. Return to the installation host and configure the post-installation upgrade by clicking Next. 
    
21. Take a VM snapshot and database backup, and then click Next. 
     
22. Enter the RBACAdmin and BLAdmin passwords (for example, clmAdm1n), and then click Next. 
     
23. In the BMC Server Automation User Information panel, enter and confirm the BLGuest password, and then click Next. 
     
24. On the Installation Preview panel, review the information for post-install configuration, and then click Install to start the upgrade.
     
25. In the Installation Summary panel, review the installation log and then click Done to finish the upgrade.
    
26. Manually upgrade the Virtual Center (VC) agent.
27. 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.
28. Continue by upgrading the Atrium Orchestrator - Configuration Distribution Peer application.

To upgrade Atrium Orchestrator - Configuration Distribution Peer

In this session, you upgrade BMC Cloud Lifecycle Management Content and the BMC Server Automation Console.

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. 
4. In the Repository Communication Settings panel, enter the repository password (by default, clmAdm1n), and then click Next.
5. On the Installation Preview panel, review the information for BMC Cloud Lifecycle Management Content, and then click Install.
    
6. Review the validation warnings, and then click Next. 
7. In the Installation Summary panel, review the BMC Cloud Lifeycle Management Content installation log and then click Done to finish the upgrade.
    
8. Manually activate the BMC Atrium Orchestrator adapters.
   
9. Continue by upgrading BMC AR System Server - Cloud Portal and Database.
   

To upgrade BMC AR System Server - Cloud Portal and Database

In this session, you upgrade BMC AR System Server - Cloud Portal and Database.

1.  On the Welcome page, click Next.
   
2. Take a VM snapshot and database backup, and then click Next.
     
3. In the Prerequisite Validation panel, review the instructions (for example, stop the rpcbind service on the server, and so on). When you finish, click Next to continue. 
    
4. Enter the Oracle 1.7 JRE directory (for example, /usr/java/jre1.7.0), and then click Next.
5. Review the portmapper information, and then click Next.
    
6. Review the AR System Server Database Platform Information (/u01/app/oracle/product/11.2.0/xe), and then click Next. 
7. On the User and Database Information panel, enter and confirm the ARAdmin password, and then click Next.
   By default, the ARAdmin password is clmAdm1n.
    
8. On the AR System Server information panel, enter and confirm the AR Server password (by default, clmAdm1n), and then click Next.
    
9. On the Installation Preview panel, review the BMC AR System Server - Cloud Portal and Database information, and then click Install.
    
10. Review the validation warnings, and then click Next. 
    These warnings are information-only and therefore benign.  
11. In the License Information panel, enter the existing AR Server License Key that is used with the BMC Atrium Core CMDB, and then click Next.
    Do not enter a new license key. 
     
12. When you are prompted by the installer that the AR Server is successfully licensed, click Next to continue.
13. In the Installation Summary panel, review the AR Server installation log and then click Done to finish the upgrade.
    
    Next you upgrade BMC Atrium Core. 
14. On the BMC Atrium Core Welcome page, click Next.
     
15. Take a VM snapshot and database backup, and then click Next.
     
16. On the AR System Server information panel, review the settings, enter the AR Server password (by default, clmAdm1n), and then click Next.
     
17. On the Web Services Registry Information panel, review the settings, enter the admin password (by default, clmAdm1n), and then click Next.
     
18. On the Installation Preview panel, review the BMC Atrium Core information, and then click Install.
     
19. In the Installation Summary panel, review the BMC Atrium Core installation log and then click Done to finish the upgrade.
    
    Next you upgrade BMC Service Request Management.  
20. On the BMC Service Request Management Welcome page, click Next.
     
21. Take a VM snapshot and database backup, and then click Next.
     
22. In the AR System Overlays Feature panel, review the recommendations, and then click Next.
     
23. On the BMC Remedy AR System Server User Inputs panel, review the settings, enter the password, and then click Next.
     
24. On the Installation Preview panel, review the Service Request Management information, and then click Install.
     
25. In the Installation Summary panel, review the Service Request Management installation log and then click Done to finish the upgrade.
    The warnings displayed in panel are benign and you can safely continue upgrading. 
    
    Next you configure AR System post-installation on the BMC AR System Server - Cloud Portal and Database. 
26. On the AR Post Install Configuration Welcome page, click Next.
     
27. Take a VM snapshot and database backup, and then click Next.
     
28. On the BMC Remedy AR System Server User Inputs panel, review the settings, enter the password (by default, clmAdm1n), and then click Next.
     
29. On the Installation Preview panel, review the AR Post Install Configuration information, and then click Install.
    
30. In the Installation Summary panel, review the AR Post Install Configuration installation log and then click Done to finish the upgrade. 
    
    
31. Continue by upgrading BMC Network Automation.

To upgrade BMC Network Automation

During an upgrade, you should not need to update the BMC Network Automation settings; simply review them. 

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, de-select the Import CSM Artifacts option unless you are absolutely sure that you want to overwrite the existing BNA content, and then click Next. 
   This default setting overwrites existing artifacts with new pods, container blueprints, and templates. De-selecting the  Import CSM Artifacts option 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, enter the password (by default, clmAdm1n), 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. 
    

   Warning

   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.
    
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, clmAdm1n) 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 select 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. In the Installation Summary panel, review the Cloud Extensions & Platform Manager installation log and then click Done to finish the upgrade.
     
15. Continue by running the data migration.

To run data migration after you finish upgrading

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

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 CloudExpress user, but not Demo or appadmin), and then click Next.
   

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.
   
   

   1. Create a CSV file with the following information – Account Name, Access Key, and Secret Access Key.
      For example:

      jstamps@calbro.com IKEAIP4FORD5KJSJS57Q suQ01rEATmoreGritsxYxiSVbreakOFn/1zZenBB
      
   2. For multiple AWS Accounts, add new row entries to the CSV file.
   3. Save the CSV locally on the installer host. 
2. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, specify the AR System administrator credentials. 
    
3. Click Next.
   The data migration process begins.

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.