THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
You should now have ServiceMix running with a sample basic configuration - but no components.
For configuration options - see 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
...
Another option is to drop the jars or zips component archives into the $SERVICEMIX_HOME/install directory and they will service assembilies into the $SERVICEMIX_HOME/deploy directory for them to be auto-deployed. See
| Info |
|---|
...
example uses auto-deployment. |