Unsupported content 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.

Patch 2 for version 3.0

This section contains information about Patch 2 for BMC Cloud Lifecycle Management version 3.0. Patch 2 is a cumulative patch that includes the fixes in Patch 1 for version 3.0.

Note

Patch 1 for version 3.0 is obsolete and no longer available.

Before you begin

You must install or upgrade to BMC Cloud Lifecycle Management 3.0 before you apply this patch.

Obtaining the patch files

To download the patch files for BMC Cloud Lifecycle Management 3.0 Patch 2, see Downloading-the-installation-files.

Installing the patch

Follow the procedures in this section to apply the patch to

  • Cloud Platform Manager
  • Enterprise BMC Remedy AR System server

Note

You must run the patch installer on both the Cloud Platform Manager server and enterprise BMC Remedy AR System server as described below.

To apply the patch to the Cloud Platform Manager

  1. Make a snapshot of the Cloud Platform Manager server before applying the patch.
  2. Extract the content of the patch zip file.
  3. Copy the setup file to the Cloud Platform Manager host computer.
  4. Launch the patch installer by running the setup command from the command line.
    • For Microsoft Windows: setup.cmd
    • For Linux: setup.sh

      The Welcome panel is displayed.
  5. Click Next to display the License Agreement panel.
  6. Click I agree to the terms of the license agreement.
  7. Click Next to display the Installation Preview panel.
  8. Click Install.

    The progress panel is displayed while the installation is in progress. When the installation is complete, the Installation Summary panel is displayed.
  9. (Optional) Click View Log to display the installation log.
  10. Click Done to exit the installer.

To apply the patch to the enterprise BMC Remedy AR System server

  1. Make a snapshot of the enterprise BMC Remedy AR System server before applying the patch.
  2. Extract the content of the patch zip file.
  3. Copy the setup file to the enterprise BMC Remedy AR System server.
  4. Launch the patch installer by running the setup command from the command line.
    • For Microsoft Windows: setup.cmd
    • For Linux: setup.sh

      The Welcome panel is displayed.
  5. Click Next to display the License Agreement panel.
  6. Click I agree to the terms of the license agreement.
  7. Click Next to display the BMC AR System Server & IT Service Mgt. Suite user inputs panel.
    ARcredentials.gif
  8. Enter the BMC Remedy AR System credentials, port, and name alias.
  9. Click Next to display the Installation Preview panel.
  10. Click Install.

    The progress panel is displayed while the installation is in progress. The patch installer imports the .def and .arx files that were updated as part of the patch. The import might take a while to complete.
    When the installation is complete, the Installation Summary panel is displayed.
  11. (Optional) Click View Log to display the installation log.

  12. Click Doneto exit the installer.

    Note

    The installation succeeds with two warnings caused by importing .def files. You can ignore these warnings.

  13. Clear the mid tier cache:
    1. Stop the BMC Remedy mid tier by stopping the Tomcat service that the mid tier is running on.
    2. Delete the files inside of the following folders:
      • <Midtier>\cache
      • <Midtier>\cachetemp
      • <Midtier>\PluginsCache
    3. Start the mid tier by restarting the Tomcat service.
    4. Clear your browser's cache.

Applying required BMC component product patches and hotfixes

After installing Patch 2 for version 3.0, use the knowledge article instructions to install the following:

  • Patch 1 for BMC Atrium Core 8.0.00: KA379087 (If you applied this patch previously, you do not need to apply it again.)
  • Patch 1 for BMC Network Automation 8.2.02: KA378938
  • Hotfix 305 for BMC Server Automation 8.2.01: KA378937

To read a knowledge article:

  1. Log on to the BMC Software Customer Support Knowledge Base.
  2. In the Search field, enter the KA number, and click Ask.
  3. Follow the instructions contained in the knowledge article to apply the patch or hotfix.

Performing data migration

When upgrading BMC Cloud Lifecycle Management in a production environment, you must migrate the cloud core data.

If you are applying this patch to a new (fresh) installation of BMC Cloud Lifecycle Management version 3.0, you do not need to migrate data.

To migrate data from version 2.1.xx to Patch 2 for version 3.0

