LDD Today


Ask Professor INI

Professor INI dips into the mailbag again this month, answering your questions about NOTES.INI variables for ECLs, full-text indexing, TCP/IP port addressing, and replication.

Q. I would like to understand more about the NOTES.INI setting
<portname>_TcpIPAddress=<?>,<ip address>:<port>
The INI setting in question is actually <TCPportname>_TCPIPAddress. This variable defines the IP address and port number for a Domino server. It applies to partitioned servers using TCP/IP only. There is no UI equivalent for this variable, nor are there any default settings. The syntax is:

<TCPIPportname>_TCPIPAddress=0,IPaddress:TCP/IP portnumber

where:
Q. What values can ECLSetup take in the NOTES.INI file? What actions do different values cause?
The NOTES.INI variable ECLSetup forces the Notes client to merge the Execution Control List (ECL) settings from the Administration ECL, located on the user's home server, with the client workstation ECL. The syntax for this variable is:

ECLSetup=value

The options are:
If the value for this setting is 3 but Notes doesn't find an ECL for the current user in the desktop—for example, when multiple users with individual Notes IDs are sharing a desktop and one of them is a new user—Notes will create an ECL for that user and merge the Administration ECL from the home server specified in the Location document.

Q. I want to deploy tighter user workstation ECLs. Specifically, I want to prevent users from adding new entries to their ECLs or adding more access privileges to existing signers. Is there a way I can set up my NOTES.INI so that every morning, the ECL of each workstation gets updated from the Administration ECL?
No. Even if ECLSetup were set to 0 (that is, merging the Administration ECL on the home server with the workstation ECL), any entries in the workstation ECL that were not in the Administration ECL would be retained. However, any entries in both would be overwritten by the entries in the Administration ECL. So, if the same entry appeared in both a workstation and Administration ECL but the entry in the Administration ECL had more restrictions, the same entry in the workstation ECL would be overwritten to have the same, tighter restrictions. In any case, users could continue to add entries to their workstation ECLs.

You can, however, make your users unable to modify their workstation ECLs at all. You do this by deselecting the "Allow user to modify" checkbox in the Administration ECL.

You can also update workstation ECLs using the Refresh ECL feature. As of 5.0.5, the Execution Control List dialog box has been updated to include a Refresh button that automatically updates the workstation ECL with settings from the Administration ECL on the user's home server. When users refresh their ECLs, new entries from the Administration ECL are added to the workstation ECL. For entries that exist in both the Administration ECL and the workstation ECL, permissions assigned in the Administration ECL overwrite those assigned in the workstation ECL. Note that you, as administrator, can't remove entries, but you can overwrite entries and essentially undo the permissions previously granted.

See Domino and Notes Release Notes for 5.0.5 for more information about the Refresh ECL feature.

Q. Do you have any information on the NOTES.INI parameter Replicator_Log_Nonevents=1?
Prior to R5, Domino servers generated an entry in the Notes log's Replication Events view every time a replication connection took place, regardless of whether any documents were replicated. As of Domino 5.0, the server only generates an entry in the Replication Events view when there are documents replicated during a replication session.

An enhancement for Domino 5.0.2 changed this functionality—now the Replication Events view shows that a Replication Event document is created, even if no databases are replicated.

To log all replication events to the Replication Events view of the Notes log, regardless of whether any documents were replicated, you must add the variable Replicator_Log_Nonevents=1 to the NOTES.INI file of the server. You can do this in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory.

Q. What does "AdminLastServer" mean?
AdminLastServer records the name of the last server accessed using the Administrator client. The syntax is:

AdminLastServer=servername

To prevent the Administrator client from opening this server when started, hold down the Shift key while starting the Administrator client.

Q. How can we prevent users from creating and/or updating a full-text index? Prior to R5, we could use Update_No_Fulltext=1 to disable full-text indexing on a server. This does not seem to work now. Is there another setting we can use to disable full-text indexing on servers?
You should be able to use Update_No_Fulltext with no problems. There were some stability issues with this parameter in earlier QMRs of Domino R5; however, as of 5.0.6, this parameter is stable and functioning reliably. So, to disable the full-text indexer, use the server variable Update_No_Fulltext.

The syntax of this parameter is:

Update_No_Fulltext=value

where 0 turns full-text indexing on and 1 turns full-text indexing off.

There is no default, although if this setting is omitted, full-text indexing is enabled. You can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory

Note: If you disable full-text indexing, you must restart the server for this change to take effect.


Do you have a NOTES.INI questions? Send it in to Professor INI. We'll answer as many questions as we can in future "Ask Professor INI" columns. Keep in mind, however, that we may not be able to answer every question, nor can we quickly respond to requests that require immediate attention. If you need an immediate response to a question, we recommend you post it in the Iris Cafe Notes/Domino Gold Release Forum where someone from the general Notes community might be able to help, or contact Lotus Customer Support.