Developed under the Java Community Process (JPC) as
an approach to the implementation of SOA, the Java Business Integration (JBI)
is identified by JCP reference JSR 208. This is a web service model, which uses
the Web Services Description Language 2.0 to deliver normalized messages
through any one of the four MEPs or message exchange patterns.
The first pattern ‘in only’ is one in which the
consumer sends a message with a status only response being sent by the
provider. Another exchange pattern is Robust in only, which also is a one-way
message exchange, where the provider sends a response to the consumer’s message
by either a status report or a fault report. In case it is a fault, the
consumer is required to respond with a status response. Then there is the
in-out pattern, wherein the consumer initiates with a message, with the
provider sending in a status response or a fault, and the consumer responding
back with a status response as standard practice. The final is the ‘optional
in-out’ pattern, which is a standard pattern of two-way message exchange, with
the provider’s response being optional.
All functions of installation, monitoring,
deployment and other concerns are handled through JMX (Java Management
Extensions). In Java Business Integration, no modification to components is
required, allowing them to be portable to any JBI implementation ‘as is’.
It should also be known that contrary
to what is generally assumed, it is possible to build service-oriented applications
without using web services by utilizing traditional technologies like Java RMI.