Monday, January 21, 2008

The controversial parallelism in Flow activity

There had been a lot of discussions detailing whether Flow activity provides parallelism as it promises. It was believed earlier, that Oracle does not provide parallelism under Windows OS, and they are working on it.

The common perception was all activities in lined sequences, were invoked one after the other, and the next activity is not picked up for execution lest the one in hand yeilds. However, observing a bit of experiments, this could be safely concluded that only synchronous Invoke activities bind the BPEL engine from executing any other activity. The wait, receive, pick and other such blocking activities are simply spawned and next activity is picked up for execution.

1 comment:

Akanksha said...

This post defines parallelism in Flow activity. The basic idea behind parallelism is given here. It includes both the points which are in favor and against parallelism. I really like your work. Thanks for the post. Keep it up.
sap upgrade automation