Configure TCS support for the Documentum connector (FAST Search Server 2010 for SharePoint)

Applies To: FAST Search 2010

Applies to: FAST Search Server 2010

This article describes how to install and configure the Microsoft SharePoint 2010 Indexing Connector for Documentum to support EMC Documentum Trusted Content Services (TCS).

System prerequisites and requirements

• Supported operating systems are either Windows Server 2008 R2 or Windows Server 2008 Service Pack 2.

• An installed and configured installation of FAST Search Server 2010 for SharePoint with the February 2012 Cumulative Update.

• An installed and configured installation of SharePoint Server 2010 with the December 2010 Cumulative Update.

• A FAST Search Content Search Service Application.

• Documentum Foundation Services (DFS) Server v6.5 SP2 patched with DFS hotfix 1049. You can ask for this hotfix from EMC customer support site http://powerlink.emc.com. This server must be configured and connected to all repositories.

• DFS Productivity Layer v6.5 with SP2 and DFS hotfix 1049 .NET assemblies.

• Documentum Content Server. The supported versions of Documentum Content Server are determined by DFS v6.5 SP2. You can find a detailed list in the DFS v6.5 SP2 release notes in the section "Backward compatibility for Content Server". You can download the release notes from the EMC customer support site http://powerlink.emc.com.

• Documentum Trusted Content Services (TCS) is required if you have to support full EMC Documentum repository security. TCS is not required to enable automatic mapping between Windows Active Directory users and Documentum users.

• A Windows Server 2008 Active Directory Lightweight Directory Services (AD LDS) instance.

Quick overview

1. Before you begin:

   1. Ensure that your system meets the System prerequisites and requirements.

   2. Download the Indexing Connector for Documentum from the Microsoft Download Center.

   3. Determine which Documentum content access account to use for crawling.

   4. On each SharePoint 2010 crawl server:

      1. Set the DFS Productivity Layer .NET assemblies.

      2. Edit the machine.config file to set the Documentum bindings.

2. Install and configure the Indexing Connector for Documentum.

   1. Deploy the Indexing Connector for Documentum on each SharePoint 2010 crawl server in the farm.

   2. Register the Indexing Connector for Documentum to the FAST Search Content SSA using Windows PowerShell.

   3. Configure the Indexing Connector for Documentum on each SharePoint 2010 crawl server in the farm using the Indexing Connector for Documentum PowerShell commandlet.

3. Set up AD LDS, run the custom security trimming script and configure the FAST Search Server for SharePoint Security Sync Service. This enables automatic user mapping and support for TCS.

   1. Stop IIS for the FASTSearchAdminAppPool on the FAST Search Server 2010 for SharePoint administration server.

   2. Install the AD LDS server role, create an AD LDS instance and create a partition for it.

   3. Set DFS Productivity Layer .NET assemblies for FAST Search Server 2010 for SharePoint in the bin directory of the installation directory.

   4. Enable custom security trimming with a Windows PowerShell script and provide the location of the AD LDS on all FAST Search Server 2010 for SharePoint servers in the farm.

   5. Restart IIS, if you have stopped it.

   6. Configure the FAST Search Server for SharePoint Security Sync Service.

   7. Verify the keys and the description field in the AD LDS partition.

4. Configure a Documentum content source in the FAST Search Content SSA in the SharePoint 2010 Central Administration.

   1. Create a crawl rule for the Indexing Connector for Documentum.

   2. Create a content source for the Indexing Connector for Documentum.

Prepare the SharePoint 2010 crawl server(s).

Determine which Documentum content access account to use

1. Determine which Documentum content access account you will use for crawling. You have to specify this account and the password later in the configuration procedure when you set up crawl rules. The Indexing Connector for Documentum uses a Documentum content access account to retrieve content from the Documentum repository. This account must have the following credentials:

   • At least read permission to documents that you want to crawl.

   • At least browse permission to cabinets, folders, and records (documents with only metadata) that you want to crawl.

Set DFS Productivity Layer .NET assemblies

1. Locate and verify the version number of the following four DFS Productivity Layer .NET assemblies that are included in DFS hotfix 1049. When extracted to the default path, these files are located in the directory %local%\emc-dfs-sdk-6.5\emc-dfs-sdk-6.5\lib\dotnet:

   • Emc.Documentum.FS.DataModel.Core.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.DataModel.Shared.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.runtime.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.Services.Core.dll (version number 6.5.0.231)

