If you want to deploy a message flow to a
Version 2.1 broker
that is participating in a
Version 6.0 broker domain, the message
flow must not use any capability that is not present in
Version 2.1 brokers;
for example:
- The message flow must not contain any of the following built-in nodes:
- DataDelete
- DataInsert
- DataUpdate
- Extract
- HTTPInput
- HTTPReply
- HTTPRequest
- JavaCompute
- JMSInput
- JMSOutput
- JMSMQTransform
- MQJMSTransform
- Mapping
- MQGet
- Passthrough
- Real-timeInput
- Real-timeOptimizedFlow
- TimeoutControl
- TimeoutNotification
- Warehouse
- XMLTransformation
Use the following alternative nodes:
Node unavailable in Version 2.1 |
Alternative node |
Extract node |
Compute node |
Mapping node |
Compute node |
DataDelete node |
Database node |
DataInsert node |
Database node |
DataUpdate node |
Database node |
Warehouse node |
Database node |
- The message flow must not contain any of the following
elements in its ESQL files:
- A LOG or RESIGNAL statement
- An ACOS, ASIN, ATAN, ATAN2, COS, COSH, COT, DEGREES, EXP, FIELDNAMESPACE,
LEFT, LN, LOG, LOG10, POWER, RADIANS, RAND, REPLICATE, RIGHT, SIGN, SIN, SINGULAR,
SPACE, TAN, TANH, OR TRANSLATE function
- A PATH clause
- A BEGIN statement with an ATOMIC keyword
- A CREATE FUNCTION or CREATE PROCEDURE statement at schema level (i.e.
not within a module)
- A DECLARE statement that uses any of the EXTERNAL, HANDLER, NAMESPACE,
NAME, ROW, or SHARED keywords
- A DELETE statement that uses any of the FIELD, FIRSTCHILD, LASTCHILD,
PREVIOUS SIBLING, or NEXTSIBLING keywords
- A PROPAGATE statement with any clauses of any kind
- A CAST function with either of the DEFAULT or FORMAT keywords
- A POSITION function with either of the FROM or REPEAT keywords
- A SELECT function that is not enclosed in parentheses
- A dynamically calculated database data source name or schema name
- Any construct that attempts to change the Root or InputRoot message trees
In addition, the broker schema must not contain a mapping file.
These
conditions mean that the broker schema can contain only module definitions.
- When you add ESQL to a bar file that is being deployed
to Version 2.1, select the Compile
ESQL for broker Version 2.1 check box in the Broker Archive editor.
- There are restrictions on some parameters of existing
nodes:
- For input nodes that have a drop-down list of parsers, such as MQInput
and MQeInput, do not select the XMLNSC or MIME parsers.
For nodes that have parser options, such as MQInput and Compute,
do not specify non-default parser options.
- For the MQOutput node, do not specify non-default Validate options.