Configure a JDBC provider using scripting

 

Procedure

  1. Start wsadmin

  2. 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.

    • Jacl:

      set node [$AdminConfig  getid  /Cell:mycell/Node:mynode/]
      

    • Jython

      node = AdminConfig.getid('/Cell:mycell/Node:mynode/')
      print node
      

    Example output:

    mynode(cells/mycell/nodes/mynode|node.xml#Node_1)
    

  3. Identify the required attributes:

    • Jacl:

      $AdminConfig required JDBCProvider
      

    • Jython

      print AdminConfig.required('JDBCProvider')
      

    Example output

    Attribute     Type
    name     String
    implementationClassName   String
    

  4. 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.

    • Jacl:

      set n1 [list name JDBC1]
      set implCN [list implementationClassName myclass]
      set  jdbcAttrs [list  $n1  $implCN]
      

      Example output:

      {name {JDBC1}} {implementationClassName {myclass}}
      

    • Jython

      n1 = ['name', 'JDBC1']
      implCN = ['implementationClassName', 'myclass']
      jdbcAttrs = [n1,  implCN]
      print jdbcAttrs
      

      Example output

      [['name', 'JDBC1'], ['implementationClassName', 'myclass']]
      

  5. Create a new JDBC provider using node as the parent:

    Example output

    JDBC1(cells/mycell/nodes/mynode|resources.xml#JDBCProvider_1) 
    

  6. In a network deployment environment only, synchronize the node.

 

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), 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.


 

See Also


AdminConfig object for scripted administration

 

See Also


Commands for the AdminConfig object