This guide shows you how to track a com.prosyst.mbs.services.da.DeviceAdmin service and how you can use the main functionality of this service of creating and removing devices and obtaining information about available protocol adapters.
General Principles
The DeviceAdmin is based on the Functional Item Management specification. You can learn more about it on the Developer Guide section. The DeviceAdmin extends FunctionalItemFactory and FunctionalItem. There are some additional restrictions related to them:
com.prosyst.mbs.services.da.Device.The following table describes the functional property of the DeviceAdmin:
Property |
Access |
Property Class |
Description |
|---|---|---|---|
|
RE |
|
Property for information for the protocol adapters. |
The following table describes the operations of the DeviceAdmin:
Operation |
Parameters |
Description |
|---|---|---|
|
|
Returns information for specific protocol adapter. |
|
|
Creates and registers a |
|
|
Creates and registers |
|
|
Removes a |
|
|
Removes the specified |
|
|
Forces the adapter to cancel a device remove operation. This operation is executed if the method is supported by the protocol adapter. |
|
N/A |
For this operation there is no defined operation method. Used only for |
States of the DeviceAdmin
The lifecycle of the Device Admin starts when the service is registered and ends when the service is unregistered. The states of the DeviceAdmin are "Registered" and "Unregistered", as shown on the following diagram:

After Device Access is initialized it registers the DeviceAdmin as an OSGi service and after that all available Devices and their Device Items are registered as an OSGi services too. The "Unregistered" state can be achieved in two ways:
DeviceAdmin.DeviceAdmin changes the state to "Unregistered" and after that changes the state to "Registered" again.