This scenario represents an application that uses WebSphere MQ to make a call to a Web service while processing a message. The MIME domain is used for this example. A message flow for this scenario, and the resulting message trees 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. The diagram below shows some of the message tree after it has left the MQInput node:
The first Compute node, Compute1, is used to set up the HTTPRequestHeader if one is required. Compute 1 can also be used to create a new MIME tree or to modify the existing MIME tree if the intermediate application providing the Web service requires a MIME message.
SET OutputRoot.MQMD = InputRoot.MQMD; SET OutputRoot.MIME = InputRoot.MIME;
HTTPRequest node properties control the content of output tree.
The diagrams below show the message tree before and after making the Web service call in the HTTPRequest node:
Compute2 is used to create or restore an MQMD if one is needed, and to tidy up the tree to remove inappropriate headers such as the HTTPResponseHeader.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac30050_ |