Connector for CMIS Setup and Reference Guide

Transcription

1 Connector for CMIS Setup and Reference Guide Published: 2018-Apr-20

2 Contents 1 CMIS Connector Introduction Products Supported features 4 2 Create a Data Source 6 3 Start URI for CMIS Data Sources 7 4 Connection to a CMIS Repository 8 5 Metadata Mapping Mapping for CMIS Properties Value-level Mapping 11 6 Smart Filter Value for CMIS Items 12 7 CMIS Exceptions 13 8 ACL Extraction for Decisiv Rules for Permissions Configuration Settings and Examples Enable or Disable ACL Extraction Define How Permissions Are Interpreted Specify Principals That Can Access Documents in Decisiv Give Document Access to Any Principal Decide How totreat Principals That Are Neither Allowed nor Denied Access 20 9 Configure the CMIS Connector Start URIs Enabled API URL User Password Use proxy server Proxy host Proxy port Use proxy authentication Proxy user name 24 Connector for CMIS - Setup and Reference Guide 2

3 9.11 Proxy user password Extract ACL Deny access for principals without permissions Permissions Normalization (PERL syntax) Anyone principals Standard properties Custom properties Document type Storage type Contact Us Terms of Use 34 Connector for CMIS - Setup and Reference Guide 3

4 1 CMIS Connector Introduction 1 CMIS Connector Introduction The CMIS connector can be used to load data from systems that follow the CMIS (Content Management Interoperability Services) standard. CMIS is an open standard that allows information sharing between different Content Management Systems. The connector uses the Apache Chemistry framework to directly access document and folder properties. The connector supports all CMIS standard properties. As the standard is based on a minimum number of common data, the connector may not be able to process items that are specific to a single content management solution. For example, the Connector for Microsoft SharePoint has a lot of features specific to SharePoint file extraction, but the CMIS connector can only load folders and documents. 1.1 Products This document applies to the following products and versions: Axcelerate on Premise, and later Versions below Axcelerate 5.14 may require patches. Decisiv 8.2 The connector supports CMIS 1.0 standard, which allows you to load data from diverse Content Management systems, and also from OpenText Infofusion 16.0 and up. 1.2 Supported features Feature Support Remark Full Crawl Incremental Crawl (with modification date and checksum) Deletion for incremental crawls Folder Security (ACL) Y Y/N N Y Supported if the source system provides modification date and checksum and if these properties are stable. Connector for CMIS - Setup and Reference Guide 4

5 1 CMIS Connector Introduction Feature Support Remark Versions Y/N Supported if the CMIS server returns stable IDs for the same items crawled multiple times. NAS Support N Exception Handling Y/N Supported if the CMIS server returns stable IDs for the same items crawled multiple times. Connector for CMIS - Setup and Reference Guide 5

6 2 Create a Data Source 2 Create a Data Source Independently of the CMIS source system, it is best practice to create a data source for file system crawls. This allows you to profit from all crawler features as far as the source data allows. To create a data source for the CMIS connector for Axcelerate: 1. In the Axcelerate Ingestion module, on the Data Sources tab, click Add new data source. 2. In the Define template type for data source step, select System template and click Next. 3. In the Define the data type of the data source step, select File and click Next. 4. In the Template selection step, select Server - file share. 5. In the Select folder to crawl step, enter the ID of the repository, preceded by cmis:/. If you are not sure of the repository ID, just enter cmis:/. You can change the URI after data source creation. 6. Follow the wizard. Tip: The wizard settings can be changed after data source creation. 7. In the last wizard step, do not choose Start immediately. Before starting the data source, you need to enter information that allows it to connect to the source system. To create a data source for the CMIS connector for Decisiv: 1. In CORE Administration, click an index engine below Document Model and, from the Actions menu, select Create data source. 2. In the Define template type for data source step, select System template. 3. In the Define Data Source Template step, select Document Model - File System. 4. Follow the wizard. 5. In the last step, click Finish. Connector for CMIS - Setup and Reference Guide 6

7 3 Start URI for CMIS Data Sources 3 Start URI for CMIS Data Sources To crawl from a CMIS repository, enter a start URI using the repository ID: cmis:/<repository ID>. Replace <repository ID> with the numeric ID that you see in CMIS Workbench when you click Repository Info. To enter the start URI: 1. In CORE Administration, open the data source configuration. 2. Go to Dataset definition > Dataset. 3. In the Start URIs field, add a new row. 4. Enter the start URI. Related: "Start URIs" on page 22 Connector for CMIS - Setup and Reference Guide 7

