The SOAPRequest node
has a property called Use WS-Addressing, for processing
WS-Addressing information that is present in the incoming message.
If
you select this property, the WS-Addressing information is processed
and the process itself is called engaging WS-Addressing.
The default is that WS-Addressing is not engaged.
You can also
specify this property in the WSDL and this is configurable from the
WSDL, automatically by the
IBM® Integration Toolkit,
when the WSDL is dragged onto the node. The behavior of the node when
WS-Addressing is engaged or not is as follows:
- Addressing not engaged
- The node does not add any WS-Addressing headers to the outgoing
message, and does not process any WS-Addressing headers that might
be present in the response message that is received by the node.
- Addressing engaged:
- The node first looks at the Destination.SOAP.Request.WSA folder
in the local environment. If this folder is empty, the
node automatically generates all required WS-Addressing Message Addressing
Properties (MAPs) in the outgoing message, by using the following
default values:
- Action, from the WSDL configuration file. If
this is not explicitly specified, this defaults to the value that
is defined in the WSDL Binding specification.
- To, from the Web Service URL node
property.
- ReplyTo, by using the special Anonymous address
(assuming that the Operation being used is not a one-way message exchange
program, in which case a ReplyTo by using the special None address
is specified).
- MessageID, a unique UUID is used.
If the Destination.SOAP.Request.WSA folder
in the LocalEnvironment is not empty, any user supplied MAPs override
the default ones that were listed previously, on a property by property
basis.
After the response to the request is received and if
the Place WS-Addressing Headers into
LocalEnvironment check box is selected on the SOAPRequest node, the SOAPRequest node removes all
WS-Addressing headers from the response message and places them in
the SOAP.Response.WSA folder. This folder allows
you to query the headers in a similar manner to the way the SOAPInput node deals with the
Input WS-Addressing headers.