Examining Enterprise Java Beans (EJB) Applications
Objectives
Upon completion of this module, you should be able to:
- Introduce the Java Platform Enterprise Edition (Java EE)
- Examine the Java EE application architecture
- Examine the EJB Application creation process
- Compare the Java EE application development with traditional enterprise application development
Introducing the Java Platform Enterprise Edition(Java EE)–Overview
- A set of specifications
- Java EE 5 Software Development Kit (Java EE 5 SDK)
- Commercial and open source Java EE application servers and tools
- Java EE components and applications
Introducing the Java Platform Enterprise Edition(Java EE)–Specifications
- Web services technologies
- Web application technologies
- Enterprise application technologies
- Management and security technologies
Introducing the Java Platform Enterprise Edition(Java EE)– SDK
- Sun Java System Application Server Platform Edition9 (application server 9 PE)
- Java EE 5 Samples
- Java 2 Platform, Standard Edition 5.0 (Java SE 5)
- Java BluePrints
- Application Programmer Interface (API) documentation (Java docs)
Examining the Java EE Application Architecture
- Generic Component-Container Architecture
- Complete EJB Application Architecture
Examining Java EE Container Services –
Deployment and Inherent Services
Deployment based services
- Persistence
- Transaction
- Security
- Injection
- Life-cycle
- Threading
- Remote object communication, such as RMI and CORBA
Vendor Specific Functionality
- Scalability
- Failover
- Load balancing
Examining Java EE Container – API Services
Examine the EJB Application Creation Process
1. Use your preferred object oriented methodology to analyze the business problem you are working on:
- The functional requirements of the application that is the business use cases.
- The non functional requirements of the application such as scalability requirements,
- The business logic that services the use cases
- Persistence data required by the application
2. Analyze the inter-tier communications requirements.
- Identify the synchronous communication requirements of the application.
- identify the asynchronous communication requirements of the application.
3. Use entity classes to model the persistence data.
4. Use session beans to model the server side business logic and synchronous service facade for the server side components.
5. Use the JMS API and message - driven beans to model the asynchronous communication requirements of the application.
6. Create the client.
7. Assemble and package the application.
8. Deploy the server side components.
9. Package and distribute the client.
Java EE Platform Roles
- Application component provider
- Application assembler
- Deployer
- System administrator
- Java EE product provider
- Tool provider
Comparing Java EE Application Development With Traditional Enterprise Application Development
No comments:
Post a Comment