devicem.attachment.timeout

Attachment Timeout [ms]

int

30000

Defines the timeout in milliseconds for performing the device attachment procedure - if a device attachment procedure is not completed after this timeout has passed, the device manager kills the engaged attachment threads and starts a new one for attaching another devices. Possible values are between 1 000 and 300 000 ms. Default is 30 000 ms.

devicem.check.dirty.drivers

Check Dirty Drivers Configuration Property

boolean

true

When true, makes the device manager check the drivers, previously installed. This is done once on every [re]start of the device manager bundle (restart of the framework). If some of these drivers becomes idle, the device manager will uninstall it. Otherwise, the idle driver will remain installed.

devicem.check.locators.identical.drvid

Check Locators

boolean

false

Deprecated. Use devicem.uninstall.driver_id.driver instead.

DriverLocator's method loadDriver(String id) returns an InputStream object that can be used to download the bundle containing the Driver service as specified by the driver ID argument. Once this bundle is downloaded and installed in the framework, it must register a Driver service with the DRIVER_ID property set to the value of the String argument.

When this property is true, makes the device manager check the DRIVER_ID properties. If they are not identical, the corresponding driver bundle is uninstalled. Otherwise, the device manager does not perform this check.

devicem.idle.timeout

Idle Timeout [ms]

int

10 000

Defines the timeout in milliseconds for the attachment thread to wait for devices, candidates for attachment. If this timeout passes without a device, which needs attachment to appear, the device manager stops the attachment threads in order to free resources. Possible values are between 1 000 and 300 000 ms.

devicem.idledriver.uninstall.timeout

Idle Drivers Uninstall Timeout [ms]

int

100 000

Indicates how long the device manager should wait to uninstall an idle driver bundle - as the device manager uninstalls the bundles that it has installed and are idle, sometimes removing driver bundles too soon, however, may cause unnecessary installs and delays when the same driver bundles are needed again. Minimum is 0 ms, default is 100 000 ms.

devicem.uninstall.driver_id.driver

Uninstall Wrong DRIVER_ID Drivers

boolean

false

DriverLocator's method loadDriver(String id) returns an InputStream object that can be used to download the bundle containing the Driver service as specified by the driver ID argument. Once this bundle is downloaded and installed in the framework, it must register a Driver service with the DRIVER_ID property set to the value of the id argument of the loadDriver method.

When this property is true, it makes the device manager check the DRIVER_ID properties. If they are not identical, the corresponding driver bundle is uninstalled. Otherwise, the device manager will not perform this check. Default is false.

devicem.unlog.attachments

Device Manager Unlog Attachment Property

boolean

true

When true (the default value), defines that the attachments for a device should be deleted from the database when the corresponding device becomes idle. Otherwise, when the property is false, the attachment information is constantly preserved, which may lead to problems mainly during driver development.