Architecture
openMDM is an open-source, freely configurable and expandable software building block (framework) for the management of measurement data. openMDM systems manifest themselves in operation as a collection of components which are distributed across various computers in the network and which communicate with each other via the CORBA protocol. The MDM objects (business objects) exchanged in this manner are described in the openMDM business model. openMDM components look after the storage, processing and display of the openMDM objects or their importation and exportation.
Divide, distribute and conquer
openMDM systems are designed essentially as distributed systems for managing data. The technologies used (CORBA/CCM) support both the network-wide distribution as well as the balancing of databases, computing and display resources. Demands emanating from the interconnections between different sites and the local capacities (memory space, computing capacity) are supported by the configurable distribution of the system components. The communication between the MDM components can be protected by configuring the respective protocols (e.g. IOP/SSL). The use of CORBA/IOP ensures efficient transfer of large volumes of data.
Storing, finding and using data
Standardised and secure storage of data with ASAM ODS is a central function of openMDM systems. In order to be able to use the standardised data storage within openMDM, an ODS data model has to be defined for the MDM business model. This object-oriented data model is called an “MDM applications model” and is stored in the ASAM ODS server.
Using the MDM API, which is implemented as a separate component, it is possible within the MDM to access the database in the ASAM ODS server.
The MDM applications model enables the ASAM ODS server to store the data in a relational database in conjunction with a mass storage memory. The database and mass storage memory can only be used by means of the ASAM ODS server.
The AOP5 interface of the ASAM ODS server represents the lowest level at which data in the openMDM system can be accessed. Above this level, the openMDM system provides access protection and security systems. openMDM external applications can already access the ASAM ODS databases through this interface, but are not able to interpret information specific to openMDM.
Divide, distribute and conquer
openMDM systems are designed essentially as distributed systems for managing data. The technologies used (CORBA/CCM) support both the network-wide distribution as well as the balancing of databases, computing and display resources. Demands emanating from the interconnections between different sites and the local capacities (memory space, computing capacity) are supported by the configurable distribution of the system components. The communication between the MDM components can be protected by configuring the respective protocols (e.g. IOP/SSL). The use of CORBA/IOP ensures efficient transfer of large volumes of data.
Storing, finding and using data
Standardised and secure storage of data with ASAM ODS is a central function of openMDM systems. In order to be able to use the standardised data storage within openMDM, an ODS data model has to be defined for the MDM business model. This object-oriented data model is called an “MDM applications model” and is stored in the ASAM ODS server.
Using the MDM API, which is implemented as a separate component, it is possible within the MDM to access the database in the ASAM ODS server.
The MDM applications model enables the ASAM ODS server to store the data in a relational database in conjunction with a mass storage memory. The database and mass storage memory can only be used by means of the ASAM ODS server.
The AOP5 interface of the ASAM ODS server represents the lowest level at which data in the openMDM system can be accessed. Above this level, the openMDM system provides access protection and security systems. openMDM external applications can already access the ASAM ODS databases through this interface, but are not able to interpret information specific to openMDM.
