Unsupported content


This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.


This topic contains information about fixes and updates in patches, as well as instructions to download and install a patch.


For information about issues corrected in these patches, see Known and corrected issues.

To create a PDF of the appropriate patch release notes, see PDFs.

Updates in the latest

Patch 3 for BMC Cloud Lifecycle Management 4.5.00 ( is the latest cumulative patch that includes the fixes of the earlier patch.

To locate any update for a particular patch, perform any of the following actions:

  • Select a patch number from the Available in list to filter the table by patch version numbers.
  • Type a character string in one or more of the boxes to filter the list of updates.  
  • Click any column heading to sort this table or change sort direction.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

UpdateDescriptionAvailable in
Access attributesTo allow a greater level of control over compute container auto start and stop actions when applying TRO options, which need the server to be stopped, startServerAfterConfigChange and stopServerAfterConfigChange, two new attributes are added to the Workload Manager (WLM) provider.
  • To enable the cloud administrator to acquire and release NAT addresses of a server for a specific service, two new commands, ipaddress-create and ipaddress-delete have been added.
  • To enable reuse of load balancer pools in different network containers, the lbpool-delete command has been modified to include loadbalancer and environment arguments. Also, lbpool-name, which is deprecated in this patch has been renamed to lbpool.
  • To enable the cloud administrator to restart one or more servers in the specified service, two new commands, service-restart and server-restart have been added.
  • To create a service by specifying the user/password in a template, the service-create command has been modified to include the usetemplatecredentials argument.
  • To stop a server or service forcefully, the service-stop and server-stop commands have been modified to include the force argument.
  • To support the Resize Disk TRO action via an SDK command, the service-update-option command has been modified to include a new disk argument.

For details of all the changes in the SDK, see Summary of changes to the CLM Python SDK.

Ability to modify description of service offering instances

As an end user or a cloud administrator, you can edit the description of a service offering instance from the BMC Cloud Lifecycle Management – My Cloud Services Console by using the operator action, Modify Description. For more information, see Modifying the description of service offering instances in the legacy console .
Add Server TRO action support for vCloud providerStarting with 4.5.00 patch 3, you can add a server to an existing service by using the Add Server Post-Deployment action of the vCloud provider.
Support for IBM shared storage pools

Starting with 4.5.00 patch 2, IBM shared storage pools are supported. To support this optional feature, apply the BMC Server Automation 8.6.01 hotfix from ftp://ftp.bmc.com/pub/BBSA8601_HF/8.6.Sp1_Hotfix.zip. Contact BMC Support to apply the hotfix.

For details, see Configuring shared memory, resources, and NPIV.

vCloud provider

  • vApp networks
  • Tags
  • Custom host name registration support

This patch includes the following enhancements for the VMWare vCloud provider:

  • The network selection logic has been modified to allow provisioning a vApp template that includes a vApp network. For details, see Provisioning VMs on VMware vCenter using Quick Start. 
  • You can now tag a resource set or a functional component of a vCloud blueprint.
  • You can use a custom host name advisor for vCloud VMs.

Changes to the API

A new API has been added to create an organization.

Support for new AWS instance types

Starting with this patch, M4, C4, and D2 instance types are supported. For more information, see Overview of support for Amazon Web Services.
Customizing a maximum quantityYou can customize set a maximum quantity that users can request for a particular service. The default is 100. See Customizing the Catalog service details page.

Downloading the patch

For download instructions, see, Downloading the installation files.

Supported upgrade paths

To install BMC Cloud Lifecycle Management version, you must first install 4.5.00. 

Preparing to install the patch 

Before installing the patch, ensure that the following conditions are met:

  1. If you are using any of the earlier versions, upgrade to BMC Cloud Lifecycle Management version 4.5.
  2. Ensure that the supported products are at the latest service pack or patch level. 
    For more information about the supported product versions, see Component BMC product service pack and patch levels.
  3. Close any open session of BMC Remedy Developer Studio before running the installer.
  4. If you have changed the administrator user password for the enterprise AR System and cloud AR System after the last time you installed BMC Cloud Lifecycle Management, you must ensure that the passwords match the installation configuration file. If the passwords do not match, the installation fails.

    1. Generate an encrypted password: 
      1. On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities.
      2. Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
      3. Click Encrypt.
      4. In the Password and Confirm Password fields, enter the new password.
      5. Click Encrypt.
      6. Copy the new encrypted password.
    2. Update the encrypted password in the installation configuration file on the enterprise AR System: 
      1. Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open the ARSystemInstalledConfiguration.xml file.
      2. Search for the BMC_AR_PASSWORD_HOSTING attribute.
      3. In the value field for the attribute, enter the encrypted password.
    3. On the cloud AR System server, follow the same steps to update the encrypted password in the installation configuration file.
  5. Ensure that the BMC Remedy AR System ports specified in the ARSystemInstalledConfiguration.xml file are accurate.
    If the ports are not accurate, stop the enterprise AR System or cloud AR System services, updated the port numbers, and restart the service. For more information, see BMC Knowledge Article 000081555.
  6. Take a VM snapshot and a database backup of the enterprise AR System server and Platform Manager.


    Installing the patch can affect the AR objects in a non-overlay mode. Ensure that you follow the BMC Remedy AR System best practices for customizations. Customizations made to the base objects in Developer Studio base development mode are not preserved through upgrades. For more information, see Best Practice Customization mode and Customizing applications using overlays and custom objects.

  7.  Ensure that the JAVA_HOME variable is set on the servers where you are installing the patch. On Linux servers, ensure that X11 libraries are installed.

Back to top

Installing the patch

This section describes the procedure to install a patch.


For installing the patch on a single-VM compact deployment setup, place the installer file on the host and extract the files. Perform step 2 below to install the patch.

See the following BMC Communities video to apply patches to BMC Cloud Lifecycle Management. It covers preparing for and executing the installation, verifying the installation, and troubleshooting any installation issues.


To install the patch

Perform the following steps to install a patch in your environment:


In the BMC lab environment, installing the patch took about 50 minutes in the Windows Compact Deployment. But the Cloud Platform Manager steps in the Small Deployment takes a little while longer.
  1. Download and extract the patch installer and place a copy on each of the VMs that have the following components installed:
    1. Enterprise BMC Remedy AR System server
    2. Enterprise AR System Secondary server, if applicable
    3. Cloud Platform Manager

    Depending on which operating system you are on and the patch version that you are installing, download either of the following files:

    Patch versionOSInstallation package nameTo access the installation files
    For the zip package CLM_FeaturePack_4.6.06.001_Windows_Installer.zip
    LinuxCLM_FeaturePack_4.6.06.001_Linux_Installer.tar.gzExtract the package using the following command:
    tar –xvf CLM_FeaturePack_4.6.06.001_Linux_Installer.tar.gz
    For the zip package CLM_FeaturePack_4.6.05.002_Windows_Installer.zip
    LinuxCLM_FeaturePack_4.6.05.002_Linux_Installer.tar.gzExtract the package using the following command:
    tar –xvf CLM_FeaturePack_4.6.05.002_Linux_Installer.tar.gz

    Extract the package and navigate to the following path:



    Extract the package and navigate to the following path:



    • Ensure that you install the patch on the enterprise BMC Remedy AR System first and then on Platform Manager.
    • On the Cloud Platform Manager host, set JAVA_HOME to the bundled JRE (for example, C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\JVM_1.8.0_60).
  2. Install the patch on the Enterprise AR System server and the Enterprise AR System Secondary server, as follows:
    1. Depending on the Operating System you are on, run either of the following installation programs:
      • On Microsoft Windows, double-click the setup.exe file.
      • On Linux, navigate to the \CLMPatchInstaller\Disk1 location and run the setup.bin file 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 the VConsole to launch the installer.

    2. On the Welcome panel, review and implement the best practices in your environment, and then click Next
    3. On the Installation Preview panel, review the patch installer information and then click Install
    4. On the Installation Summary panel, review the installation log and then click Done to finish the installation.
  3. Repeat step 2 on the Cloud Platform Manager if you are running a Small Deployment. You do not have to perform this step, if you are on a compact deployment, that is, if all your components are installed on a single server.


    While testing in the BMC lab environment, a patch is generally installed on a Platform Manager server in approximately 2-3 minutes .

  4. If the My Cloud Services console or the End User Portal is installed on a remote system (for example: tomcat) and not on the Platform Manager host, you must perform step 2 on the remote system. Note that performing this step automatically updates the clmui.war file with new data.

Back to top

Configuring after installing the patch

Ensure that you perform the following post-configuration procedures after installing the patch:

To refresh the Register Provider screen

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Providers.
  2. Under Quick Links, select Custom.
  3. On the Providers page, click the Edit icon.
  4. In the Register Provider dialog box, complete or modify the fields, as necessary.
  5. Click Submit.


    This is applicable only if you are upgrading from a version earlier than BMC Cloud Lifecycle Management

To clear the cache

Use this procedure to clear Platform Manager, mid-tier, and browser cache:

  1. Stop the Platform Manager service (BMC CSM on Windows, bmccsm on Linux).
  2. Back up the Platform Manager cache (for example, <BMC_CLM_Installation>/Platform_Manager/cache) and Platform Manager configuration (for example, <BMC_CLM_Installation>/Platform_Manager/configuration)
  3. Delete the cache folder.
  4. Delete the org.eclipse.core.runtime, org.eclipse.equinox.app, and org.eclipse.osgi files from the configuration folder.
  5. Restart the Platform Manager service.
  6. Clear the mid-tier cache.
    If the mid-tier used by the BMC Cloud Lifecycle Management console is different than the mid-tier running on the enterprise AR System server, then you need to clear the cache.
  7. Log on to the Mid Tier Configuration Tool. 
  8. Perform a flush cache.
    The flush cache removes all items from the caches that BMC Remedy Mid Tier maintains. The next time the mid tier needs those objects, the most up-to-date versions are retrieved from the AR System server.
  9. Clear the browser cache.
  10. Perform the following steps to hard delete the mid-tier cache:
    1. Stop the mid-tier service.

    2. Log in to the mid-tier server, and delete the contents of the following folders:

      1. ARSystem\midtier\attstore

      2. ARSystem\midtier\cache

      3. ARSystem\midtier\cachetemp

      4. ARSystem\midtier\dvmodule

      5. ARSystem\midtier\PluginsCache

      6. ARSystem\midtier\WEB-INF\atriumDeploymentPackages

      7. ARSystem\midtier\WEB-INF\AtriumWidget

      8. ARSystem\midtier\WEB-INF\AtriumWidget-7604

    3. Delete the atrium-* files in the ARSystem\midtier\WEB-INF\lib folder.
    4. Delete the contents of the work and temp folders in the ....\...\Apache Software Foundation\Tomcat X.X folder.
    5. Delete the viewStats.dat and viewStats.dat.bak files from the ARSystem\midtier\WEB-INF\Classes folder.
    6. Start the Tomcat (JSP Engine) service.
Back to top

Related topics

Downloading the installation files
Known and corrected issues

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.