Reconciling a large number of CIs

As a configuration manager, it is important to make sure that the resources powering the reconciliation process remain efficient, accurate, and fast when reconciling a large number of configuration items (CIs).

In such cases, use the RE ID Service to run the identification activity in a reconciliation job on a separate pod and free up the reconciliation pod for other related activities. The RE ID Service also filters out duplicate CIs from the source dataset and excludes them from the identification activity. This exclusion makes the overall reconciliation process faster and more efficient by optimizing the resources needed to process a large number of CIs. 

The RE ID Service is enabled by default, and only the identification activity in reconciliation jobs runs on a separate pod. If you disable the RE ID Service, the identification activity runs on the same pod as the reconciliation job. The logs for these jobs are located at /opt/bmc/ARSystem/db/recon-identification-service.log.


Scenario

Chris, a configuration Manager at Apex Global, wants to run reconciliation jobs with identification activity. He expects the number of CIs to be processed to be around 13 million. Hence, he wants to make sure that the reconciliation process is efficient and fast. 

Before running the reconciliation job, he logs in to Mid Tier, opens the Centralized Configurations console, and confirms that the RE-Enable-IDService is enabled.

Next, from 

CMDB Portal

, Chris runs the reconciliation job with the identification activity. With the RE ID Service enabled, Chris benefits in the following ways:

1. The Identify activity runs on a separate pod, which speeds up the process.

2. The Identify activity initially searches for duplicate CIs in the source dataset and excludes them from the identification process against the target dataset. This filtering enhances the efficiency of the identification process by reducing the probability of errors caused by duplicate CIs.

To modify the RE ID Service setting

  1. Log in to Mid Tier.
  2. Select Applications > AR System Administration > AR System Administration Console > System > General > Centralized Configuration.
  3. From the Component Type list, select com.bmc.arsys.other > reconciliation pod name .
  4. In the Setting Name column, if the RE-Enable-IDService parameter is not present, click Add to add the setting.
    This parameter is enabled by default and is not displayed in the Setting Name list. 
  5. In the corresponding Setting Value, enter either of the following value:
    • F (False) to disable the RE ID Service feature.
    • (Default) T (True) to enable the RE ID Service feature.


For information about modifying the default configurations for the RE ID Service, see Reconciliation-Engine-configuration-settings.


Where to go from here

Creating-a-standard-reconciliation-job

Creating-a-custom-reconciliation-job

 

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