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 user-defined ESQL procedures

When you convert a legacy message map that includes ESQL procedures, the conversion process converts each ESQL procedure to an equivalent Custom ESQL transform that invokes the ESQL. A Task transform is added to your converted map when an ESQL procedure does not fulfill the requirements to be called from a map on a Mapping node.

Before you begin

Read the section Requirements for ESQL modules called from a graphical data map in the following topic: Custom ESQL

Procedure

Check the conversion process behavior when you convert a legacy message map to a message map that includes ESQL procedures:

  1. By default, the conversion process converts an ESQL procedure to a Custom ESQL transform. For more information, see Custom ESQL.

    Each converted ESQL procedure is deployed as source. If you are not using IBM® Integration Bus application and library projects to store your ESQL procedures, the ESQL procedures must be uniquely named because they are deployed independently to the same integration server.

  2. The conversion process converts an ESQL procedure that uses the ESQL REFERENCE data type to a Task transform.

    You must replace the Task transform with a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform that provides equivalent function.

  3. The conversion process converts an ESQL procedure that has an INOUT argument to a Custom ESQL transform where the INOUT argument is converted as an IN argument.

    You can replace the Custom ESQL transform with a Custom XPath transform, or a Custom Java transform when the default conversion transform is not valid.

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.


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