Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Creating a Durable Subscription
 
Creating a Durable Subscription
Before creating a JMS durable subscription, make sure that the following prerequisites are met:
*If the durable subscriber's administered objects are stored in JNDI, then:
*You must have already configured the JNDI provider as a naming directory in My webMethods.
*You must have already configured the JMS administered objects (connection factory and topic) in My webMethods.
For more information, see Adding a JNDI Provider and Binding Administered Objects in JNDI.
*If the client group to which a durable subscriber belongs is basic authentication protected, you will need the client's basic authentication user name and authenticator alias.
*If the client group to which a durable subscriber belongs is SSL-protected, you will need the client's SSL user and authorization DNs. That information is stored in the client's keystore. You will need administrator access (user name and password) to the client keystore file, and the awcert utility to obtain those DNs. For more information, see Keystore File.
Note:
You cannot create non-durable subscribers using My webMethods; however, you can view non-durable subscribers created programmatically (that is, created outside of the Broker user interface).
*To create a durable subscription
1. In My webMethods: Messaging > Broker Server s > Clients.
2. On the Search tab, enter the Server Name and Broker Name to which the durable subscriber will belong and click Go.
3. Click Add Durable Subscription.
4. To create the durable subscriber from JMS objects bound to a JNDI namespace, click the From Naming Directory tab and complete the following fields:
In this field...
Select or type...
Durable Subscriber Name
A name for this durable subscriber.
On the Clients panel, the Client ID is the durable subscriber name prefixed by its connection client ID and two pound sign (##) delimiters.
Provider Name
The JNDI provider to which the administered objects for this durable subscriber are bound.
Topic Lookup Name
A JNDI lookup name for the durable subscription topic. Use the following guidelines:
*The name cannot exceed 255 bytes.
*The name must begin with an alphabetic character, followed by any combination of alphanumeric characters and underscores (_).
Connection Factory Lookup Name
The JNDI lookup name for the connection factory.
Broker Server
The name of the controlling Broker Server for the durable subscriber (read-only).
Broker
The name of the controlling Broker for the durable subscription (read-only).
Selector String (SQL92 Syntax)
Optional. A message selector to filter subscriptions.
For information about using JMS message selectors, see the webMethods Broker Messaging Programmer’s Guide.
No local
Optional. If you select this option, no subscriptions originating from the local machine will be received.
User Name or SSL DN
The basic authentication user name or the SSL DN of the user(s) receiving the durable subscription.
Provide this information only if the client group to which the durable subscribers belong is basic authentication/SSL-protected by a user ACL.
Alias Name or SSL Issuer DN
The basic authenticator alias or the SSL DN of the certification authority for the durable subscribers.
Provide this information only if the client group to which the durable subscribers belong is basic authentication/SSSL-protected by an authenticator or authorization (certificate issuer) ACL.
5. If you are creating the JMS administered objects for the durable subscription programmatically (that is, you are not using JNDI), click the At Broker tab and complete the following fields:
In this field...
Select or type...
Durable Subscriber Name
A name for the durable subscriber.
On the Clients panel, the Client ID is the durable subscriber name prefixed by its connection client ID and two pound sign (##) delimiters.
Connection Client ID
A unique client identifier.
Broker Server
The controlling Broker Server for the durable subscription.
Broker
The controlling Broker for the durable subscription.
Client Group
The client group of the durable subscriber(s).
Document Type Name
The document type that the durable subscription contains.
Application Name
Optional. A name that is meaningful to your application. By default, the name "JMS" is used.
Shared State
Optional. Sharing a client state allows multiple clients, each using its own session, to process documents from a single client queue in parallel on a first-come, first-served basis.
Select whether multiple connections can share the same connection client ID.
Shared State Order
Optional. The ordering of documents received on a shared state client:
*To receive documents ordered by publisher, select publisher.
*To receive documents in any order, select none.
Note:
You can set shared state ordering only after you select the check box next to Shared State. If you do not select the check box, shared state ordering will default to publisher.
Selector String (SQL92 Syntax)
Optional. The message selector that will be used to filter subscriptions.
For information about using JMS message selectors, see the webMethods Broker Messaging Programmer’s Guide.
No local
Optional. If you select this option, no subscriptions originating from the local machine will be received.
User Name or SSL DN
The basic authentication user name or the SSL DN of the user(s) receiving the durable subscription.
Provide this information only if the client group to which the durable subscribers belong is basic authentication/SSL-protected by a user ACL.
Alias Name or SSL Issuer DN
The basic authenticator alias or the SSL DN of the certification authority for the durable subscribers.
Provide this information only if the client group to which the durable subscribers belong is basic authentication/SSL-protected by an authenticator or authorization (certificate issuer) ACL.