AXIS receiver adapter error - Custom tags in Synchronous SOAP header

[former_member185846]

Dear Experts,

I used XSLT to populate the custom tags in SOAP header (synchronous proxy to SOAP - AXIS adapter). But, I get the error sap.aii.af.ra.ms.api.DeliveryException: (500)Internal Server Error when I run this interface. And whenever I remove the XSLT mapping it works perfect (no custom tags in SOAP header). Am really not sure why it's throwing the error (can't I populate custom tags in WS Header?). Below is the actual XML I send to the SOAP - AXIS receiver adapter. Any clue?

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header>

<WSHeader xmlns="htp://cio.abc.com/commonheader/v3" xmlns:ns2="http://newhorizon.xyz.com/IDISService">

<WSContext>

<FromAppId>ABC</FromAppId>

<ToAppId>XYZ</ToAppId>

</WSContext>

<WSMessageData>

<Timestamp>Tue, 24 May 2011 18:03:50</Timestamp>

</WSMessageData>

</WSHeader>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<n0:ItemAvailabilityRequest xmlns:n0="http://oracle.com/abc" xmlns:prx="urn:sap.com:proxy:ECC:/1SAI/TAS10D69783D5ACF6CBE834:700:2009/02/10">

<n0:itemList>000000000100000832</n0:itemList>

</n0:ItemAvailabilityRequest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Thanks.

[Former Member]

Try to test soap message with a tool (like SoapUI), and check error.

Then, check for errors comparing wsdl and message.

[markangelo_dihiansan]

Hello,

For the AXIS Receiver Adapter, the option Do Not Use SOAP Envelope is missing. However, there is a module for SOAP Header Insertion which you can find in SAP Note 1039369 - FAQ XI Axis Adapter . Go to the Advanced Usage Questions and see section 42 - Can I insert some SOAP headers?

Hope this helps,

Mark

[former_member185846]

Hello Mark,

Thanks for your prompt response. I checked the AXIS FAQs but it wasn't clear for the nested custom header (like the one in my case). Can you explain the configuration required for my requirement if possible?

Thanks in advance.

[markangelo_dihiansan]

Hello,

I checked the AXIS FAQs but it wasn't clear for the nested custom header (like the one in my case). 

For the same reason as above. I did not use the SOAP Axis Receiver because generating a nested custom SOAP header in the documentation was vague. Instead, I used the SOAP HTTP Receiver, you could also try the PLAIN HTTP Receiver too.

Hope this helps,

Mark

[baskar_gopalakrishnan2]

Is there any reason for using Soap Axis adapter? If not use the default SOAP Adapter.