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
10 Developing Applications for J2EE Servers
How JBuilder can help
manipulate data from a database so you can build data-aware servlets and JSPs.
For information about InternetBeans Express, see “Using InternetBeans Express” in
the Developing Web Applications.
This is the middle-tier J2EE technology that uses an EJB container:
■
Enterprise JavaBeans (EJBs)
Enterprise JavaBeans are server-side components that contain the business logic of
the application. JBuilder assists you in building EJB 1.x and EJB 2.0 components.
Start building enterprise beans by using the EJB wizards on the Enterprise page of
the object gallery (File|New|Enterprise). For building EJB 2.0 components, JBuilder
offers the EJB designer, a Two-Way Tool™ that allows you to design your beans
visually all the while keeping your code, deployment descriptors, and design
synchronized. For more information about building, testing, and deploying
enterprise beans, see “An introduction to EJB development” in Developing
Applications with Enterprise JavaBeans.
As you create your enterprise beans, JBuilder is building your EJB deployment
descriptors. You can use JBuilder’s EJB DD Editor to modify them as you wish. For
more information about the EJB DD Editor see Chapter 11, “Editing J2EE
deployment descriptors” and “Editing EJB deployment descriptors” in Developing
Applications with Enterprise JavaBeans.
All the web application components and enterprise bean components can be combined
and delivered in an application module. JBuilder has an Application Module wizard. For
more information, see “Creating an application module” in the “Deploying enterprise
beans” chapter of the Developing Applications with Enterprise JavaBeans book.
Other J2EE technologies
While not confined to a particular architectural tier, these technologies are enablers
that make things work:
■
Java Database Connectivity (JDBC)
JDBC is the standard used to access your database on the Enterprise Information
Systems (EIS) tier. It defines a Java API you use to write SQL statements that are
sent to your database.
JBuilder includes DataExpress, a component library for accessing data in your
database. It connects your application to your database using JDBC drivers.
JBuilder also includes JDataStore, an all-Java embedded database and component
library. You access JDataStore using JDBC.
Entity beans that access rows in your database, also connect to your data using
JDBC.
■
Java Message Service (JMS)
JMS is an enterprise messaging service that routes messages between
components and processes in a distributed application.
The Borland Enterprise Server includes SonicMQ, a JMS implementation. Also
JBuilder supports EJB 2.0 components, which include message-driven beans.
Message-driven beans integrate JMS into enterprise beans. JBuilder also includes a
JMS wizard. See “Creating JMS producers and consumers” in Developing
Applications with Enterprise JavaBeans for information on creating classes and
applications that can create and consume JMS messages.
■
Java Naming and Directory Interface (JNDI)
All J2EE servers use JNDI, a Java naming service used to locate distributed
objects.