Messaging Bridge

[Attributes and Console Screen Reference for Messaging Bridge]

The following sections explain how to configure and manage a WebLogic Messaging Bridge:

You may also want to refer these WebLogic JMS sections:

 

What Is a Messaging Bridge?

The WebLogic Messaging Bridge allows you to configure a forwarding mechanism between any two messaging products - thereby, providing interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product. You can use the Messaging Bridge to integrate your messaging applications between:

  • Any two implementations of WebLogic JMS, including those from separate releases of WebLogic Server.
  • WebLogic JMS implementations that reside in separate WebLogic domains.
  • WebLogic JMS with a third-party JMS product (for example, MQSeries).
  • WebLogic JMS with non-JMS messaging products (only by using specialized connector adapters that are not provided with WebLogic Server).

A messaging bridge consists of two destinations that are being bridged: a source destination that the bridge reads messages from and a target destination where the bridge sends the messages that it receives from the source destination. For WebLogic JMS and third-party JMS products, a messaging bridge communicates with source and target destinations using the resource adapters provided with WebLogic Server. For non-JMS messaging products, a custom connector adapter must be obtained from a third-party OEM vendor or by contacting BEA Professional Services in order to access non-JMS source or target destinations.

Source and target bridge destinations can be either queues or topics. You can also specify a quality of service (QOS), as well as message filters, transaction semantics, and connection retry policies. Once a messaging bridge is configured, it is easily managed from the Administration Console, including temporarily suspending bridge traffic whenever necessary, tuning the execute thread pool size to suit your implementation, and monitoring the status of all your configured bridges.

 

Messaging Bridge Configuration Tasks

Before you can deploy a messaging bridge, you need to configure its required components:

 

About the Bridge's Resource Adapters

A messaging bridge uses resource adapters to communicate with the configured source and target JMS destinations. You need to associate both the source and target JMS destinations with a supported resource adapter in order for the bridge to communicate with them. The JNDI name for the adapter is configured as part of the resource adapter's deployment descriptor.

Note: Although WebLogic JMS includes a "General Bridge Destination" framework for accessing non-JMS messaging products, WebLogic Server does not provide supported connector adapters for such products. Therefore, obtain a custom connector adapter from a third-party OEM vendor and consult their documentation for configuration instructions. You can also contact BEA Professional Services for information about obtaining a custom connector adapter.

The supported resource adapters are located in the $WL_HOME/server/lib directory and are described in the following table.

Adapter

JNDI Name

Description

jms-xa-adp.rar eis.jms.WLSConnection
FactoryJNDIXA 		Provides transaction semantics via the XAResource. Used when the required QOS is Exactly-once. This envelops a received message and sends it within a user transaction (XA/JTA). The following requirements are necessary in order to use this resource adapter:

  • Any WebLogic Server implementation being bridged must be release 6.1 or later.

  • The source and target JMS connection factories must be configured to use the XAConnectionFactory.

Note: Before deploying this resource adapter, refer to the Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains for specific transactional configuration requirements and guidelines.

jms-notran-adp.rar eis.jms.WLSConnection
FactoryJNDINoTX 		Provides no transaction semantics. Used when the required QOS is Atmost-once or Duplicate-okay. If the requested QOS is Atmost-once, the resource adapter uses the AUTO_ACKNOWLEDGE mode. If the requested QOS is Duplicate-okay, CLIENT_ACKNOWLEDGE is used.

Note: For more information about the acknowledge modes used in non-transacted sessions, see "WebLogic JMS Fundamentals in Programming WebLogic JMS.

jms-notran-adp51.rar eis.jms.WLS51ConnectionFactoryJNDINoTX Provides interoperability with release 5.1 when either the source or target destination is a 5.1 server instance. This resource adapter provides no transaction semantics; therefore, it only supports a QOS of Atmost-once or Duplicate-okay. If the requested QOS is Atmost-once, the resource adapter uses the AUTO_ACKNOWLEDGE mode. If the requested QOS is Duplicate-okay, CLIENT_ACKNOWLEDGE is used.

