In this paper, we will look at OpenLink latest addition to it product portfolio, the BPEL process manager and administrator, which are built on Virtuoso BPEL4WS Execution engine that provides the ability to deploy and run business processes defined in BPEL 1.1.

1.2 BPEL Overview

1.2.1 What is BPEL

BPEL4WS ( Business Process Execution Language for Web Services) or BPEL for short is an emerging as the standard designed for orchestrating services into transactional process flows in an order in which it is meaningful to the participating partners or services. BPEL 1.1 was originally designed and developed by IBM and Microsoft which was based on their respective work on WSFL and XLANG has now been standardized by OASIS Web Services BPEL Technical Committee (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel).

For the enterprise, BPEL offers the promise of reducing the cost and complexity associated with process integration of proprietary EAI and BPM solutions, which are expensive to develop, maintain, and extend across diverse, heterogeneous environments.

Virtuoso Universal Sever BPEL implementation offers a seamless addition to Virtuoso's database federation, XML and web services features.  It builds on the strength of having a local high performance relational data store for process persistency and does not require any third party application server infrastructure or databases.

`1.3` `OpenLink Process Manager`

OpenLinks Process Manager and Virtuoso BPEL4WS Execution engine key features include:

Robust BPEL Engine and Deployment Platform: Virtuoso Universal Server provides a fully featured native BPEL 1.1 engine that supports the invocation and deployment of BPEL scripts as well support for long-running and asynchronous business processes.
Business Activity Monitoring: OpenLinks Process Manager is a web-based user Interface for testing, debugging, and monitoring deployed business process. This includes support for compensation, fault handling and event handling.
WS-Reliable Messaging and Security: Enterprises can now deploy business-critical transactions over the Internet using the WS-Reliable Messaging (WS-RM) specification. WS-RM support means that guaranteed (at-most-once, at-least-once, and exactly once) messaging is now possible over HTTP. Virtuoso BPEL4WS Execution engine implementation can also make use of Virtuoso full array of web service protocols including WS-Security.

Database, XML and Web Service Integration: Virtuoso's extensive virtual database, XML and web services features provide forintelligent transformation for XML and non-XML applications and data. Virtuoso allows integration of databases into Service-Oriented Architectures (SOAs), by automating the creation of Web services from multiple tables in any ODBC, JDBC or ADO .Net-compliant database. BPEL processes can directly invoke locally hosted Java or .Net logic and access SQL data from resident in local and remote tables. This enables the rapid integration of that data with other services.
Import and Execution of any Standards-Based BPEL Business Processes: Virtuoso BPEL4WS supports standards compliant BPEL 1.1 scripts so that industry Standard Compliant BPEL processes can be developed in any of the BPEL modeling tools and deployed on the Virtuoso platform.
Interoperability OpenLinks BPEL Process Manger and Virtuoso BPEL4WS Execution Engine S have gone through an extensive interoperability testing against Microsoft, Oracle, and other vendor’s implementations. Through thorough testing of these processes, it validates the BPEL engine and ensures the rapid orchestration of existing Web services.

2 System Requirements

Software

Virtuoso Universal Server 4.0
Virtuoso Conductor VAD 04.00.2803
BPEL4WS VAD

Hardware

Operating Systems and Browsers

Compatible with Windows 2000, XP, Server 2003
Any Unix
MacOS X
IE, Mozilla, etc.

3 Installation

The OpenLink BPEL Process manager and Virtuoso BPEL4WS Execution Engine comes packaged in a file called BPEL4WS.vad This VAD (Virtuoso Application Deployment) package contains all of the components to install the application, which include table creation, default data, stored procedures, access credentials and example tutorials. The BPEL4WS.vad is a feature component of the Virtuoso Universal Server 4.0 installers and is installed in the Demo Database server by default.

Note: A VAD package is small and completely portable. VAD packages can be copied to any OS and invoked to create any number of applications.

3.1 BPEL Install via Openlink Virtuoso 4.X Setup Installer

