Home > Articles > Programming > Java

Inside J2EE

📄 Contents

  1. J2EE: Core Concepts
  2. J2EE n-Tier Application Architecture
  3. Conclusions
  • Print
  • + Share This
Like this article? We recommend

J2EE n-Tier Application Architecture

J2EE middleware defines a set of four independent tiers, over which applications can be built:

  • Client tier
  • Presentation logic tier
  • Business logic tier
  • Enterprise information systems tier

A pictorial representation of these tiers is shown in Figure 1.

Figure 1 J2EE: multitier application architecture.

Presentation logic and business logic tiers fall under the application server zone—which is nothing but the J2EE platform implementation.

Each of these tiers may physically be sitting over several machines. Moreover, within the application server zone the presentation logic can be hosted in one application server, and business logic can be hosted in another.

For example, it is possible to use iPlanet (a J2EE application server product from Sun) as an HTTP Web server and presentation logic container, and use Weblogic (another J2EE application server from BEA) to deploy business logic components.

It is common to associate the presentation logic tier with Servlet and JSP containers (discussed later in this article) and business logic tier to the Enterprise Javabeans container. It will be easier to understand tiers as conceptual entities—meant for ease of design—and containers as physical software instances—meant for providing the runtime environment for application components.

J2EE's multitier architecture is inspired by Model View Controller (MVC) architecture: A software methodology used for demarcating the boundaries and scope of individual application components in a complex system.

MVC advocates that those codes, which represent the business logic or core application functionality, should not be intermingled with those that present the proceed results to clients or other applications. They should possibly be independent of each other, and a controller should mediate the interactions between them.

For example, let us consider an Internet-based, bank account-transfer process. According to MVC, this process can be broken down to four independent tasks, as shown in Figure 2.

  • Task 1: The task of invoking the transfer from the browser (view)

  • Task 2: The task of invoking the mechanism that does the account transfer (controller)

  • Task 3: The task of doing the actual account transfer (business process or model)

  • Task 4: The task of showing the status of the transfer (success or failure) to the browser (view)

Figure 2 MVC look at an Internet account transfer process.

MVC states that the core business process (Task 3) should not assume anything about the clients. Instead of a browser, another application or a back office system may well invoke it. The process of orchestrating between the business logic and view elements is to be assigned to a dedicated entity called the controller.

Having been based on MVC methodology, J2EE's architecture naturally demarcates business logic from presentation logic tier. Controllers can be placed in either of these tiers or both. By doing so, J2EE provides room for reusability of business logic components.

J2EE Application Components

The J2EE standard defines a rich set of application component framework, with which almost all kinds of business applications can be built. These applications range from simple Web portals to complex, distributed, enterprise-scale transactional applications. Application components, which are the brick and mortar of enterprise systems, are built on the top of this framework.

J2EE component framework is only a rudimentary infrastructure—in the form of libraries, base classes, and interfaces. Application components that are built over them usually embody business logic and the presentation/controller logic that makes up the application.

For example, let us consider servlets, which are standard application components provided by J2EE. Servlets for a given business application are to be developed on top of a basic servlet interface provided by J2EE. While doing so, developers can make use of servlet libraries and services that come along with the servlet package. Many of the system level services, such as reading data from an HTTP input stream or writing data to an HTTP output stream, are available within these libraries, so that applications can readily make use of them.

Hence, we term the component infrastructure provided by J2EE as an application framework, and those codes written on top of it as J2EE application components. But I'll be using these two terms interchangeably, throughout this series for the sake of simplicity.

J2EE application components are available for the client tier, presentation tier, and business logic tiers, as shown in Figure 3.

These components include the following:

  • Client tier: applets, Javabeans

  • Presentation logic tier: servlets, Java server pages, Javabeans

  • Business logic tier: Enterprise Javabeans

Figure 3 J2EE application components.

It is very important to note that normal Java classes and Jar archives can be hosted in all of these tiers very well, apart from the J2EE-specific components listed above. In many cases, we will find application codes spilling outside the J2EE components into normal Java classes.

Components are not available for the Enterprise Information System (EIS) tier because EIS encompasses all enterprise backend resources —such as databases, BackOffice/legacy systems, and ERP implementations—in the J2EE realm. Obviously, all we need is access to these resources from our application components, which are taken care of by J2EE enterprise services. Thus, there is no scope for application components in the EIS tier.

Applications are to be coded by the programmer, using one or more of these components, and deployed in respective containers.

Arriving at a proper mix of application components for a given business scenario is the crafty job of a J2EE architect. Because there is a wide variety of components available, it requires considerable knowledge and experience to choose the right mixture of components that will result in optimized code and performance-rich applications.

By assigning specific and well-defined roles to each application component, J2EE aims to provide room for logical application architecture, design, and development. The component interfaces ensure that the components adhere to certain standards and exhibit common behavior, which provides the base for interoperable J2EE server environments.

These application components are loosely coupled across the tiers to ensure flexibility and reusability while interacting with each other. A whole range of enterprise services—such as mailing, database connectivity, messaging, and transaction processing—are available at the disposal of application components.

