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 2: Programming for the Java 2 Platform, Enterprise Edition 7
Why are J2EE applications desirable?
This expanded diagram shows you the various components you might find running on
the various tiers:
The client in a J2EE application can be a JavaServer Page (JSP), HTML page, or
applet running in a browser; a Java application on a desktop machine; or even a Java
client on some portable device, such as a personal digital assistant (PDA) or cell
phone.
The middle-tier can have a servlet or a JSP-generated servlet running on a web server.
These elements usually make up the server-side presentation logic. An EJB container
provides a runtime environment for Enterprise JavaBeans™, which contain the
business logic of application. Both a web server and an Enterprise JavaBeans (EJB)
container provide services to the components that run on them. Because these
services are always available, programmers don’t have to include them in the
components they write.
The Enterprise Information System (EIS) tier is a repository for the enterprise’s data.
Usually it consists of the data in a relational database system.
Few J2EE applications have all of these components. They can be mixed and matched
in very flexible ways to meet the needs of the enterprise. See Chapter 3, “Creating
applications with J2EE technologies” for more on this topic.