WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer service integration buses > Configure buses > Connect buses > Manage messages that use foreign bus connections

Configure exception destination processing for a link to a foreign bus

We can configure the exception destination processing for a link from a service integration bus to another service integration bus or to a WebSphere MQ network. We can configure whether any undeliverable messages the link handles are rerouted to an exception destination, and whether to use a system default exception destination or configure a specific exception destination.

To configure the exception destination processing for a service integration bus link or WebSphere MQ link, you must know the name of the foreign bus connection associated with that link. A foreign bus connection represents either a connection between two service integration buses or a connection between a service integration bus and a WebSphere MQ network.

To configure a specific exception destination for the link, the exception destination must exist. An exception destination must be a queue destination, and can be on the local bus or a foreign bus. See Create a queue for point-to-point messaging. An exception destination for a link is the destination for an inbound message when the service integration bus link or WebSphere MQ link cannot deliver the message to its target bus destination, or to the exception destination that is configured for that target destination, or when the target destination does not exist.

We can configure an exception destination for a link as one of the following:

• None. The link does not use an exception destination and undeliverable messages are not rerouted to an exception destination. For a service integration bus link, such messages can block the processing of other messages waiting for delivery to the same destination. For a WebSphere MQ link, such messages can block the processing of other messages waiting for delivery through that link to the same bus.
• System. The link uses the default exception destination. Messages that cannot be delivered to the bus destination are rerouted to the system default exception destination for the messaging engine that this link is assigned to: _SYSTEM.Exception.Destination.messaging_engine_name. This is the default option.

• Specify. The link uses the specified exception destination. If the link cannot use this exception destination, it uses the system exception destination.

Note that best-effort messages are always discarded if they cannot be delivered to their target destination, that is, they never use an exception destination.

Any report options that are set in the properties of a message also affect exception destination processing. Depending on the report options, a message might be discarded if it is not delivered.

1. In the navigation pane of the dmgr console, click Service integration -> Buses to display a list of buses.

2. Select the bus that has the link for which to configure exception destination processing.
3. In the Configuration tab, under Topology, click Foreign bus connections to display a list of connections for this bus.

4. Select the name of the foreign bus connection associated with the link for which to configure exception destination processing.

5. For a link to another service integration bus, under Related Items, click Service integration bus links. For a link to a WebSphere MQ network, under Related Items, click WebSphere MQ links.

6. Select the name of the link you require from the list. The details of that link are displayed.
7. In the Configuration tab, under General properties, in the Exception destination section, use the radio buttons to configure the exception destination processing that this link uses:

   • Select None to specify the link does not use an exception destination.

   • Select System to use the default exception destination.

   • Select Specify and enter an exception destination to configure the exception destination you require.

8. Save your changes to the master configuration.
   

Results

You have configured the exception destination processing for undeliverable messages that are handled by the link.

We can also configure exception destination processing for a bus destination.

Related concepts:

Message flow between service integration buses
Strict message ordering for bus destinations
Exception destinations

Related

Configure exception destination processing for a bus destination
Create a queue for point-to-point messaging

Related information:

Foreign bus connections [Collection]
Service integration bus links [Collection]
WebSphere MQ links [Collection]
Service integration bus links [Settings]
WebSphere MQ link [Settings]

+

Search Tips   |   Advanced Search