Kit Davies
Posts: 9
Nickname: kitd
Registered: Sep, 2003
|
|
Re: Service-Oriented Java Business Integration
|
Posted: Sep 22, 2005 6:14 AM
|
|
I think most people agree that to integrate the widest number of enterprise services as easily as possible, what is needed is a hub or bus that allows the services to be plugged in the back and protocol transceivers (aka binding components) to be stuck on the front.
Services may be web services, EJBs, POJOs, BPM engines, message translators (ie XSLT), rules engines, etc. The services offered can be described using WSDL.
Binding components may handle SOAP, JMS, HTTP, SMTP/POP3, + adapters for any specialised protocol.
Such an architecture decouples client from service. But whereas proprietary products offer similar functionality, they may lack a key component, eg rules engine, or may not offer best-of-breed (the BPM engine may run like a dog).
It would be nice if messages could be consumed, transformed, enriched and serviced by pluggable bespoke or best-of-breed components, and what is needed for that is a standard API for all the binding components and service engines to be bolted onto an underlying messaging infrastructure. JBI does that. It basically allows you to build your own service bus.
HTH
|
|
Previous Topic
