Call sync BPM from Async BPM - issue

Question

Hi,
Outline: I'm trying to call a synchronous BPM from an asynchronous BPM in a PI 7.0 SP 14 system.
When doing so i get the following error: Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed.
Now this is an oldie when searching the forums for this error message. I do however fail to see a solution to the problem.
Note that the following notes (referred to in similar posts)
- 710445
- 718734
- 830803
are implemented since theese refer to older versions of PI.
My scenario is very simple at present since i've startet from scratch again after getting the error. So what i do is:
1) send async message to async BPM
2) async BPM receives request
3) async bpm transform request til sync_request.
4) async BPM calls synchronous BPM
5) sync BPM receives request and opens a async/sync bridge
6) sync BPM maps request to response
7) sync BPM sends response and closes async/sync bridge
8) async BPM reveices sync_response
9) async BPM sends sync_response to some application
Now step 8 i never succesfully executed. Instead the error earlier described is triggered.
For simplicity i use 1 and only 1 message type in all message interfaces. I have mapping between my synchronous interfaces outside of BPM.
The synchronus BPM is executed just fine. The only issue is getting the reponse back to the asynchronous BPM.
I am familiar with the following similar posts:
- Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed
- Problem in posting the data in the syncronous mode
but find them to be of no use.
Hope someone can help.
Best Regards,
Daniel

Answer 1

Daniel Hans Engsig-Karup wrote:First you do not need any bridges if it is asyn/sync kind of a scenario in the second BPM. You need a bridge when the bpm has to wait with a sync call coming in and response in an async call. Essentially your BPMs (I donno why you need 2.. but let us go with 2)
>
>
> 1) send async message to async BPM
> 2) async BPM receives request
> 3) async bpm transform request til sync_request.
> 4) async BPM calls synchronous BPM
> 5) sync BPM receives request                        
(Remove this if you are calling a sync system here) and opens a async/sync bridge
> 6) sync BPM maps request to response
> 7) sync BPM sends response
Remove this and closes async/sync bridge
> 8) async BPM reveices sync_response
> 9) async BPM sends sync_response to some application
>
VJ