Fuse ESB - Configuring and Running Fuse ESB - Introducing Fuse ESB Configuration

OSGi configuration

The OSGi Configuration Admin service specifies the configuration information for deployed services and ensures that the services receive that data when they are active.

A configuration is a list of name-value pairs read from a .cfg file in the InstallDir/etc directory. The file is interpreted using the Java properties file format. The filename is mapped to the persistent identifier (PID) of the service that is to be configured. In OSGi, a PID is used to identify a service across restarts of the container.

Configuration files

You can configure the Fuse ESB runtime using the following files:

Table 3.1. Fuse ESB Configuration Files

Filename	Description
`activemq-broker.xml`	Configures the embedded Apache ActiveMQ broker
`config.properties`	The main configuration file for the container See Setting System and Config Properties for details.
`org.apache.felix.fileinstall-deploy.cfg`	Configures a watched directory and polling interval for hot deployment.
`org.apache.karaf.features.cfg`	Configures a list of feature repositories to be registered and a list of features to be installed when Fuse ESB starts up for the first time. See Configuring Features for more.
`org.apache.karaf.log.cfg`	Configures the output of the log console commands. See Logging Configuration.
`org.apache.karaf.management.cfg`	Configures the JMX system. See Configuring JMX for details.
`org.apache.karaf.shell.cfg`	Configures the properties of remote consoles. For more information see Configuring Remote Instances.
`org.apache.aries.transaction.cfg`	Configures the transaction feature
`org.ops4j.pax.logging.cfg`	Configures the logging system. For more, see Logging Configuration.
`org.ops4j.pax.url.mvn.cfg`	Configures additional URL resolvers
`startup.properties`	Specifies which bundles are started in the container and their start-levels. Entries take the format `bundle`=`start-level`.
`system.properties`	Specifies Java system properties. Any properties set in this file are available at runtime using `System.getProperties()`. See Setting System and Config Properties for more.
`users.properties`	Lists the users who can access the Fuse ESB runtime either remotely or via the web console. The file's contents take the format `username`=`password`,`role`

JBI component configuration

In addition to the container's configuration files, the InstallDir/etc folder may contain a number of configuration files for the JBI components that ship with Fuse ESB.

The component configuration files are named using the scheme org.apache.servicemix.components.ComponentName.cfg. For example, you would configure the JMS component using a file called org.apache.servicemix.components.jms.cfg.

The contents of a component's configuration file is largely component specific. However, each component configuration file contains properties for configuring the thread pool used by the component to process message exchanges. See Configuring JBI Component Thread Pools for details.