JDBC provider settings
Use this page to modify the settings for a JDBC provider.
To view this administrative console page, click
.Scope
Specifies the scope of the JDBC provider; data sources that are created with this JDBC provider inherit this scope.
Name
Specifies the name of the resource provider.
Information | Value |
---|---|
Data type | String |
Description
Specifies a text description for the resource provider.
Information | Value |
---|---|
Data type | String |
Class path
Specifies a list of paths or JAR file names which together form the location for the resource provider classes.
- D:/SQLLIB/java/db2java.zip for distributed operating systems.
- QIBM/ProdData/Java400/ext/db2_classes.jar for iSeries platforms.
- /usr/lpp/db2/db2710/classes/db2j2classes.zip for z/OS®.
Class path entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Class paths contain variable (symbolic) names which you can substitute using a variable map. Check the driver installation notes for the specific required JAR file names.
Information | Value |
---|---|
Data type | String |
Native Library Path
Specifies a list of paths that forms the location for the resource provider native libraries.
Native path entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Native paths can contain variable (symbolic) names which you can substitute using a variable map.
Information | Value |
---|---|
Data type | String |
Isolate this resource provider
Specifies that this resource provider will be loaded in its own class loader. This allows different versions or implementations of the same resource provider to be loaded in the same Java™ Virtual Machine. Give each version of the resource provider a unique class path that is appropriate for that version or implementation.
- You cannot isolate a resource provider if you specify a native library path. The Application Server will define a value for the native library path for some JDBC providers; this behavior is intended to help you configure your provider when a native library path is necessary. If you do not require the native library path, delete the value, and you will be able to select the option to isolate the resource provider.
- If you are running a mixed cell environment, the application server will remove any isolated
JDBC providers from nodes that are running at versions earlier than 7.0 if the provider is scoped
for a version 7.0 cell, and you have not migrated the provider from an older release. If you want to
use isolated resources at the cell level, do not use the resources in nodes that are running at
versions earlier than 7.0. Define a resource at the node level, or avoid using the resource in nodes
that are earlier than version 7.0, because this will result in a
Naming not found
exception when the application server attempts to perform a lookup on an isolated resource at the cell level.
Implementation class name
Specifies the Java class name of the JDBC driver implementation.
This class is available in the driver file mentioned in the previous class path description.
For example, com.ibm.db2.jcc.DB2XADataSource for distributed and z/OS operating systems.
For example, com.ibm.db2.jdbc.app.UDBXADataSource for iSeries platforms.
Information | Value |
---|---|
Data type | String |