You will specify the appropriate resource adapter by its JNDI name when you configure each source and target bridge destination.

 

Deploying the Bridge's Resource Adapters

Before you configure the messaging bridge destinations, deploy the appropriate resource adapters in the WebLogic Server domain that is hosting the messaging bridge, as follows:

  1. Select the domain in which you will deploy the adapters (for example, Examples).
  2. Select the Deployments - > Connector Modules option to open the Resource Connectors page.
  3. Follow the deployment assistant instructions to deploy the appropriate resource adapter, as defined in Table 105-1.

    • jms-xa-adp.rar
    • jms-notran-adp.rar
    • jms-notran-adp51.rar
  4. You must target the resource adapter to the same WebLogic Server instance that the messaging bridge will be targeted to. For more information, see Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target.

    Note: When configuring a messaging bridge to interoperate between WebLogic Server release 8.1 and release 5.1, then the release 5.1 resource adapter (jms-notran-adp51.rar) and the non-transaction adapter (jms-notran-adp.rar) must be deployed on the 8.1 domain running the messaging bridge.

For more information on deploying resource adapters, see "Packaging and Deploying Connectors in Programming WebLogic Server J2EE Connectors.

 

Configuring Source and Target Bridge Destinations

A messaging bridge connects two actual destinations that are mapped to bridge destinations: a source destination from which messages are received, and a target destination to which messages are sent. Depending on the messaging products that need to be bridged, there are two types of bridge destinations:

  • JMS Bridge Destination - For JMS messaging products, whether it is a WebLogic JMS implementation or a third-party JMS provider, you need to configure a JMSBridgeDestination instance for each actual source and target JMS destination being mapped to a messaging bridge.
  • General Bridge Destination - For non-JMS messaging products, you need to configure a generic BridgeDestination instance for each actual source and target destination being mapped to a messaging bridge.

Before starting the procedures in this section, refer to the Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains or Using the Messaging Bridge to Access a Third-Party Messaging Provider sections for specific configuration requirements and guidelines.

Note: When configuring third-party JMS provider bridge destination, you can use the Foreign JMS Server feature to quickly configure multiple source or target destinations. For more information, see Simple Access to Remote or Foreign JMS Providers.

 

Configuring JMS Bridge Destinations

A JMSBridgeDestination instance defines a unique name for a bridge's source and target destinations within a WebLogic domain, the name of the adapter used to communicate with the specified destination, property information to pass to the adapter (Connection URL, Connection Factory JNDI Name, etc.), and, optionally, a user name and password.

You need to configure a JMSBridgeDestination instance for each actual source and target JMS destination to be mapped to a messaging bridge. Therefore, when you finish defining attributes for a source JMS bridge destination, repeat these steps to configure a target JMS bridge destination, or vice versa. You will designate the source and target JMS Bridge Destinations in Configuring a Messaging Bridge Instance.

