The greatest difficulty, when it comes to tools support for BPMN to BPEL conversion, is the synchronization of changes made by the business teams to the business models and technical modifications made by the IT teams to the BPEL code. Due to this reason, most of the time organizations preferred to create their process models in isolation with IT teams, and IT teams preferred to take the bundle of process models or business requirements, and create BPEL code directly in the IDE. This resulted in information silos, which in turn meant wasted effort and "lost in translation" problems.

To provide a solution to this problem and provide a tighter coupling of our BPMN models and BPEL, the Oracle BPA provides a mechanism for sharing a common metadata format, which is called a 'process blueprint'. The metadata, or process blueprint, which is basically an abstract level BPEL process is shared with IT. At this stage, the first handshake between business...