A profile is a collection of related configuration data that can be deployed to a container. Profiles can inherit from other profiles. It contains details about Apache Karaf features to be loaded, OSGi bundles to be loaded, settings that customize the runtime behavior, and repositories where the required artifacts are stored.
A profile is a collection of configuration data that is deployed to one or more containers in a fabric. It contains details about:
Features—Apache Karaf feature specifications that define a collection of bundles, jars, and other artifacts needed to implement a set of functionality
Bundles—one or more OSGi bundles or Fuse Application Bundles to load into a container
Repositories—one or more URIs specifying a location from which the container can download the required artifacts
Config Files—one or more configuration files that will be loaded by the container's OSGi admin service and applied to the services running in the container
A profile can also inherit properties from parent profiles. The settings in the child profile are added to the settings from all of the parents. If there is a conflict between a parent setting and the child settings, the child's settings take precedence. This makes it easy to create default configurations for all of your containers and then only make minor changes for specific instances. For example, you could define a global security profile that every container is required to use. The security profile would be a parent to all other profiles in the fabric.
![[Important]](imagesdb/important.gif) | Important |
|---|---|
Parent profiles are directly linked to their children. If one of the parent profiles are changed, all of the profiles that inherit from it are also effected. |
![[Warning]](imagesdb/warning.gif) | Warning |
|---|---|
Editing a profile will effect any deployed container that is currently using the selected profile. |
 |  |  |
 |
