This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

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

Viewing migrated data exchanges in Atrium Integrator

This section provides information about how the different types of data exchanges in BMC Atrium Integration Engine data are migrated to Atrium Integrator. You can use this information to verify that your data exchanges have been successfully migrated to Atrium Integrator.

When you migrate data exchanges from BMC Atrium Integration Engine to Atrium Integrator and if the jobs fail to publish, the .ktr files of the jobs are available:

  • (Microsoft Windows) %USERPROFILE%
  • (UNIX) the home directory

The AIE to AI Migration Tool migrates active and inactive data exchanges as corresponding jobs in Atrium Integrator. However, all migrated jobs are active because Atrium Integrator does not have a corresponding inactive status.

When the AIE to AI Migration Tool migrates CSV and XML data exchanges as jobs in Atrium Integrator, if space is used in a field or column in the CSV or XML file, then the space is replaced by an underscore.

The following table describes how data exchanges are migrated to Atrium Integrator.

Mapping data exchanges to jobs and transformations in Atrium Integrator

BMC Atrium Integration Engine Data exchange type Schedule Only Event Driven Only To Be Triggered Migrated to Atrium Integrator
  • AR
  • CI Class
Yes No Yes Yes (as a transformation of the job that triggers this data exchange)
Yes No No Yes (as a standalone job)
No Yes Yes Yes (as a transformation of the job that triggers this data exchange)
No Yes No No
Relationship Class Yes No Yes Yes (as a transformation of the job that triggers this data exchange)
Yes No No No
No Yes Yes Yes (as a transformation of the job that triggers this data exchange)
No Yes No No
Was this page helpful? Yes No Submitting... Thank you

Comments