Integration Server 10.15 | Web Services Developer’s Guide | Web Services Addressing (WS-Addressing) | WS-Addressing Behavior of Web Service Descriptors | Behavior for Outbound Messages
 
Behavior for Outbound Messages
The following table describes whether Integration Server adds WS-Addressing headers to provider outbound response messages or consumer outbound request messages based on the setting of the wsdl:required attribute of the wsaw:UsingAddressing assertion in the attached policy:
wsdl:required attribute is set to...
Integration Server...
true
Includes WS-Addressing headers in the outbound message.
For an outbound response message, the provider includes:
*A wsa:Action header with a value that is explicitly or implicitly associated with the corresponding WSDL definition, for example, the Action attribute in the WSDL document.
*A wsa:MessageID header with a unique identifier that is specified in the web service connector or generated by Integration Server.
*A wsa:RelatesTo header with the value of the wsa:MessageID of the associated request message.
*A wsa:To header with the value of the destination address.
*A wsa:ReplyTo header with the endpoint address for the web service to execute.
*A wsa:FaultTo header with the endpoint address for the web service to execute.
*A wsa:From header for the source address.
For an outbound request message, the consumer includes:
*A wsa:To header with the endpoint address for the web service to execute.
*A wsa:Action header with a value that is explicitly or implicitly associated with the corresponding WSDL definition, for example, the SOAP Action or the Action attribute in the WSDL document.
*A wsa:MessageID header with a unique identifier that Integration Server generates.
*A wsa:ReplyTo header with the endpoint address for the web service to execute.
*A wsa:FaultTo header with the endpoint address for the web service to execute.
*A wsa:From header for the source address.
false
Might or might not include WS-Addressing in the outbound message.
For an outbound response message, whether the provider includes WS-Addressing headers depends on the use of WS-Addressing headers in the associated inbound request message. If the inbound request message:
*Included WS-Addressing headers, the provider includes WS-Addressing headers in the outbound response message.
The WS-Addressing headers that the provider includes will be the same as those included when the wsdl:required attribute is true. See above for a description.
*Did not include WS-Addressing headers, the provider does not include WS-Addressing headers in the outbound message.
For an outbound request message, the consumer always include WS-Addressing headers. The WS-Addressing headers that the consumer includes are the same as those included when the wsdl:required attribute is true. See above for a description. For more information, see the description above for when wsdl:required attribute is set to true.
Note:
For the resolution order of these WS-Addressing headers, see Generation of the WS-Addressing Headers: Resolution Order and Usage.