Fine-tune performance settings

You can edit configuration files to fine-tune performance settings. The Connector Services web.config file is a UTF-8 encoded file. When you edit the file, you must save it as UTF-8 to preserve the encoding.

Connector Services web.config file

The Connector Services allows you to customize your configuration using the web.config file. This file is used for optimizing the tasks you need to perform. The web.config file is a configuration file for a web site and is located in the rootConnector Services install location at <SharePoint_install_drive>\Inetpub\wwwroot\wss\VirtualDirectories\.

The following table lists some of the keys you can customize.

Key Definition
executionTimeout <httpRuntime executionTimeout="10800" maxRequestLength="2097151" />

Use this ASP.NET key to specify the maximum http timeout (in seconds) for the IBM FileNet Remote Connector Web Service. This value is configured during installation. This key is located in the system.web section of the web.config file.

maxRequestLength <httpRuntime executionTimeout="10800" maxRequestLength="2097151" />

Use this ASP.NET key to specify the maximum http request length (in kilobytes) for the IBM FileNet Remote Connector Web Service. This value is configured during installation. This key is located in the system.web section of the web.config file.

MaxRetries

<add key="MaxRetries" value="6" />

Use this key to determine the maximum number of retries when an error occurs. This entry indicates the number of retries, not total tries. For example, if the value is 6, a failed post-processing task can be tried up to a maximum of 7 (6+1) times.

The value must be a positive integer including zero, where zero means no retry. The internal default is "6" and is used if this entry is missing or invalid.

QueryPageSize

<add key="QueryPageSize" value="800" />

Use this key to determine the page size used for document crawling queries issued by the collector. This entry controls the maximum number of documents that are batched and returned per page display. Individual versions do not count as separate documents. For example, if the value is 800 and each document has three versions, a maximum of 2400 (800 * 3) document versions are returned.

The value must be a positive integer including zero, where zero means SharePoint default view's row limit is 100 if it is not explicitly modified. The internal default is 800, which is used if this entry is missing or invalid.

RetryWaitTime

<add key="RetryWaitTime" value="0, 100, 200, 300, 500, 800" />

Use this key to determine the wait time for each item that is requested in milliseconds. Each column corresponds to the current retry count. For example, if the value is 0, 100, 200, 300, 500, 800, the first retry waits 0 ms, the second retry waits 100 ms, and the third retry waits 200 ms. When the number of columns is less than the current retry count, the last retry wait time is reused. When the number of columns is more than the current retry count, the extra columns are ignored.

The values must be positive integers including zero, where zero means the retry takes place immediately after yielding to another thread with the same priority. The internal default is 0, which is used if this entry is missing or invalid.

Links

When you define your task route, you can specify a post-processing task that moves a SharePoint document to an object store, and then creates a link. The web.config file is used to assign the links to the correct Content Engine server where the corresponding documents are archived. This mapping allows you to change the Content Engine server name without breaking the existing links in SharePoint because the individual links reference only the object store and document version information.

Key Definition
CEMapping

<add key="CEMapping1" value="objectstore=<objectstorename>;
url=http://<CEServerName>:<Port>/wsi/FNCEWS40MTOM/" />

Use this key to assign links created in SharePoint to a specific Content Engine server in the FileNetConfig section of the web.config file. You must manually add a CEMapping<n> key to the FileNetConfig section for the CE server referenced by that link. The mappings used must be contiguous and must start at 1. For example, if you include CEMapping1, CEMapping2, CEMapping3 and CEMapping5, only the first three are used because the absence of CEMapping4 in the sequence signals the end of the list to the Redirector’s config reader.

This key allows you to map a physical server to the location of a specific object store. An administrator can then simultaneously re-map thousands of links to a different Content Engine server with a single line change in the web.config file.

NOTE  You must use this key to enable links. When you change a mapping to point to a different server, the name of the object store must remain the same because it is stored in the link.