2. On each SharePoint 2010 crawl server, log on with an account that has Administrator rights to the server and deploy the DFS Productivity Layer .NET assemblies to the global assembly cache %windir%\assembly.

   Note

   You can drag and drop the four DLLs into the global assembly cache (%windir%\assembly) to deploy them, but you might have to turn off User Account Control to do this.

The next step is to edit the machine.config file on each SharePoint Server 2010 crawl server to include WCF settings for the DFS Productivity Layer. This is done to make sure that the DFS Productivity Layer .NET assemblies function correctly.

The WCF settings you are about to set allow a maximum of 30 megabytes (MB) per Documentum content object (the document file plus its metadata) transferred. The administrator can increase "maxReceivedMessageSize" in "DfsDefaultService" binding for larger content. However, the SharePoint Server 2010 crawler will handle files with a maximum size of 64 MB. To crawl files larger than 64 MB, follow step 4b.

Edit the machine.config file

1. Go to %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG, open the machine.config file, and then add the following XML snippet into 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>
   

2. To crawl files larger than 64 MB, you have to get the FAST Search Content Search Service Application and store it in a variable, retrieve the current value of "MaxDownloadSize" and modify it to the size that you want to crawl.  

   1. Run this procedure on the crawl server.

   2. On the Start menu, click All Programs.

   3. Click Microsoft SharePoint 2010 Products.

   4. Right-click SharePoint 2010 Management shell and select Run as administrator.

   5. At the Windows PowerShell command prompt, type the following command(s):

      $ssa = Get-SPEnterpriseSearchServiceApplication -Identity <FAST Search Content Search Service Application>
      $ssa.GetProperty("MaxDownloadSize") 
      $ssa.SetProperty("MaxDownloadSize", <File size larger than 64>)
      $ssa.Update()
      

      Where:

      • <File size larger than 64> is the maximum file size (in MB) that you want to allow the Indexing Connector for Documentum to crawl.

      • <FAST Search Content Search Service Application> is the name of your FAST Search Content Search Service Application.

Install and configure the Indexing Connector for Documentum

Deploy the Indexing Connector for Documentum

1. Download the Indexing Connector for Documentum from the Microsoft Download Center.

2. On each SharePoint Server 2010 server in the farm that is running a crawl component, run the Indexing Connector for Documentum by running the file DCTMIndexConn.exe. Follow the steps that are presented in the installation wizard.

Register the Indexing Connector for Documentum to the FAST Search Content SSA

1. Run this procedure on the SharePoint Server 2010 crawl server to register the connector to the FAST Search Content search service application.

2. On the Start menu, click All Programs.

3. Click Microsoft SharePoint 2010 Products.

4. Right-click SharePoint 2010 Management shell.

5. At the Windows PowerShell command prompt, type the following command(s):

   New-SPEnterpriseSearchCrawlCustomConnector -SearchApplication "<name of your FAST Search Content search service application>" -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"
   

Configure the Indexing Connector for Documentum

