Architecture

WSO2 API Manager is a complete solution for publishing APIs, creating and managing a developer community, and for scalably routing API traffic. It leverages proven, production-ready, integration, security and governance components from the WSO2 Enterprise Service Bus, WSO2 Identity Server, and WSO2 Governance Registry. In addition, as it is also powered by the WSO2 Business Activity Monitor, the WSO2 API Manager is ready for any large scale deployments right away.

In this article I will discuss the architectural design and implementation details of tenant aware API management. While it did not support multi-tenancy in previous versions, WSO2 API Manager 1.4.0 onward will have multi-tenancy and be compatible with other WSO2 multi-tenant products.

Just another cloud platform, or something a bit different?

With so many cloud platforms out there, it can be difficult to pick one that best suits your needs. But what about the first truly open source cloud platform out there? WSO2’s Paul Fremantle explains how to get an application running, as well as explaining the architecture behind the project...

Download the free PDF version of the JAX Magazine to read Paul's article based on WSO2 Stratos.

The main objective of this article is to give the user a comprehensive understanding about the deployment of WSO2 Products in a MySQL Cluster. Also, the concepts related to MySQL Clustering are discussed in the process.

WSO2 API Manager is a complete solution for publishing APIs, creating and managing a developer community, and for scalably routing API traffic. It leverages proven, production-ready, integration, security and governance components from the WSO2 Enterprise Service Bus, WSO2 Identity Server, and WSO2 Governance Registry. In addition, as it is also powered by the WSO2 Business Activity Monitor, the WSO2 API Manager is ready for any large scale deployments right away.

In this presentation, Chris Haddad discusses cloud computing, PaaS, multi-tenancy, cloud ecosystems, cloud aware APIs from the perspective and the benefits it can provide to the business.

Watch the full video of the presentation at InfoQ

Store and forward is a common messaging pattern used in Messaging and Service Integration. In order to implement delivery reliability and asynchronous delivery with messaging, a Message Broker is used. WebSphere MQ is such a message broker from IBM Cooperation. In this article we discuss the steps on how to configure WSO2 ESB with WebSphere MQ to work remotely. Using the discussed configuration, messages can be routed to WebSphere MQ from the WSO2 ESB as well as receive them into the ESB.

For the WSO2 ESB, XPath is used for handling content-based message routing, mediation, filtering, transformation etc. Since performance is a major requirement of an ESB, having an optimized way of parsing XPath expressions is mandatory.

Store and forward messaging model brings loose coupling to exchanging messaging in a distributed computer system. With that, several concerns arise such as message delivery reliability and fault tolerance for network, hardware and software failures during message transmission. During the coordination of message delivery, to ensure that the messages are delivered without problems acknowledgements for messages are very important. Thus there is a close connection between message acknowledgements and delivery reliability. In this article we will explore message acknowledgement and delivery reliability patterns with respect to Java Message Service (JMS). The scenarios are described using WSO2 Message Broker as the intermediate broker.