#dominoforever | Product Ideas Portal

"How about removing interaction with notes.ini altogether and having all the settings built out on the server document, with recommendations/etc listed right alongside?" +1

How about removing interaction with notes.ini altogether and having all the settings built out on the server document, with recommendations/etc listed right alongside?

why not using a similar function to update the notes.ini Parameter documents like updating pubic Holiday schedules.

Once the new template is set to names.nsf design tab in the Database properties you could use an Action to Import/update Holiday from Template.

This should also work with notes.ini Settings.

Everything in the notes.ini should be able to be set via a policy setting on the domino server.

Old, deprecated settings should be separated to their own section so people realize these are no longer the way you should do things and can move towards the new ways.  For each replaced parameter in the deprecated Tab the recommended replacement options should be noted beside the old deprecated setting so that users can easily see where they need to go to update their old settings.

The idea of a server console log print to show deprecated parameters would be helpful. I noticed WebSphere logs do this for certain settings. Also one of the things that I like about a Traveler SystemDump is the listing of all non-standard or non-default ini parameters, what the defaults are and what the setting is configured to on the particular server. I think it would be helpful to do the same for Domino servers and print that in the NSD.

I like the idea of a notes.ini database with documentation of all the whys, when to use, and effects/affects for each.

add the information to DCT and make sure it's updated regularly/automatically

Just update DCT regularly.

A beginning has been made and around for years, open to new ini variables and free. Can be replicated and is maintained by me.

www.NotesCamp.de/notesini

please allow in such a tool also the automatic reorganization of the notes.ini parameters in sections for easier reading and finding values. Something similar  had been done by an online tool called INIGEN by Darren R Crocker, tool which is not maintained any more, afaik...

Make it a Notes application that is hosted by IBM/HCL and can be replicated by everybody. 

@Thomas, have it integrated into the dialog in the config document would make sense.
There are already some notes.ini parameters documented.

But this is not the only way to set notes.ini parameters.
And having it part of the pubnames that would make the information very static for multiple reasons:

a.) The design is only updated in a new release/dot release

b.) having it part of the design makes it quite difficult to maintain. Having it in documents would make it a lot easier and better to use

c.) Having Notes document also would give us much more flexibility and customers and partners could build their solutions based on this information.

So I would see this as a separate database that should be integrated into the pubnames dialog in the config doc.

How about extending the pubnames.ntf to actually display a description for every notes.ini variable from within the dialog box of the server configuration document?

Having a notes.ini database with all supported notes.ini variables would be very helpful!