By Suhas Das
Author
In OpenText Documentum, the interaction between the Content Server, Docbase, and the database (RDBMS) is critical for managing enterprise content efficiently. This communication ensures that both content and metadata are properly stored, retrieved, and maintained.
Role of the Database in Documentum
The database is an essential component of the Documentum architecture. It is responsible for storing:
- Metadata (attributes of documents)
- Object relationships
- Indexes for fast searching
- System and configuration data
Each object in the repository—whether a document, folder, or user—is represented by entries in database tables. These tables hold all attribute values associated with repository objects.
Object-Based Repository Model
Documentum uses an object-oriented repository model, where:
- Everything is stored as an object
- Each object has properties (metadata)
- Objects can have relationships with other objects
This model allows flexible and scalable content management. The Docbase acts as the unified repository that combines:
- Metadata (in the database)
- Actual content files (in the file system)
How Content Server Communicates with the Database
The Content Server acts as the intermediary between client applications and the database.
Communication Flow:
- A user or application sends a request (e.g., search, retrieve, update)
- The Content Server processes the request
- It connects to the database using the repository owner (database user) account
- It executes queries to read or update metadata
- It retrieves or modifies the required information
- The result is returned to the client
This communication is seamless and handled internally by the Content Server.
Role of DQL (Document Query Language)
To interact with the database, Documentum uses DQL (Document Query Language).
- DQL is a superset of SQL
- It provides a unified query language for all repository objects
- It allows querying across different object types without dealing directly with database schema complexity
Using DQL, users and applications can:
- Retrieve documents and metadata
- Filter content based on attributes
- Navigate relationships between objects
Example (conceptually):
-
Instead of raw SQL tables, DQL lets you query objects like
dm_document
Key Advantages of This Architecture
- Abstraction → Users don’t interact directly with database tables
- Consistency → All operations go through the Content Server
- Security → Access is controlled centrally
- Flexibility → Object model supports complex relationships
Conclusion
In Documentum:
- The database stores metadata and object information
- The Docbase combines database + file system
- The Content Server manages all communication and operations
- DQL provides a powerful, unified way to query repository data
This architecture ensures efficient, secure, and scalable management of enterprise content.