Set a J2C activation specification

Use this task to configure a J2EE Connector (J2C) activation specification used to deploy message-driven beans with an external resource adapter.

Use this task to use a message-driven bean as a listener on a Java Connector Architecture (JCA) 1.5 resource adapter other than the default messaging JMS provider.

You can create or modify a J2C activation spec under an installed resource adapter at the cell, node, or server scope. We can select the message listener type from those provided by the given resource adapter. Set a J2C activation spec offers two distinct advantages:

• We can share the activation spec configuration information among multiple message-driven beans across multiple applications.

• We can update the configuration properties without having to redeploy the application.

The following guidelines show which scenarios use activation specifications or listener ports:

• If using J2EE 1.2 and EJB 1.1 with WAS V4, message-driven beans are not used so you do not need listener ports or activation specifications. WAS Version 4 uses message beans, but these are not message-driven beans or enterprise beans.

• If using J2EE 1.3 and EJB 2.0 with WAS V5, use listener ports. The message-driven beans are JMS message-driven beans that implement MessageListener, and there is no JCA support. WAS Version 5 uses listener ports to associate message-driven bean classes with their JMS destinations.

• If using J2EE 1.4 and EJB 2.1 with WAS V6, use activation specifications. A connector message-driven bean uses JCA to access its resources, so the connector must therefore be configured with an activation specification. This is for new bean development, and does not affect the conversion of message-driven beans from EJB 2.0 to EJB 2.1.

• If using J2EE 1.4 and EJB 2.1 with WAS V6, the decision depends on whether the JMS provider API is implemented with JCA. In J2EE 1.4, the JMS 1.1 API can now be implemented with the JCA 1.5 API. If so, the message-driven bean is a JMS message-driven bean that is implemented as a connector message-driven bean, and must therefore be configured with an activation specification. If not, this is the same JMS situation as for J2EE 1.3, and configure this EJB 2.1 message-driven bean in the same way as you would configure an EJB 2.0 message-driven bean, which in WAS is to use a listener port.

To configure a J2C activation spec for an external resource adapter, use the admin console to complete the following steps. This task contains an optional step for you to create a new activation specification.

 

1. Display the external resource adapter. In the navigation pane, click Resources > Resource Adapters > adapter_name. This displays in the content pane a table of properties for the external resource adapter, including links to the types of J2C resources that it provides.

2. Change the Scope setting to the scope level at which the activation spec is to be visible to applications, according to the needs.

3. In the content pane, under the Activation specifications heading, click J2C Activation Specifications.

   This lists any existing J2C activation specifications for the external resource adapter in the content pane.

4. Display the properties of the J2C activation specification.

   To display an existing J2C activation specification, click one of the names listed.Alternatively, to create a new J2C activation specification, click New, then specify the following required properties:

   Name

   Type the name by which the activation spec is known for administrative purposes. The JNDI name is automatically generated based on the value for the Name property.

   Message listener type

   Select the message listener type that this activation specification instance should support. This list is based on the deployment descriptor of the external resource adapter.

   Depending on the external resource adapter, there can be additional required properties that supply. To provide values for these properties, click Custom properties. When creating a new activation specification, we might have to click Apply before this custom property selection is available.

5. Specify properties for the activation specification, according to the needs .

6. Click OK.

7. Save the changes to the master configuration.

J2C Activation Specifications collection

 

Related concepts

J2C activation spec configuration and use

 

Related tasks

Administer activation specifications and listener ports for message-driven beans