1. On each SharePoint Server 2010 crawl server, set the configuration details using the following Windows PowerShell cmdlet: Set-SPEnterpriseSearchDCTMConnectorConfig. All the settings are stored in <system drive>\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\SearchConnectors\Documentum\DCTMConfig.xml. If more than one SharePoint Server 2010 crawl server is used, all settings must be the same on each server.

   Use the following Windows PowerShell commands to display help and examples for the Indexing Connector for Documentum:

   • Get-help Set-SPEnterpriseSearchDCTMConnectorConfig -full shows full help.

   • Get-help Set-SPEnterpriseSearchDCTMConnectorConfig -examples shows only examples.

   The following table describes some of the parameters of the Set-SPEnterpriseSearchDCTMConnectorConfig cmdlet. It is important to set the parameter ACLTranslation to NoSecurity and the parameter PersistDCTMACL to True, as these settings enable automatic user mapping and TCS support.

   Command	Option	Description
   ACLTranslation	NoSecurity	The Indexing Connector for Documentum ignores the Documentum ACL during crawl. For example, all documents from Documentum will be searchable by any SharePoint user. This option enables you to decline enforcement of security trimming or implement custom security trimming.
   DisplayURLPatternForDocument		DisplayURL pattern for documents. Any valid URL with part of the string replaced by placeholders such as {ObjectId}, {RepositoryName} or {Format}. You can find an example below.
   DisplayURLPatternForContainer		DisplayURL pattern for folders and cabinets. Any valid URL with part of the string replaced by placeholders such as {ObjectId}, {RepositoryName} or {Format}. You can find an example below.
   DFSURL		Specify the DFS Web Services URL for each repository that is to be crawled. More than 1 DFS Web Services URL can be specified for each repository. Use the following format: "RepositoryName1\DFSURL1.1\DFSURL1.2\...\DFSURL1.n\\RepositoryName2\DFSURL2.1\DFSURL2.2\...\DFSURL2.n\..."
   PersistDCTMACL	True	Specify whether to store the Documentum ACL in a crawled property. If "PersistDCTMACL" is set to "True", the Indexing Connector for Documentum will store the Documentum ACL information as a crawled property. The default value is "False".

   Example:

   Set-SPEnterpriseSearchDCTMConnectorConfig -ACLTranslation "NoSecurity" -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}"
   

2. After setting the configuration details, restart the OSearch14 service on each SharePoint Server 2010 crawl server.

Set up support for TCS and enable automatic user mapping

Before you set up support for TCS, verify that you have access to the Internet Information Services (IIS) Manager. To install the IIS Manager, follow these steps:

Install the Internet Information Services (IIS) Manager

1. Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

2. Click Start, point to Administrative Tools, and then click Server Manager.

3. Right-click on Server Manager (<server name>) and click Add Features.

4. Expand the Remote Server Administration Tools menu, then expand the Role Administration Tools menu and then click Web Server (IIS) Tools.

5. Click Install and follow the instructions in the Wizard.

Stop IIS for the FASTSearchAdminAppPool

1. Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

2. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

3. In the Connections menu, expand the server menu and click Application Pools.

4. Click FASTSearchAdminAppPool.

5. If the IIS service is running, go to the Actions menu and click Stop.

Install the AD LDS server role, create an AD LDS instance and create a partition for it

1. Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

   You may install the AD LDS server role on a different FAST Search Server 2010 for SharePoint machine in your farm, but the AD LDS server role must be installed on a machine that is close to or contains the QRServer and there may only be one AD LDS instance per farm.

   Install the Active Directory Lightweight Directory Services (AD LDS) role.

   1. Click Start, point to Administrative Tools, and then click Server Manager.

   2. In the console tree, right-click Roles and then click Add Roles.

   3. Review the information on the Before You Begin page of the Add Roles Wizard, and then click Next.

   4. On the Select Server Roles page, in the Roles list, select the Active Directory Lightweight Directory Services check box, and then click Next.

   5. Finish adding the AD LDS server role by following the instructions in the wizard.

