Products
Supported features
The features of EMC Documentum that we support are listed in the following table. In this table, export refers to getting data from a docbase and import means putting data back in the docbase.
| Feature | Level of support |
|---|---|
| Folder structure | The folder structure is exported and imported as necessary to restore documents. |
| Document types and custom attributes | Document types can be exported and imported. |
| Versions | All versions of a document and all version labels can be exported and imported. |
| Content | All content pages can be exported and imported. |
| Renditions | Renditions can be exported and imported. |
| VDMs | VDM structures can be exported and imported. |
| VDM binding rules | VDM binding rules (both late and early binding) can be exported and imported. |
| VDM versions | As VDMs are regular documents internally, versioning of VDMs is automatically supported. |
| Groups | Groups and its members can be exported and imported. |
| Users | Users can be exported and imported. |
| ACLs | ACLs and the associated access rights can be exported and imported. |
| Relations | Relations can be exported and imported. Relation types are automatically exported and imported as necessary. |
| Specific document attributes | Specific attributes that we support are: owner, status |
| Transferring audit trails. | MirrorNG supports exporting and importing the audit trail in the source system to a registered table in the target system. |
| Creating audit trail entries | MirrorNG supports creating a custom audit trail entry in the target system for each migrated document. This entry can mark the migration date, the source system, etc. |
| Cleaning audit trail | MirrorNG can clean the audit train in the target system. The migration tool creates several audit trail entries in the target system that are usually unwanted. This works together with the feature of creating a custom audit trail entry. |
Below we list features that are sometimes initially requested by our clients but that we ended up never needing. This means that MirrorNG does not support them yet, but that we can support without much effort.
| Feature | Details |
|---|---|
| Setting attributes managed by Documentum | This includes attributes such as modifier, modification date, creator, creation date, ... These cannot be set by the usual means but have to be set by low level database statements, and some of these attributes are changed by Documentum when any changes are made to a document. Usually it is better to set these attributes after the migration with MirrorNG. |
| Transferring the audit trail | Recreating the audit trail in the target system is not supported (except in a registered table as explained above). The interface to Documentum that we use allows us to create these entries, but the migration activities usually create extra entries so it is usually better to clear and recreate the audit trail after migration with MirrorNG. |
| Transferring registered tables | The import of registered tables is present because it is needed by one of the features above; the export of registered tables is not yet fully supported but is not complicated. Which registered tables to transfer and how to identify the entries in the table related to a document is fully configurable for the import and would also be for the export. |
Request a demo
Want to see what MirrorNG can do? Request a MirrorNG demo
NEW CMIS Support
NEW SharePoint Support
Documentum Support
I appreciated the quick response when I send out a mail, no matter at what time of the day or day of the week.
