Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.geeksforgeeks.org/java/j2ee-multitier-architecture/ below:

J2EE Multitier Architecture - GeeksforGeeks

Last Updated : 10 Jan, 2025

A tier is an abstract concept that defines a group of technologies that provide one or more services to its clients. In multi-tier architecture, each tier contains services that include software objects, DBMS, or connectivity to legacy systems. IT departments of corporations employ multi-tier architecture because it's a cost-effective way to build an application that is flexible, scalable, and responsive to the expectations of clients.

The functionality of the application is divided into logical components that are associated with a tier. Each component is a service that is built and maintained independently of the other services. Services are bound together by a communication protocol that enables service and sends information from and to other services.

Multi-tier architecture is composed of:

• Clients: It Refers to a program that requests service from a component.
• Resource: A resource is anything a component needs to provide a service.
• Component: It is part of a tier that consists of a collection of classes or a program that performs a function to provide a service.
• Containers: It is software that manages a component and provides system services to the component. A container handles persistence, resource management, security, threading, and other system-level services from components that are associated with the container. Example: APIs.

J2EE is a four-tier architecture that consists of:

1. Client Tier/ Presentation Tier
2. Web Tier 
3. Enterprise JavaBeans Tier/ Business Tier 
4. Enterprise Information Systems Tier

These tiers are explained in detail below.

It consists of programs that interact with the users. These components prompt the user for the input conversion as
a request to forward to software on the component that processes the request and returns the result to the client program. Components under Client tier in J2EE Specification:

• Applet Client- It is a component used by Web clients that operate within Applet Container. It is a Java-enabled web browser.
• Application Client –It is a Java application that operates within the application container. It is the Java Runtime Environment (JRE).
• Rich client- This does not come under J2EE Specification. This is not considered a component of the client because it can be written in a language other than Java. J2EE does not define containers for Rich clients but these clients access any tier in the environment using HTTP, SOAP, and ebXML protocols.
• Clients are classified by the technology used to access the components and resources. 

Categories of Client Tier: There are 5 categories of clients

• Web Client,
• Java Beans Client
• EIS Client
• Web-service peers and
• Multi-tier client.

It provides the Internet functionality to the J2EE  application. The components on the web tier use HTTP to receive requests and send responses to the client that resides on the tier. Web-Tier Provides services to Client-tier using HTTP. The responsibilities act as an intermediary between components working on the web tier and other tiers and the client tier. The intermediary activities are:

• Accepting info from other s/w sent using POST, GET, and PUT using HTTP.
• Transmit data such as images and dynamic content.

Components of Web Tier: Two components that work on the web tier are mentioned below:

• Servlets
• Java server pages (JSP)

It contains business logic for J2EE applications. In this tier two or more EJB reside. It is a core component for every J2EE  Application.

• EJB beans are managed by the EJB server- which is a distributed object server that works on the EJB tier and manages transactions, and security, and ensures multi-threading and persistence when EJB are accessed.
• EJB tier provides key features such as concurrency, scalability, life cycle management, and fault-tolerant ( Back-Up) to the J2EE applications.
• EJB server and EJB container together handle low-level-systemservice required for implementing business logic in J2EE applications.

Some of the system services include Resource Pooling, Distributed object protocols, thread management, State Management, Process Management, Object persistence, Security, and Deployment Configuration.

EIS tier links the J2EE application to resources and legacy systems that are available on the corporate backbone network. It is the tier where the J2EE applications directly or indirectly interface with a variety of technologies including DBMS and Mainframes. Components on the EIS communicate to resources using CORBA or Java Connectors. 

Access Control List (ACL)

• It controls communication between tiers. 
• It acts as a bridge on different virtual networks because it adds security to web Applications. 
• ACL prevents hackers to access DBMS and similar resources.

EIS-Tier provides connectivity to the resources that are not part of J2EE- which includes resources such as Legacy Systems, DBMS, and systems provided by third-party. Provides flexibility to developers to connect resources that are not part of J2EE using CORBA and Java Connectors or through proprietary protocols.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4