Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Messaging Bridge --> Configure --> Configure Messaging Bridge

Tasks Related Topics Attributes

## Overview

A messaging bridge instance communicates with the configured source and target bridge destinations. For each mapping of a source destination to a target destination, whether it is another WebLogic JMS implementation, a third-party JMS provider, or another non-JMS messaging product, you must configure a messaging bridge instance.

This page allows you to defines general configuration attributes for a messaging bridge instance, including a message filtering selector, and a quality of service.

## Tasks

Configuring a Messaging Bridge

## Related Topics

Messaging Bridge

Modifying an Existing Messaging Bridge Instance

## Attributes

Table 116-4

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | The name of this messaging bridge configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `Name` |
Selector | A message selector for filtering the messages that are sent across the messaging bridge. Only messages that match the selection criteria are sent across the messaging bridge. For queues, messages that do not match the selection criteria are left behind and accumulate in the queue. For topics, messages that do not match the connection criteria are dropped. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `Selector` |
Quality Of Service | The quality-of-service (QOS) guarantee for forwarding messages across a messaging bridge. Exactly-once - Each message in the source destination will be transferred to the target exactly once. This is the highest QOS a bridge can offer. In order to use this QOS: Any WebLogic implementation must be release 6.1 or later. The source and target JMS connection factories must be configured to use the `XAConnectionFactory`. The transaction `jms-xa-adp.rar` adapter must be deployed and identified in the Adapter JNDI Name attribute as "`eis.jms.WLSConnectionFactoryJNDIXA`" for both the source and target destinations. Atmost-once - Each message is sent at most one time. Some messages may not be delivered to the target destination. Duplicate-okay - Each message is sent at least one time. Duplicate messages can be delivered to the target destination. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `QualityOfService` | Default: Exactly-once Valid values: Exactly-once Atmost-once Duplicate-okay
Started | Indicates the initial state of the messaging bridge when it is configured and whenever the server is restarted. You can also use this field to dynamically start and stop the messaging bridge. To stop the bridge, clear the check box. Conversely, reselect the check box to restart the bridge. Note: Unless there is a configuration issue that prevents the messaging bridge from starting, this field indicates the expected run-time state of the messaging bridge. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `Started` | Default: true Valid values: true false Dynamic: yes