Skip to Content
Information
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.

Merging two AR System servers into one AR System server after upgrade

The 4.1.x release provides the new 2AR1AR utility that merges the two AR System servers (Enterprise-AR and Cloud-AR) into the single AR System server architecture introduced in 4.0 (Cloud Portal and Database). 

The Enterprise-AR and Cloud-AR servers use the obsolete AR System architecture from the 2.x and 3.x releases of BMC Cloud Lifecycle Management.

Warning

Note

You run the merge utility from a Windows host against your Enterprise-AR and Cloud-AR servers, Windows or Linux.

To summarize the merge operation, this utility performs the following tasks when creating the single 4.x AR System server architecture. 

  • Disables DSO
  • Creates a new temporary dataset on the Enterprise-AR server
  • Creates a reconcilation merge job that ports Enterprise-AR data back to BMC.ASSET dataset on Enterprise-AR which is temporarily moved to other dataset
  • Safely deletes the obsolete records on Enterprise-AR and Cloud-AR
  • Uses the temporary dataset to move existing data in BMC.ASSET dataset to give preference to data coming from Cloud-AR
  • Runs delta data migration utility to copy data from Cloud-AR to Enterprise-AR
  • Executes a Merge Job that ports original data of Enterprise-AR BMC.ASSET dataset back to BMC.ASSET dataset on Enterprise-AR
  • Updates BMC Service Request Management, USM, and Platform Manager configuration

The following BMC Communities video how to bring BMC Cloud Lifecycle Management setups operating in two-AR mode to single AR mode to eliminate the need of the second AR.

icon-play.pnghttps://youtu.be/0PrD_8WiQWs

Before you begin

Warning

Note

When you finish the two AR System server into one AR System server migration, you see problems with service blueprints if you had LDAP authentication set up on the Enterprise-AR server but not the Cloud-AR server. The drop-down menu for the Service Blueprint is blank when you try to edit a service offering in the Service Catalog workspace. For more information, see Services, especially Creating-a-service-offering.

Workaround:

Before you start the 2-ar-to-1-ar-migration-utility, set up LDAP on all the BMC Remedy AR systems involved in 2AR to 1AR migration.

  1. Locate, copy, and extract the 2-ar-to-1-ar-migration-utility to the Windows host:
    1. Navigate to the <Installer_Dir>\Applications\BMC-CLM\Windows folder. 
    2. Copy the Installer file to your Windows host. 
    3. Extract the compressed Installer file. 
    4. Navigate to the ..\Installer\Disk1\files folder. 
    5. Extract the compressed 713b0c9491fe file. 
    6. Navigate inside the ..\713b0c9491fe\2-ar-to-1-ar-migration-utility folder to view the Windows run.bat file and the supporting folders and files.
  2. Stop the Platform Manager service (BMC CSM). 
  3. Finish the entire upgrade of BMC Cloud Lifecycle Management to version 4.1.00, including the Enterprise-AR and Cloud-AR servers. 
  4. Verify that the data migration is complete and successful after you finish the upgrade.
  5. Execute the CLM reconcilation jobs on the Enterprise-AR server (BMC CSM CDB Data Reconciliation) and the Cloud-AR server (BMC CSM ENT Data Reconciliation) before you start the 2AR to 1AR merge to make sure there is no mismatch of soft-deleted CIs between Enterprise-AR and Cloud-AR.
  6. Open the DSO Distributed Pending form on the Enterprise-AR and Cloud-AR servers and verify that there are no pending records.
    For example:
    http://<clm_MidTier>:<port>/arsys/forms/<EARorCAR>/Distributed+Pending/
    http://clmMidTier:800/arsys/forms/EAR/Distributed+Pending/ 
    http://clmMidTier:8080/arsys/forms/CAR/Distributed+Pending/ 
  7. After the DSO operations of all the pending CIs is complete on the Enterprise-AR and Cloud-AR servers, stop the DSO processes:

    1. Open the armonitor file (located by default in C:\Program Files\BMC Software\ARSystem\Conf), comment out the DSO processes, and save the file. 

      #"C:\Program Files\Java\jre7\bin\java" -Xmx512m -classpath "C:\Program Files\BMC Software\ARSystem\dsoj;C:\Program Files\BMC Software\ARSystem\dsoj\ardsoj81_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arapi81_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arcmnapp81_build001.jar;C:\Program Files\BMC Software\ARSystem\arserver\api\lib\arutil81_build001.jar" com.bmc.arsys.dsoj.DSOServer --unicode -i "C:\Program Files\BMC Software\ARSystem" -m 
    2. Restart the AR System servers.
    3. Execute the reconciliation jobs on the Enterprise-AR and Cloud-AR servers before you start the 2AR to 1AR merge to make sure there is no mismatch of soft-deleted CIs between Enterprise-AR and Cloud-AR..
  8. After the reconcilation jobs are successful, stop the reconciliation continuousjobs and make them non-continuous.
    1. Edit the BMC CSM CDB Data Reconciliation job.
      REjob.jpg 
    2. Select the Identification Activity.
    3. Under Schedule, uncheck Continuous to disable the action. 
    4. Click Save. 
    5. Perform the same steps on the BMC CSM ENT Data Reconciliation job on Cloud-AR. 

  9. Install NSH on the Windows host where you plan to run the merge utility.

    Success

    Tip

    You can run the merge utility on the same Windows host where you used the install planner, since NSH is already installed on it.

  10. On the Cloud-AR server, apply the AR Migrator license before you run migration. 
  11. Make sure that the Windows host has the following minimum recommended system configuration:
    1. Make sure that the Windows host has sufficient CPU and RAM.
    2. Run the performance tuning parameters on the Enterprise-AR and Cloud-AR servers. 
    3. Make sure that the Windows host has Oracle JRE 64-bit 1.7 installed. 

