cancel
Showing results for 
Search instead for 
Did you mean: 

Removing soapenv from a message

Former Member
0 Kudos

Hi Experts,

I am working on a synchronous scenario ABAP Proxy --> PI 7.0 --> webservice

I My client requirement is to use AXIS SOAP receiver adapter with username token secuity with password digest.

Whenevr i am sending the mesage to third party i am getting error as ACCESS DENIED in response message.

Through TCPGW i am able to capture the message with all security headers. However when i have send the same message to third party to check what is wrong in the message i got a following reply from third party

Remove u201Csoapenv:u201D from the two highlighted parts of the message below and the call completes successfully. It is these that are failing validation:

REPLACE:

<ns1:Main xmlns:ns1="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" soapenv:mustUnderstand="1" xsi:type="ns1:Main">

WITH:

<ns1:Main xmlns:ns1="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" mustUnderstand="1" xsi:type="ns1:Main">

u2026 and u2026

REPLACE:

<ns2:ReliableMessaging xmlns:ns2="http://sap.com/xi/XI/Message/30" ApplicationAckRequested="false" ApplicationErrorAckRequested="false" SystemAckRequested="false" SystemErrorAckRequested="false" soapenv:mustUnderstand="1" xsi:type="ns2:ReliableMessaging">

WITH:

<ns2:ReliableMessaging xmlns:ns2="http://sap.com/xi/XI/Message/30" ApplicationAckRequested="false" ApplicationErrorAckRequested="false" SystemAckRequested="false" SystemErrorAckRequested="false" mustUnderstand="1" xsi:type="ns2:ReliableMessaging">

Can anybody let me know how i will achive this in PI.

Please provide your valubale inputs on this.

Regards

Ankuchopra

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member187339
Active Contributor
0 Kudos

Hi Anku,

Did you check this note?

Note 1333830 - Fix for SOAP env. namespace in mustUnderstand WSA headers

Regards

Suraj

Former Member
0 Kudos

Hi Suraj,

whenever i am checking the message in sxmb_moni is is showing

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

- <!-- Call Adapter

-->

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SOAP:Header>

- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

i guess why i am getting soapenv:mustUnderstand="1" is because i am capturing the message from tcpgw tool

Please advice?

thanks in advance

Anku chopra

former_member187339
Active Contributor
0 Kudos

Hi Anku,

I am not sure whether the mustUnderstand=1 is giving you a problem of access denied in the SOAP call.

Try providing some other parameters (like proxy authentication etc) as mentioned in the link

http://help.sap.com/saphelp_nw04s/helpdata/EN/29/5bd93f130f9215e10000000a155106/content.htm

Also you can see this note

Note 1371676 - No soap:mustUnderstand in the WSRM sequence header

Regards

Suraj

Former Member
0 Kudos

Answered

former_member187339
Active Contributor
0 Kudos

Hi Anku

Good that your query is answered. But it will be better if you can mention here the solution that you have adopted

Thanks

Suraj

Former Member
0 Kudos

Hi Suraj,

Error of Access denied was beacuse we were sending XI headers to third party which were not required by them.

I have unchecked the Keep XI headers option in XI parameters section of receiver soap adapter(AXIS) and it works fine.

Regards

Anku Chopra