Configure JMS connection factory properties for durable subscriptions

Configure durable subscription properties of JMS connection factories for use by enterprise beans with the default messaging provider.

To enable applications to create durable subscriptions to JMS topics with the default messaging provider, we can set a number of properties on JMS connection factories.

If applications use message-driven beans to create durable subscriptions, we should set the properties on the JMS activation specification used by the message-driven beans, as described in Configure JMS activation specifications for durable subscriptions, instead of as described in this topic.

This topic describes the setting of properties on a unified JMS connection factory. We can also set the same properties on a JMS topic connection factory instead.

To configure the durable subscription properties to a topic for use by enterprise beans with the default messaging provider, use the administrative console to complete the following steps:

Tasks

1. Display the default messaging provider. In the navigation pane, click...

           Resources -> JMS -> JMS providers.

2. Select the default provider for which we want to configure connection factory properties.

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

4. In the content pane, under the Additional properties heading, click Connection factories. This displays any existing JMS connection factories for the default messaging provider in the content pane.

5. Click the name of the connection factory we want to configure. This displays the properties for the connection factory in the content pane.

6. Specify the following properties for the connection factory:

   Client identifier

   This is the JMS client identifier that applications use to identify durable topic subscriptions created on all connections that use this connection factory. For more information about client identifiers, see section 4.3.2 of the JMS 1.1 specification.

   Subscription home

   The name of the messaging engine used to store messages delivered to subscriptions for objects created from this JMS connection factory.

   This identifies the messaging engine where durable subscriptions are localized on the service integration bus. Administrators can manage the runtime state of durable subscriptions through publication points for that messaging engine.

7. Click OK.

8. Save changes to the master configuration.

What to do next

When applications have created durable subscriptions, we can use the administrative console to manage the runtime state of those subscriptions, as described in Administer durable subscriptions.

The JMS connection factory has some other advanced properties that we can configure to change the behavior for durable subscriptions. We should not usually need to change these properties from their default values.

Read ahead

This controls read ahead optimization during message delivery. This defines whether the provider can stream messages to durable subscribers ahead of their requests (to provide a performance enhancement).

Share subscriptions

This controls whether durable subscriptions can be accessed simultaneously by several subscribers.

To control read ahead optimization during message delivery for individual topics, we can set the Read ahead property on the topics.

Subtopics

• Configure shared durable subscriptions for a connection factory
  Configure the Share durable subscriptions option; an attribute of the connection factory that clients use to connect to the bus.

Related:

Workload sharing with publish/subscribe messaging