Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing Destinations | Binding Destinations to JNDI
 
Binding Destinations to JNDI
This procedure describes how to bind queues and topics in JNDI. Follow these instructions only if you are configuring destinations administratively.
*To bind a destination to JNDI
1. In My webMethods: Messaging > Naming Directories > Destinations.
2. In the Destinations List, click Add.
3. Complete the following fields:
In this field...
Select or type...
Lookup Name
The name of the JNDI directory in which to bind this destination. You will use the lookup name later to create this destination object.
Provider
The name of the JNDI provider to use with this destination.
Destination Name
Queues:
A fully qualified name (for example, /territory/broker/queuename) or a partial name. Use the following guidelines:
*The name cannot exceed 255 bytes.
*The name must begin with an alphabet, followed by any combination of alphanumeric characters and underscores (_).
*If you use a naming prefix, separate it from the queue name with a double colon. (::).
Note:
Space character is allowed only when using the JMSAdmin command-line tool.
Topics:
A valid topic name or wild card (for example, *). Use the following guidelines:
*The name cannot exceed 255 bytes.
*The name must begin with an alphabet, followed by any combination of alphanumeric characters and underscores (_).
*If you use a naming prefix, separate it from the topic name with a double colon. (::).
Note:
Wild card character (*) is allowed only when using the JMSAdmin command-line tool.
Destination Type
Whether the destination is a queue or topic.
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 Ordering
Optional. The ordering of documents received on a shared state client:
*To receive documents in order from a publisher, set to publisher.
*To receive documents in any order, set to 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 defaults to publisher.
4. Click OK.