You can optionally install the BPEL4WS.vad by uploading the file into Virtuoso Conductor or installing the VAD via ISQL. .

3.2 Conductor Installation

Step 1. Once the BPE4WS VAD package has been downloaded and copied to a local directory you can invoke the Virtuoso Conductor using the browser of your choosing. Example: http://localhost:6666/conductor.

Step 2. Login into the Virtuoso Conductor using the admin account, then navigate to the Systems Admin Tab and select the Packages Tab.

Step 3. Under the Install Packages, section of the UI is a list of VAD packages.

Note: If this is the first time you have installed a VAD package you will only see the Virtuoso Conductor.

Step 4. Directly under this list is the option to Install a Package. You can either enter or browse to the location of the directory of the BPEL4WS package or enter a DAV location.

Once you have provided the location, select proceed to upload the package as shown in Figure 1 below.

Figure 1: Conductor VAD packages Installation

3.3 ISQL Installation

Step 1. Once the BPE4WS VAD package has been downloaded, copy the bpel4ws.vad file to any local directory.

Step 2. Invoke the command line ISQL utility and run the Virtuoso SQL procedure vad_install and the parameters bpel42ws and zero as shown below.

C:\Program Files\OpenLink\Virtuoso 3.0\bin\isql.exe

SQL>

SQL> vad_install (‘bpel4ws.vad’,0);

SQL> exit;

3.4 Running the OpenLink Process Manager

After installation via the Conductor or executing this file (VAD package) through ISQL, several database objects will be created as well as the virtual directories /BPEL and /BPELGUI and physical directories c:/program files/OpenLink/Virtuoso 4.0/vsp/vad… After a successful VAD install the next step is to run the OpenLink BPEL Process Administrator, (BPELGUI) to administer BPEL4WS processes as shown below in Figure 2. http://localhost:port/BPELGUI

Figure 2: OpenLink Process Manager

4 BPEL Process Deployment and Testing

Now that we have successfully installed the BPEL4WS VAD package, we can begin with testing some processes. The BPEL4WS VAD package ships will a number of samples. The location QuickStart that includes a list of samples. This screen is available from the URL: http://host:port/BPELGUI/start.vsp as show below in Figure 3.

Figure 3: OpenLink Process Manager Quick Start

5 BPEL Process Deployment

The following is step-by-step instruction for loading, running and managing with LoanFlow BPEL process.

LoanFlow Setup

Before we begin, Let us take a quick look at the LoanFlow Process. The basic steps of this process are as follows:

Step 1. Loan Applicant sends a request for a loan.

Step 2. The request gets processed (CreditRating)

Step 3. Credit gets routed to a Loan Provider and offers are sent (UnitedLoan and StarLoan)

Step 4. Lowest Loan offer is chosen

Step 5. Applicant receives Loan approved with the best rate.

The QuickStart screen provided shows the location for the LoanFlow sample. This directory includes the LoanFlow wsdl, LoanFlow Bpel script, and deployment and sql files.

Copy the sql file to a local directory from:

http://host:port/BPELDemo/LoanFlow/LoanFlow.sql This SQL file will create the tables necessary to run the LoanFlow example in this document and will deploy the LoanFlow process. To Load this file into Virtuoso you have two options. The first option is to invoke the Virtuoso Conductor User Interface and select the Interactive SQL utility under the database tab as show below in Figure 4.

Figure 4: Conductor Interactive SQL (ISQL)

The next option is to load the file using the command line ISQL-Utility. This tool can be invoked directly from the command line or from the Conductor by navigating to the Database Tab and selecting ISQL.

Step 1. Load the given LoanFlow SQL file using ISQL command line utility.

SQL> load LoanFlow.SQL

The diagram in Figure 5 below shows this external view of the loan request process

LoanFlow Process

Figure 5: LoanFlow Process diagram