8 4 Connection to a CMIS Repository 4 Connection to a CMIS Repository Required: The CMIS source system is running and accessible by the data source crawler. If you use OpenText InfoFusion Integration Center, it is sufficient that the service can access the source system. Verify connectivity to the CMIS source using the Chemistry Workbench. Chemistry Workbench can be downloaded from the Apache Open Source project page. Before configuring the CMIS connector, make sure that the Chemistry Workbench shows all documents and all required document properties. Only data visible in the Chemistry Workbench can be accessed by the connector. If you use OpenText InfoFusion Integration Center for connecting to the source system, this service must be running and accessible by the data source crawler. There is a CMIS service user with at least read access to all data that you want to crawl. This is the user defined on the CMIS server and the user and password used to login using Chemistry Workbench. Connection settings, and security needed for the data load are set in the data source configuration, in the Crawler Connectors > DMS Connectors > CMIS > Connection node. Connector for CMIS - Setup and Reference Guide 8

9 4 Connection to a CMIS Repository Connection node You need to enter at least The API URL, i.e., the connection to the CMIS endpoint. This is the URL you enter to connect in the CMIS Workbench. To see it, click Connection and select the Basic tab. The URL pattern is: host name>:<port>/<cmis server>/atom11 If you use OpenText InfoFusion Integration Center, the URL is usually: host name>:38080/ifis-server/atom11 The user name and password used for crawling. You find the user name on the Basic tab of CMIS Workbench. Related: "API URL" on page 22 "User" on page 23 Connector for CMIS - Setup and Reference Guide 9

10 5 Metadata Mapping 5 Metadata Mapping All properties you can see in CMIS Workbench are taken over in the CORE document XML files' metadata. All metadata extracted from a CMIS source system is prefixed with cmis_ in the indexed XML document. There is no default mapping of metadata between the source system and the CORE system, as this connector is used for different source systems. Please work with our consultants to map required properties, in order to make the information available for display and or searching. It is best practice to run a test crawl and verify mapping works as expected. Property mapping node 5.1 Mapping for CMIS Properties You can map CMIS properties to crawler properties or CORE fields. Mapping to Standard Properties Mapping to standard crawler properties allows you to make use of Property Post Processing that is done before writing metadata to CORE fields. Property Post Pro- Connector for CMIS - Setup and Reference Guide 10

11 5 Metadata Mapping cessing is used to fill CORE fields with values that come from different properties, for example: Example: Basic mapping for a FileNet source CMIS property cmis:name cmis:contentstreamlength DocumentTitle cmis:lastmodificationdate Crawler property FILENAME FILESIZE TITLE LASTMODIFIEDDATE Mapping to CORE fields If there is no suitable standard property, map a CMIS property to one of the CORE fields that exist by default or that you created for this purpose, or to a crawler property that is not part of the standard properties. Non-standard crawler properties start with rm_. 5.2 Value-level Mapping Value- level mapping is available for: Document Type field that is used in the CORE system This field allows you to map values of CMIS properties that define types of documents to the values of the Document Type field. As Document Type field values are partially used for CORE system processing, only the exact values can be used. New values cannot be added. The source system values may be part of different CMIS properties. The mapped values appear in the Document Type Smart Filter. Storage Type field that is used in the CORE system You can map the source values to custom, new or existing, values in the Storage Type field. You can use this field, for example, to specify the source system or parts of the source system. Users can then filter for these values using the Storage Type Smart Filter. Related: "Standard properties" on page 29 "Custom properties" on page 30 "Document type" on page 30 "Storage type" on page 31 Connector for CMIS - Setup and Reference Guide 11

12 6 Smart Filter Value for CMIS Items 6 Smart Filter Value for CMIS Items To find CMIS items in the repository, use this Smart Filter: StorageType The value in this Smart Filter is CMIS entry for all indexed items. Connector for CMIS - Setup and Reference Guide 12

