cancel
Showing results for 
Search instead for 
Did you mean: 

Async/Sync bridge doesn't work at PO 7.40

Former Member
0 Kudos

We've implemented Async/sync without BPM scenario at PO 7.40

HTTP (Async) -> HTTP (sync) -> File (Async)

Configuration of sender channel:

Modules configuration:

1    AF_Modules/RequestResponseBean    Local Enterprise Bean    request

2    sap.com/com.sap.aii.adapter.http/HttpAdapterBean    Local Enterprise Bean    http

3    AF_Modules/ResponseOnewayBean    Local Enterprise Bean    response

parameters:

request  passThrough  true

response  interface  intrfSynchResp

response  interfaceNamespace  http://namespace/test

response  replaceInterface  true

Underneath is a log part:

4/9/2015 09:58:55.079 AM Information RRB: leaving RequestResponseBean

4/9/2015 09:58:55.079 AM Information RRB: suspending the transaction

4/9/2015 09:58:55.610 AM Information MP: processing local module localejbs/AF_Modules/ResponseOnewayBean

4/9/2015 09:58:55.612 AM Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields (sender party: "", sender service: "TEST_01", interface: "http://namespace/test intrfSynchSend", receiver party: "", receiver service: "TEST_01")

Interface intrfSynchSend is sending message synchronously and it seems it's not replaced by ResponseOnewayBean for the response message.

Does anybody knows if ResponseOnewayBean can work in 7.40 as it was in previous versions?

Accepted Solutions (1)

Accepted Solutions (1)

engswee
Active Contributor

Hi Mikolaj


No sender agreement configured that matches the message's header fields (sender party: "", sender service: "TEST_01", interface: "http://namespace/test intrfSynchSend", receiver party: "", receiver service: "TEST_01")

From the description of your error, it's most likely that your async response flow was not setup correctly. You need to make sure that you check "Sender Uses Virtual Receiver" and set the receiver service to TEST_01 as per the error above. Refer to the last screenshot on the following blog.

Rgds

Eng Swee

Former Member
0 Kudos

Believe me I did the configuration correctly and checked it at least 10 times.

The configuration has check "Sender Uses Virtual Receiver - what is wrong that the message says that interface is not replaced by a bean - that's an error...

engswee
Active Contributor
0 Kudos

Hi Mikolaj

Just noticed that you are using the HTTP adapter for the sync call (it didn't register earlier).

If you look at the comment from Michal on the blog below, it looks like it does not work with HTTP_AAE. Not sure if anything has changed since a year ago

Generic PI Async-Sync Bridge Configuration for Any Adapters

Alternatively, you can switch to SOAP adapter with "Do not use SOAP envelope" or if you are on SP09 or above, you can try out the REST adapter.

Rgds

Eng Swee

Former Member
0 Kudos

Thanks Eng,

REST doesn't work (same error as HTTP).

SOAP works correctly with envelope, but without it doesn't (at least calling demo HTTP adapter) - looks like it sends envelope despite the flag is checked. Maybe RequestResponseBean somehow pass the data without modification.

engswee
Active Contributor
0 Kudos

Hi Mikolaj

Looks like I missed out another important detail in your initial post - my apologies!

I just noticed that you have configured the modules on the Sender channel. The bridges that I've configured successfully so far have always had the modules on the sync Receiver channel based on the blog above (I've never tried it on the sender channel).

Can you try and configure them in your receiver channel instead? Retry with all HTTP, REST and SOAP.

If that still does not work, can you share what type of sync service are you trying to consume? Is it an HTTP with GET/POST or SOAP service?

Rgds

Eng Swee

Former Member
0 Kudos

Eng,

Forgive me - I was mistaken. I meant of course "recever" channel and so was configured.

I've checked yesterday once again SOAP channel and it worked (don't know why "do not use SOAP envelope" wasn't working previously - maybe some caching problem).

Former Member
0 Kudos

I will mark one of your post as correct answer.

Thanks a lot!

former_member188791
Participant
0 Kudos

Hi Mike lazy,

I mean facing same issue as above may I know how u solved I am using rest receiver with post, it seems responseonewaybean not replacing interface name

0 Kudos

hi Mike

I'm facing the same issue.

Did you find a solution ?

Or did you just accept the fact that it currently doesn't work with AAE_HTTP receiver adapter..

Former Member
0 Kudos

Hi,

It works - but you've got to be patient.

Change everything at configuration (comm channel, ICO and so on) - stop it, change it, activate it and start it.

It should work!

0 Kudos

Oh - I see now I should have been more specific with my question.

You're talking about the "don't use soap envelope" issue...

SOAP is not an option in my scenario.

We must use HTTP (with GET method) and therefore my question was to be understood like "did you find a solution for the http adapter".

But I realize now that you proceeded down the soap adapter path and hence never pursued a solution for the http receiver adapter.

Thanks for the answer anyway

Answers (0)