SOAP sender - how to ensure EOIO for end to end processing
In our scenario SOAP client -> XI -> ABAP proxy - the sender is interested in sending messages with QOS = EOIO.
In SAP-help I have found:
1) The SOAP message provided by the SOAP client must contain a unique GUID. This can be provided in a valid XI message header in the SOAP message header or specified in a corresponding query string in the URL......
2) The SOAP adapter generates a GUID. This becomes relevant if the SOAP client does not provide the GUID. In this case, you must set the Quality of Service in the sender SOAP adapter to <b>Exactly Once</b>. The GUID is generated and the adapter calls the XI service exactly once.....
Only the first option seems to be relevant for EOIO. I understand that to assure real EOIO from the beginning, the sender has to serialize messages and give them GUIDs - right? If so, here come my questions:
a) What should be the message header format and minimum of information included in header by sender, to ensure that XI will respect message GUID which was assigned by sender? Any example in XML format?
b) How can I generate WSDL in XI containing not only message structure but also SOAP header with correct format, at least containing GUID?
c) What checkboxes should be marked in sender SOAP adapter configuration to read and respect GUID from sender header?