To configure a source or target JMS bridge destination, follow these steps.

  1. Expand the Services - > Messaging Bridge node.
  2. Click the JMS Bridge Destinations node to open the JMS Bridge Destinations page in the right pane.
  3. Click the Configure a new JMS Bridge Destination link. A Configuration dialog shows the tabs associated with configuring a new JMS bridge destination.
  4. On the Configuration General tab, define the general configuration attributes for a JMS bridge destination:

    • Enter a JMS bridge destination name for the actual JMS destination being mapped to the bridge. This name must be unique across a WebLogic domain. For example, if you are bridging between WebLogic Server releases 6.1 and 8.1, for the source destination you could change the default bridge destination name to "61SourceDestination". Then, when you create the corresponding target destination, you could name it as "81TargetDestination". Once the bridge destinations are configured, these names are listed as options in the Source Destination and Target Destination attributes on the Bridges - > General tab.
    • Specify the JNDI name of the resource adapter used to communicate with the messaging bridge destinations:

      eis.jms.WLSConnectionFactoryJNDIXA (default) - QOS is Exactly-once

      eis.jms.WLSConnectionFactoryJNDINoTX - QOS is Atmost-once or Duplicate-Okay

      eis.jms.WLS51ConnectionFactoryJNDINoTX - used only with release 5.1 and only supports QOS of Atmost-once or Duplicate-Okay

      For more information on which resource adapter name to use, see Messaging Bridge Resource Adapters and JNDI Names.

    • Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running on WebLogic Server 6.1 or later. When connecting to either a source or target destination that is running on WebLogic Server 6.0 or earlier, the Adapter Classpath field must indicate the location of the classes for the earlier WebLogic Server release. When connecting to a third-party JMS provider, the bridge destination must supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
    • Specify the URL of the JNDI provider used to look up the connection factory and destination.
    • Specify the context factory used to get the JNDI context.
    • Specify the JMS connection factory used to create a connection for the actual JMS destination being mapped to the JMS bridge destination.

      Note: In order to use the Exactly-once QOS for transactions, the JMS connection factory has to be an XA connection factory. For more information about connection factory and QOS requirements, refer to the Attributes table in Messaging Bridge --> Configuration --> General.

    • Specify the JNDI name of the actual JMS destination being mapped to the JMS bridge destination.
    • Indicate whether the destination type is either a Queue or Topic.
    • Optionally, enter the user name and password that the messaging bridge will give to the bridge adapter.

      Note: All operations done to the specified destination are done using that user name and password. Therefore, the User Name/Password for the source and target destinations must have permission to access the underlying JMS destinations in order for the messaging bridge to work.

    For more information about JMS bridge destination attributes, see JMS Bridge Destination --> Configuration.

  5. Click Create to create an instance of the bridge destination with the name you specified in the Name field. The new instance is added under the JMS Bridge Destination node in the left pane.

When you finish defining attributes for a source JMS bridge destination, repeat these steps to configure a target JMS bridge destination, or vice versa. Then follow the instructions for Configuring a Messaging Bridge Instance.

 

Configuring General Bridge Destinations

A general BridgeDestination instance defines a unique name for the actual source and target general bridge destinations within the WebLogic domain, the name of the adapter used to communicate with the specified destination, a list of properties to pass to the adapter, and, optionally, a user name and password.

Note: Although WebLogic JMS includes a "General Bridge Destination" framework for accessing non-JMS messaging products, WebLogic Server does not provide supported connector adapters for such products. Therefore, obtain a custom connector adapter from a third-party OEM vendor and consult their documentation for configuration instructions. You can also contact BEA Professional Services for information about obtaining a custom connector adapter.

You need to configure a BridgeDestination instance for each actual source and target destination to be mapped to a messaging bridge. Therefore, when you finish defining attributes for a source general bridge destination, repeat these steps to configure a target general bridge destination, or vice versa. You will designate the source and target general Bridge Destinations in Configuring a Messaging Bridge Instance.

To configure a source or target general bridge destination, follow these steps.

  1. Expand the Services - > Messaging Bridge node.
  2. Click the General Bridge Destinations node to open the General Bridge Destinations page in the right pane.
  3. Click the Configure a new General Bridge Destination link. A Configuration dialog shows the tabs associated with configuring a new general bridge destination.
  4. On the Configuration General tab, define the general configuration attributes for a general bridge destination:

    • Enter a general bridge destination name that is unique across a WebLogic Server domain. For example, if you are bridging between WebLogic Server releases 6.1 and 8.1, for the source destination you could change the default destination name to "61SourceDestination". Then when you create the corresponding target destination, you could name it as "81TargetDestination". Once the bridge destinations are configured, these names are listed as options in the Source Destination and Target Destination attributes on the Bridges - > General tab.
    • Specify the JNDI name of the adapter used to communicate with the bridge destinations.

      eis.jms.WLSConnectionFactoryJNDIXA (default) - QOS is Exactly-once

      eis.jms.WLSConnectionFactoryJNDINoTX - QOS is Atmost-once or Duplicate-Okay

      eis.jms.WLS51ConnectionFactoryJNDINoTX - used only with release 5.1 and only supports QOS of Atmost-once or Duplicate-Okay

      For more information on which resource adapter name to use, see Messaging Bridge Resource Adapters and JNDI Names.

      Note: WebLogic Server does not provide adapters for non-JMS messaging products. Therefore, use a specialized adapter from a third-party OEM vendor, or contact BEA Professional Services to obtain a custom adapter.

    • Leave the Adapter Classpath field blank when connecting to source and target destinations that are both running on WebLogic Server 6.1 or later. When connecting to either a source or target destination that is running on WebLogic Server 6.0 or earlier, the Adapter Classpath field must indicate the location of the classes for the earlier WebLogic Server release. When connecting to a third-party JMS provider, the bridge destination must supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
    • Specify all the properties defined for a bridge destination. Each property must be separated by a semicolon (for example, DestinationJNDIName=myTopic;DestinationType=topic;). For a complete listing of the required properties for JMS implementations, refer to the Attributes table in General Bridge Destination --> Configuration.

      Note: For non-JMS messaging products that use adapters provided by a third-party OEM vendor, you should consult the vendor's documentation for property configuration instructions.

    • Optionally, enter the user name and password that the messaging bridge will give to the bridge adapter. Note that the User Name/Password for the source and target destinations must have permission to access the underlying source and target destinations in order for the Messaging Bridge to work.

    For more information about the general bridge destination attributes, see General Bridge Destination --> Configuration.

  5. Click Create to create an instance of the general bridge destination with the name you specified in the Name field. The new instance is added under the General Bridge Destination node in the left pane.

