Sun Microsystems 820433510 JavaDB Type 4 Driver

Note– An Oracle database user running the capture-schema command needs ANALYZE ANY
TABLEprivileges if that user does not own the schema. These privileges are granted to the user
bythe database administrator. For information about capture-schema, see Sun GlassFish
EnterpriseServer 2.1 Reference Manual.
JavaDB Type 4 Driver
TheJava DB JDBC driver is included with the Enterprise Server by default, except for the Solaris
bundledinstallation, which does not include Java DB. Therefore, unless you have the Solaris
bundledinstallation, you do not need to integrate this JDBC driver with the Enterprise Server.
TheJAR le for the Java DB driver is derbyclient.jar.
Congurethe connection pool using the following settings:
■Name:Use this name when you congure the JDBC resource later.
■ResourceType: Specify the appropriate value.
■DatabaseVendor: Java DB
■DataSourceClassname: Specify one of the following:
org.apache.derby.jdbc.ClientDataSource
org.apache.derby.jdbc.ClientXADataSource
■Properties:
■user- Specify the database user.
Thisis only necessary if Java DB is congured to use authentication. Java DB does not
useauthentication by default. When the user is provided, it is the name of the schema
wherethe tables reside.
■password- Specify the database password.
Thisis only necessary if Java DB is congured 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 dierent from the
default.
■URL:jdbc:javadb://serverName:portNumber/databaseName;create=true
Includethe ;create=true part only if you want the database to be created if it does not exist.
CongurationsforSpecic JDBC Drivers
Chapter3 • JDBC Resources 53