J2C Activation Specifications collection

This page contains a list of J2C activation specifications for a resource adapter configuration and is used to create new J2C activation specifications, to select J2C activation specifications for configuration changes, or to delete J2C activation specifications.

Activation specification definitions and classes are provided by a resource adapter when it is installed. Using this information, the administrator can create and configure J2C activation specifications with JNDI names that are then available for applications to use. The resource adapter uses a J2C activation specification to configure a specific endpoint instance. Each application configuring one or more endpoints must specify the resource adapter that sends messages to the endpoint. The application must use the activation specification to provide the configuration properties related to the processing of the inbound messages. The following guidelines show which scenarios use activation specifications or listener ports:

• If you are using J2EE 1.2 and EJB 1.1 with WebSphere Application Server v4, MDBs are not used so you do not need listener ports or activation specifications. WebSphere Application Server v4 uses message beans, but these are not MDbs or EJBs.

• If you are using J2EE 1.3 and EJB 2.0 with WebSphere Application Server v5, use listener ports. The MDBs are JMS MDBs that implement MessageListener, and there is no JCA support. WebSphere Application Server v5 uses listener ;ports to associate MDB classes with their JMS destinations.

• If you are using J2EE 1.4 and EJB 2.1 with WebSphere Application Server v6, use activation specifications. A connector MDB 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 MDBs from EJB 2.0 to EJB 2.1.

• If you are using J2EE 1.4 and EJB 2.1 with WebSphere Application Server v6, the decision depends on whether your 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, your MDB is a JMS MDB that is implemented as a connector MDB, 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 MDB in the same way as you would configure an EJB 2.0 MDB, which in WebSphere Application Server is to use a listener port.

You can access this administrative console page in one of two ways:

• Resources > Resource adapters > Resource adapters > resource_adapter > J2C Activation Specifications.

• Resources > Resource adapters > J2C Activation Specifications.

Configuration tab

Name

Specifies the display name of the J2C activation specification instance.

A string with no spaces meant to be a meaningful text identifier for the J2C activation specification.

Data type

String

JNDI name

Specifies the Java Naming and Directory Interface (JNDI) name for the J2C activation specification instance.

Data type

String

Scope

Scope of the resource adapter that supports this activation specification. Only applications that are installed within this scope can use this activation specification.

Provider

Specifies the resource adapter that encapsulates the appropriate classes for this activation specification.

Description

A free-form text string to describe the J2C activation specification instance.

Data type

String

Message Listener Type

The Message Listener Type that is used by this activation specification.

The list of available classes is provided by the resource adapter.

Data type

String

Sub-topics

Related tasks

Related Reference

Reference topic