Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
Chapter 3: Creating applications with J2EE technologies 15
Multi-tier applications
handle business logic, all on the client tier. You would use JDBC or Connectors to
access the data on the Enterprise Information System (EIS) tier.
Consider using the client-server model only when the number of desktops running
clients is quite small and will remain so. Once the demand for more than a few client
instances increases, you should probably consider another type of application
architecture.
Multi-tier applications
Here you see the classic multi-tier, distributed architecture that uses three tiers: the
browser on the client tier, the web container and EJB container on the middle tier that
runs on a J2EE server, and the Enterprise Information Systems (EIS) tier that is
managed by a database system. Such an application uses web components such as
JavaServer Pages (JSPs), servlets, and XML to manage the application’s presentation
logic. The EJB container contains enterprise beans that respond to requests from the
web tier components and access the data in the EIS tier.
When should you use JavaServer Pages and when should you use servlets?
JavaServer Pages are intended as user interface components. Servlets are usually
used for processing requests and controlling application logic.
XML can be very important in multi-tier applications. XML data messages use HTTP as
their transport protocol. Such data messages can encapsulate all types of data and
respond to a variety of client types, including XML-enabled browsers.
Stand-alone clients
Not all multi-tier applications use a browser on the client tier. Often the client is a Java
client or a client written in another language that consumes dynamic web content or an
application that interacts directly with enterprise beans running in an EJB container.
This diagram shows you the possibilities of this type of application:
Note that this diagram includes the client-server application also as such an application
includes a stand-alone client, too.