Library
Latest
Library

[Yenlo] Rollback a WSO2 Feature

When an administrator installs new features through the admin console it is not very difficult to make a mistake. For instance selecting an incorrect P2 repository and installing a feature which is not meant to be installed on the current version of the WSO2 product.

Read the full article on Yenlo website

[InfoQ] WSO2 API Manager 1.4.0 Introduces Multi-Tenancy

The latest WSO2 API Manager adds native multi-tenancy, automatic generation of API documentation, and SAML-based SSO, running both on servers or in the cloud.

There is a growing trend in the enterprise today: moving away from heavy SOA architectures to lighter and more flexible services offered through Web APIs. These APIs provide access to web services usually based on a REST architecture, transferring data encapsulated in JSON over HTTP. This trend has surpassed the enterprise borders from the beginning, the Web APIs being meant to be consumed by external customers, not just internally by an organization’s departments. The main purpose of Web APIs is to provide others access to one’s data. And this trend is growing because there is more and more data everyday and companies use data in ways not imaged before.

Read the full news article on InfoQ

Understanding How Siddhi Powers WSO2 Complex Event Processor 2.x

WSO2 Complex Event Processor (WSO2 CEP), is an enterprise grade server that integrates to various systems to collect, analyse, and notify meaningful patterns in real time. The core back end runtime engine that powers WSO2 CEP 2.x server is WSO2 Siddhi which is a very high performing Java event processing engine. This article walks through the key functionalities of Siddhi, its architecture, and some performance enhancement mechanisms that are handled in Siddhi. The article is written focusing on developers to better understand Siddhi code, and contribute to it.

[Blog Post] Future Proof by Design: Loose Coupling and Ensuring Long Term Success

Technical future proofing assumes constant change in both operational environments and technology. The impacts of change are mitigated by emphasizing versatility and adaptability in system architecture. This tenet applies equally to both hardware and software systems. By ensuring that system components are modular, and that they interact using standard interface patterns and in a loosely coupled manner, components can be modified or readily swapped for more capable variants across the entire system lifecycle. As a result, the system as a whole remains functional and useful well past the time when the original configuration has become obsolete. This article illustrates risks associated with inadequate future proofing and provides an overview of tools and techniques that promote long lasting, future proofed software systems.

Read the full blog post at Adam's blog

[Blog Post] WSO2: Missing artifacts from a deployed CAR file and ServerRoles By Thijs Volders, Yenlo

All WSO2 products (re-)use a generic engine. This engine, called Carbon, is instantiated within a certain role.

The WSO2 ESB carbon instance per default has the role “EnterpriseServiceBus”. The WSO2 Governance Registry carbon instance per default has the role “GovernanceRegistry”.

Read the full blog post here.

Flash Banner
Featured Video
More Videos
Upcoming Events
Upcoming Webinar
Managing ESB Artifacts with the WSO2 Governance Registry
Tuesday, June 18th, 2013
Upcoming Workshop
WSO2 Integration Platform Discovery
Thursday, June 27th, 2013
More Events