com.prosyst.mbs.framework.launch.bootdelegation.default

javax.*,org.ietf.jgss,org.omg.*,org.w3c.*,org.xml.*,sun.*,com.sun.*

In case framework is started through framework launcher, this property specifies the default boot delegation value.

It works only if JVM vendor is Oracle/Sun.

In case org.osgi.framework.bootdelegation is not configured, the value of this property will be assigned.

mbs.disableBootDelegation.VMProfile

false

if set to true disables loading of org.osgi.framework.bootdelegation property from JVM profile files

mbs.boot.disableProcessing

false

If true, disables the use of the Boot module at framework startup.

mbs.boot.bootfile

boot.ini

Sets the path to one or more startup bundles list files, containing instructions for installing specific bundles at framework startup. If several startup bundles list files are to be used, their paths should be separated with semi-commas. If the path is relative, it should start from the directory the framework will be launched from.

mbs.boot.always

false

Specifies if the framework should always call the Boot module nevertheless there may be a ready storage to load installed bundles from.

mbs.boot.merge

false

Turns on/off merging the content of the startup bundles list files specified as value of the mbs.boot.bootfile property. This property is useful in cases of startup bundles list files whose bundles have dependencies across the startup bundles list files.

mbs.boot.extension

–

Sets the name of the boot extension class implementing the com.prosyst.mbs.framework.boot.Boot interface.

mbs.framework.parallelCapableClassLoaders

true

Parallel class loading is enabled by default. With this system property you can switch back to old behavior, by setting it to false.

mbs.prs.name

default.prs;../common.prs

Specifies the name of the file to load system properties from. It can be the name of a resource file from serverXxx.jar, or a file from the file system.

mbs.startlevel

5

Indicates the active start level of the framework. Only bundles with start levels less or equal to the active level are started.

mbs.threads.stacksize

0

(JVM Default stacksize is used)

Sets the stacksize (in Megabytes) of threads which are created by the com.prosyst.util.common.ThreadUtils class, used by the Framework and some core osgi bundles. More information on threads and stacksize may be found here.

mbs.initialBundleStartLevel

1

The start level that a bundle will receive upon installation in the framework. If the property is not specified, then the bundle will have a start level equal to the maximum start level from the boot INI incremented with 1 (<boot_ini_max_level>+1).

mbs.applicationBundleStartLevel

-

Sets the minimum start level for application bundles so as to allow the framework differentiate between system bundles and applications. If the property is not specified, the minimum start level for application bundles is the maximum start level from the startup bundles list file incremented with 1 (<boot_ini_max_level>+1). That is, by default all bundles installed from the startup bundles list file are considered as system bundles, and all bundles installed afterwards are considered as application bundles.

mbs.startup.delay

0

Specifies the time in milliseconds the framework should wait before startup.

mbs.watchdog

true

Turns on/off the watchdog feature of the framework.

mbs.server.jar

–

Specifies the JAR file containing the framework implementation. Used by the Framework Loader.

mbs.exit.novmshutdown

false

If true, disables terminating the JVM process (i.e. System.exit() will not be called) when stopping framework.

mbs.sysPropsToUnite

mbs.syspackages, org.osgi.framework.bootdelegation,org.osgi.framework.system.packages

Contains a comma-separated list of the system properties whose values will be accumulated by the OSGi framework.

mbs.start.notify.file

–

Specifies the absolute path to an empty file, which the framework will create when it completes its startup, that is, when the System Bundle enters the ACTIVE state. The file will be deleted when the framework is shut down. By checking for this file an external process will know of a successful framework start.

mbs.keystore.cache.location

${mbs.storage.root}/data/0

The user may specify the folder, when .keystore file is cached/stored by the certificate manager. If not set, the storage folder of the system bundle is used.

mbs.storage.cleanIfCorrupted

false

If set to true and the framework startup fails due to corrupted storage files(f.st, bini.st, sl.st), the framework will automatically cleanup the storage folder and then start. By default this is NOT enabled