Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Download as rtf, pdf, or txt
Download as rtf, pdf, or txt
You are on page 1of 5

Today, more and more developers want to write distributed

transactional applications for the enterprise and leverage the


speed, security, and reliability of server-side technology.

The Java 2 Platform, Enterprise Edition (J2EE/Java EE)


technology provides a component-based approach to the
design, development, assembly, and deployment of enterprise
applications.

The Java EE offers a multi-tiered distributed application model,


the ability to reuse components, integrated Extensible Markup
Language (XML)-based data interchange, a unified security
model, and flexible transaction control.

Distributed Multi-tiered Applications

The Java EE uses a multi-tiered distributed application model.


Application logic is divided into components according to function,
and the various application components that make up a Java EE
application are installed on different machines depending on the tier
in the multi-tiered Java EE environment to which the application
component belongs.

 Client-tier components run on the client machine.


 Web-tier components run on the J2EE server.
 Business-tier components run on the J2EE server.
 Enterprise information system (EIS)-tier software runs on the
EIS server.

J2EE Components

J2EE applications are made up of components. A J2EE


component is a self-contained functional software unit that is
assembled into a J2EE application with its related classes and
files and that communicates with other components
J2EE specification defines the following J2EE components:

 Application clients and applets are components that run


on the client.
 Java Servlet and JavaServer Pages (JSP ) technology
components are Web components that run on the server.
 Enterprise JavaBeans (EJB ) components (enterprise
beans) are business components that run on the server.

J2EE components are written in the Java programming


language and are compiled in the same way as any program in
the language. The difference between J2EE components and
"standard" Java classes is that J2EE components are
assembled into a J2EE application, verified to be well formed
and in compliance with the J2EE specification, and deployed to
production, where they are run and managed by the J2EE
server.

J2EE Containers

The J2EE server provides underlying services in the form of a


container for every component type. Because you do not have to
develop these services yourself, you are free to concentrate on solving
the business problem at hand.

Container Services
Containers are the interface between a component and the low-level
platform-specific functionality that supports the component. Before a
Web, enterprise bean, or application client component can be
executed, it must be assembled into a J2EE application and deployed
into its container.

Container Types

J2EE Server and Containers

J2EE server
The runtime portion of a J2EE product. A J2EE server provides EJB
and Web containers.
Enterprise JavaBeans (EJB) container
Manages the execution of enterprise beans for J2EE
applications. Enterprise beans and their container run on the J2EE
server.

Web container
Manages the execution of JSP page and servlet components for
J2EE applications. Web components and their container run on the
J2EE server.

Application client container


Manages the execution of application client components.
Application clients and their container run on the client.

Applet container
Manages the execution of applets. Consists of a Web browser
and Java Plug-in running on the client together.

You might also like