Download the Collection Requirements document in PDF format here
What You Need First
Follow the instructions below to configure your environment for data collection. These instructions include client and server access and configuration, database access settings, and log options.
DNA® Data Collector Database
Store this database in the data directory of the Notes client workstation you will use to perform data collection. Please do not place this database on your server, as this will slow down the collection process significantly.
Lotus Notes Client Release
The DNA data collector requires an R6.x IBM Lotus Notes client or higher.
Domino Server Release
DNA collects data from IBM Lotus Domino Server English Release 4.x, 5.x, 6.x, 7.x and 8.x servers.
Notes User ID
DNA data collector requires a User ID file that can access all Domino servers in the network with minimum reader access to the log database and the Domino Directory. If pass-thru connections are required, the User ID used for the DNA data collection must have pass thru-access and pass thru-route rights on the systems involved.
If the User ID provided for data collection also has Reader access to the StatRep and Catalog databases, additional reports are possible. Trust Factory recommends that the customer use an ID with Reader access to StatRep.NSF.
DNA requires access to all Domino servers that are to be analyzed. This means that either directly, or via pass thru or dial-up, the Notes client running DNA data collector should be able to connect to all the Domino servers. You can achieve this by creating a local address book with Server, Connection, and Pass Thru documents for all servers.
If Connection documents are required to connect to the servers, the customer will provide a personal address book that contains the necessary Connection documents.
During the DNA Collection Tests, server access is verified for all servers. Should one or more servers not be accessible, the tool will report this. In the event that not all Domino servers can be accessed from one single client machine, both customer and Trust Factory will plan for alternative data collection plans.
During actual data collection, it may happen that connections towards remote servers are unstable. In these circumstances, the collection process can be re-tuned in order to overcome that instability. In practice, this usually means reducing the number of data collection threads towards a server.
DNA needs minimum reader access to the Domino Directory and other directories. The customer should provide Trust Factory with details about these directories.
The data collector will try to identify and collect configuration information about Directory Catalog and Directory Assistance databases configured on the first page of Server documents. This will help identify additional address books during the collection test.
Please note that with DNA the collection is a minimum of 7 days of data. This means that in the event some settings need to be modified, the data collection will be picked up at least 7 days after the change.
User and Server Locations
If DNA is to produce network bandwidth requirements for each office location, the customer should provide information on how to map each user to their office location. This can be achieved in the following ways:
- The hierarchical username reveals the location: Ninke Westra/TheHague/DNA.
- The location field in the Person document reflects the user’s office location.
- The user’s home server location defines the office location for all users.
- The customer provides a spreadsheet or text file (for example obtained from the HR department or an export from Active Directory/LDAP).
DNA consultants will process the mapping and verify the outcome with the customer. Please contact your DNA contact if assistance is required.
DNA needs minimum reader access to the Domino Log file (Log.NSF) on each server.
For DNA to be able to collect relevant information, the log settings on the server should allow the server to generate sufficient log information. Below is an overview of Notes.INI settings that DNA requires.
Default = 20
DNA requires this to be 30 (or change the log level to “informational” in the server’s Configuration document).
Default = LOG.NSF,1,0,7,8000.
The 4th parameter sets the number of days worth of data the log contains and thus determines the DNA reporting period. DNA requires this to be at least seven days.
The last parameter determines the maximum size of a log document.
To allow DNA to collect data on database activity, the Statlog task should be scheduled to run (daily) on the server(s) in scope during the collection period. This can be done by adding statlog to a ServerTasksAtx= entry in each server’s Notes.INI (by default it’s listed on the ServerTasksAt1 line), or by creating a Program document for the servers in the Domino Directory.
If any settings do not comply with the above requirements, the information influenced by those settings will not be collected. Trust Factory does not perform a specific check for these settings during data collection.
By default this parameter isn’t set (0).
For DNA this setting should be either 0 or not defined, to allow activity logging of all databases (instead of just the ones that have activity logging enabled in the database properties).
By default this parameter isn’t set (0).
For DNA this setting needs to be either absent or set to 0 to allow logging of user sessions.
By default not set (0).
This is an optional Notes.INI setting that can be either 0 or 1. However, Trust Factory recommends that customers have the same setting across all servers that are in scope.
In the default situation (or when Replicator_Log_Nonevents = 0), no replication activity data is recorded for replication sessions that don’t result in document updates. When set to 1, replication activity data will contain information about replication sessions to databases that did not result in updates (null-replication sessions).
By default this parameter is not set in the Notes.INI (0).
DNA requires this parameter to be absent or 0 to ensure mail logging to Mail Routing Events instead of Miscellaneous Events.
For DNA to be able to report about full text indexes, the User ID used during the data collection requires at least Reader access to the Catalog.NSF on the servers in scope, and the Catalog task needs to be scheduled to run daily during the collection period. By default this is done through a ServerTasksAtx= line (where x represents the hour at which the task(s) will be started). The catalog task can also be scheduled through a Program document in the Domino Directory.
The Notes User ID used for the data collection needs to have at least reader access to the Statistics Reports (Monitoring Results) database (Statrep.NSF) for the DNA collection process.
Statistics collection can be configured through the Domino Monitoring Configuration database (events4.NSF) database. DNA requires that statistics are recorded every 60 minutes and that the servers in scope run the Collect task to enable recording of platform statistics. The Collect task can be loaded at startup by adding it to the ServerTasks= line in the Notes.INI, or by creating a Program document for each server in the Domino Directory.
The following Notes.INI settings must be verified on the servers in scope:
By default this parameter is not set (0).
To enable statistics-based reporting, DNA requires this parameter to be not present or set to 0.
By default not present (0).
For statistics-based reports, DNA requires platform statistics to be enabled (set to 1).
Server time synchronization
In order to be able to relate log events across different servers, all servers in scope should keep their system time synchronized.
Also, it is important to verify that the time zone settings on all servers are correctly reflecting the location of the server. Incorrect time zone settings on Domino servers will cause incorrect logging of timestamps for mail routing. This impacts the accuracy of DNA analysis in the area of mail routing.
DNA collects a large amount of information from Domino servers. During data collection, DNA needs to gather all documents available in the log files on the servers. Depending on the size and setup of the network, the number of log documents can be several hundreds of thousands of documents.
The performance of the DNA collection process is dependant on a wide variety of factors. DNA is designed to overcome many of these issues:
- The DNA Collector executable is designed as a rapid, non-intrusive tool that does not require view-indexes to be (re-) built on the Log (Log.NSF) and Domino Directory (Names.NSF).
- DNA can fire a large number of threads towards a server in order to reduce delays resulting from slow network connections.
- DNA structures and compresses (1:100) log data before it stores it locally.
An overview of available bandwidth between the DNA collection site and remote server locations is recommended to help optimize the data collection process.
Executing the Data Collection
We recommend that the data collection be executed with the help of a Trust Factory consultant. Your consultant will ask you to share your screen using Sametime Unyte or another screen sharing utility of your choice. This allows the consultant to walk you through all the steps of data collection.
The consultant will also advise you how to adjust the tuning parameters during data collection, to optimize the performance of the collection process.
After Completing the Data Collection
The DNA collector database should now be populated with many documents that contain the collected statistics and configuration data.
You now need to submit this database to Trust Factory. There are two ways to make this happen:
- Burn the collector database on a CDROM and send it to Trust Factory by postal mail;
- Use an FTP client to upload the collector database to Trust Factory’s FTP server;