 |  JFramework |  Web Search | Download | Newsletters | Firm Profile |
|
Menu What is a Framework Framework Objectives Developing a Framework Architecture J2EE App Architecture Physical Architecture App Building Approaches Structuring Web App Components Manager Object Relational Mapping Online Documentation Glossary News Download Message Board Contacts Summary
|
||
 |
 |  J2EE App Architecture |
| You Are Here: Home > J2EE App Architecture |
|
The J2EE standard requires building component-based enterprise applications. The J2EE architecture consists of three major parts: o Components that hold presentation or business logic (EJBs, Servlets, JSPs) o Containers that provide context for components (Web Server, EJB Container - Application server) o Connectors (HTTP, JDBC, JNDI, CORBA, RMI) The J2EE application logic is divided into components according to their function, and the different application components that make up a J2EE application can be installed on the same or different servers. Where an application is installed depends on which tier in the multi-tier J2EE environment the application component belongs to. The tiers are client tier, Web tier, business tier and enterprise information system (EIS) tier, as shown in the figure. Each tier has a well-specified interface and may include application components based on one or more technologies. o Client tier - The client tier displays information and collects input from the end user. J2EE technology supports several types of client presentation technology, including Hypertext Markup Language (HTML) clients, applets, XML, mobile devices. o Web tier (Presentation tier) - This tier generates presentation logic and accepts user input from HTML, applet, XML clients and mobile devices, and generates appropriate responses for the user. You can implement this tier as Java technology-based servlets ("Java servlets") or as pages created with JavaServer Pages TM (JSP TM pages) technology on a Web server o Business tier - This tier implements the business logic. It consistes of multifunctional business components. o EIS tier - This tier handles enterprise information system software, and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems and other legacy information systems. Our Primary Goal: Developing framework that embraces the creation of and using components.  |
|
|
|
||
