Framework database
| Line 1: | Line 1: | ||
| − | A database is required by the framework for persistent storage; not | + | A database is required by the framework for persistent storage; not surprisingly it is called the framework database. It |
is used to store the configuration, states and status of the system. The framework database’s schema is imposed on | is used to store the configuration, states and status of the system. The framework database’s schema is imposed on | ||
| − | client and is considered an API. This means that it is subjected to the same rules as any | + | client and is considered an application programming interface (API). This means that it is subjected to the same rules as any TelcoBridges API. The schema |
was written in XML so the SQL generation script can be generated using simple XSL sheets. This was done to make | was written in XML so the SQL generation script can be generated using simple XSL sheets. This was done to make | ||
it easy to switch DBMS since the SQL data definition language is not always portable. This also makes it possible | it easy to switch DBMS since the SQL data definition language is not always portable. This also makes it possible | ||
Revision as of 14:53, 7 May 2009
A database is required by the framework for persistent storage; not surprisingly it is called the framework database. It is used to store the configuration, states and status of the system. The framework database’s schema is imposed on client and is considered an application programming interface (API). This means that it is subjected to the same rules as any TelcoBridges API. The schema was written in XML so the SQL generation script can be generated using simple XSL sheets. This was done to make it easy to switch DBMS since the SQL data definition language is not always portable. This also makes it possible to generate visual representations of the database using another XSL sheet and Graphviz. Of course the framework must support the DBMS, fortunately we support ODBC so the framework supports almost any database through that interface. In the future we will also add support for some DBMS natively.
This database was created and designed for the Web OAMP.
Caveats
- Note that the division is purely hierarchical and both the databases can be hosted on the same database.
- There is no restriction on the the DBMS of the framework database except that we must support it.
Return to the Toolpack User Guide