2. Create an AD LDS instance and create an AD LDS partition on the instance.

   1. Click Start, point to Administrative Tools, and then click Active Directory Lightweight Directory Services Setup Wizard.

   2. On the Welcome to the Active Directory Lightweight Directory Services Setup Wizard page, click Next.

   3. On the Setup Options page, click A unique instance, and then click Next.

   4. On the Instance Name page, provide a name for the AD LDS instance that you are installing. This name is used on the local computer to uniquely identify the AD LDS instance. For example, type CustomSecurity. Click Next.

   5. On the Ports page, specify the communications ports that the AD LDS instance uses to communicate. AD LDS can communicate by using both LDAP and Secure Sockets Layer (SSL). Therefore, you must provide a value for each port.

      Note

      The default value for the LDAP port is 389 and the default value for the SSL port is 636. If you install AD LDS on a computer where either of the default ports is in use, the Active Directory Lightweight Directory Services Setup Wizard automatically locates the first available port, starting at 50000. For example, Active Directory Domain Services (AD DS) uses ports 389 and 636, as well as ports 3268 and 3269 on global catalog servers. Therefore, if you install AD LDS on a domain controller, the Active Directory Lightweight Directory Services Setup Wizard provides a default value of 50000 for the LDAP port and 50001 for the SSL port.

      Click Next.

   6. On the Application Directory Partition page, create an application directory partition (or naming context) by clicking Yes, create an application directory partition. Then, type a name for the partition. We recommend to name the partition CN=CustomSecurity,DC=FS4SP. The full name of the AD LDS instance or farm follows the pattern LDAP://<FAST Search Server 2010 for SharePoint server host name>:<port number>/<AD LDS partition name>, for example LDAP://contoso.com:52000/CN=CustomSecurity,DC=FS4SP.

   7. On the File Locations page, you can view and change the installation directories for AD LDS data and recovery (log) files. By default, AD LDS data and recovery files are installed in %ProgramFiles%\Microsoft ADAM\instancename\data, where instancename represents the AD LDS instance name that you specified on the Instance Name page. Click Next.

   8. On the Service Account Selection page, make sure that the Network service account is selected. This should be the default selection. The account that you select determines the security context in which the AD LDS instance runs

   9. On the AD LDS Administrators page, select This account. This should be the account of the user who is running FAST Search Server 2010 for SharePoint. Provide the account name of the FAST Search Server 2010 for SharePoint user that runs Windows Services for FAST Search Server 2010 for SharePoint to become the default administrator for the AD LDS instance. The user or group that you select will have full administrative control of the AD LDS instance.

   10. On the Importing LDIF Files page, you can import schema LDAP Data Interchange Format (LDIF) files into the AD LDS instance. Mark the box in front of MS-InetOrgPerson.LDF and click Next.

   11. The Ready to Install page gives you an opportunity to review your installation selections. After you click Next, the Active Directory Lightweight Directory Services Setup Wizard copies files and sets up AD LDS on your computer.

   12. When the Active Directory Lightweight Directory Services Setup Wizard finishes installing AD LDS, it displays this message: “You have successfully completed the Active Directory Lightweight Directory Services Setup Wizard.” When the Completing the Active Directory Lightweight Directory Services Setup Wizard page appears, click Finish to close the wizard.

Set DFS Productivity Layer .NET assemblies for FAST Search Server 2010 for SharePoint

1. Locate and verify the version number of the following four DFS Productivity Layer .NET assemblies that are included in DFS hotfix 1049. When extracted to the default path, these files are located in the directory %local%\emc-dfs-sdk-6.5\emc-dfs-sdk-6.5\lib\dotnet:

   • Emc.Documentum.FS.DataModel.Core.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.DataModel.Shared.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.runtime.dll (version number 6.5.0.231)

   • Emc.Documentum.FS.Services.Core.dll (version number 6.5.0.231)

2. On the FAST Search Server 2010 for SharePoint administration server, deploy the DFS Productivity Layer .NET assemblies to the bin directory of the installation directory.

   Note

   You can drag and drop the four DLLs into the bin directory to deploy them, but you might have to turn off User Account Control to do this.

Enable custom security trimming

1. Run this procedure on each server in the farm that is running FAST Search Server 2010 for SharePoint.

   Note

   You must re-enable custom security trimming by repeating the steps in this procedure after you install a Service Pack (SP) or a Cumulative Update (CU) for FAST Search Server 2010 for SharePoint.

   Verify that you meet the following minimum requirements: You are a member of the FASTSearchAdministrators local group on the computer where FAST Search Server 2010 for SharePoint is installed.

2. Stop the FAST Search for SharePoint service. You can use the nctrl.exe reference command-line tool.

3. On the Start menu, click All Programs.

4. Click Microsoft FAST Search Server 2010 for SharePoint.

5. Right-click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.

   Warning

   If you do not run this script as an administrator, you will not be able to start the FAST Search Server 2010 for SharePoint Security Sync Service.

6. At the Windows PowerShell command prompt, type the following command(s):

   customsecurity.ps1 -action enable
   

7. Accept the default values, except when you are prompted to provide the full name of the AD LDS. Specify the full name of the AD LDS configuration location in the following pattern: LDAP://<FAST Search Server 2010 for SharePoint server host name>:<port number>/CN=Config,<AD LDS partition name>, for example LDAP://contoso.com:52000/CN=Config,CN=CustomSecurity,DC=FS4SP.

8. Optional: You can choose to specify a claim type for the claim that will contain the group memberships from Documentum. To do this, define the claim type in a URI format, for example: http://custom.documentum.local/claims/group.

   Note

   Although the format is a URI, it does not point to an object that can be physically reached.

