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.
- Selecting a Profile to Edit
- Exporting a Profile
- Locking a Profile
- Making a Profile Abstract
- Changing a Profile's Parent Profiles
- Editing a Profile's Features
- Editing a Profile's Fuse Application Bundles
- Editing a Profile's Bundles
- Editing the Repositories Available to a Profile
- Editing a Profile's Configuration Properties
- Editing a Profile's System Properties
- Editing a Profile's Configuration Files
A profile is a collection of configuration data that is deployed to one or more containers in a fabric. The profile details page displays all of the data in a way that makes it easy to see and edit a profile. It has tabs for each of the following types of data:
Features—Apache Karaf feature specifications that define a collection of bundles, jars, and other artifacts needed to implement a set of functionality
Fuse Application Bundles—one or more or Fuse Application Bundles to load into a container
Bundles—one or more OSGi bundles to load into a container
Repositories—one or more URIs specifying the location from which the container can download the required artifacts
Config Properties—configuration properties that affect the container's runtime
System Properties—specifies Java system properties that are made available at the beginning of the container's boot process
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 inherit properties from parent profiles. The details page displays a list of all the profiles from which the active profile inherits. Using this list you can add and remove parent profiles.
![[Important]](imagesdb/important.gif) | Important |
|---|---|
Parent profiles are directly linked to their children. If one of the parent profiles is changed, all of the profiles that inherit from it are also affected. |
The details page also has two additional controls that effect how a profile can be used:
Locked—specifies that the profile cannot be edited.
Abstract—specifies that the profile cannot be deployed to a container. An abstract profile is intended for use as the parent profile for other profiles.
![[Warning]](imagesdb/warning.gif) | Warning |
|---|---|
Editing a profile will affect any deployed container that is currently using the selected profile. |
 |  |  |
 |
