Configuring Mule as a Windows Service

In Mule 3.8.0, the Tanuki wrapper was upgraded to a newer version, implying a change to the certificate by which the wrapper is signed. See Mule 3.8.0 release notes concerning Tanuki Wrapper upgrade for details on resolving compatibility issues.

To install Mule as a Windows Service, type:

mule install

To remove Mule from your server, type:

mule remove

After you install Mule as a service, you can start, stop, and restart Mule:

mule [start|stop|restart]

Note: When windows restarts, the Mule service stops the same way as using the mule stop command. The only situation that this could be different is if Windows kills the process due to a timeout.

You can also use the Windows net utility:

net [start|stop] mule

Adding Properties to wrapper.conf File After Installation

Properties that are defined after the installation of the Mule as a Windows service in the wrapper.conf file can be overridden by properties generated in the wrapper.additional.conf file.

There are different behaviors for:

Mule Community Edition Properties
Mule Enterprise Edition Properties

Mule Community Edition Properties

In Mule CE:

After adding a new property, reinstall or restart the Windows Service.
Add the property and ensure that its index is greater than the greatest index in the wrapper-additional.conf file. Otherwise, your property can be overridden.

For example if the wrapper-additional.conf has the property:

wrapper.java.additional.n=-Dproperty=value

When n is the greatest index, you should add your property in the wrapper.conf file incrementing the index:

wrapper.java.additional.n+1=-DyourProperty=valueOfYourProperty

Mule Enterprise Edition Properties

In Mule EE:

By default, you can add 20 extra properties after installing Mule as a Service.
Configure the number of extra properties you need, using the following command line argument when you install the service:

-additionalJavaProperties=numberOfExtraProperties