Configuring a Weblogic JMS Bridge for testing

JMS Messaging Bridge Configuration in Domain

In this sample we use “jms-notran-adp” which is the default adapter created for JMS Messaging Bridge with default QOS selected as “Exactly-Once”.

Configure WebLogic domain with the following configuration:

  1. One Admin Server and One Managed server
  2. 1 JMS server targeted to Admin, and another targeted to Managed server
  3. Create a JMS Module targeted to the Admin Server. Inside this JMS module create below resources.
    1. JMS Connection Factory (default targeting)
    2. JMS Sub Deployment targeted to JMS server which is targeted to Admin Server
    3. JMS Queue targeted to Sub Deployment created in the above step.
  4. Create a JMS Module targeted to the Managed Server. Inside this JMS module create the following resources:
    1. JMS Connection Factory (default targeting)
    2. JMS Sub Deployment targeted to JMS Server which is targeted to Managed Server
    3. JMS Queue targeted to JMS Sub Deployment created in above step
  5. Create a JMS Bridge Destination for the Admin Server Queue with the following details. For creating a JMS Bridge Destination, click on the left Panel in the console and go to Services -> Messaging -> Bridges.
    1. Leave Adapter JNDI default name as is to “eis.jms.WLSConnectionFactoryJNDINoTX” and Intial Context Factory as default to “weblogic.jndi.WLInitialContextFactory”
    2. For Connection URL specify the t3 listen address of the Admin server, e.g., t3://localhost:7001.
    3. For Connection Factory JNDI Name specify the Connection Factory JNDI Name which is part of JMS Module targeted to Admin Server.
    4. For Destination JNDI Name select JMS Queue JNDI name which is part of JMS Module targeted to Admin Server.
    5. Select Destination Type as “Queue”.
  6. Create the JMS Bridge Destination for the Managed Server Queue same as above steps. Below are details.
    1. Leave Adapter JNDI name as is as default to “eis.jms.WLSConnectionFactoryJNDINoTX” and Initial Context Factory as default to “weblogic.jndi.WLInitialContextFactory”
    2. For Connection URL specify the t3 listen address of the Managed server, e.g. t3://localhost:7002
    3. For Connection Factory JNDI Name specify the Connection Factory JNDI Name which is part of JMS Module targeted to Managed Server
    4. For Destination JNDI Name select JMS Queue JNDI name which is part of JMS Module targeted to Managed Server
    5. Select Destination Type as “Queue”
  7. Now we will configure JMS Messaging Bridge which will pick up the messages from JMS Queue on Managed Server and will forward them to JMS Queue on Admin Server. For this we have to select source destination of JMS Bridge as Managed server Queue and target destination as Admin Server queue. Create JMS Messaging Bridge with below details.
    1. Select “Started” checkbox when creating JMS Bridge
    2. For “Existing Source Destination” select the JMS Bridge Destination created for Managed server in above step 6).
    3. Leave Messaging Provider as is to default as “WebLogic Server 7.0 or higher”
    4. For “Existing Target Destination” select the JMS Bridge Destination created for Admin server in above step 5).
    5. Target the Messaging Bridge to Managed server.
    6. Once Messaging Bridge is created click on it and select checkbox for “QOS Degradation Allowed” and save the changes.
  8. After above configuration you will see a “jms-notran-adp” resource adapter deployed on the Managed Server which is used by JMS Messaging Bridge. Restart your Domain Admin and Managed Server after above configuration.

Validating JMS Bridge Configuration

Once the JMS Bridge Configuration is complete using the above steps and the servers are restarted, login to console to check the JMS Messaging Bridge Status.

From the Administration console, click on JMS Messaging Bridge and go to Monitoring tab. The state of Bridge should be reported as “Active” and Description as “Forwarding messages.” This means that the JMS Bridge configuration is successful, up and active in forwarding messages. In this sample use case, JMS Bridge targeted to Managed server is picking messages from Managed Server JMS Queue and forwarding them to Admin Server JMS Queue.

Leave a Reply