Temporary bus destinations

A temporary destination only exists while an application is using it. Typically, this situation occurs when the application uses a JMS temporary destination. Service integration creates a corresponding temporary service integration bus destination.

For example, if an application creates a temporary JMS queue for use with the default messaging provider, 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. The name starts with the prefix _Q for temporary queues or _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. Temporary destinations do not usually need 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 not apparent to the application code. For this reason, applications cannot use a wildcard for temporary topics. This means, for example, a subscriber cannot use a wildcard to receive a copy of messages published to all temporary topics.

See also How JMS destinations relate to service integration destinations.


Icon that indicates the type of topic Concept topic



Timestamp icon Last updated: March 5, 2017 17:24
File name: cjo0003_.html