WebSphere Message Brokers
File: ak09030_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:32:39

Developing ESQL

When you use the built-in nodes Compute, Database, and Filter, you must customize them to determine the exact processing that they provide. To do this, you must create, for each node, an ESQL module in which you code the ESQL statements and functions to tailor the behavior of the node, referring to message content, or database content, or both, to achieve the results that you require. ESQL modules are maintained in ESQL files, managed through the Broker Application Development perspective.

This section provides information on:

You can use the ESQL debugger, which is part of the flow debugger, to debug the code that you write. The debugger steps through ESQL code statement by statement, so that you can view and check the results of every line of code that is executed.
Note: In previous releases there were several types of debugger, each of which handled a specific type of code, such as ESQL, message flows, or Java. In Version 6, these are integrated into a single debugger, which is known simply as "the debugger", and which handles all types of code.
Related concepts
ESQL overview
Message flows overview
Message mappings overview
ESQL nodes and debugging
Related tasks
Developing message flows
Debugging ESQL
Accessing broker properties from ESQL
Related reference
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:32:39

ak09030_ This topic's URL is: