Fuse ESB Enterprisehas the following layered architecture:
Technology layer—includes technologies such as JBI, JAX-WS, JAX-RS, JMS, Spring, and JEE
Fuse ESB —a wrapper layer around the OSGi container implementation, which provides support for deploying the OSGi container as a runtime server. Runtime features provided by the Fuse ESB include hot deployment, management, and administration features.
OSGi framework —implements OSGi functionality, including managing dependencies and bundle lifecycles
Figure 12 shows the architecture of Fuse ESB.
Fuse ESB is based on Apache Karaf, a powerful, lightweight, OSGi-based runtime container for deploying and managing bundles to facilitate componentization of applications. Fuse ESB also provides native OS integration and can be integrated into the operating system as a service so that the lifecycle is bound to the operating system.
As shown in Figure 12, Fuse ESB extends the OSGi layers with:
Console—extensible Gogo console manages services, installs and manages applications and libraries, and interacts with the Fuse ESB runtime. See the Console Reference.
Logging—powerful, unified logging subsystem provides console commands to display, view and change log levels. See Configuring and Running Fuse ESB Enterprise.
Provisioning—provides multiple mechanisms for installing applications and libraries. See Deploying Features.
Deployer—supports hot deployment of OSGi bundles. When you update or delete bundles, the changes are made automatically. See Hot Deployment.
Admin—provides console commands to administer instances of Fuse ESB. See Configuring and Running Fuse ESB Enterprise.
Spring DM—simplifies building Spring applications that run in an OSGi framework.
Blueprint—is essentially a standardized version of Spring DM. It is a dependency injection framework that simplifies interaction with the OSGi container—for example, providing standard XML elements to import and export OSGi services.
 |  |  |
 |