When you finish defining attributes for a source general bridge destination, repeat these steps to configure a target general bridge destination, or vice versa. Then follow the instructions for Configuring a Messaging Bridge Instance.

 

Configuring a Messaging Bridge Instance

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, configure a MessagingBridge instance. Each MessagingBridge instance defines the source and target destination for the mapping, a message filtering selector, a QOS, transaction semantics, and various reconnection parameters.

Before starting the procedure in this section, refer to the Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains or Using the Messaging Bridge to Access a Third-Party Messaging Provider sections for specific configuration requirements and guidelines.

To configure a messaging bridge, follow these steps:

  1. Expand the Services - > Messaging Bridge node.
  2. Expand the Bridges node to open the Messaging Bridges tab in the right pane.
  3. Click the Configure a new Messaging Bridge link. A dialog shows the tabs associated with configuring a new messaging bridge.
  4. On the Configuration General tab, define the general configuration attributes for a messaging bridge:

    Attribute

    Description

    Name Enter a messaging bridge name that is unique across a WebLogic Server domain.
    Source Destination Select the source destination from which messages are received by the messaging bridge. Following the example target JMS bridge destination name that was previously suggested for connecting WebLogic Server releases 6.1 and 8.1, you would select the "61SourceDestination" name that you created on the JMS Bridge Destination -> Configuration tab.
    Target Destination Select the target destination to which messages are sent from the messaging bridge. Following the example target JMS bridge destination name that was previously suggested for connecting WebLogic Server releases 6.1 and 8.1, you would select the "81TargetDestination" name that you created on the JMS Bridge Destination -> Configuration tab.
    Selector Specify a selector 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. For more information on using selectors to filter messages, see Developing a WebLogic JMS Application" in Programming WebLogic JMS.
    Quality Of Service (QOS) Select a quality-of-service guarantee for forwarding a message across a messaging bridge. The valid qualities of service are:Exactly-once (default) - Each message will be sent exactly once. This is the highest quality of service. In order to use this QOS:

    • Any WebLogic Server 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.
    QOS Degradation Allowed Indicate whether the messaging bridge automatically degrades the requested QOS 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.
    Maximum Idle Time
    (seconds)     		For bridges running in asynchronous mode, specify the maximum amount of time the messaging bridge will sit idle before checking the health of its connections. For bridges running in synchronous mode, this determines the amount of time the messaging bridge can block on a receive call if no transaction is involved.
    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 EJB.

    Durability Enabled This is used only for JMS topics or for third-party destinations with similar characteristics as a JMS topic. 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 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.

    Note: If a bridge must be taken permanently offline, delete any durable subscriptions that use the bridge. For information on deleting durable subscribers, see "Deleting Durable Subscriptions in Programming WebLogic JMS.

    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 Monitoring All Messaging Bridges.


    For more information about the general messaging bridge attributes, see the Attributes table in Messaging Bridge --> Configuration --> General.

  5. Click Create to create an instance of the messaging bridge with the name you specified in the Name field. The new instance is added under the Bridges node in the left pane. If you selected the Started check box, the bridge will be in a running state once it is targeted.
  6. On the Target and Deploy tab, select an independent server instance, a cluster, or a migratable server target on which to deploy the messaging bridge. This must the same target where the bridge's resource adapter was deployed. You can also reconfigure deployment targets later if you wish.

    For more information, see Targeting a Messaging Bridge to a Server, a Cluster, or a Migratable Target.

  7. Optionally, on the Connection Retry tab, change the attribute fields or accept the default values as assigned. Since the source and target destinations for a messaging bridge will not always be available, the messaging bridge must be able to reconnect to the destination at some periodic interval. These attributes govern the time between reconnection attempts. Then, click Apply to save your changes.

    For more information about the bridge's connection retry attributes, see the Attributes table in Messaging Bridge --> Configuration --> Connection Retry.

  8. Optionally, on the Transactions tab, change the attribute fields or accept the default values as assigned. Then, click Apply to save your changes.

    For more information about the bridge's transaction attributes, see the Attributes table in Messaging Bridge --> Configuration --> Transactions.

 

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

