Content management services include library services (checkin and checkout of objects stored in the repository), version control, and archiving. The Content Server uses an object-oriented model and stores everything as an object in the repository.

Metadata can be retrieved using Document Query Language (DQL), which is a superset of Structured Query Language used with databases (ANSI SQL). DQL can query objects and their relationships, in addition to any database tables registered to be queried using DQL.

Data dictionary stores information about object types in the repository. The default data dictionary can be altered by addition of user-defined object types and properties. Properties are also known as attributes and the two terms are used interchangeably to refer to metadata.

Virtual documents link multiple component documents together into a larger document. An individual document can be part of multiple virtual documents. The assembly of virtual documents can also be controlled by business rules and data stored in the repository.

Collaborative services can be deployed with an optional license and make collaboration features available in client applications. Collaborative features (Documentum 5.3) include:

Retention Policy Services (RPS) is an optional product and enables use of policies to manage the lifecycle of the objects stored in the repository. A retention policy defines the phases through which such an object passes and how it is finally disposed of or exported.

Process management services (features) include the following:

A repository uses access control lists (ACLs), also known as permission sets, as the security mechanism by default. The repository security can be turned off as well.

While the repository security model is ACL, each object has an associated ACL. The ACL provides object-level permissions to users and groups.

When the repository security is enabled, the Content Server enforces seven levels of basic permissions and six levels of extended permissions. There are additional privileges and security components, which are discussed in later chapters.

Content Server provides robust accountability and capability via auditing and tracing facilities. Auditing can track operations such as checkin or checkout that have been configured to be audited. Tracing can provide detailed run-time information useful for debugging applications.

Electronic signatures can enforce sign-offs in business processes. A sign-off is a way of authorizing or approving a decision similar to signing off on paper.

A Documentum installation can include multiple repositories and the Content Server is aware of distributed configurations that deployments can take.

The Content Server provides an application programming interface (API) and therefore needs a layer in front of it to expose its capabilities to human users. Documentum provides desktop and web-based client applications and supports creation of custom applications of either type. The following figure shows several client applications:

The full set of Content Server features is exposed via Documentum Foundation Classes (DFC) and Documentum Client Library (DMCL). DFC provides the API for interacting with the Content Server programmatically.

Documentum also provides a Web Development Kit (WDK) to facilitate development and customization of web-based client applications.

Documentum provides two interactive utilities for interacting with the Content Server using queries — IDQL and IAPI. These utilities are typically used by administrators and developers.