Documentum

Documentum is an enterprise content management platform. Its functionality is made available through application programming interfaces (API).

Most of the customisation in the basic product is done using the DFC (Documentum Foundation Classes), a comprehensive collection of Java APIs. Customisation can be done via configuration, particularly through the extension products D2 and xCP. These additions aim to provide faster ways of building applications based on document types and metadata, and business processes, respectively.

Authentication Connection

This connector require an Authentication Connection to function. Authentication connectors are used to authenticate repository/output connections that need certain authentication fields like access tokens or refresh tokens.

  1. Select Authentication from the navigation menu or the dashboard.

  2. Click the New Authentication button

  3. Enter a unique name for the connection and give it a description

  4. Select the connection type from the drop-down and click save.

  5. Fill in the configuration settings on the edit connection page and click save.

Authentication Connections Overview

Configuration

Discovery Instance

Configuration

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide to Integration connections

The Documentum DFC (Documentum Foundation Classes) Integration Connection is for retrieving content, and it's associated metadata from a Documentum Repository based on root folder, content type and document type. 3Sixty is currently compatible with Documentum v5 and higher. The Documentum Integration Connection utilises the DFC library along with DQL (Documentum Query Language) to sync/integrate content, and it's associated metadata to Documentum. 3Sixty is currently compatible with Documentum v5 and higher.

DFC Query Repository Connector

There is a new Documentum connector called the DFC Query Connector it's query based, not folder crawl based

Configuration

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under Jobs on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

Repository Run Options:

Repository Cache Options

Max Number of Items in Cache:Maximum number of folders to keep cached

Output Specifications

When using this connector as a file destination, filling out the following fields will tell 3Sixty where you want the files integrated to.

Configuration

Mapping

3Sixty Mapping gives you the ability to map your content types and metadata from one system to another.

There are two places in 3Sixty where you can set up mappings:

  • At the top of the mapping tab you can select from saved mappings

  • Creating a unique mapping based on your connectors.

Guide to 3Sixty Mapping

Tasks

Job tasks also known as processors provide a processing pipeline for documents and metadata. Post processors can also be added as a task to run after the files are processed.

Click here for a list of all the tasks you can add to your integration job.

  1. Click on the task tab in your integration job.

  2. Find the task you want to create in the drop down. Tasks are grouped by type. You can also search for the task by name.

  3. Select the create task button

  4. Fill out the configuration fields. Some tasks do not require configuration.

  5. Click Done to save the task to your job.

Troubleshooting

In a case of Troubleshooting the Documentum DFC Connector, there may be the need to look for resource leaks. To detect these leaks, a property will need to be added to your dfc.propertiesfile. If you do not have adfc.propertiesfile, create one in the web application'sWEB-INF/classes directory with the single entry. This will allow for the detection of the leaks and provide a statement about the cause of the leak in your log files. The entry to add to your log file isdfc.diagnostics.resources.enable=true

For more information see the official documentation here.

3Sixty comes pre-packaged with some required dependencies for Documentum. If you experience errors related to missing classes or any errors stemming from the DFC connector classes you may need to replace existing DFC dependencies with files from your targeted Documentum server. 3Sixty is currently compatible with Documentum v5 and higher.

  1. Locate the following jars on your Documentum server:

  • dfc.jar

  • configservice-api.jar

  • configservice-impl.jar

  1. Copy those jars to your 3Sixty server

  2. Delete the dfc-1.0.jar file from the tomcat/webapps/3sixty-admin/WEB-INF/lib directory.

  3. Place Documentum jars in the tomcat/webapps/3sixty-admin/WEB-INF/lib directory.

  4. Restart 3Sixty.

Note: There are known compatibility issues with the external DFC dependencies and Java 11. If you are using Java 11 and experience start-up errors after adding the external dependencies, please consider using Java 8.

Content Service Connector

Note:  An Auth connector is not needed for the Documentum DFC content service connector. For Security Mode, choose Service Provided Credentials

Managing Permissions with Documentum DFC Content Services

As of Version 2.7.6, this connector also offers permissions support using the /acls content service endpoint.

The API supports GET, POST, and DELETE calls.

All the endpoints take the "id" parameter, which takes the form of a string.

Supported Methods

  • checkIn

  • checkOut

  • createFile

  • createFolder

  • createVersion

  • deleteACL

  • deleteFolder

  • deleteObjectByID

  • deleteVersion

  • getACLs

  • getFileContent

  • getObjectProperties

  • getTypes

  • getVersionContent

  • getVersionProperties

  • listFolderItems

  • listVersions

  • revertVersion

  • setACLs

  • updateFile

  • updateProperties

Looking to integrate with Documentum? We can help.