EMC Documentum 5.3

Docbase
- Centralized repository for content and metadata (objects and properties)
- Storage types
-- OS file system
-- RDBMS as BLOBs
-- Cotent storage device
(EMC Centera)
-- External system

DocBroker
- Bridge (intermediary) between client and server
- Content Servers broadcast connection info at regular intervals to DocBrokers
- DocBroker sends info to requesting clients

DocApp
- Packaging unit for Documentum objects
- Dev. work happens on dev. Docbase
- DocApp as deployable packaging unit to move objects across Docbases
- Multiple Docbase objects (lifecycles, workflows, folders) can be included

Object Type
- Follow a hierarchy
- Subtype extends from a supertype , inherits all attributes.
- Has own specific attributs and inherited attributes


DQL & API, Cabinets and Folders
- Document Query Language – CRUD Docbase, Query Registered tables
- DQL fired by Documentum Administrator (web client), Documentum Foundation Classes (DFC) and IDQL utility (Command)
- Server API via DMCL (Documentum Client Library) – CRUD in Docbase
- IAPI – Interactive utility to execute Server API against a Docbase
- Cabinets & Folders – Placement of Objects

Version, Lifecycle, Workflow
- Versioning – Numeric (implicit), Symbolic
- Lifecycle – Well-defined authoring-review process
- Workflows – Models a business process

Advanced Concepts
- DMCL, DFC, ACL, Alias Set, Users & Groups Renditions, Data Dictionary,
- BOF (Business Objects Framework) – Built into DFCto create reusable Business Objects (Type-based, Service-based)
- WDK (Web Development Kit) – Framework to build web application <-> Content Server
- Web Publisher – Content creation, publish
- Registered Tables – RDBMS tables awared by content server
- Method & Jobs – Executable(M), Scheduled(J)

Web Content Mgmt System
- Enter Content – Web Publisher
- Store Content – Content Server
- Publish Content – Site Caching Services
- Query Published Content - JDBC
- Deployment – Site Deployment Services

System Architecture















Integration Architecture