JDBC provider settings
Use this page to create or modify JDBC provider settings
To view this administrative console page, click Resources > JDBC Providers > JDBC_provider.
Configuration tab
- Scope
- Specifies the level to which this resource definition is visible
-- the cell, node, or server level.
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.
- Cell
- The most general scope. Resources defined at the Cell scope are visible from all Nodes and servers, unless they are overridden. To view resources defined in the cell scope, do not specify a server or a node name in the scope selection form.
- Node
- The default scope for most resource types. Resources defined at the Node scope override any duplicates defined at the Cell scope and are visible to all servers on the same node, unless they are overridden at a server scope on that node. To view resources defined in a node scope, do not specify a server, but select a node name in the scope selection form.
- Server
- The most specific scope for defining resources. Resources defined at the Server scope override any duplicate resource definitions defined at the Cell scope or parent Node scope and are visible only to a specific server. To view resources defined in a server scope, specify a server name as well as a node name in the scope selection form.
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 - Name
- Specifies the name of the resource provider.
Data type String - Description
- Specifies a text description for the resource provider.
Data type String - Classpath
- Specifies a list of paths or JAR file names which together form
the location for the resource provider classes.
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 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.
Data type String - Implementation Classname
- Specifies the Java class name of the JDBC driver implementation.
This class is available in the driver file mentioned in the Classpath description above. For example COM.ibm.db2.jdbc.DB2XADataSource.
Data type String
JDBC providers
Creating and configuring a JDBC provider using the administrative console
Administrative console buttons
Administrative console page features
Data Sources (V4)
Data Source collection