Domino Groups (8.5.3 - 11.0.1) Options

The Domino Groups (8.5.3 - 11.0.1) seed, which is required to crawl groups and support groups collection security on Domino server versions between 8.5.3 and 11.x, includes the following general configuration options:
  • Domino Server Hostname - The Domino server name that hosts the Domino connector server component, for example, domino.example.com
  • Username - The username of the user whose credentials will be used for the crawl
  • Password - The crawl user's password
  • Target Domino Server - The Domino server that hosts the database (by default names.nsf) with the groups information
    Note: The Target Domino Server setting identified in this field must contain the names.nsf database. If this database is not present on the server entered here, the groups crawl will fail
  • Groups Database - The database that stores the groups information and its members
  • Groups View - The name of the database view that shows all the existing groups
  • Group Item Name - The name of the item that holds the group name
  • Members Item Name - The name of the item that holds the list of members for a given group
  • Seed ID - When adding multiple Domino seeds to the same collection, enter a Seed ID that uniquely identifies each seed. For example: 1, 2, 3. This will prevent the URLs from each seed to collide with each other
SSL - This section provides the following configurable options:
  • SSL Enabled - The connector will use SSL encryption when connecting to the server component. If enabled then you can either:
    • Add the server certificate to the default KeyStore that is part of the JRE used by Watson™ Explorer Engine
    • Set in the next field the SHA-1 hash of the Domino server's SSL certificate for servers that use self-signed certificates
  • SSL SHA-1 Fingerprint - The SHA-1 hash of the Domino server's SSL certificate. This option is provided for servers that use self-signed certificates. When using this option, the server certificate will not be checked for expiration or revocation, only that it matches this fingerprint.

    A more secure approach to handling certificates is to add the server certificate to the default KeyStore that is part of the JRE used by Watson Explorer Engine. Example: a7:7e:cb:7c:7b:e0:97:4b:ad:7b:d9:50:89:74:b9:61:23:4e:83:1d

Dual Mode Refresh - This section provides the following configurable options:
  • Since Date - All groups created or modified since the given date will be crawled
  • Refresh Mode - The type of refresh modes include the following:
    • Full: A full refresh will be performed every time a refresh is started
    • Incremental: An incremental refresh will be performed every time a refresh is started SeeDual Mode Refresh Options for more information
    • Incremental+Full (Recommended): An incremental refresh will be performed every time a refresh is started unless the time when the refresh starts falls on one of the selected Full Scan Days and between the Full Scan Start and Full Scan End times. In the latter case, a Full refresh will be performed.
  • Full Scan Start Time - When the collection refreshes it will only do a full scan (for deleted groups) when running after this time (and on certain days, if selected)
  • Full Scan End Time - When the collection refreshes it will only do a full scan when running before this time (and on certain days, if selected)
  • Full Scan Days - When the collection refreshes it will only do a full scan when running on these days of the week (and in the time interval if specified)
  • Clock Sync Offset - Number of seconds to be subtracted from the last crawled date to account for possible discrepancies between the clocks of the Domino and Watson Explorer Engine servers (For example, if the Domino server's clock is behind the Watson Explorer Engine clock). This is used during Incremental refresh only
Advanced Logging - This section provides the following configurable options:
  • Enable Connector Bootstrap Logging - When enabled, the connector will generate detailed startup trace logging. Enabling this option will have a negative impact on performance
  • Connector Logging Configuration - Log4j configuration for the connector. Default configuration enables ERROR level logging. The token %LOGDIR% is replaced with the full path to the Watson Explorer Engine temp directory
  • Maximum Java Heap Size - The maximum size of the Java heap. Specify the heap size using the same format when using the -Xmx argument to the java command (512m for 512 megabytes, 2g for two gigabytes, etc). Values less than 160m are ignored