Head in a blender

The Mighty Domino Configuration Collector

Andy Pedisich   February 2 2011 11:36:07 PM
I've decided that documentation on the the Lotus Domino Configuration Collector, which was actually item #6 in my list of future things to post, should be the thing I post first.

As I have mentioned, Rob and I did a session on extracting stats at Lotusphere 2011.  Near the conclusion, we briefly mentioned a nifty IBM Lotus Domino DXL feature we knew of and a free IBM Lotus tool that makes it easier to read.  A bunch of people have asked me to expand on this, so here it is.

Lotus Domino automatically makes copies every time a server document or a server configuration document is created or modified.  This is a document you can use to find out who made the last change to the server configuration and what they did.

First and most important, this is not a new feature. Here's a link to a Knowledgebase article about the collector from 2004-09-12.
What is the 'Configuration Collector' in Domino 6.5 and 6.0.3?
This article from 2001 is also relevant.
DXL roadmap: Understanding Domino's XML language
And here's an extract from the Release 8.5.2 IBM Lotus Domino help database explaining the functionality.

Image:The Mighty Domino Configuration Collector


Improving server performance using the configuration collector

The IBM® Lotus® Domino® configuration collector provides snapshots of how the Domino server is configured. You can use that configuration information to analyze recent changes made to the server's configuration that have impacted server performance.

Domino reads several documents during server initialization. These documents are the Server document, Server Configuration document, All Server Configuration document, and the Group Server Configuration document. Domino also checks the views of these documents for changes every five minutes. If modifications have been made, Domino reads and saves the modified documents. When Domino reads a document, a filename is constructed based on the document's modification time and date and the server name.  There is a default prefix assigned to each of the server and configuration documents:

  • Server document -- serverdoc
  • Configuration Settings (Specific Server) document -- configspecific
  • Configuration Settings (All Servers) document -- configall
  • Configuration Settings (Server Group) document -- configgroup
For example, if a Server document is modified on August 2, 2004, at 4:05 PM, on a server named Sales, the file name assigned to the document is serverdoc_sales_2004_08_02@16_05_20.dxl. The file is stored in the diagnostic directory, IBM_TECHNICAL_SUPPORT located in Domino's data directory. If Domino/Data is the data directory, the path is


To view the collected information, open the individual documents in the IBM_TECHNICAL_SUPPORT directory.

It's true, the documents are saved in the IBM_TECHNICAL_SUPPORT directory.  They re in the DXL

Image:The Mighty Domino Configuration Collector

There is also a free tool available to read these DXLs that will actually reconstitute the document contents.  You can find the tool here. This is an Irish version but there is another around too that looks more US-ey.  Look for:

Where to obtain the Lotus Notes Diagnostic tool - That's a link from 11/22/2010

Install this, or one like it, and you can use it to open a DXL file.

Here's one I just created because I modified a server document.
Image:The Mighty Domino Configuration Collector

Here is the change I made to the serve document.

Image:The Mighty Domino Configuration Collector

When I use the tool to open it...
Image:The Mighty Domino Configuration Collector

This is what I get.
Image:The Mighty Domino Configuration Collector

And, of course, my fingerprints are all over it.
Image:The Mighty Domino Configuration Collector

You can therefore find out who made that awful change to a server document or a server configuration document and take appropriate action.  First time offenders usually get a private discussion from me. But if I find that the offender keeps on offending, we start taking away privileges to the address book and full administrator access.

There are limits to how many past documents it will save.  Check out the documentation. I just thought you might like to know about this.  It's an great oldie that got lost in the shuffle somewhere.


11:36:07 PM February 2 2011