Customizing OSGi Runtime Management

mToolkit allows you to customize remote management of OSGi frameworks - you can configure mToolkit to automatically connect to frameworks which have been already connected by third party Eclipse plug-ins, or to have information about OSGi management logged.

To change mToolkit preferences:

Select Window > Preferences .
Browse the Preferences dialog and locate the mToolkit preferences pages.

Remote Management

Under the Remote Management preference sub-page, if needed use the following options:

To activate automatic connection to OSGi framework instances when a third party plugin opens such a connection, check the Enable OSGi Frameworks automatic connection option. Checked by default.
To activate logging of events in the Error Log view, check the Enable extended logging option. Unchecked by default
To have a bundle automatically started upon install, select Autostart bundles on install. Checked by default.
To have the bundles started on the connected framework with regard to the activation policy in their manifests, select Use activation policy to start bundles. Checked by default.
To view the bundles of a connected framework in the Frameworks view grouped by category, select Group bundles in categories. Checked by default.
To view which bundles on a connected framework are system ones and skip their installation from Eclipse, select Don't show skipped system bundles dialog. Unchecked by default
To have a bundle automatically updated upon installation from Eclipse if its version is identical to the version of a running bundle, select Automatically update bundles on install. Unchecked by default.

Certificates

Under the Certificates sub-page specify the certificates (certificate and private/public key pair) which can be used to sign bundles and deployment packages upon deployment on a connected OSGi framework. Signing is activated individually for each OSGi framework in the relevant settings (see "Adding/Removing an OSGi Runtime").

Use the Add button to specify a signer by keystore type and location, and signer alias within the keystore.

Enter the path to the jarsigner executable of your JDK in the Jar Signer Location text field or use the Browse button to locate it in the file system. It will be used to sign bundles and deployment packages.

Remote Launch

The Remote Launcher sub-page allows you to set a timeout (in seconds) for a connection to a framework as (re)launching the OSGi runtime remotely on a slow device might take more timeout than originally expected. The default setting is 60000 ms. It also allows to set the Debug/profiler attach timeout and the Restart VM timeout.

Image Builder

The Image Builder tab allows us to set up bundle version synchronization when an image is opened inside Eclipse.

Saving Changes

To save the changes made to the mToolkit preferences and options:

To apply the changes and exit the Preferences dialog, click OK.
To apply the changes and to continue using the Preferences dialog for setting specific preferences, click Apply.