The true face of ESB

Jbi component is like a Portlet, every server product in an enterprise, regardless of its interface is WebService, XML-RPC, FTP, HTTP, e-mail can be customized for them to write a jbi component, jbi is used to receive messages sent from your server or send messages to your server.

Let's take a look at several jbi components in ServiceMix.

JMS component: send and receive JMS messages.

HTTP: supports one HTTP client (remote HTTP servers can be called) and one HTTP server (to set jbi

Components is rendered as HTTP)

File: stores local files for messages. You can also monitor a group of files or directories in a local file and send them to jbi.

Jabber: Send a message to jabber or receive a message from jabber and send it to jbi through NMR.

FTP: stores messages as files on FTP. You can also monitor files or directories in FTP and send them to jbi.

Each protocol has two kinds of component: receive and send. After these components are written, the component connection, routing, and conversion are followed. Other application systems in the enterprise run as usual, if you want to communicate with another system, you can directly send your own protocol to the bus. After the bus is processed, it is sent to another system. In fact, the bus and the original system of the enterprise are independent.

There can be many bus in an enterprise, and the bus can communicate with each other.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? Postid = 481583