Chapter 4. Reference

This chapter includes detailed reference information about all BPEL tools wizards and editors.

4.1. Wizards

4.1.1. New BPEL project Wizard

This wizard helps to create new BPEL project.It is available with clicking File->New->Other->BPEL project in the menu bar.

Figure 4.1. New BPEL Project Wizard

It consists of only one page:

On the page you can adjust the name of the project and the directory where it will be created.
If "Use default" option is checked the output directory will be the workspace, othervise the user should specify it by himself using Browse button.
Figure 4.2. New BPEL Project Wizard

4.1.2. Apache ODE Deployment Descriptor Wizard

Using this wizard user can create ODE deployment descriptor (deploy.xml) and place it in the temporary directory.It is available with clicking File->New->Other->Apache ODE Deployment Descriptor Wizard in the menu bar.

Figure 4.3. New BPEL Project Wizard

On the page you can adjust the name of the deployment descriptor and the directory where it will be created.Note,that you should use /PROJECT_NAME/bpelContent directory as an output one.

4.1.3. New BPEL Process file Wizard

Using New BPEL Process file Wizard user can create BPEL process file and WSDL file if it is necessary. The wizard includes several pages:

The first page has the following options to set:

Table 4.1. New BPEL Process file Wizard. First Page Options.

Option	Description	Default
Name	Enter the process name.	no default value
Namespace	Enter the namespace url here	no default value
Template	Select one of the provided templates: Asynchronous BPEL Process - generates the basis of orchestration logic: receive and reply activities are included into the process;client WSDL is generated, service is defined in the parentlink of the process. The caller is notified asynchronously when the process completes. Empty BPEL Process - list of services participating in this BPEL process together with the one of messages used within the process is empty.There are no any orchestration logic. Synchronous BPEL Process - similar to Asynchronous BPEL Process template except the fact that here the caller is notified synchronously when the process completes.	Asynchronous BPEL Process
Abstract Process	Specifies the created process as an abstract one -partially specified processes that are not intended to be executed.	unchecked

Figure 4.4. New BPEL Process file Wizard

On the second page the user should select the BPEL project and folder where the process file will be created:
Figure 4.5. New BPEL Process file Wizard

Note

Process files that are used in the BPEL project must be under the bpelContent folder. Only in this case these files can be deployed to JBoss server.

4.2. Editors

4.2.1. Business Process Editor

Business Process Editor is intended to facilitate the process of changing and adding new logic to BPEL process file.You can open .bpel in this editor by right click the file in the project explorer and selecting Open With...->Business Process Editor

Figure 4.6. Business Process Editor

The editor consists of two tabs:Design tab and Source tab.

4.2.1.1. Design tab

Design tab is the main part of Business Process Editor.It consists of 3 parts:

Visual Pane:
Figure 4.7. Visual Pane of Business Process Editor

The Visual Pane graphically displays the order in which the activities are executed.
Palette:
Figure 4.8. Palette of Business Process Editor

The Palette represents different elements of the BPEL activities organized into functional categories. Using it the user can easily add new elements to the sequence activity. To do this,he should just click the required element and then drug and drop it to the place on the Visual Pane where it should be added.
Behavior Components View:
Figure 4.9. Behavior Components View of Business Process Editor

Execution behavior components are grouped into the Behavior Components View. The view is also fully syncronized with Properties view where you can customize all the properties of the component.
Figure 4.10. Process Structure View of Business Process Editor

To add an element to some component group click plus() icon, for its deleting you should click the element and use its Delete option in the popup menu.

4.2.1.2. Source tab

Source tab can be used for editing BPEL process file directly. The validation of file structure is also available.

Figure 4.11. Validation error in Source tab

If the user wants to disable/unable validation he can do it by following Window->Preferences->Validation.

Figure 4.12. Validation configuration

4.2.2. ODE Deployment Descriptor Editor

To deploy your process in Ode you need to create a simple deployment descriptor with basic information and ODE Deployment Descriptor Editor facilitates the process of descriptor configuration. You can see how the descriptor file,opened in the editor looks like on the picture below:

Figure 4.13. ODE Deployment Descriptor Editor

The table below describes the configuration options of the ODE Deployment Descriptor Editor:

Table 4.2. ODE Deployment Descriptor Editor.Options.

Section	Options	Description
General	This process is	Select one of the provided options: activated deactivated retired
General	Run this process in memory	for performance purposes, you can define the process as being executed only in-memory.
Inbound Interfaces(Services)	Associated Port	Click Associated Port and the dropdown list with all available port names will appear. Select the one you need ,other fields will be filled automatically. This action configure the services provided by the process and bind each service to an endpoint
Outbound Interfaces(Invokes)	Associated Port	Click Associated Port and the dropdown list with all available port names will appear. Select the one you need, other fields will be filled automatically. This action configure the services invoked by the process
Process-level Monitoring Events	None All Selected: Instance life cycle Activity life cycle Data handling Scope handling Correlation	Using ODE's deployment descriptor, it's also possible to make events generation to filtrate which ones get created. All option just duplicates the default behaviour, when nothing is specified in the deployment.
Scope-level Monitoring Events	Scope	This section makes it possible to define filtering for each scope of your process.

Create new JBoss Tools Documentation Jira issue