How to apply CLM 3.0 Patch 2 and Hotfixes

 

The following is a high level summary of the steps necessary for upgrading/patching CLM 3.0 to Patch 2 plus necessary hot fixes.  A valid Support ID is required to access these files and patches.

  1. Place the Patch 2 software on the Enterprise AR and Platform Manager servers.  Execute the install planner as follows:
    1. Open up cmd.exe as Administrator, and execute the setup.cmd on the Platform Manager server, follow the wizard to install.
    2. Open up cmd.exe as Administrator, and execute the setup.cmd on the Enterprise AR server, follow the wizard to install.
      1. Ignore the two warning messages on the installer log files.
  2. 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   (this dir may not exist) 
      • <Midtier>\PluginsCache
    3. Start the mid tier by restarting the Tomcat service.
    4. Clear your browser’s cache.
  3. Install Patch 1 for BMC Atrium Core 8.0.00: KA379087  (Refer to Knowledge Article to attain and install patch).
    1. Extract the winrar file onto the Enterprise AR (EAR), then extract the Atrium 8.0 P1 zip archive.
    2. Open up cmd.exe as Administrator of the local EAR server.
    3. Set up JAVA_HOME as an environment variable to point to your Java home (usually C:\Program Files\Java\JRE….).
    4. Execute the setup.cmd in the subfolder Disk1 where the patch is located, to launch the Install Wizard.
    5. There should be no warnings or errors on the Install Logs.
  4. Install Patch 1 for BMC Network Automation 8.2.02: KA378938 (Refer to Knowledge Article to attain and install patch).
    1. Extract the ZIP patch file into a temp directory
    2. Open up cmd.exe as Administrator of the local BNA server, and navigate to the subfolder Disk1.
    3. Execute the setup.cmd in the Disk1  folder, to launch the Install Wizard.
    4. There may be some warnings in the Install Log, validate that BNA is up and running by logging onto web console.
  5. Install Hotfix 305 for BMC Server Automation 8.2.01: KA378937.  Download the hotfix from the Knowledge Article, unzip with WinRAR, and then apply in the following sequence:
    1. BBSA Upgrade Sequence for Windows:
      1. Upgrade the RSCD agent on BBSA Server
      2. Upgrade the RSCD agent on VC Server
      3. Stop the Appserver
      4. Close all the BBSA Consoles
      5. Upgrade the Appserver
      6. Ensure the each deployment is correctly configured with DB credentials (specially app server, job server, and _spawner).
        1. In a cmd prompt, type:
          1. blappconf -s config_deployment_<hostname>
          2. blappconf -s job_deployment_<hostname>
          3. blappconf -s _spawner
      7. Run the DB Migration tool:In the external-files.zip for BSA 8.2 SP1, run :
        <installDirectory>/NSH/bin/blmigration_mgr.exe <path-to>\8.2-SP1-external-files\bl_8.2.01\db_scripts\sqlserver\upgrade
      8. Upgrade all the consoles
        1. Remember to set the following Registry Keys to “0” (zero) in the BSA server or systems where consoles are to be upgraded:
          1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server->PerSessionTempDir and DeleteTempDirsOnExit
          2. Add the BBSACONSOLE82-SP1-WIN64 installer to DEP (My Computer->Properties->Advanced System Settings->Performance Settings->Data Execution Prevention->Add.
      9. Start the Appservers
      10. Start the console
  6. Run the Maintenance tool to migrate data between CLM 3.0 to CLM 3.0 Patch 2 (results were inconsistent, beware):
    1. Stop the Cloud Platform Manager CSM 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 (also known as Remedy User Tool – RUT. Unfortunately, CLM 3.0 no longer installs RUT as part of the AR install. Therefore, best way is to get it from a CLM 2.1 installation).
    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 theBMCCloudLifeCycleManagementMaintenanceTool file in the <BMCCloudLifeCycleManagement Installed Dir>/utilities folder.
    9. Provide the inputs requested by the utility.

That’s it!

All rights reserved by BMC Software, more details on BMC’s Cloud Lifecycle Management solution here.

Written by

October 29, 2012
2 Comments

Comments

  1. Hi,

    have you realised the same tutorial with upgrade 3.0 to 3.0 SP1 ? i am very interesting for migrate and apply hotfix for ARS SA and NA

    Best regards

    • Vinnie Lima says:

      I have found that upgrade from 3.0 to 3.0 SP1 or 3.1 SP1 is pretty straight forward. Have you run into issues?

Speak Your Mind

*


*