The database to which you want to connect might require
that you set some custom properties.
About this task
Depending on the database to which you want to connect, you
must define various properties. The following table presents the minimum
set of properties that are necessary to define the supported databases.
If your driver is not listed, check the
WebSphere Application
Server documentation for
more information.
Note: Some of these properties might already be
defined. For example, if you are following this configuration procedure
and have created a Derby database, all the properties for that database
are already defined.
Table 1. Database driver propertiesDatabase |
Properties |
DB2® Universal
JDBC Driver |
- databaseName: The actual database name if driverType is
set to 4, or a locally cataloged database name if driverType is
set to 2
- driverType: The possible values are 2 or 4.
The following properties are required only if driverType is 4:
- serverName: The TCP/IP address or host name
- portNumber: The TCP/IP port number
|
DB2 Universal
JDBC XA Driver |
- databaseName: The locally cataloged database
name
- driverType: The possible values are 2 or 4.
If you are running a version of DB2 earlier
than DB2 V8.1 FP6, you are restricted
to using only Type 2 driver. The following properties are required
only if driverType is 4:
- serverName: The TCP/IP address or host name
- portNumber: The TCP/IP port number
|
DB2 legacy
CLI-based Type 2 |
databaseName: for example, Sample |
Oracle JDBC Driver |
URL: For example, jdbc:oracle:oci:@sample |
Derby |
databaseName: The path
to the location of the database files. For more information, refer
to the Derby documentation. |
You can also set custom properties for any of the resources
that are listed in the Custom properties page.