Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with a third-party or (deprecated) V5 default messaging provider > Manage messaging with a third-party JCA 1.5-compliant messaging provider

Configure an activation specification for a third-party JCA resource adapter

We can configure an activation specification used to deploy message-driven beans with a Java™ Connector Architecture (JCA), also called J2EE Connector (J2C), resource adapter that is not included as part of the WAS.

For guidance about when to configure your message-driven beans to work with listener ports rather than activation specifications. see Message-driven beans, activation specifications, and listener ports.

This task assumes that we have installed the resource adapter for the third-party provider, as described in Install a resource adapter archive.

Use this task to use a message-driven bean as a listener on a JCA resource adapter other than the default messaging provider or the WebSphere MQ messaging provider.

Procedure

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

3. Optional: Change the Scope setting to the scope level at which the activation specification is to be visible to applications, according to your needs.

4. In the content pane, under the Activation specifications heading, click J2C Activation Specifications. This lists any existing activation specifications for the resource adapter.
5. Display the properties of the activation specification.

   To display an existing activation specification, click one of the names listed.

   Alternatively, to create a new activation specification, click New, then specify the following required properties:

   Name
   Type the name by which the activation specification 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 resource adapter.

   Depending on the 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, you might have to click Apply before this custom property selection is available.

6. Specify properties for the activation specification, according to your needs.

7. Click OK.

8. Save your changes to the master configuration.

Related

J2C Activation Specifications collection
J2C activation specification configuration and use
Configure an activation specification for the default messaging provider
Manage messaging with a third-party JCA 1.5-compliant messaging provider
Configure an activation specification for the WebSphere MQ messaging provider

+

Search Tips   |   Advanced Search