This document discusses some common features in managing devices in a programming way. The basic concepts of device management in RM are described in the Device Management Overview, Control Units and Device Representation and Device Management System Architecture conceptual guides.
The main participants in the Device Management System Architecture RM model for management of devices of miscellaneous types are shown in the next figure. Basically, the model is divided in three layers:
Application Layer – Includes applications managing devices and device components visible through RM. Such applications use the Device Manager API to communicate with the Generic Device Manager module and to send requests to target devices.
Management applications can reside in a location remote to RM and can communicate with RM by using the Remote Access Client (RAC). An example of a remote management application over RAC is the RM-enabled console. The other option is that the management application resides on a backend framework and uses directly the available application OSGi-compliant services.
Refer the Managing Devices and Device Components for information about calling devices from management applications.System Layer – Includes the parts, composing the Generic Device Manager. The part of the Generic Device Manager responsible for communication with the Application Layers resides in the control center and on the remote access servers of the system. The part of the Generic Device Manager in charge of the interaction with the Device Root Control Unit Providers and the Component Control Unit Providers from the Provider Layer resides in management servers. The RAS-part and the MS-part communicate data with each other over the RM RPC Service.
Provider Layer – Includes Device Root Control Unit Providers representing devices in RM and Component Control Unit Providers representing components of plugged device types. Providers communicate with the RM system through the Generic Device Manager, which maps requests from the Application Layer to the proper providers over the Control Unit Provider SPIs.
Refer to the Adding New Device and Component Types for information about calling devices from management applications.
