1 / 11

A Next Wave of Challenges in the Junction of Information Management (esp. Integration) and the Web

A Next Wave of Challenges in the Junction of Information Management (esp. Integration) and the Web. Yannis Papakonstantinou Associate Prof., CSE, UCSD. Involvement with Enterprise Information Integration. Enosys Software in 2000 Enosys = greek for “union, merge, fusion”

karsen
Télécharger la présentation

A Next Wave of Challenges in the Junction of Information Management (esp. Integration) and the Web

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Next Wave of Challenges in the Junction of Information Management (esp. Integration) and the Web Yannis Papakonstantinou Associate Prof., CSE, UCSD

  2. Involvement with Enterprise Information Integration • Enosys Software in 2000 • Enosys = greek for “union, merge, fusion” • Enterprise Information Integration product • XML virtual view • Thanks to great fundamental discoveries of IDM field • Product also sold under BEA’s Liquid Data brand since 2002 • Acquired by BEA in 2003 • As conventional EII is under way we may want: • A myriad communities of myriads of sources • And easy to build corresponding portals

  3. Architecture for Unified Access to Data & Services (Web )Client Application Integrated (XML) Global Schema/Ontology + Services Cache & Replication Mediator Local (XML) View + Methods Local (XML) View + Methods Wrapper Wrapper Information + Service Source Information + Service Source

  4. Integration by whom and how? Current EII’s status:Small Domain, Vertical Partition, Primarily Application-Driven, Propeler-head saves the day by elaborately mapping each source into global schema Integrated Global View Schema V(M, S, E) Application developer GAV View V View Builder (design time) Mediator (run time) Schemas Data Local View E Local View M Local View S Service Marketing Sales Well under-way: years of research, startups, moving well into mainstream (BEA Liquid Data, IBM DB2, …)

  5. Approaches towards View-Based Data Integration Integration Specification Method Info model & Query Language GAV + LAV XML (XQuery) Local As View (LAV) Object-Oriented Global As View (GAV) Relational (SQL) Warehousing (materialized views) On-Demand (virtual views)

  6. Integration by whom and how? Myriad Domains, Myriad Clients, Sources, “Moderators”, Horizontal Partition, Source Owner Participation Client Application 1 Client Application m View/Query V1a (G) View/Query Vma (G) Q/V: V1a Q/V: Vma Query/VIew Builder Integrated View Owner’s Domain Global Schema/Ontology G Registration Builder Reg: W1 Reg: Wn Registration Builder Local XML View S1 Local XML View Sn Source Owner

  7. C:\Enosys\projects\allPONS.qpr* - Enosys Query Builder Visual Tools Matter! TARGET SCHEMA (XML VIEW) 1 OPEN & VIEW SOURCE SCHEMAS IN XML 2 DRAG & DROP TO CREATE TARGET XML VIEW AUTOMATICALLY GENERATED MAPS

  8. C:\Enosys\projects\allPONS.qpr* - Enosys Query Builder 3 RUN & TEST XQUERY XML RESULT XQUERY BASED ON DESIGN SPECS

  9. Semi-Automation of Registering Queries and Sources • The full automation of many mapping and matching problems is risky • Yet its study provides great fundamental discoveries • Tools that provide guidance and semi-automate • Integration’s QBE: What types of meaningful queries can I formulate on the view using available data and services? • Integration’s Registration Tool: Does it worth it to clean up attribute X and register it? If so, give a ranked list of target global schema attributes • Compare amount of data one has to absorb and time he has to spend with/without tool

  10. Portal Building Made Easy • Site Structure • WebML, Strudel • Forms • QURSED

  11. Beyond Accessing Data: High Level Specifications of the Business Logic Web design tools address the look-and-feel requirements Business logic specification: We are mostly absent! Access to databases and information: IDM did and keep doing great work

More Related