Average Reviews:
(More 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.
Click Here to see more reviews about: Service Oriented Java Business Integration: Enterprise Service Bus integration solutions for Java developers
Product Description:
In Detail
The goal of Java Business Integration (JBI) is to allow components and services to be integrated in a vendor-independent way, allowing users and vendors to plug and play.
Java Business Integration (JBI) is a specification aiming to define a Service Provider Interface for integration containers so that integration components written for these containers are portable across containers and also integrate with other components or services using standard protocols and formats. JBI is based on JSR 208, which is an extension of Java 2 Enterprise Edition (J2EE).
This book first discusses the various integration approaches available and introduces the Enterprise Service Bus (ESB), a new architectural pattern that facilitates integrating services. ESB provides 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. 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.
What you will learn from this book?
Assembling services and porting them across containers using JBI
Exposing EJB as a WSDL-compliant service across firewalls
Binding remote services to ESB to be consumed internally
Exposing local components in ESB like POJO as externally accessible WSDL-compliant services
Providing a web service gateway for external consumers
Accessing web services over a reliable transport channel like JMS
Implementing web service versioning using ESB
Implementing service aggregation at ESB
Transactions, Security, Clustering, and JMX in ESB
Approach
The book covers all concepts with examples that can be built, deployed, and run by readers using the Apache Ant tool in Apache ServiceMix, which is an open-source Enterprise Service Bus that combines the functionality of a Service Oriented Architecture (SOA) and an Event Driven Architecture (EDA).
The aim of this book is to prepare an architect or developer for building integration solutions using ESB. To that end, this book takes a practical approach, emphasizing how to get things done in ServiceMix with code. When needed, it delves into the theoretical aspects of ESB, and such discussions are supplemented with working samples. The book, thus, distils some of the knowledge that has emerged over the last decade in the realm of Java Integration.
Who this book is written for?
This book is aimed at Java developers and integration architects who want to become proficient with the Java Business Integration (JBI) standard. Readers should have some experience with Java and have developed and deployed applications in the past, but need no previous knowledge of JBI. The book can also be useful to anyone who is struggling to understand ESB and how it differs from other architectures and to understand its position in SOA.
This book primarily targets IT professionals in the field of SOA and Integration solutions--in other words, intermediate to advanced users. You are likely to find the book useful if you fall into any of the following categories:
A programmer, designer, or architect in Java who wants to learn and code in JBI or ESB.
A programmer, designer, or architect who doesn't normally code in Java can still benefit from this book, since we 'assemble integration components' using XML with little to no Java code.
An IT Manager or an Officer who knows well about SOA or SOI but want to see something in code (you can adorn your flashy presentations with some live code too).
Want to buy Service Oriented Java Business Integration: Enterprise Service Bus integration solutions for Java developers at other amazon sites? Click the corresponding icon below:
0 comments:
Post a Comment