Page History

...

In the middle, there's the bus. The messages on the bus are JBI Normalized Messages, which are XML-based with optional binary attachments, header values, etc. (for more detail see What is JBI?).

On the bottom are binding components Binding Components. These are JBI components (like plugins) that have the capability to convert incoming messages from some protocol (like SOAP over HTTP, REST over JMS, SNMP, some custom binary junk, etc.) into Normalized Messages, and put those messages onto the bus. Or take a Normalized Message from the bus, and send it out using some other protocol. Or both.

On the top are service engines Service Engines. These are JBI components (again, like plugins) that can do interesting things with Normalized Messages. Like perform some custom message routing, or transform the message via XSLT, or run a BPEL process, or invoke a method on an EJB and return the result as another Normalized Message.

So when you deploy an a JBI application, it will probably include things like:

• Some POJOs, Spring Beans, or other components with service logic
• Configuration files to activate certain service engines (e.g. to convert accept Normalized Messages from the bus and translate those into method calls on your beans above)
• Configuration files to activate certain binding components (e.g. to connect your services to the send or receive SOAP-over-HTTP protocol on a certain URL, converting to or from Normalized Messages on the bus)
• Any additional routing rules, perhaps using a routing service engine, if it can't be deduced (e.g. by comparing the format of a Normalized Message to the WSDL describing the services) or needs additional customization

...