4.5.00.001: Patch 1 for version 4.5.00

Redirect Notice

This page will redirect to /xwiki/bin/view/Automation-DevSecOps/Client-Management/BMC-Cloud-Lifecycle-Management/clm45/Release-notes-and-notices/Patches/ in about 30 seconds.

Note

Documentation for this patch has been moved to the Patches page. If you had bookmarked this page and happen to open it, you will be automatically redirected to the Patches page after 30 seconds.

This topic contains information about fixes and updates in this patch, and provides instructions for downloading and installing the patch.

This topic includes the following sections:

Tip

For information about issues corrected in this service pack, see Known-and-corrected-issues.

Click here to create a PDF version of the Patch 1 release notes.

Updates

Patch 1 for BMC Cloud Lifecycle Management 4.5 provides the following updates.

To locate any update, perform any of the following actions:

Select an option 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.

Downloading the patch

For download instructions, see, Downloading-the-installation-files.

Supported upgrade paths

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

Preparing to install the patch

Before installing Patch 1, ensure that the following conditions are met:

If you are using any of the earlier versions, upgrade to BMC Cloud Lifecycle Management version 4.5.
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.

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.
Perform the following steps to ensure that the passwords match
1. Generate an encrypted password:
  On the Cloud Platform Manager, go to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Utilities.
  Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
  Click Encrypt.
  In the Password and Confirm Password fields, enter the new password.
  Click Encrypt.
  Copy the new encrypted password.
2. Update the encrypted password in the installation configuration file on the enterprise AR System:
  Go to InstallationDirectory\BMCCloudLifeCycleManagement\ and open the ARSystemInstalledConfiguration.xml file.
  Search for the BMC_AR_PASSWORD_HOSTING attribute.
  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.
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 KA410544.
Take a VM snapshot and a database backup of the enterprise AR System server and Platform Manager.
Warning
Installing the patch can affect the AR objects in a non-overlay mode. Ensure that you follow the best practices for customizations.
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.

Installing the patch

This topic describes the procedure to install Patch 1.

Note

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

To install Patch 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. Cloud Platform Manager
  Notes
  Install Patch 1 on the enterprise BMC Remedy AR System first and then on Platform Manager.
  For Linux, extract the installer by using the tar –xvf CLMPatchInstaller4500Px.tar command.
  In the above command, x refers to the patch number. Therefore, to extract patch 1, run tar –xvf CLMPatchInstaller4500P1.tar.
On the Enterprise AR System server, install patch:
1. Start one 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.
    Note
    You can also use the VConsole to launch the installer.
2. On the Welcome pane, note the warnings and click Next.
3. On the Directory selection pane, navigate to the location on the host where you want to install the BMC Cloud Lifecycle Management patch installer files and click Next.
  You can accept the default value if you do not have a specific location for the installation files.
4. On the Installation Preview pane, review the summary and click Next.
Repeat step 2 on the Cloud Platform Manager.
(Optional; only if you have a high availability environment) On each additional or secondary enterprise AR System server, copy all the files from the <CLMPatchInstaller>\Disk1\files\patch\ear\Px\jars\Cloud_Portal\plugin and replace them in the <BMCCloudLifeCycleManagementInstallationDirectory>\Cloud_Portal\plugin location.
Note
In the above path, x refers to the patch number. Therefore, to refer to the path for patch 1, specify <CLMPatchInstaller>\Disk1\files\patch\ear\P1\jars\Cloud_Portal\plugin.

Configuring after installing the patch

You must clear cache after installing Patch 1. Perform the following post configuration steps:

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.
Log on to the Mid Tier Configuration Tool.
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.
Clear the browser cache.
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:
  - ARSystem\midtier\attstore
  - ARSystem\midtier\cache
  - ARSystem\midtier\cachetemp
  - ARSystem\midtier\dvmodule
  - ARSystem\midtier\PluginsCache
  - ARSystem\midtier\WEB-INF\atriumDeploymentPackages
  - ARSystem\midtier\WEB-INF\AtriumWidget
  - 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.