next up previous contents
Next: 6.3.5.1 Decision for the Up: 6.3 Implementing Metapolicies in Previous: 6.3.4 Policy and Metapolicy   Contents

6.3.5 Implementation Details

General considerations, the enhancements to existing classes, and the class diagram of the Metapolicy Service Mobile Agent are presented in this part.

Additional attributes and classes are depicted by slanted typeface in the class diagrams. An exception is the class diagram for the Mobile Service Mobile Agent, because this has completely been developed.

There is no real refinement process and thus no appropriate decision points in the NoCScontrol system. For this reason, the passive metapolicy enforcement is not implemented by the Policy Factory Mobile Agent. It can be realised in the same way as it is done in the enforcement process.

The Object State Database and the Action Event Database conceptually store the state of objects. Two different databases are used to support an efficient implementation. For the realisation of new state attributes, the mechanism of policies already implemented by NoCScontrol is used. This allows maximum flexibility in choosing the number and type of attributes for the objects. The policies need a public API to call methods by CORBA. Therefore, the entries of the Object State Database are added and removed with the help of such public methods. Also, the entries in the Object State Database are more ``stable'' in contrast to the entries in the Action Event Database. The entries of the Action Event Database are received by events. These events are stored directly in Action Event Database.



Subsections
next up previous contents
Next: 6.3.5.1 Decision for the Up: 6.3 Implementing Metapolicies in Previous: 6.3.4 Policy and Metapolicy   Contents
Copyright Munich Network Management Team