Achieve EIP- Enterprise Integration Patterns with WSO2 ESB

When enterprises seek for an integration solution, one basic aspect they always look for is, EIP. 

Gregor Hohpe, the ex-Google Architect has written a book on the widely used integration patterns.

WSO2 ESB, which is a world renown message mediation, routing and integration engine, has compiled a guide on EIP with WSO2 ESB.

This guide explains how WSO2 ESB can be configured to operate in each pattern with sample configurations. This contains:

• Introduction to the pattern
• Example business scenario
• Sample configuration to achieve the above use case
• Explanation on how each configuration operates

Visit, read the comprehensive guide and get your enterprise going with the EIP!!! 

WSO2 ESB becomes Fastest ESB again.. ESB Performance Round 7.5

WSO2 has done another round of performance test with the WSO2 ESB latest release, WSO2 ESB 4.8.1

The performance test results is being published in the WSO2 Library article: ESB Performance Round 7.5

The study shows how the latest WSO2 ESB outperforms a number of other open source ESBs. A summary of the observation is below:

The above figure clearly shows how high performant WSO2 ESB is, over the other vendors.

Want to experience a speedy and smooth integration in your enterprise??
Visit WSO2 ESB page and download today.
You can read more on WSO2 ESB in the latest ESB documentation.  

Advertising with WSO2 API Manager by Publishing to External API Store

 In WSO2 API Manager 1.5.0, we don't have the support of API sharing across tenants because with the current design, there is not way to replicate API metadata that should be written to the databases and registries along with the API configurations. Therefore, there is no straightforward approach to replicate a set of tenant APIs from one tenant to others.

 

But we have the Advertising feature, where we have the capability of displaying APIs published by tenant 1, in tenant 2's API store. However, tenant 2's users will not be able to subscribe to the APIs published by tenant 1.

To do this, you need to uncomment the <ExternalAPIStores> element in $APIM_HOME/repository/conf/api-manager.xml. Tenant's external API stores can be configured as follows by giving the tenant domain, tenant admin's user name and password
     <ExternalAPIStore id="Store1" type="wso2">
            <DisplayName>Store1</DisplayName>
            <Endpoint>http://localhost:9763/store?tenant=abc.com</Endpoint>
            <Username>abc@abc.com</Username>
            <Password>abc123</Password>
        </ExternalAPIStore>

Imagine you logged into the API Publisher as the tenant xyz.com. Then in the UI, there will be a tab available saying "External API Store". There, you will be able to see all the External tenant details you have configured earlier via the api-manager.xml. Now tenant xyz.com can publish its API, so that tenant abc.com too can see it.
Now if you login to tenant abc.com's API store, you will see the API advertised or published by tenant xyz.com. (But still tenant abc.com will not be able to subscribe to it using abc.com's credentials. )

Await for the next WSO2 API Manager release, which will allow you to subscribe to the Advertised API regardless of the tenant. 

Experience What is New in Mulit Tenanted WSO2 App Factory

App Factory is a multi-tenanted Enterprise platform that enables multiple project teams to collaboratively create, run and manage enterprise applications.

This is a one stop shop, which helps you to manage your agile application development, testing and releasing process by providing all the necessary tools and options. This includes
 - Continous Build system (Jenkins build farm)
 - Source control system (Git repo)
 - User management system (LDAP)
 - Issue tracking system (WSO2 Issue Tracker)
 - Application hosting environment (WSO2 AS)
 - API management environment (WSO2 API Manager)
 - Databases and datasource management environment (MySQL)

The inceptional design of AF (App Factory) was such that, an application was considered as a tenant. There was no organization concept attached in the old AF story.

But now the story has been matched with the real organizational behavior in an industry. In the current implementation, we have considered this organizational concept into picture. Now, an ORGANIZATION IS A TENANT.

You can register an Organization in App Factory and you will be getting a tenant space for your organization. In their you can have multiple applications belonging to your organization. (Earlier you are getting a tenant space each time you create an application. Now tenant space is given at the creation of organization)

Few architectural changes in essence

	New Architecture	Old Architecture
