You can configure the nodes in your message flows to customize the behavior of those nodes by using one or more of the supported programming interfaces.
You can use one of the following options for converting message formats in your message flows:
You can use mappings in the Mapping node.
You can use ESQL in the Compute, Database, and Filter nodes.
You can use Java only in the JavaCompute node.
You can use XSL only in theXSLTransform node.
Use this option if your message flows are processing XML messages, and your message flow designers are familiar with the XSL style sheets.
You can use .NET in the .NETCompute node, and call .NET code from ESQL.
When you configure your message flows and nodes, you create a set of files that are stored in your workspace.
The files created are of the following types:
You can customize the following built-in nodes by creating free-form ESQL statements that use the built-in ESQL statements and functions, and your own user-defined functions:
You can include other files in your integration project so that they are deployed to the integration node with your message flow. The integration node stores these extra files but does not process them in any way.
For details of how to create the files to support these transform options, and create their content, see Transforming and enriching messages.