The list below includes a breif descritption and definition of many of the Docuentum modules and components. The content in this post has been compiled from a variety of differnt sources (see references toward the end of the page). Feel free to contribute or comment…
Need assistance with your Enterprise Content Management Project, we offer a variety of implementation and consulting services for Documentum and SharePoint. Contact Us today at sales@capps-llc.com or via phone at 954-769-0066 or using our online request form.
Enterprise Content Management |
|
|
|
|
 |
|
Architectural Overview |
|
| At its core, the Documentum Content Server is a platform that offers many levels of services and tools to build applications. A high-level overviews of those services are shown in Figure 1.
Figure 1 – Overview of Documentum  Documentum Architechture Overview The content server itself is a three tier architecture, as show in Figure 2. A database is used to store metadata about the content stored within the content server. For the Documentum Developer Edition (DDE), a SQL backend is used. The second layer is the application server layer. The content manager runs on any standard enterprise ready application server. The third layer is the content server itself. You will learn more about the content server in this document. The Content Server layer consists of: repository services (web services), security services, other Documentum solution services, search and other services. |
|
|
|
The Documentum Repository |
|
| The high-level description of how Documentum works, above, showed the relationship of Documentum to various components. But the following diagram, Figure 3, demonstrates how the Documentum Repository incorporates various features.
Content Files: A file store contains the content assets RDBMS: Contains attribute tables that store the meta-data about the content Full-text Indexes: To allow for searching through the content files Directory Services: To integrate with an external LDAP, or run basic authentication.  Repository Structure |
|
|
|
Content Objects |
|
The Documentum platform defines repository content as objects. (Content objects may consist of a collection of objects.) Objects comprise three parts:
A content object’s set of attributes and set of methods are configurable and extensible. Using Documentum development tools, developers can create new object types that behave exactly as dictated by specific business needs. Furthermore, content attributes characterize the relationships among the stored content objects. The repository organizes content around its metadata; users and applications use the metadata to interact with and retrieve relevant content. |
|
Security |
|
Core security is provided by EMC Documentum Content Server; additional security can be added via Trusted Content Services and Information Rights Management Services. The core security services include:
Each fulfills a unique function within an organization’s security architecture. First, the Documentum platform builds on the underlying enterprise-wide security infrastructure to authenticate access to the repository. Next, the platform manages access control lists (ACLs) to authorize access to content stored within the repository. Any activity can be audited using flexible auditing tools, with an audit trail stored in the repository. The platform can then encrypt all communications between the content server and other systems such as clients, web-based applications, and directory servers. |
|
Core Content Services |
|
| The Core Content Services provide the fundamental capabilities for accessing and storing repository content. These include library services, workflow services, lifecycle services, XML services, Enterprise Content Integration Services, Content Transformation Services, Content Intelligence Services, and Site Caching Services. |
|
Library Services |
|
Library Services manage content in three ways:
Library services, in turn, rely on an extensive set of security services to determine how users or applications are authenticated and authorized to access repository content. |
|
Workflow |
|
The Documentum workflow automates business activities and policies for repository content. A workflow is defined by a model, the sequence of steps that comprise the process, and the actions that must occur at each step. A workflow can describe a simple or complex process; it can be serial, with activities occurring one after another, or parallel, with all activities occurring simultaneously; and it can combine serial and parallel activities. Because an object’s workflow state is defined by a set of content attributes attached to the object, it travels with the object.
 Process Management Overview For example, a press release workflow might require an approval process involving five people and seven serial steps. The Documentum platform persistently manages the state of multiple instances of each workflow—often hundreds or thousands of instances—by storing workflow objects in the Documentum repository. Similarly, workflow templates (definitions) are stored as repository objects so various services, such as security, versioning, and retention, can be applied.  Case Management Overview |
|
Lifecycle |
|
The Documentum platform defines, maps, and implements flexible content lifecycle rules according to the business policies established by the enterprise.Like workflow, an object’s lifecycle state is defined by a set of content attributes attached to the object, so it also travels with the object. But instead of being defined by a flexible workflow model, lifecycle services are defined by a set of business policies or business rules. While a workflow routes a document among various users and automatic tasks, lifecycles define the business rules for changes that apply to content as it moves through predefined stages (such as “draft,” “in review,” “active,” and “obsolete”). As you might expect, unlike workflow, each content object has only a single lifecycle.Lifecycle services automate the lifecycle policies of repository content. These services assign a lifecycle stage to the content object, and then manage the object’s transition from one stage to another. An organization can extend the lifecycle stages to encompass its own operating policies
 Lifecycle and Retention Policies |
|
XML Services |
|
The Documentum platform provides XML services for managing XML documents in their native format within the Documentum repository. The platform provides the ability to automatically parse, validate, transform, map, and store imported XML documents. It also supports XML applications that directly store XML-tagged content to (and manage the content within) the Documentum repository.XML services provide several features that are essential for managing XML documents in their native format: XML content validation, automatic attribute population, XML link management, XML componentization, and XQuery. Documentum also provides XML Transformation services for XML, as discussed below (see Content Transformation Services).
|
|
Enterprise Content Services
|
|
| The Documentum platform includes technologies and services to integrate, access, and query content beyond the information stored within a Documentum repository. These federated search services are based on an Enterprise Content Integration Services (ECI) technology leveraging a framework of adapters for various internal and external repositories. Federated search is useful when interacting with information stored in third-party (non-Documentum) repositories and external websites. | |
Content Transformation Services |
|
| Documentum provides a framework and a suite of Content Transformation Services (CTS) for changing various kinds of content—such as documents, photos, video, and medical images—into different formats and resolutions. The CTS framework provide common administration, configuration and customizations of the various transformations. CTS services include: content analysis, metadata extraction, and thumb nailing for rich media content types to name a few. Transformations can occur synchronously or asynchronously. | |
Content Intelligent Services |
|
Content Intelligence Services (CIS) analyze the text within documents and other content objects, automatically classifying the content assets; put another way, CIS determines what the text is about. The results of the classification can be used to automatically populate the content metadata or to map the content assets into a taxonomy.CIS uses linguistic algorithms to analyze content, utilizing content-related terms, keywords, and attributes related to the information domain of an enterprise. CIS aggregates content from disparate sources, runs it through a parser, and uses three engines to analyze the resulting text. The three analysis engines include:
CIS produces a list of concepts contained within the set of documents or other content objects. These concepts can improve search accuracy as well as provide the ability to automatically categorize the repository |
|
|
|
Site Caching Services |
|
| Site Caching Services provides the replication of content to caching and delivery services in a run-time web infrastructure (including web server farms, enterprise portals, and application servers). Site Caching Services connects the source repository with a target distribution environment, and supports both one-way publishing and two-way user interactions. These services thus offer the flexibility, reliability, and scalability for publishing static, dynamic, and interactive content to disparate delivery environments. These services can also capture, ingest, and manage user-generated content.
Source OneEMC SourceOne™ eDiscovery – Kazeon automates in-house identification, collection, preservation (legal hold), processing, analysis, review, and policy-based management of unstructured content. It works with data sources such as file shares, desktops, laptops, Microsoft Exchange, Microsoft SharePoint, IBM Lotus Domino, Symantec Enterprise Vault, and EMC Documentum. The product enables your legal and IT teams to respond rapidly and efficiently to today’s information governance needs, including litigation, investigations, and compliance. In addition, you can proactively discover, classify, manage, and preserve information according to business value and risk. EMC SourceOne™ Email Management for Microsoft Exchange is a next-generation e-mail archiving solution that helps you reduce operational costs while enforcing e-mail record-keeping policies in compliance with internal governance as well as industry and government regulations. With EMC SourceOne Email Management for Microsoft Exchange, you improve user productivity by providing seamless access to archived content. You gain proactive information management to help with litigation readiness, including a centralized archive to accelerate large-volume discovery searches and enable secure legal hold. And you get the flexibility of a solution that scales to meet large enterprise needs, yet offers a simple footprint for midsize organizations. EMC SourceOne for Microsoft SharePoint leverages the underlying EMC SourceOne platform to help you manage challenges related to growing volumes of SharePoint content. It delivers operational, compliance, and litigation readiness benefits while providing a completely transparent end-user experience. SourceOne for Microsoft SharePoint gives you a building-block approach to managing SharePoint content that focuses on operational challenges. It also delivers compliance and, as you come to understand more about information in your SharePoint environment, you can apply long-term retention as well. |
required. For example, the repository can maintain multiple versions of a set of web pages, and revert to a version from a prior date when needed.
