Terminology

Mobile Device – device supporting the OMA Device Management (DM) protocol.

Purpose

The RM Mobile Device Management Package provides rather middle-ware services than ready-to-use end-user features for management of arbitrary OMA DM devices. That is, in order to achieve full-featured device management of particular class of OMA DM enabled devices, RM must be provided with the appropriate configurations and/or custom extensions, which correspond to the management model supported by the concrete device class. For example, the RM OSGi Mobile DM Package steps on the Mobile DM package and provides the needed extensions for managing of devices supporting the OSGi Mobile specification. Respectively, system integrators and developers may configure and extend the features of the RM Mobile DM system for management of other OMA DM device types.

Functions

  • Generic representation and management of OMA DM devices

  • Powerful and flexible mechanism for integration of miscellaneous classes of mobile devices

  • Component download and update on mobile devices

  • Support for J2ME MIDlets, Opera and W3C widgets in the Software Repository

Lock and Wipe Management Object

The Mobile Device Management Package contains support for the Lock and Wipe Management Object. It is configured to work with OMA DM enabled devices that support Lock And Wipe Management object, but you can change the syncml/dmtm/mprm.generic.oma-dm.device_LAWMO.xml CU-DMTM file and the other related files so as to fit your device type.

Firmware Update Management Object (FUMO)

The Mobile Device Management Package contains support for Firmware Update Management Object. It is configured to work with OMA DM enabled devices that support FUMO Management object, but the syncml/dmtm/mprm.generic.oma-dm.device_FUMO.xml CU-DMTM file and the other related files can be changed properly, so as to fit any custom device types. The current supported action is only DownloadAndUpdate on existing FUMO node.

Package Dependencies

The Mobile Device Management Package requires the System Package, Generic Device Management Package and Software Repository Package for its correct operation. Some extra features of the package, like service management, require the Service and Subscription Management Packages, but it is not crucial for the overall performance of the package. The dependencies of the Mobile Device Management Package are shown below:


Directory Structure

Directory

Sub-Directory

Description

lib

/api/omadm-api.jar

The public API of the RM Mobile Device Management Package, which may be used for compilation of custom applications.

/rac/omadm-rac

Remote Access Client library of the RM Mobile Device Management Package. Provides remote connectivity and Java API to the RM servers.

licenses

/Mobile Device Management

Holds the license agreement of the package.

packages

/omadm

Contains bundles for managing Mobile devices, installed on the backend