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

upgrade two AR System servers, upgrade one AR System server, only one AR System server, 2AR1AR utility, 2AR1AR, 2-ar-to-1-ar-migration-utility, 2-ar-to-1-ar, merging data

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.

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.

icon-play.png 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 new dataset on Enterprise-AR
  • Builds new data dictionaries for Enterprise-AR and Cloud-AR
  • Renames request IDs on Cloud-AR and cleans up instances
  • Copying instances from Cloud AR to Enterprise AR
  • Cleans up regular forms
  • Runs reconciliation job to merge instances
  • Updates BMC Service Request Management, USM, and Platform Manager configuration
  • Imports required filters on Enterprise-AR

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>\media\Applications\Migration_2_AR_TO_1_AR\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. Generate a data-checker report and fix all inconsistencies in your Enterprise-AR and Cloud-AR servers.
    To obtain the CLM Data Consistency Checker (DCCU) and Estimator Utility, contact BMC Customer Support.
  3. Verify that your CLM stack is in good working condition.
    For more information, see Verifying-the-installation. 
  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 (Windows) or /etc/arsystem/<serverName>/ (Linux), 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. Verify that all reconcilation jobs are completed by checking RE Jobs form for any entries in started/queued state.
  7. 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.
      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. 
  8. Disable the normalization engine and DSO on Enterprise-AR and Cloud-AR.
    1. Open ar.cfg/ar.conf (C:\Program Files\BMC Software\ARSystem\Conf for Windows or) and armonitor.cfg/armonitor.conf.
    2. Check for normalization entries.
    3. Comment them out.
    4. Check for DSO process entries.
    5. Comment them out.
    6. Save your changes.
  9. (Optional) Install the AR Migrator license on Cloud-AR.
  10. Install NSH on the Windows host from where you will run the 2AR1AR 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.  
  11. Verify that all integrations performed on Cloud-AR (for example, LDAP) are available on Enterprise-AR.
  12. Stop and restart AR services after making changes to ensure stack is working as expected.
  13. Make sure that sufficient space is available on database machines (Enterprise-AR) to ensure proper transfer of data. 
    The free space on the Enterprise-AR database should be <DB size of Cloud-AR+50GB>. The 2AR1AR links the Cloud-AR and Enterprise-AR databases and the transfer of data is not in memory. During the migration, data is moved into temp storage and then injected into Enterprise-AR database.
  14. Verify that your systems have enough RAM/CPU available while the 2AR1AR utility is running. 
    This requirement will vary based on database size. A minimum of 16G RAM and 8G CPU is required on AR and DB servers.
  15. Collect following details before you start the 2AR1AR utility
    • Enterprise-AR and Cloud-AR details (for example, username, password, ports)
    • Enterprise-AR and Cloud-AR database details (for example, username, passwords, ports)
    • Platform Manager path details

  16. For Windows SQL Server and Linux Oracle databases, collect or create the following settings:

    Database

    Required information

    Windows SQL Server

    User with sysadmin privileges. For example, you can use sa while giving inputs for Enterprise-AR and Cloud-AR databases.

    Linux Oracle

    You must create a new service name (ServiceName) for the Cloud-AR database in the Enterprise-AR database in tnsnames.ora as follows:

    <DB_LINK_NAME> =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP) (HOST = <remote IP>) (PORT = 1521))
        (CONNECT_DATA =
          (SID = <SERVICE_NAME>)
        )
      )

    <remote IP> is the IP address or hostname of the Cloud-AR database host.
    PORT is the Cloud-AR database port.
    <SERVICE_NAME > is the Cloud-AR database ServiceName.

 

(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.

 

 

 

 

 

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