Page History

...

An ESB also supports requirements such as security, orchestration, and transactionality. These exist in "hard-wired" integration methods, but are not automatically available in a service-oriented architecture. One of the key requirements for the ESB is to give loosely coupled service-based integration methods a level of enterprise-class reliability and security.

Why ServiceMix

ServiceMix is an ESB that is based on the What is Java Business Integration (JBI) standard. The JBI-based design specifies a standards-based pluggable architecture with a JVM-based runtime component called the Normalized Message Router (NMR). ?

Briefly, JBI is an architecture for integration systems specifying plug-in components that interface through mediated message exchange rather than interacting directly. This decoupling increases flexibility because each component only needs to know how to interact with the JBI bus and not with n number of other components. JBI components plug into the JBI framework. There are two types of components: Service Engines (SE) and Binding Components (BC). The SEs provides business logic and transformation services. The BCs provide connectivity for applications that are external to the JBI. The mediated message exchange between components is provided by the Normalized Message Router (NMR). The NMR routes normalized messages. A normalized message consists of two parts: the message content (payload) and the message metadata. The message metadata contains information such as, security information, and can affect the processing of the message as it routes through the JBI.

Why ServiceMix

ServiceMix is an ESB that is based on the Java Business Integration (JBI) standard. The JBI-based design specifies a standards-based pluggable architecture with a JVM-based runtime component called the Normalized Message Router (NMR).