JBI with ServiceMix

最新推荐文章于 2016-08-23 16:54:13 发布

原创最新推荐文章于 2016-08-23 16:54:13 发布 · 881 阅读

0 ·

CC 4.0 BY-SA版权

Java 专栏收录该内容

51 篇文章

订阅专栏

本文详细介绍了JBI（Java Business Integration）规范的核心概念，包括服务引擎(SE)和绑定组件(BC)，以及它们如何通过NMR（Normalized Message Router）进行通信。文章还探讨了ServiceMix作为JBI标准的实现，它提供了如JMS、BPEL、Web服务和Camel等组件，并强调了与Spring框架的整合。最后，文中提到了另一个强大的ESB（Enterprise Service Bus）分发——Fuse ESB。

There are a couple of key concepts in the JBI specification. There are two kinds of JBI components, the service engine (SE) and binding component (BC), which provide integration logic. BCs provide communication functionality to send messages to and from the JBI container, like for example a JMS BC, a File BC and a HTTP BC. SEs provide integration functionality that can be used to build your integration solutions, such as routing, transformation and routing logic. The BCs and SEs communicate with each other via a normalized message router (NMR). With the presence of a NMR, the BCs and SEs are decoupled and communication is done with so-called normalized messages. The communication layer between the BCs en SEs and the NMR is implemented with a delivery channel (DC). The DC is a bidirectional communication pipe that provides an API contract for BCs and SEs to be able to sent and receive messages from the NMR.

ServiceMix uses a JBI standard which provides a lot of components like JMS, BPEL, Web service, and Camel. The inclusion of Camel is a strong point for ServiceMix along with the Spring Framework, which is also supported. FUSE ESB is another great distribution of Apache ServiceMix.