web server - Borland Technical Publications

JNDI Definitions Module
Important
serial URL prefix, that is “serial://”. With the Naming Service being the default service
provider, this prefix is no longer required in JNDI name specification. Deployment of
existing DARs/JNDI Definitions modules that have JNDI names with this prefix are now
automatically bound to the Naming Service.
A resource related object is obtained in J2EE through a resource reference. You can
reference resource connection factories or JMS destinations from EJBs, servlets and
other J2EE application components using resource-reference elements in the
component's deployment descriptors. Refer to Chapter 22, “Using JDBC” for more
specific information on how to define JDBC datasource resource references, and
Chapter 23, “Using JMS” for resource reference definition examples of JMS connection
factories and destinations.
Each BES partition has a predeployed DAR module named default-resources.dar
containing example definitions for JDBC datasources, JMS connection factories and
JMS destinations. This module can be examined, updated and redeployed in the
following steps:
1 Navigate to default-resources.dar under the Deployed Modules node of a partition
in the left pane of the BES console.
2 Right-click on default-resources.dar and select Edit deployment descriptor from
the context menu. The Borland Deployment Descriptor Editor window will open. The
available datasources and connection factories should be visible in the left pane.
3 Right-click on the root node in the navigation pane of the Borland Deployment
Descriptor Editor and select the appropriate option to create a New object you want
to add.
When a J2EE component attempts a JNDI lookup for a resource reference, vendor
classes associated with the resource object must be available in the runtime
environment. If the J2EE component is deployed to a BES partition, the vendor class
libraries must be deployed to the partition as a library archive. Exceptions to this rule
include JNDI lookups for resource objects whose dependent class libraries are bundled
with BES. For example, a JDataStore datasource or any JMS resource object of the
JMS message server installed with BES.
For documentation updates, go to www.borland.com/techpubs/bes.
JNDI Definitions Module
Note
Resource related objects are bound under the Naming Service through deployment of
a DAR file containing the JNDI Definitions Module. A DAR has a special .dar file
extension. It must be deployed to a BES partition either individually or packaged with
other J2EE modules in an EAR file.
A DAR is not a part of the J2EE specification. It is a Borland-specific implementation
designed to simplify deployment and management of resource connection factories
and JMS destinations. You do not package connection factory or JMS destination
vendor classes in this archive type. Those classes must be deployed as a library to
individual Partitions.
The only contents of the DAR that you must provide is an XML descriptor file called
jndi-definitions.xml. It contains definitions for resource related objects, each with a
JNDI name identifying its location in JNDI. Like other descriptors, this is placed within
the META-INF directory of the DAR. The contents of the DAR hence is as follows:
META-INF/jndi-definitions.xml
192 BES Developer’s Guide