by John Ragan
|
Select A Section home public service database mgr. data access data modeler site notes |
Currently In This Section CoreModel Metadata Server ( Please Scroll Down ) |
Pages In Section summary installation architecture testing metadata srvr user manual |
|
( Document has not been substantially updated in years, so report of erroneous or misleading information will be appreciated. ) __________________________________________________
CoreModel Copyright 1996 - 2013 John E. Ragan.
__________________________________________________ The CoreModel system includes a Metadata Server sub-system that can maintain an external data repository as a dynamic public interface to allow metadata consumption by external systems. It is part of CoreModel's empowerment of an organization to centrally model and administer its entire data structure. It is an optional sub-system that is turned on and controlled by the system administrator. The process can be configured to run 24-7.
__________________________________________________ The CoreModel Metadata Server constains two sub-servers. One serves systems and the other serves people. Each specializes in a different type of interface to the data models. They can be run locally and manually by the administrator or they can each be configured to run 24-7 to maintain the data repository for an organization. Each server may be run on a separate computer, or they may be run on the same computer.
__________________________________________________ The human-oriented metadata server is an automated web site administrator which creates and maintains a complete CoreModel web site for human consumption. The size and complexity of the web site is determined by the server that automatically changes the site to match live modeling activities. For a large organization, with heavy data modeling, the coremodel web site may seem overwhelming, but should be of little concern to a human administrator. If the organization already has a web site, the server can be configured to tie its site into the master site.
__________________________________________________ The system oriented server maintains a data dictionary interface which is more appropriate as an interface to external systems which require metadata. The system interface is not HTML, but resides within schema-based XML. The metadata for that system metadata is documented on the web site and the server maintains published pointers into the dictionary so that other systems can find their way into the dictionary without human intervention. Thus, the CoreModel architecture allows external systems to access its models while safeguarding its internal database.
__________________________________________________ After a model is complete and has been actualized, it may then be published through metadata conversion by CoreModel. Publication is affected through formal controls within the CoreModel system. The publication is controlled by both the modeler and the (human) system administrator. (See Model Release below.)
__________________________________________________ The translation of a model into metadata is handled entirely by the CoreModel Metadata Server. All of the model's structures, objects, characteristics, and data are translated, organized, and moved into the repository.
__________________________________________________ A model is released to the Metadata Server by the modeler, so that each modeler controls the publication of his model. After a model is released by the modeler, the system administrator must release it to the server. After both releases have been made for a model, the administrator must insure that the server has been told to include models in its publications. Since the data dictionary presents an interface which is expected to be used by external systems and agents, with perhaps dynamic links being formed by external systems, publication cannot be rescinded by the modeler. However, the model is dynamically linked to the metadata interface, so changes made by the modeler to the model are transmitted to the interface to allow updates directly into metadata consumers.
__________________________________________________ Since the CoreModel system automatically and autonomously administers its web site and data repository, the metadata is dynamically driven by changes as they are made by data modelers. The server modules within CoreModel are toggled on or off and have parameters that are controlled by the human system administrator, but the CoreModel servers otherwise independently maintain the web site and the data dictionary so that a link is maintained between the metadata and the models. This autonomous nature and the fact that CoreModel generates schema-based XML also allows external data management systems to be driven from within the CoreModel modeling operations if so desired. |
|
|
Technology and web site
|
|
|
Web site is maintained with Notepad.
|
|