Use this page to create or modify JDBC provider settings
To view this administrative console page, click Resources > JDBC Providers > JDBC_provider.
Configuration tab
Resources such as JDBC Providers, Namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes.
Note that no matter what the scope of a defined resource, the resource's properties only apply at an individual server level. For example, if you define the scope of a data source at the Cell level, all users in that Cell can look up and use that data source, which is unique within that Cell. However, resource property settings are local to each server in the Cell. For example, if you define max connections to 10, then each server in that Cell can have 10 connections.
When resources are created, they are always created into the current scope selected in the panel. To view resources in other scopes, specify a different node or server in the scope selection form.
Data type | String |
Data type | String |
Data type | String |
For example, D:/SQLLIB/java/db2java.zip.
Classpath entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Classpaths contain variable (symbolic) names which you can substitute using a variable map. Check the driver installation notes for the specific required JAR file names.
Data type | String |
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.
Data type | String |
This class is available in the driver file mentioned in the Classpath description above. For example COM.ibm.db2.jdbc.DB2XADataSource.
Data type | String |