You can choose the servers, clusters, or migratable targets in your domain on which you would like to deploy a messaging bridge. You can also reconfigure deployment targets later if you wish.

  1. Expand the Messaging Bridge - > Bridges node to show the list of messaging bridges defined in your domain.
  2. Click the messaging bridge that you want to assign to a server, cluster, or migratable target. A dialog displays in the right pane showing the tabs associated with the messaging bridge instance.
  3. Click the Target and Deploy tab to display the following targeting options.

    • Independent Servers - you can select a server or servers where the messaging bridge will be deployed. The messaging bridge will be available on all the selected servers.
    • Clusters - you can select a cluster where the messaging bridge will be deployed. The messaging bridge will be available on all servers in the selected cluster. You can also target an individual server or servers within a cluster.
    • Migratable Targets - you can select a WebLogic Server migratable target where the messaging bridge will be deployed. When WebLogic Server is first booted, the messaging bridge is initially available only on the user-preferred server. After that, the bridge can be migrated to another server listed in the migratable target.

      Note: This must be the same target where the bridge's resource adapter was deployed. For more information, see Deploying the Bridge's Resource Adapters.

  4. Click Apply to save your assignments.

 

Using the Messaging Bridge to Interoperate with Different WebLogic Server Releases and Domains

The following interoperability guidelines apply when using the messaging bridge to access JMS destinations on different releases of WebLogic Server and in other WebLogic Server domains.

Note: When the messaging bridge is used to communicate between two domains running different releases of Weblogic Server, a best-practice recommendation is for the messaging bridge to be configured to run on the domain using the latest release of Weblogic Server.

 

Naming Guidelines for WebLogic Servers and Domains

Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. Therefore, make sure that:

  • WebLogic Server instances and domain names are unique.
  • WebLogic JMS server names are unique name across domains.
  • If a JMS file store is being used for persistent messages, the JMS file store name must be unique across domains.

 

Enabling Security Interoperability for WebLogic Domains

Whenever the Exactly-once QOS (quality of service) is required for transactionally transferring messages across different WebLogic Server domains, establish a trust relationship between these domains by using a common security credential. This requirement applies to the source and target destination domains, as well as to the messaging bridge domain - if the messaging bridge is not running in the same domain as the source or target domains.

