Table Of Contents

The Databases of CLASS

Managing the AOCs: The Class database

Database map

The class database schema

Conclusion

The Databases of CLASS

---

This section gives a complete description of the databases of MWFM NMOS Active Object Class loader and management system, CLASS.

Managing the AOCs: The Class database

In order to manage the Active Object Classes (AOCs), CLASS utilizes a database called the Class database (class), which consists of two tables, the activeClasses table (class.activeClasses) and the staticClasses table (class.staticClasses).

This database enables CLASS to deduce the class hierarchy and the relationships between all the classes in the AOC directory. The Class database also enables you to discern which classes are currently active in the system. As is the case with all databases of MWFM NMOS, you have the flexibility to interrogate and modify the database using the OQL service provider riv_oql. These tables reflect two different views of the class hierarchy; while their structure is identical, their content will differ.

The staticClasses table

The staticClasses table is used by CLASS to hold the contents of a raw AOC as it is initially detailed in the.aoc file. Any changes made via the AOC browser will be reflected here.

It is worth noting that the number of AOCs reported by the staticClasses table is always equal to the number of AOCs reported by the activeClasses table. The information retained about each AOC by the staticClasses table is listed below.

•The unique name of the AOC.

•The parent class of the AOC.

•A list of the data dictionaries used by the AOC.

•The rules for instantiating the AOC.

•A list of extensions applicable to the class (Fault Manager, configuration, etc.) as defined in the AOC.

•A list of menu rules.

•A list of Action types to be taken.

The activeClasses table

The activeClasses table holds the full definition of every AOC active in MWFM NMOS. CLASS uses the inheritance tree and the raw information contained within the staticClasses table to calculate any inherited property in a class for all classes. The information retained about each AOC is:

•The unique name of the AOC.

•The parent class of the AOC.

•A list of the data dictionaries used by the AOC.

•The rules for instantiating the AOC.

•A list of extensions applicable to the class (Fault Manager, configuration, etc.) as defined in the AOC.

•A list of menu rules.

•A list of Action types to be taken.

Database map

Figure 22-1 The database of CLASS

The class database schema

The schema of the activeClasses table of the Class database is shown below.

Table 22-1 Synopsis of the class database and its tables

Database name	Class database: class
Database definition location	$RIV_HOME/etc/ClassSchema.cfg
Fully qualified database table names	activeClasses table: class.activeClasses staticClasses table: class.staticClasses

Table 22-2 The activeClasses table: class.activeClasses

Table column name	Properties (column constraints)	Column data type	Description
ClassName	PRIMARY KEY NOT NULL UNIQUE	Text	Name of the AOC.
SuperClass	NOT NULL	Text	Name of the parent AOC.
Dictionary		List of Text data type	List of data dictionaries used by the AOC.
Instantiate	NOT NULL	Text	Rules for instantiating the AOC.
Extensions	Externally defined extension data type	Object of extension data type	List of extensions contained within the AOC.
VisualIcon	NOT NULL	Text	The icon associated with this AOC.
MenuRules	Externally defined menurule data type	List of Object data type (Object is of the menurule data type)	A list of menu rules associated with the AOC.
ActionType	Externally defined actions data type	Integer	The broadcast type ID.

Table 22-3 The staticClasses table: class.staticClasses 

Table column name	Properties (column constraints)	Column data type	Description
ClassName	PRIMARY KEY NOT NULL UNIQUE	Text	Name of the AOC.
SuperClass	NOT NULL	Text	Name of the parent AOC.
Dictionary		List of Text data type	List of data dictionaries used by the AOC.
Instantiate	NOT NULL	Text	Rules for instantiating the AOC.
Extensions	Externally defined extension data type	Object of extension data type	List of extensions contained within the AOC.
VisualIcon	NOT NULL	Text	The icon associated with this AOC.
MenuRules	Externally defined menurule data type	List of Object data type (Object is of the menurule data type)	A list of menu rules associated with the AOC.
ActionType	Externally defined actions data type	Integer	The broadcast type ID.

Conclusion

This chapter detailed the use of the Class database, which retains information about AOCs in MWFM NMOS and enables CLASS to determine the relationships and hierarchy between AOCs. The next chapter describes the databases that configure the overall behavior of the MWFM NMOS auto-discovery process controller, DISCO.