Best practices for BMC Helix Remedy integration

This section describes some configuration best practices for a seamless integration with BMC Helix Remedy.

Avoiding issues when importing large datasets

The connector supports delta uploads. Large amounts of data might slow down the system and cause issues. To avoid issues, it is recommended to do the following:

  • The Filters option in the connector configuration should be used to divide and upload the data in several stages. For example, one instance of the connector could be configured to upload only servers from Snow License Manager on day one and the second instance could be configured to upload only desktops.

  • The Upload settings option in the connector configuration should be used to set a lower number of instances to be uploaded to the BMC Helix Remedy server, if a higher number, or the default, impact the performance.

    The default settings are tested to be the best sizes, so increasing sizes will most likely cause issues.

  • While the connector is uploading data to the BMC Helix Remedy server, no normalizations and reconciliation jobs should be run simultaneously on the BMC Helix Remedy server.

  • If you have a large amount of data, schedule Snow Integration Manager to run right after the Data Update Job and select the checkbox Wait for Data Update Job to finish in the connector configuration. This creates the largest possible window to get the upload done.

Note

Timeouts might happen with large CI/Dependency batchsizes. If this occurs we recommend using the default sizes and change the filters to avoid uploading everything at once. This applies to first runs mostly, since the size of the upload is significantly smaller when the delta functionality is in place.