Adding BPEL features to WSO2 WSAS/ESB

A few days back, WSO2 has released carbon feature packs which allow users to integrate various functional components into their existing WSO2 products. I blogged about plugging in service hosting components into ESB while we were preparing for carbon release. With the carbon feature packs, now it is much more easier to add the functionalities what you want.

WSO2 BPS provides the facilities to execute business processes written using the WS-BPEL standard. BPEL feature pack enables the business process management inside your WSO2 WSAS or ESB instances.
Let's see how BPEL features can be added to WSO2 WSAS or ESB.

Pre-requisites:
Install WSO2 WSAS-3.0.1 or WSO2 ESB-2.0.1

Step 1
We are hoping to install BPEL features into WSAS or ESB. Therefore, download BPEL feature pack from here.

Step 2
Unzip the downloaded feature pack into a directory in your file system (suppose it is $BPEL_feature_pack_home)
You will see two sub directoris inside the extracted zip file, plugins and repository.

Go to $BPEL_feature_pack_home/plugins/ directory and copy all the jars to WSAS_HOME/webapps/ROOT/WEB-INF/plugins/ directory. (WSAS_HOME is the root directory of your WSO2 WSAS instance)

Then, go to $BPEL_feature_pack_home/repository directory and copy the contents to WSAS_HOME/repository.

Step 3
Restart WSO2 WSAS and access management console. You will see the BPEL features shown in the left menu as follows.



Thats it. We have installed BPEL features into WSAS. You could follow the same steps to install BPEL features into WSO2 ESB.

Comments

Bacardi said…
Hello,

I'm trying to install BPEL features on WSAS 3.1.3. on WSAS_HOME, the plugin folder contains 3 subfolders: commmon, console and server. I tried copying the jars to the root of plugin, and into those 3 folders, but the BPEL functionalities never show up.

Can you help me with this, please?
Thanks in advance

Tiago
March 12, 2010 at 8:00 AM
Charitha said…
Hi,
In WSAS-3.1.3, you do not need to manually copy the jiras, Equinox P2 based provisioning will do it for you. It is very simple now.

1. Start WSAS with wso2server.bat -DosgiConsole
2. After the server get started, press enter, you will get Osgi Console.
3. Then Issue the following commands

provaddrepo http://dist.wso2.org/p2/carbon/releases/2.0.3/

provaddartifactrepo http://dist.wso2.org/p2/carbon/releases/2.0.3/

provinstall org.wso2.carbon.bpel.feature.group 2.0.3

4. Restart the server.

Thats all

Regards
Charitha
March 12, 2010 at 9:04 AM
Unknown said…
Hello Charitha,
I'm trying to install BPEL features on wso2esb-3.0.0.

I've followed your instructions from the last post and when the server restarted it threw two exceptions:

- The first one: org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Package uses conflict: Import-Package: org.wso2.carbon.core.util; version="0.0.0"

- And the second one: java.lang.ClassCastException: org.wso2.carbon.bpel.ode.integration.management.InstanceManagementServiceMessageReceiverInOut cannot be cast to org.apache.axis2.engine.MessageReceiver

After restarted, the interface include a the new "business Processes" section in the menu, but when one of these new options is selected, many exceptions are thrown and the interface shows a empty page.

Please, ¿could tell me what is wrong?
¿Are wso2esb-3.0.0 and org.wso2.carbon.bpel.feature.group 2.0.3
compatible?

Thanks in advance
Adolfo
June 8, 2010 at 7:13 AM
Charitha said…
Hi Adolfo,
This blogpost is not applicable for WSO2 ESB-3.0.0. In WSO2 ESB-3.0.0, you can easily add BPEL features by accessing the feature manager UI. Just log in to management console using https://localhost:9443/carbon and click on "features" at the left menu. Then select "Add repository" and add "http://dist.wso2.org/p2/carbon/releases/3.0.0/" as the URL. After adding the repository, search for BPEL feature in "Available Features" tab and install it.
Please let me know, if you encounter any issues.
Regards
Charitha
June 8, 2010 at 8:41 AM
Unknown said…
Hello,

I have accessed the feature manager UI and I have added the repository but BPEL is not included in the available features list.

Is there any new version of the repository?

Valen
July 14, 2010 at 3:32 AM
Unknown said…
Hi Charitha,
I followed yours instructions

"In WSO2 ESB-3.0.0, you can easily add BPEL features by accessing the feature manager UI. Just log in to management console using https://localhost:9443/carbon and click on "features" at the left menu. Then select "Add repository" and add "http://dist.wso2.org/p2/carbon/releases/3.0.0/" as the URL. After adding the repository, search for BPEL feature in "Available Features" tab and install it."

But in WSO2 ESB I have the same problems of Adolfo and I can't deploy any BPEL.

When I used the rep. http://builder.wso2.org/~carbon/releases/carbon/3.0.0/4RC24/p2-repo/
I hadn't any problems and BPEL
deployment was correct (now thi rep. is offline).

Thanks in advance.
Matteo
September 21, 2010 at 2:14 AM
Unknown said…
When I try to deploy a BPEL I obtaion this ERROR:

[2010-09-21 12:26:09,687] ERROR - BPELPackageManagementServiceSkeleton Failed to
get BPEL process store from axisconfig.

Matteo
September 21, 2010 at 3:25 AM
rulix batistil said…
Hi,

I am using wso2esb-3.0.1 version and add the BPEL features in the UI.

However when I restarted the esb server, I got osgi and eclipse related exceptions below


org.osgi.framework.BundleException: The state indicates the bundle is resolved at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolution FailureException(AbstractBundle.java:1296)


Could you help me fix this issue?

Thanks,
Rulix
February 2, 2011 at 1:16 PM
Post a Comment

Popular posts from this blog

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&q
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

How to configure soapUI to send HTTP chunked encoded requests

Image
soapUI makes use of Apache HttpClient (based on HTTPComponents project) as the client side HTTP implementation. When submitting requests using soapUI, you may have noticed that, the requests always send Content-Length HTTP header. You can find it out in the Raw View of the request editor. POST http://localhost:9000/services/SimpleStockQuoteService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: text/xml;charset=UTF-8 SOAPAction: "urn:getQuote" User-Agent: Jakarta Commons-HttpClient/3.1 Host: localhost:9000 Content-Length: 416 In functional and non-functional testing, we usually need to test the servers by sending HTTP requests with both Content-Length as well as chunked transfer encoding. How can we configure soapUI to send chunked encoded requests instead of Content-Length? Step 1 Click on Global soapUI Preferences icon in the main tool bar (Or else, click on File --> Preferences) Step 2 HTTP Settings tab will be selected by default. You will notice
Read more