user manual

Chapter 21: Connecting to Resources with BES: using the Definitions Archive (DAR) 221
Chapter
21
Chapter 21Connecting to Resources with
BES: using the Definitions
Archive (DAR)
J2EE specifies a uniform mechanism to establish connections to relational
databases using JDBC datasources, message brokers using JMS resource
objects, and general Enterprise Information Systems (EIS) using Connectors
resource adapters. JNDI bound objects called resource connection factories
are used to implement this mechanism. For example, a JDBC datasource is
an object that your applications use to establish connections to a database. In
the Borland Enterprise Server, creating, editing, and deploying all types of
resource entries is done using the Management Console and DDEditor. You
capture the properties that define the resource objects in an XML descriptor
and then use normal deployment procedures to bind the objects into JNDI.
The Borland Partition's Naming Service takes care of creating the Java
objects representing the data that was provided in the descriptor and binding it
to the proper JNDI name during deployment. Once bound, you may reference
the datasource from your enterprise beans and servlets using the resource-
reference elements in their deployment descriptors. This is a portable way to
specify a particular database instance, message broker instance, or legacy
instance.
Borland provides mechanisms for deploying both. Go toChapter 22, “Using
JDBC” and Chapter 23, “Using JMS” for more specific information. Setting up
and deploying these requires the following steps: