IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Managing conversion errors on converted legacy message maps

The conversion process creates a Task transform with an error when it cannot automatically convert a legacy message map transformation. You can use any of the transforms in the Graphical Data Mapping editor to reconstruct an equivalent transformation. Typically, you might use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic.

These errors are displayed in the Graphical Data Mapping editor as Task transforms marked with an error.

You can see the error description associated with the conversion in the Problems view or by hovering over the red exclamation symbol associated to a Task transform.

In the Graphical Data Mapping editor, open your converted map, and complete the following actions to resolve the error:

Select a Task transform.
The transform properties are displayed in the Properties view.
In the Properties view, click the Documentation tab to review details about the mapping structure that was not re-created by the conversion process.
In the Documentation tab of the transform, the map conversion process includes the mapping structure from your legacy message map. For example, you can find the following description for conversion of unsupported legacy transforms:
```
The expression {0} used for {1} cannot be automatically converted into a supported transform. \n\
Refer to {2} and manually create a transform with an equivalent expression.
```
Change the Task transform to a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform.
Click the arrow in the transform box, and select a transform from the list of available ones. For more information, see Editing message maps.
Configure the transform properties to manually re-create the transformation logic.

Check the following conversion error descriptions and the actions you can take to resolve them:

Conversion error descriptions	Action to resolve it
The statement {0} cannot be automatically converted into a supported transform. Refer to {1} and manually create mappings to perform the corresponding transformation.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic.
The expression {0} cannot be automatically converted into a supported transform. Refer to {1} and manually create a transform with an equivalent expression.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic. If the expression is `esql:coalesce`, see Limitations on the conversion of esql:coalesce calls.
The expression {0} used for {1} cannot be automatically converted into a supported transform. Refer to {2} and manually create a transform with an equivalent expression.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic.
The XPath function call {0} for {1} is not supported. Refer to {2} and manually create a transform with an equivalent expression.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic.
The message map contains an erroneous expression. An attempt is made to convert the expression. Refer to {0} and review the converted expression.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic.
The message map references a user-defined ESQL routine {0} which has an argument {1} of REFERENCE type. A routine with an argument of REFERENCE type cannot be called from the converted map. Refer to {2} and manually create a transform with an equivalent result.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic. For more information, see Converting a legacy message map that includes user-defined ESQL procedures.
The message map references a user-defined ESQL routine {0} which has an INOUT argument {1}. When a routine with an INOUT argument is called from the converted map, the argument must behave like an IN argument. Refer to {2} and the ESQL routine.	Check the Documentation tab of the Task transform to get details of the original expression. Use a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform to re-create the transformation logic. For more information, see Converting a legacy message map that includes user-defined ESQL procedures.

br40820_.htm |

Last updated Friday, 21 July 2017