bk40720_.htm |
Last updated Friday, 21 July 2017By default, ESQL files are deployed in BAR files as individual resources, and can be edited and redeployed without redeploying the message flows that reference them.
This topic assumes that you have created an ESQL file. For more information, see Creating ESQL for a node.
When you create a broker archive (BAR) file and add your message flow, the IBM® Integration Toolkit packages any ESQL files that are referenced by the message flow into the BAR file. If the ESQL code references additional ESQL files that are not directly referenced by the message flow, the additional ESQL files must be added to the BAR file manually before it is deployed.
Optionally, 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 files to a broker archive.
Deployed ESQL files are displayed in the Integration Nodes view. If your messaging solution uses applications or libraries, deployed ESQL files are displayed under the application or library to which they were deployed. If your messaging solution does not use applications or libraries, deployed ESQL files are displayed under the integration server to which they were deployed.
Last updated Friday, 21 July 2017