+

Search Tips   |   Advanced Search

Configure new J2C activation specifications

We can configure new Java 2 Connector activation specifications and the wsadmin scripting tool.

Before starting this task, wsadmin.sh must be running. See the topic Starting the wsadmin scripting client topic for more information.

To configure a J2C activation specifications:

  1. Identify the parent ID and assign it to the newra variable.

    • Jacl:

        set newra [$AdminConfig getid /Cell:mycell/Node:mynode/J2CResourceAdapter:RAR1/]

    • Jython:

      newra = AdminConfig.getid('/Cell:mycell/Node:mynode/J2CResourceAdapter:RAR1/')
      print newra

    Example output:

      RAR1(cells/mycell/nodes/mynode|resources.xml#J2CResourceAdapter_1)

  2. There are two ways to configure a new J2C administrative object. Perform one of the following:

    • Use the AdminTask object:

      1. List the administrative object interfaces:

        Jacl:

          $AdminTask listMessageListenerTypes $newra

        Using Jython:

          AdminTask.listMessageListenerTypes(newra)

        Example output:

          javax.jms.MessageListener

      2. Create a J2C administrative object:

        Jacl:

          $AdminTask createJ2CActivationSpec $newra { -name ac1 -jndiName eis/ac1 -messageListenerType javax.jms.MessageListener}

        Jython:

          AdminTask.createJ2CActivationSpec(newra, ['-name', 'ao1', '-jndiName', 'eis/ao1', '-messageListenerType', 'javax.jms.MessageListener'])

    • Use the AdminConfig object:

      1. Jacl:

          $AdminConfig required J2CActivationSpec

        Using Jython:

          print AdminConfig. required('J2CActivationSpec')

        Example output:

        Attribute Type
        activationSpec ActivationSpec@

      2. If the resource adapter is JCA V1.5 and we have multiple activation specifications defined, it is required specified the activation specification attribute. If the resource adapter is JCA V1.5 and we have only one activation specification defined, it will be picked up automatically. If the resource adapter is JCA V1.0, we do not need to specify the activationSpec attribute. Perform the following command to list the activation specifications defined by the resource adapter:

        Jacl:

          $AdminConfig list ActivationSpec $newra

        Using Jython:

          print AdminConfig.list('ActivationSpec', $newra)

      3. Set the administrative object that we need to a variable:

        Using Jacl:

        set ac [$AdminConfig list ActivationSpec $newra]
        set name [list name J2CAC1]
        set jname [list jndiName eis/J2CAC1]
        set j2cacAttrs [list $name $jname $cdcttr]

        Jython:

        ac = AdminConfig.list('ActivationSpec', $newra)
        name = ['name', 'J2CAC1']
        jname = ['jndiName', 'eis/j2cac1']
        j2cacAttrs = [name, jname,cdattr]

      4. If we are specifying the ActivationSpec attribute, also set up the following:

        Jacl:

          set cdcttr [list activationSpec $ac]

        Using Jython:

          cdattr = ['activationSpec', ac]

      5. Create a J2C activation specification object:

        Jacl:

          $AdminConfig create J2CActivationSpec $newra $j2cacAttrs

        Using Jython:

          print AdminConfig.create('J2CActivationSpec', newra,j2cacAttrs)

        Example output:

          J2CAC1(cells/mycell/nodes/mynode|resources.xml#J2CActivationSpec_1)

  3. Save the configuration changes. See the topic Saving configuration changes with wsadmin.sh for more information.

  4. In a network deployment environment only, synchronize the node. See the topic Synchronizing nodes with wsadmin.sh for more information.


Related tasks

  • Use the wsadmin scripting AdminConfig object for scripted administration
  • Use the wsadmin scripting AdminTask object for scripted administration
  • Synchronize nodes using wsdmin.sh
  • Start the wsadmin scripting client
  • Saving configuration changes with wsadmin.sh

  • Commands for the AdminConfig object
  • Commands (AdminTask)