Cartridge subscription happens at	Tenant creation	Application creation
Jenkins allocation	For each tenant, jenkins_home and maven_home is set. Jenkins.war is copied to all tenants Jenkins.war has a context.xml that contains tenant specific domain info	Jenkins_home and maven_home is shared among applications Single Jenkins.war for all the apps
Git repo creation	No space is created at tenant creation. At application creation, a repo is created with the tenant name appended to the repo url as $git_basedir/abc.com/app1.git	At application creation. Created repo is $git_basedir/app1.git
Issue tracker	Any user in an organization can see all the issues of all apps in that organization.	App level isolation on the issues.
User Management	Roles (Dev, QA, DevOps, AppOwner) are for the organization level. Not for the application level Multiple app owners per app Developers can’t create apps	Roles for the users are in application level Single app owner per app Developers can create apps

We have put up all these latest changes into a preview hosting, so you can get a glimpse of it.
To experience all these latest changes visit
https://cloudpreview.wso2.com/ and register your tenant now and start playing around with it.

Hope you will enjoy your new AF experience.

WSO2 CARAMEL - Caramelize your AS environment

Have you ever tried writing the Front End of your application in Jaggery?

Jaggery is a framework for writing web apps and HTTP web services which you can implement front end and server side logic in pure java script.  You can get the latest taste of jaggery in here.




Do you know Caramel? Caramel is a framework built for Jaggery while enforcing a standard for developing web applications using Jaggery.

Latest WSO2 UES server is enriched with Caramel framework. Do you want to make your service hosting environment Caramelize? You can follow the steps below:

1. Download a latest AS 5.2.0 SNAPSHOT from here.(You need the latest AS because, you need latest jaggery features)
2. Put the caramel, handlebars and markdown modules into your AS_HOME/modules that reside inside caramel feature after building the caramel source.
3. Test your environment by deploying the sample

Congratulations!
If you are able to view the UI of the sample with nice icons, without any errors, then you have successfully installed caramel features on your AS environment.

Now you are ready to taste the jaggery with caramel.

Create Artifacts for WSO2 App Factory using WSO2 Developer Studio

After a couple of iterations, now the  WSO2 App Factory is released. You can experience the live version of WSO2 App Factory from here.
The Developer Studio too is compatible with creating artifacts and deploying them into App Factory.

The blog below shows how to work on App Factory seamlessly with Developer Studio.

1. Download and install Eclipse Juno distribution - eclipse-jee-juno-SR2-linux-gtk-x86_64.tar.gz
2. Download latest Dev Studio distribution from http://wso2.com/more-downloads/developer-studio/
3. Start Eclipse and install the above Dev Studio distribution. This contains the latest App Factory tooling support as well.
4. Go to Windows --> Open Perspective --> App Factory

5. Once click on App Factory, this will prompt a window to enter the Host, Username and Password to connect to App Factory.

6. Once provided the above, it opens up the App Factory views as below.

7. In the Application List view, go to an app, Select an app --> version --> checkout --> Add to workspace

The particular App version will be appeared in the Project Explorer.

8. Right click on app in project explorer --> Team --> Share Project --> in the wizard, select Git

Select the project and click Finish.

9. Change a file in the application. The changes will be shown as below. (with a “>”)

10. Right click changed file --> Team -->Commit.

Add a commit message --> Commit 
Right click the file --> Team --> Push to Upstream

I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond

I was continuously getting this error when trying to try out this code.

May 6, 2013 5:53:51 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond

May 6, 2013 5:53:51 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: Retrying request

May 6, 2013 5:54:53 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond

May 6, 2013 5:54:53 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: Retrying request

May 6, 2013 5:55:54 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond

May 6, 2013 5:55:54 PM org.apache.http.impl.client.DefaultRequestDirector execute

INFO: Retrying request

Exception in thread "main" org.apache.http.NoHttpResponseException: The target server failed to respond

at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101)

at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)

at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)

at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:227)

at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:229)

at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)

at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)

at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)

at QuickStart.main(QuickStart.java:107)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115)

Finally after wasting about 5-6 hours of my time, :( found that this was due to an old HTTPClient jar. I had earlier used the version 4.0 org.apache.httpcomponents.httpclient. 

When upgraded this to 4.1, the issue got fixed. (source from a mail archive)