The file containing the startup bundles list might be in or outside the framework JAR.

When started the framework locates the startup bundles list file(s) by using the value of the mbs.boot.bootfile system property. In case several startup bundles list files should be used, their paths should be separated with semicolons. Relative paths should be related to the directory where the framework is started which is bin/vms/<vm_name>. The default startup bundles list file is boot.ini placed in the bin/vms directory. This file contains the most important bundles that one may need in the OSGi runtime.

In case you want to have your own bundles loaded on initial framework startup by including them in a startup bundles list file, apply one of the following approaches:

• Define your startup bundles list file as an extension to the boot.ini file – Recommended. Use an extension startup bundles list file to append your bundles to the basic system and service bundles in the boot.ini file placed in the bin/vms folder.

  Specify the path to your extension file by appending it to the value of the EXTBOOTFILE environment variable prior to starting OSGi Runtime. For example:

  Windows:

  set EXTBOOTFILE=%EXTBOOTFILE%;mybundles1.ini;mybundles2.ini

  Linux:

  export EXTBOOTFILE=$EXTBOOTFILE;mybundles1.ini;mybundles2.ini

• Make your startup bundles list file(s) basic by overriding the default one - Use a basic startup bundles list file containing essential system bundles for your platform to override the default startup bundles list file.

  Specify one or more basic startup bundles list files by adding their location to the FWBOOTFILE environment variable prior to starting the OSGi Runtime (you might simply uncomment the variable definition in the bin/vms/server_common script, or include the FWBOOTFILE definition in a script starting with "auto" and placed in the bin/vms/<vm_name> directory). For example:

  Windows:

  set FWBOOTFILE=mybundles.ini

  Linux:

  export FWBOOTFILE=mybundles.ini

For more information on setting system properties by means of OS environment variables, refer to Changing settings.

Do not use a property file, such as common.prs or default.prs, to define a custom startup bundles list file as it will be overridden by the value of the FWBOOTFILE environment variable.