11. Configuration
Prev |  | Next

## 11. Configuration

You use configuration files in the `$SERVER_HOME/config` directory to configure Virgo. You can also configure the OSGi framework using files in `$SERVER_HOME/lib`. This section divides the configuration of the server into the following high-level tasks:

- Configuring the OSGi framework

- Configuring framework extensions and fragments on the system bundle

- Configuring serviceability

- Configuring the local provisioning repository

- Configuring the hosted repository

- Configuring the kernel and User Region

- Configuring the embedded Tomcat servlet container

- Configuring the web integration layer

- Configuring the embedded Jetty servlet container

## 11.1 Configuring the OSGi Framework

This section provides information about configuring the OSGi framework by updating the following files in the `$SERVER_HOME/lib` directory:

Table 11.1. OSGi Framework Configuration Files

Property File | Description
--- | ---
`org.eclipse.virgo.kernel.launch.properties` | Configures OSGi framework properties.
`java6-server.profile` | Configures the OSGi framework profile.

### Configuring OSGi Framework Properties

You specify the framework properties in the `$SERVER_HOME/lib/org.eclipse.virgo.kernel.launch.properties` file. The properties most relevant to users are described in the following table.

WARNING: We strongly recommend that you update only the `org.eclipse.virgo.suppress.heap.dumps` property; updating the other properties could cause Virgo to fail. These properties are documented for your information only.

Table 11.2. Framework Properties

Property | Description
--- | ---
`launcher.bundles` | This property lists the bundles that comprise the kernel using `file:` URIs. Bundles to be started are tagged with a trailing `@start`.
`org.eclipse.virgo.suppress.heap.dumps` | Set to 'false' by default this property will prevent heap dumps being contributed to dumps taken during a First Failure Data Capture (FFDC) event. When the heap dumps are produced they will be located along with the other dump artifacts in the `$SERVER_HOME/serviceability/dump/` folder.
`osgi.java.profile` | Specifies the profile to use using a `file:` URI with default value `file:lib/java6-server.profile`.

### Configuring OSGi Framework Profile

You specify the framework profile in the `$SERVER_HOME/lib/java6-server.profile` file. The properties most relevant to users are described in the following table.

WARNING: We advise you not to change the framework profile unless you are sure you know exactly what you are doing; updating the profile could cause Virgo to fail.

Table 11.3. Framework Profile Properties

Property | Description
--- | ---
`org.osgi.framework.bootdelegation` | This property specifies the packages which are loaded by delegation to the application class loader. Bundles can load classes belonging to these packages without importing the packages. The `.*` wildcard matches any package suffix. `java.*` is always boot delegated and must not be specified in this property. A common reason for adding packages to this property is to run Virgo under a performance profiler.
`org.osgi.framework.system.packages` | This property specifies the packages which are exported by the system bundle. Although the system bundle is typically imported into the User Region, any additional packages will not be visible in the User Region unless you also import them using the `packagedImports` property. See Configuring the User Region for instructions. It is very occasionally necessary to extend the set, for example when configuring email logging appenders since the implementation of `javax.mail` is intimately related to the implementation of `javax.activation`. To make the corresponding classes available for loading, the relevant JAR file(s) should be placed in `$SERVER_HOME/lib` so that they will be added to the application class path.

Prev |  | Next
10.2 Undeploying Artifacts | Home | 11.2 Configuring Framework Extensions and Fragments on the System Bundle