You are viewing an older version of this topic. To go to a different version, use the version menu at the upper-right. +

Installing the Demo Bundle

If you have MULE_HOME [environment variable] set to an older installation of Mule ESB, then the scripts included in this demo bundle will start the old Mule instance instead of the new ones in this bundle. To prevent this from occurring, empty the variable in each new console before you start a Mule sever.

To empty MULE_HOME in Windows:


To empty MULE_HOME in Mac or Linux: c:/set MULE_HOME=

To Run the Scripts in Step 4

  1. Windows: Open the Console.

    Mac: Open the Terminal application (Applications > Utilities > Terminal).

  2. Access the directory and folder into which you downloaded the demon bundle, then direct your system to execute a script.

    For example, for Windows, type /user/aaron/downloads/mule-ha-bundle-3.3.1/bin/startServer1.bat

    For example, for Mac or Linux, type user/aaron/downloads/mule-ha-bundlle-3.3.1/bin/

  3. Wait for you system to complete the script execution. For example, when it has completed executing the startServer1 script, Mule displays a notifications that reads, Mule is up and kicking (every 500ms).

Be sure to run each script in a different console and keep each console open while running the demo.

To Install the Demo Bundle

  1. Ensure that you have installed JDK6 on your computer.

  2. Download the Mule HA Demo Bundle

  3. On your local drive, navigate the folder which contains you newly downloaded file. If your system has not already unzipped the file, unzip it now.

  4. The demo bundle includes six scripts in the mule-ha-bundle-3.3.1/bin folder. Open your Console (PC) or your Terminal application (Mac), then execute the following scripts one-by-one in the order in which they are listed.

    1. clean - cleans the cluster environment to clear out any previous installations of the demo bundle.

    2. install - sets up the cluster environment

      • creates two Mule serves to form a cluster

      • create a third Mule server to run the Mule Management Console

      • creates the WidgetUI Web application to use to apply load to the cluster

      • downloads a play framework required to run the WidgetUI application

    3. startServer1 - starts the first Mule server

    4. startServer2 - starts the second Mule server

    5. startMmc - starts the Mule Management Console server (this may take several minutes)

    6. startWidgetUI - starts the Widget UI Web application

In a production environment, the various cluster components would be distributed across multiple machines, so as to minimize the changes that a single-point hardware or other failure could cause the entire system to crash.

For demonstration purposes, we install and run all the cluster components in this example on a single, local drive.

Next: Creating a Cluster >>