6 Using Process Blueprints in JDeveloper

This chapter describes how to develop BPEL processes in JDeveloper using process blueprints created in Oracle BPA.

Note: Before using the Blueprint Editor in JDeveloper, the business process must first be shared with IT, as described in the previous chapter.

This chapter includes the following sections:

• Creating a BPEL Process Using a Blueprint

• Merging with Newer Versions of a Process Blueprint

• Saving the BPEL Process and Deploying

6.1 Creating a BPEL Process Using a Blueprint

In this section, the Order Booking BPEL process is created from a blueprint.

6.1.1 Create an Oracle BPA Connection

Define connections in to an Oracle BPA Server using the Connection Navigator in JDeveloper.

1. Select File > New then choose New BPA Server Connection from the General > Connections section of the New Gallery.

2. The BPA Server Connection dialog is displayed.

3. Enter the name you want to use for the BPA server connection in the Name field.

4. Select the Location of the server: Local Server or Remote Server. Note that if you want to use a local server (i.e. the BPA Repository in the Oracle BPA tool), that tool must be running.

5. If using a local server, enter the Directory in which your local BPA server is installed or browse to the directory.

6. If using a remote server, enter the hostname or IP address in the Host field.

7. Enter the Username and Password for the connection.

   Figure 6-1 Remote BPA Server Connection

   
   

   Figure 6-2 Local BPA Server Connection

   
   

8. Click on the Test tab, and then click Test Connection.

   Details of the test are displayed in the Connection Diagnostics area. If the test succeeds, a success message appears in the status text area. If the test does not succeed, an error appears.

9. When the test succeeds, click OK.

The new connection name appears under the Connections > BPA Server node in the Application Resources section of the Application Navigator.

6.1.2 Creating a New BPEL Process Based on a Blueprint

You must create an application and a project to begin. Do not include any special characters in the project name (such as periods), as it will cause errors when you attempt to compile your project.

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

2. Double-click Application in the Items window.

3. Enter your application name in the Application Name field and accept the default path in the Directory Name field, then click OK.

4. Click Cancel on the Create Project window.

5. Right-click your new application node in the Application Navigator and choose New Project.

6. Double-click BPEL Process Project in the Items window to display the BPEL Project Creation Wizard window.

7. The Name field is automatically populated with the blueprint name. All other fields default to the correct values for creating an asynchronous BPEL process.

8. Select "Existing Blue Print" in the Type field.

   Figure 6-3

   
   

9. Browse to the BPMN model you previously shared with IT, then click OK.

   Figure 6-4

   
   

6.1.3 Understanding Blueprint and BPEL Generated Artifacts

The project that is generated comprises a Process Blueprint and abstract BPEL code.

The Process Blueprint comprises business scopes with business annotations for IT to refer to when converting the abstract BPEL process into a concrete BPEL process.

Figure 6-5 Process Blueprint with Business Scopes and Annotations

Figure 6-6 Business Annotation for Human Workflow Business Scope in Process Blueprint

The generated BPEL project contains the following:

• BPEL process source (projectname.bpel)

• Web services description language (WSDL) client interface (projectname.wsdl)

• BPEL process deployment descriptor (bpel.xml)

• Sensor definition, if defined in the BPD

• Task Service and BPEL artifacts to invoke a workflow if a Human Workflow activity is contained in the BPD.

• Decision Service and BPEL artifacts to invoke a Decision Service if a Business Rule activity is specified in the BPD.

• Notification Service and BPEL artifacts to invoke a Notification Service if a Notification Service is specified in the BPD.

• Partner Link and BPEL artifacts to invoke a Partner Link if an Automated activity is specified in the BPD.

Figure 6-7 Generated BPEL Code

6.1.4 Adding Implementation Details to the BPEL Code

Implementation details need to be added to the BPEL code to convert the abstract BPEL process into an executable process that can be deployed to the BPEL server.

For information on creating or defining an executable BPEL process in JDeveloper, see the Oracle BPEL Process Manager documentation available on the Oracle BPEL Process Manager site at Oracle Technology Network (OTN):

http://www.oracle.com/technology/bpel/

6.2 Merging with Newer Versions of a Process Blueprint

Newer versions of the Process Blueprint generated in the BPA Repository can be merged with the local Process Blueprint version in the JDeveloper project. The following steps show how to do this.

6.2.1 Changing the Business Process Model and Regenerating the Process Blueprint

1. Drag the Notification Activity "Notify customer regarding credit check" to be after, or below, the Automated activity "Check Customer Credit Info".

2. Select SOA > Share Blueprint with IT from the main JDeveloper menu.

3. A newer version of the Process Blueprint is generated and saved in the BPA Repository.

Figure 6-8 Change to the Business Process Model

6.2.2 Merging with a Newer Version of a Process Blueprint

1. Click the Blue Print View tab in the editor window to display the process blueprint.

2. Right click on the background of the diagram then select Refresh from BPA Server. to display the Refresh from BPA Server dialog.

3. Choose BPA server from those available in the Server dropdown list.

4. Select Compute Differences with BPA Server Process link to analyze the differences between the local blueprint and the version on the BPA server.

5. Select the Visual Differences icon to display the differences between the local and server versions of the blueprint visually.

   Figure 6-9 Visual Differences Icon

   
   

6. The differences between the local and server versions of the blueprint are displayed.

   Figure 6-10 Merge Differences Between Process Blueprint in BPA Repository and Process Blueprint in Local JDeveloper Project

   
   

   Figure 6-11 Graphical Merge Differences Between Process Blueprint in BPA Repository and the Process Blueprint in the Local JDeveloper Project

   
   

   Figure 6-12 Merged Process Blueprint after Accepting the Changes

   
   

7. Click OK to refresh the blueprint from the BPA server.

6.3 Saving the BPEL Process to the BPA Repository

When the changes to the BPEL process are complete, the process can be saved back to the Oracle BPA Repository.

1. Select the Blue Print View tab in the editor window.

2. Select Save to BPA Server.

   Figure 6-13 Save to BPA Server

   
   

3. Confirm the BPA Server to which you want to upload, and then click Save.

   The model is now saved on the BPA Server, and is available to other business and IT users.