Set new WAS40 custom properties using scripting

Use scripting and wsadmin to configure a new WAS40 custom property.

Before starting this task, wsadmin must be running. See the Start wsadmin article for more information.

Perform the following steps to configure a new WAS40 custom properties:

 

1. Identify the parent ID:
   • Jacl...

     set new40ds [$AdminConfig getid /Cell:mycell/Node:mynode/ JDBCProvider:JDBC1/WAS40DataSource:was4DS1/]

   • Jython...

     new40ds = AdminConfig.getid('/Cell:mycell/Node:mynode/ JDBCProvider:JDBC1/WAS40DataSource:was4DS1/') print new40ds

   For example...

   was4DS1(cells/mycell/nodes/mynodes|resources.xml$WAS40DataSource_1)

2. Get required attributes:
   • Jacl...

     set propSet [$AdminConfig showAttribute $newds propertySet]

   • Jython...

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

   For example...

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

3. Get required attribute:
   • Jacl...

     $AdminConfig required J2EEResourceProperty

   • Jython...

     print AdminConfig.required('J2EEResourceProperty')

   For example...

   Attribute Type name String

4. Set up required attributes:
   • Jacl...

     set name [list name RP5]
     set rpAttrs [list $name]

   • Jython...

     name = ['name', 'RP5']
     rpAttrs = [name]

5. Create J2EE Resource Property:
   • Jacl...

     $AdminConfig create J2EEResourceProperty $propSet $rpAttrs

   • Jython...

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

   For example...

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

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

7. In a network deployment environment only, synchronize the node. See the Synchronizing nodes with wsadmin article for more information.

 

Related tasks

Use the AdminConfig object for scripted administration

 

Related

Commands for the AdminConfig object