13 7 CMIS Exceptions 7 CMIS Exceptions If data is crawled using the CMIS connector, the Apache Chemistry library may throw runtime exceptions. You can see them as entries in the Exception Type or Exception Class Smart Filter after a crawl. The table below helps you identify the actual exception name. Mapping between crawler exception types and classes and CMIS exceptions Crawler exception type Crawler exception class CMIS Exception Access denied Access CmisOAuthException Access denied Access CmisPermissionDeniedException Access denied Access CmisProxyAuthenticationException Access denied Access CmisUnauthorizedException CMIS connection System CmisConnectionException CMIS connection System CmisServiceUnavailableException CMIS connection System CmisTooManyRequestsException Datasource problem Unexpected CmisVersioningException File not found Access CmisObjectNotFoundException Miscellaneous error Unexpected CmisRuntimeException Not supported Unexpected CmisConstraintException Not supported Unexpected CmisContentAlreadyExistsException Stream access Unexpected CmisStreamNotSupportedException Unexpected Unexpected CmisFilterNotValidException Unexpected Unexpected CmisInvalidArgumentException Unexpected Unexpected CmisNameConstraintViolationException Unexpected Unexpected CmisNotSupportedException Unexpected System CmisStorageException Connector for CMIS - Setup and Reference Guide 13

14 7 CMIS Exceptions Crawler exception type Crawler exception class CMIS Exception Unexpected Unexpected CmisUpdateConflictException Connector for CMIS - Setup and Reference Guide 14

15 8 ACL Extraction for Decisiv 8 ACL Extraction for Decisiv Required: Add ACL information to documents in the Common node of the data source configuration is selected (default that should not be changed). A user that logs into Decisiv gets a set of principals from login modules. These principals define the user's rights and the user's group memberships, etc. A user usually has several principals. The index engine compares these principals when it evaluates the visibility of a document. The principals extracted from ACLs (Access Control Lists) by the CMIS connector must match the principals returned by the login modules. 8.1 Rules for Permissions When you configure ACL settings, have these rules in mind: In the CORE system, groups that are denied access to documents prevail over groups that are allowed access. CMIS does not distinguish between users and user groups; the connector treats all principals as groups. This may lead to cases like this: John is a source system user and member of the Administrators group. This group is denied access to a file. John is nevertheless assigned a principal that should allowhim access to the file. After data has been loaded, John doesnot have access to the document in Decisiv. This is because the connector added him to the John group that is allowed access and to the Administrators group that is denied access. The denied right always prevails. 8.2 Configuration Settings and Examples To see the ACL of a document in the CMIS Workbench, click the ACL tab. In the connector configuration, you can configure these access details: Connector for CMIS - Setup and Reference Guide 15

16 8 ACL Extraction for Decisiv ACL settings node Enable or Disable ACL Extraction Select the Extract ACL check box to take over permissions as Decisivprincipals. If you clear the check box, the crawler will make all documents public, i.e., all Decisiv users can access them Define How Permissions Are Interpreted The CMIS standard knows these standard permissions: cmis:read, cmis:write and cmis:all. The connector treats the standard permissions as reading permitted by default. If the source system uses additional permissions, check whether the additional permissions need to be taken over by the connector. This is only the case if some documents' ACLs contain one of the standard permissions, and some don't. Example: Source system uses cmis:read for some documents, READ for other documents, and NO ACCESS cmis:read is covered by default. You only need to add the READ and the NO ACCESS permission to the Permissions table. Connector for CMIS - Setup and Reference Guide 16

17 8 ACL Extraction for Decisiv Syntax Pattern Ignore case Permission exact READ Yes Permitted exact NO ACCESS Yes Denied The Permitted permission will be added to all principals that have READ permission in the source ACL. cmis:read will be ignored, as it is a duplicate of READ. The Denied permission will be added to all principals with NO ACCESS rights in the source ACL. If a user belongs to different groups, with different principals, they will be assigned all permissions, even if they are conflicting. Example: The standard permissions shall not be used If you want to only use permissions that are specific to your source system, but no standard CMIS permissions, and the standard permissions may be mentioned in ACLs, you must list every permission you want to use and declare that you want to ignore the standard permissions. Entries in Permissions table Syntax Pattern Ignore Permission exact cmis:all Yes Ignored exact cmis:write Yes Ignored exact cmis:read Yes Ignored exact READ Yes Permitted exact ALL Yes Permitted With the above configuration, all standard permissions are ignored, even if they occur in a document's ACL. Only principals with READ or ALL permission get access in Decisiv Specify Principals That Can Access Documents in Decisiv To have access to a document, a principal extracted from ACLs must match a principal of the Decisiv Search login modules. The access information for documents loaded using the CMIS API must be extracted from the document properties that you see in CMIS Workbench. Connector for CMIS - Setup and Reference Guide 17

