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:
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, update the broker ContentType property. When this property is changed, the MIME tree is updated automatically.
The following sample contains information about manipulating MQ headers and using the MQGet node: You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.