WAS v8.5 > Script the application serving environment (wsadmin) > Welcome to scripting for Messaging resources > Configure messaging with wsadmin scripting

Configure new topics using scripting

We can configure new topics using wsadmin and scripting.

Before starting this task, wsadmin must be running. To configure a new WebSphere queue:

In the following examples, code blocks beginning with wsadmin> show code that is entered by the user. Lines that do not begin with wsadmin> show code that has been returned by the console.

  1. Identify the parent ID and assign in to a variable. In this example the variable is named v5jmsp.

    • Jacl:

        wsadmin>set v5jmsp [$AdminConfig getid "/Cell:mycell/Node:mynode/JMSProvider:WebSphere JMS Provider/"]
    • Using Jython:
      wsadmin>v5jmsp = AdminConfig.getid("/Cell:mycell/Node:myNode/JMSProvider:WebSphere JMS Provider/") 
      wsadmin>print v5jmsp

    Example output:

      "WebSphere JMS Provider(cells/mycell/nodes/mynode|resources.xml#builtin_jmsprovider)"
  2. Get required attributes:

    • Jacl:

        wsadmin>$AdminConfig required WASQueue
    • Using Jython:

        wsadmin>print AdminConfig.required('WASQueue')

    Example output:

    Attribute       Type
    name       String
    jndiName    String

  3. Set up required attributes:

    • Jacl:
      wsadmin>set name [list name WASQ1]
      wsadmin>set jndi [list jndiName jms/WASQ1]
      wsadmin>set wqAttrs [list $name $jndi]

      Example output:

        {name WASQ1} {jndiName jms/WASQ1}
    • Using Jython:
      wsadmin>name = ['name', 'WASQ1']
      wsadmin>jndi = ['jndiName', 'jms/WASQ1']
      wsadmin>wqAttrs = [name, jndi]
      wsadmin>print wqAttrs

      Example output:

        [[name, WASQ1], [jndiName, jms/WASQ1]]

  4. Create the queue:

    • Jacl:

        wsadmin>$AdminConfig create WASQueue $v5jmsp $wqAttrs
    • Using Jython:

        wsadmin>print AdminConfig.create('WASQueue', v5jmsp, wqAttrs)

    Example output:

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

  5. Save the configuration changes.


Related


Use the wsadmin scripting AdminConfig object for scripted administration
Start the wsadmin scripting client using wsadmin.sh
Save configuration changes with wsadmin


Reference:

Commands for the AdminConfig object using wsadmin.sh


+

Search Tips   |   Advanced Search