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 new WAS40 data sources using wsadmin.sh

Use scripting to configure a new WAS40 data source. See the Start the wsadmin scripting client using wsadmin.sh article for more information.

Perform the following steps:

Procedure

1. 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
   

   Example output:

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

2. Get required attributes:

   ### Jacl

   $AdminConfig required WAS40DataSource
   

   ### Jython

   print AdminConfig.required('WAS40DataSource')
   

   Example output:

   Attribute    Type
   name    String 

3. Set up required attributes:

   ### Jacl

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

   ### Jython

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

4. Create WAS40DataSource:

   ### Jacl

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

   ### 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.

6. Synchronize the node.

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

Related

Commands for the AdminConfig object using wsadmin.sh

+

Search Tips   |   Advanced Search