Set new WAS40 data sources using scripting
Use scripting to configure a new WAS40 data source.
Before starting this task, wsadmin must be running. See the Start wsadmin article for more information.
Perform the following steps:
- Identify the parent ID:
- Jacl...
set newjdbc [$AdminConfig getid "/JDBCProvider:Apache Derby JDBC Provider/"]- Jython...
newjdbc = AdminConfig.getid('/JDBCProvider:Apache Derby JDBC Provider/')
print newjdbc
For example...
JDBC1(cells/mycell/nodes/mynode|resources.xml$JDBCProvider_1)- Get required attributes:
- Jacl...
$AdminConfig required WAS40DataSource- Jython...
print AdminConfig.required('WAS40DataSource')
For example...
Attribute Type name String- Set up required attributes:
- Jacl...
set name [list name was4DS1]
set ds4Attrs [list $name]- Jython...
name = ['name', 'was4DS1'] ds4Attrs = [name]
- Create WAS40DataSource:
- Jacl...
set new40ds [$AdminConfig create WAS40DataSource $newjdbc $ds4Attrs]- Jython...
new40ds = AdminConfig.create('WAS40DataSource', newjdbc, ds4Attrs) print new40ds
For example...
was4DS1(cells/mycell/nodes/mynode|resources.xml#WAS40DataSource_1)- Save the configuration changes. See the Saving configuration changes with wsadmin article for more information.
- 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