This documentation supports the 19.02 version of BMC Atrium Core.

To view the latest version, select the version from the Product version menu.

Improving the performance of Atrium Integrator

The performance of Atrium Integrator depend on your network, BMC Remedy AR System, the BMC Remedy AR System server database, and the external data store load. Predicting the effect of a specific change on Atrium Integrator performance is difficult, but configuration considerations can influence performance. 

Although it is easy to add field mappings or extra transformations for each field, remember that each item you add is compared against every record in your database. Seemingly minor additions could have a major impact if your database contains many records. For example, if you have 1200 records in your database and a change adds an additional half-second to the run time for each record, the data transfer might take an additional 10 minutes to run.

Related topics

Transferring data from external datastores to BMC CMDB

Managing the archiving process policies in the AR System Archive manager console


Best practices to improve the performance of Atrium Integrator

Best practiceReference
To prepare the data for transfer, create index entries on:
  • The BMC_BaseElement class for keys that are used as primary keys in the CMDB Output plugin and DatasetId in Atrium Integrator Spoon.
  • External data stores for transformations with the External Data to CMDB data direction and for relationship transformations.

Transferring data from external datastores to BMC CMDB

Provide minimum and maximum values for the Fast Thread and List Thread options in the BMC Remedy AR System Administration Console.

Defining queues and configuring threads

Launch multiple copies of a step. For optimum performance, you can launch 20 copies of a step. You can also use the following formula:
Number of copies=Number of CPUs x 3 threads
Launching several copies of a step to improve the performance of Atrium Integrator.

For all data transfer jobs created by using the Integration Job Builder wizard, the CMDBOutput step is set to launch three times. Depending on the configuration of your computer, you can increase the number of copies of the CMDBOutput step to increase the overall throughput of the data transfer job. BMC recommends that you set the number of copies to not more than ten.

Launching several copies of a step to improve the performance of Atrium Integrator.
To run a bulk job (more than one million) from the Atrium Integrator console, the JVM size of the Carte server must be minimum 2GB. To increase the JVM size of Carte server, update the required JVM size in armonitor.conf file.

armonitor.conf or armonitor.cfg

Set the Is Cache Required option to Yes to improve performance in update cycle.

Increasing cache size for Atrium Integrator


Archiving policies to improve the performance of Atrium Integrator

Atrium Integrator sometimes may experience slow performance when loading UDM (Unified Data Model) jobs execution forms or job log data forms. This occurs due to an accumulation of job logs that get created on every job execution and this eventually slows the performance of the job log forms.

Archiving policies

There are two default archiving policies for UDM archiving:

  • UDM Job Log Archival policy – for archiving job runs and all its sub jobs and contained transformations.
  • UDM Transformation Logs Archival policy – for archiving transformations and all its contained transformations.

These are defined for the age of 90 days and enabled by default. You can override this policy using settings in the AR System Archive Manager Console. You can disable the policies, define custom age, and so on. You can also run the archiving whenever you need to improve performance.

Forms archived by default

The following are the forms where data gets accumulated:

  • UDM:JobLog
  • UDM:JobEntryLog
  • UDM:TransformationLog
  • UDM:StepLog

Archiving of the data from these forms is set by default. 

Archiving associations

The following associations are defined in the default archiving policy:

  • UDMJobLog_UDMJobEntryLog
  • UDMJobLog_UDMStepLog
  • UDMJobLog_UDMTransformationLog
  • UDMTransformationLog_UDMStepLog

Associations form the basic structure for operations such as cascade delete and other functionalities in AR System. 

Hierarchy of archiving data

To modify the archiving policy to optimize the performance of Atrium Integrator

The default archive policies for UDM job logs and UDM transformation logs defined in the AR System Archive Manager Console prevent the accumulation of job logs by archiving them. You can customize the archive policy settings in the AR System Archive Manager Console according to how often you want the forms to be archived. 

Change the default archive policy settings for the UDM job logs and UDM transformation logs for optimum performance of the Atrium Integrator.

  1. Login to the Mid Tier with your credentials.
  2. Select Applications > AR System Administration > AR System Archive.
    The AR System Archive Manager Console opens.
  3. For UDM Job Logs Archival Policy and UDM Transformation Logs Archival, change the value of the Default Policy Age in Days according to your business needs.

To disable server group archiving after an upgrade


Login to the Mid Tier with your credentials.After upgrading Atrium Integrator and BMC CMDB, you may have a large amount of data in the UDM job log and the UDM transformation log that matches the archiving policy criteria. This may cause an initial load on the server as it tries to archive the backlog. To avoid this, you must disable the server group archiving after an upgrade.

  1. Select Applications > AR System Administration > AR System Archive.
    The AR System Archive Manager Console opens.
  2. Clear the Enable Server Group Archive check box.

    Select the Enable Server Group Archive check box later when the server has minimum load.


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

Comments