Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Scripting for data access resources > Configure data access with wsadmin scripting


Configure custom properties for J2C resource adapters using wsadmin

We can configure custom properties for Java 2 Connector resource adapters using the wsadmin tool. See the topic Starting the wsadmin scripting client article for more information.

Configure a new custom property for a J2C resource adapters:


Procedure

  1. Identify the parent ID and assign it to the newra variable.

      ### Jacl

      set newra [$AdminConfig getid /Cell:mycell/Node:mynode/J2CResourceAdapter:RAR1/]
      

      ### Jython

      newra = AdminConfig.getid('/Cell:mycell/Node:mynode/J2CResourceAdapter:RAR1/')
      print newra
      

    Example output:

    RAR1(cells/mycell/nodes/mynode|resources.xml#J2CResourceAdapter_1)
    

  2. Get the J2EE resource property set:

      ### Jacl

      set propSet [$AdminConfig showAttribute $newra propertySet]
      

      ### Jython

      propSet = AdminConfig.showAttribute(newra, 'propertySet')
      print propSet
      

    Example output:

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

  3. Identify the required attributes:

      ### Jacl

      $AdminConfig required J2EEResourceProperty
      

      ### Jython

      print AdminConfig.required('J2EEResourceProperty')
      

    Example output:

    Attribute     Type
    name         String 

  4. Set up the required attributes:

      ### Jacl

      set name [list name RP4]
      set rpAttrs [list $name]
      

      ### Jython

      name = ['name', 'RP4']
      rpAttrs = [name]
      

  5. Create a J2EE resource property:

      ### Jacl

      $AdminConfig create J2EEResourceProperty $propSet $rpAttrs
      

      ### Jython

      print AdminConfig.create('J2EEResourceProperty', propSet, rpAttrs)
      

    Example output:

    RP4(cells/mycell/nodes/mynode|resources.xml#J2EEResourceProperty_8)
    

  6. Save the configuration changes. See the topic Saving configuration changes with wsadmin.sh for more information.

  7. Synchronize the node. See the topic Synchronizing nodes with the wsadmin tool for more information.


Use the wsadmin scripting AdminConfig object for scripted administration
Synchronize nodes using wsadmin.sh
Start the wsadmin scripting client using wsadmin.sh
Saving configuration changes with wsadmin.sh


Related


Commands for the AdminConfig object using wsadmin.sh

+

Search Tips   |   Advanced Search