Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Merging two AR System servers into one AR System server

If you are running an environment with two AR System servers (Enterprise-AR and Cloud-AR), use the 2AR1AR utility to merge the servers into one AR System server before you start the upgrade. If you run the 2AR1AR utility after the upgrade, you include significantly more data in the merge operation. Because of DDM, this can greatly hamper performance of the 2AR1AR utility and increase the amount of time for the merge to finish. 

Note

  • The 4.1 release introduced the single AR System server architecture for all new installations of BMC Cloud Lifecycle Management. 
  • The minimum version required for applying the 2AR1AR merge utility is 4.1.00. If you are using an earlier version, first upgrade to 4.1 and then run the 2AR1AR merge utility. In addition, the maximum supported version to run 2AR1AR is 4.6.00. You cannot run the 2AR1AR merge utility after applying feature packs (for example, 4.6.04).

 

Note

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

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.

 https://youtu.be/0PrD_8WiQWs

Merge operation overview

To summarize the 2AR1AR merge operation, this utility performs the following tasks when creating the single AR System server. 

  • 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


When the installer prompts you if you use one AR System server during the upgrade,
select Yes, I have only one BMC AR System server, and then click Next.

Before you begin

Note

When you finish merging the two AR System server into one AR System server, 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.

You run the 2AR1AR migration utility on a Windows host.

  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. Execute the CLM reconciliation 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.
  4. 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:8080/arsys/forms/EAR/Distributed+Pending/ 
    http://clmMidTier:8080/arsys/forms/CAR/Distributed+Pending/ 
  5. 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..
  6. After the reconcilation jobs are successful, stop the reconciliation continuous jobs and make them non-continuous.
    1. Edit the BMC CSM CDB Data Reconciliation job.
    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. 
  7. Install NSH on the Windows host where you plan to run the merge utility.
    You must install NSH because sometimes, the 2AR1AR utility keeps prompting you for the Platform Manager installation path even after specifying the correct path. 

    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.

  8. On the Cloud-AR server, apply the AR Migrator license before you run migration.
  9. Turn off normalization.
    1. Stop the BMC Remedy AR System service.
    2. Open the ar.cfg (or ar.conf) file.
      On Windows, open C:\Program Files\BMC Software\ARSystem\Conf\ar.cfg. On Linux, open /opt/bmc/ARSystem/conf/ar.conf.
    3. Set the CMDB-Inline-Normalization option to false (F).

    4. Save the file.

    5. Open the armonitor.cfg (armonitor.conf) file.
      On Windows, open C:\Program Files\BMC Software\ARSystem\Conf\armonitor.cfg. On Linux, open /etc/arsystem/hostName/armonitor.conf.

    6. Comment the normalization process, for example:
      # "C:\Program Files\Java\jre7\bin\java" -Xmx512m -classpath "C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\ne;C:\Program Files\BMC Software\AtriumCore\cmdb\plugins;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arpluginsvr81_build001.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arapi81_build001.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arutil81_build001.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\log4j-1.2.14.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\cmdbapi81.jar;" com.bmc.arsys.pluginsvr.ARPluginServerMain -x vw-aus-clm-qa37 -i "C:\Program Files\BMC Software\ARSystem"
    7. Save the file.
    8. Restart the BMC Remedy AR System service.
  10. 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

The 2AR1AR utility applies the private extensions to the Enterprise-AR server. However, as an option, you can manually apply private extensions on Enterprise AR before you start the 2AR1AR merge process. Use the Atrium Core Maintenance utility (AtriumCoreMaintenanceTool.exe) to apply only private > schema and private > logic extensions, but not private > DSO.