18 8 ACL Extraction for Decisiv The ACL principal property usually needs to be transformed by the connector to match the Decisiv principal. This is done in the Normalization (PERL syntax) table. Example: FileNet source system user principal The ACL principal is: cn=p8admin,o=sample This principal name must be mapped to a Decisiv principal, i.e., a Perl substitution must match the actual principal name. Entry in Normalization (PERL syntax) table Syntax Pattern Ignore case PERL substitution perl cn=.* Yes s/cn=(.*),o=."/$1/ For any ACL principal name starting with cn=, the connector will remove cn= and,o=sample, and only keep the part P8Admin. This part must match a login module principal. Connector for CMIS - Setup and Reference Guide 18

19 8 ACL Extraction for Decisiv Example: File share source group principal Entry in Normalization (PERL syntax) table Syntax Pattern Ignore case PERL substitution perl BUILTIN.* Yes s/builtin\(.*)\s:./$1/ For any ACL record starting with BUILTIN, the connector will remove BUILTIN\ and the part that starts with S:, and only keep the actual principal name, which is Administrators. This name must match a login module principal name Give Document Access to Any Principal You can make a document public using a principal that represents anyone. A document becomes public in Decisiv if the source system contains a principal that represents any authenticated user or anonymous user Connector for CMIS - Setup and Reference Guide 19

20 8 ACL Extraction for Decisiv the document's ACL contains the principal with read permission you list this principal in the Anyone principals table The connector then ignores any other principal with read access for a document, and only adds additional denied principals according to what is defined in the Permission and Normalization (PERL syntax) tables. Example The #AUTHENTICATED-USERS principal of a FileNet source system document has the standard cmis:read permission. If you list this principal in the Anyone principals table, then any user that is not denied access can view this document. Entry in Anyone principals table Syntax Pattern Ignore case exact #AUTHENTICATED-USERS Yes Decide How totreat Principals That Are Neither Allowed nor Denied Access You can allow all principals with no explicit allowed or denied permission to access documents. To do so, clear the Deny Access for principals without permission check box. If you keep the default setting, i.e., select the check box, then principals without any permission are denied access. However, if an ACL contains an anyone principal with allowed access, then selecting this check box has no effect for the respective document. Connector for CMIS - Setup and Reference Guide 20

21 8 ACL Extraction for Decisiv Note: There may be cases where additional configuration by Customer Support is needed. Related: "Extract ACL" on page 25 "Deny access for principals without permissions" on page 25 "Permissions" on page 26 "Normalization (PERL syntax)" on page 27 "Anyone principals" on page 28 Connector for CMIS - Setup and Reference Guide 21

22 9 Configure the CMIS Connector 9 Configure the CMIS Connector The configuration settings in CORE Administration are shown in the order they appear in the user interface. 9.1 Start URIs Start URIs can trigger the use of a specific connector. For some connectors, the Start URI is the access point to the data to be loaded. Some connectors require additional connection information. Besides URIs, certain common file path syntaxes are allowed. Note: Look for connector-specific start URI information in the first part of this documentation. Example URIs are file:///d:/data/, d:\data for files in Windows file systems; /home/usr/data/, file:///home/usr/data/ for files on a UNIX file system; csv:///d:/data for CSV load files; and for the Web. For access to a database using an ODBC bridge, use jdbc:obdc:odbcdatasource; and for a generic JDBC data source, use the appropriate JDBC connection string. Location: Data source: Dataset definition > Dataset Allowed values: anything allowed in URIs or file paths None 9.2 Enabled Enables the CMIS connector if selected. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: true false false 9.3 API URL AtomPub URL of the CMIS service. Connector for CMIS - Setup and Reference Guide 22

23 9 Configure the CMIS Connector Example: For OpenText InfoFusion Integration Center, the URL is usually host name>:38080/ifis-server/atom11 Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: host name>:<port>/<server name>/atom11 empty 9.4 User User name for connecting to the CMIS service. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: text 9.5 Password Password of the CMIS service user. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: text 9.6 Use proxy server Select this check box if a proxy server is used for the communication between the connector and the CMIS service. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: true false false Connector for CMIS - Setup and Reference Guide 23

24 9 Configure the CMIS Connector 9.7 Proxy host Host name of the proxy server. Examples: proxy.example.com, Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: text 9.8 Proxy port Port number of the proxy server. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: Use proxy authentication Select this check box if authentication is needed for the proxy server. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: true false false 9.10 Proxy user name User name for the proxy server. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: text Connector for CMIS - Setup and Reference Guide 24

