cancel
Showing results for 
Search instead for 
Did you mean: 

Sender SOAP Adapter error

Former Member
0 Kudos

Hi All,

I was trying to post SOAP message and i got the following error in Adapter Monitoring.

________________________________________________________

Audit Log for Message: ed480ae0-3ccf-11db-bfa0-000255b6218b

Time Stamp Status Description

2006-09-05 16:46:07 Success SOAP: request message leaving the adapter (call)

2006-09-05 16:46:07 Success Application attempting to send an XI message synchronously using connection AFW.

2006-09-05 16:46:07 Success Trying to put the message into the call queue.

2006-09-05 16:46:07 Success Message successfully put into the queue.

2006-09-05 16:46:07 Success The message was successfully retrieved from the call queue.

2006-09-05 16:46:07 Success The message status set to DLNG.

2006-09-05 16:46:07 Error SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: SOAP; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Sender agreement found belongs to adapter SOAP; however, current adapter is 'XI'

2006-09-05 16:46:07 Error Returning synchronous error notification to calling application: Received HTTP response code 500 : Error during conversion of XI message.

2006-09-05 16:46:07 Error Transmitting the message using connection http://xidev:8001/sap/xi/engine?type=entry failed, due to: Received HTTP response code 500 : Error during conversion of XI message.

2006-09-05 16:46:07 Error The message status set to FAIL.

________________________________________________________

It would be much appriciated if any one can throw some light on this problem.

Thanks in adv.

Accepted Solutions (0)

Answers (2)

Answers (2)

bhavesh_kantilal
Active Contributor
0 Kudos

Muna,

take a look at section 3.2.2 in this document,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873...

Think while creating the Webservice from your Interface determiantion, you must have selected the <b>PROPSEURL BUTTON</b> . You should not select the same.

Just enter the URL manually as <b>http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=:<service>:<channel></b>

Also , amake sure you have given the correct message interface .

Just recreate this once again as shown in 3.2.2 and this should work.

Regards,

Bhavesh

Former Member
0 Kudos

Hi Bhavesh,

I entered the URL manually while creating the WSDL file. But gettting the same error at adapter monitoring.

I am using XI 7.0. Will it make any difference..??

Former Member
0 Kudos

Can any one suggest..what's worng in this..??

Thanks in adv.

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

<b>Sender agreement found belongs to adapter SOAP; however, current adapter is 'XI'</b>

Somehow, you seem to have mixed somewhere between SOAP and XI adapter.

Just make sure you have used the SOAP adapter in the Sender Agreement.

Regards,

Bhavesh

Former Member
0 Kudos

Hi,

Also, the URL of the client application sending the SOAP message should be in the following format:

http://server:port/XISOAPAdapter/MessageServlet?channel=party:service:sender_comm_chan

Regards,

Bill

Former Member
0 Kudos

Hi,

I used the Same URL format to pump the message from the SOAP Client and In the sender aggrement, i configured the SOAP adapter as sender communication chanenl.

Am i doing anything wrong...?? Any suggestions...!!

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

Can you paste as the SOAP url you have created.

If you have no PARTY, then this is how it should be,

http://server:port/XISOAPAdapter/MessageServlet?channel=:service:sender_comm_chan

Can you cofrim this.

Regards,

Bhavesh

Former Member
0 Kudos

Hi Bhavesh,

Here the URL which i used to create the Webservice in Directory,

http://xidev:8001/XISOAPAdapter/MessageServlet?channel=:Bank_WebService:CC_BankDetails_Webservice

But I am getting the following URL in xml spy as end point: http://xidev:8001/XISOAPAdapter/MessageServlet?channel=:Bank_WebService:CC_BankDetails_Webservice&am...

Is there any thing wrong with URL..??

Thanks in adv.