Conditions for deploying a message flow to a Version 2.1 broker
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 satisfy the following conditions:
The message flow must not contain any of the following built in nodes:
DataDelete
DataInsert
DataUpdate
Extract
HTTPInput
HTTPReply
HTTPRequest
JavaCompute
JMSClientInput
JMSClientOutput
Mapping
MQGet
Passthrough
Real-timeInput
Real-timeOptimizedFlow
TimerInput
Warehouse
XMLTransformation
You can use a Compute node instead of an Extract or Mapping node, and
use a Database node instead of a DataDelete, DataInsert, DataUpdate, or Warehouse
node.
The broker schema of the message flow must not contain, at the schema
level, any of the following in its ESQL files:
A PATH statement
The declaration of a constant, which includes a NAMESPACE or NAME constant
The definition of a function
The definition of a procedure
In addition, the broker schema must not contain a mapping file.
These
conditions mean that the broker schema can contain only module definitions.
No module in the broker schema of the message flow can contain any of
the following:
A call to a procedure that is not defined within the module. However,
the module can call a procedure that is defined within the module.
The use of a function that is not defined within the module. However,
the module can use a predefined function, or a function that is defined within
the module.
The declaration of a constant, which includes a NAMESPACE or NAME constant.