Java Business Integration

[SoftWore]

Introduction :
Java Business Integration (JBI) is a specification developed under the Java Community Process (JCP) for an approach to implementing a 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 Services 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 2.0. The central message delivery mechanism, the normalized message router (NMR), delivers normalized messages via one of four Message Exchange Patterns (MEPs), taken from WSDL 2.0:

- In-Only: A standard one-way messaging exchange where the consumer sends a message to the provider that provides only a status response.
- Robust In-Only: This pattern is for reliable one-way message exchanges. The consumer initiates with a message to which the provider responds with status. If the response is a status, the exchange is complete, but if the response is a fault, the consumer must respond with a status.
- In-Out: A standard two-way message exchange where the consumer initiates with a message, the provider responds with a message or fault and the consumer responds with a status.
- In Optional-Out: A standard two-way message exchange where the provider's 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 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.

[SoftWore]

Java Business Integration is a standard established in the JSR 208 under the Java Community Process. JBI is based on an approach to SOA. The initial problem is the integration of data from different sources within an information system composed of disparate applications. JBI defines an architecture that allows the implementation of integration solutions based on the use of components that communicate via messages. The Enterprise Service Bus is an implementation of this standard. JBI is a specification standardizing these integrations through a set of APIs to enable any supplier, they can connect according to a JBI container to exchange messages with the rest of SI.

EndPoint :
The services offered by the components are accessible via endpoints. A service is an endpoint. The components that consume services can specify an endpoint of two ways:

Implicitly : The endpoint is selected based on the type of service provided by the components and the one desired. This method is "dynamic" allows you to find a component providing the required service if there is at least one available.

Explicitly : The endpoint is selected by its name. This method thus shows the endpoint by name in the code. If the endpoint is unavailable, but another component offers the same service, it can not be used while this is the case with an implicit specification.


Message Exchange Pattern (MEP) :
There are four different MEPs, the difference is based on the types of invocations One-way and Request-Response. They can modulate the types of communications.

In-Only (One-Way): The message is sent to the recipient. No plea is made to ensure that it has arrived or not.
Robust In-Only (One-Way): the message is sent to the recipient and a message is transmitted back to the sender in case of error.
In-Out (Request-Response): A message requiring a reply is sent to the recipient.
In Optional-Out (Request-Response): A message is sent to the recipient and can sometimes require a response.


BI implementations :
The following are open-source software JBI based ESB implementations available:

- Open ESB
- Apache ServiceMix
- FUSE ESB (enterprise ServiceMix)
- Bostech ChainBuilder ESB
- 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 compliant issue.
- JBossESB
- OW2 PEtALS

Open-source JBI implementations certified by the TCK are Sun/Open ESB and OW2/PEtALS. In addition, the Project GlassFish open-source Java EE application server comes with the JBI runtime from the Open ESB project. Java EE SDK also includes the JBI runtime and a BPEL orchestration engine. Oracle claims its Fusion Middleware comes with JBI implementation. TIBCO ActiveMatrix Service Grid is a service virtualization product that provides a service container framework, based on the JSR 208 and SCA specifications, allowing service containers (Java, Java EE, .net, BPEL) to be added as needed, as composite applications on a common foundation.