Follow these steps to establish a trusted relationship between release 6.1 or later WebLogic domains.

  1. Configure the security for the 8.1 domain where the messaging bridge is running as follows:
    1. Expand the Domains node (for example, Examples).
    2. Click the View Domain-Wide Security Settings link on the General tab.
    3. Select the Security Configuration - > Advanced tab.
    4. If necessary, clear the Enable Generated Credential check box.
    5. Enter a password for the domain in the Credential field. This password must match the password used for the domain that you are interoperating with.

      Note: When interoperating with a release 6.1 domain, the 7.0 or 8.1 Credential password must exactly match the "system" user password configured for the 6.1 domain.

    6. Confirm the password in the Confirm field, and then click Apply.
  2. When interoperating with a release 6.1 domain, make sure that "system" user is a member of the Administrators group in the 7.0 or 8.1 domain.

Note: For more information about WebLogic Server 7.0 or later domain interoperability security, see "Enabling Trust Between WebLogic Domains in Managing WebLogic Security.

 

Using the Messaging Bridge To Access Destinations In a Release 6.1 or Later Domain

Use these guidelines when configuring a messaging bridge on a release 8.1 domain to provide "Exactly-once" transactional message communication between two release 6.1 or later domains. Note that the Exactly-once quality of service for two-phase transactions is only supported for release 6.1 or later.

  • If a JMS file store is being used for persistent messages, the JMS file store name must be unique across WebLogic domains, as described in Naming Guidelines for WebLogic Servers and Domains.
  • Make sure that security interoperability between the domains is correctly configured, as described in Enabling Security Interoperability for WebLogic Domains.
  • Make sure that the XA connection factory is enabled for the domains by selecting the XAConnection Factory Enabled check box on the Services - > JMS - > Connection Factories - > Configuration - > Transactions tab.
  • Deploy the transaction resource adapter, jms-xa-adp.rar, on the 8.1 domain where the messaging bridge is running, as described in Deploying the Bridge's Resource Adapters.
  • When configuring the JMS bridge destinations, as described in Configuring JMS Bridge Destinations, do the following for both the source and target destinations:

    • In the Adapter JNDI Name field, identify the transaction adapter's JNDI name, eis.jms.WLSConnectionFactoryJNDIXA.
    • Do not enter anything in the Adapter Classpath field.
  • On the Messaging Bridge - > Configuration - > General tab, select a Quality Of Service of Exactly-once, as described in Configuring a Messaging Bridge Instance.

 

Using the Messaging Bridging To Access Destinations In a Release 6.0 Domain

When configuring a messaging bridge involves interoperability between WebLogic Server 8.1 and a release 6.0 domain, configure the following items on the Weblogic Server 8.1 domain that the bridge is running on: Note that the Exactly-once QOS (quality of service) for transactions is not supported for WebLogic Server 6.0. For more information on the bridge QOS options, see the Attribute table in Messaging Bridge --> Configuration --> General.

  • Deploy the non-transaction resource adapter, jms-notran-adp.rar on the 8.1 bridge domain, as described in Deploying the Bridge's Resource Adapters.
  • When configuring the JMS source and target destinations, as described in Configuring JMS Bridge Destinations, do the following:

    In the Adapter JNDI Name field:

    • For the source and target destinations, specify the non-transaction adapter's JNDI name as eis.jms.WLSConnectionFactoryJNDINoTX.

    In the Adapter Classpath field:

    • For the 8.1 destination, leave the field blank.
    • For the 6.0 destination, indicate the location of the classes for the WebLogic Server 6.0 release.

      For example, if you have WebLogic Server 6.0 GA installed in a directory named WL60_HOME, then set the Adapter Classpath as follows for the 6.0 JMS bridge destination:

      WL60_HOME\lib\weblogic60.jar

  • On the Messaging Bridge - > Configuration - > General tab, select a Quality Of Service of Atmost-once or Duplicate-okay, as described in Configuring a Messaging Bridge Instance.

 

Using the Messaging Bridging To Access Destinations In a Release 5.1 Domain