Note

  1. Locate and extract Cloud_DB:
    1. Navigate to <Installer_Dir>\Applications\BMC-CLM\Windows\Installer\Disk1\files (Windows) or <Installer_Dir>\Applications\BMC-CLM\Linux (Linux).

    2. Extract the installer file (Installer.zip for Windows or Installer.tar.gzp for Linux). 
    3. Navigate inside the files folder and locate the compressed Cloud_DB file. 
    4. Copy the compressed Cloud_DB file to the Enterprise-AR host. 
    5. Extract the compressed Cloud_DB file.
  2. Launch AtriumCoreMaintenanceTool.
    For Windows, navigate to the C:\Program Files\BMC Software\AtriumCore\atriumcore folder; for Linux, go to <Installer_Dir>/bmc/AtriumCore/atriumcore.
  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:\Cloud_DB\extensions\clm\private\schema for Windows, or /data1/bmc/BMCCloudLifeCycleManagement/Cloud_DB/extensions/clm/private/schema for Linux).
  5. Click Next to enter the Enterprise-AR server details. 
  6. Enter the User Name (for example, Demo), Password, Port Number (for example, 9595), and AR Server Host Name.
  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 for Windows or /data1/bmc/BMCCloudLifeCycleManagement/Cloud_DB/extensions/clm/private/logic for Linux.

To merge two AR System servers into one AR System server

  1. Stop Platform Manager.
    • (Windows) From the Services window, select the BMC CSM service, and click Stop Service.
    • (Linux) From a command prompt, type the following command: /etc/init.d/bmccsm stop
  2. Copy the merge utility zip file to the Windows host and extract it.

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

    Has pre-requisites completed? Press Y to continue and N to abort :y
    Enter Enterprise AR Server Name/IP :vl-aus-clm-qa31
    Enter Enterprise AR Server Port :0
    Enter Enterprise AR Server Admin User Name :Demo
    Enter Enterprise AR Server Admin Password :
    Found Property Name [PDFName] and Property Value [BMCCloudLifecycleManagement.pdf]
    Found Property Name [Name] and Property Value [BMC Cloud Lifecycle Management]
    Found Property Name [DataLanguage] and Property Value [English]
    Found Property Name [Version] and Property Value [4.6.00]
    Found Property Name [LanguagePacks] and Property Value [en]
    Found Property Name [PDFName] and Property Value [BMCCloudLifecycleManagement.pdf]
    Found Property Name [Name] and Property Value [BMC Cloud Lifecycle Management]
    Found Property Name [DataLanguage] and Property Value [English]
    Found Property Name [Version] and Property Value [4.6.00]
    Found Property Name [LanguagePacks] and Property Value [en]
    Found Property Name [PDFName] and Property Value [BMCCloudLifecycleManagement.pdf]
    Found Property Name [Name] and Property Value [BMC Cloud Lifecycle Management]
    Found Property Name [DataLanguage] and Property Value [English]
    Found Property Name [Version] and Property Value [4.6.00]
    Enter Cloud AR Server Name/IP :vw-aus-clm-qa14
    Enter Cloud AR Server Port :0
    Enter Cloud AR Server Admin User Name :Demo
    Enter Cloud AR Server Admin Password :
    Enter Platform Manager machine Name/IP :vl-aus-clm-qa30
    Enter Platform Manager installation directory without single or double quotes
    :C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager
    Enter Enterprise AR Database Server Type SQL(S)/ORACLE(O) :s
    Enter Enterprise AR Database Server Name/IP :vl-aus-clm-qa31
    Enter Enterprise AR Database Server Port :1433
    Enter Enterprise AR Database Server Admin User Name :sa
    Enter Enterprise AR Database Server Admin Password :
    Enter Enterprise AR Database name :ARSystem
    Enter Cloud AR Database Server Type SQL(S)/ORACLE(O) :s
    Enter Cloud AR Database Server Name/IP :vw-aus-clm-qa14
    Enter Cloud AR Database Server Port :1433
    Enter Cloud AR Database Server Admin User Name :sa
    Enter Cloud AR Database Server Admin Password :
    Enter Cloud AR Database name :CARSystem

    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.
  4. If you turned off normalization as described in the Before you begin section, turn on normalization.

Updating the Enterprise-AR product registry

