Java Business Integration: Difference between revisions

Revision as of 14:44, 28 May 2014

Latest revision as of 08:04, 22 January 2024

(25 intermediate revisions by 18 users not shown)

Line 1:

{{Short description|Java specification}}

{{Redirect|JBI|the United States Air Force Information Management System|Joint Battlespace Infosphere|the Jewish Institute for the Blind|JBI International}}

'''Java Business Integration''' ('''JBI''') is a specification developed under the [[Java Community Process]] (JCP) for an approach to implementing a [[Service oriented architecture|service-oriented architecture]] (SOA). The JCP reference is JSR 208 for JBI 1.0 and JSR 312 for JBI 2.0. JSR 312 was removed from the JCP balloting process on 17 Dec, 2010 by the submitters without being accepted.

'''Java Business Integration''' ('''JBI''') is a specification developed under the [[Java Community Process]] (JCP) for an approach to implementing a [[Service oriented architecture|service-oriented architecture]] (SOA). The JCP reference is JSR 208 for JBI 1.0 and JSR 312 for JBI 2.0.

JBI is built on a [[Web Service]]s model and provides a pluggable architecture for a container that hosts service 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 [[Web Services Description Language|Web Services Description Language 2.0]]. The central message delivery mechanism, the normalized message router (NMR), delivers normalized messages via one of four [[Message Exchange Pattern]]s (MEPs), taken from WSDL 2.0:

Line 11 ⟶ 10:

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 service units 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.<ref>[https://coresumo.com/difference-between-c-vs-c-vs-python-vs-java/ Difference Between C vs C++ vs Python vs Java]</ref>

==JBI implementations==

Line 17 ⟶ 16:

* [[Open ESB]]

* [[Petals ESB]]

* [[Apache ServiceMix]]

* [[FUSE ESB]] (enterprise ServiceMix) - compliant JSR 208

* [[Mule (software)|Mule]]. Though not a JBI compliant container by itself, Mule provides interoperability with JBI containers. There is a separate Mule-JBI project that is to address this JBI compliance issue.

Line 29 ⟶ 28:

Oracle <!-- change this to a reference [http://www.oracle.com/corporate/press/2006_oct/openworldsf06-07.html?rssid=rss_ocom_pr claims] --> claims its Fusion Middleware comes with JBI implementation. {{Citation needed|date=May 2014}}

[[TIBCO]] ActiveMatrix Service Grid provides a service container framework, based on the JSR 208 and [[Service component architecture|SCA]] specifications ([[Service Component Architecture]]), allowing service containers (Java, Java EE, .net, BPEL) to be added as needed, as composite applications on a common foundation.

== Existing JBI Components ==

The [https://open-jbi-components.dev.java.net/ Open JBI Components] project on java.net is an incubator project started to foster community-based development of JBI components that conform to the Java Business Integration specification (JSR 208).

==Books==

*Binildas A. Christudas, "Service -Oriented Java Business Integration" (Packt Publishing: Feb 2008, {{ISBN |1-84719-440-0}}; {{ISBN |978-1-84719-440-4}}), http://www.packtpub.com/service-oriented-java-business-integration

==See also==

*[[Enterprise Service Bus]] solutions offered by several [[Java platform]] vendors.

*[[Service Component Architecture]] (SCA)

==References==

Line 47:

*[http://jcp.org/en/jsr/detail?id=312 JSR 312 page on the JCP site]

*[http://www.osoa.org/display/Main/Relationship+of+SCA+and+JBI Open SOA article on JBI's relationship to SCA]

*[https://download.oracle.com/otndocs/jcp/jbi-1_0-pfd2-spec-oth-JSpec/ Java Business Integration Specification.]

*[http://www.wikihost.org/w/eventdrivensoa/java_business_integration Discussion of differences between JBI and commercial product offerings.]

[[Category:Java enterprise platform|Business Integration]]