AutoMed Project

1
AutoMed Project

• Another Look at Data Integration
• Geoff Sharman

2

• Typical e-business Architecture

Mainframe
sync msgs
async msgs
Mainframe
sync msgs
Presentation server - Static web pages - Cached
web pages - Dynamic web pages - Portal -
Connectors
Integration server - Tight coupling - Loose
coupling - Stand-in processing - Flow
ctrl/compensation - Connectors
Unix
Line of business Transaction servers
Thin clients
Note connectors are shown in yellow
3
Securities Company 2 - Project B

• Schwab.com Trading Service
• (circa 2000)

CICS TS for zOS ES/9000 Sysplex
CICS for AIX RS/6000 SP Server
Netscape Web Server
Web browsers
HTTP
DCE RPC
SNA/LU6.2 CICS ISC

• Features
• Over 2 million Internet based self service
  customers
• gt400 nodes running Netscape Web server
  WebSphere
• gt100 nodes running CICS for AIX Server on IBM
  RS/6000
• gt15 million Internet transactions/day into
  trading system

4

• General e-business Architecture

Line of Business Applications
LOB 1
sync msgs
async msgs
LOB 2
sync msgs
Presentation server - Static web pages - Cached
web pages - Dynamic web pages - Connectors
Integration server - Tight coupling - Loose
coupling - Stand-in processing - Flow
ctrl/compensation - Connectors
LOB 3
Thin clients
Service Integration
Note connectors are shown in yellow
5
Observations

• Data Integration often performed as part of an
  operational system not just for data
  warehousing
• Usually performed by activities out of the main
  transaction path, driven by reliable asynchronous
  messaging
• Typical examples are reconciliation of data
  between heterogeneous systems downstream
• Many opportunities for upstream use