Configure shared non-durable subscriptions for an activation specification

Configure the Share non-durable subscriptions option; an attribute of the JMS activation specifications that message-driven beans use with the default messaging provider.

The Share non-durable subscriptions option controls whether subscriptions are shared between subscribers in a cluster. To set this option, use the administrative console to complete the following steps.

Tasks

1. In the navigation pane, click...

           Resources -> JMS -> JMS providers.

2. Select the default provider for which we want to configure activation specification properties.

3. Optional: Change the Scope check box to set the level at which the connection factory is visible, according to our needs.

4. In the content pane, under Additional Properties, click Activation specifications.

5. Click the name of the activation specification we want to configure. The properties for the activation specification are displayed in the content pane.

6. Under General Properties, in the Subscription Durability section, set the Share non-durable subscriptions property. Select one of the following options from the list:

   In cluster

   Clients connected to the bus in a cluster member can use the same client identifier and subscription name, and can retrieve messages from the durable subscription.

   Always shared

   All clients, regardless of where they are connected to the bus, can use the same client identifier and subscription name, and can retrieve messages from the durable subscription.

   Never shared

   Clients cannot use the same client identifier and subscription name as an existing session.

   See the administrative console help for information about the other fields on this page.

7. Set the Subscription home for shared non-durable subscription. The name of the messaging engine used to store messages delivered to non-durable subscriptions for objects created from the JMS activation specification. This is a required field when using a non-durable topic subscription.

   Administrators can manage the runtime state of non-durable subscriptions through publication points for this messaging engine.

   For shared non-durable subscription, the messaging engine name value under the Subscription home field is treated as the target messaging engine. So any messaging engine name that is defined under the Target field is ignored.

8. Click OK.

9. Save changes to the master configuration.