In this section, we will initiate the LoanFlow Process using the OpenLink Process Manager (OBPM) and console. Through this console, you will be able to upload the BPEL process, invoke, test and deploy a process instance. In addition, you can view the current state of an instance, debug, audit, update links and view reports throughout the life cycle of a process.

Step 1. Step 1. After you have setup the LoanFlow Database, invoke the OBPM by navigating to the URL: http://host:port/BPELGUI/

Step 2. Login to the OBPM using the administration username and password, which by default is dba as shown below in Figure 6.

Figure 6: OpenLink Process Manager Login

Step 3. The home screen consists of two sections: Tasks and Info as shown in Figure 7 below:

Figure 7: OpenLink Process Manager Home

Tasks Section: Contains a set of links that are shortcuts to the basic activities you can perform with OBPM :

View Process
Upload Process
Debug Process
View Instances
View Reports
Configure System

Info Section: Provide a set of links to:

View On-Line BPEL Tutorials;
BPEL Process Manager Reference Guide;
BPEL Interop Web Site.

Step 4. The next step is to select the Processes Tab from the Main Navigation toolbar as shown in Figure 8 below. Under this tab, there are two options:

Process List: Provides a list of active processes
Process Upload: Provides the option of loading BPEL scripts and corresponding WSDL files or the BPEL deployment file.

Figure 8: OpenLink Process Manager Processes List

Step 1. After you have run the LoanFlow.sql file using ISQL or the Interactive ISQL screen from Conductor, the process should be deployed automatically and you will be able to view it in the list of processes.

Step 2. Now if you want manually to upload the LoanFlow process, click on the link LoanFlow in the column ‘Name’ from the Processes List as shown in Figure 9 below.

Figure 9: OpenLink Process Manager Process

Step 1. Click on the link ‘Delete all versions and instances. The result will be displayed in the screen as shown in Figure 10 below:

Figure 10: OpenLink BPEL Delete Process Confirmation

Step 2. Click the button ‘Yes’ to confirm deletion of the LoanFlow process.

Step 3. To upload the LoanFlow BPEL process, select Process Upload tab, enter for Process name ‘LoanFlow’ and enter location of the Virtual directory containing the URL of the BPEL file. Click the ‘Import Process’ button. For example http://localhost:6666/BPELDemo/LoanFlow/bpel.xml as shown in Figure 11 below:

Figure 11: OpenLink Process Manager Upload Process

Note: Optionally you can enter the BPEL and WSDL files located in a local directory or DAV location by choosing for Deployment Methods ‘Upload process’ as it is shown in Figure 12 below:

Figure 12: OpenLink Process Manager Upload Process

Once you have successfully imported the bpel.xml file, the Process Upload Details screen for deploying BPEL Process will be displayed. In this screen, we can enter the values for deploying the LoanFlow BPEL Process as it is shown in Figure 13 below:

Figure 13: OpenLink Process Manager Process Upload Details

6 Configuring the LoanFlow endpoints

In Figure 13, the following attributes for the LoanFlow process are presented:

Process Name: Contains the non-editable value of the process, which in this case is 'LoanFlow'.

6.1

BPEL Buttons: Options include View, and Update

By selecting the View icon, the content of the BPEL file will be shown as in Figure 14 below. Use the Close icon for closing the screen and return to the form screen.

Figure 14: OpenLink Process Manager View file for bpel

When the Update icon is chosen, the content of the BPEL file can be changed by typing URL for the file or upload the file from the current file system by hitting the browse button as shown in Figure 15 below. To upload the chosen file, use the Upload icon. Use the Back icon for returning to the form screen.

Figure 15: OpenLink Process Manager Upload BPEL file

WSDL Buttons: Options include View and Update

By selecting the View icon, the content of the WSDL file will be shown as in Figure 16 below. Use the Close icon to close the screen and return to the form screen.

Figure 16: OpenLink Process Manager View file for WSDLs

