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

Introducing Fuse ESB Enterprise 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 Enterprise runtime using the following files:

Table 2. Fuse ESB Enterprise Configuration Files

Filename	Description
`activemq.xml`	Configures the defaultApache ActiveMQ broker in a Fabric (used in combination with the `org.fusesource.mq.fabric.server-default.cfg` file).
`config.properties`	The main configuration file for the container See Setting OSGi Framework and Initial Container Properties for details.
`keys.properties`	Lists the users who can access the Fuse ESB Enterprise runtime using the SSH key-based protocol. The file's contents take the format `username`=`publicKey`,`role`
`org.apache.aries.transaction.cfg`	Configures the transaction feature
`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 Enterprise starts up for the first time.
`org.apache.karaf.features.obr.cfg`	Configures the default values for the features OSGi Bundle Resolver (OBR).
`org.apache.karaf.jaas.cfg`	Configures options for the Karaf JAAS login module. Mainly used for configuring encrypted passwords (disabled by default).
`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 a Container for Remote Access.
`org.apache.servicemix.jbi.cfg`	Configures the shutdown timeout for the JBI container.
`org.apache.servicemix.nmr.cfg`	Configures the default thread pool settings for JBI. See Old Mechanism not supported.
`org.apache.servicemix.components.Name.cfg`	Configures the thread pool settings specifically for the `Name` JBI component. See Old Mechanism not supported.
`org.fusesource.bai.agent.cfg`	Configures the Fuse BAI (Business Activity Insight) feature, if it is installed.
`org.fusesource.fabric.fab.osgi.url.cfg`	Configures the Maven repositories used by the Fuse Application Bundle (FAB) runtime when downloading artifacts. If the properties in this file are not set, FAB defaults to the values in `org.ops4j.pax.url.mvn.cfg`.
`org.fusesource.fabric.maven.cfg`	Configures the Maven repositories used by the Fabric Maven Proxy when downloading artifacts, (The Fabric Maven Proxy is used for provisioning new containers on a remote host.)
`org.fusesource.mq.fabric.server-default.cfg`	Configures the defaultApache ActiveMQ broker in a Fabric (used in combination with the `activemq.xml` file).
`org.jclouds.shell.cfg`	Configures options for formatting the output of `jclouds:*` console commands.
`org.ops4j.pax.logging.cfg`	Configures the logging system. For more, see Logging Configuration.
`org.ops4j.pax.url.mvn.cfg`	Configures additional URL resolvers.
`org.ops4j.pax.web.cfg`	Configures the default Jetty container (Web server). See Securing the Web Console in Security Guide.
`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 Enterprise runtime either remotely or via the web console. The file's contents take the format `username`=`password`,`role`

Configuration file naming convention

The file naming convention for configuration files depends on whether the configuration is intended for an OSGi Managed Service or for an OSGi Managed Service factory.

The configuration file for an OSGi Managed Service obeys the following naming convention:

<PID>.cfg

Where <PID> is the persistent ID of the OSGi Managed Service (as defined in the OSGi Configuration Admin specification). A persistent ID is normally dot-delimited—for example, org.ops4j.pax.web.

The configuration file for an OSGi Managed Service Factory obeys the following naming convention:

<PID>-<InstanceID>.cfg

Where <PID> is the persistent ID of the OSGi Managed Service Factory. In the case of a managed service factory's <PID>, you can append a hyphen followed by an arbitrary instance ID, <InstanceID>. The managed service factory then creates a unique service instance for each <InstanceID> that it finds.

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 Enterprise.

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.

Comments powered by Disqus