25 9 Configure the CMIS Connector 9.11 Proxy user password Password for the proxy server user. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Connection Allowed values: text 9.12 Extract ACL Select the Extract ACL check box to take over permissions of CMIS principals for Decisiv principals. If you clear the check box, the crawler will make all documents public, i.e., all Decisiv users can access them. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > ACL settings Allowed values: true false false 9.13 Deny access for principals without permissions If this check box is selected, principals that have no explicit permitted or denied permissions (cmis:read, cmis:write or cmis:all or any other listed in the Permissions table) are explicitly added as denied principals, i.e., if there are no permissions for the principal, or none of the permissions have been mapped, or all of the permissions have been mapped to be ignored. Selecting the check box has no effect if there is an anyone principal in the Anyone principal table that is allowed access for an item. If this check box is cleared, an item will become public, i.e., every principal has access unless they are explicitly denied access to the item. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > ACL settings Connector for CMIS - Setup and Reference Guide 25

26 9 Configure the CMIS Connector Allowed values: true false true 9.14 Permissions Define which permissions should be mapped to permitted or denied read access or be ignored. The basic CMIS permissions cmis:read, cmis:write and cmis:all are treated as permitted read permissions by default. If they will not be used, they must be explicitly excluded, i.e., listed as Ignored. The first match defines the mapping. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > ACL settings Syntax Define whether the pattern requires an exact match or if it is a glob or perl expression. Allowed values: perl glob exact perl (NOT) glob (NOT) exact(not) exact Pattern Pattern that matches a permission. Allowed values: text, glob or regular expression Axcelerate Review & Analysis: value Axcelerate Ingestion: value Decisiv: value Ignore case If selected, matches are case insensitive. Connector for CMIS - Setup and Reference Guide 26

27 9 Configure the CMIS Connector Allowed values: true false true Permission Access permission as needed for Decisiv. Allowed values: Denied Ignored Permitted Ignored 9.15 Normalization (PERL syntax) Enter a PERL substitution pattern which will be applied to source system ACL principals that match the configured pattern. The substitution result should match a Decisiv user name. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > ACL settings Syntax Define whether the pattern requires an exact match or if it is a glob or perl expression. Allowed values: perl glob exact perl (NOT) glob (NOT) exact(not) exact Pattern Pattern that matches a principal entry in ACLs. Connector for CMIS - Setup and Reference Guide 27

28 9 Configure the CMIS Connector Allowed values: text, glob or regular expression Ignore case If selected, matches are case insensitive. Allowed values: true false true PERL substitution PERL substitution of the entry matching the pattern. Allowed values: regular expression 9.16 Anyone principals Enter regular expressions for principals that should be treated as anyone or anonymous. If such a principal has read permissions for a document, the document will be treated as a public document. Everyone can read it except for explicitly denied principals. Principal normalization is executed before the principals are checked against these patterns. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > ACL settings Syntax Define whether the pattern requires an exact match or if it is a glob or perl expression. Connector for CMIS - Setup and Reference Guide 28

29 9 Configure the CMIS Connector Allowed values: perl glob exact perl (NOT) glob (NOT) exact(not) exact Pattern Pattern that matches a principal after normalization. Any document with a principal matching this pattern will be treated as public document. Allowed values: text, glob or regular expression Ignore case If selected, matches are case insensitive. Allowed values: true false true 9.17 Standard properties Define the mapping between CMIS properties and crawler standard properties. Use the property ID of the CMIS properties, e.g., cmis:name. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Property mapping CMIS Property Property ID as used in the source system. Allowed values: text Recommind Property Connector for CMIS - Setup and Reference Guide 29

30 9 Configure the CMIS Connector Crawler standard property. Allowed values: Properties available in the drop-down list Custom properties Define the mapping between CMIS properties and custom properties. These may be other crawler properties (starting with rm_) or CORE fields, as shown in the document model. Use the property ID of the CMIS properties, e.g., cmis:name. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Property mapping CMIS Property Property ID as used in the source system. Allowed values: text Recommind Property Property or field name in the target CORE system. Allowed values: text 9.19 Document type Define the mapping between CMIS properties and values of the CORE Document type field. Use the property ID of the CMIS properties, for example, cmis:objecttypeid. Values should be written in the same way as in the source system. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Property mapping CMIS Property Property ID as used in the source system. Allowed values: text Connector for CMIS - Setup and Reference Guide 30

