![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
•
• The temporary destination wildcard is defined as $TMP$.>, and can be used for both topics and queues. All properties set on topics using the wildcard are inherited by all temporary topics. Similarly, all properties set on queues using the wildcard are inherited by all temporary queues.Although the same wildcard is used for both destination types, property values assigned using the wildcard are not shared between topics and queues. That is, you can assign one overflowPolicy to all temporary topics, and a different overflowPolicy to all temporary queues.Properties can also be set on the $TMP$.> temporary destination wildcard through a variety of ways:
• Using the following tibemsadmin commands:
−
−
−
−
−
−
• Properties set on the $TMP$.> topic are immediately and directly inherited by all existing temporary topics and all temporary topics created in the future.Properties set on the $TMP$.> queue are immediately and directly inherited by all existing temporary queues and all temporary queues created in the future.The temporary destination wildcard $TMP$.> can only be used to set properties on temporary topics or queues through inheritance.
• $TMP$.> cannot be used to send or receive messages.
• $TMP$.> cannot be used as the source or target of a destination bridge.
• You cannot use $TMP$.> to import or export messages from TIBCO FTL, Rendezvous, or SmartSockets transports.
• $TMP$.> never inherits any properties from other destination wildcards. For example, $TMP$.> does not inherit from the wildcard >.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |