Reading contents of SOAP Header

Question

Hi folk,
I did some reseach on SDN on how to read the contents of the SOAP header, there were a lot of promising leads but i havn't hit the bull'sEye yet.....
1.i have a requirement whrein i need to read some contents frm the SOAP header hold on to it and send it back in the respnse.
2.2nd requirement i have to modify the soap header's contents based on the current date/time and send it.
Can someone give me some leads/hints on how to achieve this.
If you can give me the mapping API i need to call in the mapping that will be greatly appreciated!!
Thank u all.
Hank

Answer 1

some quick facts:
#1: there is a confusion between HTTP Headers (which is addressed by the Variable Transport Binding option in both SOAP and HTTP adapters) and the SOAP Header (part of the XML message that is the payload of the HTTP Request). Notice that the SOAP Header is not addressable through the Dynamic Configuration of the HTTP Headers.
#2: in order to read data from the SOAP Header on the outbound (sender) side, you need to:
    #2.1. select the "Do Not Use SOAP Envelope" option in the Sender communication channel (the SOAP Envelope has two subtags, the SOAP Header and the SOAP body, which contains the payload);
   #2.2. in the mapping, you need to consider the whole SOAP Envelope as source message. You could even try to address it through a Message Mapping, given that you have an external message definition (e.g. wsdl, xsd) that defines the SOAP Envelope layout. But it is much easier to handle it through a XSLT or Java Mapping, at a 1st moment, to read the necessary information from the SOAP Header* and to extract the payload from the SOAP Body, and then use your existing Message Mapping in the payload.
Example of XSLT mapping: Re: XI30 SPS16 - SOAP Sender Adapter - self-defined SOAP-Header (last message)
You just need to enhance the part where you read the header field you need.
Best,
Henrique.
to recover the read value at a later point, you could use for example a mapping variable (PI 7.1+) or a custom context object (use dynamic configuration to read/write on a custom context object). Notice that Dynamic Configuration works as a custom HashMap, where you can read/write any combination of context objects namespace/technical name. Just define your custom namespace and technical name (e.g. 'http://sap.sdn.com/test' and 'MyParam'), fill it in the XSLT mapping** and read it afterwards, wherever you need***.
Sample code to read/write Dynamic Configuration in XSLT mappings: http://help.sap.com/saphelp_nw70/helpdata/en/43/03fe1bdc7821ade10000000a1553f6/frameset.htm
if you want to use this value in a Receiver Determination, you can even use Adapter Metadata to define them as "fake ASMAs": /people/michal.krawczyk2/blog/2006/10/09/xi-dynamic-configuration-in-adapter-modules--one-step-further