How to export the contents of a Domino.Doc Library on the local file system? (part II)

This is the scond part of a two parts article.

The Cabinet documents created by the PopolaCabinets agent stores also the total binders numbers and the total documents number.
There are also two datetime fields used to store the start and the end time of the export.

The Cabinet form to store cabinet and binders info.

The EsportaCabinet agent

Here follows the code for the EsportaCabinet agent: is the agent that create the file system structure and populates it with the Domino.Doc attachments.

Continua a leggere

How to export the contents of a Domino.Doc Library on the local file system? (part I)

What You Need:

  • a PC running Lotus Notes, Lotus Notes Designer, a Domino.Doc Desktop Enabler full installation (with the Domino.Doc API), enough disk space to hold the exported documents;
  • a Lotus Notes id with full permissions for the Domino.Doc library (the Domino.Doc id administrator usually is fine);
  • the OpenLog, an open source application available on


  1. Download OpenLog on the local machine and configure a database to store the logs generated from exports.
  2. Download from the link (in the Part II post) the application edomdoc.nsf and store it in the data directory of the Lotus Notes client.
  3. Change the ACL of the database and sign the database with the ID notes above.
  4. Open the application edomdoc.nsf in the Notes Designer.
  5. Follow the instructions in the OpenLog database in order to enable logging in the edomdoc.nsf: the Script Library OpenLogClass and OpenLogFunctions are inside the edomdoc.nsf db, so you just need to change the line in the Sub Initialize with the right name of the OpenLog db you created above.
    logDbName = “OpenLog1_5Apache.nsf”
  6. Open the PopolaCabinets agent and modify the line 31 with the Lotus Notes id password and the line 32 with the path to the Domino.Doc server library (similar action is required for the EsportaCabinet agent).

Continua a leggere