31 9 Configure the CMIS Connector CMIS Value Value that occurs in the CMIS property. Allowed values: text Document type Value of the Document type field that is mapped to the CMIS value. Allowed values: Values available in the drop-down list Storage type Define the mapping between CMIS properties and values of the CORE Storage type field. Use the property ID of the CMIS properties, for example, cmis:objecttypeid. Values should be written in the same way as in the source system. Location: Data source: Crawler Connectors > DMS Connectors > CMIS > Property mapping CMIS Property Property ID as used in the source system. Allowed values: text CMIS Value Value that occurs in the CMIS property. Allowed values: text Document type Value of the Storage type field that is mapped to the CMIS value. You can define new values, by adding any text. Connector for CMIS - Setup and Reference Guide 31

32 9 Configure the CMIS Connector Allowed values: text Connector for CMIS - Setup and Reference Guide 32

33 10 Contact Us 10 Contact Us About OpenText OpenText provides the most accurate and automated enterprise search, automatic classification, and ediscovery software available, giving organizations and their users the information they need when they need it. Visit us at Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: Toll Free Canada/USA: International: Fax: Support For support issues on our products, documentation, Knowledge Base articles and more information, use the Ticketing System on My Support. Documentation Find product documentation, Knowledge Base articles, and more information on My Support. For login access to the site, contact OpenText Support. The Documentation team is interested in your feedback. For comments or questions about Recommind product documentation, contact the documentation team. Connector for CMIS - Setup and Reference Guide 33

34 11 Terms of Use 11 Terms of Use Disclaimer This document, as well as the products and services described in it, is furnished under license and may only be used or copied in accordance with the terms of the license. The information in this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Open Text, Inc., including its affiliates and subsidiaries (collectively, "OpenText"). OpenText assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software or services that may be provided in association with this document. Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of OpenText. Information in this document is provided in connection with OpenText s products and services. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. EXCEPT AS PROVIDED IN OPENTEXT S SOFTWARE LICENSE AGREEMENT OR SERVICES AGREEMENT FOR SUCH PRODUCTS OR SERVICES, OPENTEXT ASSUMES NO LIABILITY WHATSOEVER, AND OPENTEXT DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF OPENTEXT PRODUCTS OR SERVICES INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. OPENTEXT MAKES NO WARRANTIES REGARDING THE COMPLETENESS OR ACCURACY OF ANY INFORMATION, NOR THAT THE PRODUCTS OR SERVICES WILL BE ERROR FREE, UNINTERRUPTED, OR SECURE. IN NO EVENT WILL OPENTEXT, THEIR DIRECTORS, EMPLOYEES, SHAREHOLDERS AND LICENSORS, BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT, SPECIAL OR EXEMPLARY DAMAGES INCLUDING, BUT NOT LIMITED TO, LOSS OF ANTICIPATED PROFITS OR BENEFITS. OpenText may make changes to specifications, and product and service descriptions at any time, without prior notice. OpenText's products may contain design defects or errors known as errata that may cause the product or service to deviate from published specifications. Current characterized errata are available on request. Whilst every effort has been made to ensure that the information and content within this document is accurate, up-to-date and reliable, OpenText cannot be held responsible for inaccuracies or errors. OpenText software, services and documentation have been developed and prepared with the appropriate degree of skill, expertise and care. While every effort has been made to ensure that this documentation contains the most up-to-date and accurate information available, OpenText accepts no responsibility for any damage that may Connector for CMIS - Setup and Reference Guide 34

35 11 Terms of Use be claimed by any user whatsoever for the specifications, errors or omissions in the use of the products, services and documentation. Trademarks and Patents OpenText's underlying technology is patented under U.S. Patent Nos. 6,687,696, 7,328,216, 7,657,522, 7,747,631, 7,933,859, 8,024,333, 8,103,678, 8,429,159 and 8,489,538 Open Text, Inc. is the leader in predictive information management and analysis software, delivering business applications that transform the way enterprises, government entities and law firms conduct ediscovery, enterprise search, and information governance. OpenText, Recommind, Axcelerate, Axcelerate Cloud, Axcelerate OnDemand, and CORE s name and logo are registered trademarks of Open Text. Copyright Copyright 2018 Open Text. All Rights Reserved. Trademarks owned by Open Text. Connector for CMIS - Setup and Reference Guide 35