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
16 Developing Applications for J2EE Servers
Stand-alone clients
Consumers of dynamic web content
One type of stand-alone client is a Java application or another programming language
that consumes dynamic web content. This web content is usually XML data messages:
The web container performs the XML transformations and provides web connectivity to
clients. The client handles the presentation logic while the web tier manages the
business logic and accesses the data on the EIS tier if necessary. Business logic might
be implemented as enterprise beans. The J2EE technologies likely to be used are
XML, servlets, web services, and possibly enterprise beans and JDBC to access
enterprise data.
Java client calling EJBs
Enterprise JavaBeans (EJBs) are server-side components that run in a middle-tier EJB
container. The container provides services to the beans, such as transaction
management and security. You, as the developer, don’t have to implement such low-
level and complex services, but instead can concentrate on developing the business
logic for the beans, knowing that the services are there when they are needed.
Developers often choose EJBs when building applications that will be distributed over
several servers. They also like to use EJBs because of the transparent way they
handle transactions.
The following diagram depicts a Java client that calls upon the business methods
encapsulated with the enterprise beans that are running in an EJB container. If the
beans are entity beans, they access company data on the EIS tier through JDBC and
J2EE connectors. Ideally, the client should access company data through a session
bean which interacts with the entity beans that model company data. A session bean
that interacts with an entity bean in this way is usually using the Session Facade
design pattern; see “Creating session facades for entity beans” in Developing
Applications with Enterprise JavaBeans for more information. XML is used in the
deployment descriptors for enterprise beans.
If the application you need requires secure transactions over a distributed system,
consider using enterprise beans.