Page Comparison

...

Create Connection | User Interface

Select Connections > Add connection.
Select Documentum as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Test the connection to ensure DryvIQ can connect using the information entered.
Select Done.

Add connection modal - Documentum

...

Field	Description	Required
Display as	Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named using the CMIS URL. For example, Documentum (http://XX.XX.XX.XXX:XXXX/emc-cmis/resources). If it will be useful for you to reference the connection by the URL, you should use the default name.	Optional
CMIS URL	Enter the URL for the Content Management Interoperability Services (CMIS) server.	Required
User name	Enter the username that should be used to log on to the server. This needs to be an account with permissions to access the content that will be processed.	Required
Password	Enter the password for the username added in the previous field.	Required
Repository	Enter the Documentum repository name.	Required
Item Type	Enter the item type that should be assigned to uploaded items. For example, cmis:document.	Optional
Secondary Item Types	Enter the secondary item types that should be applied. This is a comma or semicolon delimited list of item types for properties being retained as metadata. This is user defined and will vary by instance.	Optional
Agent URL	Enter the URL for the computer where the Documentum agent is installed. The Documentum agent provides access to additional functionality. This is an optional entry, but DryvIQ uses the entry to determine if additional features should be turned on for the connection. If this field is populated, DryvIQ turns on the additional features; if it is blank, DryvIQ assumes the agent is not being used and doesn’t turn on the additional features. See Documentum Agent under Features and Limitations for more information about the features enabled through the Documentum agent.	Optional
Lifecycle	Enter the lifecycle state that should be applied to the document when it is created. The DryvIQ extension module must be installed to use this option.	Optional

Connection Test Succeeded

...

Features and Limitations

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. The information below is platform specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations. Additional information about Documentum can be found in on the EMC Documentum Help.

...

Below is list of Documentum’s supported and unsupported features as well as additional file/folder restrictions.

Supported Features	Unsupported Features	Other Features/Limitations
Version preservation	Timestamp preservation	Path length maximum: 255
Author/Owner preservation Requires Documentum agent if Documentum is the destination	File size maximum	Invalid characters: \ \\ / < > : \| ? *
File lock propagation	Restricted types	No Leading whitespace
Mirror lock ownership	Segment path length	No trailing whitespace before extensions
Account map Requires Documentum agent

/wiki/spaces/S4D/pages/193691984

User impersonation	No trailing whitespace after extensions
Group map Requires Documentum agent	Tags map
Permission preservation Requires Documentum agent
Metadata map

Linked Documents

Per information in the EMC Documentum Help, links are used to associate items in the repository with different repositories or locations. Cabinets, folders, or files may be linked to a location in the repository, another repository, or a location on the local machine.

...

A basic Documentum connection can be made using the example below.

POST {{url}}v1/connections/

Code Block

{
  "name": "display name goes here",
  "platform": {
  	"id": "documentum"
  },
  "auth": {
        "uri": "http://CMIS URL",
        "username": "username",
        "password": "password",
        "repository": "repository name",
        "item_type": "cmis:document",
        "secondary_item_types": "property1;property2;property3",
        "agent_url": "http://CMIS URL/documentum-usermapping",
        "lifecycle": "lifecycle state"
	}
}

...

Create a Job | DryvIQ API Job Configuration Example

Below is an example Job for a connection created as standard user, no impersonation.

POST {{url}}v1/jobs

Code Block

{
    "name":"Simple Job",
    "kind": "transfer",
    "transfer": {
      "transfer_type": "copy",
        "source": {
            "connection": { "id": "Source Connection ID" },
            "target": {
                "path": "/sourceDocumentLibrary"
            }
        },
        "destination": {
            "connection": { "id": "Destination Connections ID" },
            "target": {
                "path": "/destinationFolder"
            }
        },
        "simulation_mode": false
    },
    "schedule": {
        "mode": "manual"
    },
    "stop_policy": {
        "on_success": 5,
        "on_failure": 5,
        "on_execute": 25
    },
    "category": {
      "name": "Report {Name}"
    }
}

Versions Compared

Old Version 8

New Version Current

Key

Create Connection | User Interface

Features and Limitations

Linked Documents

Create a Job | DryvIQ API Job Configuration Example