Introduction

This section describes how to run Mule for the first time.

Completing the Installation

The first time you run Mule it will attempt to finalize your installation. This involves two things: presenting a license file for your acceptance and downloading additional libraries.

License Display and Acceptance

If you are starting Mule for the first time, you will either be doing so from the startup scripts in MULE_HOME/bin or an example start script,, such as those in MULE_HOME/examples/ant/hello. In either case, the MuleSource Public License will be displayed, page by page. To advance a page, use the Return key. At the end of the license display, you will be asked whether or not you accept the license file:

Do you accept the terms and conditions of this license agreement [y/n]?

If you type "y" to this question, the startup will proceed. If not, the startup will abort.

Automatic Third-party Jar Download

After you have accepted the license, Mule will download some additional third-party jars required for various components. This step occurs because of distribution restrictions on these jars. This also means that the machine you are running Mule on must have a connection to the Internet. If you are behind a firewall, you may need to configure your HTTP proxy settings in the file $MULE_HOME/conf/wrapper.conf in order for this download to work.

Currently, Mule downloads the following libraries:

All libraries are downloaded from either http://www.ibiblio.org/maven2 or the public Mule dependencies directory on http://dist.codehaus.org/mule/dependencies/maven2. These jars are downloaded to the $MULE_HOME/lib/user or MULE_BASE/lib/user directory (see the Running Mule page for more details on this].

A typical download process will look like this:

Downloading http://www.ibiblio.org/maven2/javax/activation/activation/1.1/activa
tion-1.1.jar ...
done
Downloading http://www.ibiblio.org/maven2/javax/mail/mail/1.4/mail-1.4.jar ...
done

Manual Third-party Jar Download

If your machine does not have access to the internet, you can still find the required jars and manually copy them to your Mule installation. These jars can be found on either of the two download locations mentioned above or any Maven2 repository. Please note the versions used as well as what to rename the jars to, from the table above.

Testing the Installation

Once your script has gone through the installation steps above, Mule should start. Assuming that there were no configuration errors, you should see something similar to the following:

**********************************************************************
* Mule ESB and Integration Platform version 1.4-SNAPSHOT             *
* MuleSource, Inc.                                                   *
* For more information go to http://mule.mulesource.org              *
*                                                                    *
* Server started: Tuesday, January 16, 2007 5:02:39 PM GMT           *
* Server ID: Hello_Sample                                            *
* JDK: 1.4.2_10 (mixed mode)                                         *
* OS: Windows XP - Service Pack 2 (5.1, x86)                         *
* Host: 192.168.11.107                                     *
*                                                                    *
* Agents Running:                                                    *
*   Mule Admin: accepting connections on tcp://localhost:60504       *
**********************************************************************
INFO  2007-01-16 17:02:39,546 [WrapperSimpleAppMain] org.mule.MuleServer: Mule Server initialized.

Mule's AdminAgent default port is 60504. From another window run netstat and search for port 60504.

From a Windows console, type:

netstat -an|find "60504"

OR

From a Unix command shell, type:

netstat -an|grep 60504

Additional Resources

Before using Mule you should take a few minutes to get an understanding of what Mule is and how it works. We recommend the Getting Started Guide guide and once you have installed the distribution try running the Examples, this is a really easy way to get something up and running in Mule and they are fully documented. We suggest you start with the Echo Example and work you way down the list. Also, you can inspect and manage a running Mule instance using [JMX Management], where you can stop and start component and view message processing statistics.