- Derby JDBC Provider
The Derby JDBC driver
provides JDBC access to the Cloudscape v10.x database by using the
framework that is already embedded in WebSphere Application Server
for Cloudscape. However, you cannot use any Version 4.0 data sources
with Cloudscape v10.x.
The Derby JDBC Provider supports one
phase data source:
org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
Requires
JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar
Requires
DataStoreHelper class:
com.ibm.websphere.rsadapter.DerbyDataStoreHelper
Does
not require a valid authentication alias.
Requires properties:
- databaseName The name of the database from which the
data source obtains connections. If you do not specify a fully qualified
path name, Application Server uses the default location of WAS_HOME/derby (or
the equivalent default for a supported UNIX system or Linux system
environment).
- Example database path name for Windows: c:\temp\sampleDB
- Example database path name for supported UNIX systems or Linux
systems: /tmp/sampleDB
If no database currently exists for the path name you want to
specify, simply append ;create=true to the path name
to create a database dynamically. (For example: c:\temp\sampleDB;create=true)
- Derby JDBC Provider (XA)
The Derby JDBC
driver (XA) provides JDBC access to the Cloudscape v10.x database
by using the framework that is already embedded in WebSphere Application
Server for Cloudscape. However, you cannot use any Version 4.0 data
sources with Cloudscape v10.x.
The Derby JDBC Provider (XA)
supports two phase data source:
org.apache.derby.jdbc.EmbeddedXADataSource
Requires
JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar
Requires
DataStoreHelper class:
com.ibm.websphere.rsadapter.DerbyDataStoreHelper
Does
not require a valid authentication alias.
Requires properties:
- databaseName The name of the database from which the
data source obtains connections. If you do not specify a fully qualified
path name, Application Server uses the default location of WAS_HOME/derby (or
the equivalent default for a supported UNIX system or Linux system
environment).
- Example database path name for Windows: c:\temp\sampleDB
- Example database path name for supported UNIX systems or Linux
systems: /tmp/sampleDB
If no database currently exists for the path name you want to
specify, simply append ;create=true to the path name
to create a database dynamically. (For example: c:\temp\sampleDB;create=true)
- Derby Network Server using Universal JDBC Driver
Deprecation note: The JDBC
provider for Derby Network Server using the Universal JDBC Driver
is deprecated in WebSphere Application Server Version 6.1. Therefore
it is no longer an available choice among provider types in the administrative
console. The console now lists the JDBC provider for Derby Network
Server using Derby Client.
The Derby Network Server using
the Universal JDBC Driver takes advantage of the Network Server support
that the DB2 Universal JDBC Driver type 4 provides. You cannot use
any Version 4.0 data sources with Cloudscape v10.x.
Use the
following one phase data source for the Derby Network Server using
the Universal JDBC Driver:
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
Requires
JDBC driver files:
- db2jcc.jar If you install and run DB2, you must
use the db2jcc.jar file that comes with DB2. To do
that, the classpath in the JDBC template for Derby Network Server
is set to be:
<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath>
<classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/otherJars/db2jcc.jar</classpath>
<classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath>
which means that the db2jcc.jar from DB2 always takes precedence.
Note that this also means that you must set the DB2 environment variable DB2UNIVERSAL_JDBC_DRIVER_PATH in
WebSphere Application Server when you set up your DB2 data source.
This is instead of hard coding the path of the db2jcc.jar for DB2
data sources.
- db2jcc_license_cu.jar This file is the DB2 Universal
JDBC Driver license file that provides access to the Derby databases
using the Network Server framework. Use this file to gain
access to the database. This file ships with WebSphere and is located
in ${UNIVERSAL_JDBC_DRIVER_PATH}.
Note: UNIVERSAL_JDBC_DRIVER_PATH is
a WebSphere environment variable that is already mapped to the location
in Websphere Application Server where the license jar file is located,
and will only be used if the DB2UNIVERSAL_JDBC_DRIVER_PATH is
not set. DB2 users should ensure that DB2UNIVERSAL_JDBC_DRIVER_PATH is
set to avoid loading multiple versions of the db2jcc.jar file.
Note: DB2UNIVERSAL_JDBC_DRIVER_PATH is
a WebSphere environment variable that you must set to point to the
location of db2jcc.jar file (that comes with DB2). This variable is
set only if you create a DB2 provider.
Note: Derby requires
only db2jcc_license_c.jar; however, WebSphere Application Server uses db2jcc_license_cu.jar
because this works for both DB2 UDB and Derby.
Requires
DataStoreHelper class:
com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper
Requires
a valid authentication alias.
Requires properties:
- databaseName The name of the database from which the
data source obtains connections. If you do not specify a fully qualified
path name, Application Server uses the default location of WAS_HOME/derby (or
the equivalent default for a supported UNIX system or Linux system
environment).
- Example database path name for Windows: c:\temp\sampleDB
- Example database path name for supported UNIX systems or Linux
systems: /tmp/sampleDB
If no database currently exists for the path name you want to
specify, simply append ;create=true to the path name
to create a database dynamically. (For example: c:\temp\sampleDB;create=true)
- driverType Only the Type 4 driver is allowed.
- serverName The TCP/IP address or the host name for the
Distributed Relational Database Architecture (DRDA) server.
- portNumber The TCP/IP port number where the DRDA server
resides. The default value is port 1527.
- retrieveMessagesfromServerOnGetMessage This property is
required by WebSphere Application Server, not the database. The default
value is false. You must set the value of this property
to true, to enable text retrieval using the SQLException.getMessage() method.
- Derby Network Server using
Derby Client provider
Use this provider to access only Cloudscape
10.1.x databases that run on the same node as WebSphere Application
Server.
Use the following one phase data source for the Derby
Network Server using Derby Client provider:
org.apache.derby.jdbc.ClientConnectionPoolDataSource
Cloudscape
v10.1.x does not support Version 4.0 data sources.
Requires
the following JDBC driver file:
Requires
DataStoreHelper class:
com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper
Requires
the
databaseName property: The name of the database from which
the data source obtains connections. If you do not specify a fully
qualified path name, Application Server uses the default location
of
WAS_HOME/derby (or the equivalent default for
a supported UNIX system or Linux system environment).
- Example database path name for Windows: c:\temp\sampleDB
- Example database path name for supported UNIX systems or Linux
systems: /tmp/sampleDB
If no database currently exists for the path name you want to
specify, append
;create=true to the path name to
create a database dynamically. (For example:
c:\temp\sampleDB;create=true)
- Derby Network Server using
Derby Client provider (XA)
Use this provider to access only
Cloudscape 10.1.x databases that run on the same node as WebSphere
Application Server.
Use the following XA data source for this
Derby Network Server using Derby Client provider:
org.apache.derby.jdbc.XADataSource
Cloudscape
v10.1.x does not support Version 4.0 data sources.
Requires
the following JDBC driver file:
Requires
DataStoreHelper class:
com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper
Requires
the
databaseName property: The name of the database from which
the data source obtains connections. If you do not specify a fully
qualified path name, Application Server uses the default location
of
WAS_HOME/derby (or the equivalent default for
a supported UNIX system or Linux system environment).
- Example database path name for Windows: c:\temp\sampleDB
- Example database path name for supported UNIX systems or Linux
systems: /tmp/sampleDB
If no database currently exists for the path name you want to
specify, append
;create=true to the path name to
create a database dynamically. (For example:
c:\temp\sampleDB;create=true)
To learn more about the new Cloudscape code base, visit the
Open Source Apache Derby Project Web site or the IBM Cloudscape version
10.0 information center.