9. Start the FAST Search for SharePoint service and verify that all of the services are running. You can use the nctrl.exe reference command-line tool.

Restart IIS

1. If you have stopped IIS on the FAST Search Server 2010 for SharePoint administration server, restart it.

2. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

3. In the Connections menu, expand the server menu and click Application Pools.

4. Click FASTSearchAdminAppPool.

5. If the IIS service is stopped, go to the Actions menu and click Start.

Configure the FAST Search Server for SharePoint Security Sync Service

1. Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

2. Go to the bin directory of your FAST Search Server 2010 for SharePoint installation directory and open the Microsoft.SharePoint.Search.Extended.Security.TrimmingSync.exe.config file.

3. Using the same information you provided when you configured the Indexing Connector for Documentum, edit the <Datasource.Documentum> section as follows:

   1. Set the Documentum user and password for the login account. Use the account that you determined to be the Documentum content access account. This should be a user with elevated user permissions on the Documentum Content Server. For more information, see Determine which Documentum content access account to use.

   2. Set the name of the Documentum repository. This can be a repository that has Trusted Content Services (TCS) enabled.

   3. Set the location of the Documentum Foundation Services (DFS) by providing the URI for the DFS.

4. Edit the <Emc.Documentum> section, using the same Documentum bindings you entered when you configured the machine.config file on the SharePoint Server 2010. See Edit the machine.config file.

5. Optional: Modify the syncIntervalMinutes parameter to adjust the synchronization interval. The default value is 60 minutes.

6. Save and close the Microsoft.SharePoint.Search.Extended.Security.TrimmingSync.exe.config file.

Set the log on account for the FAST Search Server for SharePoint Security Sync Service

1. Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

2. Click Start, point to Administrative Tools and click Server Manager.

3. Expand the Configuration menu and select Services.

4. Locate and right-click the FAST Search Server for SharePoint Security Sync service and then click Properties.

5. Click the Log On tab.

6. Select This account and type the account name and the password of the user who is running FAST Search Server 2010 for SharePoint.

7. Optional: On the General tab, change the startup type from Manual to Automatic.

8. Click Apply and then click OK.

Verify the keys and the description field in the AD LDS partition

1. Now that you have run the FAST Search Server for SharePoint Security Sync Service, verify that the following keys and descriptions exist in the AD LDS partition.

2. Using ADSI Edit, or another tool that lets you view and edit the AD LDS partition, verify that the hierarchy looks like the following example. Also, make sure that the “description” field under CN=Setup contains a DataSource value of the CN=Setup (for example: DataSource:CN=Documentum,CN=DataSources,CN=CustomSecurity,DC=FS4SP):

   CN=Config
      CN=Setup
         A "description" field containing a DataSource value of the CN=Setup.
   CN=DataSources
      CN=Documentum
         CN=Config
      CN=GroupMemberships
         A "description" field containing semi-colon separated group membership information.
   

3. If the CN=Config is missing, create a new object of the type "container" named Config.

4. If the CN=Setup under CN=Config is missing, create a new object of the type “controlAccessRight” named Setup.

Optional: Troubleshoot the FAST Search Server for SharePoint Security Sync Service

1. If the FAST Search Server for SharePoint Security Sync Service stops after it has started, investigate the Event Viewer for an event that mentions a host setup failure.

   Run this procedure on the FAST Search Server 2010 for SharePoint administration server.

   1. Open the Server Manager.

   2. On the Start menu, click Administrative Tools.

   3. Click Event Viewer.

   4. Investigate the events and look for host setup failure messages.

2. If you find an event that indicates a host setup failure, open and edit the Microsoft.SharePoint.Search.Extended.Security.TrimmingSync.exe.config file located in the bin directory of your FAST Search Server 2010 for SharePoint installation directory.

   1. Search for 10100. You should retrieve the following line: <add baseAddress="https://localhost:10100/secTrimmingSync" />

   2. Edit the port number 10100 to a port number that the FAST Search Server 2010 for SharePoint Administrator user has access to. For example, you can use port number 13279. This port is opened by default on a FAST Search Server 2010 for SharePoint server.

   3. Save and close the Microsoft.SharePoint.Search.Extended.Security.TrimmingSync.exe.config file.