When the Update icon is chosen, the content of the WSDL file can be changed by typing URL for the file or upload the file from the current file system by hitting the browse button as it is shown in Figure 17 below. To upload the chosen file, use the Upload icon. Use the Back icon for returning to the form screen.

Figure 17: OpenLink Process Manager Upload WSDL file

Partner Links: In this section, a list of the partner links for the process is shown. In the case of the LoanFlow example, there are four partner links, which include:

client
CreditRatingService
UnitedLoanService
StarLoanService

Next to each of these partner links there are two icons:

When the View icon is selected, in a new pop-up screen is displayed the content of the wsdl file of the current partner link.
Use the Close icon for closing the screen and return to the Process Upload Details screen.
The Update icon provides an option to update the content of the wsdl file by providing an option to upload a new WSDL file. On this screen there are two choices provided to upload the file by URL or physical location. To exit this screen, select the Back icon for returning or the Upload icon to upload the process.

Action section: The actions section provides the following options for a process:

Compile: The Compile Button, compiles the process, as well as verifies if there is no wsdl file defined for partner link.
Delete: The Delete Button will delete a process and all its versions. Note: a confirmation is issues before parentally deleting the process.

The Refresh Icon can be selected if there are any files that have been updated including BPEL, WSDL or WSDL files for the partner links, the changes will only be reflected after a refresh.

Note: The option is only necessary if the user wants to review any of the recent uploaded or changed files.

Figure 18: OpenLink Process Manager Process Upload details

7 LoanFlow Process Compilation, Testing and Deployment

In this section, you will learn how to compile, test and view the LoanFlow BPEL process in the OpenLink Process Manager.

7.1 Compiling BPEL Processes:

Step 1. Under the Process Upload, select the Compile Process button on the bottom to compile the LoanFlow process,

Step 2. Assuming the process compiles successfully, you will be redirected to the Processes List screen, which is under the Processes tab on the main navigation toolbar as shown in Figure 19 below.

Figure 19: OpenLink Process Manager Processes List

Step 3. Click on the ‘WSDL’ link from the Properties column in order to view the wsdl file content of the LoanFlow process. As result a new screen will be given with the content of the wsdl file as shown in Figure 20 below:

Figure 20: OpenLink Process Manager WSDL file content view

Step 4. Click on the ‘Source’ link from the Properties column in order to view the source file content of the LoanFlow process. As result a new screen will be given with the content of the source file as shown in Figure 21 below:

Figure 21: OpenLink Process Manager BPEL file content view

Step 5. Click on the ‘Graph’ link from the Properties column in order to view the graph with activities for the LoanFlow process. As result in tree mode view will be given the list of these activities as shown in Figure 22 below:

Figure 22: OpenLink Process Manager Process Graph view

Step 6. Click for example on the ‘Receive’ activity to view its properties. On the given activity’s property screen there is given the list of the properties for the activity and their values as shown in Figure 23 below:

Figure 23: OpenLink Process Manager Activity

Step 7. Now go back to the Processes List screen as shown in Figure 24 below:

Figure 24: OpenLink Process Manager Processes List

Note: If you want to change the content of the BPEL, WSDL files or WSDL of the partner links, you can use the ‘Redefine’ activity and will be given as result the edit process screen as shown in Figure 25 below:

Figure 25: OpenLink Process Manager Process Edit

Now click on the ‘Edit Process’ button. As result the Upload Process details screen will be given as shown on the Figure 26 below:

Figure 26: OpenLink Process Manager Upload Process Details

On this screen after changing the content of the relevant files, compile the process. As result on the processes list screen, there will be two processes as shown in Figure 27 below:

Figure 27: OpenLink Process Manager Processes List

Note: Observe the two process of LoanFlow whose state is obsolete and one that is current. LoanFlow Process.

The Processes List contains a list of uploaded processes. In this screen, you can optionally select a list of processes using filter criteria to reduce the list presented by entering values in the Process Filter criteria. The Process filter criteria selection consists of two fields:

· Name contains – This will limit the rows selected to the input value.

