Chapter 2. Running the FUSE ESB Runtime in Standalone Mode

The default way for deploying the FUSE ESB runtime is to deploy it as a standalone server. You can deploy the FUSE ESB runtime in standalone mode without doing any special packaging. You start and stop the runtime using a single container.

Setting up your environment

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 do the following:

Add the bin directory of your FUSE ESB installation to the PATH.

Windows

          set PATH=%PATH%;InstallDir\bin

*NIX

          export PATH=$PATH,InstallDir/bin

Add a folder called hotdeploy to the folder from which you intend to start the FUSE ESB runtime.
This folder is the hot deployment folder from which all the JBI components and service assemblies will be loaded.
For more information on hot deployment see Hot Deploying JBI Artifacts.
Copy the desired components from InstallDir/hotdeploy into the new hotdeploy folder.
These components will be automatically available when the FUSE ESB runtime starts. You can add more components as they are needed.
For more information on deploying components see Deploying JBI Components into the FUSE ESB Runtime.

Launching the runtime

If you are launching the FUSE ESB runtime from the installation directory use the following command:

Windows

      bin\servicemix.bat

*NIX

      bin/servicemix

If you are launching it another directory and already performed the steps in Setting up your environment, use the servicemix command.

If the FUSE ESB runtime starts up correctly you should see the following on the console:

Starting Apache ServiceMix ESB: 3.3.0.6-fuse
      
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO  - ConnectorServerFactoryBean     - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO  - JBIContainer                   - ServiceMix 3.3.0.6-fuse JBI Container (ServiceMix) is starting
INFO  - JBIContainer                   - For help or more informations please see: http://incubator.apache.org/servicemix/
INFO  - ComponentMBeanImpl             - Initializing component: #SubscriptionManager#
INFO  - DeploymentService              - Restoring service assemblies
INFO  - JBIContainer                   - ServiceMix JBI Container (ServiceMix) started
INFO  - JDBCAdapterFactory             - Database driver recognized: [apache_derby_embedded_jdbc_driver]
INFO  - LogTask                        - Logging system reconfigured using file: file:/C:/iona/fuse-esb-3.3.0.6/conf/log4j.xml

Problems starting the server

There are two common problems encountered when starting the FUSE ESB runtime:

A java.lang.IllegalArgumentException exception
This is caused by having illegal characters in your class path.
A Port 1099 already in use error
This is caused by another application using port 1099. FUSE ESB uses port 1099 as its default port used by the RMI registry and the JMX connector. You can solve this by either freeing up port 1099, or by configuring the FUSE ESB runtime to use a different port. For information about configuring the FUSE ESB runtime to use a new port see Changing the RMI Port and the JMX URL.