You can configure a JDBC provider using the wsadmin tool and scripting.
Procedure
- Identify the parent ID and assign it to the
node variable. The following example uses the node configuration
object as the parent. You can modify this example to use the cell, cluster,
server, or application configuration object as the parent.
Using Jacl:
set node [$AdminConfig getid /Cell:mycell/Node:mynode/]
Using Jython:
node = AdminConfig.getid('/Cell:mycell/Node:mynode/')
print node
Example output:
mynode(cells/mycell/nodes/mynode|node.xml#Node_1)
- Obtain the required attributes.
Using Jacl:
$AdminConfig required JDBCProvider
Using Jython:
print AdminConfig.required('JDBCProvider')
Example output:
Attribute Type
name String
implementationClassName String
- Set up the required attributes and assign
it to the jdbcAttrs variable. You can modify the following example
to setup non-required attributes for JDBC provider.
Using Jacl:
set n1 [list name JDBC1]
set implCN [list implementationClassName myclass]
set jdbcAttrs [list $n1 $implCN]
Example output:
{name {JDBC1}} {implementationClassName {myclass}}
Using Jython:
n1 = ['name', 'JDBC1']
implCN = ['implementationClassName', 'myclass']
jdbcAttrs = [n1, implCN]
print jdbcAttrs
Example output:
[['name', 'JDBC1'], ['implementationClassName', 'myclass']]
- Create a new JDBC provider using node as the
parent.
Using Jacl:
$AdminConfig create JDBCProvider $node $jdbcAttrs
Using Jython:
AdminConfig.create('JDBCProvider', node, jdbcAttrs)
Example output:
JDBC1(cells/mycell/nodes/mynode|resources.xml#JDBCProvider_1)
- Save the configuration changes. See the Saving configuration changes with the wsadmin tool
article for more information.
- In a network deployment environment
only, synchronize the node. See the Synchronizing nodes with the wsadmin tool
article for more information.
What to do next
If you modify the class path or native library path of a JDBC provider:
After saving your changes (and synchronizing the node in a network deployment
environment), 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.