300 likes | 508 Views
Document Management Reference Model. Draft 05a, 2/19/99. Desktop Apps. Business Process Applications. Authoring (WP, Web) Presentations Document Assembly Scan/Capture Image Editing. Managed Document Repository. Managed Document Repositories. Managed Document Repository.
E N D
Document Management Reference Model Draft 05a, 2/19/99
Desktop Apps Business Process Applications Authoring (WP, Web) Presentations Document Assembly Scan/Capture Image Editing Managed Document Repository Managed Document Repositories Managed Document Repository Other Repositories Indexed Content Stores LOB App Data Stores Message Stores Document Repository Interfaces Repository Access Native DM Clients Web Browsers View/Search Tools Cross-repository Search Print Services Enterprise Apps Workflow Apps Data Merge Apps Databases Access Control Data Repositories are Central to Key Applications
Data Center Systems Knowledge Workers Publishing Workgroups Imaging & COLD Systems Messaging, Workgroup, & Web Repositories Document, Content, & Asset Management Systems Extranet WAN Intranet LAN Modem Ad Hoc Scanning & Printing Production Scanning & Printing Transaction Printing AFP/Metacode Printers Personal/Workgroup Printers Production Printers Scanning and Printing Interfaces LAN
DM Reference Model - A Collaborative Effort • Marilyn Wright, AIIM International • Benny Ong, Boeing Corporation • Fred Siegmund, Chevron • Carl Frappaolo, The Delphi Group • Diane Entner, Eastman SW/Black Forest Group • Chuck Fay, FileNET • Michael Leslie, General Motors • Surendra Reddy, Oracle Corporation • Jean Heminway, Xerox Corporation • Toby Cobrin, XPLOR
Document Management Reference Model - Goals • Provide a framework which shows how document management systems fit into a corporate information technology infrastructure • Show how document repository integration and interoperability can be handled seamlessly with document management standards • Illustrate how extensible services like security and directory services are provided through the existing enterprise infrastructure • Give a consistent way to illustrate the differences between document management standards
Document Management in the Enterprise Architecture Corporate Information Technology Infrastructure System & Network Man. Other Services Object Management Security & Directory Workflow/ WfMC OS Services Network Presentation/ Application Layer Document-Related Applications Middleware/ API Layer Document Management Middleware and/or API Service Provider Layer Repository Services Repository Administration Services
DMA in the DM Reference Model Corporate Information Technology Infrastructure System & Network Man. Other Services Object Management Security & Directory Workflow/ WfMC OS Services Network Presentation/ Application Layer DMA Client Applications <DMA API> Middleware/ API Layer DMA Middleware <DMA API> Service Provider Layer DMA Service Provider 1 (DM Repository 1) DMA Service Provider 2 (DM Repository 2)
ODMA in the DM Reference Model Corporate Information Technology Infrastructure System & Network Man. Other Services Object Management Security & Directory Workflow/ WfMC OS Services Network Popular office applications Application integration for ODMA Presentation/ Application Layer ODMA Connection Manager DM Integration Native DM Client Application API Layer <Native DM API> Serv. Prov. Layer DM Repository
ODMA with Multiple Repositories Corporate Information Technology Infrastructure System & Network Man. Other Services Object Management Security & Directory Workflow/ WfMC OS Services Network Popular office applications Application integration for ODMA Presentation/ Application Layer ODMA Connection Manager DM Integration 1 DM Integration 2 DM Client App. 1 DM Client App. 2 API Layer <Native DM 1 API> <Native DM 2 API> Serv. Prov. Layer DM Repository 1 DM Repository 2
ODMA and DMA Interoperability Corporate IT Infrastructure Popular office applications Presentation/ Application Layer Application integration for ODMA ODMA Connection Manager ODMA-to-DMA Client Application <DMA API> Middleware/ API Layer DMA Middleware <DMA API> DMA Service Provider 1 (DM Repository 1) DMA Service Provider 2 (DM Repository 2) Serv. Prov. Layer
WebDAV in the DM Reference Model WebDAV Client WebDAV Client Application HTTP/WebDAV HTTP/WebDAV <Native HTTP API> WebDAV Service Provider WebDAV-enabled Web Server
Generic DMA Distributed Client DMA Client DMA Client Application Network Services Network Services DMA Client (skeleton) <DMA API> DMA Middleware DMA Repository <DMA API> DMA Service Provider
WebDAV and DMA Interoperability WebDAV Client WebDAV Client Application HTTP/WebDAV HTTP/WebDAV WebDAV to DMA Translator <DMA API> DMA Middleware DMA Repository and Web Server <DMA API> DMA Service Provider
CORBA and DMA Interoperability CORBA Client Java Client Application CORBA ORB CORBA ORB CORBA IDL to DMA Translator <DMA API> DMA Middleware DMA Client & Repository <DMA API> DMA Service Provider
CORBA and DMA Interoperability • CORBA ORBs could also be used to distribute the middleware and/or service provider layers of the DM reference model • CORBAservices and CORBAfacilities are additional infrastructure that could be leveraged in DMA service provider implementations
Generic DMA Distributed Middleware DMA Client DMA Client Application <DMA API> DMA Middleware Network Services Network Services DMA Middleware <DMA API> DMA Service Provider DMA Repository
Generic DMA Distributed Service Provider DMA Client Application DMA Client <DMA API> DMA Middleware <DMA API> DMA Service Provider Stub Network Services Network Services DMA Service Provider DMA Repository
Presentation/Application Layer • Document-related applications • Desktop applications • Enterprise applications • Native document management clients • Scan/Print services • Presentation layer • Provides user interface • ODMA 1.0 providers and other extensible presentation frameworks are at this level
Middleware/API Layer • Defines common interfaces for services provided by document repositories • DMA and CORBA IDL for DM are examples • Proprietary API in some cases (e.g., in ODMA model) • Provides a uniform access model for document repositories • Repository registration and location • Cross-repository search
Middleware/API Layer • May provide transparent object distribution across network boundaries (e.g., via CORBA or DCOM) • Alternatively, may intercede only in limited ways, and otherwise allow client calls to pass through untouched • E.g., non-distributed DMA middleware handles repository registration and location, and cross-repository search, but allows all other functions to pass directly from client to service provider
Service Provider Layer • Provides services for repository usage and administration • Different DM vendors can plug in their DM repositories within a standards-based enterprise-wide framework • Administration distinguished from usage; administration currently not standardized
Corporate Information Technology Infrastructure • DM model builds on existing enterprise IT infrastructure services -- transport, object management, network management, security, directory, database, work flow, OS • E.g., DM vendors could build on CORBA or DCOM for distributed object management, rather than build a proprietary infrastructure
Network Services • Network services provide for communicating with document repositories in a networked environment • Allows clients to communicate with document repositories, and to request and receive information from service providers
Network Services • Provides flexible transport mechanism by which documents are transferred from document repositories to clients • Application-level protocols like WebDAV provide high-level functions like locking, property management, etc. on top of basic transport protocols
Object Management Services • Provides transparent object distribution, e.g., via CORBA, DCOM, or RPC • Gives the clients uniform access to distributed, heterogeneous information resources and services • Supports object lifecycle management, transactions, etc. -- e.g. CORBAservices, MTS, COM IUnknown
System & Network Management • System Management: Manages software installation, configuration, & upgrades across an enterprise • Network Management: Monitors, manages, & controls network topology and nodes
Security & Directory Services • Security Services: Enforces access controls and user authentication • Directory Services: Provides service for locating network resources, nodes, users, groups, etc.
Operating System Services • Provides fundamental services for memory allocation and management, file systems, device management, network connectivity, ...
Relationships Between Elements • In the front document management plane, physical proximity of layers implies that those layers interact via objects and method calls. • Likewise, the proximity of the document management plane to the IT infrastructure planes implies interaction. • However, the positioning of the infrastructure layers in the diagram is arbitrary; juxtaposition does not necessarily imply a relationship between infrastructure layers. Interactions among the elements of the IT infrastructure are beyond the scope of this reference model.