WSO2 Carbon [ Documentation Index ]
WSO2 Carbon is the award-winning base platform for WSO2's enterprise-grade middleware stack. It provides the core capabilities for security, clustering, logging, statistics, and management, and through a technology called OSGi, higher level capabilities can be readily added as components to this core. The WSO2 Carbon core platform hosts a rich set of middleware components encompassing capabilities such as service hosting and management, message routing and transformation, governance and identity management, business process management and business activity monitoring, and more. The point-and-click WSO2 Carbon Component Manager makes it a snap to select the perfect set of components to address your unique requirements.
WSO2 Carbon is based on Java OSGi technology which allows components to be dynamically installed, started, stopped, updated, and uninstalled, as well as eliminating component version conflicts. In Carbon, this capability translates into a solid core of common middleware components useful across any enterprise project, plus the ability to add components for specific features needed to solve a specific enterprise scenario.
The core set of components in WSO2 Carbon provides WSO2 middleware products with a consistent set of enterprise-class management, security, clustering, logging, statistics, tracing, throttling, caching, and other capabilities as well as a management UI framework. Central to these components is WSO2’s solid and high performance SOA and Web Services engine. Add-in components encapsulate major types of functionality.
A unified graphical management console can deploy, manage, and view services, processes, process instances, and statistics across the whole platform, comprising of different products. As each runtime component is added, associated management components are added to the UI. With a clean front-end/back-end separation between the UI and the runtime, all capabilities can be controlled through a remote WSO2 Carbon UI, or through a clean Web Services interface.
We use Carbon as the core of our middleware products, which are simply common “constellations” of components reflecting familiar middleware product categories. Most users will start with one of these categories, but rest easy in the assurance that components can be added to encompass requirements.