· Current version only checkbox – This will reduce or limit the row to the current running version.

Note: The Filter icon will filter or limit the rows for the process list and the Clear icon will clear process list screen.

Directly under the Process List criteria are the Process list and a number of columns per process. The values under each of the columns will vary based on state of the process and method of upload. The columns are as follows:

Table 1 – Process List Criteria

Column Name	Description
Name	The name of the process
URI	URI for a given process
State	Presents the current state of the process (edit
Upload Date	Presents how long the process has been deployed (example 20 mins ago)
Audit Check Box	If is checked (which is by default), an audit file will be created for each instance run for the process If is unchecked, the audit is disable and no audit file will be created for the process's instances.
Debug Check box	If is checked, the Debug option is enabled and when invoking the process, user can go through it step by step If is unchecked, the Debug is disabled
Properties Links	GRAPH Link presents a tree mode for activates for the process	WSDL Link provides the associated wsdl for the process	SOURCE link displays the content of the Processes BPEL file.
Actions Links	REDEFINE leads to the screen where the user can redefine the process: If the process is in 'Current' mode, after 'Redefine' is hit, the user is redirect to the screen where there is 'Edit Process' button	TEST leads to the screen where the user can test the process (this we will discuss later) This link is enabled only when the process is in state 'Current'	PARTNER LINKS leads to the screen, which is giving list of partner links for the process:

Step 1. Under Action, select the highlighted Partner Link for the current LoanFlow process. The source is highlighted:

Step 2. As shown in Figure 28 below the information about Partner Links for the LoanFlow BPEL process is provided. The options on the screen are as follows:

· Select the Properties icon to view the properties of the Partner Link. This will go to a separate screen showing the properties for the Partner Link such as WS-Addressing, Delivery Execution, WS-Security, etc.

· Select the View icon, which will show the WSDL file for the current Partner Link. This will bring up pop-up screen showing the wsdl content of the process.

· Select the Edit icon if you need to change the Endpoint values, the Backup or the Debug for the process.

Figure 28: OpenLink Process Manager Partner Links

On this screen, next to each partner link for the LoanFlow process we can modify the following:

Change the Endpoint Value or Backup or toggle the debug by selecting the Edit icon as show below in Figure 29.

Figure 29: OpenLink Process Manager Edit Partner Link

Under Actions: by selecting the Properties icon we can change the WS-Addressing version, Delivery Execution properties and WS-Security for particular partner link as show below in Figure 30.

Figure 30: OpenLink Process Manager Partner Link Properties

On the Partner Properties Page, we can change the following:

· WS-Addressing Version (pulldown values – 2003 & 2004)

· Delivery Execution:

o Prompts for Input and Output (pulldown values - 'None', 'Exactly Once', 'In Order')

· WS-Security:

o Values for the Key and Partner Public Key can be select from the Security tokens screen

· Checked/Unchecked Input and Output.

· Actions:

o Select the Save Icon to save your selections

o Use the Close Icon to close the screen and return to the partner links list screen.

Figure 31: OpenLink Process Manager Security Tokens

8 Testing the LoanFlow BPEL Process

In this section, we will initiate a test instance of the LoanFlow BPEL process.

Step 1. Select the test link for the process LoanFlow. This will bring you to the debugger tab.

Step 2. Under Action, select Invoke as shown below in Figure 32.

Figure 32: OpenLink Process Manager Invoking BPEL Process

Step 3. Enter values for each field prompt as shown below in Figure 33 below.

For example, enter the following values for the Loan Application:

· SSN (string): 12345

· email (string): test@openlinksw.com

· customer Name (string): Mary Jennings

· loan Amount (double): 3000

· car Model (string): Ford Mustang

· car Year (string): 1999

· credit Rating (int): 5

Figure 33: OpenLink Process Manager Invoking BPEL Process and Name prompt

In Figure 34, we can view the message before we run our test by selecting the 'Preview’ button to view the message before invocation.

Figure 34: OpenLink Process Manager Invoking BPEL Preview the Process

Next, Let us invoke the process.

Once invoked the process will return with out errors, however you may want to see view the response messages of the instance, which is discussed in the section 9.

9 Viewing the Debug Response Message and Actions

9.1 Debugging Response Messages

To view the debug Response message go back to the process view on the Processes List screen and check the audit and debug checkbox for the process LoanFlow with state current, then select test and enter your name again.

Note: Unlike the first test round, you will see a row containing the date, direction, operation, and process name or audit trail for this completed instance.

Step 1. Select the Actions icon on the far right as shown below in Figure 35 below.

Figure 35: OpenLink Process Manager Queue

In the console response message screen you can go back to return to the process or discard any remaining operations as shown below in Figure 36 below.

Figure 36: OpenLink Process Manager Outgoing Message

As shown in Figure 36 above in this particular LoanFlow process we are presented with the 'Outgoing message' properties, which include:

Instance
Partner
Endpoint
Node ID
SOAP-ENV:Envelope document

Here are two options:

1) Hit the button 'Proceed with invoke with partner'

