This scenario represents a Web service providing an interface to a WebSphere MQ enabled application using MIME as the domain.
A message flow for this scenario, and the resulting message trees are given below:
When a MIME message enters the message flow the top-level Content-Type of the message is stored in the HTTPInputHeader tree and in the MIME logical message 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 the message tree after the message has left the HTTPInput node:
SET OutputRoot.XMLNS.X.rid = CAST(InputLocalEnvironment.Destination.HTTP.RequestIdentifier AS CHARACTER);The diagram below shows the message tree after it has left Compute1:
If the application that is receiving the MQ message expects the message to be in a MIME format, a MIME tree is needed. Compute1 can supply this by either creating a new MIME tree, or modifying and propagating the existing MIME tree. To modify the Content-Type of the message, the broker ContentType property must be used. When the broker ContentType property is modified, the Content-Type property in the MIME tree is updated automatically.
SET OutputLocalEnvironment.Destination.HTTP.RequestIdentifier = CAST(InputRoot.XMLNS.X.rid AS BLOB);Compute2 can also set up an explicit HTTPReplyHeader.
If the output domain is MIME, a MIME tree must be created to output the message. Compute2 either creates a new MIME message, or modifies and propagates the input MIME message as required to create the output message. The following diagram shows the message tree after it has gone through Compute2: