Upgrade considerations

This section lists items for you to take into consideration as you plan your upgrade to this version.

• • Upgrading with HTTP/SSL
  • Using individual TrueSight Orchestration content installer causes upgrade to fail
  • Compact deployment upgrade considerations
  • TrueSight Server Automation upgrade considerations
  • Upgrade considerations for BMC Cloud Lifecycle Management version 4.6.07 or later
    • Preserving customization after upgrade
  • Backward compatibility of products in Zone 1 and Zone 2
  • Where to go from here

Flushing cache after upgrades

When you finish upgrading, inform your user community to flush the cache on their browsers. Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers. 

Upgrading with HTTP/SSL

If you plan to upgrade using HTTP/SSL with third-party SSL certificates, you have the following options.

• Import RootCA.crt into Planner\Disk1\files\jre\lib\security\cacerts:

  Planner\Disk1\files\jre\bin\keytool.exe -import -alias root -keystore
  Planner\Disk1\files\jre\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt

• Copy the existing keystore to a different location. During the upgrade (for example, Platform Manager or CLM Self Check Monitor), select the Use Existing Certificate option and then provide the path to the keystore location along with the password details. 
  For example:
   

For more information, see Using-CLM-applications-with-third-party-Certification-Authority-certificates.

Using individual TrueSight Orchestration content installer causes upgrade to fail

Note that the installation of TrueSight Orchestration content (not part of BMC Cloud Lifecycle Management stack) using the individual installer corrupts the AMREPO PlatformInstalledConfiguration.xml and ProductRegistry.xml files. This causes the upgrade installation to fail. Contact support for more information (reference defect QM001765785).

Compact deployment upgrade considerations

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

TrueSight Server Automation upgrade considerations

To ensure that you do not lose valuable data (for example, MaxHeapSize or any other customized settings) after the upgrade, you must back up the C:\Program Files\BMC Software\BladeLogic\RSCD\daal (Windows) or /opt/bmc/bladeLogic/rscd/daal (Linux) folders. You will use this information after you finish the upgrade to manually configure the settings. 

Upgrade considerations for BMC Cloud Lifecycle Management version 4.6.07 or later

If you are upgrading from 4.6.07 or later, review the following considerations for your upgrade strategy. 

Perform the following steps:

1. In ar.conf/ar.cfg, verify whether the following RPC queues are registered:
   • 390690
   • 390691
   • 390696
2. (Optional) If the preceding RPC queues are not registered, register them in ar.conf/ar.cfg.
3. In pluginsvr_config.xml, set the RPC queue value for <override_ar_system_private_rpc_socket> to 390690. Note that you must update three occurrences with this value.
4. In cloudservices.json, set the RPC queue (rpc_queue) value for Database(AR) RPC Queue Number to 390696.
5. Restart the AR System server and Platform Manager services.

Inform your user community to flush the cache on their browsers. 
 Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers.

_{Back to top}

Preserving customization after upgrade

If you made extensive customizations to your production environment and want to preserve them, you must plan the upgrade accordingly. During upgrade, some but not all production configuration files are preserved.   

After you upgrade the AR System Server on both Enterprise-AR and Cloud-AR, see Creating-overlays-with-BPCU-for-existing-customizations to create overlays before you continue the upgrade. 

Finally, you might have customized one or several components in the solution to suit your business needs (for example, the Network Automation API). You must decide whether to replace your customizations or port them.

Backward compatibility of products in Zone 1 and Zone 2

BMC Cloud Lifecycle Management component products are categorized as backward compatible (Zone 1) or non-backward compatible (Zone 2). This topic explains your options when you decide to upgrade to 4.x. 

You must upgrade the products in the solution based on their backward compatibility. This means that when you upgrade a product to the latest version in the solution, that product will continue to be compatible with other products of the older version. For example, if you upgrade TrueSight Server Automation (formerly called BMC Server Automation) to version 8.5.00, it will continue to work with BMC Cloud Lifecycle Management 4.x. The upgraded TrueSight Server Automation product would not have any impact on the solution production environment.

Where to go from here

Upgrade-prerequisites

_{Back to top}