MQ Nodes
MQ Input Node:
It is used to receive the messages from MQ queue. The messages will be received from broker associated queue manager.
This is the starting node in a message flow and use MQGET call to read the message from the queue.
Once the broker MQ flow was deployed, the Integration server process polls the queue for the messages.
Terminals:
Out terminal: To which the message is routed if successfully retrieved from the queue.
Catch terminal: To which the message will be routed if an exception is caught
Failure: The messages will be routed to this terminal if any error occurs
Following domains will handle the message parsing in this Input node they are:
- For binary or text messages with a Data Format Description Language schema model(DFDL)
- For XML messages namespace aware, validation, low memory use( XMLNSC)
- For data from Web Sphere Adapters, CORBA and Database records (Data Object)
- For JavaScript Object Notation messages(JSON)
- For messages with an unspecified format (BLOB)
- For MIME wrapped data including multipart (MIME)
- For binary or text messages that are modeled in a message set(MRM)
- For JMS Map Message messages (XML) JMS Map
- For JMS Stream Message messages (XML) JMS Stream
- For XML messages (namespace aware) XMLNS
MQ Output Node:
This Node will put the message to the queue
Terminals: in, out and failure.
Persistent Mode:
Automatic: The persistence property of the message is taken from the incoming message.
If yes: The message is put persistently.
No: The message is put as non-persistent.
MQ Header Node:
In this node we can Add or modify or delete the MQ message header or the dead letter header.
Terminals: in, out and failure.
This node does not modify the message body.
MQ Get Node:
It is used to get a message from the queue anywhere in the message flow except the flow starting node.
Wait interval: The max time is in milliseconds for the node to wait for the message in the queue.
MQ Reply Node:
This node will send the reply to the originator of the message. This node will get the reply from queue and the queue manager name fields from the MQ header.