On the flip side, unlike .Net framework, which is Microsoft's middleware architecture, all J2EE application components are to be coded only in the Java language!

J2EE Enterprise Services

The nutrients for the blossoming of enterprise applications—such as mailing, database connectivity, messaging, and transaction processing—are readily catered to by the J2EE environment as enterprise services.

These essential services are made available in the form of interfaces, class libraries, drivers, and adapters. As in the case of operating systems, J2EE provides a common Java interface over these services, so that the application codes are shielded from the subtleties of specific service implementation provided by the application vendors.

For example, JDBC is one service that provides connectivity to a wide variety of databases available in the market. Connectivity to different databases (such as Oracle, MySQL, Informix, and SQL Server) is achieved through specific JDBC drivers that are provided by the database manufacturers themselves or by third-party vendors. Application developers need not worry about the intricacies of specific databases; all they need to do is to make use of standard JDBC calls to access these resources, and the underlying JDBC driver takes care of implementing them.

J2EE enterprise services include the following:

Connectivity Services

  • Java Database Connectivity (JDBC): provides database connectivity services

  • Java Connector Architecture (JCA): provides connectivity to legacy systems

Communication Services

  • Java Messaging Service (JMS): provides messaging services across the tiers and components

  • Java Activation Framework/Java Mailing services (JAF/Javamail): provides e-mail services

  • Java Interface Definition Language/RMI—IIOP: enable CORBA communication with J2EE

  • Java XML APIs (JAX): provides XML parsing/binding services

Identification Services

  • Java Naming and Directory Interface (JNDI): provides distributed naming and directory services

  • Other Services

    • Java Transaction Service (JTS/JTA): provides transaction-monitoring services

    • Java Authentication and Authorization service (JAAS): provides access control services

    Specific drivers and adapters for selected services usually come bundled with the application server itself. For example, Web logic comes with a JDBC driver for connecting J2EE applications to Informix. This becomes an important selection criterion when evaluating different application servers for a given enterprise infrastructure.

    J2EE Runtime Environment (Containers)

    J2EE application components in different tiers come to life in their runtime environments, which are called containers in J2EE terminology. These containers are vendor-specific products that adhere to certain common interfaces, and provide the much-required low-level infrastructure facilities for J2EE middleware components.

    After being coded to J2EE standards, application components need to be deployed in the respective containers by using vendor-specific deployment tools.

    J2EE standard defines four different containers:

    • Applet container: hosts applets

    • Application client container: hosts standard Java application clients (including swing windows applications)

    • Web container: hosts servlets and JSPs in the presentation logic tier

    • EJB container: hosts Enterprise Javabeans in the business logic tier

    It is typical to include an HTTP Web server along with the Web containers to host static HTML Web pages, and almost all popular J2EE application servers have built-in HTTP Web servers.

    It is worthwhile to note that one of the principal visions of J2EE architecture was that developers should be writing codes for their business logic, and should not worry about system-level capabilities. This vision is achieved only through the concept of containers.

    The infrastructure facilities provided by the containers typically include memory management, synchronization/threading, garbage collection, availability, scaling, load balancing, and fault tolerance.

    The basic interfaces and facilities that should be implemented by the containers are defined in J2EE specifications, but the means by which they are to be accomplished, is left to the container vendor. Thus, J2EE provides the scope for vendor-specific codes while ensuring compatibility across different application servers. In fact, it is mainly with the help of containers, apart from other facilities, that vendors are able to distinguish themselves in the middleware industry.

    • + Share This
    • 🔖 Save To Your Account

    InformIT Promotional Mailings & Special Offers

    I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


    Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

    This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

    Collection and Use of Information

    To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

    Questions and Inquiries

    For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

    Online Store

    For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


    Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

    Contests and Drawings

    Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


    If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

    Service Announcements

    On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

    Customer Service

    We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

    Other Collection and Use of Information

    Application and System Logs

    Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

    Web Analytics

    Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

    Cookies and Related Technologies

    This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

    Do Not Track

    This site currently does not respond to Do Not Track signals.


    Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


    This site is not directed to children under the age of 13.


    Pearson may send or direct marketing communications to users, provided that

    • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
    • Such marketing is consistent with applicable law and Pearson's legal obligations.
    • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
    • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

    Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

    Correcting/Updating Personal Information

    If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


    Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

    Sale of Personal Information

    Pearson does not rent or sell personal information in exchange for any payment of money.

    While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

    Supplemental Privacy Statement for California Residents

    California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

    Sharing and Disclosure

    Pearson may disclose personal information, as follows:

    • As required by law.
    • With the consent of the individual (or their parent, if the individual is a minor)
    • In response to a subpoena, court order or legal process, to the extent permitted or required by law
    • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
    • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
    • To investigate or address actual or suspected fraud or other illegal activities
    • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
    • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
    • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


    This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

    Requests and Contact

    Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

    Changes to this Privacy Notice

    We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

    Last Update: November 17, 2020