When configuring a messaging bridge involves interoperability between WebLogic Server 8.1 and release 5.1, configure the following on the Weblogic Server 8.1 implementation that the bridge is running on: Note that the Exactly-once QOS for transactions is not supported for WebLogic Server 5.1. For more information on the bridge QOS options, see the Attribute table in Messaging Bridge --> Configuration --> General.

  • The jms51-interop.jar file in the WL_HOME\server\lib directory must be in the CLASSPATH of the WebLogic Server 8.1 implementation.
  • The release 5.1 resource adapter (jms-notran-adp51.rar) and the non-transaction adapter (jms-notran-adp.rar) must be deployed on the 8.1 bridge domain, as described in Deploying the Bridge's Resource Adapters.
  • When configuring the JMS source and target destinations, as described in Configuring JMS Bridge Destinations, do the following:

    In the Adapter JNDI Name field:

    • For the 8.1 destination, specify the non-transaction adapter's JNDI name as eis.jms.WLSConnectionFactoryJNDINoTX.
    • For the 5.1 destination, specify the 5.1 adapter's JNDI name as eis.jms.WLS51ConnectionFactoryJNDINoTX.

    In the Adapter Classpath field:

    • For the 8.1 destination, leave the field blank.
    • For the 5.1 destination, indicate the location of the classes for the WebLogic Server 5.1 release, as well as the location of the jms51-interop.jar file for the 8.1 release.

      For example, if you have WebLogic Server 5.1 GA installed in a directory named WL51_HOME and your WebLogic Server 8.1 release is installed in WL81_HOME, then set the Adapter Classpath as follows for the 5.1 destination:

      WL51_HOME\classes;WL51_HOME\lib\weblogicaux.jar;
      WL81_HOME\server\lib\jms51-interop.jar

      Note: If your implementation is using a 5.1 Service Pack, the corresponding sp.jar files must also be added to the Adapter Classpath field.

  • On the Messaging Bridge - > Configuration - > General tab, select a Quality Of Service of Atmost-once or Duplicate-okay, as described in Configuring a Messaging Bridge Instance.

 

Using the Messaging Bridge to Access a Third-Party Messaging Provider

When configuring a messaging bridge involves interoperability with a third-party messaging provider, configure the following:

  • Before starting WebLogic Server:

    • Supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
    • Include the PATH of any native code required by the provider's client-side libraries in the WebLogic Server system PATH. (This variable may vary depending on your operating system.)
  • In the JMSBridgeDestination instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:

    • Connection URL
    • Initial Context Factory
    • Connection Factory JNDI Name
    • Destination JNDI Name
Note that the messaging bridge cannot provide the "Exactly-once" quality of service when the source and target bridge destinations are located on the same resource manager (that is, when the bridge is forwarding a global transaction that is using the XA resource of the resource manager). For example, when using MQ Series, it is not possible to use the same Queue Manager for the source and target bridge destinations.

For more information on configuring the remaining attributes for a JMS Bridge Destination, see Configuring JMS Bridge Destinations.

 

Managing a Messaging Bridge

Once a messaging bridge is up and running, it can managed from the console.

 

Monitoring All Messaging Bridges

To monitor the status of all configured messaging bridges in your domain:

  1. Expand the Server node.
  2. Select the server instance where the messaging bridges are configured. A dialog displays in the right pane showing the tabs associated with the selected server instance.
  3. Select the Services - > Bridge tab.
  4. Click the Monitor all Messaging Bridge Runtimes text link.
  5. A table displays showing all the messaging bridge instances for the server and their status (either as running or not running).

 

Stopping and Restarting a Messaging Bridge

To temporarily suspend and restart an active messaging bridge:

  1. Expand the Messaging Bridge node.
  2. Select the messaging bridge instance that you want to suspend.
  3. On the Configuration - > General tab, clear the Started check box to suspend the bridge.
  4. To restart the bridge, select the Started check box.

 

Configuring the Messaging Bridge Execute Thread Pool Size

You can configure the default execute thread pool size for your messaging bridges. For example, you may want to increase or decrease the default size to reduce competition from the WebLogic Server default thread pool. Entering a value of -1 disables this thread pool and forces a messaging bridge to use the WebLogic Server default thread pool.

  1. Expand the Servers node.
  2. Select the specific server instance where the messaging bridge is configured.
  3. In the right pane, select the Services - > Bridge tab.
  4. Enter a new value in the Messaging Bridge Thread Pool Size field.
  5. Click Apply to save your changes.

Skip navigation bar  Back to Top Previous Next