This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi! Java Connector Architecture provides you a common API in Java (thus exploiting its obvious advantages), so that you can integrate the existing EIS (Enterprise Information Systems) with your App server seamlessly. Through what is called as Resource Adapters, the existing multiple EISs can be integrated to a given AppServer. For this, the App Server need to have extended/adopted the J2EE standards. Through this JCA, you can integrate even legacy systems. The existing EAI tools have got their own proprietary connection and integration protocol and mechanisms. There is no standard. JCA attempts to bring them under one roof - J2EE. These Resource Adapters execute/follow a certain protocol what would be called as System Contract between itself and the Appserver. This include Connection, Transaction and Security Management. For more information this link would be quite useful. http://java.sun.com/j2ee/connector/
You have asked a great question.. where does JCA fit into the traditional EAI picture. Well, JCA extends the application servers capability to interface with legacy and other non-J2EE applications and application environments. JCA also establishes standards that are uniform from the J2EE application servers perspective when interfacing with different legacy applications. However EAI is more then just connectivity or interfaces. It is about transformation, filtering, and routing of information as well. Hence in my perspective EAI tools enable you to manage the end-to-end integration more easily (hopefully) and JCA enables you to implement some of the interfaces and connectivity from the application server perspective. If you want to maximize the ROI from you intergration projects then you need to find ways to integrate EAI tools with J2EE application servers and JCA resource adapters. That is one of the objectives of defining a CCI based API for all resource adapters. Hope this helps. Atul
Atul Apte<br />President and CEO <a href="http://www.iconexio.com/" target="_blank" rel="nofollow">iConexio Technologies Inc</a>.<br />Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0672323109/ref=ase_electricporkchop" target="_blank" rel="nofollow">Java Connector Architecture: Building Enterprise Adaptors</a>
Joined: Nov 20, 2001
Hello Atul ! What do You use as host-emulator when developing with a JCA How do you use WSAD(from IBM) when developing with a JCA
Joined: Feb 19, 2002
Hi Tom, One way to use host emulation or screen scrapping tools or even terminal emulation protocols is to develop a CCI that will support screen interactions. So if you have an host emulator that has a well defined protocol you could extract a lot of meta-data as well as screen data before invoking the CCI interface of the JCA adapter. I would recommend that you evaluate stronger integrate frameworks that will enable you to link the host emulator to the JCA adapter (CCI). Remember you may have to do this in a bi-directional way (from host emulator to JCA/CCI and JCA to host emulator). If you want, I can send you a CD with a framework that we built which you may find interesting. Use it to do your research and let me know if you think my thinking is appropriate for your integration scenario. Atul