...
ServiceMix uses XML configuration files. From 2.0 of ServiceMix onwards we use the XBean library to do the XML configuration; which allows you to use regular Spring configuration or our custom XSD based XML configuration.
...
ServiceMix has a number of parameters that you can set to change it's runtime behaviour on either the JBIContainer or the derived SpringJBIContainer .
These are as follows:
| Info |
|---|
| title | Key Attributes |
|---|
| borderStyle | solidbgColor='lighblue' |
|---|
|
Name | type | Description |
|---|
name | String | name of the container - needs to be unique if running in a cluster The default is defaultJBI | rootDir | String | the path to the directory structure used by ServiceMix - the default is <current directory>/wdir | flowName | String | one of seda, st, jms or jca - see NMR Flows | useMBeanServer | boolean | if true, ServiceMix will try and find an MBeanServer from the MBeanServerFactory if one is not supplied | createMBeanServer | boolean | if true, ServiceMix will create it's own MBeanServer if one is not supplied to the container or found from an MBeanServerFactory | installationDirPath | String | the path to the installation directory that ServiceMix can optionally monitor for new component archives | monitorInstallationDirectory | boolean | if true, ServiceMix will monitor the installation directory for new component archives to install | deploymentDirPath | String | the path to the deployment directory that ServiceMix can optionally monitor for new service assembilies | monitorDeploymentDirectory | boolean | if true, ServiceMix will monitor the deployment directory for new service assembilies to deploy | dumpStats | boolean | if true, ServiceMix will dump message throughput statistics to file for individual components | statsInterval | int | interval (in seconds) between collection of statistics for message throughput | rmiPort | int | the port used for the rmi registry (and thus, the JMX connector), defaults to (1099) | |
|
...
