Java Business Integration: Difference between revisions

Revision as of 01:04, 23 January 2006

Revision as of 22:12, 25 January 2006

Line 1:

'''Java Business Integration''' ('''JBI''') is a [[Java_Community_Process|Java community process]] initiative for an approach to implementing a [[Service_oriented_architecture|service-oriented architecture]]. The JCP reference is JSR-208.

JBI is a [[Java Specification Request]] (JSR) built on Web Services that provides a pluggable architecture to a container that hosts producer and consumer components. Services connect to the container via binding components (BC) or can be hosted inside the container as part of a service engine (SE). The services model used is WSDL 2.0. The central message delivery mechanism, the normalized message router (NMR), delivers normalized messages via one of four message exchange patterns (MEPs):

# '''In-Only''': A standard one-way messaging exchange where the consumer sends a message to the provider that provides only a status response.

Line 8:

# '''In Optional-Out''': A standard two-way message exchange where the providers response is optional.

To handle functionality that deals with installation, deployment, monitoring and lifecycle concerns amongst BCs and SEs, Java Management Extensions (JMX) is used. JBI defines standardized packaging for BCs and SEs, allowing components to be portable to any JBI implementation without modification.

JBI defines standard packaging for composite applications: applications that are composed of service consumers and providers. Individual service units are deployable to components; groups of components are gathered together into a service assembly. The service assembly includes metadata for "wiring" the service units together (associating service providers and consumers), as well as wiring service units to external services. This provides a simple mechanism for performing composite application assembly using services.

Although JBI is intended for use with [[Enterprise_Service_Bus|Enterprise Service Bus]], its adoption has not been accepted by the larger [[J2EE]] vendors that have their own ESB / ESB ready products [http://www.javaworld.com/javaworld/jw-11-2004/jw-1101-iw-jbi_p.html]. There are however [[Open-source_software|open-source software]] JBI based ESB implementations available: