cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP_AAE sender adapter error

minal_vaidya2
Explorer
0 Kudos

Hello Experts,

I am looking for some help in the below scenario on PI7.4 dual stack.

We have a Advanced Adapter Engine installed and are in the process of converting existing HTTP communication to HTTP_AAE.


There is a scenario where one interface is triggering another interface on the same PI server through SOAP-HTTP request.

First interface - >

     RFC -> SOAP (Synchronous) 

Here receiver URL is nothing but HTTP_AAE url of same PI server. This is the URL used to post data to HTTP endpoint -

http://test:50000/HttpAdapter/HttpMessageServlet?service=LVQ11060&namespace=http://www.hrchelm0001.s...


Second interface - >

     HTTP_AAE -> RFC (Synchronous) Here I have used message protocol as POST in HTTP_AAE.

When testing this interface with plain HTTP it works fine. For HTTP_AAE I am getting 500 internal server error.

Can someone please provide some suggestions ?

Thanks

Minal

Accepted Solutions (1)

Accepted Solutions (1)

minal_vaidya2
Explorer
0 Kudos

Issue is resolved!

Parameter names were changed and qos was added to the URL in SOAP receiver channel and it worked!

Not sure if thats the rectriction in HTTP_AAE to maintain qos, because with plain HTTP, this scenario was working without mentioning qos.

/HttpAdapter/HttpMessageServlet?interfaceNamespace=http://www.hrchelm0001.sap.ch&interface=Z_HR_CH_ELM_SoapOutInForSigning&senderService=LVQ11060&qos=B...

Answers (1)

Answers (1)

gagandeep_batra
Active Contributor
0 Kudos

Hi Minal,

Can you test individually second scenario through soap UI and check what error is coming.

Regards

GB

minal_vaidya2
Explorer
0 Kudos

Hi Gagandeep

Thanks for the reply.

Its working fine and I am receiving expected results if second scenario is triggered from test tool. I am using the test tool provided for HTTP_AAE testing in this blog -

However, when SOAP is trying to trigger the second scenario, error is coming.

Thanks

Minal