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


Converting a legacy message map that includes calls to message map functions

The conversion process converts a number of supported calls to predefined legacy message map functions (msgmap:functionName) to an XPath expression, or a Custom XPath transform.

About this task

If there is no XPath equivalent of a message map function, the conversion process creates a Task transform instead.

The following legacy message map functions have no XPath equivalent:
  • msgmap:element-from-bitstream
  • msgmap:cdata-element
  • msgmap:db-path

Procedure

Complete the following steps to convert a transformation that includes a call to a message map function that is not converted automatically:

  1. Select a Task transform.
  2. In the Task transform Properties view, check out the information provided in the Documentation tab.
  3. Replace the Task transforms with any of the available transforms. Consider using a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform.
  4. Manually re-create the equivalent transformation logic of the message map function.

What to do next

Continue converting your legacy message map. For more information, see Converting a message map from a .msgmap file to a .map file.


br40821_.htm | Last updated 2015-05-28 20:53:08