Improving the performance of Atrium Integrator
The performance of Atrium Integrator depends on your network, Action Request System, the AR System server database, and the external data store load.
Best practices to improve the performance of Atrium Integrator
Best practice | Reference |
|---|---|
To prepare the data for transfer, create index entries on:
| |
Provide minimum and maximum values for the Fast Thread and List Thread options in the Action Request System Administration Console. | |
Launch multiple copies of a step. For optimum performance, you can launch 20 copies of a step. You can also use the following formula: | |
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. | |
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. | |
Set the Is Cache Required option to Yes to improve performance in update cycle. |
Archiving policies to improve the performance of Atrium Integrator
You can modify archiving policies to improve the performance of Atrium Integrator. When loading UDM (Unified Data Model) jobs execution forms or job log data forms, Atrium Integrator may sometimes experience slow performance due to an accumulation of job logs that get created after every job execution. You can define archiving policies to archive this data to improve the performance of Atrium Integrator.
Archiving policies
There are two default archiving policies for UDM:
- 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 policies are defined for the age of 90 days and enabled by default. You can override this policy by 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 policies whenever you need to improve the performance of Atrium Integrator.
Forms archived by default
Data gets accumulated in the following forms:
- UDM:JobLog
- UDM:JobEntryLog
- UDM:TransformationLog
- UDM:StepLog
Data is set to be archived from these forms by default.
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 age to optimize the performance of Atrium Integrator
The default archiving policies for UDM job logs and UDM transformation logs defined in the AR System Archive Manager Console prevent the accumulation of job logs. You can customize the archiving policy age settings in the AR System Archive Manager Console according to how often you want the forms to be archived.
- Log in to the Mid Tier with your credentials.
- Select Applications > AR System Administration > AR System Archive.
The AR System Archive Manager Console opens. - For UDM Job Logs Archival Policy and UDM Transformation Logs Archival, change the value of Default Policy Age in Days according to your business needs.
To disable server group archiving to avoid overloading the server
After upgrading Atrium Integrator and BMC Helix CMDB, you might have a large amount of data in the UDM job log and the UDM transformation log that matches the archiving policy criteria. This might cause an initial load on the server as it tries to archive the backlog. To avoid this, you must disable server group archiving after an upgrade.
- Log in to the Mid Tier with your credentials.
- Select Applications > AR System Administration > AR System Archive.
The AR System Archive Manager Console opens. - Clear the Enable Server Group Archive check box.
You can select the Enable Server Group Archive check box later when the server has minimum load.
Impact of adding extra transformations on data transfer time
Although it is easy to add field mappings or extra transformations for each field, each item you add is compared against every record in your database. Minor additions may 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.