Abstract

Recently, meta-directories have begun to be used for unifying and centrally managing disparate directories/devices within an enterprise. Meta-directories must address many problems that have been extensively studied in the area of data integration, such as data cleaning and schema integration. However, some new challenges arise. Whereas previous data integration systems have focused on read-only queries, update support forms a major component of meta-directories. Network devices performing time-critical tasks should not be interrupted (queried) too often, and thus meta-directories must materialize the integrated data. At the same time, network devices must sometimes be managed independently from the meta-directory. Thus, meta-directories must ensure that data remains consistent across devices and the integrated view in the presence of updates to both devices and integrated view. In addition, existing directory servers have a number of limitations. For example, LDAP directories lack active functionality, and have extremely weak typing and transactional support. This paper discusses the MetaComm meta-directory: its implementation, how it addresses data integration issues and LDAP limitations, and our experiences in building a real product.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.