SCEA v5 Certified

[Borys Marcelo Borches Herrera]

I'm glad to share with you Racher guys that I'm the newst SCEA certified of the Forum. Many thanks to you all!

Hello Borys,



Thank you for contacting Sun Certification Customer Support. We are happy to assist you.



We apologize for the delay in the posting of your exam results. We have verified your exam results from the Assignment Watcher database and processed your certification as a Sun Certified Enterprise Architect for the Java Platform, EE 5 in the Sun CertManager Database at http://www.certmanager.net/sun.



Your Sun certification welcome package is being processed. Please allow up to four weeks for delivery.



There is a technical issue in Prometric’s testing system that is preventing exam scores from being transferred to our database for many candidates. Until the issue is resolved, we have verified your passing exam result and manually granted your certification. The exam results will not appear until a later date. This will cause no problems with your certified status.



Please let us know if we may be of further assistance. Thank you for choosing Sun products and services.



Sincerely,



Michele Castle

Sun Certification Customer Support
[email protected]

[Alexey Kuntsevich]

Congratulations!

[Celinio Fernandes]

well done.

[Bharath Satti]

Hello- Could you please share your part2 and part 3 preparation and experiences?

[Kiaamaa Liammes]

congrats

[Vijitha Kumara]

Congrats

[Remko Strating]

Congrats .....

[Kuppusamy Venkatasubramanian]

Hi,

Congratulations on your certification. I am preparing for the exam and planning to sit in Jan 2010. Please guide in the preparation. What are the materials you referred? I have completed first reading of HeadFirst Design Pattern & Core J2EE Patterns. Please advise about the materials you referred.

Thanks,
Kuppusamy.V.,

[Riyaz Enayath]

Hi Borys,
How much time you have spent on the assignment to complete it successfully? What are the complex portions(which diagrams,NFR,..) you feel in your assignment?
Kindly share your experience.

Regards,
MR

[prathap venkata naga yelugula]

Congratulations...

Can You share your experiences in the area of
1. integration and messaging.
2. Security.

We need material,Books details for exact content preparation.

Thanks,
Pratap.

[Puran chandel]

cong8,


please can you guide us how we prepare part one.

[Mikalai Zaikin]

Well done !!!

[Borys Marcelo Borches Herrera]

Hello Code Rachers!

I would say:

For part 1

- Read and revise the J2EE Version 5 Tutorial SCEA v5 Tutorial
- Read the book SCEA Certification without wasting your time with onborded tests as they are all superficial. SCEA CERTIFICATION BOOK
- Do at least 5 full mock exams.

Tips:

- Be sure you know all the aspects involved in Scalability, Extensiability, Modifiability, Manageability etc. At least 10 questions.
- Be sure you know all the aspect of Networking configuration, like Reverse Proxy, DMZ, Session Stick, DNS Round Robin - At least 2 or 3 questions
- Be sure you know all the aspects of an J2EE Architecture and its appliance in an starting project. Like, if my team doesn't know Java, what Java Technology am I going to use? I my team does know a little about Java, what technology does apply in this case?
- Be sure you know the different between Layer and Tier and what should each one be aware of in the context of an application.
- Be sure you know something about security threats like Denial of Services, Man in the Middle, Session Stole etc.

Be sure you understand all the items, I repeat, all the items in the SCEA Assignment Objectives list. Assignment Objectives

Don't be innocent to go to the exam without knowing each aspect in the list!!!

For Step 2 - Project:

The project you are required to continue can vary a lot. But be sure you make the following:

1 - Read the entire project description at once.
2 - Make sure you understand how to submit you project. For example, the name of the file should be scea-YOURPROMETRICID.jar
be sure you create the .jar using the jar command, like in jar -c scea-YOURPROMETRICID.jar -C yourDirectoryWhereToPullFiles/
3 - Make sure you have an index.html pointing to the following links:

Deployment Diagram
Component Diagram
Class Diagram
Foo Use Case - Sequence Diagram
Foo2 Use Case - Sequence Diagram
Foo3 Use Case - Sequence Diagram
Foo4 Case - Sequence Diagram
Risk List
Assumptions

4 - Make sure that each file, including the index.html, has a title in the <title></title> tag and in the body of the page showing:

The Name/Purpose of the page - YOURPROMETRICID


5 - Create first the Deployment Diagram. Make sure you include your servers as Devices and inside them each Execution Environment explicity marked. Demonstrate cluster with a note pointing to both Devices (Web Server and Business Server) An Ntier application remember?! Mark each connection to your application with the required security level, like in an http request, it should be marked as HTTP over SSL (128 bits at minimun). Connections between the Web Server and the Application Server should be marked as IIOP over TLS if you are using EJB in the Business Layer. External Systems that accepts HTTP transactions should be marked as HTTP over SSL and JMS application should use encrypted messages.

