Section | Max points | Minimum score |
Component Diagram | 40 | 26 |
Class Diagram | 40 | 26 |
Deployment Diagram | 24 | 17 |
Interaction Diagrams | 16 | 0 |
Risk & Mitigation List | 16 | 0 |
Part 3 Short Answer | 24 | 17 |
Total | 160 |
Title | Author | JR Horseshoe Rating | Links |
OCM Java EE 6 Enterprise Architect Exam Guide | Paul Allen & Joseph Bambara | Amazon | |
Sun Certified Enterprise Architect for Java EE Study Guide (2nd Edition) [See CadeSheilSceaFaq] | Mark Cade, Humphrey Sheil | 7 | Amazon JR review |
Sun Certified Enterprise Architect for Java EE Study Guide (Exam 310-051) | Paul R. Allen, Joseph J. Bambara | - | Amazon |
Oracle Certified Master, Java EE Enterprise Architect Practice Guide | Amritendu De | - | Amazon |
Java Security | Scott Oaks | 8 | JR Review Amazon |
Professional Java Server Programming, J2EE 1.3 Edition | Subrahmanyam Allaramaju et.al. | 9 | JR Review Amazon |
IT Architectures and Middleware: Strategies for Building Large, Integrated Systems | Chris Britton | 10 | JR Review Amazon |
Applied Java Patterns | Stephen Stelting, Olav Maassen | 9 | JR Review Amazon |
Software Architecture: Organizational Principles and Patterns | David M. Dikel, David Kane, James R. Wilson | 9 | JR Review Amazon |
Design Patterns Explained: A New Perspective on Object-Oriented Design | Alan Shalloway, James R. Trott | 9 | JR Review Amazon |
UML Distilled | Martin Fowler, et al | 9 | JR Review Amazon |
Enterprise Java with UML | CT Arrington | Amazon | |
Design Patterns | Erich Gamma, et al | 8 | JR Review Amazon |
Java Design Patterns: A Tutorial | James W. Cooper | 7 | JR Review Amazon |
Java and UML | Paul R. Reed Jr. | 5 | JR Review Amazon |
Java Internationalization | Andy Deitsch, David Czarnecki | 9 | JR Review Amazon Sample chapter |
Java Message Service | Richard Monson-Haefel and David A. Chappell | 8 | JR Review Amazon Sample chapter |
Enterprise JavaBeans | Richard Monson Heafel | 9 | JR Review Amazon |
Mastering Enterprise JavaBeans | Ed Roman | 10 | JR Review Amazon Download |
Head First EJB: Passing the Sun Certified Business Component Developer Exam | Kathy Sierra, Bert Bates | 9 | JR Review Amazon |
Core Security Patterns: Best Practices and Strategies for J2EE™, Web Services, and Identity Management | Christopher Steel, Ramesh Nagappan, Ray Lai | Amazon |
Title | Author | JR Horseshoe Rating | Links |
Sun Certified Enterprise Architect for J2EE Technology | Mark Cade, Simon Roberts | 7 | JR Review Amazon |
Sun Certified Enterprise Architect for J2EE Study Guide (Exam 310-051) | Paul R. Allen, Joseph J. Bambara | 8 | JR Review Amazon |
Christian Nicoll wrote:I'm (unfortunately) not an expert of JCA, but I would have chosen a "SOAP webservice" approach. Well in the question was shown that one application is written in "C", but does this necessarily mean for you that this one is also a legacy system? Is every application written in C (or assembler) for you a legacy application? Not for me.
I would have chosen the SOAP webservice, because over this approach the two system's wouldn't be tightly connected, and in the future it would also be possible that other systems would be able to easily consume the service. Would JCA offer the system flexibility?
Regards,
Christian
Sergio Figueras wrote:
I'm using Whizlabs for training and there's the following question:
An application is written in "C" language. It has to receive documents like PDF from a Java EE application. What is the best technology that can be used for this? Please select one of the following technologies:
A) JMS
B) JCA (Java Connector Architecture)
C) SOAP WebService
D) JPA
I would choose between SOAP WebServices/JCA, but in the end I would choose JCA by the following characteristics:
- I would need to provide an "wrapper" implementation for webservice or JCA, so using JCA I would create conditions for connection, transaction and security, and would be more naturally using this to translate files.
- WebServices is not (by default) used for PDF mimetypes, SOAP webservices works essentially with SOAP XML protocol.
But the Whizlabs correct answer is C) SOAP WebService because SOAP provides platform interoperability and JCA,JMS and JPA are not suitable for this
Do you agree guys?
Message Consumption
Messaging products are inherently asynchronous: There is no fundamental timing dependency between the production and the consumption of a message. However, the JMS specification uses this term in a more precise sense. Messages can be consumed in either of two ways:
Synchronously: A subscriber or a receiver explicitly fetches the message from the destination by calling the receive method. The receive method can block until a message arrives or can time out if a message does not arrive within a specified time limit.
Asynchronously: A client can register a message listener with a consumer. A message listener is similar to an event listener. Whenever a message arrives at the destination, the JMS provider delivers the message by calling the listener’s onMessage method, which acts on the contents of the message.
There are two modes of communication, depending on the level of coupling between the sender and receiver:
Synchronous Asynchronous
In synchronous mode, a distributed component sends a message via the MOM message queue to another component and waits for the reply to proceed further. The synchronous communication is “tightly coupled”—that is, both the sender and receiver know each other and rely on each other. The sender is responsible for retries in case of failures. This mode is typically used for transaction processing, where the sender needs the reliable response in real time (for example, stock purchase). When multiple messages are sent, they reach the destination in the same order in which they are sent. In asynchronous mode, the distributed component sends messages via the MOM message queue to the listening component and continues its processing without waiting for the response. This communication mechanism is “loosely coupled,” where sender and receiver need not have specific knowledge about each other. Messages arrive at the destination but not necessarily in same order in which they are sent. MOM is responsible for retry in case of failure in the communication. The asynchronous communication is desirable if the sender wants to broadcast messages to multiple receivers efficiently to handle high-volume processing.