Update the product registry (ProductRegistry.xml) on the Enterprise-AR server before you start the upgrade. 

  1. Go to the Enterprise-AR host.
  2. Back up and update ProductRegistry.xml (C:\Windows\ProductRegistry.xml on Windows and /opt/bmc/ProductRegistry.xml on Linux) with the changes indicated with the bold font:

    <registeredProduct id="G4sn283wZ6m8uDgEy6rl0h1yv9t4h001">
       <productKey>productBMCCloudLifeCycleManagement</productKey>
       <productHome>C:\Program Files\BMC Software\BMCCloudLifeCycleManagement3</productHome>
       <productHomeVariableName>BMC_CLOUD_LIFE_CYCLE_MANGEMENT_HOME</productHomeVariableName>
       <installedConfigurationFileName>BMCCloudLifeCycleManagementInstalledConfiguration.xml</installedConfigurationFileName>
       <installingConfigurationFileName>BMCCloudLifeCycleManagementInstallingConfiguration.xml</installingConfigurationFileName>
       <installHistory>
         <installEntry>
           <timestamp>1336475947694</timestamp>
           <date>May 8, 2012</date>
           <time>4:19:07 AM PDT</time>
           <version majorVersion="1" minorVersion="00" releaseVersion="2"/>
           <installedFeatures>
              <feature>featurePublicExtension</feature>
              <feature>featurePortal</feature>
         </installedFeatures>
        </installEntry>
        <upgradeEntry>
          <timestamp>1404225946815</timestamp>
          <date>July 1, 2014</date>
          <time>7:45:46 AM PDT</time>
          <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
          <addedFeatures/>
        </upgradeEntry>
        <upgradeEntry>
           <timestamp>1404225946815</timestamp>
           <date>July 1, 2014</date>
           <time>7:45:46 AM PDT</time>
           <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
              <addedFeatures>
           <feature>featurePrivateExtension</feature>
              </addedFeatures>
         </upgradeEntry>
       </installHistory>
    </registeredProduct>

  3. Back up and update BMCCloudLifeCycleManagementInstalledConfiguration.xml (C:\<install_directory>\BMCCloudLifeCycleManagementInstalledConfiguration.xml on Windows and /<install_directory>/BMCCloudLifeCycleManagementInstalledConfiguration.xml on Linux) with the changes indicated with the bold font:

    <productFeatureMap>
      <productFeature backupOnUpgrade="false" id="featurePublicExtension" independentOfChildren="false" parent="featureCloudDbExtensions" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
      <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
      <requiredDiskSpaceMap>
       <requiredDiskSpace id="default" size="200 MB"/>
       <requiredDiskSpace id="backup" size="5 MB"/>
       <requiredDiskSpace id="temporary" size="400 MB"/>
       </requiredDiskSpaceMap>
      </productFeature>
    <productFeature backupOnUpgrade="false" id="featurePrivateExtension" independentOfChildren="false" parent="featureCloudDbExtensions" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
      <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
      <requiredDiskSpaceMap>
       <requiredDiskSpace id="default" size="1 MB"/>
       <requiredDiskSpace id="backup" size="0 bytes"/>
       <requiredDiskSpace id="temporary" size="0 bytes"/>
      </requiredDiskSpaceMap>
      <productFeatureReferenceMap>
       <productFeatureReference id="featurePublicExtension" type="LOCAL"/>
       </productFeatureReferenceMap>
      </productFeature>
      <productFeature backupOnUpgrade="false" id="featurePortal" independentOfChildren="false" rebootRequiredOnInstall="false" rebootRequiredOnUninstall="false" rebootRequiredOnUpgrade="false" requiredDiskSpaceMode="default" state="INSTALLED" visible="true">
      <version majorVersion="1" minorVersion="00" releaseVersion="4"/>
      <requiredDiskSpaceMap>
       <requiredDiskSpace id="default" size="150 MB"/>
       <requiredDiskSpace id="backup" size="5 MB"/>
       <requiredDiskSpace id="temporary" size="1 MB"/>
      </requiredDiskSpaceMap>
    </productFeature>

  4. On the Platform Manager host:
    1. Open the <Platform_Manager_Install_dir>\BMCCloudLifeCycleManagement.xml file. 
    2. Update all the instances of Cloud-AR to the Enterprise AR host. 
  5. Start the install planner to upgrade to 4.5.00 and continue with product integration. 

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.

Comments