Package org.mbs.services.cup

Defines API for transferring Control Unit Protocol messages to Managed Devices or remote OSGi frameworks hiding the data serialization.

See: Description

Interface Summary

Interface	Description
ControlUnitProxy	This service could be used by remote applications to perform cu protocol requests for control units administration to a target OSGi framework.
RemoteControlUnitAdminApplication	Interface implemented by the user applications for processing callbacks from cu protocol requests.

Package org.mbs.services.cup Description

Defines API for transferring Control Unit Protocol messages to Managed Devices or remote OSGi frameworks hiding the data serialization. The main interface ControlUnitProxy is provided in mPRM for management of three conceptually different control unit targets:

system control units
These are control units exported on the backend frameworks and providing backend-system resources as manageable control unit representations.
Instance of the ControlUnitProxy for management of system control units could be created via a factory service definied in com.prosyst.mprm.admin.systemcu package (see: BackendControlUnitProxyFactory

control units on managed devices
This conception is exported by the Generic Device Management package, which provides the ability for creating instance of the ControlUnitProxy for management of component control units provided on any particular device managed in mPRM.

control units on remote osgi framework via com.prosyst.mprm.net.message.Connection
This conception is exported by the OSGi Device Management Package, which provides the org.mbs.services.cup.factory.ControlUnitProxyFactory factory service for creating instance of the control unit proxy to osgi devices managed by mPRM. This factory service could also be used by non-mPRM standalone applications to manage control units on any remote osgi framework with enabled messaging.

The control unit proxy concept is to provide remote managemenet on control units via asynchronous method invocations. Thus, the results of its methods are not java-method results, but are applied in user-provided callback implementation of RemoteControlUnitAdminApplication. The call back interface is supplied by the user in the phase of proxy creation regarding the respective proxy factory.