About the iManage Connector

Overview

The iManage connector is a web-service connector that enables you to index iManage content with security.

It supports all standard connector capabilities:

Incremental and Full crawls
Security
Metadata Provides context with details such as the source, type, owner, and relationships to other data sets. Metadata provides details around the item being crawled by Connectivity Hub.

Enables searching for any kind of document stored in iManage.
Operates with minimal impact on iManage.
- Once content is crawled, all search activity takes place in SharePoint, or any other portal.
Provides high performance indexing, so large amounts of content can be made available to users.
Leverages iManage security to determine which documents users can access.
All content remains safely in iManage.
- The portal has only a searchable representation of documents – pointers – and users are directed back to iManage to launch documents found in their search result.

Instances of *.imanage.work tenants are NOT supported.
Instances of cloudimanage.com tenants are supported.
If you are crawling more than 10,000 users, groups, or group members, you must use the iManage with Sync API service when you setup your connection Connection defines the how Connectivity Hub connects to your Source System (which contains your documents, graphics, etc.,). Your Connection includes identifying elements such as: URL of the BA Insight web service connector you are using, (File Share connector, SharePoint Online connector, etc.), Authentication mode, User Accounts and Credentials, Database information (for database connectors). If you want to continue to use the iManage Work API, you can implement the workaround in the web.config settings
If you are upgrading to the iManage connector 2.1.0.0, and you are going to use the new iManage with Sync API service, you must rerun all your security sync jobs Loads User and Group tables and executes the mapping based on the connector configuration. and perform a full crawl job.

Note: Start date setting on content settings page is not supported.

Important! A full crawl is required whenever the last incremental crawl Scanning and capturing only new data from all of your content sources. This data did not exist when the last crawl was run./ full crawl was started more than 2 weeks ago.