2 Replies Latest reply on Dec 10, 2013 10:32 PM by LFHeckler

    Calling from one BPEL to other BPEL



      We have 2 different processes and we have some common functionality which need to do in both these processes so we are thinking to put 2 different BPELs and one more BPEL with common functionality so we can call this BPEL from both other BPELs. But we have very high volume nearly 2000-3000 per hour and it has very complex logic also so we are little worried about common BPEL and looking for some suggestions as it is good idea or we need to have only 2 BPELs for these processes and no common BPEL.




        • 1. Re: Calling from one BPEL to other BPEL

          Hi Bijendra,


                  You should put the common functionality in a single BPEL process and then the other two BPEL process can call the first BPEL using Direct Binding. It's better to have all the complex logic in one process and use it as a service from other processes. You should also look into purging these instances on daily or weekly basis.



          -- Sid

          • 2. Re: Calling from one BPEL to other BPEL

            The suggestion made by Sid seems a good option in case you use BPEL.

            IMHO I would only suggest to do not generate audit data in case you don't need to track your instances: better than do the purge is do not generate the information to be purged.


            But other suggestion is use OSB instead of BPEL. Have you considered this?

            I believe with OSB you can have a better performance and control over the process and throughput, since the processing volume is high.