Use the following tasks to configure permanent bus destinations on service integration buses.
The steps involved in configuring a bus destination depend on the intended usage of the destination.
For example, the following figure shows a basic scenario based on an application using a JMS queue for point-to-point messaging. A producing application sends messages to a JMS queue from which a consuming application retrieves the messages. The JMS queue is assigned to a queue destination and its associated queue point, where messages are stored.
After you have created a queue destination, you can optionally configure the queue point to override some properties configured on the queue destination. You can also perform other configuration tasks on the destination and its queue point, and can act on the runtime view.
Each messaging engine has a default exception destination, named _SYSTEM.Exception.Destinaton.me_name. This exception destination can be used to handle messages that cannot be delivered for all bus destination that are localized to the messaging engine. Each bus destination can be configured with a non-default exception destination.
For more information about configuring bus destinations, see the following topics:
In this information ...Subtopics
Related concepts
| IBM Redbooks, demos, education, and more(Index) |