Service-Oriented Java Business Integration
by Binildas A ChristudasISBN-10: 1847194400
ISBN-13: 9781847194404
Pub. Date: 02/09/2008
Publisher: Packt Publishing
Overview
The book first discusses the various integration approaches available and introduces the Enterprise Service Bus, which is a new Architectural pattern that can facilitate integrating services. ESB provides different forms of mediation services including routing and transformation. Java Business Integration (JBI) provides a collaboration framework that provides standard interfaces for integration components and protocols to plug into, thus allowing the assembly of Service-Oriented Integration (SOI) frameworks following the ESB pattern. JBI is based on JSR 208, which is an extension of Java 2 Enterprise Edition (J2EE). Once JBI and ESB are introduced, we look at how we have been doing service integration without either of these using traditional J2EE. The book then slowly introduces ESB and, with the help of code, showcases how easily things can be done using JBI.
Product Details
- ISBN-13:
- 9781847194404
- Publisher:
- Packt Publishing
- Publication date:
- 02/09/2008
- Edition description:
- New Edition
- Pages:
- 436
- Product dimensions:
- 7.50(w) x 9.25(h) x 0.89(d)
Customer Reviews
Average Review:
Most Helpful Customer Reviews
 |
Read the introductory texts on Service Oriented Architecture and Web Services Description Language? Perhaps you've noticed that those sometimes frustratingly refer to more elaborate business processes that can be built atop them. How to do this? Now SOA and WSDL are strictly independent of an implementing programming language. But just suppose that you're willing to pick Java. One result is that you can turn to this book. It shows recent, state of the art, Java packages and standards, that use SOA and WSDL. Java Business Integration is still fairly new and the text gives its basics. The applications are manifold. One major case is to extend or incorporate EJBs across a set of WSDL machines. If you recall, EJBs predate WSDL by several years. And most books on EJB talk about using it within a system of computers run by the same company. The blending of existing EJBs with a WSDL setup is otherwise awkward, without JBI. You might even consider JBI as a successor to EJB, in the Web Services environment. JBI proponents would argue it's much more than that. But in terms of explaining JBI, especially to people who've invested time in coding EJBs, it's a useful concept. The book also talks about existing ways to learn and build JBI components. Foremost amongst these is the use of the Service Mix container. It holds JBI components. That is its task. Just like EJBs need an EJB container. But Service Mix is also a JBI component in its own right. For Java programmers, the analogy is to something like a JPanel that is a container for Swing widgets, but which is also a widget. Hence, Service Mix has a nice modular design that makes it interoperable with other JBI containers that might be developed.
|