Oracle has two approaches for BPM:
1. Using BPMN and BPEL along side by side, and run them with single runtime engine (BPM Suite + SOA Suite)
2. Using BPMN and generate or merge it into BPEL, and run them with BPEL engine (BPA Suite + BPM Suite + SOA Suite)

How does it transform business process into a BPEL process?

The business process models are abstract and have to be implemented before they can be realized. Once business decides that a specific version of the process model is ready for implementation, the model is marked for IT implementation and saved in the Business Process Repository. The blueprint can now be used to create a BPEL process in Oracle JDeveloper.
BPEL transformation generates Process Blueprint and associated skeletal BPEL code. The IT developer needs to add implementation details to the BPEL code to convert it into an executable process that can be deployed on the run-time engine (BPEL Process Manager).

The transformation a business process into a BPEL process comprises the following:
■ Notification Services are transformed into a Business Scope upon BPEL transformation. The corresponding Notification service as well as the BPEL artifacts for invoking the Notification service are created within the business scope.
■ Human tasks are converted to a human workflow business scope upon BPEL transformation. The Task Service gets automatically generated as well as the BPELartifacts for invoking the Task service also gets generated. The Notification/Reminder notes get translated to business annotations.
■ Automated activities are converted to a business scope upon BPEL transformation.
■ Business Service is converted to a Partner Link upon BPEL transformation. If the Business Service is associated with a concrete WSDL, it is converted to a concrete Partner Link. Otherwise, it is converted into an abstract Partner Link. If Represented by is set to "invoke", an invoke activity is created inside the business scope and is linked to the Partner Link. If Represented by is set to "receive", a receive activity is created inside the business scope and is linked to the Partner Link. The Sensor definition is converted in to a business annotation.
■ XOR, AND and OR gateways are converted to switch and case statements upon BPEL transformation.
■ All Business Data in the Business Process Diagram are converted to Variables upon BPEL transformation. If the Business Data is associated with an XSD, the XSD is exported and the Variable in the BPEL skeletal process generated is then set to the XSD type. Otherwise, the Variables are set to String type.
■ Business Rules are converted into a Decision Service. The free text in the Rules field is converted into business annotation.

BPA View




BPEL View in JDeveloper



Cool..you can switch BPEL view and BPA view.

BPM Studio documentation stated somewhere that we can convert bpmn process to bpel which i can't find it. Because when you create SOA project from JDeveloper and connect it to BPA Repository, it will only convert it.