The Quick Start guide explains how to set up and start the WSO2 BPS, model a BPEL process, deploy and test it using the WSO2 BPS management console. The guide has the following sections:
...
Table of Contents | ||||
---|---|---|---|---|
|
Setting up the BPS
Anchor | ||||
---|---|---|---|---|
|
WSO2 BPS setup is very simple. While more detail of the installation can be found in the Getting Started, we have given below a basic summary to get you started fast.1.
- Ensure that the following are installed in your environment.
- JDK 1.6.* or higher.
- JAVA_HOME environment variable is set to <JDK_HOME>. For example,
JAVA_HOME=c:\Program Files\java\jdk1.6.0_27
.
...
- Download the BPS binary distribution from http://dist.wso2.org/products/bps/3.0.0/wso2bps-3.0.0.zip.
...
- Extract the zip file to a folder which will be referred to as <CARBON_HOME> throughout the rest of this guide.
...
- Open a command prompt (or a shell in Linux) and go to <CARBON_HOME>\bin directory.
...
- Start the BPS server by executing wso2server.sh (or wso2server.bat in Windows).
...
- The operation log keeps running until the server starts, which usually takes several seconds. Wait until the server fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."
Modelling a BPEL Process
Anchor | ||||
---|---|---|---|---|
|
...
Info | ||
---|---|---|
| ||
Alternatively, you can use the SOAP UI tool to test a business process. The SOAP UI application shows the request/response soap messages and is particularly helpful in error handling. |
Writing a human task artifact
Business processes cannot always proceed in a fully automated manner. They need human interaction as a means of decision making, error handling and exception cases. For example, canceling a flight due to a strike or bankruptcy, deciding whether to accept the claim based on the requested amount etc. Human tasks provide the specification to define tasks performed by human beings.
Sample scenario
When a user requests a claim to be approved by the system, the system automatically approves claims under an amount of 1000 .This is a simple BPEL process. If the claim exceeds 1000, it will be handed over to the regional clerk who checks the claim amount along with the user information, decides whether or not to approve it, and the final decision is sent to the user. So when the claim is higher than 1000, it will be processed as a human task. The sample process is shown below.
Writing human tasks
The basic process is designed as a normal BPEL process with an IF component. For human tasks, we use the BPEL4PEOPLE activity remote task. It will get the input from the claim approval request such as the name and amount, and the output is sent via a claim approval callback service as true or false. The user can then see the final decision. This process needs some presentation elements. Human tasks are implemented as JSP pages.
The BPEL process is implemented using the BPEL4PEOPLE activities and deployed into the server. Human tasks have to be deployed as a separate process. Since there is no tool to create a human task workflow, all the steps have to be done manually. However, there is a predefined package structure which makes the work easier. As an initial step, you should create a package structure in your local directory.
Package structure of an HT artifact
There are four components in the HT package.
Table of Contents | ||||
---|---|---|---|---|
|
.ht file
The .ht file contains the information about the human task of the BPEL process. It is an XML-based file consisting of a predefined set of human task description elements. The table below shows the basic elements and their descriptions with some examples from the ClaimsApprovalTask sample.
Element | Description | |||||
---|---|---|---|---|---|---|
<htd:humanInteractions> | Contains declarations of elements from the WS- HumanTask namespace, that is <htd:logicalPeopleGroups> , <htd:tasks> and <htd:notifications> . | |||||
<htd:import> | This is used to import the appropriate WSDL files. You should correctly specify the name spaces. Example:
| |||||
<htd:logicalPeopleGroups> | This is used to specify logical people groups used in an inline human task or a people activity. The name attribute contains the name of the logical people group. The name must be unique among the names of all logical people groups defined within the
| |||||
<htd:tasks> | Specifies the human tasks used in the business process.
| |||||
<htd:task> | This is used to provide the definition of an inline human task. The name attribute specifies the name of the task. The name must be unique among the names of all tasks defined within the It also consists of the
| |||||
<htd:interface> | Specifies the port types and operations of the human task.
| |||||
<htd:peopleAssignments> | Used to assign people to process-related generic human roles.
| |||||
<htd:documentation> | Provides annotations for users.
| |||||
<htd:from>
<htd:argument> | From element used to assign people for roles which have been specified in the business process. Argument element will pass values used in the people query.
| |||||
<htd:presentationElements> | Specifies the user interface for human tasks or how the user interacts with the human task.
| |||||
<htd:notifications> | Used to provide the definition of an inline notification.The name attribute specifies the name of the notification. The name must be unique among the names of all notifications defined within the
|
htconfig.xml file
This file consists of deployment details of the human task. Human tasks supports two task types called task and notification. A task can have a publish and a callback. Publish means providing a service and Callback means calling an external service to provide the output. Notification is also a task type. A notification task provides one operation for external parties to create notifications.
Example from the claim task sample:
Code Block | ||
---|---|---|
| ||
<hic:HTDeploymentConfig xmlns:hic="http://wso2.org/ht/schema/deployment/config"
xmlns:claim="http://www.example.com/claims/"
xmlns:claimtask="http://www.example.com">
<hic:task name="claimtask:ApproveClaim">
<hic:publish>
<hic:service name="claim:ClaimService" port="ClaimPort" />
</hic:publish>
<hic:callback>
<hic:service name="claim:ClaimServiceCB" port="ClaimPortCB" />
</hic:callback>
</hic:task>
<hic:notification name="claimtask:ClaimApprovalReminder">
<hic:publish>
<hic:service name="claim:ClaimReminderService" port="ClaimReminderPort" />
</hic:publish>
</hic:notification>
</hic:HTDeploymentConfig> |
Here, the htconfig.xml file consists of three services used by a human task; get data from the user, call back of either approve or not and the reminder web service.
<Service>.wsdl
You can have one or more WSDL files which have been used in the BPEL process. You can have a composite WSDL addressing many web services. Claim Approval task has one composite WSDL.
Web folder
There are four .jsp files inside the web folder. Three .jsp files end with:
- <TaskName>-input.jsp
- <TaskName>-output.jsp
- <TaskName>-response.jsp
<TaskName>-input.jsp
The input.jsp file uses the (OMElement) request.getAttribute("taskInput")
attribute to obtain the task details of the OMElement. This is inserted into the JSP context from BPS. The input.jsp file is used to show the task information to the task user.
Example from the ApproveClaim-input.jsp:
Code Block | ||
---|---|---|
| ||
OMElement requestElement = (OMElement) request.getAttribute("taskInput");
String ns = "http://www.example.com/claims/schema";
if (requestElement != null) {
OMElement customerElement = requestElement.getFirstChildWithName(new QName(ns, "cust"));
if (customerElement != null) {
OMElement id = customerElement.getFirstChildWithName(new QName(ns, "id"));
if (id != null) {
customerId = id.getText();
} |
The input web will show the human task list of the regional clerk user.
<TaskName>-output.jsp
The output .jsp is used to provide the user with a task form. Task processing happens when this is completed and submitted by the user.
All output .jsp files should implement the JavaScript method:
Code Block | ||
---|---|---|
| ||
createTaskOutput = function() {
}; |
This should provide the corresponding XML string expected by the task operation.
Example from the ApproveClaim-output.jsp:
Code Block | ||
---|---|---|
| ||
createTaskOutput = function() {
var outputVal = getCheckedRadio(); //get approve or not from radio button
if(outputVal == 'approve') {return'<sch:ClaimApprovalResponse xmlns:sch="http://www.example.com/claims/schema"><sch:approved>true</sch:approved></sch:ClaimApprova lResponse>';
} else if (outputVal == 'disapprove') {return'<sch:ClaimApprovalResponse
xmlns:sch= "http://www.example.com/claims/schema"> <sch:approved>false</sch:approved>
</sch:ClaimApprov alResponse>';
}
}; |
Output JSP is used by the regional clerk user to approve the claim.
<TaskName>-response.jsp
Response.jsp is used to display the output of the completed task. It also uses the OMElement responseElement = (OMElement) request.getAttribute("taskOutput"); to obtain the OMElement corresponding to the output.
Example from the ApproveClaim-response.jsp:
Code Block | ||
---|---|---|
| ||
String approved = "No Value Assigned";
OMElement responseElement = (OMElement) request.getAttribute("taskOutput");
if (responseElement != null) {
approved = responseElement.getFirstElement().getText(); } |
The response after approving the claim looks like this:
Info |
---|
An additional .jsp called <TaskName>-Reminder-input.jsp exists to send reminders for task caller. |
Excerpt | ||
---|---|---|
| ||
The Quick Start guide of the WSO2 Business Process Server. |