Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Configure resources for the default messaging provider
Configure JMS activation specification properties for durable subscriptions
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 Configure JMS connection factory properties for durable subscriptions.
durableSubscriptions.ser file in the WAS_HOME/temp directory is used by the messaging service to keep track of durable subscriptions for message-driven beans. If you uninstall an application that contains a message-driven bean, this file is used to unsubscribe the durable subscription. If we have to delete the WAS_HOME/temp directory or other files in it, ensure that you preserve this file.
To configure the durable subscription properties to a topic for use by message-driven beans with the default messaging provider, use the admin console to complete the following steps
- Display the default messaging provider. In the navigation pane, click Resources -> JMS -> JMS providers .
- Select the default provider for which to configure activation specification properties.
- 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 Additional properties heading, click Activation specifications. This displays any existing JMS activation specifications for the default messaging provider in the content pane.
- Click the name of the activation specification 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 use to identify durable topic subscriptions created on all connections tht use this activation specification. 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 activation specification. This is a required field when using a durable topic subscription.
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
- The subscription name needed for durable topic subscriptions. Required field when using a durable topic subscription.
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.
What to do nextWhen applications have created durable subscriptions, you can use the admin console to manage the runtime state of those subscriptions, as described in Administer durable subscriptions.
Workload sharing with publish/subscribe messaging