Use this task to configure durable subscription properties of JMS
connection factories for use by enterprise beans with the default messaging
provider.
Why and when to perform this task
To enable applications to create durable subscriptions to JMS
topics with the default messaging provider, you can set a number of properties
on JMS connection factories.
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 Configuring JMS activation specifications
for durable subscriptions, instead of using the task described in this
topic.
This topic describes the setting of properties on a unified JMS
connection factory. You 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:
Steps for this task
- 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 Connection factories label, click JMS
connection factory. This displays any existing
JMS connection factories for the default messaging provider in the content
pane.
- Click the name of the connection factory you want to configure. This displays the properties for the connection factory in the
content pane.
- Specify the following properties for the connection factory:
- Client identifier
- This is the JMS client identifier that applications need to identify durable
topic subscriptions created on all connections using this connection factory.
For more information about client identifiers, see section 4.3.2 of the JMS
1.1 specification.
- Durable subscription home
- The name of the messaging engine used to store messages delivered to durable 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.
- 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.
The
JMS connection factory has some other advanced properties that you can configure
to change the behavior for durable subscriptions. You should not normally
need to change these properties from there defaults.
- Read ahead
- This controls read ahead optimization during message delivery. This defines
whether or not the provider can stream messages to durable subscribers ahead
of their requests (to provide a performance enhancement).
- Share durable subscriptions
- This controls whether or not durable subscriptions can be accessed simultaneously
by several subscribers.
If you want to control read ahead optimization during
message delivery for individual topics, you can set the Read ahead property on the topics.