MessagingBridge

Description

This class represents a messaging bridge, which is responsible for transferring messages between any two messaging products--including separate implementations of WebLogic JMS.

Specifically, you can configure a source/target mapping of a JMS destination (queue or topic) to another JMS destination. Messages that are sent to the source bridge destination are then automatically forwarded to the target bridge destination. The messaging bridge also allows you to specify a degree of QOS (quality of service), as well as message filtering, transaction semantics, and connection policies.

Syntax

<!ELEMENT MessagingBridge EMPTY >

<!ATTLIST MessagingBridge
   AsyncEnabled               (true | false)           "true"
   BatchInterval              CDATA                    "-1"
   BatchSize                  CDATA                    "10"
   DeploymentOrder            CDATA                    "1000"
   DurabilityEnabled          (true | false)           "true"
   IdleTimeMaximum            CDATA                    "60"
   Name                       CDATA                    #REQUIRED
   Notes                      CDATA                    #IMPLIED
   QOSDegradationAllowed      (true | false)           "false"
   QualityOfService           (Exactly-once | 
                               Atmost-once | 
                               Duplicate-okay)         "Exactly-once"
   ReconnectDelayIncrease     CDATA                    "5"
   ReconnectDelayMaximum      CDATA                    "60"
   ReconnectDelayMinimum      CDATA                    "15"
   Selector                   CDATA                    #IMPLIED
   SourceDestination          CDATA                    #IMPLIED
   Started                    (true | false)           "true"
   TargetDestination          CDATA                    #IMPLIED
   Targets                    CDATA                    #IMPLIED
   TransactionTimeout         CDATA                    "30"
>

Parent Elements

The MessagingBridge element is a child of the Domain element.

Attributes

Table 51-1 MessagingBridgeMBean Element Attributes

Attribute	Description	Range of Values and Default	Console Label
Async-Enabled	Indicates whether or not the messaging bridge will work in asynchronous messaging mode. Note: This attribute only applies to messaging bridges whose source destination supports asynchronous receiving. Messaging bridges that work in asynchronous mode (true) are driven by the source target. The messaging bridge listens for messages and forwards them as they arrive. When the value is set to false, the bridge is forced to work in synchronous mode, even if the source supports asynchronous receiving. Note: For a messaging bridge with a QOS of Exactly-onceto work in asynchronous mode, the source destination has to support the MDBTransaction interface. Otherwise, the bridge will automatically switch to synchronous mode if it detects that MDBTransactions are not supported by the source destination.	Default: true	Asynchronous Mode Enabled
Batch-Interval	Defines the maximum time, in milliseconds, that the bridge will wait before sending a batch of messages in one transaction, regardless of whether the Batch Size amount has been reached or not. Note:This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions.	Default: -1	Batch Interval (milliseconds)
Batch-Size	Specifies the number of messages that are processed within one transaction. Note:This attribute only applies to bridges that work in synchronous mode and whose QOS require two-phase transactions.	Default: 10 Minimum: 0	Batch Size
Deployment-Order	A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all startup classes before it prioritizes and deploys EJBs. Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.	Default: 1000 Minimum: 0 Maximum: 2147483647	Deployment Order
Durability-Enabled	Indicates whether or not the messaging bridge allows durable messages. This only applies to a source destination that uses durable subscriptions, which allows the source JMS implementation to save messages that are sent to it while the bridge is not running. The bridge will forward these messages to the target destination when it is restarted. The administrator can choose not to be durable.	Default: true	Durability Enabled
Idle-Time-Maximum	Defines the maximum amount of idle time for the messaging bridge. If the bridge works in asynchronous mode, the maximum idle time defines the longest time the bridge will stay idle before it checks the sanity of its connection to the source. If the bridge works 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.	Default: 60 Minimum: 0 Maximum: 9223372036854775807	Maximum Idle Time (milliseconds)
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.		Name
Notes	Optional information that you can include to describe this configuration.		Notes
QOSDegradation-Allowed	Indicates whether or not the bridge allows the degradation of its QOS when the configured QOS is not available.	Default: false	QOS Degradation Allowed
Quality-Of-Service	Defines one of the following QOS (quality of service) values for the 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. Atmost-once One message in the source will be transferred to the target only once with the possibility of being lost during the forwarding. Duplicate-okay Messages in the source will not get lost but some may appear in the target more than once.	Default: "Exactly-once" Valid values: "Exactly-once" "Atmost-once" "Duplicate-okay"	Quality Of Service
Reconnect-Delay-Increase	Defines an incremental delay time, in milliseconds, that the messaging bridge will wait longer between one failed reconnection attempt and the next retry. This attribute works with the ReconnectDelayMinimum and ReconnectionDelayMaximum attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectionDelayMinimum. Each time a reconnect attempt fails, the bridge will increase its waiting time by the number of seconds defined by ReconnectDelayIncrease. The maximum delay time is defined by ReconnectionDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the minimum value defined by ReconnectionDelayMinimum.	Default: 5 Minimum: 0 Maximum: 9223372036854775807	Incremental Delay (seconds)
Reconnect-Delay-Maximum	Defines the longest time, in seconds, that the messaging bridge will wait between one failed attempt to reconnect to the source or target and the next retry. This attribute works with the ReconnectDelayMinimum and ReconnectionDelayIncrement attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectionDelayMinimum. Each time a reconnect attempt fails, the bridge will increase its waiting time by the number of milliseconds defined by ReconnectDelayIncrement. The maximum delay time is defined by ReconnectionDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the initial value defined by ReconnectionDelayMinimum.	Default: 60 Minimum: 0 Maximum: 9223372036854775807	Maximum Delay (seconds)
Reconnect-Delay-Minimum	Defines the minimum amount of time, in seconds, that the messaging bridge will wait before it tries to reconnect to the source or target destination after a failure. This attribute works with the ReconnectDelayMaximum and ReconnectionDelayInterval attributes. After the first failure to connect to a destination, the bridge will wait for the number of seconds defined by ReconnectionDelayMinimum. If the second trial also fails, it will increase its waiting time by the number of seconds defined by ReconnectDelayInterval. The maximum delay time is defined by ReconnectionDelayMaximum. Once the waiting time is increased to the maximum value, the bridge will not increase its waiting time anymore. Once the bridge successfully connects to the destination, its waiting time will be reset to the initial value defined by ReconnectionDelayMinimum.	Default: 15 Minimum: 0 Maximum: 9223372036854775807	Minimum Delay (seconds)
Selector	Defines the message selector for the messaging bridge. The message selector allows you to filter 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.		Selector
Source-Destination	Defines the source destination for the messaging bridge. This must be an instance of either BridgeDestinationMBean or JMSBridgeDestinationMBean, which define the source destination from which the bridge reads messages.	Default: null	Source Destination
Started	Indicates the "started" and "stopped" state of the messaging bridge. If the value is true, the bridge is in working condition. If the value is false, the bridge is temporarily stopped.	Default: true	Started
Target-Destination	Defines the target destination for the messaging bridge. This must be an instance of either BridgeDestinationMBean or JMSBridgeDestinationMBean, which define the target destination to which the bridge sends the messages it receives from the source destination.	Default: null	Target Destination
Targets	The targets in the current domain on which this item can be deployed.		Targets
Transaction-Timeout	Defines the amount of time, in seconds, that the transaction manager will wait for each transaction before timing it out. Transaction timeouts are used when the QOS for a bridge requires transactions. If a bridge is configured with Exactly-onceQOS, the receiving and sending is completed in one transaction.	Default: 30 Minimum: 0 Maximum: 2147483647	Transaction Timeout