on 04-14-2015 10:03 AM
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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.