1Z0-900 · Question #54
A Java EE application that uses an EJB container must communicate with a legacy system developed using non-Java technologies. Which two Java EE technologies can be used in the integration tier of…
A (JMS) and D (JCA) are correct because they are specifically designed for the integration tier. JCA (Java Connector Architecture) is the primary answer - it was built explicitly to connect Java EE applications to Enterprise Information Systems (EIS) and legacy platforms…
Question
A Java EE application that uses an EJB container must communicate with a legacy system developed using non-Java technologies. Which two Java EE technologies can be used in the integration tier of the application? (Choose two.)
Options
- AJMS
- BJSF
- CJPA
- DJCA
Explanation
A (JMS) and D (JCA) are correct because they are specifically designed for the integration tier.
JCA (Java Connector Architecture) is the primary answer - it was built explicitly to connect Java EE applications to Enterprise Information Systems (EIS) and legacy platforms (COBOL, SAP, mainframes, etc.) through standardized resource adapters, regardless of the underlying technology.
JMS (Java Message Service) enables asynchronous message-based communication via queues and topics, making it ideal for decoupled integration with non-Java legacy systems that can send/receive messages.
JSF is a presentation tier technology for building web UIs - it has nothing to do with back-end system integration. JPA is a persistence tier technology for ORM/database access - it talks to relational databases, not legacy external systems.
Memory tip: Think of the integration tier as the "bridge" layer. JCA = the connector (it's literally in the name - Connector Architecture), and JMS = the messenger. If a technology builds UIs (JSF) or maps database rows (JPA), it belongs on a different tier and can be eliminated immediately.
Topics
Community Discussion
No community discussion yet for this question.