Using custom http headers in SOAP sender adapter

[Former Member]

Hi,

my problem is exactly the same as reported [here|;] and [here|;

Basically I'd like to send through the soap sender adapter some custom http headers. I check the necessary options in the advanced tab (set adapter-specific message attributes and variable transport binding), and in the variable header one I put x-StoreCode, which is the same http header I send to PI.

But I won't see anything in the dynamic configuration section when the message is persisted in PI.

Very surprised that I've seen this issue is a common problem others have faced before without success.

Thanks!

[MichalKrawczyk]

Hi,

did you put the &version as a first parameter after the channel name ? and only then the rest ?

Regards,

Michal Krawczyk

[Former Member]

Hi Michal,

the extra info I'm trying to send separated from the message is an http header, not part of the query string.

If I incorporate the extra info as a parameter to the query string like this, for example:

http://host:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=S1&receiverParty=&receiver...

Then I can see the value in the dynamic configuration section:

<SAP:Record namespace="http://sap.com/xi/XI/System/SOAP" name="SQueryString">senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true</SAP:Record>

But what I'm trying to do shoould be possible, according to sap help:

http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm (section Define Adapter-Specific Message Attributes)

[Former Member]

Hi Jorge,

There seems to be a bug in the SOAP adapter. Many people are reporting this issue, as you have also noticed.

You can either report this issue as a critical bug and have it fixed or you can just use the axis adapter which supports this feature.

It is easy to read in arbitrary HTTP headers using the axis adapter. These headers can be read into the dynamic configuration header. You can find more information in the Axis Adapter FAQ Note 1039369. The pain part of using the axis adapter is you need to deploy the axis jar and other jar files. But this deployment part must be done only once and it is straight forward. You can read the note and think about it.

Best regards, Yza

[Former Member]

Thanks yzanagi, I may try to go through regular support, that feature could be useful for some of our scenarios.