To upgrade from version 2.1.xx, run the BMC Cloud Lifecycle Management 3.0 installer, as described in Upgrading. When the upgrade portion is complete, an option appears in the installer UI to run the data migration utility to migrate the cloud core data.

Before you run the data migration utility:

  1. Exit the BMC Cloud Lifecycle Management 3.0 installer.
  2. Apply Patch 2 for version 3.0, as described above.
  3. Migrate your data using the Maintenance Tool, as described below in To run the Maintenance tool to migrate data.
  4. After migration is complete, check to ensure that the product is no longer in Maintenance Mode:
    1. Look at the code in the following file:
       <installation directory>\BMCCloudLifeCycleManagement\Platform_Manager\configuration\Cloudservices.json.
    2. Search for Maintenance Mode in the file.
    3. If Maintenance Mode is set to true, turn off Maintenance Mode as described below in To turn off Maintenance Mode.

If you ran the data migration utility before applying this patch, you must run the Maintenance Tool to migrate your data.

To migrate data from version 3.0 or Patch 1 to Patch 2 for version 3.0

Migrate your data using the Maintenance Tool, as described in To run the Maintenance tool to migrate data.

Note

If you are applying this patch to a new (fresh) installation of BMC Cloud Lifecycle Management version 3.0, you do not need to migrate data.

After migration is complete, check to ensure that the product is no longer in Maintenance Mode:

  1. Look at the code in the following file:
     <installation directory>\BMCCloudLifeCycleManagement\Platform_Manager\configuration\Cloudservices.json.
  2. Search for Maintenance Mode in the file.
  3. If Maintenance Mode is set to true, turn off Maintenance Mode as described below in To turn off Maintenance Mode.

To run the Maintenance tool to migrate data

  1. Stop the Cloud Platform Manager service.
  2. Delete the cache files in <Platform Manager Installed Dir>/cache/
  3. Start the Cloud Platform Manager service.
  4. Log in to the cloud BMC Remedy AR System server using the AR Admin user.
  5. Open the Share Application Properties form.
  6. Search for the Task No property.
  7. Change the value of the Task No property from 230 to 0.
  8. On the enterprise BMC Remedy AR System server, launch the data migration utility by running the BMCCloudLifeCycleManagementMaintenanceTool file in the <BMCCloudLifeCycleManagement Installed Dir>/utilities folder.
  9. Provide the inputs requested by the utility.

For more information, see Migrating-data-for-the-cloud-core-components.

Applying version 3.0 Patch 02 to an upgraded environment

When upgrading BMC Cloud Lifecycle Management in a production environment from version 2.1.xx to version 3.0 Patch 02, use the following instructions.

To upgrade from version 2.1.xx

  1. Run the BMC Cloud Lifecycle Management 3.0 installer, as described in Upgrading.
  2. After the portal upgrade and before starting with Upgrade Data Migration node, apply version 3.0 Patch 02 as described above.
  3. Run Upgrade Data Migration as described in Migrating-data-for-the-cloud-core-components

To upgrade when BMC Cloud Lifecycle Management 2.1 is already upgraded to version 3.0 and the version 3.0 upgrade data migration is already done

  1. Apply the version 3.0 Patch 02 as described above.
  2. Run Upgrade Data Migration as described in To run the Maintenance tool to migrate data.
  3. After migration is complete, check to ensure that the product is no longer in Maintenance Mode:
    1. Look at the code in the following file:
       <installation directory>\BMCCloudLifeCycleManagement\Platform_Manager\configuration\Cloudservices.json.
    2. Search for Maintenance Mode in the file.
    3. If Maintenance Mode is set to true, turn off Maintenance Mode as described below in To turn off Maintenance Mode.

To turn off Maintenance Mode

During upgrade and migration, Maintenance Mode is set to true to prevent service offering requests from being processed. However, the migration process might not set Maintenance Mode back to false when migration is complete. To turn off Maintenance Mode:

  1. Stop the Cloud Platform Manager service.
  2. Edit <installation directory>\BMCCloudLifeCycleManagement\Platform_Manager\configuration\Cloudservices.json
  3. Search for Maintenance Mode in the file.
  4. Change value of Maintenance Mode to false.
  5. Start the Cloud Platform Manager service.

Corrected issues

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*