6 - After the Deployment Diagram, do the Component Diagram with all the components you are going to use in your app. Include JSP, XHTML, JSPX files, Actions, Servlets or Managed Beans (JSF Backing BEans). Create using J2EE design Patterns and should be enough. Like Helpers, Business Delegates + Service Locator, Session Facase, Business Objects, ApplicationServices, DAOs etc. Be sure you call external Systems using an ApplicationService layer.

For more information see: J2EE Core Patterns

7 - Then create the class diagram. Be organized and separate the Class diagram per flow, like: Managed BeanA call Helper A, Call Business Delegate that uses Service Locator, that calls Remote Session Facade, that Calls Business Object A that Calls ApplicationServiceA etc.

8 - Be sure to think carefully in the Risk list and some alternatives because the risk list is basicly the Part 3 of the exam. the SCEA Essay.

9 - Make a list of assumptions.

10 - Review your design all over again. Think carefully and make sure to not cover all the aspects that was not asked you to do! Don't fail because the excessive design.


For the Part 3:

The part 3 is almost about What Design Pattern you used in your design that helped you with the "...itys" items (Manageability, Scalability, Security....).
Be sure you have the Risk List in mind with a list of alternatives for the threats.


Please let me know if you have questions!

Borys Marcelo

[Rahul Mishra]

Could you please tell me..where did you get five full mock exams for the latest version of the exam?

I know of whizlabs and ePractice..but as i have read..in other threads..none of these come close to the real complexity of the exam..

any pointers in this regards are appreciated.

thanks

[Borys Marcelo Borches Herrera]

Hi,

unfortunately,

having SCEA a big complexity and visibility certification, I would recommend you to buy mock exams as it scratch what a real exam is. I personally recommend the whizlabs / ePractice as you can do a lot of trainning.


Regards,

Borys Marcelo

[srees Nivas]

Hi Borys Marcelo / ranchers,

Thank you for your valuable suggestions.

I'm working on part-II, extension to your point # 7, I've a question for you / ranchers. I really appreicate if you share some ideas.

Here is the overall path that I'm thinking of:

JSP Page --> Faces Servlet --> Managed Beans --> Business Delegate --> ??? --> Stateless Session Bean --> Entity

Here are my thoughts:

In order to use EJBs/Entities I have two choices, i) Service locator/JNDI code , ii) @EJB/@PersistenceContext annotations

If I want to make use of Business Delegate I cannot use annotations as Business Delegate is not a managed object and must go with service locator.

If I eliminate Business Delegate and use annotations in Managed Beans, then I'm giving access to business objects directly to web layer, which is not good.

What is the best approach to access business objects?

Another question is, how to decide the number of business delegaters,
1 per each Session Bean or 1 per each category like session bean, web services etc.


Thanks in advance,
Sri.

[Borys Marcelo Borches Herrera]

I would say, stay with Business Delegate + Service Locator as you should never let the view module "see" the underlying process of the business tier and should not have direct access to it without passing through a intermediate layer. One of the requirements are modifiability etc. So, if you change it to use a Fast Lane Reader, you will not be able habing your Managed Beans annotated.

Remember, the Architecture Design is not Micro Design, in ways the Architecture Design should not know idiosyncrasies of the implementation.

Regards,

Borys Marcelo

[srees Nivas]

Hi Borys Marcelo,

Thank you for your instant reply. Your thoughts are really helpful.

Best Regards,
Sri.

[Sharma Ritu]

Congratulations!

Java Certification Exam Mock Tests

SCJA  SCJP 5.0  SCJP 6.0  SCJP 6.0 (Online Training)  SCJP 6.0 Instructor Led Training)   SCWCD 5   SCBCD 5.0  SCEA 5

[Ali Kianzadeh]

srees Nivas wrote:Hi Borys Marcelo / ranchers,


JSP Page --> Faces Servlet --> Managed Beans --> Business Delegate --> ??? --> Stateless Session Bean --> Entity

So you are agree to eliminate DAO layer since we are using JPA and EJB3?

[srees Nivas]

Ali Kianzadeh wrote:

srees Nivas wrote:Hi Borys Marcelo / ranchers,


JSP Page --> Faces Servlet --> Managed Beans --> Business Delegate --> ??? --> Stateless Session Bean --> Entity

So you are agree to eliminate DAO layer since we are using JPA and EJB3?

