Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.2)
  3. Deploying Mule ESB 3
  4. Deployment Scenarios

  5. Deploying Mule to WebLogic

Deploying Mule to WebLogic

For details on configuring WebLogic JMS in Mule, see WebLogic JMS Integration.

These instructions assume you have downloaded and installed WebLogic Application Server version 10.3. Note that WebLogic 8.x and 9.x are also supported, but these instructions are specific to version 10.3, both on BEA Weblogic and Oracle WebLogic.

NOTE: For an example of Mule running in a webapp under Weblogic, take the webapp example from the standalone distribution and make the changes described above.

Creating a WebLogic Domain for Mule

The first step is to create a WebLogic domain for Mule using the BEA WebLogic Configuration Wizard.

  1. Launch the Configuration Wizard. For example, on Windows choose Start > All Programs > BEA Products > Tools > Configuration Wizard.

  2. In the Welcome screen, select the option to create a new domain and click Next.

  3. In the Select Domain Source screen, select the option to generate a domain for WebLogic Server and click Next.

  4. In the Configure Administrator Username and Password screen, enter the user name and password you want to use, and then click Next.

  5. In the Configure Server Start Mode and JDK screen, select Development Mode, select the Sun SDK 1.5 instead of JRockit, and then click Next.

  6. In the Customize Environment and Services Settings screen, leave No selected and click Next.

  7. In the Create WebLogic Domain screen, enter Mule2 for the domain name, leave the location set to the default user projects domains directory, and then click Create. Note that you can use whatever domain name you like, but the rest of this page assumes the name Mule2.

  8. When the domain has been created, click Done.

Deploying Mule inside of a WebLogic web application:

  1. Required. Override commons-lang as described in 'Overriding commons-lang'.

  2. Configure logging as described in 'Configuring Logging'.

Overriding commons-lang

Mule requires a a newer version of Commons lang.

You must copy the JAR file into your domain’s lib folder and modify your classpath so it is used correctly by Mule and WebLogic.

Be aware that failure to complete this step results in errors which read java.lang.LinkageError or java.lang.ClassCastException.

  1. Copy the commons-lang.jar file from your Mule distribution into <WLHome>/user_projects/domains/<yourdomain>/lib

  2. In the <WLHome>/user_projects/domains/<yourdomain>/bin directory, modify the startWebLogic.sh/.cmd file as follows so that the commons-lang.jar in your lib directory is loaded first. Windows:

DOMAIN_HOME="<WLHome>/user_projects/domains/<yourdomain>"
PRE_CLASSPATH=%DOMAIN_HOME%/lib/commons-lang-2.4.jar;%PRE_CLASSPATH%

Linux/OSX:

DOMAIN_HOME="<WLHome>/user_projects/domains/<yourdomain>"
export DOMAIN_HOME
PRE_CLASSPATH=$DOMAIN_HOME/lib/commons-lang-2.4.jar:$PRE_CLASSPATH
export PRE_CLASSPATH

Configuring Logging

Mule uses Log4j. WebLogic can be configured so that WebLogic’s and Mule’s logging both use log4j.

  1. Copy <WLHOME>/wlserver_10.3/server/lib/wllog4j.jar to <WLHome>/user_projects/domains/<yourdomain>/lib.

  2. Download the Log4j logging file.

  3. Unzip the file and copy log4j.jar to <WLHome>/user_projects/domains/<yourdomain>/lib.

  4. Download the Commons logging file.

  5. Unzip the file and copy commons-loggin.jar to <WLHome>/user_projects/domains/<yourdomain>/lib.

  6. Launch your WebLogic domain and log into the console.

  7. In the left navigation pane, expand Environment and select Servers.

  8. In the Servers table, click the name of the server instance whose logging you want to configure.

  9. Select Logging > General, and click Advanced at the bottom of the page.

  10. In the Logging Implementation list box, select Log4j.

  11. Click Save.

  12. Restart your WebLogic domain to activate the changes.

Deploying Mule

There are many ways to deploy applications to the WebLogic server. These instructions demonstrate the two most common approaches: through auto-deployment, which provides a fast method for deploying for testing and evaluation, and through the Administration console, which provides more control over the configuration. Note that this section also applies when deploying an EAR or WAR that embeds Mule to WebLogic, in which case you deploy the EAR or WAR instead of the RAR file.

To Auto-deploy Mule:

  1. Copy mule-enterprise-jca.rar into the <WLHome>/user_projects/domains/<yourdomain>/autodeploy directory.

  2. Restart your domain server instance in development mode. During the starting process, the new RAR file will be auto-discovered and deployed by the domain server.

To Deploy Mule Using the Administration Console:

  1. Start the WebLogic server. For example, on Windows choose Start > BEA Products > WebLogic Server.

  2. Start the Admin Server for the Mule2 domain. For example, on Windows you would choose Start > BEA Products > User Projects > <yourdomain> > Start Admin Server for WebLogic Server Domain.

  3. When prompted, log in to the console using the user name and password you specified when creating the domain. If you close the console and need to restart it later, you can go to the URL http://localhost:7001/console/console.portal.

  4. In the Domain Structure on the left, click Deployments.

  5. Click Install, and then navigate to the location where you downloaded the Mule RAR file.

  6. Select the RAR file and click Next.

  7. Select Install this deployment as an application

  8. Select Next

  9. Select Finish

  10. In the Change Center on the left, click Activate Change.

Mule is now deployed to WebLogic via the Mule JCA Resource Adapter. You must now replace the default configuration file in the RAR file with the configuration file for your Mule application.

Replacing the Mule Configuration File in the Vanilla RAR

Mule includes a placeholder configuration file called mule-config.xml in the RAR file under mule-module-jca-core.jar. If you simply want to modify this file, you can do the following:

  1. Unpackage the RAR and the JAR file.

  2. Modify the configuration file.

  3. Repackage the JAR and RAR with the updated file and copy the RAR into the <WLHome>/user_projects/domains/<yourdomain>/autodeploy directory.

  4. Run the startWebLogic command.

If you want to use a different configuration file, do the following:

  1. Unpackage the RAR file and copy your configuration file to the top level where all the JAR files are located.

  2. Open the META-INF folder, and then open weblogic-ra.xml for editing.

  3. Immediately after the <enable-global-access-to-classes>true</enable-global-access-to-classes> entry and right before outbound-resource-adapter, add the following lines, where echo-axis-config.xml is the name of your configuration file:

    <properties>
  <property>
    <name>Configurations</name>
    <value>echo-axis-config.xml</value>
  </property>
</properties>

  4. Repackage the RAR file and deploy it by copying it to the autodeploy directory and running startWebLogic.