Running

ServiceMix comes with a server that you can either embed in Spring or Geronimo or you can run the server as a stand alone process. To run ServiceMix in standalone mode, get a binary download of ServiceMix and type the following commands in a terminal

cd bin
servicemix

You should now have ServiceMix running with a sample configuration.

When the server is running, whether embedded or as a stand alone service you should be able to use a JMX Console to monitor the statistics and state of the server.

Overview of the example configuration

The default example runs an embedded ActiveMQ message broker, a JCA Container and a transaction manager (JOTM) together with some simple example components which consume JMS messages using the JCA container.

The example components set off a timer to send messages to a source destination. Then those messages are consumed by another component and sent to a different output destination - along with a trace component displaying the output messages as they arrive. This demonstrates a simple JMS bridge in action along with timers and tracing. There are many more components available to use in ServiceMix.

Deploying new JBI deployment units

JBI defines a collection of different JBI deployment units (components, service units etc). ServiceMix supports these and allows hot deployment of these at runtime. You can use the Ant Tasks for these along with the Management features.

Another option is to drop the jars or zips into the $SERVICEMIX_HOME/install directory and they will be auto-deployed. See the BPEL support for an example JBI deployment unit help page.