Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Messaging Bridge --> Configuration --> General

Tasks Related Topics Attributes

## Overview

A messaging bridge communicates with the configured source and target 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 the source and target destination for the mapping, a message filtering selector, and a quality of service.

## Tasks

Modifying an Existing Messaging Bridge Instance

Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target

## Related Topics

Monitoring All Messaging Bridges

Simple Access to Remote or Foreign JMS Providers

"Using Message-Driven Beans" in Programming WebLogic Enterprise JavaBeans

`MDBTransaction` interface in the weblogic.jms.extensions

Developing a WebLogic JMS Application in Programming WebLogic JMS

## Attributes

Table 97-1

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` |
Source Destination | The source bridge destination from which messages are received by the messaging bridge. This must be an instance of either the JMS Bridge Destination (`JMSBridgeDestinationMBean`) or the General Bridge Destination (`BridgeDestinationMBean`), which are used to define the source destination that the messaging bridge will read messages from. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `SourceDestination` | Default: null
Target Destination | The target bridge destination to which messages are sent from the messaging bridge. This must be an instance of either the JMS Bridge Destination (`JMSBridgeDestinationMBean`) or the General Bridge Destination (`BridgeDestinationMBean`), which are used to define the target destination that the messaging bridge will send the messages it receives from the source destination. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `TargetDestination` | Default: null
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
QOS Degradation Allowed | Indicates whether the messaging bridge automatically degrades the requested QOS (quality-of-service) when the configured one is not available. If this occurs, a message is delivered to the WebLogic startup window (or log file). If QOS Degradation Allowed is not selected, and the messaging bridge cannot satisfy the requested QOS, it will result in an error and the messaging bridge will not start. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `QOSDegradationAllowed` | Default: false Valid values: true false
Maximum Idle Time (seconds) | The maximum number of seconds the messaging bridge will remain idle. For bridges running in asynchronous mode, the maximum idle time defines the longest time the bridge will stay idle before it checks the heath of its connections. For bridges running in synchronous mode, the maximum idle time defines the amount of time the bridge can block on a receive call if no transaction is involved. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `IdleTimeMaximum` | Minimum: 0 Maximum: 9223372036854775807 Default: 60 Dynamic: yes
Asynchronous Mode Enabled | Indicate whether a messaging bridge works in asynchronous mode. Messaging bridges that work in asynchronous mode are driven by the source destination. The messaging bridge listens for messages and forwards them as they arrive. When Asynchronous Mode is disabled, the bridge works in synchronous mode, even if the source supports asynchronous receiving. Note: For a messaging bridge with a QOS of Exactly-once to work in asynchronous mode, the source destination has to support the `MDBTransaction` interface described in the `weblogic.jms.extensions` Javadoc. Otherwise, the bridge automatically switches to synchronous mode if it detects that `MDBTransactions` are not supported by the source destination. For more information about `MDBTransactions`, see "Using Message-Driven Beans" in Programming WebLogic Enterprise JavaBeans. (See the links in the Related Topics section.) MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `AsyncEnabled` | Default: true Valid values: true false
Durability Enabled | Durability is specified only for JMS topics or for third-party destinations with similar characteristics as a JMS topic. This attribute is ignored if the source destination is a JMS queue. By enabling durability, a messaging bridge creates a durable subscription for the source destination. This allows the source JMS implementation to save messages that are sent to it when the bridge is not running. The bridge will then forward these messages to the target bridge destination once it is restarted. If this attribute is not selected, messages that are sent to the source JMS topic while the bridge is down cannot be forwarded to the target destination. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `DurabilityEnabled` | Default: true Valid values: true false
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. For information on monitoring all the configured messaging bridges in your domain, see the "Monitoring All Messaging Bridges" link in the Related Topics section. MBean: `weblogic.management. configuration. MessagingBridgeMBean` Attribute: `Started` | Default: true Valid values: true false Dynamic: yes