Configuring Mule as a Windows Service
|MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.|
|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:
To remove Mule from your server, type:
After you install Mule as a service, you can start, stop, and restart Mule:
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 [start|stop] mule
Properties that are defined after the installation of the Mule as a Windows service
wrapper.conf file can be overridden by properties generated in the
There are different behaviors for:
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.conffile. Otherwise, your property can be overidden.
For example if the wrapper-additional.conf has the property:
When n is the greatest index, you should add your property in the
wrapper.conffile incrementing the index: