CMIS

Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to interoperate over the Internet. Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols.

Connector Compatibility

Repo: Yes

Output: Yes

Content Service: Yes

Content Search: No

Manage In Place:

More info on connection types

Note:  If going from CMIS to CMIS, associations are only included if job type mappings are included


Authentication Connection

  • Name: The name of your CMIS authentication connector

  • Username: Username to authenticate with.

  • Password: Password to authenticate with.

  • URL: The full URL leading to your CMIS endpoint

  • Binding: AtomPub or Web Services. AtomPub is the default and most common choice.

  • Repository ID: You can specify a specific repository to query.

  • Vendor (CMIS 1.0 Only): No vendor, Alfresco, or FileNet


Discovery Connection

Discovery makes mapping to and from your sources easier for data migration and ensures the data gets connected to the right fields. Discovery requires an Authentication Connection

Guide to Discovery Connections

The CMIS Discovery Connector requires a CMIS Authentication Connection

  • Name: Unique name for your connector

  • Authentication Connection: Select the auth connector for this discovery

  • Ignore Types (comma delimited list): Chose document types to ignore when running discovery

  • Repository ID: You can specify a specific repository to discovery if supported by your specific CMS. The CMIS Discovery Connector will discover all content models including their metadata and properties.


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.

There are no fields to configure in an integration connection.

Guide toIntegration connections

Utilising the CMIS Query Language, the CMIS Integration Connection allows the user to query the CMS system for content and metadata. It is also designed to write content, and it's associated metadata into a CMIS compliant Content Management System (CMS). This connector leverages the Apache OpenCMIS API v1.1.

To set up the CMIS Integration Connection fill in the following fields:

  • Connection Name: Name the Connector

  • Description: Add a description for the connector

  • Authentication Connection: Select the Auth connector

  • Secondary Auth Connection: Not used for CMIS


Content Service Connection

This connection will provide a full ECM API for interacting with files, folders, metadata, versions, and renditions.

Content Service Connections Overview

Basic Configuration

  • Connector ID: Give your connector a unique name

  • Description: Provide a description for this connection

  • Type: Select the Filesystem Content Service Connector

  • Keep Connection Alive: Keep this connection active

  • Keep alive in Milliseconds (300000 is 5 minutes): How long until connection expires if unused

  • Connection URL: The web address for your connection

  • Security Mode: None needed for this connection

  • Mapping Type: Choose single map or group mapping if you are using mapping for jobs


Job 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.


API Keys

CMIS Connector: Read=true: Write=true: MIP=false

Repo (Read) Specs

Key

Description

Data Type

cmisQuery CMIS Query You must select from cmis document d. We use d.cmis lastModificationDate for date range queries String

cmisQueryOrderBy

CMIS Query Order By

String

versionDepth

Version Depth

Integer

includeRelationships

Include Relationships will make the connector look for relationships on each document.

Boolean

searchallversions

Search All Versions?

Boolean

Output (Write) Specs

Key

Description

Data Type

outputfolderpath Output Folder Path String

strictversionmode

Strict Version Mode (true/false)

Boolean

cacheenabled

CMIS Cache Enabled (true/false)

Boolean

addacl

Add ACLs

Boolean

incaspnofm

Include Aspects With No Field Mappings

Boolean

eanvfl

Aspect Remove Field Mapping

String

cmisUpdateQuery

CMIS Update Query

String

cicoou

Check In / Check Out On Updates

Boolean

cmisupbin

Update Binary on Updates

Boolean


Looking to integrate a CMIS compliant system? We can help.