JDBC provider settings
Modify the settings for a JDBC provider.
From the admin console, click...
Resources > JDBC > JDBC providers > JDBC_provider.
If we use this page to modify the class path or native library path of an existing JDBC provider: After applying and save the new settings, we must restart every application server within the scope of that JDBC provider for the new configuration to work. Otherwise, we receive a data source failure message.
Scope
Scope of the JDBC provider; data sources created with this JDBC provider inherit this scope.
Name
Name of the resource provider.
Information Value Data type String
Description
Text description for the resource provider.
Information Value Data type String
Class path
List of paths or JAR file names which together form the location for the resource provider classes.
For example:
- D:/SQLLIB/java/db2java.zip for distributed operating systems.
- (iSeries) 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 using the ENTER key and must not contain path separator characters (such as ';' or ':'). Class paths contain variable (symbolic) names which we 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
List of paths that forms the location for the resource provider native libraries.
Native path entries are separated using the ENTER key and must not contain path separator characters (such as ';' or ':'). Native paths can contain variable (symbolic) names which we can substitute using a variable map.
Information Value Data type String
Isolate this resource provider
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.
Be aware of the following:
- We cannot isolate a resource provider if we 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 we configure our provider when a native library path is necessary. If we do not require the native library path, delete the value, and we will be able to select the option to isolate the resource provider.
- If we are running a mixed cell environment, the application server will remove any isolated JDBC providers from nodes running at versions earlier than 7.0 if the provider is scoped for a version 7.0 cell, and we have not migrated the provider from an older release. To use isolated resources at the cell level, do not use the resources in nodes 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
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.
(iSeries) For example, com.ibm.db2.jdbc.app.UDBXADataSource for iSeries platforms.
If we modify the implementation class name of the JDBC provider after we have created the provider, we might disconnect the provider from the template used to create it. As a result, data sources created from this JDBC provider do not have an associated template; we must manually configure a working data source through setting custom properties.
Information Value Data type String
Related:
JDBC providers Configure a JDBC provider Data source collection Considerations for isolated resource providers