Configuring Reconciliation Engine system parameters
You can define system parameters for the Reconciliation Engine.
To modify the Reconciliation Engine system parameters
- From the Reconciliation console, click Edit Server Configuration.
- In the Server Configuration Editor, enter values for the following parameters:
|Name in the AR Configuration (ar.cfg or ar.conf) file|
Definition Check Interval (Seconds)
An expiration, in seconds, of the Reconciliation Engine's cache of job definitions. The default is 300. For 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 (Seconds)
The polling interval in seconds. The Reconciliation Engine "sleeps" until the next job is scheduled to run or for this interval whichever occurs first. Polling interval is used only when the dispatcher does not send a signal to the Reconciliation Engine. The default is 18000 seconds (5 hours).
Continuous Job Interval (Seconds)
The execution interval of a continuous job. The default value is 1800 seconds (30 minutes). If you set this value to less than 120 seconds (2 minutes), then the Reconciliation Engine converts that value to 120 seconds (2 minutes). For more information, see Creating a continuous reconciliation job.
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. Because the Reconciliation Engine uses many API calls for BMC Atrium CMDB, you should use only those ports reserved for BMC Atrium CMDB and not ports that BMC Remedy AR System can use.
Log File Path
Location of log files. The default location is <installDir>\Logs.
Amount of information to log. The following levels are available:
Note: When the logging level is set to Error, the Reconciliation Engine creates a new 0 byte log file for each run of a reconciliation job, even when the job is successful. You can choose to configure the deletion of 0 byte log files for individual reconciliation jobs. For more information, see Configuring the deletion of Reconciliation Engine job log files.
Maximum Job Log File Size (KB)
This option is used to control the size of the job log files. When the log file reaches its maximum size, it is renamed using the <jobName><n> file name syntax, and log messages continue to be written to the original file, which is now empty. A value of zero indicates no maximum file size. The default is 300KB.
Look Into Other Datasets for Parallel Jobs
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.
Maxmium ARRecond Log File Size (KB)
This option is used to control the size of the arrecond process log file. When the log file reaches its maximum defined size, it is renamed to arrecond_n.log and the logging is continued in the arrecond.log. A value of zero indicates that the limit on the maximum file size is not specified. In that case, the log file takes the default value. The default size is 20480KB. You can specify a value in the range of 0 to 2097152 KB. For more information on how to use this parameter see, Restricting the Reconciliation Engine log file size.
Job Idle Time (Minutes)
This is the time interval for which a job can remain idle. For BMC Atrium Core version 9.1 and later, the feature is disabled by default and the value is set to 0 minutes.
If you realize that an RE job is idle for more than 12 hours, BMC recommends 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 detailed information on the fail safe feature see, Monitoring reconciliation jobs using the fail-safe mechanism.