Autonomy iManage and OpenText eDocs both have protocol handlers for SharePoint, which enable the SharePoint Enterprise Search engine to index documents stored in the DMS, while keeping the documents in the DMS.  Many people haven’t been aware of this and thought you had to migrate all of the documents into SharePoint to search them, or to use an enterprise search engine provided by the DMS vendor.  However, these protocol handlers can provide the best of both worlds by allowing you to continue managing documents in the current DMS, while taking advantage of Microsoft’s FAST enterprise search indexer to index the DMS content, SharePoint content, file shares, web sites, Exchange public folders, and other enterprise systems.  Security trimming is preserved by the protocol handler, so users will never see documents in the DMS that they don’t have access to.  The protocol handlers both support Microsoft Office SharePoint Server 2007.

More information on the OpenText eDocs SharePoint integration and protocol handler can be found here:

http://www.opentext.com/download/livelinkdownload.html?path=product/microsoft/ot-clmsp-edocs-po.pdf

More information on the iManage SharePoint protocol handler can be found in their partner portal, by filtering the list of products to “SharePointProtocol Handler.”  Note that you need a partner login account to download the documentation and release notes.

http://worksitesupport.interwoven.com/WorkSite/scripts/portal.aspx

Both vendors also offer a comprehensive set of web parts to drop into a SharePoint environment to view and manage their documents from within a SharePoint site.

For those of you keeping up to date with your Open Text eDOCS DM environment, you may have experienced the following issue with version 5.2.1 CU3 (and possibly other versions).   When using DM Extensions, the new Save User Interface built into DM 5.2 may take up to 20 seconds or longer to render, causing annoying delays when saving documents.

Open Text recently posted a simple resolution for this issue.  From the Open Text Knowledge Base:

This issue can be resolved by moving two files on the client computer.

1. Navigate to the following folder:

C:\WINDOWS\system32\wbem\Framework\root\Hummingbird\Extensions

2. Move the following two files from the above folder to a safe storage location; do not delete the files as they may be needed for future logging or troubleshooting purposes:

Hummingbird.DM.Extensions.Logging.Logger_SN__Version_5.2.1.0.cs
Hummingbird.DM.Extensions.Logging.Logger_SN__Version_5.2.1.0.mof

3. Restart DM Extensions.

DM 5.2.1 CU4 was recently released, and this particular issue is not listed in the Fixed Issues documentation.  We’ll see if a future update resolves the issue entirely, but the steps above can be a simple way to immediatley improve performance if you are seeing this behavior. 

For customers and partners, the Open Text Knowledge Base and software downloads can be accessed here.