Use of variable header XHeaderName1 in SOAP sender adapter

[Former Member]

Hi all,

I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:

the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)

I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.

I tried with those settings in SOAP adapter configuration:

Keep headers checked

XHeaderName1 = Test

I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)

1. Pass "Test" value xxxx in SOAP Header as a tag

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<SOAP-ENV:Header>
		*<Test>xxxx</Test>*
	</SOAP-ENV:Header>

	<SOAP-ENV:Body>
		.........
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

2. Pass "Test" value xxxx in SOAP URL

http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&...;Test=xxxx

Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?

Thanks a lot,

Manuel

[manuel_bassani]

Maybe it can be useful for someone else: I solved by handling the entire SOAP message and using the nosoap=true attribute in URL.

[Former Member]

Hi Manuel,

Could you give a bit more detail on how you handled the SOAP message yourself.

I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.

At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.

Could we use the XI Adapter and ABAP proxy in a similar way?

Thanks,

Tim J.

[stefan_grube]

You can read or write HTTP headers, not SOAP headers.

But not standard headers like content-type, only customer specific headers.

Regards

Stefan

[manuel_bassani]

Stefan thank you for the answer.

So the mistake is to pass the custom field in SOAP Header.

It's still not clear for me how to configure and to use the adapter-specific attribute XHeaderName1

Should it be passed in the url ? and in which form ?

Best regards,

Manuel

[former_member607993]

stefan.grube shabarish.vijayakumar

Is this possible to read/write the SOAP Headers in SAP PO newer revisions (v7.4, v7.5)?

Just eager to know.Cheers!