File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Clarifications for Architect Part II Exam Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Clarifications for Architect Part II Exam" Watch "Clarifications for Architect Part II Exam" New topic

Clarifications for Architect Part II Exam

Cengiz Kayay

Joined: Feb 16, 2006
Posts: 7
Hi List,

I have some questions and I would appreciate all the answers from guys who passed the test already.
I am preparing for Part II and my assumptions are:

- To integrate with the Frequent Flier Mileage System, I consider to wrap it as a webservice and to access the webservice JAX-RPC could be used ?
- To integrate with the credit card service, I would consider this third-party service already setup their webserver to use XML-RPC and to access it XML-RPC could be used ?
- Do I have to use EntityBeans at all? Cause, the system does not say that the architecture needs to be distributed and it is not currently a complex application. I would like to use DAO with POJO business logic objects instead. I will do the transaction management with JTA in a servlet filter (see: adventure builder architecture)
- I would use a Session EJB (EJB tier) for the swing client to access the business logic thru a business delegate object. The business logic will be in the web tier and it will be shared with the EJB tier.
- I would try to use no session state in the web tier and ejb tier to maximize the scability and failover.
- I want to use Struts framework in this MVC based architecture.(service to Worker pattern)
- In my component diagram, I will show the MVC pattern in the UI tier, Session Bean with the Business Delegate with Session Facade and Service Locator in the EJB tier, Application Service wrapping the business logic in POJO's in web tier, DAO objects for DB access in the Integration tier and POJO's that wrap access to credit card service (XML-RPC) and frequent flier system (JAX-RPC to access the web service, I assume to wrap the existing system as a web service)
- In the component diagram I will also show the modules (Registration, Customer, Payment, etc with their interfaces)
- I will also send a RUP style SAD document additionaly to show the 4+1 view (Logical view, Use case view, Deployment View, Data View, Implementation View)

Are my assumptions OK, so far.?
Anything I have missed ?

Thanks for your all comments.

I agree. Here's the link:
subject: Clarifications for Architect Part II Exam
jQuery in Action, 3rd edition