Permanent bus destinations
A permanent destination is configured by an administrator and has its runtime instances created automatically by the messaging provider. Permanent destinations remain until the administrator explicitly deletes them.
When we configure a destination on a bus member that is an IBM MQ server, the destination has a single queue point called an IBM MQ queue point. This IBM MQ queue point is an IBM MQ queue on the IBM MQ queue manager or queue-sharing group that the IBM MQ Server represents. For more information about IBM MQ queue points, see related concepts.
The configuration and runtime components of a permanent destination are shown in the following figure.
The administrator configures a bus destination, to define properties such as the type of destination, and mediations and quality of service for the destination. A bus destination is defined on a service integration bus, and is hosted by one or more bus members, depending on whether it is a queue destination or a topic space destination. This results in the system generating one or more message points, where messages are held on that bus. A message point can be configured to override some properties inherited from the bus destination.
For point-to-point messaging, the administrator configures the destination as a queue and selects one bus member, an application server or server cluster, as the assigned bus member that is to hold messages for the queue. This action automatically defines a queue point (a type of message point) for each messaging engine in the assigned member. When an assigned messaging engine starts up, a runtime instance of each of its message points is automatically created. Use the runtime view of a message point to administer the messages on that location.
For publish/subscribe messaging, the administrator configures the destination as a topic space (a hierarchy of topics), but does not have to select any assigned bus member for the topic space. A topic space has a publication point (a type of message point) defined automatically for each messaging engine in the bus.
Related: