Configuring the cluster nodes

You must configure all nodes of the IBM® Content Collector cluster in the same way.

Complete these steps to configure the cluster nodes:

1. If a node is configured to write log files, temporary files, working directories, or audit logs to any location other than the default folders, ensure that these folders exist under the same path on all nodes.
2. If you use Lotus® Domino® as a source system, copy your Lotus Notes® ID file and notes.ini file from the subdirectory notesdata where IBM Content Collector is installed on the first node to the same location on all nodes.

   The Email Connector searches this location for the Lotus Notes ID and notes.ini files.

3. To check whether access to the configuration store is possible, run the Configuration Manager. A connection to the configuration store is successfully established if the Configuration Manager loads without error messages and displays the same configuration data on all nodes.
4. Ensure that theIBM Content Collector Task Routing Engine service runs under the same user account on all nodes. By default, this is the account AFUTaskRouteSvc. If you configured the IBM Content Collector Task Routing Engine service to run under a different user account as described in the topic about changing the user account of a service, change the account on all nodes.

   If you use the File System Source or SharePoint connectors, you must ensure that the users of the File System Source or SharePoint services, respectively, have Read/Write access to the document content file, which for SharePoint is the connector's temporary file location. You must also ensure that users of the IBM Content Collector FileNet® P8 Connector service, IBM Content Collector Content Manager Connector service, and IBM Content Collector Utility Connector service (if you use them) have Read access to the document content file.

   If you use Microsoft Exchange as the source system, you can use the same account as for the IBM Content Collector Email Connector service.
5. In the Configuration Manager, click Tools > Task Route Service Configuration and enable configuration synchronization: In the Configuration synchronization interval field, specify a value, in seconds, greater than zero. The default value is 300 seconds.
   The Task Routing Engine of each node connects to the configuration store at given intervals to submit and check for configuration updates. If a node does not connect to the configuration store in the given interval, the Task Routing Engine considers the node failed and distributes work to different nodes.
6. If you run the IBM Content Collector Web Application in scale-out mode in a high-availability cluster, and for performance reporting in a high-availability cluster, you must enable access to the configuration store for the embedded web application server as described in the topic about reconfiguring the web application server.
7. Change the startup type of the IBM Content Collector Web Application service to automatic on all nodes to ensure that the web applications and the report data gatherers are started automatically. You should configure a load balancer to ensure high availability of the web applications.