+

Search Tips   |   Advanced Search

 

Configure new WAS40 data sources using scripting

 

Use scripting to configure a new WAS40 data source. Before starting this task, the wsadmin tool must be running. See the Start the wsadmin scripting client article for more information.

 

Overview

Perform the following steps:

 

Procedure

  1. Identify the parent ID:

      Use Jacl:

      set newjdbc [$AdminConfig getid "/JDBCProvider:Cloudscape JDBC Provider/"]
      

    • Use Jython:

      newjdbc = AdminConfig.getid('/JDBCProvider:Cloudscape JDBC Provider/') print newjdbc
      

    Example output:

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

  2. Get required attributes:

      Use Jacl:

      $AdminConfig required WAS40DataSource
      

    • Use Jython:

      print AdminConfig.required('WAS40DataSource')
      

    Example output:

    Attribute    Type name        String
    

  3. Set up required attributes:

      Use Jacl:

      set name [list name was4DS1] set ds4Attrs [list $name]
      

    • Use Jython:

      name = ['name', 'was4DS1'] ds4Attrs = [name]
      

  4. Create WAS40DataSource:

      Use Jacl:

      set new40ds [$AdminConfig create WAS40DataSource $newjdbc $ds4Attrs]
      

    • Use Jython:

      new40ds = AdminConfig.create('WAS40DataSource', newjdbc, ds4Attrs) print new40ds
      

    Example output:

    was4DS1(cells/mycell/nodes/mynode|resources.xml#WAS40DataSource_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.



Use the AdminConfig object for scripted administration

 

Related Reference


Commands for the AdminConfig object