The PATH feature is optional and specifies a list of external schemas, separated by commas, through which to search.
This definition provides compatibility with previous WebSphere Business Integration Message Broker versions. The broker ESQL generated by the Eclipse tooling set when the unnamed schema is the only schema referenced does not contain the new syntax.
The PATH feature is used to resolve unqualified function and procedure names in the tools according to the following algorithm.
The <node schema> is the schema containing the node's message flow. The name of this schema is given by the last segment of the message processing node uuid in the broker XML message.
Whatever happens next depends on whether the caller is in a module routine or is a schema routine.
The <node schema> is defined as the schema containing the node's message flow. The name of this schema is given by the last segment of the message processing node uuid in the broker XML message.
The <node schema> is specified in this manner to provide backward compatibility with previous versions of WebSphere Business Integration Message Broker
When the <node schema> is the only schema referenced, the broker XML message does not include the extra features contained in WebSphere Business Integration Message Broker V5.0.
Brokers in previous versions of WebSphere Business Integration Message Broker do not support multiple schemas, for example, subroutine libraries for reuse. To deploy to a broker in a previous version of the product, put all ESQL subroutines in the same schema as the message flow and node that is invoking them.
Eclipse tooling uses WebSphere Business Integration Message Broker V5.0 ESQL syntax in content assist and source code validation. When generating broker ESQL code, the Eclipse tooling can generate V2.1 style code for backward compatibility.
Without the presence of any of the preceding items, the Eclipse tooling generates broker ESQL without MODULE and FUNCTION Main wrappers. This style is accepted by both V2.1 and V5.0 brokers. However, if you use a V2.1 broker, you cannot use any V5.0 syntax in the code, for example, namespace
Functions and procedure names must be unique within their SCHEMA or MODULE.
Related concepts
ESQL
Related tasks
Developing ESQL
Related reference
Syntax preference
ESQL statements
BROKER SCHEMA statement
CREATE MODULE statement
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ak05105_ |