Updates
Latest Tweet
What's New?
Check out for latest innovation, a computer based training video collection
Like this Page
J2EE(TM) Connector Architecture and Enterprise Application Integration Review by Ganeshji Marwaha
JCA is here to stay - Stay Connected
J2EE Connector Architecture (controversially abbreviated as JCA) is arguably one among the best JSRs created at JCP. This JSR defines a standard plug ability architecture using which various Enterprise Information Systems (EIS) can be integrated into a J2EE server. An EIS can be thought of as any resource that is outside a J2EE app, and that begs to be integrated into the larger architecture of the platform. Example: Legacy apps, SAP, mainframe apps etc...
There could be various ways to achieve this feat. Some are given below...
1. Use an EAI product; (think TIBCO) - Do u really want to enter the proprietary world of integration; my best wishes...
2. Use Messaging Servers; (think MQ Series) - Again proprietary. Ok, JMS might make it portable, but that again is just JCA in disguise. If you are wondering what I mean by that, trust me this book will clarify it.
3. Use ad-hoc integration - Use RMI, JNI, CORBA, FTP or other techniques to use the EIS API directly from your application
There are the 4th and 5th techniques too, 4th being the second best and 5th being the best up until today.
4. Use JCA
5. Use Web Services
Web Services, is an open standard that can be used by any platform for integrating other systems. But, it is still in its early phases, though it is going to be the best way to integrate enterprises going forward.
Today, JCA remains to be the most elegant architecture to solve this problem, very similar to web services, difference being that JCA is very mature, easy but only for the java platform.
During the time, I am writing this review, JCA is in version 1.5. But, when this book was written JCA was in 1.0 final and version 1.5 was proposed. So, this book is by-and-large about 1.0 version of JCA, but the author also adds some salient features that are planned for 1.5 (he calls it version 2.0, for some odd reason).
The 1.5 version of JCA has a lot of additions and improvement over 1.0 version. So, either this book needs an update for version 1.5, or you are better off typing in "112" in the "jcp.org" site and downloading the latest 1.5 specification. Trust me, this specification is well written, so you might not find it a daunting task to read it, at least not as daunting as the SOAP Note from W3C.
Or, if you are like me, read this book first, then get into the 1.5 version immediately after the basics are clear. It will be far easier to read the spec then. Choice is yours. But, do yourself a favor and keep yourself updated on JCA. It is arguably the most elegant and mature way to solve integration problems at present in the J2EE platform.