Java db type 4 driver – Sun Microsystems GLASSFISH ENTERPRISE 820433510 User Manual
Page 53
Note –
An Oracle database user running the capture-schema command needs ANALYZE ANY
TABLE privileges if that user does not own the schema. These privileges are granted to the user
by the database administrator. For information about capture-schema, see
Java DB Type 4 Driver
The Java DB JDBC driver is included with the Enterprise Server by default, except for the Solaris
bundled installation, which does not include Java DB. Therefore, unless you have the Solaris
bundled installation, you do not need to integrate this JDBC driver with the Enterprise Server.
The JAR file for the Java DB driver is derbyclient.jar.
Configure the connection pool using the following settings:
■
Name:
Use this name when you configure the JDBC resource later.
■
Resource Type:
Specify the appropriate value.
■
Database Vendor: Java DB
■
DataSource Classname:
Specify one of the following:
org.apache.derby.jdbc.ClientDataSource
org.apache.derby.jdbc.ClientXADataSource
■
Properties:
■
user
- Specify the database user.
This is only necessary if Java DB is configured to use authentication. Java DB does not
use authentication by default. When the user is provided, it is the name of the schema
where the tables reside.
■
password
- Specify the database password.
This is only necessary if Java DB is configured to use authentication.
■
databaseName
- Specify the name of the database.
■
serverName
- Specify the host name or IP address of the database server.
■
portNumber
- Specify the port number of the database server if it is different from the
default.
■
URL: jdbc:javadb://
serverName:portNumber/databaseName;create=true
Include the ;create=true part only if you want the database to be created if it does not exist.
Configurations for Specific JDBC Drivers
Chapter 3 • JDBC Resources
53