cancel
Showing results for 
Search instead for 
Did you mean: 

Adapter engine messaging URL returns HTTP 403

ceedee666
Active Contributor
0 Kudos

Hi all,

I currently have a problem with the following scenario: SOAP Adapter -> XI -> JDBC Adapter. I have configured the scenario and everything seems to be running correctly (in the component monitoring the adapters and the integration engine are green). However when I send a request to the SOAP Adapter I get the following response:

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>DeliveryException</code>

<text><![CDATA[

com.sap.aii.af.mp.module.ModuleException

at

...

Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 403.

...

</text>

</s:SystemError>

In the Message Display tool of the runtime workbench I get the following trace:

2005-06-05 11:03:08 Success SOAP: request message leaving the adapter (call)

2005-06-05 11:03:08 Success Application attempting to send an XI message synchronously using connection AFW.

2005-06-05 11:03:08 Success Trying to put the message into the call queue.

2005-06-05 11:03:08 Success The message was successfully retrieved from the call queue.

2005-06-05 11:03:08 Success The message status set to DLNG.

2005-06-05 11:03:08 Success Message successfully put into the queue.

2005-06-05 11:03:08 Error Returning synchronous error notification to calling application: Received HTTP response code 403..

2005-06-05 11:03:08 Error Transmitting the message using connection http://<host>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 403..

2005-06-05 11:03:08 Error The message status set to FAIL.

2005-06-05 11:03:08 Error Returning to application. Exception: Received HTTP response code 403.

So it seem that somehow the adapter framework is not allowed to send a message to the integration engine via the messaging URL.

Any ideas how to resolve this problem?

Thanks for you help,

Christian

Accepted Solutions (0)

Answers (2)

Answers (2)

ceedee666
Active Contributor
0 Kudos

Hi all,

finally I found a solution to my problem. I had to execute the report RSXMB_ACTIVATE_ICF_SERVICES again (see SAP Note 736312) after patching our system to SP 11.

Christian

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

If you've changed the passwords for XI service users

then you may also want to check this note: 721548

XI 3.0: Changing the passwords of the XI service users

Regards,

michal

ceedee666
Active Contributor
0 Kudos

Hi all,

thanks for the tips. I checked if the users are not locked and also updated the passwords in the exchange profile. However I still get the same error message. Any additional ideas?

CU Christian

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

have you refreshed exchange profile? (or maybe even restarted the XI?)

regards,

michal

ceedee666
Active Contributor
0 Kudos

Hi Michal,

I just restarted the whole system. Still no change. I still get the HTTP 403 return code.

Any additional ideas?

Christian