Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.
Barney Beal, News DirectorBy submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.
From an API point of view, there isn't much correlation between the two. JCA and JMX are two separate standardization efforts, that will eventually lead to two different API packages. (Even though both standards use the term "connector" and "adapter" a lot, but in very different contexts).
JCA is about "connectors" for J2EE application servers, that let your J2EE applications tap into ERP systems, JMS servers, etc. in a standardized manner.
JMX is about network management, in the sense of SNMP, CMIP, Tivoli, etc. JMX specifies instrumentation design patterns (MBeans), an MBean server and a client interface that should allow any JMX administration client to work with any MBean server, and any MBean server to be used to administer any application whose objects have been instrumented as MBeans.
You will find more information about JMX on java.sun.com/products/JavaManagement/
You will find more information about JCA on java.sun.com/j2ee/connector/
This was first published in January 2002
Join the conversationComment
Share