Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.7)
  3. Deploying
  4. Mule High Availability HA Clusters
  5. Evaluating Mule High Availability Clusters Demo

  6. 1 - Installing the Demo Bundle

Installing the Demo Bundle

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.
You can now easily create a cluster through the Runtime Manager UI. See Creating and Managing Clusters.

  1. Ensure that you have installed JDK 7 on your local drive.

  2. Download the Mule HA Demo Bundle - mule-ha-bundle-3.0.zip and unzip it

    Currently Running an Older Version of Mule?

    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 your start a Mule server.

    To empty MULE_HOME in Windows:
    c:/set MULE_HOME=

    To empty MULE_HOME in Mac or Linux:
    $ MULE_HOME=
    $ export MULE_HOME

  3. On your local drive, navigate to the folder which contains your newly downloaded mule-ha-bundle-3.0.zip 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.0/bin folder. From the command line, execute the following scripts one by one in the order in which they are listed.

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

    2. install- sets up the cluster environment

      • creates two Mule servers to form a cluster

      • creates 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 Widget UI 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 chances 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.

How to Run the Scripts

Follow this procedure for each one of the scripts:

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

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

    For example, for Windows, type /users/aaron/downloads/mule-ha-bundle-3.0/bin/clean.bat

    For example, for Mac or Linux, type users/aaron/downloads/mule-ha-bundle-3.0/bin/clean.sh

  3. Wait for your system to complete the script execution. For example, when it has completed executing the startServer1 script, Mule displays the following notification:

    mule_is_kicking

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

See Also