A queue destination is a bus destination configured for point-to-point messaging.
The term "queue" is used, as an abbreviation for "queue destination", to refer to a bus destination configured for point-to-point messaging.
Applications use API-specific artifacts like a JMS queue, which encapsulates the name of a queue destination, but are unaware of the existence of the destination or of the service integration bus it is configured on. The term "JMS queue" is used to refer to the queue that JMS applications interact with, and which an administrator configures as a JMS resource of the default messaging provider.
The administrator assigns a queue to only one member (an application server or server cluster) of the service integration bus. The messaging engine in the bus member hosts the message point for the queue, known as a queue point. The queue point is the location where messages for the queue are stored and processed.
If the bus member has more than one messaging engine, the queue is partitioned across the messaging engines. Each messaging engine has a separate queue point for the queue, and handles a share of the messages arriving at the destination.
An application can also create its own temporary queues, which appear temporarily in the list of queue points for the messaging engine, but normally need no administrative intervention.