Legacy Update: Get back online, activate, and install updates on your legacy Windows PC

Microsoft SharePoint 2010 Indexing Connector for Documentum enables your SharePoint 2010 products to index the contents of an EMC Documentum repository.

• Microsoft SharePoint 2010 Indexing Connector for Documentum enables SharePoint 2010 products to index the contents of an EMC Documentum repository. Once indexed, users of SharePoint 2010 products can search full text contents of Documentum repository. These capabilities are based on the indexing connector's ability to natively access the appropriate file content, metadata and security implementation of the EMC Documentum system.

Files

Status: Deleted This download is no longer available on microsoft.com. The downloads below are archives provided by the Internet Archive Wayback Machine from the Microsoft Download Center prior to August 2020.

File	SHA1 Hash	Size
DCTMIndexConn.exe	353800fbb72c9f2ac08389cd21277e4e03163772	927 KB

• • Windows Server 2008 Service Pack 2, Windows Server 2008 R2
  • This indexing connector for Documentum works with the following SharePoint 2010 products:
    
    • Microsoft Search Server 2010, Microsoft Search Server 2010 Express, Microsoft SharePoint Server 2010, Microsoft SharePoint Server 2010 for Internet Sites Standard, Microsoft SharePoint Server 2010 for Internet Sites Enterprise, Microsoft FAST Search Server 2010 for SharePoint, and Microsoft FAST Search Server 2010 for SharePoint Internet Sites
  • The following Documentum components are also required to setup the indexing connector for Documentum:
    
    • Documentum Foundation Services (DFS) Server v6.5 SP2 patched with DFS hotfix1049. You can ask for this hotfix from EMC customer support site http://powerlink.emc.com
    • Documentum Content Server. The supported versions of Content Server are determined by DFS v6.5 SP2. Detail list could be found in section "Backward compatibility for Content Server" of DFS v6.5 SP2 release notes, which you can download from EMC customer support site http://powerlink.emc.com

