1. Yannis Papakonstantinou Associate Prof., CSE, UCSD
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 EII is (expensively) under way we may want:
A myriad communities of myriads of sources
Inexpensive corresponding portals
as easy as starting and participating in newsgroups and lists

3. Conventional 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
Heterogeneity is formats, vocabularies and access methods prevents unified access. Integrated View, governed by integrated global schema/ontology provides unified access.
Wrapper
Wrapper
Information
+ Service
Source
Information
+ Service
Source

4. V Service Marketing Sales
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
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. Global Schema/Ontology G
Integration by whom and how? In Future, 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
Mix LAV/GAV
Registration Builder
Reg: W1
Reg: Wn
Registration Builder
Local XML View S1
Local XML View Sn
Source Owner

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

8. XQUERY BASED ON DESIGN SPECS
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 keeps doing great work