Broker 10.15 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | JMSAdmin Command Reference | JMSAdmin Command Descriptions | Bind Topic
 
Bind Topic
Adds a topic definition into a JNDI context.
Syntax
bind topic lookup-name with { topicName | tn }=document-type-name
 
[ deadLetterOnly={ true | false } ]
[ localOnly={ true | false } ]
[ priorityOrdering={ true | false } ]
[ event type=event-type-name ]
[ { sharedState | ss }={ true | false } ]
[ { sharedStateOrdering | sso }={ none | publisher } ]
The command syntax has these parts:
Part
Description
lookup-name
Required. The name used to look up this topic in the JNDI directory.
topicName
Required. The name of the topic (destination) through which publishers and subscribers will exchange messages. The name must meet the following criteria:
*The first character cannot be a pound sign (#).
*The name cannot contain the at sign (@), forward slash ( /), or colon (:). However, topic names can contain colons when using event type scopes (for example, MyTopics::Topic1 is allowed; MyTopics:Topic1 is not).
*Each name segment cannot exceed 255 bytes.
deadLetterOnly
Optional.If you set this option to true, only dead letter subscriptions will be received. The default value is false.
localOnly
Optional. If you set this option to true, only messages originating (published) from the local machine will be received. The default value is false.
priorityOrdering
Optional.Whether or not the subscribers' queues order messages by priority. The default value is true.
eventType
Optional. If you specify an event-type-name, the supplied name will be used for the document name on the Broker. The name must meet the following criteria:
*The first character cannot be a pound sign (#).
*The name cannot contain the at sign (@), forward slash ( /), or colon (:).
*Each name segment cannot exceed 255 bytes.
The event-type-name can be the same as the lookup-name and the topicName; the default eventType is the same as the topicName.
sharedState
Optional. Whether to allow multiple connections to share the same Broker client for the subscription. The default value is false.
If sharedState is set to true, webMethods Broker used as a JMS provider creates Broker clients as shared state clients for the connection.
sharedStateOrdering
Optional. The ordering of documents received on a shared state client. The default value is none.
*To receive documents in order from a publisher, set to publisher.
*To receive documents in any order, set to none.
Remarks
You can organize topic names using the scope delimiter (::). The scope can consist of zero or more levels. Following is the syntax:
context::subcontext::subcontext...
where subcontext segments are optional.
The name must begin with an alphabetic character followed by alphanumeric characters or an underscore (_). The following are valid topicName and eventType values:
paris
stocks::all
stocks::nasdaq::webm
stocks::nasdaq::csco
A topic subscriber can also use a topic name that includes a single wildcard character, *, at the end of a topic name. For example, to subscribe to all NASDAQ stocks quotes you could use the following topic name:
stocks::nasdaq::*
If you use wildcards in the topic name, only those topics for which the subscriber has permission to subscribe are included in the subscription.
Related Commands
Create Durable Subscriber
Create Topic
Delete Durable Subscriber
Delete Topic
Modify Topic