File name: udat_manjdbcprodet.htmlJDBC provider settings
Use this page to modify the settings for a JDBC provider.
To view this administrative console page, click .
Important: If you 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, you must restart every application server
within the scope of that JDBC provider for the new configuration to
work. Otherwise, you receive a data source failure message.
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.
For example:
- QIBM/ProdData/Java400/ext/db2_classes.jar for iSeries platforms.
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.
Avoid trouble: Be aware of the following:
- 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.
gotcha
Implementation class name
Specifies the 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.jdbc.app.UDBXADataSource for iSeries platforms.
Note: If you modify the implementation class name of the JDBC provider
after you have created the provider, you 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; you must
manually configure a working data source through setting custom properties.
Information |
Value |
Data type |
String |
|
