user manual

222 BES Developer’s Guide
JNDI Definitions Module
1 If any external drivers are needed, which is usually the case, they must be
deployed to the target Partition as a library archive. See User's Guide,
Using Partitions chapter, for information on deploying to Partitions. Note
that this step is not necessary if you are using the native all-Java database,
JDataStore as your backend, or the JMS services broker.
2 Using the Console choose the predeployed JNDI Definitions Module in the
Deployed Modules folder named default-resources.dar and right-click to
launch the DDEditor. The predeployed module already has a datasource
defined for JDataStore and sample JMS connection factories and
destinations for the JMS services broker.
3 Add a new definition or edit an existing one in the module to suit your
environment, then save the module. The changes will take effect on the
server. Information on defining JDBC datasources and JMS connection
factories is provided below.
Important For documentation updates, go to www.borland.com/techpubs/bes.
JNDI Definitions Module
J2EE resource connection factory objects are bound to JNDI when they are
deployed as a part of a JNDI Definitions Module. This module is similar to
other J2EE standard Java archive types, and ends in the extension .dar. This
module is also referred to as a DAR, therefore. This module adds to the
standard J2EE module types like JAR, WAR, and RAR. It can be packaged as
a part of an EAR, or deployed stand-alone. Since datasources are contained
in their own module(s), they appear in the Server tree of the Borland
Enterprise Server's console, meaning you can easily enable and disable them
by right-clicking their representations in the tree.
Note A DAR is not a part of the J2EE specification. It is a Borland-specific
implementation designed to simplify the deployment and management of
connection factories. You do not package connection factory classes in this
archive type. Those classes must be deployed as a library to individual
Partitions.
Since the Partition itself constructs the connection factory class, the only
contents of the DAR that you must provide is an XML descriptor file called
jndi-definitions.xml. Like other descriptors, this is placed within the META-INF
directory of the DAR. The contents of the DAR hence look like the following:
META-INF/jndi-definitions.xml
You deploy the DAR containing the descriptor file just as you would any other
J2EE module using either the console or command-line utilities, or as part of
an EAR. Note that DAR deployment semantics are exactly like other J2EE
modules. You can deploy any number of distinctly named DARs in the same
Partition or to a cluster. Should two deployed DARs have objects with identical
JNDI names, the last deployed module overwrites its object on the same
node.