JDBC provider settings
To modify the settings for a JDBC provider.
To view this admin console page, 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 you apply and save the new settings, restart every appserver within the scope of that JDBC provider for the new configuration to work. Otherwise, you receive a data source failure message.
- Scope
Scope of the JDBC provider; data sources that are created with this JDBC provider inherit this scope.
- Name
Name of the resource provider.
Data type String
- Description
Specifies a text description for the resource provider.
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.
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 we can substitute using a variable map. Check the driver installation notes for the specific required JAR file names.
Data type String
- Native Library Path
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 we can substitute using a variable map.
Data type String
- Isolate this resource provider
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.
Avoid trouble: 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 you configure the provider when a native library path is necessary. If we 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 running a mixed cell environment, the appserver 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. 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 appserver 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 class path description above.
For example, com.ibm.db2.jcc.DB2XADataSource for distributed and z/OS operating systems.
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; manually configure a working data source through setting custom properties.
Data type String
Related concepts
JDBC providers
Related tasks
Set a JDBC provider
Related
Data source (WAS V4) collection
Data source collection
Considerations for isolated resource providers