What updates the publisher filter in dsrepcfg.nsf, and how often does it happen?
The dsrepcfg.nsf publisher filter is updated by NotesDriverShim.jar every time NotesDriverShim is started.
You should not have to delete dsrepcfg.nsf in order to update the publisher filter. But if you do, the NotesDriverShim should re-create the file with an appropriate publisher filter.
dsrepcfg.nsf file is created by NotesDriverShim.jar and contains driver publisher details utilized by ndsrep, including the publisher filter. ndsrep uses the publisher filter stored in dsrepcfg.nsf to know which types of Notes documents and fields to publish to the publisher cache file (ndsrep output file; ndsrep.nsf). If dsrepcfg.nsf is present, dsrepcfg.nsf is created by NotesDriverShim.jar using Notes database methods from Notes.jar and an existing Notes database template, dsrepcfg.ntf. Every time the driver starts, dsrepcfg.nsf is appropriately updated with any new publisher information. dsrepcfg.nsf is read and can be updated by ndsrep.
To verify the contents of the publisher filter within dsrepcfg.nsf,
1. Open dsrepcfg.nsf with a Notes client.
2. Select the driver instance (by driver name).
3. View the publisher filter text within the database.
In this way you can validate exactly which types of Notes documents and fields will be published to the ndsrep publisher cache file (ndsrep.nsf).
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.