WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring a JDBC provider using scripting

Before you begin

Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client article for more information.

Why and when to perform this task

Perform the following steps to configure a new JDBC provider:

Steps for this task

  1. 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)
  2. Identify the required attributes:
    • Using Jacl:

      $AdminConfig required JDBCProvider
    • Using Jython:
      print AdminConfig.required('JDBCProvider')
    Example output:
    Attribute     Type
    name     String
    implementationClassName   String
  3. 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']]
  4. 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) 
  5. Save the configuration changes. See the Saving configuration changes with the wsadmin tool article for more information.
  6. 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

Attention: 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.



Related concepts
AdminConfig object for scripted administration

Related reference
Commands for the AdminConfig object

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/txml_configjdbc.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)