Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer bus destinations


Configure bus destinations

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.

Figure 1. Application use of destinations - basic case

To enable the JMS applications to use a queue destination, you configure the following administrative destination objects:

  1. A queue destination on a service integration bus. This configures the properties of the queue, such as the name, and associates the queue with one bus member (an application server or server cluster). This also automatically configures, on the bus member, a queue point where messages for the queue are held and processed.
  2. A JMS queue, which configures the name that applications can use to look up the queue in JNDI. The JMS queue encapsulates the name of the queue destination, as defined in the queue destination above, together with other properties to be used by applications.

After we have created a queue destination, you can optionally configure the queue point to override some properties configured on the queue destination. We can also undertake 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.messaging_engine_name . This exception destination can be used to handle messages that cannot be delivered for all bus destinations 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:


Bus destinations
Create a bus
Configure message points
Administer destination roles
Administer topic space root roles
Administer topic roles
Destinations [Collection]

+

Search Tips   |   Advanced Search