Use this task to configure durable subscription properties of JMS
activation specifications for use by message-driven beans with the default
messaging provider.
To enable a message-driven bean (MDB) application to create durable
subscriptions on JMS topics with the default messaging provider, you set a
number of properties on the JMS activation specification used by the application.
If
applications use message-driven beans to create durable subscriptions, you
should set the properties on the JMS activation specification used by the
message-driven beans, as described in this topic. Otherwise, for enterprise
beans to create durable subscriptions, you should set the properties on the
JMS connection factory as described in Configuring JMS connection factory properties for durable subscriptions.
To configure the durable subscription properties
to a topic for use by message-driven beans with the default messaging provider,
use the administrative console to complete the following steps
- Display the default messaging provider. In the navigation
pane, click . This
displays in the content pane a table of properties for the default messaging
provider, including links to the types of JMS resources that it provides.
- Optional: Change the Scope check
box to set the level at which the connection factory is to be visible, according
to your needs.
- In the content pane, under the Activation specifications heading,
click JMS activation specification. This
displays any existing JMS activation specifications for the default messaging
provider in the content pane.
- Click the name of the activation specification you want to configure. This displays the properties for the activation specification
in the content pane.
- Specify the following properties for the activation specification:.
- Client identifier
- This is the JMS client identifier that applications need to identify durable
topic subscriptions created on all connections using this activation specification.
For more information about client identifiers, see section 4.3.2 of the JMS
1.1 specification.
- Durable subscription home
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.
- Subscription durability
- To be able to create durable subscriptions, set this property to Durable.
- Subscription name
Each JMS durable subscription is identified by a subscription name (specified
on this property). A JMS connection also has an associated client identifier
(specified on the Client identifier property), which is used to associate
a connection and its objects with the list of messages (on the durable subscription)
that is maintained by the JMS provider for the client.
This subscription
name must be unique within a given client identifier.
- Specify the properties for the activation specification, according
to your needs.
- Click OK.
- Save your changes to the master configuration.
When applications have created durable subscriptions, you can use
the administrative console to manage the runtime state of those subscriptions,
as described in
Administering durable subscriptions.