Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.3)
  3. Reference Materials for Mule ESB 3
  4. Transports Reference
  5. JMS Transport Reference

  6. WebLogic JMS Integration

WebLogic JMS Integration

If you are using a WebLogic version prior to 10.3, copy the weblogic.jar file to $MULE_HOME/lib/user. For WebLogic versions 10.3 and up, you must generate a wlfullclient.jar file from your WebLogic installation as follows:

  1. Go to the server/lib directory of your WebLogic installation.

  2. Run this command to generate the client JAR:

    java -jar wljarbuilder.jar

  3. Copy the generated wlfullclient.jar file to the $MULE_HOME/lib/user directory.

JNDI destinations syntax

If Mule fails to look up topics or queues in WebLogic’s JNDI, but the JNDI tree lists them as available, try replacing JNDI subcontext delimiters with dots, so tracker/topic/PriceUpdates becomes tracker.topic.PriceUpdates.

Configuration for WebLogic 8.x and Earlier

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:spring="http://www.springframework.org/schema/beans"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:jms="http://www.mulesoft.org/schema/mule/jms"
    xsi:schemaLocation="
      http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/3.0/mule.xsd
      http://www.mulesoft.org/schema/mule/jms http://www.mulesoft.org/schema/mule/jms/3.0/mule-jms.xsd">

    <jms:connector name="jmsConnector"
                   jndiProviderUrl="t3://localhost:7001"
                   connectionFactoryJndiName="javax.jms.QueueConnectionFactory"
                   jndiDestinations="true"
                   forceJndiDestinations="true"
                   jndiInitialFactory="weblogic.jndi.WLInitialContextFactory"
                   specification="1.0.2b"/>

Configuration for WebLogic 9.x

For WebLogic 9.x, the configuration is almost the same. The only differences are:

  • Supported JMS specification level is 1.1 (1.0.2b should still work, however)

  • The unified JMS connection factory can be used as a result of the above. The following example demonstrates using the default factories available out of the box.

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:spring="http://www.springframework.org/schema/beans"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:jms="http://www.mulesoft.org/schema/mule/jms"
    xsi:schemaLocation="
      http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/3.0/mule.xsd
      http://www.mulesoft.org/schema/mule/jms http://www.mulesoft.org/schema/mule/jms/3.0/mule-jms.xsd">

    <jms:connector name="jmsConnector"
                   jndiProviderUrl="t3://localhost:7001"
                   connectionFactoryJndiName="weblogic.jms.ConnectionFactory"
                   jndiDestinations="true"
                   forceJndiDestinations="true"
                   jndiInitialFactory="weblogic.jndi.WLInitialContextFactory"
                   specification="1.1"/>