![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You can use wildcards when specifying statically created destinations in queues.conf and topics.conf. The use of wildcards in destination names can be used to define "parent" and "child" destination relationships, where the child destinations inherit the properties and permissions from its parents. You must first understand wildcards to understand the inheritance rules described in Inheritance.
• The wildcard > by itself matches any destination name.
• When > is mixed with text, it matches one or more trailing elements. For example:
• Overlapping wildcard destinations can cause conflicts with disjoint properties. For example, consider the following configuration of the store property:The topic topic.sample.quotes.tibx would be assigned both stores, $sys.failsafe and $sys.nonfailsafe. Therefore, the wildcard topics topic.sample.> and topic.sample.quotes.* cannot coexist. Their creation would fail.If you subscribe to a topic containing a wildcard, you will receive any message published to a matching topic. For example, if you subscribe to foo.* you will receive messages published to a topic named foo.bar.You can subscribe to a wildcard topic (for example foo.*), whether or not there is a matching topic in the configuration file (for example, foo.*, foo.>, or foo.bar). However, if there is no matching topic name in the configuration file, no messages will be published on that topic.
• If foo.bar is not in the configuration file, then you can publish to foo.bar if foo.* or foo.> exists in the configuration file.
• As described in Dynamically Creating Topics and Queues, the EMS server may dynamically create destinations on behalf of its clients. The use of wildcards in the .conf files can be used to control the allowable names of dynamically created destinations.
• If the queues.conf file contains:
• If the topics.conf file contains only:The EMS server can dynamically create topics with names like foo.bar, foo.boo, foo.boo.bar, and foo.bar.boo.
• If the queues.conf file contains only:The EMS server can dynamically create queues with names like foo.bar and foo.boo, but not foo.bar.boo.
• If the topics.conf file contains only:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |