This topic contains the following sections:
Use the MQeOutput node to send messages to clients that connect to the broker using the WebSphere MQ Mobile Transport protocol.
The MQeOutput node forwards messages to WebSphere MQ Everyplace queue managers. If you specify a non-local destination queue manager, ensure that there is either a route to the queue manager, or store-and-forward queue servicing for the queue manager, if it exists.
You cannot use the MQeOutput node to change the transactional characteristics of the message flow. The transactional characteristics that are set by the message flow's input node determine the transactional behavior of the flow.
You cannot use MQeOutput nodes in message flows that you deploy to z/OS systems.
If you create a message flow to use as a subflow, you cannot use a standard output node; you must use an instance of the Output node to create an out terminal for the subflow through which to propagate the message.
If you do not want your message flow to send messages to a WebSphere MQ Everyplace queue, choose another supported output node.
The MQeOutput node is represented in the workbench by the following icon:
For an example of how this node can be used, consider a farmer who checks his fields to see how well they are irrigated. He is carrying a PDA device with WebSphere MQ Everyplace installed. He sees that his fields are not being irrigated, and uses his PDA and a Global Satellite Navigation link to check the water flow valve, and finds that it is faulty. This information is available because the remote SCADA device that is responsible for controlling the valve has published a diagnostic message, which was retrieved by the broker and forwarded to an MQeOutput node and on to the WebSphere MQ Everyplace client on his PDA.
You can find further information about WebSphere MQ Everyplace, and the properties of the node, in the WebSphere MQ Everyplace documentation on the WebSphere MQ Web page.
When you have put an instance of the MQeOutput node into a message flow, you can configure it. To display its properties, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.
Configure the MQeOutput node as follows:
Connect the In terminal to the node from which outbound messages bound are routed.
Connect the Out or Failure terminal of this node to another node in this message flow if you want to process the message further, process errors, or send the message to an additional destination. If you propagate the message, the LocalEnvironment that is associated with the message is enhanced with the following information for each destination to which the message has been put by this node:
These values are written in WrittenDestination within the LocalEnvironment tree structure.
If you do not connect either terminal, the LocalEnvironment tree is unchanged.
If you use aggregation in your message flows, you must use these terminals.
The MQeOutput node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts a message for processing by the node. |
Failure | The output terminal to which the message is routed if a failure is detected when the message is put to the output queue. |
Out | The output terminal to which the message is routed if it has been successfully put to the output queue, and if further processing is required within this message flow. |
The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The MQeOutput node Description properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type, MQeOutput | The name of the node. |
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
The MQeOutput node Basic properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Queue Manager Name | No | Yes | The name of the WebSphere MQ Everyplace queue manager to which the output queue, which is specified in Queue Name, is defined. | |
Queue Name | No | Yes | The name of the WebSphere MQ Everyplace output queue to which this node puts messages. |
The MQeOutput node Advanced property is described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Destination Mode | Yes | No | Destination List | The queues to which the output message is sent. Valid values are Queue Name, Reply To Queue, and Destination List. |
The MQeOutput node Request properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Request | Yes | No | Cleared | If you select the check box, each output message is generated as a request message. |
Reply-to queue manager | No | Yes | The name of the queue manager to which the output queue, which is specified in Reply-to queue, is defined. | |
Reply-to queue | No | Yes | The name of the reply-to queue to which to put a reply to this request. |