1

Tutorial 2

Generate BPEL model from the Blueprint and Round Trip Integration

Overview This is the second tutorial in the three part series. The first half of the tutorial describes the use Oracle JDeveloper to generate the BPEL model from the process blueprint created previously in Tutorial 1 (“Business process model creation using Oracle BPA Suite”). As described in Tutorial 1, the blueprint is generated by the business user using Oracle BPA and then handed off to the development team to create the executable software. The second half of this tutorial illustrates the round trip integration between the modeling (Oracle BPA Suite) and the development (Oracle JDeveloper) environments. Prerequisites 1. Oracle Business Process Analysis Suite 10g, available here. 2. Oracle JDeveloper, available here. Time to complete: Approximately 2 hours.

2

I. Generate the BPEL model ........................................................................................... 3

II. Round trip integration: Part 1 ..................................................................................... 17 III. Round trip integration: Part 2 ..................................................................................... 19

IV. Summary .................................................................................................................... 23

3

I. Generate the BPEL model

1. Select File > New from the main JDeveloper menu.

2. Double click on Application in the Items window.

3. Enter BPA OBE as the application name and accept all the other default entries. 4. Click OK to continue.

4

5. Click Cancel.

6. Right click on the new BPA OBE application and select New Project.

5

7. Select BPEL in the Categories list and double click on BPEL Process Project in the Items window.

8. This brings up the BPEL Project Creation Wizard. Designer. Select Synchronous

BPEL Process as shown.

6

9. Select Existing Blueprint from the Type drop down menu.

7

10. Click on the flashlight icon next to the Blue Print field to bring up the BPA Model

Chooser.

11. Select the Add Connection icon as highlighted.

8

12. The BPA Server Connection dialog is displayed. (Note: This tutorial assumes that the

BPA Suite and JDeveloper are installed on the same machine. Verify that your local BPA Suite is up and running).

13. Enter BPA-demo for the BPA Server Name. 14. Select Local Server in the Location drop down list. 15. Enter the Username and Password for the BPA Server connection (this tutorial uses

system/manager as the username/password, but your system may have a different login).

9

16. Click on Test Connection to validate the settings. Click OK to proceed.

10

17. Navigate to the BPMN model that was previously created and shared (in Tutorial 1).

Click OK to proceed.

11

18. The Name fields are populated with the blue print name. Click Next.

19. Click on the flashlight icon next to the Input Schema Element.

12

20. Navigate to the location of the (attached) schema file (BPA_OBE.xsd) and click Open.

21. In the Type Chooser, select BPA_OBEProcessRequest and click OK

13

22. Click on the flashlight icon next to the Output Schema Element and navigate to the location of BPA_OBE.xsd (as in Step 20).

23. In the Type Chooser, select BPA_OBEProcessResponse and click OK.

24. Click Finish to proceed.

14

25. The Blue Print and BPEL views are generated. Click on Blue Print View to bring up the BPMN viewer.

The locks next to the BPMN objects indicate that the IT developer cannot modify the business flow. This can only be modified by the business user to ensure that the business model drives the IT development process and to protect the integrity of the business model.

15

The "stick it" notes on the other side of the BPMN object (in the previous screen shot) contain attributes defined by the business user. These are used to provide information to IT for use in the development phase.

26. Select BPEL View to see the automatically generated BPEL artifacts. The BPMN activities in the Blue Print view are translated into BPEL scopes in the BPEL view. The automated activities that were created in the business process diagram are now represented as BPEL partner links (they are as yet to be defined in this example, hence they are depicted as Not_definedPL). The IT developer would add the appropriate artifacts (for instance: Assign, Transform) to complete the individual scopes as well as the calls to the various partner links.

16

Note: As the above BPEL model is used to create the executable software in Tutorial #3, it is recommended that the reader STOP at this point and proceed with Tutorial #3 (“Create executable software from the BPEL model”) instead. The remaining section (“Round trip integration”) of this tutorial can be revisited following the completion of Tutorial #3.

17

II. Round trip integration: Part 1

(As previously mentioned, it is recommended that the reader STOP prior to this section and proceed with Tutorial #3, “Create executable software from the BPEL model”, instead. This section can be revisited following the completion of Tutorial #3.) The tight coupling between the Oracle BPA Suite and Oracle JDeveloper provides the round trip integration between the modeling and the execution environments, ensuring that the two processes remain in alignment. Any change to the business process model inside the BPA Suite can be automatically propagated and merged with changes in the development environment (JDeveloper). To illustrate this capability, assume that the business process model has been changed to allow the employee to update his address during the benefits enrollment program. Changes to the process model are always performed by the business analyst using Oracle BPA. 1. In the Oracle BPA Suite, bring up the business process diagram (BPA-OBE) that was

created in Tutorial 1. 2. Create an automated activity with Name: Update address. Select Abstract BPEL

activity in the Represented by drop down list.

18

3. Insert the newly created Update address activity between Insert W4 and Get

Dependents.

4. Select File > Save all. 5. Select SOA > Share Blueprint with IT from the main menu. 6. Select No to skip the validation. 7. Select OK to complete the Blueprint creation.

19

III. Round trip integration: Part 2

Now we switch roles and assume the role of the IT developer. 1. In Oracle JDeveloper, double click on BPA_OBE.bpel.

2. Navigate to the Blue Print View (note the alert indicating the presence a newer version

of the process model in the repository). Click on the Refresh from BPA Server icon as highlighted.

20

3. Select Click Here to Compute Process Differences.

4. The newly added activity (Update address) is reported. Click on the Visual Differences icon as highlighted.

21

5. The changes to the Server process as well as the resulting Merged process are depicted

visually. Click Close.

6. Accept all the changes by clicking on OK and Yes.

22

7. The Blue Print and BPEL Views now reflect the new changes.

23

IV. Summary

This tutorial illustrates the tight integration between the modeling and the execution environments and the ease with which they can collaborate. A subsequent tutorial (Tutorial #3) will demonstrate the generation of executable software using the BPEL model.