3. Start the FAST Search Server for SharePoint Security Sync Service.

   1. On the Start menu, click Administrative Tools.

   2. Click Server Manager.

   3. Expand the Configuration menu and select Services.

   4. Locate and right click the FAST Search Server for SharePoint Security Sync service and then click Start.

Configure a Documentum content source in the FAST Search Content SSA in the SharePoint 2010 Central Administration.

Before a crawl, create crawl rules to include or exclude specific content in Documentum. Use the following procedure to create a crawl rule for the Indexing Connector for Documentum.

Run this procedure on the SharePoint Server 2010 server that contains the FAST Search Content search service application.

Create a crawl rule for the Indexing Connector for Documentum

1. Verify that the user account that is performing this procedure is an administrator for the FAST Search Content search service application.

2. Open SharePoint Central Administration, and then click Manage Service Applications.

3. Click the name of your FAST Search Content search service application for which you want to create a crawl rule.

4. Under Crawling, click Crawl Rules.

5. On the Manage Crawl Rules page, click New Crawl Rule.

6. On the Add Crawl Rule page, specify the following information to create at least one crawl rule.

   • In Path box, type the path of the content that you want to crawl.

     You can use wildcard "*" or regular expression syntax. Because Documentum uses case sensitive names for the content, select the Match case check box. Refer to the section Syntax to refer to a Documentum object for examples.

   • In Crawl Configuration section, select Include all items in this path, and then select Crawl complex URLs (URLs that contain a question mark - ?).

   • In the Specify Authentication section, select Specify a different content access account, and then type the Documentum content access account and password in the appropriate boxes. See the procedure Determine which Documentum content access account to use earlier in this article.

   • Make sure that the Do not allow Basic Authentication check box is cleared.

7. Click OK to finish configuration.

   Note

   • You can create multiple crawl rules for Documentum to include or exclude Documentum content.

   • You can use different crawl rules to specify different content access accounts for different Documentum content. For example, you have two repositories and two content access accounts for each repository. The Documentum content access account specified in a crawl rule will only be applied to Documentum content covered by the path in that crawl rule. In that case, you must set up a FAST Search Server for SharePoint Security Sync service for each repository.

Create a content source for the Indexing Connector for Documentum

1. Verify that the user account that is performing this procedure is an administrator for the FAST Search Content search service application.

2. Open SharePoint Central Administration, and then click Manage Service Applications.

3. Click the name of your FAST Search Content search service application in which you want to create a content source.

4. On the Search Administration page, under Crawling, click Content Sources.

5. On the Manage Content Sources page, click New Content Source.

6. On the Add Content Source page, do the following:

   1. In the Name box, type the name of the content source.

   2. In the Content Source Type section, select Custom Repository.

   3. In the Type of Repository section, select the SharePoint 2010 Indexing Connector for Documentum. Mark the radio button in front of the name that you specified for the Indexing Connector for Documentum when you registered it with the FAST Search Content search service application, for example dctm.

   4. In the Start Addresses section, type the start addresses. The start address format is the same as the format used to specify the path. You can type more than one start address for the content source, one per line.

      Refer to the section Syntax to refer to a Documentum object for examples.

   5. In the Crawl Schedules section, select schedules from the Full Crawl and Incremental Crawl drop-down lists, or create schedules for each kind of crawl.

   6. In the Content Source Priority section, assign a priority level to the content source according to your business requirements.

   7. Select Start full crawl of this content source to start a crawl immediately after the content source is created.

   8. Click OK to finish the configuration and accept all configured options.

   The Documentum content source is configured and the system can crawl Documentum content repositories that are specified in the content source.

   SharePoint Server 2010 supports a scalable architecture for performance scale-out. You can deploy more than one crawl server and configure multiple SharePoint Server 2010 crawlers to crawl the EMC Documentum database simultaneously.

Syntax to refer to a Documentum object

The format to refer to a Documentum object that you use for the path (when you set up a crawl rule) and the start address (when you set up a content source) is defined in the following table:

<clientapphostname> is the host name of your Documentum client application such as Webtop or DA. The <clientapphostname> configured here should be same as the same as the one used in content source. <repository name>, <cabinet name>, and <folder name> are case sensitive.