Behavior for Inbound Messages

The following table describes how Integration Server handles provider inbound request messages and consumer inbound response messages based on the setting of the wsdl:required attribute of the wsaw:UsingAddressing assertion in the attached policy and whether the inbound message includes WS-Addressing headers.

wsdl:required attribute is set to...	The inbound message...	Integration Server...
true	Contains WS-Addressing headers	Processes the WS-Addressing headers in the inbound message, extracting the addressing information from the header to use for later processing. For an inbound request message, the provider expects: Optionally, the wsa:To header for the destination address. The wsa:Action header to determine the web service operation to execute. The wsa:MessageID header for a unique identifier for the message. Integration Server only requires this header when In-Out MEP or Robust In-Only MEP is in use.
	Does not contain WS-Addressing headers	Returns a fault message.
false	Contains WS-Addressing headers	Honors the WS-Addressing headers in the inbound message and behaves as it does when the wsdl:required attribute is set to true. For more information, see the description above for when wsdl:required attribute is set to true and the inbound message contains WS-Addressing headers.
	Does not contain WS-Addressing headers	Processes the inbound request without using WS-Addressing.