Configuration settings for the Email Connector for Lotus Domino
You can adapt settings for problem determination, retry, and logging as well as the credentials that are used for connecting to the Lotus Domino server. You can also determine the Names and Address Books that are used for address book lookups.
General settings
- Maximum number of mailboxes to be processed in parallel
- This number determines the number of threads that are used to
process mailboxes in parallel. When a collector is started, it resolves
the source, such as the group or SMTP address, into a list of mailboxes.
For each mailbox, a request to crawl the mailbox is added to a single
job queue on which the specified number of crawler threads work. The
number of crawler threads is independent of the number of collectors.
Any number of collectors can add entries to this job queue.
The number of mailboxes processed in parallel has an impact on performance, not the number of collectors running in parallel. The greater the number of mailboxes processed in parallel, the higher is the stress on the mail system.
- Number of log file copies to keep for problem determination
- If a problem occurs with the connector processes, the connector copies its log files to a separate subdirectory of the log file directory for later analysis. The crash directory is a subdirectory of the support directory and contains as many subdirectories for failures as you define here. The name of the subdirectory for the failure information is the timestamp when the failure occurred, for example, <icclog>\support\crash\<timestamp>, where <icclog> is the path to the log file location. The Content Collector default path is C:\Program Files\IBM\ContentCollector\ctms\log on a 32-bit operating system and C:\Program Files (x86)\IBM\ContentCollector\ctms\log on a 64-bit operating system.
- Retry interval
- This is the time interval after which documents for which processing
failed are processed again. However, documents with a permanent problem
are not processed again.
The retry interval should not be smaller than the schedule interval of active task routes. For example, if the task route is configured to run every hour and the retry interval is even shorter, the maximum number of retries for an erroneous document might be reached before temporary error conditions can be detected.
Also consider the maintenance intervals of source and target servers, when you set the retry interval.
- Maximum number of processing attempts
- This setting defines how often a collector attempts to process
documents again when the processing failed before. Limit the number
of processing attempts so that an erroneous document is not processed
over and over again. You can find details about the erroneous document
under .
The maximum number should not be lower than two, so that temporary errors do not prevent blacklisted documents from being successfully reprocessed.
- Enable stubbing functions for CommonStore documents
- Select this option to enable the stubbing functions for documents that were archived with IBM® CommonStore. Configure stubbing for CommonStore documents in the stubbing collector.
- Log settings
- Define the level of detail for logging events and the location
where the log files are stored.
With the Truncate log files option, you configure multiple log files. Also specify the maximum number of log files to be created and the maximum size that a log file is allowed to reach. There is a dependency between the number of log files and the size that each log file can have. As soon as the first log file reaches this size level, a new log file is created. When the maximum number of log files has been reached, and all log files have also reached their maximum size, the oldest log file is overwritten with a new one. This is also known as the round-robin method. If you do not select to configure multiple log files, a single log file of unlimited size is written.
- Working directory
- Specify the full path to the directory in which you want to save
temporary files. These files are created by collectors and provide
the basis for further processing steps in a task route. The path must
contain no other characters than a-z, A-Z, and 0-9 of the Latin-1
character set. Important: The working directory must be a local directory on a separate and fast disk and not on a shared network drive. If you use a shared network directory as working directory, this will decrease performance significantly.
Connection settings
You must provide certain credentials so that IBM Content Collector can connect to an email server. To connect to Lotus Domino, specify the location of a valid notes.ini file and a password.The default directory in which the notes.ini file is created by the initial configuration is <INSTALL_DIR>\notesdata\. The notes.ini file must contain the name of a Lotus Domino server that hosts the public names and address book that Content Collector uses to resolve addresses, and mailbox and journal names.
- The rights to sign or run unrestricted methods and operations.
- The rights to sign or run restricted LotusScript/Java agents.
- The user needs to be editor with remove document access at least.
The password that you specify must belong to the ID file which is referred to in the notes.ini file.
You can have Content Collector validate the settings to ensure that you entered the correct credentials.
Address settings
- The public names and address book (names.nsf) on the Lotus Domino server that is specified as Lotus Domino server in the notes.ini file that Content Collector uses. This address book is also known as Domino Directory or Public NAB.
- One or more user-defined address books (Lotus Notes databases). When you add such an address book, you must specify the Lotus Domino server where the database resides unless the server is on a local machine. In this case, leave the server field blank. You must also specify a database that inherits its design from the pubnames.ntf template, which means, that its design is based on the public Names & Address Book (NAB), for example, dir1\companyNAB.nsf.