Some companies have deployed Web services and Web applications for years; others are just beginning to branch out and do so. However, no matter what stage enterprises are at, they need to be properly equipped to manage high volumes of Web application programming interface (API) requests. In their joint presentation at WSO2Con 2011, Paul and Hiranya discussed the real-world challenges of handling high-volume Web traffic, best practices for Web API management, and how to leverage the WSO2 Enterprise Service Bus (ESB). Here are highlights from their talk. About the Speakers Hiranya first joined WSO2 in October 2007 as an intern where he worked on WSO2’s automated interoperability test framework and implementing finance messaging capability for WSO2 Enterprise Service Bus. Now an Associate Technical Lead, he currently works on WSO2 Enterprise Service Bus and WSO2 Carbon projects. He is an Apache committer for Apache SynapseESB and Apache Xerces2/J. Hiranya is the author of the Financial Information Exchange (FIX) transport for Apache SynapseESB and WSO2 ESB and is a regular contributor to open source projects like Apache Derby and Apache Web Services.

Businesses rely on their enterprise applications to share data, configurations, and other organizational resources. However, connecting these applications—with their diverse programming languages, platforms, data formats and protocols—can be an architect's worst nightmare. In his presentation at WSO2Con 2011, Hiranya discussed how an enterprise service bus (ESB) can be used as a backbone for service-oriented architecture (SOA) integration and provide a simple and uniform platform for connecting heterogeneous applications. Here are highlights from his talk. About the Speaker Hiranya first joined WSO2 in October 2007 as an intern where he worked on WSO2’s automated interoperability test framework and implementing finance messaging capability for WSO2 Enterprise Service Bus. Now an Associate Technical Lead, he currently works on WSO2 Enterprise Service Bus and WSO2 Carbon projects. He is an Apache committer for Apache SynapseESB and Apache Xerces2/J. Hiranya is the author of the Financial Information Exchange (FIX) transport for Apache SynapseESB and WSO2 ESB and is a regular contributor to open source projects like Apache Derby and Apache Web Services.

This article describes how failover can be achieved when using Java Messaging Service (JMS) with WSO2 ESB. It describes the problem that need to solve and then walk through complete working configurations. The material assumes some understanding of WSO2 ESB.

This article describes a usecase which demonstrates how the WSO2 ESB can be used with BlackBerry client. You can also do many things inside this proxy service like calling actual Web services, mediate message, logging, message reformat etc.

This article is targeting enterprise architects who are building SOA-based solutions. It describes how generic patterns are mapped to WSO2 products for implementation.

The VFS transport implementation is based on Apache Commons VFS implementation. VFS (Virtual File System) transport implementation is a module which belongs to the Apache Synapse project. This article will demonstrate a SFTP file transfer sample for WSO2 ESB. The sample proxy configuration copies a file from one SFTP location to another SFTP location. This tutorial will discuss how to troubleshoot when running this sample.

Here we are going to learn how to subscribe to an AMQP Queue by using WS-Eventing. We are going to use Apache Qpid Java broker as the AMQP implementation and WSO2 Eventing implementation ships with WSO2 ESB will be the WS-Eventing implementation.

This is a guide on how to setup a cluster for any WSO2 carbon based product using Governance Registry as the central repository. The replication among the cluster nodes will be handled using a shared Governance Registry. We suggest users to read the article about Registry separation concepts before following the steps below.

Stored procedure is a powerful mechanism to interact with a relational database. It allows business logic to be embedded inside database as an API. Stored procedure is stored in a pre-compiled format within the database itself resulting in faster execution speed.

WSO2 Carbon Registry Kernel contains three main partitions of the Registry space. Those are namely Local Data Repository, Configuration Registry and Governance Registry. These three partitions are available on all the products based on WSO2 Carbon Platform, which allows to share resources and configuration replication.