Patch 2 for Service Pack 2 for version 2.1.00

This topic contains information about BMC Cloud Lifecycle Management 2.1 SP2 Patch 2 (2.1.02.02).

Downloading the patch

Download the patch files for BMC Cloud Lifecycle Management 2.1 SP2 Patch 2 from the BMC Electronic Product Distribution (EPD) site.

Installing the patch

Follow the procedures in this section to apply the patch to the following components:

• Cloud Platform Manager
• Enterprise AR System server
• Cloud AR System server

Patch content

The patch files are organized as follows:

1. The Java binaries, AR System definition files, and data files are organized into individual folders. The folders are named after specific product components. For example:
   <Patch name>
   .....Cloud AR
   .....Enterprise AR
   .....Platform Manager
2. For easy identification, the names of BMC Remedy AR System-specific files (for the enterprise AR System server and the cloud AR System server) start with the patch name. For example, Patch1_file1.def and Patch2_file1.def. The Java binaries do not follow this convention.

Depending on the current version of your BMC Cloud Lifecycle Management environment, apply all the files or only patch-specific files. The following table lists the files that you need to install for your environment. If you are not sure of the current patch version, apply all files in the patch folder.

Upgrade paths

To apply the patch to Cloud Platform Manager

1. Stop the Platform Manager service:
   • (Microsoft Windows) Stop the BMC_CSM service
   • (Linux) /etc/init.d/bmccsm stop
2. Make a backup of the <Platform Manager Installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/lib folder.
3. Copy and replace the binary files provided in the Platform Manager/lib folder of the patch zip file to the <Platform Manager Installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/lib folder.
   The existing lib folder might contain additional binary files that are not affected by this patch. Do not remove them from the lib folder.
4. If you are updating a Linux system, make sure the new binary files have execute permission.
5. Make a backup of the cmdb-api-7.6.04-SNAPSHOT.jar file in the <Platform Manager Installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/3rdParty folder.
6. Copy and replace the cmdb-api-7.6.04-SNAPSHOT.jar file in the Platform Manager folder of the patch zip file to the <Platform Manager Installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/3rdParty folder.
7. If you are updating a Linux system, give execute permission to the cmdb-api-7.6.04-SNAPSHOT.jar file.

8. Open the providers.json file in a text editor and add the following JSON to the access values section of the BMC Server Automation provider section. (The JSON provides the access attribute value for the BBSA_BLCLI_COMMAND_TIMEOUT_SECONDSaccess attribute.)

   {
     "cloudClass":"com.bmc.cloud.model.beans.AccessAttributeValue",
     "accessAttribute":{
       "cloudClass":"com.bmc.cloud.model.beans.AccessAttribute",
       "datatype":"INTEGER",
       "description":"Timeout for the execute command",
       "guid":"5fcf3080-ed80-450f-8e01-2ec91f0c9027",
       "isOptional":true,
       "isPassword":false,
       "modifiableWithoutRestart":false,
       "name":"BBSA_BLCLI_COMMAND_TIMEOUT_SECONDS"
     },
     "attributeValue":"300",
     "guid":"1c6c8770-5f12-49b5-9756-bd258d75b442",
     "name":"BBSA_BLCLI_COMMAND_TIMEOUT_SECONDS"
   }
   

   If you need more information about how to add the access attribute value to the providers.json file, click the following disclosure triangle.

    Adding the access attribute value

   The following example shows the access values section in the BMC Server Automation provider section of a providers.json file. The last entry in the section is for the value of an access attribute named BBSA_ENABLE_CLEANUP_ON_ROLLBACK and ends with a square bracket (]).

   {
     "cloudClass":"com.bmc.cloud.model.beans.Provider",
     "accessValues":[
       {
         "cloudClass":"com.bmc.cloud.model.beans.AccessAttributeValue",
   
         <...>
   
         "description":"Enable clean-up on rollback",
         "guid":"2bf19b0c-2b95-4d2e-a40b-9ab0eced06b0",
         "name":"BBSA_ENABLE_CLEANUP_ON_ROLLBACK"
       }]
   

   To add the new access attribute value, type a comma before the square bracket at the end of the section and then copy and paste the JSON for the value of the BBSA_BLCLI_COMMAND_TIMEOUT_SECONDS access attribute. After you paste the JSON into the file, the section should look similar to the following code snippet:

   {
     "cloudClass":"com.bmc.cloud.model.beans.Provider",
     "accessValues":[
       {
         "cloudClass":"com.bmc.cloud.model.beans.AccessAttributeValue",
   
         <...>
   
         "description":"Enable clean-up on rollback",
         "guid":"2bf19b0c-2b95-4d2e-a40b-9ab0eced06b0",
         "name":"BBSA_ENABLE_CLEANUP_ON_ROLLBACK"
       },
       {
         "cloudClass":"com.bmc.cloud.model.beans.AccessAttributeValue",
         "accessAttribute":{
           "cloudClass":"com.bmc.cloud.model.beans.AccessAttribute",
           "datatype":"INTEGER",
           "description":"Timeout for the execute command",
           "guid":"5fcf3080-ed80-450f-8e01-2ec91f0c9027",
           "isOptional":true,
           "isPassword":false,
           "modifiableWithoutRestart":false,
           "name":"BBSA_BLCLI_COMMAND_TIMEOUT_SECONDS"
         },
         "attributeValue":"300",
         "guid":"401a2598-b52f-44e6-97ea-f8a614e18215",
         "name":"BBSA_BLCLI_COMMAND_TIMEOUT_SECONDS"
       }
     ]
   

9. Delete the org.eclipse.osgi folder from the <Platform Manager Installation directory>/BMCCloudLifeCycleManagement/Platform_Manager/configuration directory.
10. Start the Platform Manager service:
    • (Microsoft Windows) Start the BMC_CSM service
    • (Linux) /etc/init.d/bmccsm start

To apply the patch to the enterprise AR System server

1. Make a snapshot of the enterprise AR System server before applying the patch.
2. Connect to the enterprise AR System server by using BMC Remedy Developer Studio.
3. From the enterprise AR System server, import all the files in the Enterprise AR folder from the zip file.
4. While importing the objects, select the Replace Objects on the Destination Server option and verify that the other options are not selected.
5. Stop the enterprise AR System server.
6. Copy the cloud-plugin.jar file to the <installation directory>BMCCloudLifeCycleManagement/Cloud_Portal/plugin folder.
7. Start the enterprise AR System server.

To apply the patch to the cloud AR System server

1. Make a snapshot of the cloud AR System server before applying the patch.
2. Connect to the cloud AR System server ny using BMC Remedy Developer Studio.
3. From the cloud AR System server, import all the files in the Cloud AR folder from the zip file.
4. While importing the objects, select the Replace Objects on the Destination Server option and verify that the other options are not selected.

Corrected issues

The following BMC Cloud Lifecycle Management issues are corrected by this patch: