Understanding Repository Services

Trusted Content Services

Trusted Content Services (TCS) provides additional security features such as digital shredding of content files, strong electronic signatures, content encryption, and enhanced ACLs.

Content Services for EMC Centera

Content Services for EMC Centera (CSEC) adds support for Centera storage for guaranteed retention and immutability. Centera storage is suitable for storing large amounts of infrequently changing data that needs to be retained for a specific period.

Content Storage Services

Content Storage Services (CSS) enables the use of content storage and migration policies, which automate the assignment of content to various storage areas. CSS can be used for optimizing the use of storage infrastructure in the enterprise. CSS also provides features for content compression and de-duplication.

Retention Policy Services

Retention Policy Services (RPS) 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 off or archived.

Understanding WebContent Management

Web Publisher WP

Authoring and publishing of websites into (local intranet) web sites and portals. Iis part of the Collaboration Services of the WDK.
Proviedes some authoring tools:

WP Roles

wcm_content_author_role
wcm_content_manager_role
wcm_web_developer_role
wcm_administrator_role

Digital Asset Manager DAM

organizes images and video clips, create thumbnails and is part of the Collaboration Services of the WDK.

 

Understanding Object ID

Every persistent object has the unique property r_object_id . The property has 16 digits from type string. Every character is one hexadecimal digit.

The first two digits representing the type of the object. The next six digit representing the Repository ID and the last eight digits display the unique object ID

Example: r_object_id for one dm_document object: 090003fb900100ff

Example: r_object_id for one dm_user object stored in the same repository:110003fb12345678

Type
and all subtypes(child objects)
Digit
object types (excerpt)hexadecimal
dm_type03
dmr_content06
dm_component08
dm_sysobject08
dm_document09
dm_user11
dm_group12
dm_relation37
dm_acl45
dm_policy46
dm_alias_set66
dm_folder0b
dmi_queue_item1b
dmi_workitem4a
dm_process4b
dm_workflow4d
dm_audittrail5f

 

Understanding Data dictionary

What the data dictionary is

The data dictionary is a collection of information about object types and their properties.
The information is stored in internal data types and made visible to users and applications through the process of publishing the data.

EMC Documentum Content Server Version 6.5 Fundamentals

The data dictionary is the mechanism you can use to localize Content Server. The data dictionary supports multiple locales. A data dictionary locale represents a specific geographic region or linguistic group.

Publishing the data dictionary

Data dictionary information is stored in repository objects that are not visible or available to users or applications. To make the data dictionary information available, it must be published. Publishing the data dictionary copies the information in the internal objects
into three kinds of visible objects:

  • dmi_dd_attr_info
    Contains the published data dictionary information for a property.
  • dmi_dd_common_info
    Contains the published data dictionary information that an object type and property have in common.
  • dmi_dd_type_info
    Contains the published data dictionary information for an object type.

For example, if a site has two locales, German and English installed, there will be two dd_type_info objects for each object type—one for the German locale and one for the English locale. Similarly, there will be two dd_attr_info objects for each property—one for the German locale and one for the English locale. However, there will be only one dd_common_info object for each object type and property because that object stores the information that is common across all locales.

Retrieving data dictionary information

You can retrieve data dictionary information using DQL queries or a DFC method. Using DQL lets you obtain multiple data dictionary values in one query. However, the queries are run against the current dmi_dd_type_info, dmi_dd_attr_info, and dmi_dd_common_info objects. Consequently, a DQL query may not return the most current data dictionary information if there are unpublished changes in the information.
Neither DQL or DFC queries return data dictionary information about new object types or added properties until that information is published, through an explicit publishDataDictionary method (in the IDfSession interface) or through the scheduled execution of the Data Dictionary Publisher job.