Custom ESQL

In the Graphical Data Mapping editor, select Custom ESQL from the Custom Transforms list. You can then use the transform properties to select ESQL code stored in your workspace. When you select the ESQL route, the Parameters table Name and Type columns are populated. You must then select an input element or XPath expression in the Value column for each parameter. You can use the content assist in the Value column to help you to assign the required element, literal or XPath expression.

The ESQL file that contains the referenced ESQL module must be visible for mapping to be selectable. Ensure the application, library, or project references are set to make the ESQL file accessible to the map. When deploying the map, ensure the ESQL file is also deployed, and that Compile and in-line resources is not selected.

Requirements for ESQL modules called from a graphical data map

The following requirements apply to ESQL modules that are called from a graphical data map:

• The syntax of an ESQL procedure is shown in CREATE PROCEDURE statement. The procedures that can be called from a Custom ESQL transform in a graphical data map must conform to the following requirements:
  • Only IN parameters are allowed
  • A RETURN is required
• The input and return datatypes must be simple scalars; ESQL reference datatypes are not supported.
• An ESQL module with no inputs can be used to assign to an output element.
• Each input parameter to the ESQL module can be taken from an input element wired into the custom ESQL transform or specified as a constant.
• The ESQL must not include SQL calls to a data source. The Graphical Data Mapping editor provides facilities to include database operations in the map; see Mapping database content for more information.