A quick look at WSO2 Business Process Server (BPS)

WSO2 Business Process Server (BPS) is the newest member of WSO2 SOA product suite. It is developed on top of the revolutionary WSO2 Carbon platform hence the components of WSO2 ESB, WSO2 Web services application server (WSAS) can easily be plugged in.
WSO2 BPS provides the facilities to execute business processes written using the WS-BPEL standard. It uses Apache ODE as process server engine.
I'm going to demonstrate how a simple BPEL package will be deployed in WSO2 BPS and some of the features such as process instance creation and process summary statistics.

Step 1
Download WSO2 BPS-1.0 from here. Extract the downloaded zip into a directory. We will refer to the extracted location as BPS_HOME

Step 2
Start business process server by running wso2server.bat{sh} which can be found at BPS_HOME/bin

Step 3
Access BPS management console using https://localhost:9443/carbon. Log in to management console using the default administrator credentials, admin/admin
BPS Home page will be displayed as follows.



Step 4
We are going to deploy a new BPEL package. BPEL package is a ZIP archive with all the relevant deployment artifacts. BPEL package should contain the deployment descriptor, one or more process definitions(.bpel or .cbp), WSDL and XSDs. You may find more information about these artifacts in Apache ODE user guide.
In this demonstration, I will use a sample BPEL package (HelloWorldNew.zip) used for testing purposes. You can download it from here.
Now, select Business Processes --> Add BPEL in the left navigation menu of WSO2 BPS management console. You will be directed to New BPEL Package page. Browse the downloaded HelloWorldNew.zip file in your file system and click on upload.
You will see the confirmation message if the deployement is successful.

Step 5
We have completed adding a new BPEL package. You can find the deployed package in the Deployed Packages page as follows.



Step 6
When you upload a new BPEL package, the associated business process will be created and will be listed in Deployed Processes page. You can find the process definition and more details of the process by clicking on the process ID.



Step 7
When a new BPEL package is deployed, the services which are defined as partner links in the process definition (services participating in a particular BPEL process) will be listed in the Deployed Services page as shown below. You will notice the HelloWorldNew service at the top of the table.



Step 8
Now we can create process instances by invoking this HelloWorldNew service. The simplest way of invoking the service is using "Try this Service" feature associated with the service. Click on Try this Service link in HelloWorldNewService.
You will be directed to Try the HelloWorldNewService service page where you can give any string value as input. Click on Process button to invoke the service.
With different string inputs, invoke the service few more times.

Step 9
After invoking the service, select Business Processes --> Instances in the left menu.
You will see the generated process instances as shown below.



With WSO2 Business Process Server (BPS), you can secure processes using WS-security and enable reliable messaging with minimum configuration steps. I will demonstrate these QOS (quality of service) features in a future post.

For more information about Business process server, access WSO2 BPS home page at WSO2 Oxygen Tank.

Comments

Post a Comment

Popular posts from this blog

WSO2 Stratos - Introducing WSO2 middleware Platform as a Service (PaaS)

Image
Yesterday we released our newest integrated cloud middleware platform, WSO2 Stratos . It is now online and ready for use! For the past few years, WSO2 has been doing many releases based on revolutionary Carbon platform , which helped to consistently improve the platform with introducing latest state-of-art technologies. The initial releases of Carbon product platform intended to improve the features of the individual products. For example, a lot of core features were introduced to WSO2 ESB, WSAS, Governance Registry etc.. Then we focused on ease of integration and more component based model. We introduced Equinox based provisioning model to build your SOA platform by picking and choosing the components as and when you need. Then, the core product platform has been enhanced to support multi-tenancy. With the multi-tenant supported architecture at hand, our brilliant development team was able to introduce the first ever comprehensive middleware PaaS. Why is this so important? Now, WSO2 C...
Read more

Common mistakes to avoid in WSO2 ESB - 1 - "org.apache.axis2.AxisFault: The system cannot infer the transport information from the URL"

In the next few weeks, you could expect a series of blog posts from me which explain the remedies to avoid some common mistakes which we do when working with WSO2 ESB . This is the first of many. During the initial rounds of testing your integration solution or even in production systems, you may have come across the following error. org.apache.axis2.AxisFault: The system cannot infer the transport information from the URL .... Some of you may have struggled hours figuring out a solution to address this issue. Let me explain this error in detail and possible causes of this. So, next time when you see this error in your WSO2 ESB setup, you will not have to spend time unnecessarily googling everywhere. There can be many different causes of this error. I have observed  four main reasons. Cause 1 This is the simplest cause. Suppose, you have a proxy service similar to the following. <proxy xmlns="http://ws.apache.org/ns/synapse" name="MistakesTest...
Read more

Working with HTTP multipart requests in soapUI

Image
You can use HTTP request test step in soapUI to submit messages with various Content-Types.  In this post, we will have a quick look into the multipart/form-data requests in soapUI. multipart/form-data requests usually come into action when you do HTML form submissions with file attachments. For example, have a look at the following HTML form post. <form action="http://localhost:8090/CKFileUploadApp/UploadServlet" method="post" enctype="multipart/form-data"> <input type="file" name="file"> <input type="text" name="paramName"> <input type="submit" name="Submit" value="Upload File"> </form> In the forms like above, we have file upload option as a form input where we can upload a file along with the form submission. In that case, the request's HTTP content type will be multipart/form-data. How can we simulate such a request using soapUI...
Read more