How to plug service hosting components in to WSO2 ESB

With the revolutionary WSO2 carbon framework, plugging in service hosting components in to WSO2 Enterprise Service Bus (ESB) is just a matter of seconds! It is extremely simple.

WSO2 ESB is an message mediation framework and the service endpoints usually hosted in a separate JVM. However there may be requirements to host the services inside ESB. There are different types of services you can deploy in a service container.

Axis2 web services
Pojo services
EJB services
Data services
Spring web services
Axis1 services
JaxWS services

Now, you can add any of these service hosting components in to your ESB. Lets see how it can be done.

1. Download WSO2 Enterprise Service Bus (ESB) -2.0 beta2
2. Extract the downloaded zip
3. Go to the bin directory in the extracted folder (ESB_HOME/bin) and run wso2server.sh or wso2server.bat
4. Point you browser to the URL https://localhost:9443/carbon and login as an admin (Use "admin", "admin" as the username and password)



5. Suppose you want JAXWS services are hosted in ESB. Then you need to have the jaxws service hosting components. You will be able to download the individual components from WSO2 Oxygen Tank soon. However, we will downlaod WSO2 WSAS-3.0-beta2 and get the components from it. Therefore, please download WSO2 WSAS 3.0-beta2 and extract the downloaded zip file in to local file system. (Lets name the extracted directory as WSAS_HOME)

6. Go to WSAS_HOME/webapps/ROOT/WEB-INF/plugins. You will find a lot of libraries inside that directory.
Copy org.wso2.carbon.jaxwsservices.ui_SNAPSHOT.jar, org.wso2.carbon.jaxwsservices_SNAPSHOT.jar and org.wso2.carbon.jaxws-2.1.jar files and paste them into ESB_HOME/webapps/ROOT/WEB-INF/plugins
7. Restart WSO2 ESB server
8. Log in to ESB management console again. You will find the JAXWS service component is listed in the left menu.



In this way, you can add any of the above service components into ESB. For example, if you want Axis2 service component inside ESB, you just need to copy org.wso2.carbon.aarservices-SNAPSHOT.jar and org.wso2.carbon.aarservices.ui-SNAPSHOT.jar as explained above.

Comments

ICARO said…
I try to add the dataservice pluggin from wsas to wso2esb server but it doesn´t work via web admin and via config file .ds.
No log information is provide ...
can you help me please?
January 20, 2009 at 5:23 AM
Charitha said…
Hi,
You must copy org.wso2.dataservices.core_SNAPSHOT.jar and org.wso2.dataservices.ui_SNAPSHOT.jar included in WSAS_HOME/webapps/ROOT/WEB-INF/plugins directory to ESB_HOME/webapps/ROOT/WEB-INF/plugins to add the data service functionality in to ESB. Please try with WSO2WSAS-3.0-beta3 and WSO2ESB-2.0-beta3 releases.

regards
Charitha
January 20, 2009 at 7:37 AM
ICARO said…
Hi Charitha,
I use the right versions of the wso2 services wso2esb-2.0-beta3 and wso2wsas-3.0-beta3. I add the plugins for dataservices in the plugins wso2esb directory:
org.wso2.dataservices.core_SNAPSHOT.jar
org.wso2.dataservices.ui_SNAPSHOT.jar
I can see the admin interface to add a new dataservice, but I can´t complete the configuration in the web interface (I try this with firefox and explorer).
When I manually configure de dataservice in a .ds file in repository/dataservices/ the server appears ignore it. The same configuration file works in a standalone wso2wsas server.
The system is a linux Debian, jdk-6u11-linux-i586 and sqlserver jdbc driver installed correctly in wso2esb and wso2wsas.
I´ve searched in mailman archive http://wso2.org/mailarchive/carbon-dev/ and the wso2 website for any issue with no success...
Any idea?
Thank you.
Icaro
January 20, 2009 at 8:15 AM
Charitha said…
Hi Icaro,
In beta3 releases, Data services UI wizard was not completed. Therefore you may have encountered that configuration UI issue. We are planning to release another beta within few days so that you can try it out.

In ESB , hot deployment set to false by default in axis2.xml. Therefore, you should restart the server after adding a *.dbs file.

Let me know if you need more information on this.

Charitha
January 20, 2009 at 8:26 AM
ICARO said…
Hi Charitha, it works!!
When hot deployment is enabled and the deployer dbs extension uncoment in axis2.xml:
<deployer extension="dbs" directory="dataservices" class="org.wso2.dataservices.DBDeployer"/>
the server sucessfully expose the dataservice.
I think carbon is very powerfull ;-) good work.
Many thanks for all.
January 21, 2009 at 1:00 AM
Anonymous said…
Perfect!!You are a outstanding person!Have you ever wore chaussures puma,Here are the most popular puma CAT,Puma shoes store gives some preview of puma speed cat,and casual but no sweat puma basket.

http://gilletterazor.blog.drecom.jp
http://www.getablog.net/ColumbiaJackets
http://crystal888.edublogs.org
http://blog.qlep.com/blog.php/gillette
http://chinaclothes.net
June 16, 2009 at 9:17 PM
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