+

Search Tips   |   Advanced Search

 

Create configuration objects using the wsadmin tool

 

You can use scripting and the wsadmin tool to create configuration objects. Before starting this task, the wsadmin tool must be running. See the Start the wsadmin scripting client article for more information.

 

Overview

Perform this task if you want to create an object. To create new objects from the default template, use the create command. Alternatively, you can create objects using an existing object as a template with the createUsingTemplate command. You can only use the createUsingTemplate command for creation of a server with APPLICATION_SERVER type. To create a server with a type other than APPLICATION_SERVER, use the createGenericServer or the createWebServer command.

 

Procedure

  1. Use the AdminConfig object listTemplates command to list available templates:

      Use Jacl:

      $AdminConfig listTemplates JDBCProvider
      

    • Use Jython:

      AdminConfig.listTemplates('JDBCProvider')
      

    where:

    $ Jacl operator for substituting a variable name with its value
    AdminConfig object that represents the WebSphere Application Server configuration
    listTemplates AdminConfig command
    JDBCProvider object type

  2. Assign the ID string that identifies the existing object to which the new object is added. You can add the new object under any valid object type. The following example uses a node as the valid object type:

      Use Jacl:

      set n1 [$AdminConfig getid /Node:mynode/]
      

    • Use Jython:

      n1 =  AdminConfig.getid('/Node:mynode/')
      

    where:

    set Jacl command
    $ Jacl operator for substituting a variable name with its value
    n1 variable name
    AdminConfig object that represents the WebSphere Application Server configuration
    getid AdminConfig command
    Node object type
    mynode host name of the node where the new object is added

  3. Specify the template to use:

      Use Jacl:

      set t1 [$AdminConfig listTemplates JDBCProvider "DB2 JDBC Provider (XA)"]
      

      Use Jython:

      t1 = AdminConfig.listTemplates('JDBCProvider', 'DB2 JDBC Provider (XA)')
      

    where:

    set Jacl command
    $ Jacl operator for substituting a variable name with its value
    t1 variable name
    AdminConfig object that represents the WebSphere Application Server configuration
    listTemplates AdminConfig command
    JDBCProvider object type
    DB2 JDBC Provider (XA) name of the template to use for the new object

    If you supply a string after the name of a type, you get back a list of templates with display names that contain the string you supplied. In this example, the AdminConfig listTemplates command returns the JDBCProvider template whose name matches DB2 JDBC Provider (XA). This example assumes that the variable specified here only holds one template configuration ID. If the environment contains multiple templates with the same string, for example, DB2 JDBC Provider (XA), the variable will hold the configuration IDs of all of the templates. Be sure to identify the specific template to use before you perform the next step, creating an object using a template.

  4. Create the object with the following command:

      Use Jacl:

      $AdminConfig createUsingTemplate JDBCProvider $n1 {{name newdriver}} $tl
      

    • Use Jython:

      AdminConfig.createUsingTemplate('JDBCProvider', n1, [['name', 'newdriver']], t1)
      

    where:

    $ Jacl operator for substituting a variable name with its value
    AdminConfig object that represents the WebSphere Application Server configuration
    createUsingTemplate AdminConfig command
    JDBCProvider object type
    n1 evaluates the ID of the host node that is specified in step number 3
    name attribute of JDBCProvider objects
    newdriver value of the name attribute
    t1 evaluates the ID of the template that is specified in step number 4

    All create commands use a template unless there are no templates to use. If a default template exists, the command creates the object.

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

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