Configuring the Initial Features in a Standalone Container

The first time you start a standalone container, the container looks in the etc/org.apache.karaf.features.cfg file to discover the feature URLs (feature repository locations) and to determine which features it will load. By default, Fuse ESB Enterprise loads a large number of features and you may not need all of them. You may also decide you need features that are not included in the default configuration.

	Fabric Containers
	The features loaded by a Fabric Container are controlled by the container's profiles. Changing the values as described below will have no effect on a Fabric container.

The values in etc/org.apache.karaf.features.cfg are only used the first time the container is started. On subsequent start-ups, the container uses the contents of the InstallDir/data directory to determine what to load. If you need to adjust the features loaded into a container, you can delete the data directory, but this will also destroy any state or persistence information stored by the container.

For more on features and how they are used in Fuse ESB Enterprise, see Deploying Features in Deploying into the Container.

By default, Fuse ESB Enterprise installs a large number of features, including some that you may not want to deploy.

You can change the initial set of installed features by editing the featuresBoot property.

Fuse ESB Enterprise registers a number of URLs that point to feature repositories on start-up. You can change the initial set of feature URLs by editing the featureRepositories property.