Permanent bus destinations

A permanent destination is configured by an administrator and has its runtime instances created automatically by the messaging provider. Such destinations remain until the administrator explicitly deletes them.

The configuration and runtime components of a permanent destination are shown in the following figure.This figure shows a bus destination and its message point, which is the location on a messaging engine where messages are held for the destination.

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 one or more locations, generally called message point , 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.

For publish/subscribe messaging, the administrator configures the destination as a topic space (a hierarchy of topics), but does not need 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.

When an assigned messaging engine starts up, a runtime instance of each of its message points is created automatically and need no administration. You can use the runtime view of a message point to administer the messages on that location.




Related concepts
Learning about bus destinations
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=cjo0008_
File name: cjo0008_.html