2) Alternatively, enter a value for credit rating (example 5) and select 'Send Reply’.

For this demonstration, select the 'Proceed with invoke with partner'.

Once you have selected the button you will be returned to the debugger console as shown in Figure 37 below. Click the Refresh icon.

Figure 37: OpenLink Process Manager Debugger Console

Note: the queue has four messages on the list for process LoanFlow.

For each message, the actions performed are the same:

Example: Choose the partner UnitedLoanService with direction 'out' and hit 'Actions' icon. As result is given 'Outgoing message' properties as shown in Figure 38

Note the values are:

Instance
Partner
Endpoint
Node ID
SOAP Envelope

At the bottom select proceed with invoke partner as shown in Figure 38 below:

Figure 38: OpenLink Process Manager Invoking a Partner

10 Viewing Process Instances

Now that we have tested and debugged the process as seen in section 9, we will return to the Process List screen so we can view all occurences of the LoanFlow process we have tested.

10.1 Viewing Process Instances

Step 1. Go back to the process screen by selecting the process tab as shown below in Figure 39.

Figure 39: OpenLink Process Manager Processes List

Note: There may be several occurences of the LoanFlow process, each with different states.

Step 2. For this example, select the LoanFlow Link next to the state with the value current, which will bring you to the Process details Screen as shown below in Figure 40.

Step 3. Under this screen, we view the details of the LoanFlow process. In addition, its states. In the next section, we can view the instance, current state as well as return to other steps easily by the links displayed.

Step 4. These include, redefining the process, testing, updating partner links, restarting or deleting specific instance and the removal of all version instances.

Figure 40: OpenLink Process Manager Process Details

11 Process Audit, Status and Removing an Instance

The next step is to review the process audit. In the audit screen, each event shows the current activity info separated by an Id number, a Node name, Additional info and the Date of the event.

11.1 Process Audit

Note: The Audit trail for the instance of a BPEL process in case the Audit for the process is enabled.

Step 1. Continue with Process Screen as shown above in Figure 40.

Step 2. Select the audit link next to the only run id, which will bring up the Audit screen as show below in Figure 41.

Figure 41: OpenLink Process Manager Queue Audit Trail view

11.2 Process Status

The status screen shown in Figure 41 below provides information on the state of each activity for an instance, including variable values, partner links, etc. The information for all the activities is presented in a tree view format. The following highlights information details:

· Those activities whose states are known to be true are highlighted in green.

· Those activities which have state of unknown are marked in red

· For each activity with the known state there are specific properties including variables highlighted in blue, which is a link to an xml document. When these links are selected a new pop-up screen appears containing the xml contents of this variable

For example, to View value for a particular variable, select the input variable crError before the fault-NegativeCredit. Once selected, a screen will be displayed showing the xml content of the variable.

Notes:

1. If there is error while running the instance, you will see the error highlighted in red with the error details.

2. Observe that the Status View continues to change until the moment the instance state is 'Finished' or 'Aborted'.

To return to the Process Details screen select the Back link or the name of the process highlighted in yellow.

· To delete the instance select the Delete Instance button.

Note: Once selected a deletion cannot be undone.

Figure 41: OpenLink Process Manager Status

11.3 Removing an Instance

From the status screen, let us assume we want to remove or delete the instance.

Step 1. From the Status screen, select the “Delete Instance” checkbox.

Step 2. You can see as shown in Figure 42 below we have only process instance where we had two before.

Figure 42: OpenLink Process Manager Queue Process LoanFlow

Instance removed

12 Statistic and Process Reports Section

Statistics including but not limited to script execution times, response times of referenced outside services, and the frequency can all be gathered and viewed under the Statistics and reports tab.

Note: Processes as shown above that have been set into audit mode posts each execution step that is recorded into a file.

Under the Process Statistics,both process and endpoints are easily viewed from the statistics and reporting tab as shown below in Figures 43-45. Thestatistics are divided in two sections: Process Statistics and End Point Statistics.

12.1.1 Process Statistics

By default, the Statistics gathering is disabled. Click on the Enable Statistics button as shown in Figure 43 below.

Figure 43: OpenLink Process Manager Process Statistics disabled

Note: Enabling Statistics can be done also from the End Point Statistics.

Figure 44: OpenLink Process Manager Process Statistics enabled

· Statistics gathering can be stop by clicking the Stop Statistics gathering button.

· Statistics can be reset by clicking the Reset Statistics button.

This screen provides statistical information on each process in the Processes List. This information includes the average time to complete an instance run, the number of active instances total, and the number of completed instances.

Click on the Process name link in order to view the process’s details screen.

12.1.2 End Point Statistics

The Details list provides a list of End Points statistics for each uploaded BPEL process including name of the operation, activity type, average wait time, total wait time, total invokes, total receives, total errors as shown in Figure 45 below.

Figure 45: OpenLink Process Manager End Point Statistics

Click on the Process name link to view the process’s details screen.
Click on the Partner link name to view its properties screen.

12.2. Reports

Under the ReportsTab both details for all process can be filtered by the Instance state execution times viewed and then sorted by the order by instance. The information displayed includes the Process name, Version, Instance ID, Instance state, Inactive time, start time and any errors for the processes as shown below in Figures 46.

Figure 46: OpenLink Process Manager Custom Reports

Step 1. For process name choose the LoanFlow from the given list

Note that the Version field now has the list of all versions of the LoanFlow process. Choose the last item from the list for example.

Step 2. From the Instance State list, select ‘continuing’.

Step 3. Additionally you can specify Start Date or Time Status changed, and the Order by ID, Start Date, and Time Status Changed.

Step 4. Now click the Filter icon as shown in Figure 47 below.

Figure 47: OpenLink Process Manager Custom Reports new filter criteria

As a result, the two instances are filtered with the state, ‘Suspended’.

Click on the Process name link in order to view the process’s details screen.
Click on the Instance Id value in order to view the Instance status.

13 Instances

In this section, we will view the active BPEL instances from the Instances screen in OBPM.

13.1 Instance Screen

Step 1. Navigate to the Instance tab as shown in Figure 48 below. All the instances for all uploaded BPEL processes are listed on this screen.

Step 2. From this screen select any of the links in the Instances List: For example:

· Click on the Process name link to view the process’s details screen.

· Click on the Instance Id value to view the Instance status.

· Click on the View link from the Audit column to view the Audit screen for the current instance.

Alternatively, you may enter search criteria for a given instance.

Figure 48: OpenLink Process Manager Instances

13.2 Instance Search Criteria

The Instances Search Criteria form consists of the following:

Process name : When specified, only processes whose name contains this string will be listed.
Date: When specified Started Since or Started Before, only instances for this date wil are given.
Instance ID: Specify value from the Instance ID's list and enter a number value in the blank field next to the list in order to be included in the Instance Search criteria.

