Configure new J2C activation specifications using wsadmin.sh

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

See the topic about starting the wsadmin scripting client for more information.

Perform the following steps to configure a J2C activation specifications:

Tasks

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:

        Use Jacl:

        $AdminTask listMessageListenerTypes $newra
        

        Use Jython:

        AdminTask.listMessageListenerTypes(newra)
        

        Example output:

        javax.jms.MessageListener
        

     2. Create a J2C administrative object:

        Use Jacl:

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

        Use Jython:

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

   • Use the AdminConfig object:
     1. Jacl:

        $AdminConfig required J2CActivationSpec
        

        Use Jython:

        print AdminConfig.required('J2CActivationSpec')
        

        Example output:

        Attribute Type
        activationSpec ActivationSpec@
        

     2. If our resource adapter is JCA V1.5 and we have multiple activation specifications defined, it is required specified the activation specification attribute. If our resource adapter is JCA V1.5 and we have only one activation specification defined, it will be picked up automatically. If our 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:

        Use Jacl:

        $AdminConfig list ActivationSpec $newra
        

        Use Jython:

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

     3. Set the administrative object needed to a variable:

        Use Jacl:

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

        Use 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:

        Use Jacl:

        set cdcttr [list activationSpec $ac]
        

        Use Jython:

        cdattr = ['activationSpec', ac]
        

     5. Create a J2C activation specification object:

        Use Jacl:

        $AdminConfig create J2CActivationSpec $newra $j2cacAttrs 
        

        Use 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 the wsadmin tool for more information.
4. In a network deployment environment only, synchronize the node. See the topic Synchronize nodes with the wsadmin tool for more information.

wsadmin AdminConfig

wsadmin AdminTask

Synchronize nodes

Start the wsadmin scripting client

Save wsadmin configuration changes

Commands for the AdminConfig object

Commands for the AdminTask object