Creating a Web service with WebSphere MQ as the transport

This scenario implements a Web service using WebSphere MQ as the transport mechanism and MIME as the domain. A message flow for this scenario, and the resulting message tree are given below:

This diagram shows an external MQ enabled client sending and receiving messages from a message flow. The message flow consists of a MQInput node connected to a Compute node. The Compute node is then connected to a MQOutput node. The reply message is sent back to the MQ client.

The diagram shows a logical message tree. The root of the tree is called Root, and it has four children. These are, in order, Properties, MQMD, MQRFH2, and MIME.

When a MIME message enters the message flow the Content-Type and any other top-level MIME headers are stored in the MIME tree. The broker also stores a copy of the Content-Type of the message as the ContentType value in the Properties subtree.

Any processing that this message flow needs to do is done in the Compute node. The output domain of this message flow is also MIME, therefore the output message must be a MIME tree. This tree can be made by either creating a new tree, or modifying the incoming MIME message tree using the Compute node. If the Content-Type of a message needs to be modified, updating the broker ContentType property. When this property is changed, the MIME tree is updated automatically.

The Coordinated Request Reply sample sample contains information about manipulating MQ headers and using the MQGet node.
Related concepts
Manipulating messages in the MIME domain
MIME tree details
MIME messages
Related tasks
Developing ESQL
Developing Java
Related reference
Creating a Web service with HTTP as the transport
Accessing a WebSphere MQ enabled application as a Web service
A WebSphere MQ enabled application calling a Web service