Automatic Data Ramon Lawrence University of Manitoba
Published byModified over 3 years ago
Presentation on theme: "Automatic Data Ramon Lawrence University of Manitoba"— Presentation transcript:
Automatic Data Ramon Lawrence University of Manitoba firstname.lastname@example.org
base Integration Ken Barker University of Calgary email@example.com
Summary è Database integration allows systems within a company or on the WWW to interoperate. è Current integration solutions require manual coding which is costly and time-consuming. è Our integration architecture uses XML and a standard dictionary to automate integration. è Database systems are integrated using 3 processes: capture, integration, and query. è The architecture is implemented in a software package called Unity. è Unity is capable of automatic database integration and querying using ODBC. è Applications include data warehouse design, web site integration, and systems integration.
Integration Architecture Architecture Components: 1) Integrated Context View user’s view of integration 2) X-Spec Editor stores schema & metadata uses XML 3) Standard Dictionary terms to express semantics 4) Integration Algorithm combines X-Specs into integrated context view 5) Query Processor accepts query on view determines data source mappings and joins executes queries and formats results Local Transactions X-Spec X-Spec Editor Standard Dictionary Integration Algorithm Integrated Context View Query Processor and ODBC Manager Database Client Subtransactions Client Multidatabase Layer Database X-Spec
è The integration architecture consists of three separate processes: u Capture process: independently extracts database schema information and metadata into a XML document called a X-Spec. u Integration process: combines X-Specs into a structurally-neutral hierarchy of database concepts called an integrated context view. u Query process: allows the user to formulate queries on the integrated view that are mapped by the query processor to structural queries (SQL) and the results are integrated and formatted. Integration Processes
Architecture Components è The architecture consists of four components: u A standard dictionary (SD) to capture data semantics ïSD terms are used to build semantic names describing semantics of schema elements. u X-Specs for storing data semantics. ïrelational database info. stored and transmitted using XML ïstores semantic names to describe schema elements u Integration Algorithm ïIdentical concepts in different databases are identified by similar semantic names. ïProduces an integrated view of all database concepts. u Query Processor ïallows the user to formulate queries on the view ïtranslates from semantic names in integrated view to SQL queries and integrates and formats results s involves determining correct field and table mappings s and discovery of join conditions and join paths
Architecture Discussion è The architecture automatically integrates relational schemas into a multidatabase è Desirable properties: u individual mappings - information sources integrated one-at-a-time and independently u integrated view constructed for query transparency - user queries system by semantics instead of structure u handles schema conflicts - including semantic, structural, and naming conflicts u automated integration - integrated view constructed efficiently and automatically u no wrapper or mediator software is required u transparent querying - users issue semantic queries which are translated to SQL by the query processor u no changes are performed on underlying databases
Conclusions è Automatic database integration is possible by using a standard term dictionary and defining semantic names for schema elements. è Integration of data sources has applications to the WWW and construction of data warehouses. è Users are able to transparently query integrated systems by concept instead of structure. è Future Work: u Test the system in large industrial projects. u Improve the Unity implementation and develop an integration component for a web browser. u Increase the efficiency of the query processor. u Allow distributed updates and global updates on all databases.
Why is Integration Required? è There are many integration environments: u operational systems within an organization u system integration during company merger u data warehouses, Intranets, and the WWW è Users require information from many data sources which often do not work together. è Companies require a global view of their entire operations which may be present in numerous operational databases for different departments and distributed geographically. è Business-to-Business (B-to-B) and Business-to- Consumer (B-to-C) E-commerce demand integration of web databases with production systems for efficiency and productivity.
What is Integration? è Database integration requires conflict resolution during schema integration. è A schema is a description of the data organization and format in a database. è Schema integration combines database schemas into a unified view of the data. u Constructing an integrated view is difficult because databases will store different types of data, in varying formats, with different meanings, and reference it using different names. Subsequently, the construction of the integrated view must handle the different mechanisms for storing data (structural conflicts), for referencing data (naming conflicts), and for attributing meaning to the data (semantic conflicts). Data is integrated at both the schema level (the description of the data) and the data level (individual data instances).
What is the Current Solution? è SQL and multidatabase query languages: u querying is difficult for numerous databases è Research systems: u do not use standardization so cannot be automated è Industrial standards: u XML, BizTalk, E-commerce portals u apply to limited domains/industries u require standard structures and database changes è Current techniques for database integration have some of these problems: u require integrator to understand all databases u integration process is manual u do not hide system complexity from the user u force changes on the existing database systems
Unity Overview è Unity is a software package that implements the integration architecture with a GUI. è Developed using Microsoft Visual C++ 6 and Microsoft Foundation Classes (MFC). è Unity allows the user to: u construct and modify standard dictionaries u build X-Specs to describe data sources u integrate X-Specs into an integrated view u transparently query integrated systems using ODBC and automatically generate SQL transactions è A screen-shot of Unity editing a standard dictionary is below. è Unity is available for demonstration and distribution.
References è Publications: u Unity - A Database Integration Tool, R. Lawrence and K. Barker, TRLabs Emerging Technology Bulletin, January 2000. u Multidatabase Querying by Context, R. Lawrence and K. Barker, DataSem2000, pages 127-136, Oct. 2000. u Integrating Relational Database Schemas using a Standardized Dictionary, To appear in SAC’2001 - ACM Symposium on Applied Computing, March, 2001. è Sponsors: u NSERC, TRLabs è Further Information: u http://www.cs.umanitoba.ca/~umlawren/