Managing ESQL files
In an application, library, or integration project, manage ESQL files that contain the ESQL code that you provide to modify or customize the behavior of Compute, Database, DatabaseInput, and Filter nodes.
About this task
The ESQL code for a message flow node is contained in a module that is associated with the node.
Each module must be created in an ESQL file (file extension
.esql) . You can change the name of the module in the ESQL
file from its default value of
MessageFlow_NodeName,
where MessageFlow is the name of the message flow and
NodeName is the name of the message flow node. The name of
the module in the ESQL file must match the name specified for the module in the
ESQL Module property of the
corresponding message flow node.
By default, ESQL files are deployed to the integration server as individual resources, and can be edited and redeployed without redeploying the message flows that reference them. Alternatively, you can include the code from an ESQL file directly in the compiled message flow (.cmf file) that references it. Compiled message flows that include ESQL code in this manner must be redeployed each time you change the ESQL code. For more information, see Adding resources to a BAR file.