• A comprehensive guide is available on TechNet to provide detail instructions of installation and configuration of the indexing connector for Documentum. Below is a short version describing the steps:
  
  1. GAC the following 4 DFS Productivity Layer .Net assemblies on each SharePoint indexer machine. You can find them from the DFS1049 hotfix, under \emc-dfs-sdk-6.5\emc-dfs-sdk-6.5\lib\dotnet. Note that the dll version must be 6.5.0.231.
     • Emc.Documentum.FS.DataModel.Core.dll
     • Emc.Documentum.FS.DataModel.Shared.dll
     • Emc.Documentum.FS.runtime.dll
     • Emc.Documentum.FS.Services.Core.dll
     
     
  2. On each SharePoint indexer machine, edit the configuration file %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config. Add the following XML under the "configuration" element
     
     • <system.serviceModel>
       <bindings>
       <basicHttpBinding>
       <binding name="DfsAgentService" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="10000000" maxBufferPoolSize="10000000" maxReceivedMessageSize="10000000" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true">
       <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
       <security mode="None">
       <transport clientCredentialType="None" proxyCredentialType="None" realm="" />
       <message clientCredentialType="UserName" algorithmSuite="Default" />
       </security>
       </binding>
       
       <binding name="DfsContextRegistryService" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="10000000" maxBufferPoolSize="10000000" maxReceivedMessageSize="10000000" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true">
       <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
       <security mode="None">
       <transport clientCredentialType="None" proxyCredentialType="None" realm="" />
       <message clientCredentialType="UserName" algorithmSuite="Default" />
       </security>
       </binding>
       
       <binding name="DfsDefaultService" closeTimeout="00:01:00" openTimeout="00:10:00" receiveTimeout="00:20:00" sendTimeout="00:10:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="10000000" maxBufferPoolSize="10000000" maxReceivedMessageSize="30000000" messageEncoding="Text" textEncoding="utf-8" transferMode="StreamedResponse" useDefaultWebProxy="true">
       <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="1048576" maxNameTableCharCount="16384"/>
       <security mode="None">
       <transport clientCredentialType="None" proxyCredentialType="None" realm=""/>
       <message clientCredentialType="UserName" algorithmSuite="Default"/>
       </security>
       </binding>
       </basicHttpBinding>
       </bindings>
       </system.serviceModel>
       
  3. On each SharePoint indexer box, run DCTMIndexConn.exe to deploy the indexing connector for Documentum.
  4. Use the New-SPEnterpriseSearchCrawlCustomConnector PowerShell cmdlet to register the indexing connector for Documentum
     
     • To register the indexing connector with a single SSA, use this sample:
       • New-SPEnterpriseSearchCrawlCustomConnector -SearchApplication 'name of your SSA' -Protocol 'dctm' -ModelFilePath 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\SearchConnectors\Documentum\MODEL.xml' -Name 'Microsoft SharePoint 2010 Indexing Connector for Documentum'
     • To register the indexing connector with all SSA’s on the farm, use this sample:
       • Get-SPEnterpriseSearchServiceApplication | New-SPEnterpriseSearchCrawlCustomConnector -Protocol 'dctm' -ModelFilePath 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\SearchConnectors\Documentum\MODEL.xml' -Name 'Microsoft SharePoint 2010 Indexing Connector for Documentum'
  5. Set configuration details using the Set-SPEnterpriseSearchDCTMConnectorConfig PowerShell cmdlet on each SharePoint indexer machine.
     • See 'Get-help Set-SPEnterpriseSearchDCTMConnectorConfig –full' for documentation on configuration
     • Use this sample for configuration when User Mapping Table is used. See more information about User Mapping Table at step 9
       • Set-SPEnterpriseSearchDCTMConnectorConfig -ACLTranslation "UserMappingTable" -UnmappedAccount "DiscardACE" -UserMappingTableSQLServer "YourDatabaseServerName" -UserMappingTableSQLInstance "YourDatabaseInstanceName" -UserMappingTableDBName "YourMappingDatabaseName" -UserMappingTableName "YourMappingTableName" -DFSURL "RepositoryName1\http://MACHINENAME1:PORT1/services\\RepositoryName2\http://MACHINENAME2:PORT2/services\http://MACHINENAME3:PORT3/services" -DisplayURLPatternForDocument "http://MACHINENAME4:PORT4/webtop/component/drl?objectId={ObjectId}&format={Format}&RepositoryName={RepositoryName}" -DisplayURLPatternForContainer"http://MACHINENAME5:PORT5/webtop/component/drl?objectId={ObjectId}&RepositoryName={RepositoryName}"
  6. After setting configuration details, restart the SharePoint Search Service on each SharePoint indexer machine.
  7. Create a Content Source on the SSA you registered the indexing connector with in step 4
     
     • The start address format is dctm://[clientapphostname]/[repository name]/[cabinet name]/[folder name]
     • [clientapphostname] is the host name of your Documentum client application such as Webtop or DA.
     • Note, [repository name], [cabinet name], [folder name] are case sensitive.
  8. You must create a Crawl Rule on the same SSA
     • The URL pattern for a Crawl Rule is the same as the start address format. You can use "dctm://*" to apply the rule to all Documentum content.
     • Under "Path", make sure "Match case" is checked.
     • Under "Crawl Configuration", choose "Include all items in this path" and "Crawl complex URLs (URLs that contain a question mark - ?)"
     • For "Specify Authentication", choose "Specify a different content access account" and enter a Documentum account which has read permission to all the objects you want to crawl. Make sure "Do not allow Basic Authentication" is unchecked
  9. Create User Mapping Table – If your Documentum Server uses Active Directory for user management, or you don't want security trimming on search results, skip this step and next step.
     • A User Mapping Table is a SQL Server table that contains pairs of accounts: a Documentum user/group account, and the NT Auth account that it maps to.
     • The User Mapping Table consists 4 columns
       • DCTMCredentialDomain: domain name of a Documentum account. Fill this column when the account comes from local machine or an LDAP system, otherwise leave it as an empty string ''.
       • DCTMCredentialRepository: repository name of a Documentum account. Fill this column when the account comes from a Documentum repository, otherwise leave it as an empty string ''.
       • DCTMCredentialLoginName: login name of a Documentum account.
       • NTCredential: the NT Auth account that will search Documentum contents in SharePoint, with format of "domain\account".
     • Use this SQL script to create the table
       • CREATE TABLE <replace with your user mapping table name>
         (
         DCTMCredentialDomain nvarchar (255) NOT NULL ,
         DCTMCredentialRepository nvarchar (32) NOT NULL ,
         DCTMCredentialLoginName nvarchar (80) NOT NULL ,
         NTCredential nvarchar (255) NOT NULL ,
         CONSTRAINT PK_CredentialMapping PRIMARY KEY CLUSTERED
         ( DCTMCredentialDomain, DCTMCredentialRepository, DCTMCredentialLoginName )
         )
         
     • The SharePoint Search Service account must have read permission on this table.
  10. Populate User Mapping Table – You must populate the mapping table with Documentum/NT Auth pairs.
  11. The Documentum Content Source is now ready to be crawled.