Concepts

Configuration via default.prs

The OSGi-compliant framework uses system properties, set prior to its startup, to tune its boot and runtime behavior. You can use the default.prs property file for setting system properties on your own and applying them on framework startup on a specific JVM. The state of the system properties can survive framework restart.

For more detailed information on system properties, please refer to the "System Properties" document from the OSGi Runtime documentation.

mToolkit provides functionality for editing the system properties of the default.prs on connected runtime straight from the development environment of Eclipse. In this way, you can configure the OSGi environment in situations where you do not have other access to it except through mToolkit from Eclipse.

Configuration via Startup Add-On

The OSGi Runtime is capable launching setup data in addition to its main settings, i.e. to the JVM-specific server script and default.prs, via a startup add-on. Through this feature you can configure the behavior of the OSGi environment from within Eclipse without the need of direct access to the host device.

A startup add-on contains the following components saved to the bin/vms/<vm_name> folder of the OSGi runtime image:

• A system properties file addon.prs, which will contain system properties definitions in addition to those already defined in the runtime image. For more details on setting system properties refer to the "OSGi Overview" and "Changing Settings" guides.

  If the default settings already contain system properties from addon.prs, then those from addon.prs will be taken into account.

• An additional startup bundles list file, addon.ini, for extending the set of bundles loaded by default at runtime clean startup. Refer to the "Customizable Boot Module" document from the OSGi Runtime documentation for more details on "startup bundles list files".
• A shell script, addon.bat for Windows and addon for Linux, which will instruct the runtime to use addon.prs and addon.ini in addition to the predefined settings of the runtime image. You can also place environment variable settings or shell commands in the script. Refer to the "Environment Variables" guide for a list of supported environment variables.

Once you populate the files building the startup add-on, restart the OSGi platform.

After framework restart, the mToolkit will be disconnected from the OSGi runtime. It is necessary to connect to the framework manually.

As at the default bundle configuration does not contain the mToolkit IAgent, to be able to connect the OSGi platform to Eclipse after a clean launch, you might include the IAgent bundles in the addon.ini.