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.

Limitations of AIE to AI Migration Tool when migrating data exchanges

The following table describes the limitations with the AIE to AI Migration Tool when you migrate data exchanges from BMC Atrium Integration Engine to Atrium Integrator.

Limitations of AIE to AI Migration Tool

For a quick overview of limitations, see Limitations of AIE to AI Migration Tool  video. This video is recorded using the earlier version of BMC Atrium Core and is valid for BMC Atrium Core 9.1.

Limitation

Impact/Workaround

The AIE_Configuration.arx file created from BMC Atrium Integration Engine export utility is not migrated to Atrium Integrator.

Not supported.

Instance names for data exchanges from BMC Atrium Integration Engine are not migrated to the corresponding jobs in Atrium Integrator.

In Atrium Integrator, all migrated data exchanges run under a single carte server.

Relationship type of data exchange is migrated as a child transformation of CI Class.

Change the Execute Exchange Asoption to Even Driven Only from Schedule Only to migrate the job.

If in BMC Atrium Integration Engine, if the data has two double quotes in any rule, then that data is not recognized by Atrium Integrator. For example, the following data will not be recognized by Atrium Integrator. STMT|IF $'HOST CITY'$ = ""UPS P0012 (NEW YORK, UNITED STATES)"" THEN VALUE = "NULL" ELSE VALUE = "SUCCESS" ENDIF

To support the usage, modify the rule in the Set Rules step in the transformation.

The AIE to AI Migration Tool does not migrate data exchanges containing external data stores as flat files with .dat files.

AIE to AI Migration Tool only migrates external data stores as flat files with CSV files. To migrate such exchanges before migrating you need to convert the .dat file to .csv.

To convert a .dat file to .csv:

  1. Replace all back slashes in the .dat file with comma.
  2. Remove the first comma.
  3. Add the field names from the .tbl file to the .dat file as headers.
  4. Save the .dat file as .csv.

If the Delete according to data mapping option is selected with Permanently delete option, then the data exchange is migrated to Atrium Integrator with Soft delete option.

Records won't be deleted physically from the database. Atrium Integrator does not support permanent (hard) delete.

Data types of fields in XML files are not migrated to Atrium Integrator.

By default the data type for XML files will be a string. You need to modify the data type in BMC Atrium Integrator Spoon. For more information about data types, see Atrium Integrator supported data types.

CMDB export (CMDB to external data stores) delete data exchanges are not migrated to Atrium Integrator.

Create a new job in Atrium Integrator. You can refer to the sample delete jobs.

AR System import (external data store into AR System) and AR System export (AR System into external datastore) delete data exchanges are not migrated to Atrium Integrator.

Not supported.

$SRC qualifiers in the mapping cannot be migrated for export type of data exchanges.

After you migrate the data exchange, open the job in BMC Atrium Integrator Spoon and modify the mapping.

$Key$=$KEYLIST$ qualifiers in the mapping cannot be migrated.

After you migrate the data exchange, open the job in BMC Atrium Integrator Spoon and modify the mapping.

For CSV/XML export type of data exchanges, rules are migrated but, output value of the rules are not mapped to any output field of CSV/XML.

Create new fields in the CSV/XML and assign the value of the rules to that output fields.

A chain (to be triggered) of the BMC Atrium Integration Engine relationship based data exchanges is not migrated to Atrium Integrator. Only the first data exchange in the chain is migrated.

You can open a sub job in Atrium Integrator and add transformations in a to be triggered relationship chain.

When you run an AR System or CMDB export type job for CSV and XML from BMC Atrium Integrator Spoon, the updated record count is not displayed in the Updated Column of the Step Matrix.

You can look for the updated records information in the CSV or XML file. Or you can also find this information in the log file.

If a BMC Atrium Integration Engine data exchange is having a Class-based relationship or Vendor-based relationship with delta and it is migrated, a query is formulated in Table input with ModifiedDate field, which is not available in Table input and thus the corresponding job may not run. However, if the secondary data exchange has delta then the data exchange is migrated and the corresponding job runs correctly.

If secondary data exchange is non-delta or if the delta information is not displayed correctly, manually change the Table input in the delta field in the relationship transformation with proper LMT field.

The AIE to AI Migration Tool does not migrate AR System type of data exchanges with Delta setting.

Not supported.

The AIE to AI Migration Tool does not migrate data exchanges that use same class as used in the Relationship. For example, if you create data exchange for class BMC_ComputerSystem and create Relationship exchanges and mapping with same class BMC_ComputerSystem and used this Relationship in To Be triggered mode with exchanges, in this case, the data exchange is not migrated.

Not supported.

Checksum for relationship mapping is not migrated.

Manually add a character type attribute in the BaseRelationship and then proceed with configuring the checksum.

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

Comments