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.

Migration of data mappings to Atrium Integrator

The following topics are provided:

Migration of data mappings 

Data mappings in BMC Atrium Integration Engine define how data in the source corresponds to data in the target and which actions to take when transferring the data.

  • BMC Atrium Integration Engine enables you to specify multiple data mappings for a data exchange. However, the AIE to AI Migration Tool migrates only the first main data mapping that is defined for a data exchange. You must migrate data mappings one at a time.
  • The AIE to AI Migration Tool does not migrate the delete and response fields.
  • The AIE to AI Migration Tool does not migrate queries that are set for data mappings.
    You can only map zero or one to a response field and not to any CMDB field. However, mapping of other CMDB fields as response is possible through BMC Atrium Integrator Spoon by modifying the UpdateResponse step.
  • In BMC Atrium Integration Engine data exchange, if the data set ID is not mentioned at the main mapping level, the data set ID specified at the Data Field Mapping level is used. If the data set ID is not mentioned even at the Data Field Mapping level, BMC.SAMPLE is used as the data set ID.

The AIE to AI Migration Tool migrates a subset of the rules that can be defined for the data mappings in BMC Atrium Integration Engine. However, if in BMC Atrium Integration Engine the rule is disabled or if the syntax is wrong, then the AIE to AI Migration Tool does not migrate the associated attribute.

The rules are migrated to Atrium Integrator as Java code. For example, if you have defined a rule that uses the timestamp() function, the AIE to AI Migration Tool creates the following Java code for that rule in Atrium Integrator:

public boolean processRow(StepMetaInterface smi, StepDataInterface sdi) throws KettleException{

Object[] r = getRow();
if (r == null) {
setOutputDone();
return false;
}
if (first){

first = false;
}r = createOutputRow(r, r.length+5);
String o = getData(r);
putRow(data.outputRowMeta, r);
return true;
}
private String getData(Object[] r) throws KettleException{
String rule1 = timestamp();
get(Fields.Out, "AssignedTo_100").setValue(r, rule1);
return null;
}
private static String concat(String[] strArray){
String str = "";
for(int i=0; i<strArray.length; i++){
str = str + strArray[i];
}return str;
}


For more information about the rule and function syntax in BMC Atrium Integration Engine and the corresponding Java code in Atrium Integrator, see Mapping BMC Atrium Integration Engine rules and function syntax with corresponding Java output in Atrium Integrator.

Recommendation

After migrating rules to Atrium Integrator, verify if rules are migrated correctly.

To verify if rules are migrated correctly to Atrium Integrator

  1. Open the transformation in Atrium Integrator Spoon.
  2. Double-click the Set Rules step.
  3. Click Test Class.
    If there are any errors in the migrated rules an error occurs.
Was this page helpful? Yes No Submitting... Thank you

Comments