If you want to connect CMIS repositories to ADx, you need to enter the specifications of all object types in a given CMIS repository so that ADx knows it. This is necessary so that data available in the remote CMIS repository can be correctly represented in ADx. This page explains how to configure type definitions on CMIS-compatible repositories.
Before you configure type definitions, it's helpful to read about OASIS specification for better understanding.
Log in to ADx. Go to the Administrator page:
Select a CMIS repository and click Details.
Under Connection, find the Type Definitions section. Click Assign/Create New to start assigning a new definition. New CmisTypeDefinitions form opens.
You now have the options to add the definition of all CMIS base object types, including: document, folder, item, policy, secondary, all types (where you can save any CMIS base type specification) and unknown (used if additional object types exist in the CMIS repository).
Click Assign under the correct category to start defining a base type of your CMIS repository.
Enter the CMIS specification:
Property Explanation definitionId Enter the
idattribute of the CMIS object you're describing.
KIND One of CMIS base object types. Select the type you're currently describing. localName Enter the
localNameattribute of the CMIS object you're describing.
baseType If the object you're currently describing is NOT a CMIS base type, you can assign its base type here. canCreate canDelete canUpdate description description of this specification displayName How this CMIS object is represented in ADx (for example, you could use CMIS Folder for FOLDER kind). isBaseType Select if this object is a CMIS base type (document, folder, item, policy, secondary). isControllableAcl Select
falseas defined on CMIS side. This attribute indicates whether or not objects of this type are controllable by ACL’s. Only objects that are
controllableACLcan have an ACL.
falseas defined on CMIS side. Indicates whether or not objects of this type are controllable via policies. Policy objects can only be applied to controllablePolicy objects.
falseas defined on CMIS side. Indicates whether new objects of this type MAY be created. If the value of this attribute is FALSE, the repository MAY contain objects of this type already, but MUST NOT allow new objects of this type to be created.
falseas defined on CMIS side. Indicates whether or not objects of this type are ﬁle-able.
falseas defined on CMIS side. Indicates whether objects of this type are indexed for full-text search for querying via the CONTAINS() query predicate. If the value of this attribute is
TRUE, the full-text index MUST cover the content and MAY cover the metadata.
falseas defined on CMIS side. Indicates whether this type and its subtypes appear in a query of this type’s ancestor types. For example: if Invoice is a sub-type of cmis:document, if this is TRUE on Invoice then for a query on cmis:document, instances of Invoice will be returned if they match. If this attribute is FALSE, no instances of Invoice will be returned even if they match the query.
falseas defined on CMIS side. Indicates whether or not this object-type can appear in the FROM clause of a query statement. A non-queryable object-type is not visible through the relational view that is used for query, and CAN NOT appear in the FROM clause of a query statement.
localNamespace Enter the
localNamespaceattribute of the CMIS object you're describing.
parentType Assign the parent type if it's present on the CMIS object you're describing. queryName Enter
queryNameattribute of the CMIS object you're describing.
children If this CMIS object type has any children, enter their specification here. properties Enter any additional properties of the CMIS object, if they are present.
Having defined CMIS types, you can continue configuring your CMIS repository.