14 Configuration

In this section we will review, the configuration options. Under the Configuration tab, we can set the OBPM options that are listed in the following table:

Table 2 - Configuration Options

Option	Value
BPEL Operator Email address	Example: Test@openlinksw.com
Outgoing SMPP server	Mail.openlinksw.com
Email header for Alert e-mails	Subject {subject} (default)
Subject Heading Error Alerts	BPEL Engine Alert (default)
Template for email alerts	Template provided by default
Subject Heading for error email	BPE Engine Error report (default)
Email template for error notifications	Template provided by default
Instance for interval expiration	24 (default)
Global statistics flag	Not checked by default. If checked you do not have to enable the statistics under this statistic tab.
Directory where any .Net assemblies are stored for process calling programs.	C:/Microsoft VS…..

Figure 49: OpenLink Process Manager Configuration

· Actions:

Select the Save Icon to save your selections Use the Cancel Icon to close the screen as shown below in Figure 28

Click the icon ‘Save’ in order to save your changes

Click the button ‘Restore Defaults’ if you want to undo your changes and get the default settings.

15 Help

On each screen, there is a Help icon, which when selected links to a screen for the relevant help information.

The help information on this screen is organized as follows:

Short description of the screen
Usability of the icons and buttons in order to perform the current activity
A form listing the fields of the screen where each field has a described functionality.

For example, for the Processes List screen if you click this icon, a new pop-up screen will be displayed that contains the help content for the Processes List as shown in Figure 50 below:

Figure 50: OpenLink BPEL Help

Note: If you want to view the help for a current form field only, click on the name of the field, which in fact is a link. For example, if you click on the Name contains link from Process filter criteria for Processes List screen, there will be given the help for this field in a new pop-up screen as shown in Figure 51 below:

Figure 51: OpenLink Process Manager Help Field screen

16 Conclusion

The uptake of BPEL by IT in the last year is impressive since it provides an easy-to-learn language to orchestrate web services. A number of technology vendors such as Oracle and Microsoft support BPEL.

Virtuoso BPEL4WS Execution engine and OpenLinks Process Manager provides an easy-to-use infrastructure for importing, deploying and managing BPEL processes. For the enterprise, Virtuoso BPEL4WS offers a comprehensive and integrated solution, which leverages Virtuoso Virtual database, XML and web services.

17 References

17.1.1 Resources:

BPEL4WS 1.1 Specification locations can be found at

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbizspec/html/bpel1-1.asp or http://www.ibm.com/developerworks/webservices/library/ws-bpel/

OASIS Technical Committee

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel

17.1.2 Tutorials and Training

OpenLink Process Manager comes with a suite of tutorial cases. The tutorials include the following:

Echo
Fibonacci function
Loan Flow

For more information on the Virtuoso Universal Server or OpenLinks Process Manager (OBPM), visit our online documentation or logon to experience our BPEL demonstrations:

Virtuoso Documentation

17.1.3 Process States

The values for the state of a process include the following:

Started
Suspended
Finished
Aborted

17.2 Documentation

Reference Guide

17.3 Tutorials & Samples

The BPEL4WS VAD package for Virtuoso includes a number of simple BPEL process samples. The sample included:

ECHO Simple BPEL4WS process
FI Fibonacci function BPEL4WS process
LOANFLOW LoanFlow process
SECLOAN LoanFlow process using WS-Security
RMLOAN Reliable Loan Flow process
SECRMLOAN Secure and Reliable Loan Flow process
SQLEXEC Using SQL binding and SQLX to generate requests process
USECASES BPEL Data Manipulation Options processes
JAVAEXEC Java Execution BPEL4WS process
CLR-EXEC .NET Execution BPEL4WS process
PROCESSXSLT XSLT processing example
PROCESSXQUERY XQuery processing example
PROCESSXSQL XSQL processing example