Temporary Destination Properties
Temporary destinations, both topics and queues, support the following properties:
Temporary destinations tend to be short-lived objects by nature. Applications have no control over destination names for temporary topics and queues. For these reasons, you cannot directly set the above supported properties on temporary destinations.
However, EMS defines a special temporary destination wildcard that can be used to assign properties and values to temporary topics and queues by way of inheritance.
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:
- In the topics.conf and queues.conf configuration files.
- In the JSON configuration file.
Topics
Properties set on the $TMP$.> topic are immediately and directly inherited by all existing temporary topics and all temporary topics created in the future.
Queues
Properties set on the $TMP$.> queue are immediately and directly inherited by all existing temporary queues and all temporary queues created in the future.