This content has been marked as final. Show 13 replies
Can you please have a better description for Scenario 2?
step 1) Create 2-way Synchronous BPEL Process
step 2) Within this process add a scope, in that scope add four activity namely
step 3) Create 2-way Asynchronous BPEL Process
step 4) Add assign_to_process_request_to_response
Now, when I invoke synchronous bpel process wither through em console or through soap ui client, then i get error as mentioned above in my post.
Hope, I have cleared the scenario
Thanks Arik for your reply.
In your second scenario – did you call a one-way bpel process or an Asynch' bpel process?
Both Synchronous & Asynchronous BPEL process are two-way for Scenario 2
Synchronous bpel process exposed as a web service is a 2-way bpel process
Similarly, Asynchronous bpel process is a 2-way bpel process
Synchronous bpel process invoke Asynchronous bpel process and also have a receive node to receive response back.
Hope, I have cleared the scenario.
Timeout is a known issue when using massages invocation. The system default for timeout is 300s'.
Clearly this can be configured.
If you are calling an asynch' bpel process, you shouldn't have any problem receiving a response (using receive activity).
The thing is - if your callee process(asynch'), perform some actions (call other services etc..), that takes some time, you might end up with timeout exception.
So, the question is – is it possible your actions in the callee process increase the process duration?
Let me explain more clear the scenario,
my exposed synchronous bpel process(2-way) expects the result back from the Asynchronous bpel process(2-way).
And in my synchronous bpel process, I have invoke activity to invoke asynchbpel_process_ and following it a receive activity to receive responce from asynchbpel_process_
If this scenario can be achieved, then illustrate the solution. It is ok to increase the process duration for my process.
Illustrate how to achieve this scenario ?
I really hope I understood your request.
I've created and uploaded for you a very simple example (v126.96.36.199):
Let me know if that is what you wanted.
(I've used also a scope with catchAll activity for your other post)
Thanks exactly this is what I am looking for. your example works as expected. But I am doing something very similar, but getting the timeout exception.
I have uploaded my example here https://www.dropbox.com/s/4d0gmj62ofmjcjx/MyScenarioApp.rar
Examine my process, tell me where I am going wrong.
Appreciate your help. Thanks
Well...you've added the oneWayDeliveryPolicy & transaction property.
They are not needed here.
Delete and run it.
It will work for you now.
Thanks Arik. It worked :)
But let me tell you, I haven't explicitly added these properties. Just added 2 bpel process & configured required activities inside the two bpel process. How exactly these properties get added into the composite.xml ?
Strange...try to create it again step by step and see if and when it happens.
I have noticed this carefully. My Jdeveloper version 188.8.131.52.0
Whenever I drag a BPEL Process from component palette to components area, then in the process dialog apart from name, namespace, template, service name, input & output --> there is one more field is there called delivery.
case 1: if i select Asynchronous BPEL Process, then delivery values are async.persist/async.cache/sync
case 2: if i select Synchronous BPEL Process, then delivery changes to transaction having 2 values required/requiresNew
case 3: if i select one way BPEL Process, then case 1
for other templates, this is disabled.
Please pour in your thoughts on this.
The persistence policy(Delivery option) is very important when you build your orchestration process/s.
When you call one bpel process to another, or receive a callback from the other, you should consider the policy/rules that those calls
communicate. The policy you will choose will affect: the behavior of the processes, performance, stability, correct business flow etc…
In 184.108.40.206 version, you have the option to choose those properties from the wizard.
In lower versions(11.1.1.X) you can add those properties manually.