Temporary destinations are bus destinations that are created and deleted automatically for API-specific temporary destinations.
For example, if an application creates a temporary JMS queue for use with the default messaging provider, which is based on service integration technologies, the SIB service automatically creates a temporary queue destination on the bus.
A temporary destination is assigned a unique name specific to the SIB service, starting with the prefix _Q for temporary queues and _T for temporary topics.
Temporary destinations appear on the list of runtime queue and publication points for a messaging engine on the service integration bus, but normally need no administration.
Temporary topics cannot be explicitly created on the service integration bus. API-specific temporary destinations (for example, JMS temporary topics) are implemented by creating a temporary topic space and using a single topic within the temporary topic space. This is transparent to the application code. For this reason, applications cannot use a wildcard for temporary topics; for example, a subscriber cannot use a wildcard to receive a copy of messages published to all temporary topics.