This topic provides further information about how to configure nodes in a message flow to handle particular situations.
Although you can also set the reply status in the special header (X-Original-HTTP-Status-Code in the HTTPReplyHeader section of the output message which overrides all other settings) in a Compute node, you are recommended to use the LocalEnvironment content for this purpose.
For example, if you design a pair of message flows that interact with an existing WebSphere MQ application (as described in Working with Web services example scenarios), you can save this value in the request flow and restore it in the reply flow to ensure that the correct client receives the reply. If you do so, you must not change the data, and you must retain the data as a BLOB.
The HTTPReply node extracts this value from LocalEnvironment and sets up the reply so that it is sent to the specific client.
If you design a message flow that includes both an HTTPInput and an HTTPReply node, the value is set into the LocalEnvironment by the HTTPInput node, but the HTTPReply node does not use it. Therefore if your message flow includes both nodes and a Compute node in the same flow, you do not have to include the LocalEnvironment tree when you specify which components of the message tree are copied from input message to output message by the Compute node (the Compute mode property).
Although you can also set the request URL in the special header X-Original-HTTP-URL in the HTTPRequestHeader section of the request message (which overrides all other settings) in a Compute node, you are recommended to use the LocalEnvironment content for this purpose.
The HTTPReply node always rewrites the Content-Length header (even if you have cleared the Generate default HTTP headers from input or response check box) to ensure that its content is correct.
All other headers are copied from the HTTPResponseHeader. After this, if no Content-Type header exists, it is added with a value of text/xml; charset=utf-8.
If an HTTPReplyHeader section existed in the message received by the HTTPReply node, and the Output terminal of the HTTPReply node is connected, the HTTPReplyHeader section is updated with any changed or added values.
The HTTPRequest node always rewrites the Content-Length header (even if you have cleared the Generate default HTTP headers from input check box), to ensure that its content is correct.
All headers are copied from the HTTPInputHeader except:
Several headers are generated with default values if they are not found in the incoming HTTPRequest or HTTPInput headers:
Any header that is present in an HTTPRequestHeader in the message received by the node overrides a header with the same name that is also present in an HTTPInputHeader in the same message. If an HTTPRequestHeader exists in the received message, the HTTPRequestHeader is updated with any changed or added values.
Related concepts
WebSphere MQ Web Services Transport
Generate Web Services Description Language (WSDL)
Related tasks
Creating a message flow
Working with Web services example scenarios
Deploying message flow applications
Checking the results of deployment
Related reference
HTTPInput node
HTTPReply node
HTTPRequest node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac20450_ |