(Optional) To manually apply private extensions to the Enterprise-AR server before 2AR1AR execution

Optionally, you can manually apply private extensions on Enterprise AR before the 2AR1AR merge process. You must use the Atrium Core Maintenance utility (AtriumCoreMaintenanceTool.exe) to apply only private > schema and private > logic extensions, but not private > DSO.

Warning

Note

  1. Locate and extract Cloud_DB:
    1. Navigate to <Installer_Dir>\Applications\BMC-CLM\Windows\Installer\Disk1\files.
    2. Extract the compressed Cloud_DB file.
  2. Navigate to the C:\Program Files\BMC Software\AtriumCore\atriumcore folder and launch AtriumCoreMaintenanceTool.exe.
  3. Click the Configuration tab and then click the Run Extensions tab.
  4. Enter the path of the schema ExtensionLoader.xml file (for example, located at C:\BMC-CLM\Windows\Installer\Disk1\files\Cloud_DB\extensions\clm\private\schema).
    ExtLoaderPath.jpg 
  5. Click Next to enter the Cloud Portal and Database server details. 
  6. Enter the User Name (for example, Demo), Password, Port Number (for example, 9595), and AR Server Host Name.
    MaintenanceTool.jpg 
  7. Click Next.
  8. Click Run to execute the XML file.
  9. Repeat these steps to enter the path of the logic ExtensionLoader.xml file located, for example, at C:\BMC-CLM\Windows\Installer\Disk1\files\Cloud_DB\extensions\clm\private\logic.

To merge two AR System servers into one AR System server

  1. Copy the merge utility zip file to the Windows host and extract it. 

  2. Open a command window and execute the run.bat script. 

    C:\2-ar-to-1-ar-migration-utility>run.bat
    C:\2-ar-to-1-ar-migration-utility>java -Dlog4j.configuration=file:log4j.properties -jar 2-ar-to-1-ar-migration-jar-with-dependency.jar
    Enter Enterprise AR Server Name/IP : vw-pun-csm-dv07
    Enter Enterprise AR Server Port : 9595
    Enter Enterprise AR Server Admin User Name : Demo
    Enter Enterprise AR Server Admin Password :
    Enter Cloud AR Server Name/IP : vw-pun-csm-dv08
    Enter Cloud AR Server Port : 9595
    Enter Cloud AR Server Admin User Name : Demo
    Enter Cloud AR Server Admin Password :
    Enter Platform Manager machine Name/IP : vw-pun-csm-dv08
    Enter Platform Manager installation directory : C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager

     

    1. Enter the Enterprise-AR server name or IP address.
    2. Enter the Enterprise-AR port.
    3. Enter the Enterprise-AR administrator and password.
      The script verifies your Enterprise-AR logon information.  
    4. Enter the Cloud-AR server name or IP address.
    5. Enter the Cloud-AR port.
    6. Enter the Cloud-AR administrator and password.
      The script verifies your Cloud-AR logon information. 
    7. Enter the Platform Manager host name or IP address.
    8. Enter the Platform Manager installation directory (for example, C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager). 
    9. Press Enter.

 

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

BMC Cloud Lifecycle Management 4.1