0% found this document useful (0 votes)
95 views

J2EE Intro

J2EE provides a standard for developing multi-tier enterprise applications using modular Java components. It defines a thin-client architecture with presentation, business, and data tiers that separates concerns and improves scalability, flexibility, and reusability. The key J2EE components are servlets, JSPs, and EJBs, and it provides services like JDBC, JMS, security through an application server like GlassFish or JBoss.

Uploaded by

Saad Chougule
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
95 views

J2EE Intro

J2EE provides a standard for developing multi-tier enterprise applications using modular Java components. It defines a thin-client architecture with presentation, business, and data tiers that separates concerns and improves scalability, flexibility, and reusability. The key J2EE components are servlets, JSPs, and EJBs, and it provides services like JDBC, JMS, security through an application server like GlassFish or JBoss.

Uploaded by

Saad Chougule
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 25

J2EE : Why, What and How

TM

1
Objectives
• Why J2EE?
• What is J2EE?
• How to use J2EE?

2
Why J2EE?

Motivation for J2EE


• Need for
– New multi-tier enterprise computing model in
web environment
– A way to bring in different elements of
enterprise application
• Web interface design
• Transaction processing
• Meeting non-functional system requirements:
– Availability, reliability, enhance ability, performance,
scalability, reusability, interoperability
• Timely development and deployment
3
Why J2EE?
Two-tier Client/Server
Architecture

Client Server

4
Why J2EE?

Simple Web Client/Server


• Interaction of two-tier architecture
• Client: simply accesses web pages
through web browser
• Server: retrieves html documents

5
Why J2EE?

CGI-based Web Client/Server


• Interaction of two-tier architecture
• Client: uses service requiring secondary
storage
• Server: manipulates forms, Database
updates, (primitive) electronic commerce
• Fat Server/ Thin Client

6
Why J2EE?
Java Applet-based Web
Client/Server
• Interaction of two-tier architecture
• Client: uses Java Applet for client-side
computation
• Server: provides Applet bytecode
• Fat Client/Thin Server

7
Why J2EE?
Two-tier Client/Server
Architecture
• So, important processing needs to be run on the server
• Then, Java needs to run on the server too to be more useful  enterprise
• The server is almost like what CGI-programming does
• Client: data access applying business logic and presentation of data
(computation)
• Server: serves only as service-database server, not application server web
server
Client Server

But what is the problem with this architecture? 8


Why J2EE?
Drawbacks of
two tier application architecture

• Easy to deploy, but difficult to enhance or


upgrade
• Reusability of business and presentation
logic difficult
• Not scalable

9
Why J2EE?

Vision of J2EE
• An open standard
• Umbrella for anything Java-related
• For designing, developing, assembling,
and deploying component-based
enterprise applications
• Separation of business logic from
presentation
• Reusability, enhanceability, scalability,
interoperability
10
Why J2EE?

Separation of Business logic


from Presentation logic
• Presentation logic : display
• Business logic : what the company wants to do

Example: the distribution of different sales figures by diff dept


(business logic) can be represented in many different ways (pie
chart, bar graph, etc)

11
Why J2EE?
• Simplifies the complexity of a building n-
tier application
• Standardizes an API between components
and application server container
• J2EE Application Server and Containers
provide the framework services

12
What is J2EE?
• Defines the standard for developing multitier
enterprise applications
• Simplifies enterprise applications by:
– Basing them on standardized, modular components
– Providing a complete set of services to those
components
– Handling many details of application behavior
automatically, without complex programming

13
What is J2EE?

Thin-client Multi-tiered Architecture

14
J2EE Tiers
• Client Presentation
 HTML or Java applets
deployed in Browser
 XML documentations
transmitted through HTTP
 Java clients running in
Client Java Virtual Machine
(JVM)
• Presentation Logic
 Servlets or JavaServer
Pages running in web
server
• Application Logic
 Enterprise JavaBeans
running in Server

15
J2EE Components & Services
• Components
- Java Servlets
- JavaServer Pages (JSP)
- Enterprise JavaBeans (EJB)
• Standard services & supporting technologies
- Java database connectivity(JDBC) data access API
- Java Messaging Service (JMS)
(Remote Method Invocations (RMI))
- Extensible Markup Languages(XML)
- JavaIDL (Interface Description Language)
- JavaMail
- Java Security
- CORBA technology
- Design Patterns
16
Advantages of Multi-tiers
• Tiers separate functionality:
– Presentation Logic, Business Logic, Data
Schema
• Easier upgrade since one tier can be
changed without changing the rest
• Lower deployment and maintenance cost
• More flexible (can support changes), more
extensible (can add functionality)
17
18
What is J2EE?

The Big Picture

19
What is J2EE?

4-Tier Model
Web Tier
Client Tier

EIS Tier

Business
Tier 20
What is J2EE?

What is Application Server


Application servers enable the development of
multi-tiered distributed applications. They are
also called “middleware”

An application server acts as the interface


between the database(s), the web servers and
the client browsers

21
Application Server: Key Services

22
GlassFish Server

• GlassFish is an open source community comprising of users, developers,


parteners that are developing an open source application server that
implements Java EE.

• GlassFish is an Application Server which can also be used as a Web Server


(Http Server). A web Server means: Handling HTTP requests (usually from
browsers). A Servlet Container (e.g. Tomcat) means: It can handle servlets
& JSP. You should use GlassFish for Java EE enterprise applications.

23
JBoss- Application Server

24
What is J2EE?

J2EE Components

• Java Servlets

• JavaServer Pages (JSP)

• Enterprise JavaBeans (EJB)

25

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy