Configure new WAS40 custom properties using scripting
You can use scripting and the wsadmin tool to configure a new WAS40 custom property. 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 to configure a new WAS40 custom properties:
Procedure
- Identify the parent ID:
Use Jacl:
set new40ds [$AdminConfig getid /Cell:mycell/Node:mynode/ JDBCProvider:JDBC1/WAS40DataSource:was4DS1/]
- Use Jython:
new40ds = AdminConfig.getid('/Cell:mycell/Node:mynode/ JDBCProvider:JDBC1/WAS40DataSource:was4DS1/') print new40dsExample output:
was4DS1(cells/mycell/nodes/mynodes|resources.xml$WAS40DataSource_1)
- Get required attributes:
Use Jacl:
set propSet [$AdminConfig showAttribute $newds propertySet]
- Use Jython:
propSet = AdminConfig.showAttribute(newds, 'propertySet') print propSetExample output:
(cells/mycell/nodes/mynode|resources.xml#J2EEResourcePropertySet_9)
- Get required attribute:
Use Jacl:
$AdminConfig required J2EEResourceProperty
- Use Jython:
print AdminConfig.required('J2EEResourceProperty')Example output:
Attribute Type name String
- Set up required attributes:
Use Jacl:
set name [list name RP5] set rpAttrs [list $name]
- Use Jython:
name = ['name', 'RP5'] rpAttrs = [name]
- Create J2EE Resource Property:
Use Jacl:
$AdminConfig create J2EEResourceProperty $propSet $rpAttrs
- Use Jython:
print AdminConfig.create('J2EEResourceProperty', propSet, rpAttrs)Example output:
RP5(cells/mycell/nodes/mynode|resources.xml#J2EEResourceProperty_9)
- Save the configuration changes. See the Saving configuration changes with the wsadmin tool article for more information.
- 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