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 17
Web-centric applications
Web-centric applications
There are times when your application just doesn’t need to use enterprise beans and if
you do so, you add a layer of complexity. If your application doesn’t require
transactions on a distributed system, consider a web-centric application model:
This scenario puts both the presentation and business logic on the web tier. The web
container can host JavaServer Pages and servlets. The client is simply a browser and
data is transferred using XML, HTTP protocol, and/or HTML pages. Servlets can
access the EIS tier, when necessary, using JDBC or connectors. Applications using
this type of architecture are quite common.
Business to business
When you need a web-based commerce solution, consider the business-to-business
model. This might include multiple web containers and multiple EJB containers.
Web container to web container architecture is suitable for ecommerce solutions.
Communication takes place through XML data message over HTTP. Such applications
are very loosely coupled.
Peer-to-peer communication between EJB containers offers a more tightly coupled
model that works well for intranet solutions. In these types of applications, seriously
consider using message-driven enterprise beans and Java Message Service (JMS),
which enable you to develop loosely coupled applications.