The default way for deploying the Fuse ESB runtime is to deploy it as a standalone server with an active console. You can also deploy the runtime to run as a background process without a console.
You can start the Fuse ESB runtime from the installation directory without doing any work.
However, if you want to start it in a different folder you will need to add the
bin directory of your Fuse ESB installation to the PATH
environment variable, as follows:
Windows
set
PATH=%PATH%;InstallDir\bin
*NIX
export
PATH=$PATH,InstallDir/bin
If you are launching the Fuse ESB runtime from the installation directory use the following command:
Windows
bin\servicemix.bat
*NIX
bin/servicemix
If Fuse ESB starts up correctly you should see the following on the console:
____ _ __ __ _
/ ___| ___ _ ____ _(_) ___ ___| \/ (_)_ __
\___ \ / _ \ '__\ \ / / |/ __/ _ \ |\/| | \ \/ /
___) | __/ | \ V /| | (_| __/ | | | |> <
|____/ \___|_| \_/ |_|\___\___|_| |_|_/_/\_\
Apache ServiceMix (4.4.1-fuse-00-08)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
karaf@root>Launching in server mode runs Fuse ESB in the background, without a local console. You would then connect to the running instance using a remote console. See Connecting and Disconnecting Remotely for details.
To launch Fuse ESB in server mode, run the following
Windows
bin\servicemix.bat server
*NIX
bin/servicemix server
Alternatively,
you can launch Fuse ESB in server mode using the start script in the
InstallDir/bin
In production environments you may want to have a runtime instance accessible using only a local console. In other words, you cannot connect to runtime remotely. You can do this by launching the runtime in client mode using the following command:
Windows
bin\servicemix.bat client
*NIX
bin/servicemix client
 |  |  |
 |
