Accessing integration node properties from ESQL

You can access integration node properties, at run time, from the ESQL modules in your message flow nodes.

About this task

You can use integration node properties on the right side of regular SET statements. For example: 
DECLARE mybroker CHARACTER;
SET mybroker = BrokerName;
where BrokerName is the integration node property that contains the name of the integration node on which the message flow is running. However, you cannot use integration node properties on the left side of SET statements. This restriction exists because, at run time, integration node properties are constants: they cannot be modified, therefore their values cannot be changed by SET statements. If a program tries to change the value of an integration node property, the error message Cannot assign to a symbolic constant is issued.
Integration node properties:
  • Are grouped by integration node, integration server, flow, and node.
  • Are case sensitive. Their names always start with an uppercase letter.
  • Return NULL if they do not contain a value.

If your ESQL code already contains a variable with the same name as one of the integration node properties, your variable takes precedence; that is, your variable masks the integration node property. To access the integration node property, use the form SQL.<broker_property_name>. For example: SQL.BrokerName.

Integration node properties that are accessible from ESQL, the Mapping node, and Java shows the integration node, flow, and node properties that are accessible from ESQL and indicates which properties are also accessible from Java.