Yes I agree. If we have DAO again then we are introducing another layer. Do you see any problem here? I mean in eliminating DAO.

Thanks,
Sri.

[Samir Kureshi]

Congratzzz...

Can you suggest books for JSF? What are % of questions from JSF?

Thanks,
Samir

[Sabarish Varma]

[Erkin Kanlioglu]

First of all, congratulations.....

and the rest...

Hi

As I think it is good to discuss everything, I would like to share my ideas.

There are couple of points (that I think) contradicts with reality as we are developing the application in the assignment from scratch and I think it is important to think about rapid development, initial simple requirements.

1-) Separation of web tier from application tier is inevitable but it doesn't have to reflect on deployment.

In reality, we deploy web tier and application tier on the same jvm instance and we try to use local executions/calls instead of remote executions. So annotations are there to use and for fast development.
(Clustering between jvm instances which serve web+application)

If we ignore from the beginning these realities, so what is the point investing on these new ideas?

Note: Yes, Ideal solution could be
a) to have different jvm instances for web and application tiers
b) to use remote call between them
c) ssing different physical nodes (even more ideal) and arranging DMZ.
d) then writing Business Delegate, Service Locator

My suggestion would be...
JSP Page --> FacesServlet --> Managed Beans(Facade) --> Stateless Session Beans --> ??? --> Entity

2) I put question marks before Entity as I believe that it would be good to use some abstraction with generics --> Yes genericDAO )
Even though JPA is domain store implementation and easy to use, it is good to have a generic DAO for all basic operation and more specific DAO implementation for getting closer to domain.
For DDD friends, from my perspective

Repository implementations sounds/smells like DAO.
Functional approach is better than object oriented approach to follow to get some information from domain.

Note: I agree that DAO should NOT be accessed/injected as SLSB. Factory which takes EntityManager as a parameter is better solution if you are not using Spring.

3) TO (Transfer Object)
As far as I can see, most of us discarded using TO as entities are pojo and detached entity can be used in the view tier.
still not sure it is right approach to take as every change on entity might mean change on view as well... Keeping derivative fields on the entity or
putting some even very simple logic on the view to derive a field doesnt sound good.
Duke's Bank Example on JEE is still using TO pattern.
Note: I didnt like to see that Sun's reference implementation is using SFSB heavily even though it can ben solved with SLSB.


please let me know your thoughts ....

[Kazimierz Trzonek]

1)Why using slsb as dao is bad? We have already done it and it was quite handful.

2) Are business delegate + service locator still valid when using ejb 3.0?

[Erkin Kanlioglu]

Kazimierz Trzonek wrote:
1)Why using slsb as dao is bad? We have already done it and it was quite handful.

2) Are business delegate + service locator still valid when using ejb 3.0?

a1-) if you read following link and the discussions, I think it will be crystal clear.
JPA Discussion

a2) Yes, if your deployment strategy to use different jvm instances for presentation tier and business tier. As you need to access remote business objects and current annotations doesnt support injection of remote business/resource objects, you have to implement business delegate and service locator.

Please check following link EJB Tech Tips

Regards

[Kazimierz Trzonek]

This article states:

Use the @EJB annotation to inject either a session bean's or entity bean's interfaces, which can be either local or remote. You can use the @EJB annotation to look up both EJB 3.0 and EJB 2.1 bean references.

- so can't I inject a remote interface from other vm? I cant find it written there.

[Erkin Kanlioglu]

Kazimierz Trzonek wrote:This article states:

Use the @EJB annotation to inject either a session bean's or entity bean's interfaces, which can be either local or remote. You can use the @EJB annotation to look up both EJB 3.0 and EJB 2.1 bean references.

- so can't I inject a remote interface from other vm? I cant find it written there.

Hi Kazimierz

Sorry, I should have been more clear about this.

Use the @EJB annotation to inject either a session bean's or entity bean's interfaces, which can be either local or remote.

I think this sentence means that you can add/use your ejb with remote or local interface.

It is better to check EJB annotation spec. In EJB annotation spec, I couldn't find any parameter for JNDI Provider url setting.
Your application server might provide a file(to be used while annotation resolution) which maps
"EJB name or EJB beanName --> JNDI Provider URL"
but this will be application server specific or you can use mappedName(Global JNDI name of EJB) but it is again application server specific.

My answer to your question will be No, you can't.

Note: I'm not %100 sure but deploying 2 applications on the same node (bind on same ip address) and using default port for jndi provider might give you an access to ejbs on different vm.

Thanks
Erkin

[ForLuck Yang]

Hi Guys,

Congratulations and thank you for your suggestions!

Actually, I'm working on this too. And wish me good luck!