This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Reconciliation Engine configuration settings

The parameters in the Reconciliation section allow you to configure reconciliation settings in a server group environment.

If you are in a server group environment, select the required AR server from the Select Server drop-down list. If you have a stand-alone environment, the required server name is automatically displayed.



Default Value

Setting in the AR Configuration file 
(ar.cfg or ar.conf)

Definition Check Interval

Defines an expiration period for the Reconciliation Engine's cache of job definitions.

Example: If you change job, activity, precedence, or merge definitions, and then run a job, you might not see the results after the cache expires. Setting an expiration for the cached definitions helps to improve performance and reduce log size.


Polling Interval

Defines the polling interval in seconds. The Reconciliation Engine "sleeps" until the next job is scheduled to run or for this interval, or whichever occurs first. The Polling interval is used only when the dispatcher does not send a signal to the Reconciliation Engine.

RPC Socket

The BMC Remedy AR System server RPC socket that the Reconciliation Engine uses for processing. You can specify only 390698 or 390699, which are the ports reserved for the Reconciliation Engine. You should use only those ports reserved for BMC CMDB and not ports that the BMC Remedy AR System can use. 

If you use a port other than the reserved ports, the Reconciliation Engine displays a warning that the port in invalid. This can be used to specify a maximum number of threads.

Execution Interval for Continuous JobThe execution interval of a continuous job. If you set this value to less than 120 seconds (2 minutes), then the Reconciliation Engine converts that value to 120 seconds (2 minutes).


(30 minutes)

Job Idle Time

This is the time interval for which a job can remain idle.

Important: By default, the feature is disabled by setting the value to 0 minutes.

If you realize that a reconciliation job is idle for more than 12 hours, we recommend you to increase the value in the Job Idle Time field to 500 minutes. This ensures that after 500 minutes, the fail-safe mechanism detects the unresponsive job, starts a new job instance, and deletes the earlier job instance that was stuck.

For more information on the fail safe feature see, Monitoring a reconciliation job.

Select this option if you have configured jobs that are running in parallel. When this option is selected, the jobs run the identify activity on the source and target datasets that are configured for the jobs and on all the other datasets. This ensures that the same Reconciliation ID is assigned to identical CIs in all the datasets and the data integrity is maintained.FalseRE-Parallel-Job-Run

Besides setting the core configuration parameters for reconciliation, you can configure the server settings and threads for the Reconciliation Engine. 

For setting up Reconciliation Engine logging, see Contents of the logs

Was this page helpful? Yes No Submitting... Thank you


  1. Jesus Diaz-ropero simon

    Hello, what about the contents of prev versions where the recon (identification and merge activities, and the others too) where explained with detail? BMC consider it's not important?, Thank you.

    Dec 29, 2020 04:14
    1. Maithili Deshpande

      Hello Jesus,

      Thank you for your feedback on the documentation. Please see the following topics from the documentation which we feel are relevant to your query:

      1. Creating a reconciliation job
      2. Identifying changes to CIs by using the Compare activity
      3. Copying CIs from one dataset to another
      4. Deleting CIs from a dataset by using the Delete activity
      5. Running reconciliation jobs in a sequence by using the Execute activity

      Please let us know if you are looking for some other information. If you want to contact Customer Support to log a formal ticket on this issue, click here.


      Jan 06, 2021 03:01