Instalacion de Quickr 8.2
INSTALLATION STEPS STEP
- Install Domino 8.0.1. You should just have to double-click the install package and follow the prompts. You can use the default settings.
- Double-click the “Lotus Domino Server” icon to launch the Server Setup routine. You can use the default settings except for the “Internet Services” page in the setup wizard, where you should make sure that HTTP and LDAP are both checked.
- After setup is complete, double-click the “Lotus Domino Server” icon again to start the server. Allow the server to run for at least 5 minutes so it can build all the necessary databases and indexes. If there is firewall software on your server, make sure that (at a minimum) port 80 and 1352 are open, and nserver.exe and nhttp.exe are allowed to listen for connections.
- Using a Lotus Notes client or Domino Administrator, open your server document in the Domino Directory and go to the “Internet Protocols”, “Domino Web Engine” tab. Make sure your server is using the Domino servlet engine, and also that session-based authentication is NOT enabled (we can re-enable it after Quickr is set up, if desired).
- Modify TCP/IP registry settings on Windows servers as follows: If your Lotus Quickr server runs on Microsoft® Windows®, you must modify specific TCP/IP registry parameters to ensure good performance. Adjust values for the following Windows TCP/IP registry parameters on the server:
TcpTimedWaitDelay
MaxUserPort
TcpWindowSize
MaxFreeTcbs
MaxHashTableSizeFor detailed information on these parameters, see the section “TCP/IP registry optimizations” in the IBM Redbook, Tuning Windows Server 2003 on IBM System x Servers.
Here are sample values for these parameters:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]“TcpTimedWaitDelay”=dword:0000001e
“MaxUserPort”=dword:0000fffe
“TcpWindowSize”=dword:0000ffff
“MaxFreeTcbs”=dword:00011940
“MaxHashTableSize”=dword:0000ffff
- Enable the Domino servlet engine. This step enables place managers to use place administration actions, such as qptool lock and unlock from My Places > Show Usage Statistics. To use this feature you must configure the server to use single sign-on authentication. Perform the following steps:
From IBM Lotus Notes® or the Domino Administrator, open the Domino Directory (names.nsf) on the server.
Open the Server document.
Click Internet Protocols > Domino Web Engine.
Below Java Servlets, select Domino Servlet Manager in the Java servlet support field.
Click Save and Close. - Enable UTF-8 character encoding for servers storing non-English content. If you use any Lotus Quickr server that stores non-English content, you must set up the server to generate output using UTF-8 encoding so that page content displays correctly in non-English languages.
From Lotus Notes or the Domino Administrator, open the Lotus Domino® Directory (names.nsf) on the server.
Open the Server document for the server and click Edit Server.
Click Internet Protocols > Domino Web Engine.
In the Character Set section, select Yes in the Use UTF-8 for output field.
Click Save and Close. - Shut down the Domino server.
- Install Quickr 8.1. When you double-click the eAssembly package it will unzip all the install files to a directory of your choice (your temp directory by default). After the files have been unzipped, you’ll need to browse to the directory they were unzipped to and look for a “server” subdirectory. Double-click the “setup.exe” file in that subdirectory to launch the Quickr Setup routine. You can use the default settings, and you will be prompted to create the Quickr Admin user during setup — NOTE: the Quickr Admin user MUST be a name that is unique to Quickr and is not already in the Domino directory (for example, “quickradmin” or something similar).
- Restart the Domino server.
- Open Internet Explorer or Firefox and browse to http://your.server.dns/LotusQuickr . Use the “Log In” link at the top right of the welcome page to log in as the Quickr Admin user you specified in Step 6. After logging in, you will see a “Site Administration” link at the bottom left of the page.
- Go to “Site Administration” and choose the “User Directory” link. In the “directory type” field choose “LDAP Server”, and in the “name” field enter the DNS name of your Domino server (for testing on the local server you can use 127.0.0.1 as the name, although in a production environment you will need to use a valid DNS host name).
- In the Specify name and password window, type the user name and password for the first Lotus Quickr server administrator. Specify the name for a new, local administrator. Do not specify the name of the Lotus Domino server administrator or any other name from a user directory that Lotus Quickr uses.
POST-INSTALLATION STEPS (optional, but STRONGLY recommended) Visit IBM Fix Central and grab the latest Quickr HotFix, and apply it using the instructions supplied. You should also enable session-based authentication on your server. If you do this, you MUST use “multi-server” session-based authentication (not single server) and follow the directions for customizing the domcfg.nsf login form, found in the Quickr Admin Guide. Your Quickr server is now ready for use! There are a number of other options and security settings that you can configure — the Quickr Admin Guide has a tremendous amount of additional information.
How To Handle ODS Database Versions in Mixed Notes Environments
Another good reference point for people undergoing a conversion… From the KnowledgeBase…
How To Handle ODS Database Versions in Mixed Notes Environments
Document Number: 1102152
Problem
How can you determine the On Disk Structure (ODS) version of a Notes database? Also how should you handle ODS in mixed Notes environments?
Content
In Notes R5 Client as well as later clients, the InfoBox for database properties displays the ODS version. To view the ODS of a database, open it and select File, Database, Properties; switch to the “i” (information) tab in the InfoBox which appears. The version will be one of the following:
- ODS version 51 = Notes 8.5 database format
- ODS version 48 = Notes 8.0 database format
- ODS version 43 = Notes 7 database format
- ODS version 43 = Notes 6 database format
- ODS version 41 = Notes R5 database format
- ODS version 20 = Notes R4 database format
- ODS version 17 = Notes R3 database format
Note: The InfoBox on a R4 Client does not show the ODS version of the same database because the ability to display the ODS version is new to the InfoBox in R5.
The following table lists some considerations for copying or replicating files between a R4 entity and a R5 entity. This information can also be used to determine the same behavior in mixed environment involving later releases (R5 vs. 6.x for example). In Notes R5 the ODS specific filename extension is NS5.
|
Scenario
|
Resulting ODS on the Target Database
|
| R4 Client creates Db locally (R4 ODS). Then, through GUI (via File, Database, New Copy or New Replica), makes a copy or replica on R5 Server. |
R5 ODS |
| R4 Client creates Db on R4 Server (R4 ODS). Then, through GUI, makes copy or replica with extension .NSF on R5 Server. |
R5 ODS |
| R4 Client creates Db on R5 Server (ODS is R5). Then, through GUI, makes copy or replica on R4 Server. |
R4 ODS |
| R4 Client creates Db on R5 Server. | R5 ODS |
| R5 Client creates Db locally (ODS is R5). Then, through GUI, makes a copy or replica on R4 Server. |
R4 ODS |
| R5 Client creates Db locally (ODS is R5). Then, through GUI, makes a copy or replica with extension .NS4 on R5 Server. |
R4 ODS (Compact on the R5 Server will leave the R4 ODS as is.) |
| R4 Client creates Db on R5 Server specifying the extension as .NS4. | R4 ODS (Compact on the R5 Server will leave the R4 ODS as is.) |
| At operating system (OS) level, user renames a file giving it a .NS4 extension. | If the database was R5, it will stay R5. If the database was R4, the next Compact will convert it to R5. If the database is compacted with Compact -r it will be R4 but only until the next time Compact runs without the -r option. |
| User receives a R5 database as an attachment in an email and detaches it to a R4 Client or Server. | R5 ODS (Neither the R4 Client nor the R4 Server will be able to use the R5 database, and won’t be able to revert it to R4 format. The message, “Invalid NSF Format” will display.) |
| R5 Client compacts a local R4 ODS Db | R5 ODS |
Some Important Concepts Regarding the Independence of ODS, Replication, and Design:
1. The ODS does not replicate. So, it is completely supported to have three replicas of a database as follows:
- One replica with R5 ODS on R5 Server
- Another replica with R4 ODS on R4 Server
- Another replica with R4 ODS on R5 Server (via .NS4 extension)
2. ODS version is unrelated to Database Design.
- Changing the ODS will not affect the database design.
- Changing the design will not affect the ODS.
- A database in R4 ODS can inherit design from a R5 template and vice versa.
3. Putting the two concepts together.
- Creating a replica with a .NS4 extension on the R5 Server will not prevent design changes when the two replicas replicate.
- The replica with the .NS4 extension on the R5 Server can inherit design from a R5 template.
- Those changes can replicate to the replica on the R4 Server.
- That could lead to problems if those R5 design elements contain features that aren’t available in R4, such as new @functions, or new LotusScript properties and methods.
Seguridad en Lotus Notes y Domino
LOTUS NOTES
Lo más destacable dentro de la seguridad de Lotus Notes es la gestión de usuarios. El correo se almacena en el servidor pero se puede mantener una copia en local en la estación de trabajo desde la que se accede. La configuración de los usuarios se guarda también en cada equipo dentro de un fichero con la extensión .ID, además de en la base de datos del servidor denominada “Domino Directory”.
Logo de Lotus Notes
Cada servidor Lotus tiene un archivo .ID único. Cada usuario también tiene un fichero .ID que contiene:
- La fecha del último cambio de contraseña
- El número de días que faltan para que la contraseña expire.
- El número máximo de días que se puede utilizar la actual contraseña sin tener que cambiarla.
- La contraseña actual cifrada.
- El histórico de los últimos 49 passwords usados y las fechas de caducidad de cada uno de ellos.
Lotus Notes, además, se protege de accesos no autorizados mediante ataques por fuerza bruta o diccionario para que, en caso de haber podido obtener el fichero USER.ID de un usuario pero no se conozca la contraseña, no se pueda acceder al servidor Domino. Para ello se va incrementando el tiempo de espera entre inicios de sesión cada vez que se introduce una contraseña errónea.
El archivo de cada usuario (USER.ID) se guarda de forma local en unidades de red o en el disco duro de cada dispositivo y contiene la contraseña (cifrada) que se puede intentar descifrar para acceder al correo electrónico de ese usuario y a las bases de datos Notes (.nsf, .box o .ns4) a las que tenga permisos. El password se almacena en el USER.ID cifrado en formato RC2 de 64 y 128 bits pero a partir de las versiones 8.5 y posteriores el nivel de cifrado ha mejorado y se puede utilizar AES de 128 o 256 bits.
En una instalación Notes, es bastante habitual encontrar numerosos ficheros de usuario (.ID) o, incluso, datos provenientes del proceso de configuración por parte de los administradores de lotus (server.id, admin.id, etc.). Basta recopilarlos e intentar descifrar la contraseña, proceso para el cual existen diversos programas, el más completo, aunque de pago, es:
- Passware Kit Enterprise que descifra contraseñas de más de 150 tipos de archivos, USER.ID de Notes entre ellos, basta indicarle la ruta donde se encuentra el fichero .ID y el programa ya reconoce que se trata de un archivo de Lotus Notes (http://www.lostpassword.com/kit-enterprise.htm).
LOTUS DOMINO E iNOTES
Como se ha visto la parte servidor se denomina Lotus Domino. Desde el punto de vista de la seguridad, lo más destacable son el montón de bases de datos de Lotus, con la extensión .NSF existentes, además de diversas plantillas y templates con la extensión .NTF donde se guarda toda la información del servidor, incluido el correo de los usuarios que suele encontrarse en la ruta /servidor_revisado.com/mail/nombre_de_usuario.NSF.
iNotes es el servicio de mensajería de Lotus para poder acceder al correo vía Web con cualquier navegador.
Para poder revisar la seguridad de un servidor Lotus desde Internet basta fijarse en aquellas bases de datos que permitan acceso anónimo y sin autenticar. Son especialmente importantes las siguientes bases de datos Lotus (.NSF) que proporcionan múltiple información acerca del sistema:
- statrep.nsf (http://servidor_revisado.com/statrep.nsf): base de datos con los resultados de la monitorización del sistema.
- schema.nsf (http://servidor_revisado.com/schema.nsf): esquema LDAP del servidor Domino.
- reports.nsf (http://servidor_revisado.com/reports.nsf): reportes del servidor.
- names.nsf (http://servidor_revisado.com/names.nsf): directorio del servidor Domino, listado de usuarios, etc.
- log.nsf (http://servidor_revisado.com/log.nsf): logs y registros de la actividad del servidor.
- events4.nsf (http://servidor_revisado.com/events4.nsf): fichero de configuración de la monitorización del sistema.
- admin4.nsf (http://servidor_revisado.com/admin4.nsf): archivo de la administración del servidor.
- webadmin.nsf (http://servidor_revisado.com/webadmin.nsf): fichero de configuración del servidor web.
- catalog.nsf (http://servidor_revisado.com/webadmin.nsf): listado de las bases de datos Lotus existentes en el servidor.
- homepage.nsf (http://servidor_revisado.com/homepage.nsf): página de introducción de la instalación de Lotus Domino, identifica la versión instalada.
- decsadm.nsf (http://servidor_revisado.com/decsadm.nsf): Domino Enterprise Connection Services (DECS).
- domcfg.nsf (http://servidor_revisado.com/domcfg.nsf: fichero con la configuración del servidor Domino.
- stcenter.nsf (http://servidor_revisado.com/stcenter.nsf): acceso al Lotus Sametime por Web que es el cliente de mensajería instantánea de Lotus.
- accounts.nsf (httP://servidor_revisado.com/accounts.nsf): fichero con los datos de usuarios del servidor Domino.
Ejemplo de base de datos de Lotus Domino – Catalog.nsf
Hay multitud de ficheros que son interesantes para revisar la seguridad, se puede incluso utilizar algún fuzzer para buscar nuevos ficheros de los desarrollos propios de cada servidor con la extensión .NSF.
Normalmente, todos estos archivos están protegidos mediante autenticación y solicitan un nombre de usuario y contraseña. Sin embargo, muchos administradores de Lotus, en un descuido, sólo deshabilitan el acceso anónimo permitiendo que, si la página web presenta algún tipo de formulario para registrarse, enviar el CV o lo que sea, se pueda crear un usuario y acceder a muchas de las bases de datos Notes que se han enumerado anteriormente.
Ejemplo de Protección de las Bases de Datos de Notes mediante autenticación
Además, con una simple búsqueda en google de ficheros .NSF (filetype:nsf) se pueden encontrar multitud de sistemas con un servidor Lotus como servidor de aplicaciones accesible.
ANALIZADORES DE SEGURIDAD PARA LOTUS
Rapid7 (http://www.rapid7.com/) de NeXpose es un escáner de vulnerabilidades comercial con una versión de evaluación. Dispone de una base de datos con numerosas vulnerabilidades para Lotus Notes pero también para otras plataformas. Algunas de estas vulnerabilidades permiten la ejecución remota de comandos en el servidor Domino que pueden comprometer al resto de la red, mientras que otros permiten el acceso libre a las contraseñas desde el Directorio de Domino. Se actualiza periódicamente.
DominoScan (http://www.ngssoftware.com/products/internet-security/dominoscan.php) de NextGenss es un escáner de seguridad que busca vulnerabilidades comunes en los servidores web de Domino.
AppDetective (http://www.appsecinc.com/products/appdetective/domino/) que es un escáner también comercial con una versión totalmente funcional que permite usarse durante un mes y que dispone también de una amplia base de conocimiento de las vulnerabilidades de Lotus Notes.
MÁS INFORMACIÓN
http://www.ibm.com/developerworks/lotus/library/domino8-lockout/index.html?S_TACT=105AGX13
http://www-01.ibm.com/software/lotus/notesanddomino/nd85.html
Remote Torrent Downloads Via SSH
Screen and BitTornado
Once I’m connected to my home network I then use a combination of Screen and BitTornado to download any torrent files.
Screen enables me to start a download and exit my SSH connection without stopping the download. I can then reconnect via SSH and use the command “screen -r” to return to the download screen and check on the progress of the download.
BitTornado is not required but I like it as it adds additional features to Ubuntu’s default bittorrent client.
You can install Screen and BitTornado with the following terminal command:
sudo apt-get install screen bittornado
Usage
1. To start a new download enter the following command [remember to replace the example URL with the location of the real torrent]:
screen btdownloadcurses http://example.com/example.torrent
You should now be able to see something similar to the screengrab below:
2. To detached the screen and leave the download running use the following key combination:
<Ctrl>+<A>+<D>
3. To reattach the screen enter the following command:
screen -r
4. Once the download has finished you can kill the screen with the following key combination:
<Ctrl>+<C>
Notes: If you have multiple screens running, entering the command “screen -r” will return a list of available screens to reattach.
LotusScript tips
10 fundamental LotusScript tips
Bill Buchan
03.27.2007
Rating: -3.82- (out of 5)
| 1. Option Declare
4. How to code 6. Extending arrays the easy way 10. Hiding your code
Make sure you always use “Option Declare.” It sounds obvious, but there are several determining factors as to why you should always use it. Here are some of the reasons:
When working with templates and versions in LotusScript in custom code, there are a few things you should always do:
You might say these all sound like good reasons, but why should I use them? There are three major reasons: 1. Because it makes it much easier to roll back. 2. It helps with version control. 3. It makes it simpler to construct test cases with other versions.
When dealing with the lifecycles of your applications, there are a few best practices you should follow: 1. Always develop in a development sandbox — a non-production environment where each developer keeps his or her working copy of the code base. 2. Always test in a user acceptance environment. 3. Pass the template to your Domino administrator to copy. Here is why you should adhere to these rules:
Here are the fundamental how’s and why’s of how to code in LotusScript:
Here is why you should follow these LotusScript how-to coding guidelines:
“Measure twice, cut one” may sound a bit cliche, but it is a good analogy when you are writing LotusScript code. Here are a couple ways it applies.
This works well because you are spending more time planning and less time doing actual labor.
You should always try to use “ubound” to establish the size of your array. Below you will find an example of it in use. Sub initialize() Dim myArray() as String redim my Array(0) call myExtend (myArray, "Hello Sailor"") end sub function myExtend(S() as String, ns as String) as integer if (S(ubound(S)) <> "") then redim preserve S(ubound(S)+1) S (ubound(S)) = ns extend = true end function If you set up your arrays this way, you won’t need to keep a separate index of the array size; it also automatically trims the code. However, there is a minor drawback to implementing this. It will slow down large arrays, so you’ll need to define the “empty” value. Otherwise, it works great.
When you use the list operator, it stores a value with a unique lookup key. It’s a good idea to use the list operator because:
Here is some example code:
Dim WR list as String
WR("Peter") = "Perfect"
WR("Penelope") = "Pitstop"
Print "Peter's last name is: " +WR("Peter")
if not isElement(WR("Dick")) then print "Dick isn't racing!"
forall thisRacer in WR
Print listtag(thisracer) + " " + thisRacer
end forall
Another good tip is to log your LotusScript agents, especially if they are scheduled agents. It’s also a good idea if you have a broad range of clients. If you do, you need to log both your client and scheduled agents runtime status. If you don’t log your agents, chances are that your applications will break. Logging your agents will also help to let you know when your LotusScript agents do break. It’s also a good timing metric for performance testing. Show caution when logging your agents though — you don’t want to make the logging so slow that it affects application performance!
When dealing with the structure of your LotusScript code, it is usually good to keep it as short as possible. Smaller code sequences are easier to deal with and maintain and are easily reusable. A good rule to go by is if your code is more than a screen’s worth, you should determine if it is possible to break it up. Some tips when determining your LotusScript code structure:
When we say we’re “hiding our code,” we’re basically saying that we’re decomposing it so consumers can’t see it. You don’t want anyone to be able to view it, not even yourself. When you hide your code, you are inferring a logical interface with clear naming. As such, your users and customers can write to the interface but not the code itself. This is good practice because it simplifies the coding experience. You can easily hide your code by using “private/public” methods in your classes, script libraries, etc. |
10 everyday LotusScript tips
Bill Buchan
03.27.2007
Rating: -4.10- (out of 5)
| 1. Use error trapping
4. Use NotesDateTime instead of strings 6. Use wizard interface in your Notes client 8. Use classes
Error trapping tests a particular condition when running a program. If the program runs into an error, it will then execute a corresponding routine to fix the error. This should always be done. Error handling is not a joke — it should always be handled in a serious manner and should always be mandatory. There are two ways to go about this:
While it may seem a bit paranoid, you should practice using defensive LotusScript coding — it will save you time in the long run. Always assume the worst and check all inputs on every function. It doesn’t usually affect performance, but it is a good failsafe. Here is a good example of defensive LotusScript coding in a typical function. Function mytest (p1as String, p2 as String) as integer mytest = false if p1 = "" then exit function if p2 = "" then exit function . . . ' Now actually do something! . . . . mytest = true end function
When creating commercial applications, it’s a very good idea to hide your code. But, you may be asking how. There are actually two ways you can go about it:
You should never store date/time values as strings. It is always good practice to use NotesDateTime structures instead and save them. You might say, sure, but why? Well, you never know how the client will interpret dates. Is it dd/mm/yyyy or mm/dd/yyyy? It also means that views will be able to sort on dates. Trust me, this is a good tip to practice. This issue comes up more often than you might think.
A good reason to consider using DXL as Transport stems from a situation where a customer wants to easily send back “log” documents. When this happens, you can use a LotusScript agent to:
At the receiving end, this will:
This way, you are transferring data without replication. Below is a sample code of this being implemented.
Dim sSession As New NotesSession
Dim dbThis As notesDatabase
Set dbThis = sSession.CurrentDatabase
Dim dc As NotesDocumentCollection
Set dc = dbThis.UnprocessedDocuments
If (dc Is Nothing) Then exit sub
If (dc.count < 1) Then exit sub
Dim doc As NotesDocument
Set doc = dc.GetFirstDocument
While (Not doc Is Nothing)
Dim de As NotesDXLExporter
Set de = sSession.CreateDXLExporter()
Call de.setInput(doc)
Dim dxl As String
dxl = de.Export
' continued overleaf..
Dim dbMail As
New NotesDatabase("", "")
Call dbMail.OpenMail()
Dim docM As NotesDocument
Set docM = dbMail.CreateDocument
Call docM.ReplaceItemValue
("Form", "Memo")
Call docM.ReplaceItemValue
("Recipients", "logs@hadsl.com")
Call docM.ReplaceItemValue
("SendTo", "logs@hadsl.com")
Call docM.ReplaceItemValue
("Subject", "Log Documents")
Dim rt As New NotesRichTextItem
(docM, "Body")
Call rt.AppendText(dxl)
Call docM.Send(False)
Set docM = Nothing
Set de = Nothing
Set doc = dc.GetNextDocument(doc)
Wend
When using a wizard interface with your Lotus Notes client, there are a few steps you should follow:
There are two different ways you can go about consuming Web services. The first is quick and to accomplish it, you should follow these steps:
Below is some code that illustrates how to create the Microsoft SOAP object.
Dim Client As Variant
Set Client = CreateObject("MSSOAP.SoapClient")
'Initialize connection to the Web Service
Call Client.mssoapinit
("http://localhost/testWS.nsf/Simple?wsdl")
'Call our simple GetEmailAddress
function provided by Web service
Dim result As String
result = Client.getJoke()
'output result to message box
Messagebox result, 48, "Get Joke"
The other approach is a little different. It’s big and robust and uses Stubby. Just point it at a Web service and it produces the code for you. Some good points about it are that it is multi-platform, scalable and there are no dynamic link libraries. However, it does require you to use more than four lines of code.
When developing with LotusScript, it is always a good idea to use classes. Here are some reasons why:
Classes have a good design methodology, which leads to Java. But everyone is not used to them and it may take time to sink in. Below you will see some code that implements classes. Class Person private nName as NotesName private strUNID as String sub new(strNewName as string, strNewUNID asString) me.nnName = new NotesName(strNewName) me.strUNID = strNewUNID end sub public function getName as String if (me.nnName is nothing) then exit function getName = nnName.Canonical end function public function getUNID as String getUNID = strUNID end function end class
The Evaluate command allows you to run @Functions within LotusScript. It is sometimes quicker and easier, as it allows you to use your favorite function in certain situations. An example of it might be: evaluate(|@unique|) Don’t overuse it though. Loads of LotusScript functions mimic @functions.
It is good practice to use trusted servers because scheduled agents cannot normally open databases on other servers. The “trusted servers” field in a Lotus Domino R6 server document’s security section allows servers to trust other servers. By doing this, it allows you to centralize “collection” agents. You also simplify your architecture and limit the number of agents you use. However, it does rely on a fast, reliable network infrastructure. |
10 advanced LotusScript tips
Bill Buchan
03.27.2007
Rating: -4.12- (out of 5)
| 1. Understand binding
5. Use platform-specific LotusScript code with classes 6. Use version-specific LotusScript code with classes 7. Use LSI_Info()/GetThreadInfo 10. Mixing Java and LotusScript
There are two types of binding: early binding and late binding. Early binding is set by the compiler and works well because it uses type checking, works quickly and is easy to use. An example of early binding might be: Dim S as String Late binding is set at runtime. It is very flexible, but doesn’t use type checking. Unfortunately, the performance isn’t as good as early binding and you might run into some runtime errors. Dim V as variant Dim S as new NotesSession set V = S.CurrentDatabase print V.getTitle()
When you’re coding for performance, always remember that expensive operations include opening Lotus Notes databases, and views and documents with lots of fields. So, when you’re collecting data, remember to cache views wherever possible and use NotesViewEntry instead of opening documents. As an example, let’s say you have a Lotus Notes database with 100,000 documents in it. This would take seven hours to actually open every document in the Lotus Notes database, if you don’t code for performance and use views. If you do code for performance, it will only take you 60 minutes to open these using NotesView and only 12 minutes if you use NotesViewEntry!
It’s good practice to use LotusScript lists and classes because classes bind complex data and operations. Lists can look these up quickly in memory. For a quick example, here’s how we might extend our Person class:
dim People list as Person
dim PeopleByUNID list as Person
Dim P as new Person
("Joe Bloggs/ACME", "010101010201020")
....
set People(P.getName) = P
set PeopleByUNID(P.getUNID) = P
if (isElement(People("Joe Bloggs/ACME"))) then _
Print "Joe's UNID is: " +
People("Joe Bloggs/ACME").getUNID
if (isElement(PeopleByUNID("010101010201020"))) then _
Print "UNID '010101010201020' is: " + _
PeopleByUNID("010101010201020").getName
Class inheritance allows us to “Extend” classes to add functionality. For example: class StaffPerson as Person private strStaffID as String sub new(strNewPerson as String, strNewUNID as String) end sub public function setStaffNumber(newNo as String) strStaffID = newNo end function public function getStaffNumber as String getStaffNumber = me.strStaffID end function end class
Dim s as new NotesSession Dim mem as variant select case s.platform case "Windows/32" set mem = new getMemW32() case "AIX" set mem = new getMemAIX() case else Print "Platform not supported" set mem = nothing end case if (not mem is nothing) then call mem.printMemory() Class getMem function getMem() as long getMem = 0 end function sub printMemory print me.getMem() end sub end class Class getMemW32 as getMem function getMem() as long getMem = getWindowsMemory() end function end class Class getMemAIX as getMem function getMem() as long getMem = getAIXMemory() end function end class
Dim s as new NotesSession dim vCU as variant select case s.version case 5 set vCU = new createUser() case 6 set vCU = new createUserv6() case else Print "Version not supported" set vCU = nothing end case if (not vCU is nothing) then _ call vCU.CreateUser(....) Class createUser function createUser(...) as integer .... end function end class Class createUserv6 as createUser function createUser(...) as integer .... end function end class
You can use the LSI_INFO() command to get some runtime information. Be aware though that this information is superceded by the GetThreadInfo command. If you use GetThreadInfo(11), that will return you the calling class. If you use GetThreadInfo(10), that will return you the function name. And these are just the beginning. Through error trapping, we can track where we came from. We don’t have to pass lists of parameters to error trapping code. It also prevents coding errors through using the copy and paste method. Here is an example of this in use, preceded by the calling code:
' calling code...
...
ExitFunction:
exit function
errorhandler:
Call RaiseError()
resume exitFunction
end function
Function RaiseError()
Dim thisType As String
Dim es as String
thisType = Typename(Me)
' Not a class, use the calling module instead
If (thisType = "") Then thisType = Getthreadinfo(11)
es = thisType & "::" & Getthreadinfo(10) & ": "
If (Err = 0) Then
es = es + "Manually raised an error"
Else
es = es +
"Run time error: (" + Trim(Str(Err)) + ") " + _
Error$ + " at line: "+ Trim(Str(Erl))
End If
Print es
end function
By using the execute command, you can run LotusScript from a string. Doing this accommodates version/platform differences at runtime. Here’s an example: Dim executeString as String executeString = | print "Hello world" dim s as new NotesSession dim db as NotesDatabase set db = s.currentDatabase print "Current Database name is: " + db.Title | execute (executeString)
By using the OpenNTF “OpenLog” solution, you can make simple LotusScript library additions to your code, provide “called from,” “error,” and “line number” functionality. Our system now works on error trap and displays all objects in memory.
By mixing Java and LotusScript together, you can really get the most out of each scripting language. The trick is to use each language to its strengths. For example, Java is good for Web service, network I/O, and multithreaded operations. LotusScript is the traditional Lotus Notes development language and works in the user interface. Mixing the two languages together is easy — just call an agent, passing a Lotus Notes document. You should also know that this works both ways, as you can call Java from LotusScript. This is called LS2J. An example is below:
// Create a Script Library of type "Java" called xlib
// containing the following function:
public class calculator {
public int add(int a, int b) { return a + b; }
public int div(int a, int b) { return a / b; }
public int mul(int a, int b) { return a * b; }
public int sub(int a, int b) { return a - b; }
}
Option Public
Use "xlib"
Uselsx "*javacon"
Sub Initialize
Dim mySession As JavaSession
Dim myClass As JavaClass,
calculator As JavaObject, a,b,c As Integer
Set mySession = New JavaSession()
Set myClass = mySession.GetClass("calculator")
Set calculator = myClass.CreateObject()
a = 10
b = 5
c = calculator.mul(a,b)
MessageBox "a * b = " & c
End Sub
|
LotusScript Lists.
One of the most powerful features of LotusScript is hardly used. Its been around for *ages* (Like, early 4.5 days, boys and girls) and would save you much pain. And yet, when I look at code – they’re not there. Why ? I don’t know.
What are they ?
Lists.
Half of the audience has went “Yeah”, and moved to the next topic. Those who have stayed on – well, brace yourself.
Imagine having an array type “thing” that you don’t have to initialise. That has auto-building indexes so you can look things up – quickly. That maintains itself. And is very, very simple to use!
Its a list.
For instance, lets pick a very trivial problem. We have four people, with first names and last names, and we want to look up the persons last name by their first name. Simple, eh ?
Using an array, you’d create the array, populate it, and every time you wanted to search it, would have to run through each element, checking it. Ouch. When you get into thousands of elements, well, it gets slow.
Lists help you.
For instance.
dim myList list as String
mylist(“Penelope”) = “Pitstop”
myList(“Peter”) = “Perfect”
myList(“Dick”) = “Dastardley”
myList(“Professor”) = “Pat Pending”.
Print “Peters last name is: ” + myList(“Peter”).
This would, of course, produce “Peters last name is: Perfect”.
All together. Slap forehead. Say “Wow!”.
And its as simple as that.
To declare,
dim myvariablename list as whateverTypeYouWant
Just a simple addition of the word list between the variable name and the typename.
Cool. But I can see you asking questions like: Well, how do I check if something is in a list. As it stands (with this rather wacky example), it’d cause a run-time error if you didn’t exactly get the indexing “thing” right. Ouch. Not good.
So use the “IsElement()” function. Like this.
If (IsElement(myList(“Peter”))) then
print “Peters last name is: ” + myList(“Peter”)
else
print “Peter is not on the list. Is he still in the race ?”
end if
Is that cool ?
So – how do you easily print out all members of a list without knowing in advance their values ? Simple again. Use FORALL.
For instance:
Print “Todays starters in the race are:”
forall Racers in myList
Print “Surname: “+ Racers
Print “First Name: ” + listtag(Racers)
end forall
Wow. So we can get the VALUE of the list assignment using forall. But whats this “ListTag” thing ? Its a way of getting the index value back. In this case, “listtag(Racers)” will produce “Penelope” on the first iteration, etc, etc.
Neat ?
So how do I get rid of ONE entry in the list ? Use Erase
erase myList(“Dick”)
To erase all entries in the list, use:
erase myList.
Couple of tips:
- Lists can get as large as you like. No limits. Well, okay, basically your constrained by the memory in your machine. Dont worry, I’ve used lists with MILLIONS of entries before.
- List comparisons tend to be case sensitive. Dont use “Option nocase” in declarations, as you can guarantee that some twit will delete it, and break your code. Convert everything to uppercase for the index value instead. Then you know what your doing
- Caveat: DONT try to dump a list straight onto a field as a multi-element array. You’ll get garbage. Convert it into an array first.
- Step through this code example in a debugger and expand the list to see whats in it.
Use them twice, and call them your own.
Lists are like a “Green Belt” thing in Lotusscript. They’re not difficult, but I see *lots* of people NOT using them, when I have to audit code. I think to myself “Ouch – this is really bad – and unreliable. This programmer could save himself a *lot* of effort using lists”.
Things like directory comparisons, for instance, you could collect *all* names from both sides of your compare, and compare them in memory, really quickly. You can pre-cache frequently looked up information from views.
This separates the hunt and peck coding brigade from proper code jockeys. Use it. Impress your friends. Speed your code. Make your life easier.
Enjoy,
123 LotusScript Tips/FAQ’s
1. How to use a range as argument in a custom @function – why cant I define a function as:
myfunc(R As Range)
2. Allowed property method usage in custom @ functions – I get the message “Only Get Property requests can be serviced…..” messages ?
3. Calling DLLs from 123 with LotusScript.
4. Can you access Win32 registry keys in LotusScript?
5. How do I construct a DLL with exported functions for 123?
6. How can I access the value of a cell within a range in a custom @ function – I cant use object methods such as Cell() in a custom @ function.
1. How to use a range as argument in a custom @function ?
The lack of documentation on this has caused a lot of head scratching. For example I want to create a custom @function to count the blank cells in a range:
@countblank(A:A1..A:D300) has a corresponding function definition : Function COUNTBLANK(Rg)
123 sheet cells basically contain only two types of contents : STRING and DOUBLE. 123 custom @ functions are meant to accept cell contents and range arguments and they do this via the Variant type. Functions defined in 123 LotusScript can be used as custom @ functions only if the arguments are untyped or typed as Variants.
Our example @countblank() is meant to count the total cells in a range would be defined as follows:
Function COUNTBLANK(Rg) ‘Allowed Rg treated as Variant
Function COUNTBLANK(Rg As Range) ‘Not Allowed in custom @ function must be untyped or variant.
Function COUNTBLANK(Rg As Variant) ‘Allowed but same as COUNTBLANK(Rg)
custom @ function arguments are assumed to be a Variant. Variants can contain a large number of different argument types e.g. String, Integer, Long, Double and Range etc and the LotusScript function Typename() can be used to read the type of variable held by the variant. e.g. tname$ = Typename(Rg) would return “DOUBLE”, “STRING”, “LONG”, “RANGE” if input as part of a custom @ function.
- If Rg is a single cell reference then 123 determines the Typename() of the cell value either “STRING” or “DOUBLE”. The exception to this is that a blank cell is set to “LONG” (instead of “DOUBLE”) and this can be used to detect blank cells.
- If Rg is a range reference e.g. “A1..A2″ or “C:D34..C:E105″ or HISTORY (where HISTORY is a valid range) Rg will be stuffed into a VARIANT with Typename() “RANGE”.
Instead do not specify any input argument types and test the arguments with Typename(A) as in the sample below:
Function @COUNTBLANK(Rg)
if Typename(Rg)<>”RANGE” Then Exit Function
Dim MyRange As Range
Set MyRange=Rg ‘Note you need to use “Set” to have 123 link the argument to the internal range MyRange
2. Allowed property/method usage in custom @ functions ?
Newcomers to custom @ function design using LotusScript will have noticed the error dialog that warns :
“Only Get Property requests can be serviced. No properties can be set and no commands can be executed because the application is in a read-only state. Make sure the application is in a read-write state then try again.”
This ensures that an @ function does not break the rule that it cannot modify any part of the workbook or workbooks. It can only return a value in the cell or cell formula in which it is located.
However, this is annoying when class methods look like they should be OK only to be rejected. For example the Cell method in the code below:
Function MYATFUNCTION(Rg)
Set cellrange=Rg.Cell(0,0,0)
MYATFUNCTION=Rg.Contents
End Function
This code sequence is not allowed because Cell() is a method you must use the Cells property instead :
Function MYATFUNCTION(Rg)
Dim cellrange As Range
Dim Rgs As Ranges ‘Rgs will be is a collection of all cells in Rg
Set Rgs=Rg.Cells ‘assuming Rg is a valid range Set elsewhere in the code (not shown)
cellrange=Rgs(0) ‘index to Rgs is zero numbered and is the top left top sheet cell of a range see
MYATFUNCTION=cellrange.Contents
End Function
See Item 6 how to index a cell in a range using the above technique.
As a general rule programmers of custom @ functions can only use ‘Properties’ of a 123 object and then only ‘Get’ not ‘Set’.
3. Calling DLLs from 123 with LotusScript.
The ‘Declare’ statement in LotusScript facilitates the calling of external functions within DLLs. Using ‘Declare’ you can access the windows SDK performing functions not available within LotusScript itself e.g.:
- read *.ini files
- read/set registry values
- locate/manipulate windows on the desktop environment
- generate sounds
- use the windows common dialog set e.g. file open, file save, color palette
You can also access your own compiled 32 bit DLLs using external windows language compilers e.g. Microsoft Visual C, Borland C++, Delphi etc. See Item 5. How do I construct a DLL with exported functions for 123?
Below is a copy of a Lotus LotusScript 123 FAQ article :http://www.lotus.com/
Quote
How do I call DLL functions?
When you create LotusScript applications for 1-2-3, you are not limited to calling LotusScript procedures. Your LotusScript applications can call any procedures that are compiled in a dynamic-link library (DLL).
To call procedures in a DLL, you need to know the following:
- The name of the DLL
- The full path for the DLL (if it is not in your default path)
- The names and parameters for procedures that you want to call
Note The following example calls a Win32 API function named sndPlaySound that is stored in the DLL file C:\WINDOWS\SYSTEM\WINMM.DLL.This function plays a Windows .WAV file. To use this function in a LotusScript application, first declare the function and then call it from a script.
Enter the following statements in (Declarations) for (Globals) if you want to call .WAV files from any script in your application.
' Runtime Dependencies: ' Files and paths: WINMM.DLL must be installed in C:\WINDOWS\SYSTEM ' or somewhere in your current path. The sound file ' OFF2RACE.WAV must be installed in the subdirectory ' C:\WINDOWS\MEDIA. ' Declare a return value to use when you call the DLL ' function in a script. Dim SoundReturnValue As Integer ' Declare the DLL function as a public function in LotusScript. Declare Public Function sndPlaySound Lib "winmm"_ Alias "sndPlaySoundA" _ ( Byval WaveFile As String, Byval theFlags As Long ) _ As Integer ' Declare some of the constants used by parameters of the DLL function. Public Const SND_SYNC = &H0000 ' play synchronously (default) Public Const SND_ASYNC = &H0001 ' play asynchronously Public Const SND_NODEFAULT = &H0002 ' silence (!default) if sound not found Public Const SND_MEMORY = &H0004 ' pszSound points to a memory file Public Const SND_LOOP = &H0008 ' loop the sound until next sndPlaySound Public Const SND_NOSTOP = &H0010 ' don't stop any currently playing sound
The following script calls the declared function and specifies a .WAV file to play.
Sub TestSoundFiles SoundReturnValue = sndPlaySound( "C:\WINDOWS\MEDIA\OFF2RACE.WAV", SND_SYNC ) End Sub End Quote
See also 4. below
4. Can you access Win32 registry keys in LotusScript?
Yes!
Yes. Pioneering these requirements have been:
http://www.grs.se/notesfaq/canaccess.html
http://www.goes.com/~graham/addshort.html
Ken Yee’s NotesFAQ site
Ken Yees site has an item :Can you access Win32 registry keys in LotusScript- that applies equally to 123.
5. How do I construct a dll with exported functions for 123?
Rules to look out for are as follows:
- must be 32 bit dll
- be careful of name mangling in exported functions of *.cpp source file based dlls. Use of the Microsoft Visual C specific: __declspec( dllexport ) double fnMyFunction(double mynumber) will produce a compiler mangled name such as _FNMYFUNCTIOND8EKK@ which the DECLARE statement will not find! Using export “C” does not entirely remove the name mangling. Instead use a *.DEF file and spell out the function names in the EXPORT section.
- strings that you need to modify in the DLL need to be passed ByVal e.g.
Declare Public Function getUpper Lib “mydll” ( Byval myStr As String) As Integer
The corresponding function exported from the DLL would be:
extern “C” double __stdcall GETUPPER(char* myStr)
here modifying the string myStr in the DLL will modify the string in the LotusScript function/sub contrary to what might be expected! - Alias for the DLL file name can be used to supply the mangled name e.g.:
Declare Public Function getUpper Lib “mydll” Alias “_MYDLL9R8F8G” ( Byval myStr As String) As Integer
where _MYDLL9R8F8G is the mangled name found using the DUMPBIN utility in Microsoft Visual C. Better to use a DEF file see above.
6. How can I access the value of a cell within a range from within a custom @ function
As a custom @ function in LotusScript does not allow use of object methods such as Cell() i.e.
cellrange = range.Cell(row, column, [sheet])
We are forced to use properties such as Cells see Item 2.
Lets say you are given a range as input and you need to get the value of cell with coordinates (S,C,R) relative to the top left cell.
‘ function returns the value at sheet S from top (+ve down), C columns to right (right +ve), R rows from top (down +ve)
Function GetVal(Rng,S,C,R)
Print “Typename(Rng)=”,Typename(Rng)
If Typename(Rng)<>”RANGE” Then Exit Function
Dim inRange As Range
Set inRange=Rng
Dim row As Integer
Dim sheet As Integer
Dim col As Integer
‘Get offsets using Cint integer type converter
row=Cint(R)
sheet=Cint(S)
col=Cint(C)
‘Check limits
Dim totcols As Integer
totcols=inRange.EndColumn-inRange.StartColumn+1
If col>totcols-1 Then Exit Function
Dim totrows As Integer
totrows=inRange.EndRow-inRange.StartRow+1
If row>totrows-1 Then Exit Function
Dim totsheets As Integer
totsheets=inRange.EndSheet-inRange.StartSheet+1
If sheet>totsheets-1 Then Exit Function
‘Index into range using Ranges collection
Dim Rgs As Ranges
Set Rgs=inRange.Cells
Dim indx As Long
indx=sheet*totcols*totrows + col*totrows + row
‘Return the cell value
GetVal=Rgs(indx).CellValue
End Function
Notes ini settings
| Notes.ini settings: A |
| Setting | Description | Example | Comment |
| Admin Applies to: Servers | Specifies the user name of the server administrator. Enter each part of the name in canonical format, separated by a slash (/), where: CN is the common name; OU is the organization unit; O is the organization; and C is the country code. There is no default setting. | Admin=CN=John Smith/ OU=Marketing/O=Acme | There is no UI equivalent. |
| AdminPInterval Applies to: Servers | Specifies the number of minutes that AdminP waits before checking for interval requests. If there is a valid Interval definition in the Server document, this variable is ignored. There is no default setting. | AdminPInterval = minutes | There is no UI equivalent, although you can specify this setting in the Notes.ini Settings tab of the Configuration Settings document in the Domino Directory. |
| AdminPModify NamesFields Applies to: Servers | Use this variable to enable AdminP to rename users in plain Names fields during a rename process, when “Modify all Reader and Author fields” is chosen in the ACL. Set the value to 1 to enable this. There is no default setting. | AdminPModify NamesFields = 1 | There is no UI equivalent. |
| AdminpModifyPerson DocumentsAt Applies to: Servers | Specifies the hour of the day when daily requests are processed. If there is a valid daily requests definition in the Server document, this variable is ignored. There is no default setting. | AdminpModifyPerson,br /> DocumentsAt = minutes | There is no UI equivalent, although you can specify this setting in the Notes.ini Settings tab of the Configuration Settings document in the Domino Directory. |
| Agent_Design_Update Applies to: Servers | Since Domino 6, the “OnBehalf” security model allows the agents to run on behalf of the specified user, as long as the agent is signed by the identity that has rights to sign agents on behalf of someone else. The server has this right implicitly. When the design update happens for enabled agents, the agents are disabled and thus stop running. When enabled, this variable restores the earlier behavior of not storing the agent signer in OnBehalf, so the agents remain enabled when a design update occurs. 1 – Does not store agent signer in OnBehalf and keeps agents enabled 2 (default) – Force disabling of agents for design updates | Agent_Design_Update = value | There is no UI equivalent. |
| Allow_Access Applies to: Servers | Specifies servers, users, and groups that can access a server. You must specify a hierarchical name in hierarchical format, for example, Alice Jones/Acme. An asterisk represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. The Deny_Access setting overrides the Allow_Access setting. | Allow_Access = names | Applies to servers. No default setting. For more information on the Deny_Access setting, see the topic “Deny_Access”. |
| Allow_Access_portname Applies to: Servers | Specifies servers, users, and groups that can access a server port. The portname parameter indicates the name of the port you enabled in the Port Setup dialog box and in the Server document. An asterisk represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. | Allow_Access_lan3 =* (All users listed in the Domino Directory can use the LAN3 port on this server) | No default setting. |
| Allow_Anonymous_Access _From_DB2 Applies to: Servers | Ordinarily, when Notes data is accessed in SQL, as through a DB2 access view (DAV) user- level security checks are done on the user, through Notes user name – DB2 user name mapping. If you don’t want to use user name mapping, you can control access to DAVs by using DB2’s GRANT mechanism, by adding this setting to the NOTES.INI file on the DB2 Access server. When this NOTES.INI setting is enabled, anonymous access to Notes is used whenever a DB2 user name is not mapped to a Notes user name. 0 – Disables anonymous access 1 – Enables anonymous access through DB2 GRANT mechanism | Allow_Anonymous_Access _From_DB2 = value | No default setting. Although enabling anonymous access removes the name mapping requirement, Domino still controls access to the DAV. In order to use anonymous access, the Domino server must allow anonymous access and the default access level of the NSF associated with the DAV must provide sufficient rights to perform the requested SQL operation. For example, read permission for SELECTS, author permission for INSERTs, and so forth. |
| Allow_Passthru_Access Applies to: Servers | Specifies servers, users, and groups that can access a server port. The portname parameter indicates the name of the port you enabled in the Port Setup dialog box and in the Server document. An asterisk represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. | Allow_Passthru_Access =* (All users listed in the Domino Directory can access this server using passthru.) | No default setting. |
| Allow_Passthru_Callers Applies to: Servers | Specifies servers, users, and groups that can instruct this server to establish a connection to call a destination server. If you do not enter a name, no calling is allowed. An asterisk represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. | Allow_Passthru_Callers = names | No default setting. |
| Allow_Passthru_Clients Applies to: Servers | Specifies servers, users, and groups that can use a passthru server to connect to this server. If you do not specify a name, passthru is not allowed. An asterisk represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash and a hierarchical certifier’s name represents everyone certified by that certifier. | Allow_Passthru_Clients = names | No default setting. |
| Allow_Passthru_Targets Applies to: Servers | Specifies the destination servers that this server can connect to using passthru. If you do not specify a name, this server can route to all servers. | Allow_Passthru_Targets = names | No default setting. |
| AMgr_DisableMailLookup Applies to: Servers | By default, a mail-triggered agent performs a mail lookup of the user who last modified it. It only runs if the server running the agent is also the user’s mail server. When users create or modify a mail-triggered agent on a server other than their own mail server, you can use this setting on the server to disable mail lookup so that the agent can run. Notes displays the message for the user “Unable to determine the execution access privileges” if the mail server cannot be reached. 0 – Perform mail lookups when running mail-triggered agents 1 – Do not perform mail lookups when running mail-triggered agents | AMgr_DisableMailLookup = value | No default setting. Without this setting, mail-triggered agents perform mail lookups. |
| AMgr_DocUpdateAgentMin Interval Applies to: Servers and clients | Specifies the minimum elapsed time, in minutes, between the execution of the same document update-triggered agent. | AMgr_DocUpdateAgentMin Interval = number of minutes | Default setting is 30 minutes. |
| AMgr_DocUpdateEventDelay Applies to: Servers and clients | Specifies the delay time, in minutes, that the agent manager schedules a document update- triggered agent after a document update event. | AMgr_DocUpdateEventDelay = number of minutes | Default setting is 5 minutes. |
| AMgr_NewMailAgentMin Interval Applies to: Servers and clients | Specifies the minimum elapsed time, in minutes, between execution of the same new mail- triggered agent. | AMgr_DocUpdateEventDelay = number of minutes | Default setting is 0 minutes. |
| AMgr_NewMailEventDelay Applies to: Servers and clients | Specifies the time (in minutes) that the Agent Manager delays before scheduling a new mail- triggered agent after new mail is delivered. | AMgr_NewMailEventDelay = number of minutes | Default setting is 1 minute. |
| AMgr_SchedulingInterval Applies to: Servers and clients | Specifies a delay (in minutes) between running of the Agent Manager’s scheduler. Valid values are 1 minute to 60 minutes. | AMgr_SchedulingInterval = number of minutes | Default setting is 1 minute. |
| AMgr_UntriggeredMail Interval Applies to: Servers and clients | Specifies a delay (in minutes) between running of the Agent Manager’s check for untriggered mail. Valid values are 1 minute to 1440 minutes (the number of minutes in a day). | AMgr_UntriggeredMail Interval = number of minutes | Default setting is 60 minutes. |
| AMgr_WeekendDays Applies to: Servers and clients | When agents use the On Schedule trigger, the Run on Schedule options box is available and includes the Don’t run on weekends check box option. When you select this option, the agent does not run on weekend days. The default value for weekend days is Saturday (7) and Sunday (1). You can specify any number of days, up to 7. For example: AMgr_WeekendDays = 1,6,7 causes agents that have the Don’t run on weekends option checked not to run on Sundays, Fridays, and Saturdays. | AMgr_WeekendDays = day1, day2, … | Default setting is 7 (Saturday) and 1 (Sunday). |
| AppleTalkNameServer Applies to: Servers and clients | Applies to AppleTalk users only. Identifies the name of the user’s secondary AppleTalk server. For more information, see your AppleTalk network documentation. | AppleTalkNameServer = server name | No default setting. |
| AutoLogoffMinutes Applies to: Clients | Specifies the number of inactive minutes before a user is automatically logged off. | AutoLogoffMinutes = number of minutes | In the UI, select File – Preferences – User Preferences – Basics – Lock ID after x minutes of inactivity. |
| Notes.ini settings: B |
| Setting | Description | Example | Comment |
| BatchRegFile Applies to: Servers | Use this variable on servers to specify the name of a batch registration file. If you add this variable, Domino does not prompt you for the filename when you import users from a text file. | BatchRegFile = file name | There is no default setting. |
| BillingAddinOutput Applies to: Servers | Specifies where Domino logs billing events. Use the following values to set this variable: 1 – Billing database (BILLING.NSF) 8 – Binary file (BILLING.NBF) 9 – Both the billing database and binary file Domino creates the BILLING.NSF database and/or the BILLING.NBF file the first time the billing add-in task is started with this option set. | BatchRegFile = file name | Default setting is 1. |
| BillingAddinRuntime Applies to: Servers | Specifies how long the billing add-in task runs. For example, BillingAddinRuntime = 30 specifies that the billing add-in will process billing records for 30 seconds. After 30 seconds the billing add-in stops processing records, even if there are additional records to be processed. The BillingAddinRuntime value must be less than the value you specify for the BillingAddinWakeup variable. Applies to servers. Default setting is 10 seconds. | BillingAddinRuntime = number of seconds | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| BillingAddinWakeup Applies to: Servers | Specifies how often the billing add-in task runs. For example, BillingAddinWakeup = 300 specifies that the billing add-in task wakes up every five minutes (300 seconds) to process the billing records in the billing message queue. The BillingAddinWakeup value must be greater than the value you specify for BillingAddinRuntime. Applies to servers. Default setting is 60 seconds. | BillingAddinWakeup = number of seconds | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| BillingClass Applies to: Servers | Specifies one or more of six classes of billing activity:
The billing process tracks only the activities that you specify in the BillingClass variable. There is no default setting. | BillingClass = class(es) | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| BillingSuppressTime Applies to: Servers | Specifies the frequency of record stamping during session and database activities if session and database activities are specified for the BillingClass variable. If you want billing data collected more frequently, decrease the default value (15 minutes). To minimize the billing workload on your system, increase the value. | BillingSuppressTime = number of minutes | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| BrowserRenderDisable Applies to: Clients | Specifies the use of browsers other than the Notes embedded browser for rendering HTML-formatted mail messages for reading only. (If a user edits an HTML-formatted mail message or forwards or replies to one, the new mail message is rendered using the Notes-embedded browser, and may not retain all of the original HTML formatting.) You may want to disable the improved HTML rendering for security reasons, as HTML formatting has some risks associated with its use. 1 (default) – Use Microsoft Internet Explorer, Mozilla, and Safari browsers for HTML-formatted mail messages 0 – Use the Notes embedded browser for HTML-formatted mail. | BrowserRenderDisable = value | There is no UI equivalent. |
| Notes.ini settings: C |
| Setting | Description | Example | Comment |
| CDP_Command Applies to: Servers and clients | The set of CDP settings control the opening, handling, and closing of applications using OLE. All OLE applications use these variables:
All other applications use DIP and need to be hard-coded with separate lines. For normal usage, you should never need to modify CDP settings. There is no default setting. | CDP_Command = value | There is no UI equivalent. |
| CertificateExpChecked Applies to: Servers and clients | Specifies the path to the local ID file and the last time the ID was checked for certificates that have expired or are about to expire. By default, the ID file and last date are checked for expiration. | CertificateExpChecked = path and date | There is no UI equivalent. |
| CertifierIDFile Applies to: Servers and clients | Specifies the path to the certifier ID. The path must contain the drive letter or network drive, directories, and file name. For example:
| CertifierIDFile = path | There is no UI equivalent. |
| ClockType Applies to: Servers | Specifies whether the Domino server clock displays time in 12-hour format (AM and PM) or 24-hour format (sometimes called military time). A value of 12_HOUR sets the clock type as 12-hour. A value of 24_HOUR sets the clock type as 24-hour. This setting overrides the system clock setting defined in the server’s operating system. Applies to UNIX servers only. There is no default setting, although without this setting the Domino server displays 12-hour time. | ClockType = value | There is no UI equivalent. |
| Clrepl_Obeys_Quotas Applies to: Servers | Specifies whether the Cluster Replicator obeys quotas. 0 – Disables the Cluster Replicator from obeying quotas. 1 – Enables the Cluster Replicator to obey quotas. By default, the Cluster Replicator does not obey quotas. | Clrepl_Obeys_Quotas = value | There is no UI equivalent. |
| Cluster_Replicators Applies to: Servers | Use this setting to start multiple cluster replicators, where value is the number of cluster replicators required. By default, Domino starts one cluster replicator. | Cluster_Replicators = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Compact_Retry _Rename_Wait Applies to: Servers | If you have specified a value for the Num_Compact_Rename_Retries setting, Domino waits 30 seconds before trying to rename a database that was copy-style compacted. You can request a different amount of time to wait by specifying the value of the Compact_Retry_Rename_Wait setting in the NOTES.INI file. For example, to request that Domino wait 2 minutes before trying rename a database that was copy-style compacted, specify Compact_Retry_Rename_Wait = 120. Domino enforces the following upper limit when trying to rename a copy-style compacted database: Num_Compact_Rename_Retries x Compact_Retry_Rename_Wait <= 60 minutes. There is no default, but in the absence of the setting, Domino waits 30 seconds before trying to rename a database that was copy-style compacted. | Compact_Retry _Rename_Wait = number of seconds | There is no UI equivalent. For more information, see the entry for Num_Compact_Rename_Retries setting. |
| Console_Log_Enabled Applies to: Servers | Specifies whether to enable logging to the Console Log file (CONSOLE.LOG, by default). 0 – Disable Console Log file logging 1 – Enable Console Log file logging To toggle logging to the Console Log file from the server console, use the “start consolelog” and “stop consolelog” commands. There is no default setting. | Console_Log_Enabled = value | There is no UI equivalent. |
| Console_Log_Max _Kbytes Applies to: Servers | Sets the maximum size of the Console Log/mirror files. Mirroring makes use of the circular log mechanism; therefore, if mirroring is enabled circular logging, Console_Log_Max_KBytes, is automatically enabled also. When the Console Log wraps, the new mirror file is created. When mirroring is enabled, the default value for Console_Log_Max_KBytes is 100,000 (100 MB) and the maximum value is 1,000,000 (1 GB). When mirroring is enabled, the default value for Console_Log_Max_KBytes is 100,000 (100 MB) and the Maximum value is 1,000,000 (1 GB). 100,000 (default) – Default when mirroring is enabled. 1,000,000 – Maximum value | Console_Log_Max _Kbytes = value | There is no UI equivalent. |
| Console_Log_Mirror Applies to: Servers | Enables the mirroring feature. When mirroring is enabled, all keystrokes are copied to the console log and mirrored, so backspaces may appear in the console logs. When mirroring is enabled, the new Server thread “Console Log Mirror Task” is created. Existing mirror files are deleted if the NOTES.INI setting, Retain_Mirror_Logs, has not been set. A new mirror file is created and is assigned the name of the console log with a number appended to it, where 999 is the maximum appended number. The default console log name is CONSOLE.LOG. As the console log changes, the data is read from the console log and copied to the new mirror log file. Console_Log_Mirror is disabled by default. 0 or not present (default) – Disables console log mirroring 1 – Enables console log mirroring | Console_Log_Mirror = 1 | There is no UI equivalent.” |
| ConstrainedSHM Applies to: Servers | Introduced in Domino 6.0. When enabled, restricts shared memory to a set of default sizes:
| ConstrainedSHM = 1 | There is no UI equivalent.” |
| ConstrainedSHMSizeMB Applies to: Servers | Introduced in Domino 6.0. Restricts memory to the size (in MB) specified. | ConstrainedSHMSizeMB = size in mega-bytes | There is no UI equivalent. |
| Country_Language Applies to: Servers and clients | Specifies the language used for the Domino/Notes interface. Default value is en-US (US English). | Country_Language = value | UI equivalent: File – Preferences – User Preferences – International – Content Language dialog box. You can also specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Crash_SendtoIBM Applies to: Servers | To enable the Send to IBM feature on the Domino server, set this variable to 1. When the server restarts after a server crash, diagnostic information is collected and an email is sent to IBM. There is no default setting. | CRASH_SENDTOIBM = 1 | There is no UI setting for this Notes.ini variable. See Debug_Crash_SendtoIBM_Disable. |
| Create_File_Access Applies to: Servers | Specifies users, servers, and groups that can create new databases on the server. You must specify a hierarchical name in hierarchical format, for example, Alice Jones/Acme. If you don’t specify a name, all certified users can create files. An asterisk (*) represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash ( / ) and a hierarchical certifier’s name represents everyone certified by that certifier. There is no default setting. | Create_File_Access = names | UI equivalent: The Create New Databases field in the Security tab of the Server document. The Server document takes precedence over the NOTES.INI setting. Domino uses the Create_File_Access setting only if the Create New Databases field is empty. |
| Create_Replica_Access Applies to: Servers | Specifies the groups that can create replicas on the server. You must specify a hierarchical name in hierarchical format, for example, Alice Jones/Acme. If you don’t specify a group, all certified users can create replicas. An asterisk (*) represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. There is no default setting. | Create_Replica_Access = names | UI equivalent: The Create Replica Databases field in the Security tab of the Server document. Note that the Server document takes precedence over the NOTES.INI setting. Domino uses the Create_Replica_Access setting only if the Create Replica Databases field is empty. |
| Create_R8_Databases Applies to: Servers | To allow compression of database design, NSFs must be ODS 48. Use this setting to upgrade the databases to ODS 48. There is no default setting. | Create_R8_Databases = 1 | There is no UI setting for this Notes.ini variable. This setting affects only NSFs; it has no effect on DB2-enabled Notes databases. |
| CSEnblRstTm Applies to: Clients | Sometimes, in a series of repeating meetings, some instances of those meetings are rescheduled for different meeting times. The chair of a repeating meeting may decide to synchronize all or some of the repeating meetings to be at the same time. Users have the option of resetting the times on some or all meeting instances based on one instance’s times. In order to take advantage of this feature, the Calendaring and Scheduling ResetTimes feature in the associated Desktop policy must be enabled, or if policies are not being used, then this variable must be enabled in the workstation Notes.ini file. 0 – User cannot reschedule repeating meetings using the ResetTimes feature 1 – User can reschedule repeating meetings using the ResetTimes feature There is no default setting. Applies to workstations. | CSEnblRstTm = value | UI equivalent: The “Reschedule repeating meetings using ResetTimes feature” on the Databases tab of the Desktop Settings document. |
| CTF Applies to: Clients | Specifies the international import/export character set. | CTF = file name | UI equivalent: File – Preferences – User Preferences – International – Import/Export Character Set dialog box. |
| Notes.ini settings: D |
| Setting | Description | Example | Comment |
| DB2Database Applies to: Servers | Stores the name of the specified DB2 database. Applies to servers. Default value is Domino. | DB2Database = name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2 After the DB2 Enablement Tool is run on a Domino server, and the server is restarted, DB2 Notes.ini settings are automatically added to the Notes.ini file. |
| DB2DBCodepage Applies to: Servers | Indicates the code page for the DB2 database to be created. This setting is ignored after the DB2 database is created. The default is UTF-8, and should not be changed. Applies to servers. | DB2DBCodepage = UTF-8 | There is no UI equivalent. |
| DB2_DBS_Per_Schema Applies to: Servers | Specifies the maximum number of Notes-enabled DB2 databases that a DB2 database schema can contain. The limit specified here is read by the DB2 database creation code. This information is updated on server shutdown and on the regular poll interval. Applies to servers. Default value is 10. | DB2_DBS_Per_Schema = value | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2 |
| DB2Directory Applies to: Servers | Specifies the name of one or more directories in which table spaces for Domino databases are stored. Applies to servers. No default setting. | DB2Directory = name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2. |
| DB2Init Applies to: Servers | Specifies the status of DB2 object creation, as follows:
No default setting. | DB2Init = value | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2. |
| DB2Instance Applies to: Servers | Stores the name of DB2 instance or DB2 node name you specify for the Domino environment. | DB2Instance = name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2. |
| DB2QueryViewRowLimit Applies to: Servers | Specifies the maximum number of rows returned by an SQL query when using query views in Domino Designer. This setting must be added manually. It is not automatically added to the NOTES.INI file after the DB2 Enablement Tool is run on a Domino server. Default value is 500. | DB2QueryViewRowLimit = value | UI equivalent: On DB2-enabled servers designers can set “Maximum rows returned by an SQL query” in the View Properties – option tab. If the DB2QueryViewRowLimit variable is set at the server level, designers can still limit the number of rows to a smaller value, and the smaller value will take precedence. |
| DB2UDFPath Applies to: Servers | Specifies the full path for the location of the DB2 Access server. The DB2 database uses this path to access the DB2 Access server .dll. There is no default value. | DB2UDFPath = path name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2 |
| DB2UDFPath Applies to: Servers | Specifies the full path for the location of the DB2 Access server. The DB2 database uses this path to access the DB2 Access server .dll. There is no default value. | DB2UDFPath = path name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2 |
| DB2UDFServer Applies to: Servers | Specifies the name of the DB2 Access server installed with DB2. The server name is used for DB2 Access views. There is no default value. | DB2UDFServer = server name | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2 |
| DB_Creation_Default_Type Applies to: Servers | Specifies the default format – DB2 or NSF – in which to create and store Domino databases in DB2. The default value is DB2. | DB_Creation_Default_Type = format | UI equivalent: DB2 tab on the Server document of the server that has been enabled for DB2. |
| DB2_DBS_PER_SCHEMA Applies to: Servers | Specifies the maximum number of DB2-enabled Notes databases per DB2 group. A DB2 group is a container, or tablespace, for DB2-enabled Notes databases. This value is set to ten for performance purposes. If you change the entry to a value greater than ten, the next time a database create is performed, the DB2 groups will backfill until the new maximum number of DB2-enabled Notes databases per group is reached. For example, the next DB2-enabled Notes database will be associated with GRP1 unless it is explicitly locked. You cannot reset the maximum number of databases allowed in a DB2 group that is locked. The default value is 10. | DB_DBS_Per_Schema = value | UI equivalent: The “Maximum number of NSFs in Group” field on the DB2 tab of the Server document |
| DDE_Timeout Applies to: Clients | The amount of time (in seconds) Notes waits for another DDE application to respond to a DDE message. The default value is 10 seconds. | DDE_Timeout = number of seconds | UI equivalent: The “Maximum number of NSFs in Group” field on the DB2 tab of the Server document |
| DDM_SecProbe _PersonDoc_Limit Applies to: Servers | The DDM Best Practices probe subtype, by default, reports on the first 25 Person documents that do not comply with the probe configuration settings. Use this setting to specify the number of Person documents on which to report. The value of Number of Person docs reported can be anything between 0 and 250, inclusive. 0 indicates that no person documents will be reported. Instead, a summary report will be produced that indicates the number of person document that do not comply with the probe specifications. 250 is the upper limit of the number of Person documents reported upon. This limit is imposed to insure that the report (detail document) does not become unreasonably large. The default value is 25 Person documents. | DDM_SECPROBE _PERSONDOC_LIMIT = number of Person docs reported | There is no UI equivalent. |
| DEBUG_CRASH_ SENDTOIBM_DISABLE Applies to: Clients | To disable the Send to IBM feature on the Notes client, add this setting to the Notes.INI file on the Notes client: There is no default setting. | DEBUG_CRASH_ SENDTOIBM_DISABLE = 1 | There is no UI setting for this Notes.ini variable. |
| Debug_Outfile Applies to: Servers | Specifies the file name to which to send all console output, so that it can be sent to IBM Support for analyis. If both this setting and the LogFile_Dir setting exist and Debug_Outfile contains a fully qualified path name, then LogFile_Dir is not used. If only the Debug_Outfile setting exists and it contains only a file name, then the default path \DATADIRECTORY\ IBM_TECHNICAL_SUPPORT is used. If neither Debug_Outfile or LogFile_Dir exist, then the default path is \DATADIRECTORY\ IBM_TECHNICAL_SUPPORT and the default path is CONSOLE.LOG. There is no default setting. | Debug_Outfile = file name | There is no UI equivalent. |
| Debug_Roaming Applies to: Clients | Use this setting, along with Debug_Outfile, to collect information when troubleshooting a roaming user problem. After upgrading a Notes user to a status of roaming user, add these two NOTES.INI variables to the NOTES.INI file on the Notes client. The Notes client will generate debug codes to the file specified in the Debug_Outfile setting. You can then provide this information to Support to assist you in resolving problems. There is no default setting. | Debug_Roaming = 1 | There is no UI equivalent. |
| Debug_Smart_Upgrade Applies to: Servers and clients | Use this variable to enable all Smart Upgrade messages to be sent to the console, either for the Domino server or on the Notes client. 1 – Enable console output of Smart Upgrade messages 0 – Disable console output of Smart Upgrade messages The default setting is 1. | Debug_Smart_Upgrade = value | There is no UI equivalent. |
| Debug_SSL_Cert Applies to: Servers | Enables viewing of certificate information at the server console. To enable viewing, set Debug_SSL_Cert to a value of 2. There is no default setting. | Debug_SSL_Cert = value | There is no UI equivalent. |
| DEBUG_SSO_TRACE _LEVEL Applies to: Servers | Use this variable to obtain detailed debugging information for Internet protocols that support single sign-on, such as HTTP and DIIOP. 1 – Prints debugging information as tokens are generated and verified, as well as configuration details. 2 – Prints detailed memory dumps as tokens are generated and verified in addition to the information above. Default setting is 0. | DEBUG_SSO_TRACE _LEVEL = value | There is no UI equivalent. |
| Debug_ThreadID Applies to: Servers | Prepends all console output with the Process ID and Thread ID of the thread that generated the output. There is no default setting. | Debug_ThreadID = 1 | There is no UI equivalent. |
| Debug_Fault_Analyzer Applies to: Servers | If Fault Analyzer is enabled, upon server start-up it reads all of the server configuration documents and desktop policy documents in the local Domino Directory. If any of these documents have a fault reports database specified (DCLoc), Fault Analyzer determines if the database is on the local server and if so will add it to its list of databases to monitor. Every 10 seconds, the process will see if the data-modified time of any of the databases it is monitoring has changed, and if so, will scan for new unprocessed documents to try to match. Use DEBUG_FAULT_ANALYZER to provide debug information for Fault Analyzer as follows: 1 – lists errors 2 – list errors and also show the progression of the code (for example, ‘found 3 matching databases’ or ‘looking for new faults’) There is no default setting. | Debug_Fault_Analyzer = value | There is no UI equivalent. |
| DEBUG_TRANSLOG _EXTENTS_PERCENTAGE _FULL Applies to: Servers | Allow administrators to specify that the disk be full by a certain percentage before deleting extents, rather than marking them for reuse. There is no default setting. | DEBUG_TRANSLOG _EXTENTS_PERCENTAGE _FULL = percentage | There is no UI equivalent. |
| Default_Index_Lifetime _Days Applies to: Servers | Specifies a default lifetime for view indexes if none was selected by the database designer in the view properties box. If the index is inactive for the specified number of days, the Indexer task purges the index. For example: Default_Index_Lifetime_Days = 60 sets the lifetime of indexes to 60 days. There is no default setting. | Default_Index_Lifetime _Days = number of days | None, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| DEFAULT_QV_USER Applies to: Servers | Use this variable to indicate whether or not to use the default DB2 user, as specified using the Admin Client configuration tab tool. The default name will be retrieved from the server ID. There is no default setting. 0 – Use the default DB2 user 1 – Do not use the default DB2 user | DEFAULT_QV_USER = value | There is no UI equivalent. |
| Deny_Access Applies to: Servers | Specifies servers, users, and groups that are denied access to the server. You must specify a hierarchical name in hierarchical format, for example, Alice Jones/Acme. An asterisk (*) represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash (/) and a hierarchical certifier’s name represents everyone certified by that certifier. The Deny_Access setting overrides the Allow_Access setting. For more information, see the Allow_Access setting. There is no default setting. | Deny_Access = names | UI equivalent: The Not Access Server field in the Security tab of the Server document. The Server document takes precedence over the NOTES.INI setting. Domino uses the Deny_Access setting only if the Not Access Server field is empty. |
| Deny_Access_portname Applies to: Servers | Specifies servers, users, and groups that are denied access to a specific server port. The portname parameter indicates the name of the port you enabled in the Port Setup dialog box and in the Server document. An asterisk (*) represents everyone listed in the Domino Directory. An asterisk followed by a view name represents everyone listed in that view of the Domino Directory. An asterisk followed by a slash and a hierarchical certifier’s name represents everyone certified by that certifier. For example: Deny_Access_SPX = Terminations. The users in the Terminations group cannot access the SPX port. There is no default setting. | Deny_Access_portname = names | There is no UI equivalent. |
| Desktop6 Applies to: Clients | Use this setting to specify the location of the DESKTOP6.DSK file used to customize the Notes workspace. For example:
There is no default setting, although if this setting is omitted, Notes looks for the file DESKTOP6.DSK in the Notes Data directory. | Desktop6 = path | There is no UI equivalent. |
| DIIOPConfigUpdate Interval Applies to: Servers | Specifies the time interval, in minutes, at which DIIOP should refresh its configuration data from the Domino Directory. The default value is 3 minutes. | DIIOPConfigUpdate Interval = number of minutes | There is no UI equivalent. |
| DIIOPCookieCheck Address Applies to: Servers | Modifies the behavior of server-based cookies used with applets that are downloaded by the Domino HTTP server. Set the value to 1 to enable the checking of client IP addresses for these cookies. The default value is 0 (disabled), which means that DIIOP will not require the client’s IP address using one of these cookies to match the IP address of the client to whom the cookie was issued. Client IP addresses will not match in most cases because the cookie is issued to the browser using the HTTP protocol, which is typically routed through proxy servers and therefore the client appears to be the proxy server. While the user of the cookie is the applet running in the browser, its network traffic does not go through a proxy server. | DIIOPCookieCheck Address = value | There is no UI equivalent. |
| DIIOPCookieTimeout Applies to: Servers | Modifies the behavior of server-based cookies used with applets that are downloaded by the domino HTTP server. It specifies the time period (number of minutes) for which each cookie is valid. When a cookie expires it cannot be used to obtain a session with the DIIOP task. The minimum setting is 1 minute. The default value is 10 minutes. | DIIOPCookieTimeout = number of minutes | There is no UI equivalent. |
| DIIOP_Debug_Invoke Applies to: Servers | Use for debugging only. It provides a level of logging beyond that of DIIOPLogLevel. Each transaction that the DIIOP task receives is logged along with the object ID that was the target, as well as the session ID. Valid values are: 1 – Show transaction details when a transaction finishes 2 – Show transaction details when a transaction starts. There is no default value. | DIIOP_Debug_Invoke = value | There is no UI equivalent. |
| DIIOP_DUP_KEYRING Applies to: Servers | To use SSL with DIIOP/NCSO and the remoted back-end classes, the Domino server must first be configured for SSL. When SSL is configured on a server, a keyring is created to contain the server certificates. A Domino server keyring has the file extension .kyr and is specified in the server document and in the Internet site document. Each Domino server that uses SSL must have a trusted root certificate from a certificate authority in its server keyring file. TrustedCerts.class is also a keyring that only contains the public certificate server’s signer, also known as the trusted root certificate. TrustedCerts.class is automatically created by DIIOP, using the server’s or Internet site key ring(s), when DIIOP is configured to listen on the SSL port. It is typically found under the domino\java directory. The server will accept DIIOP SSL sessions from a remote Java client to encrypt the network traffic. DIIOP SSL currently does not support authentication with client certificates. When the Java client and the Domino server share a trusted root, they can establish an encrypted network session. The Notes.ini setting DIIOP_DUP_KEYRING = classname creates a Java class file that contains the same certificates that are in the TrustedCerts.class, but the class name can be user specified. The class name can be used as a parameter to the methods, below, by including -ORBSSLCertificates = classname in the string array argument.
There is no default value. | DIIOP_DUP_KEYRING = class name | There is no UI equivalent. |
| DIIOPDNSLookup Applies to: Servers | Specifies that DIIOP should do a DNS name lookup for every client that connects and uses DIIOP services. This information is visible when using the server console command “show tasks.” Set the value to 1 to enable DNS lookups for clients. The default value is 0 (disabled). | DIIOPDNSLookup = value | There is no UI equivalent. |
| DIIOPIgnorePortLimits Applies to: Servers | This parameter is only valid on a Linux platform. It indicates that DIIOP may use the default ports of 63148 and 63149. On some Linux installations, the default ports are not available for use and DIIOP will automatically select ports 60148 and 60149. Set this value to 1 to use the higher numbered ports. The default value is 0 (use default ports). | DIIOPIgnorePortLimits = value | There is no UI equivalent. Prior to Domino 6, this variable was known as DIIOP_IGNORE_PORT _LIMITS. It is still valid for backwards compatibility. |
| DIIOPIORHost Applies to: Servers | To have DIIOP advertise its existence using an alternate hostname or IP address, you can set DIIOPIORHost to an alternate host name or address other than the server default. The server default is based on the value specified in the Server document setting “Fully qualified Internet host name.” The default value is to use the setting in the Server document. | DIIOPIORHost = host name | The preferred method of setting this value is through the Server document, on the DIIOP section of the Internet Protocols tab. Prior to Domino 6, this variable was known as DIIOP_IOR_HOST. It is still valid for backwards compatibility. |
| DIIOPLogLevel Applies to: Servers | This parameter increases the level of information that DIIOP reports to the server console and to the log. This value can be set manually by modifying the NOTES.INI directly or it can be set using the “tell diiop log=n” command. Possible values are: 0 – Show Errors & Warnings only 1 – Also show informational messages 2 – Also show session init/term messages 3 – Also show session statistics 4 – Also show transaction messages | DIIOPLogLevel = value | There is no UI equivalent. |
| Dircat_Include _Readerslist_Notes Applies to: Servers | When set to 1 the Dircat task aggregates documents that contain Readers lists. Users that are not in the Readers lists can nevertheless read these documents in the directory catalog. There is no default setting. Without this setting the Dircat task does not aggregate documents that contain Readers lists. Note that even users who are included in the Readers list cannot access the documents through the directory catalog. | Dircat_Include _Readerslist_Notes = value | There is no UI equivalent. |
| Dircat_Include _Readerslist_Notes Applies to: Servers | Have the Dircat task aggregate documents that contain Readers lists. Dircat does not do this by default. | Dircat_Include _Readerslist_Notes = value | There is no UI equivalent. |
| Directory Applies to: Servers and clients | Specifies the location of the Data directory for Domino or Notes. This path is originally set during the Install program. The default is C:\LOTUS\NOTES\DATA, or the directory specified during the Install program. | Directory = path | UI equivalent: File – Preferences – User Preferences – Basics – Local database folder |
| Disable_Cluster_Replicator Applies to: Servers | Use this setting to disable/enable cluster replication. 0 – Cluster replication enabled 1 – Cluster replication disabled There is no default setting, but cluster replication is on by default. | Disable_Cluster_Replicator = value | There is no UI equivalent. |
| DisableLDAPOnAdmin Applies to: Servers | If you do not want to run the LDAP service on any server in a domain, you can stop the LDAP service from running on the administration server for the Domino Directory. Set this INI setting to 1, and remove LDAP from the ServerTasks Notes.ini setting. | DisableLDAPOnAdmin = value | There is no UI equivalent. |
| Disable_SaveServerConfig Applies to: Servers | At server startup, the automatic collection of files containing server configuration information, including NSD files, can be disabled through this variable. Set Disable_SaveServerConfig = 0 to disable this feature. See Disable_SaveNSDConfig for more information. | Disable_SaveServerConfig = value | There is no UI equivalent. |
| Disable_View_Rebuild_Opt Applies to: Servers | Use this setting to enable/disable the view rebuild optimization feature, which presorts the view entries in temporary files before inserting them into the view index. Use the following values for this setting: 0 – Enables 1 – Disables There is no default setting, although the view rebuild optimization feature is enabled in Domino by default. | Disable_View_Rebuild_Opt = value | There is no UI equivalent. |
| DisabledPorts Applies to: Servers and clients | This setting indicates which ports are disabled for the server or workstation. Ports are enabled/disabled in Server documents (servers) and in the User Preferences dialog box (workstations). There is no default setting. | DisabledPorts = port name(s) | On a workstation, see the Ports tab in the User Preferences dialog box (choose File – Preferences – User Preferences). On a server, see the Port tab in the Server document. |
| DisableLDAPOnAdmin Applies to: Servers | If set to DisableLDAPOnAdmin = 1 prevents the LDAP task from running on the administration server of the Domino Directory for a domain. Since this administration server manages the schema and verifies the directory tree for all servers in the domain that run the LDAP service, use this setting only if you do not run the LDAP task on any server in a domain. To disable the LDAP service on the Domino Directory administration server, you must also remove the LDAP task from the server’s ServerTasks NOTES.INI setting. To prevent the LDAP task on the Domino Directory administration server from processing LDAP requests but still allow it to manage the schema and verify the directory tree for other servers in the domain that run the LDAP service, disable the ports for the LDAP service on the administration server. There is no default setting. | DisableLDAPOnAdmin = value | There is no UI equivalent. |
| DisplayFontAdjustment Applies to: Clients | Varies the display font of the client by a degree proportionate to the number. Negative numbers make the font smaller; positive numbers make it bigger. Values range from -25 to 25. There is no default setting. | DisplayFontAdjustment = n | There is no UI equivalent. |
| Display_MessageID Applies to: Servers | Enables the display of the hexadecimal Message ID (MID) for events written to the Domino console. The MID is usually equivalent to the resource ID for that string in the Domino resource table. The console will print them in curly braces, following a {Module:MID:SC} format. MIDs and SCs can be toggled individually. 0 – Disables the MID display for events written to the console 1 – Enables the MID display for events written to the console The default setting is disabled. | Display_MessageID = value | There is no UI equivalent. |
| Display_MessageSeverity Applies to: Servers | Enables the display of the hexadecimal Severity codes (SC) for events written to the Domino console. The console will print them in curly braces, following a {Module:MID:SC} format. MIDs and SCs can be toggled individually. 0 – Disables the SC display for events written to the console 1 – Enables the SC display for events written to the console The default setting is disabled. | Display_MessageSeverity = value | There is no UI equivalent. |
| Domain Applies to: Servers and clients | On a server, specifies the server’s domain. On a workstation, specifies the domain of the user’s mail server. This setting must contain at least one default name. | Domain = name | On a server, the Domain Name field in the Basics tab of the Server document; on a workstation, the Domain field in the Mail tab in the user’s Person document. |
| DominoComplete DocType Applies to: Servers | Use any of the following values for this .INI variable to have the Domino Web server product various doctype strings in the generated HTML: 0 (default) – <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”> 1 – <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN” “http://www.w3.org/TR/ html4/loose.dtd”> 2 – <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN” “http://www.w3.org/TR/ html4/strict.dtd”> | DominoComplete DocType = value | There is no UI equivalent. |
| DominoDisableFile UploadChecks Applies to: Servers | Stops the Domino server from checking to see if a file upload is coming from a file upload control. This allows developers to code HTML file upload files and have uploads complete successfully. There is no default. | DominoDisableFile UploadChecks = value | There is no UI setting for this Notes.ini variable. |
| DominoDisableLast ModifiedWithETAGS Applies to: Servers | If the Domino Web server is using ETag headers, set this variable to 1 so the server will not generate Last-Modified headers. The variable only has an effect if the Web server generates ETags. This setting will be ignored if any of the following are true:
There is no default setting. | DominoDisableLast ModifiedWithETAGS = value | There is no UI equivalent. |
| DominoDisablePassthru HTML Applies to: Servers | This setting allows the server to disable the recognition of passthru HTML characters, thus allowing any HTML enclosed to be treated as regular text. This means that the marked rich text is ignored and treated as it would be if it were not marked. This setting affects rendering (Web server generated output), not input. Thus, someone can still post an item that has the passthru html in it, but it won’t be interpreted as such when the Web server generates output HTML.
Having two levels of disabling passthru allows administrators to eliminate any external threat — such as passthru added by someone from the Web — but allows applications written using the Notes editor style of passthru to continue working (for example, the mail template). Setting of DominoDisablePassThruHTML does not affect if and how the notes client treats passthru html, or other ways of putting “raw” html into a document (for example, marking a form as content type html or putting a field named HTML on the document). There is no default setting. | DominoDisablePassthru HTML = value | There is no UI equivalent. |
| DominoMultiPart PostBufferSize Applies to: Servers | Specifies the number of megabytes to allocate to the memory buffer. The size of the buffer can be affected by the Notes.ini variable DSAPI_MAX_POST_DATA_BUFF_SIZE. If DSAPI_MAX_POST_DATA_BUFF_SIZE is greater than DominoMultiPartPostBufferSize, than the maximum buffer size is set to DSAPI_MAX_POST_DATA_BUFF_SIZE. By default, DSAPI_MAX_POST_DATA_BUFF_SIZE is set to 1 MB and cannot exceed 100 MB. Therefore, DominoMultiPartPostBufferSize has a 10 MB minimum and a 100 MB maximum. The default setting is 10 MB. | DominoMultiPart PostBufferSize = value | There is no UI equivalent. |
| DominoMultiPart PostBufferSize Applies to: Servers | The size of the buffer can be affected by the NOTES.INI variable DSAPI_MAX_POST_DATA_BUFF_SIZE. If DSAPI_MAX_POST_DATA_BUFF_SIZE is greater then DominoMultiPartPostBufferSize, than the maximum buffer size will be set to DSAPI_MAX_POST_DATA_BUFF_SIZE. By default, DSAPI_MAX_POST_DATA_BUFF_SIZE is set to 1 megabyte and cannot exceed 100 megabytes. Therefore, DominoMultiPartPostBufferSize has a 10 megabyte minimum and a 100 megabyte maximum. Default setting is 10 MB. | DominoMultiPart PostBufferSize = n, where n is the number of megabytes to allocate to the memory buffer | There is no UI equivalent. |
| DominoNoBanner Applies to: Servers | Web pages created with Domino display a Domino banner in source headers, as follows: <HTML> <! — Lotus-Domino Release [release number] – [date of release] on [platform] –> <HEAD> Use the DominoNoBanner setting to hide/display the banner. 0 – Displays the banner 1 (default) – Hides the banner. This option provides greater default security Disable all passthru for text marked astpassthru with the Notes editor, using Text – Pass-thru HTML, or specifying a paragraph style “HTML.” Having two levels of disabling passthru allows administrators to eliminate any external threat — such as passthru added by someone from the Web — but allows applications written using the Notes editor style of passthru to continue working (for example, the mail template). Setting of DominoDisablePassThruHTML does not affect if and how the notes client treats passthru html, or other ways of putting “raw” html into a document (for example, marking a form as content type html or putting a field named HTML on the document). There is no default setting. | DominoNoBanner = value | There is no UI equivalent. |
| DominoNoDirLinks Applies to: Servers | On a Web server, specifies whether browser users can use directory links. Options are: 0 (default) – Allow browser users to access directory links 1 – Prevent browser users from accessing directory links | DominoNoDirLinks = value | There is no UI equivalent. |
| DominoNoWebAdmin Applies to: Servers | Specifies whether or not the HTTP server task automatically creates and manages the Domino Web Administrator (webadmin.nsf) application. There is no default setting. 0 – Creates/manages the webadmin.nsf application automatically 1 – The HTTP server task does not create/manage the webadmin.nsf application | DominoNoWebAdmin = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| DominoR5IntlURL Decoding Applies to: Servers | Use DominoR5IntlURLDecoding to enable decoding of international URL strings using a proprietary encoding scheme. 0 (default) – Disables Domino 5 international URL decoding. By default, Domino 6 encodes URLs according to the IRI (International Resource Identifiers) standard and does not decode URL strings encoded by Domino 5. 1 – Enables Domino 5 international URL decoding | DominoR5IntlURL Decoding = value | There is no UI equivalent. |
| DominoValidate FramesetSRC Applies to: Servers | If this variable is set to1 and the Web Server OpenFrameSet command has a Src argument, the argument’s value is validated to insure that it designates a design note in the same database as the fraemset being opened. This prevents improper use of the Src argument to redirect browsers to arbitrary web sites (a possible security vulnerability) Note that the Src and Frame arguments are used by the autoframe feature and are not intended for general use. There is no default setting. | DominoValidate FramesetSRC = value | There is no UI equivalent. |
| DominoXURLProcess Applies to: Servers | Use DominoXURLProcess to enable a Domino Web server’s URL command parser to accept ‘!’ as an alternative query component separator. 0 (default) – Disables ‘!’ as an alternative query component separator. By default, Domino does not recognize ‘!’ as an alternative query component separator. 1 – Enables ‘!’ as an alternative query component separator | DominoXURLProcess = value | There is no UI equivalent. |
| Dont_Cache_Monitor _Formulas Applies to: Servers | When system mail rules or headlines are used on a Domino server, the server keeps in memory the list of databases affected so that when a note is updated, databases that must react to note updates can be found quickly and the action taken. By default, if the action involves a programatic check, such as a system mail rule, the code to perform that check is cached as well. On a server with many such monitors, the memory required to cache the code to perform the monitoring may be so big that normal server operations are affected. Use this variable to prevent caching of the compute objects for. This greatly reduces memory usage at a small cost in processing power. There is no default setting. | Dont_Cache_Monitor _Formulas = 1 | There is no UI equivalent. |
| Dont_Use_Remembered _Addresses Applies to: Servers | When initially connecting to a server, Domino 7 tries all the addresses for all the ports for that server until one works. To speed up subsequent server searching, Notes and Domino default to caching the last successful port and address for a server and use only the cached address for the rest of the day. This makes attempts to connect to a server that is down very fast. If an administrator plans to change the address of a server, it should be done late in the evening, since the cache is not used again the next day. This works well for servers that have only one address. However, if the server has multiple valid addresses (it can be multi-homed with multiple IPV4 addresses, or it can have both IPV6 and IPV4 addresses), and a successful address for a server is unavailable, the remaining addresses won’t be tried until the next day, when the server cache is cleared. In order to bypass the cache, and have the Domino server try all addresses for a given server, you must set this notes.ini variable. Doing so will cause slower server connection failures when servers go down, because every connection attempt will try every port and every address. 0 (default) – Domino server will use port and address from the cache 1 – Domino server will try all ports and addresses for a given server | Dont_Use_Remembered _Addresses = value | There is no UI equivalent. |
| DST Applies to: Servers and clients | Specifies that a server or workstation observe daylight saving time: 0 – Do not observe daylight saving time 1 (default) – Observe daylight saving time When you select this option, the created/modified time for documents created or modified from the second Sunday in March through the first Sunday in November are time-stamped one hour later than the server’s system time. This option lets you adjust for daylight saving time without changing the actual system time. | DST = value | On a workstation, the Daylight saving time field is on the Basics tab in the Advanced tab in the Location document; on a server, the Daylight saving time field is in the Server document. For information on additional ways to adjust the time stamp for daylight savings time, see “DST_Begin_Date,” “DST_End_Date,” and “DSTlaw.” |
| DSTlaw Applies to: Servers | Specifies when daylight saving time (DST) is observed. By default, the DST period is defined as the second Sunday in March to the first Sunday in November. (This is the period during which DST is observed in the United States.) The variables begin_month, begin_week, and begin_day define the month, week, and day, respectively, when DST begins. The variables end_month, end_week, and end_day define when DST ends. Months are 1 (January) through 12 (December); weeks are 1 through 4; days are 1 (Sunday) through 7 (Saturday). You use negative numbers to specify the weeks, where -1 is the last week of the month, -2 is the second to last week, and so on. For example, the default setting for this variable is 3 -3 1 11 -4 1 (The second Sunday in March to the first Sunday in November). | DSTlaw = begin_month, begin_week, begin_day, end_month, end_week, end_day | None. For information on additional ways to adjust the time stamp for daylight savings time, see “DST,” “DST_Begin_Date,” and “DST_End_Date.” |
| DST_Begin_Date Applies to: Servers | Specifies the date when daylight saving time begins, specified in dd/mm/year format. In most cases, this parameter is not necessary. Some regions of the world do not recognize the beginning of daylight saving time on the second Sunday in March. If your server is in a region where this is true, use this parameter to specify the exact date when DST begins. Use this setting along with DST_End_Date, which specifies when daylight saving time ends. There is no default setting, although if this setting is omitted, daylight saving time begins the first Sunday in April. | DST_Begin_Date = dd/mm/year | There is no UI equivalent. For information on additional ways to adjust the time stamp for daylight saving, see “DST,” “DST_End_Date,” and “DSTlaw.” |
| DST_End_Date Applies to: Servers | Specifies the date when daylight saving time ends, specified in dd/mm/year format. In most cases, this parameter is not necessary. Some regions of the world do not recognize the ending of daylight saving time as the last Sunday in October. If your server is in a region where this is true, use this parameter to specify the exact date when DST ends. Use this setting along with DST_Begin_Date, which specifies when daylight saving time begins. There is no default setting, although if this setting is omitted, daylight saving time ends the last Sunday in October. | DST_End_Date = dd/mm/year | There is no UI equivalent. For information on additional ways to adjust the time stamp for daylight saving, see “DST,” “DST_Begin_Date,” and “DSTlaw.” |
| Notes.ini settings: E |
| Setting | Description | Example | Comment | |
| EmptyTrash Applies to: Clients | Specifies when and how the Trash folder will be purged of documents marked for deletion. Options are: 0 (default) – Prompt the user before closing the database 1 – Always empty the Trash folder before closing the database 2 – Empty the Trash folder manually | EmptyTrash = value | UI equivalent: File – Preferences – User Preferences – Basics – Empty Trash folder | |
| Enable_ACL_Files Applies to: Servers | Specifies whether or not to enable ACL file checking on a server. ACL files are an option for protecting server directories, and contain the names of users authorized to access those directories. Servers in xSP configurations enable this feature by default. In an xSP configuration, an individual ACL file is automatically created for each individual hosted organization, to prevent users in one hosted organization from traversing a directory that belongs to another hosted organization. 0 – Disable ACL file checking (default for non-XSP configurations) 1 – Enable ACL file checking (default for xSP configurations) | Enable_ACL_Files = value | There is no UI equivalent | |
| EnableBiDiNotes Applies to: Clients | Use this variable to toggle the support for bi-directional Languages (for example Arabic or Hebrew). 0 (default) – Turns BiDirectional support off 1 – Turns BiDirectional support on | EnableBiDiNotes = value | There is no UI equivalent | |
| Enforce_Personal _Agents Applies to: Servers | Used for running agents in a transitional environment, for example a Domino 6 server and Notes 5 clients and templates. Notes 6.0 users with LotusScript rights are automatically granted personal agent rights. If this variable is enabled, users who have LotusScript rights are not granted personal agent rights unless they are explicitly listed in the Server record or if the Personal agents field is blank. . 0 (default) – do not enforce personal agents 1 – enforce personal agents | Enforce_Personal _Agents = value | There is no UI equivalent | |
| Event_Pool_Size Applies to: Servers | Use this variable to specify the amount of memory used for unprocessed events, unprocessed notifications, and event suppression. The default setting is 10 MB. The minimum setting is 5 MB and the maximum setting is 100 MB.
| Event_Pool_Size = value | There is no UI equivalent. | |
| ExtMgr_AddIns Applies to: Servers and clients | Defines the list of add-in files for the Extension Manager. Domino or Notes reads this variable on initialization and then attempts to load the specified library or libraries. For example: ExtMgr_AddIns=logdll,amgrdll In addition, you can use ExtMgr_AddIns to add one or more custom Extension Manager applications. The name of the add-in file may begin with the platform specifier character N under Windows. This character may be omitted when using the ExtMgr_AddIns setting. There is no default setting. | ExtMgr_AddIns = value1, value2, value3… | There is no UI equivalent | |
| Notes.ini settings: F | ||||
| Setting | Description | Example | Comment |
| Fault_Analyzer _Match_Percentage Applies to: Servers | Fault Analyzer is an aspect of the Automatic Diagnostic Collection that allows client and server crashes that occur at customer sites to be automatically matched against known crashes to determine if there are any matches. If the crash results from a known issue that is fixed in a release subsequent to that at the customer site, IBM/Lotus provides the optional configuration to download the upgrade kit into the Smart Upgrade database to enable the user to upgrade to resolve the problem. The formula used to determine a partial match between the two stacks depends on the average length of the stacks. If the average stack length is:
However, this can be overidden by using the Fault_Analyzer_Match_Percentage .ini variable, which applies the specified percentage to the number of matching function names in the two stacks, regardless of average stack length. There is no default setting. | Fault_Analyzer_ Match_Percentage = percentage | There is no UI equivalent |
| FaultRecoveryFromINI Applies to: Servers | Because fault recovery runs after an exception has occurred, it makes use of operating system features, rather than relying on Domino’s internal facilities. The fault-recovery system, therefore, is initialized before the Domino Directory can be read. During this initialization, fault-recovery settings are read from the NOTES.INI file, then later read from the Domino Directory and saved back to the NOTES.INI file. Any changes to the Domino Directory or the NOTES.INI file become effective when the Domino server is restarted. 0 (default)- Enable the reading of the Domino Directory and subsequent update to the NOTES.INI file 1 – Disable the reading of the Domino Directory and subsequent update to the NOTES.INI file However, this can be overidden by using the Fault_Analyzer_Match_Percentage .ini variable, which applies the specified percentage to the number of matching function names in the two stacks, regardless of average stack length. There is no default setting. | FaultRecoveryFromINI = value | There is no UI equivalent |
| FileDlgDirectory Applies to: Servers | Specifies the default directory for all file searches. If you specify this setting, Domino looks only in the specified location. There is no default setting, although if this setting is omitted, Domino searches the Domino Data directory. | FileDlgDirectory = path | There is no UI equivalent |
| Fixup_Tasks Applies to: Servers | Specifies the maximum number of Fixup tasks that are created at server startup. A Fixup task performs a consistency check on any database that requires it. Server initialization continues while Fixup tasks run. The default setting is twice the number of CPUs on the system. | Fixup_Tasks = number of tasks | There is no UI equivalent |
| FormulaTimeout Applies to: Servers | Specifies the time period, in seconds, in which a formula is allowed to run. There is no default setting. | FormulaTimeout = time in seconds | There is no UI equivalent |
| FT_Domain_ Directory_Name Applies to: Servers | Allows users and administrators to select the location and name of the domain index. By default, the domain index is located in the Domino data directory and is named FTDOMAIN.DI. If an alternate location is specified using this setting, Domino will support directory links and index relocation. There is no default setting; if this setting is omitted, the Domain Index is located in the Domino data directory. | FT_Domain_ Directory_Name = directory | There is no UI equivalent |
| FT_Domain_IdXthdsS Applies to: Servers | Specifies the number of indexing threads to use for Domain Search. Using more threads lets the Domain Catalog server index more files simultaneously, but requires more CPU utilization, and response to search queries may be slow. With fewer indexing threads, search speeds up because of greater CPU a vailability, but changes are not reflected in the index as quickly. There is no default setting, although if this setting is omitted, the default number of threads used is two per CPU. For example, a server with two CPUs uses four indexing threads by default when indexing. Do not exceed eight threads per server or you may degrade the performance of the server, even on servers with more than four CPUs. | FT_Domain_IdXthds = number of threads | There is no UI equivalent |
| FT_Index _Attachments Applies to: Servers | Specifies whether to exclude types of document attachments in the Domain Index that are not already excluded by default. A value of 1 includes these document attachments in the index, and a value of 2 excludes them. The following types of attachments are excluded from the Domain Index by default: .au, .cca, .dbd, .dll, .exe, .gif, .img, .jpg, .mp3, .mpg, .mov, .nsf, .ntf, .p7m, .p7s, .pag, .sys, .tar, .tif, .wav, .wpl, .zip. The default setting is 1. | FT_Index _Attachments = value | There is no UI equivalent |
| FT_Intl_Setting Applies to: Clients | Imposes several limitations on full text functionality to let Notes work properly with the Japanese language. When enabled (set to 1), this setting turns off stemming, makes all full text indexes case-sensitive, and ignores the setting for the stop word file. There is no default setting. | FT_Intl_Setting = language | There is no UI equivalent |
| FT_Max_Search _Results Applies to: Servers and clients | Specifies the maximum number of results (up to 2147483647) that can be retrieved at one time on a database without any index. For example: FT_Max_Search_Results = 10000 allows a single NotesDatabase or NotesDocumentCollection “FTSearch” to return up to 10000 entries. Default setting is 5000. | FT_Max_Search _Results = number of entries | There is no UI equivalent |
| FT_No_Compwintitle Applies to: Servers | Specifies whether the Domain Catalog server computes the window titles for documents that are returned by a search. XXX (default)- Computes document window titles 1 – Omits the computation of document window titles, thus conserving CPU. | FT_No_Compwintitle = value | There is no UI equivalent |
| FTG_No_Summary Applies to: Servers | Specifies whether document summaries can be displayed in search results. If you use server access lists within a domain to limit access to information, you might need to check the ACLs of databases on those servers to ensure that results are filtered. Otherwise, a search might return a result to a user who cannot access the result document. If the Domain Catalog server is on a Windows system, search results can include document summaries whereby users might be able to discern confidential information. If you are running Domino on Windows and are not sure that you can properly maintain database ACLs to prevent this, you might want to disable document summaries by using this setting in the Domain Catalog server’s NOTES.INI file. For information on Domain Search security, see the chapter “Setting Up Domain Search” in the Domino Administration Help. See also Domain Search Security. XXX (default)- Allows the display of document summaries in search results. 1 – Prevents the display of document summaries in search results. | FTG_No_Summary = value | There is no UI equivalent. |
| FT_Summ_ Default_Language Applies to: Clients | Specifies the language for a document summary in search results whenever the language in the document is not supported. Valid values (supported languages) are as follows. If a locale’s native language is not supported, use a value of NULL or english.
| FT_Summ_ Default_Language = value | There is no UI equivalent. |
| FTUpdate_Idle_Time Applies to: Servers (Domino 7 only) | Use this variable if the FT index thread is running to specify the number of seconds between full text indexes. Default value is 5. | FTUpdate_Idle_Time = number of seconds | There is no UI equivalent |
| FTUpdate_Idle _Time_MS Applies to: Servers (Domino 7 only) | Use this variable if the FT index thread is running to specify the number of milliseconds between full text indexes. Default value is 5. | FTUpdate_Idle _Time_MS = number of milliseconds | None. |
| Notes.ini settings: G |
| Setting | Description | Example | UI Eqivalent |
| GuessMIMEBodyLang Applies to: Client | Applies to Domino Web Access. Use this setting so that Domino Web Access will determine which character set group to use based on the language used in the body of e-mail messages. By default, Domino Web Access determines the character set for e-mail being sent, based on settings in the Configuration Settings document (MIME – Settings by Character Set Groups tab). When GuessMIMEBodyLang is set to 0 (default), and the “Use UTF-8 for outout” setting in Server document (Internet Protocols – Domino Web Engine tab) is turned on, Unicode is used as the character set group. When this is set to 1, Domino Web Access guesses the language of the mail body and uses that language for the character set group. | GuessMIMEBodyLang = value | There is no UI equivalent |
| Notes.ini settings: H |
| Setting | Description | Example | Comment |
| Health_Report_Purge _After_N_Days Applies to: Servers | Used for server health monitoring. N is the number of days that historical documents remain in the database. By default, historical reports are purged from the database after seven days. To override the default, add this variable to the NOTES.INI file, and specify the number of days for which historical documents remain in the database. Default setting is 7 days. | Health_Report_Purge _After_N_Days = number of days | There is no UI equivalent. |
| HidePromptFailoverInc Applies to: Clients | When the server that holds an application is no longer responding, the user is prompted to choose whether Notes should switch to a replica on another server. This INI variable allows users to suppress this prompt — the failover just occurs. 0 (default) – The user is prompted when a server is not responding. 1 – Prompts to the user are suppressed when a server is not responding. (This does not prevent Notes from failing over.) | HidePromptFailoverInc = value | There is no UI equivalent. |
| HTTPDisableMethods Applies to: Servers | If you are using the Web Configurations view instead of Internet Sites, you can disable HTTP methods by setting this variable with a value of the method name. For example, to disable the TRACE method, you would enter HTTPDisableMethods = TRACE. | HTTPDisableMethods = method name | There is no UI equivalent. |
| HTTPEnableConnector Headers Applies to: Servers | Enables the Domino HTTP task to process special headers that are added to requests by a WebSphere 4.0.3 plug-in installed on a foreign Web server. When the plug-in relays an HTTP request to the Domino back-end server, the plug-in adds headers that include information about the front-end server’s configuration and user authentication status. As a security measure, the HTTP task ignores these headers if the setting is not enabled. This prevents an attack via plug-in mimicking. 0 (default) – The Domino HTTP task does not process the special headers. 1 – The Domino HTTP task does process the special headers. | HTTPEnableConnector Headers = value | There is no UI equivalent. |
| HTTPLogUnauthorized Applies to: Servers | When set to 1, the Web Server logs Error 401 instances to the server console. These instances are generated when a user attempts to access a resource but is not authorized for it, or when a user has failed to authenticate. There is no default setting. Without this setting, Error 401 instances are not logged to the server console. With or without this setting, Error 401 instances are logged to the Web Server logs. | HTTPLogUnauthorized = value | There is no UI equivalent. |
| HTTP_PWD_CHANGE _CACHE_HOURS Applies to: Servers | Use this Notes.ini parameter to configure the length of time that the information is cached. Once the information times out from the cache, the user can only log in using the password that can be verified against the password information found by the server in the Domino Directory. By default, the cached new Internet password is honored by the HTTP server for 48 hours. | HTTP_PWD_CHANGE _CACHE_HOURS = number of hours | There is no UI equivalent. |
| Notes.ini settings: I |
| Setting | Description | Example | Comment |
| ICMNotesPort Applies to: Servers | Specifies the name of the Notes network port for TCP/IP that you are linking the Internet Cluster Manager (ICM) service with. This setting is required for a partitioned server hosting the ICM service, and for a single server hosting that service if the server has more than one Notes port for TCP/IP. There is no default setting. | ICMNotesPort = port name | There is no UI equivalent. |
| ID_Recovery_Suppress _Recovery_Msg Applies to: Clients | Prior to Domino 7, if an administrator updated ID recovery information, a memo was generated that administrators could use to notify users that their ID recovery information has been updated, and to prompt them to accept recovery information into their user ID. Administrators can use this variable to suppress the creation of this memo, as it is no longer necessary for users to manually accept recovery information. There is no default setting. This option is not enabled if the Notes.INI variable is not present in the .INI file. | ID_Recovery_Suppress _Recovery_Msg = 1 | There is no UI equivalent. |
| IM_Enable_SSO Applies to: Servers | Instant Messaging (IM) is included in the Notes client installation, and is installed when you install the Notes client. As an administrator, you can include IM in single sign-on with Lotus Notes and push this feature down to users through dynamic configuration through the NOTES.INI variable, IM_ENABLE_SSO. If this variable is set to 1, IM with single sign on is enabled; if this variable is set to 0 (zero), single sign on for IM is disabled. There is no default value. | IM_Enable_SSO = value | Setting in User Preferences dialog box |
| IMAILExactSize Applies to: Servers | Specifies that the IMAP service report the exact size of a MIME message when requested by a client. 0 (default) – The IMAP service estimates the message size 1 – The IMAP service reports the exact message size By default, the IMAP service estimates the message size. This helps improve server performance. Set this to 1 only if clients require the exact size. | IMAILExactSize = value | There is no UI equivalent. |
| IMAP_Config _Update_Interval Applies to: Servers | Specifies in minutes how frequently the IMAP server checks for configuration changes made to the Domino Directory. There is no default setting, although the update interval is 2 minutes if this setting is not included in NOTES.INI file. | IMAP_Config _Update_Interval = number of minutes | There is no UI equivalent. Certain IMAP properties are not dynamically configured and require you to shut down and restart the service before they go into effect. Also, a given IMAP session uses whatever properties were in effect at the time the session began for the duration of that session; configuration changes apply only to IMAP sessions started after the update occurs. |
| IMAP_Convert _Nodisable_Folder_Refs Applies to: Servers | Specifies whether the mail conversion utility (CONVERT) preserves folder references when updating mail files for use with the Domino 6 IMAP service. There is no default setting, although without this variable, Domino removes folder references during conversion. 0 (or variable not set) – The conversion process disables folder references. 1 – The conversion process preserves folder references. | IMAP_Convert _Nodisable_Folder_Refs = value | There is no UI equivalent. In earlier releases of Domino, the IMAP service used folder references in the mail template to retrieve IMAP folder and message data. Because the Domino 6 IMAP service does not use folder references, and preserving folder references retards IMAP performance, by default, when you run the mail conversion utility (CONVERT) to prepare mail files for IMAP use, it removes folder references from the converted mail files. Set this variable only in environments where Domino applications other than the IMAP service use folder references in mail files to track information. When this variable is set, folder references are preserved during all mail file conversions, whether performed manually from the server console, or automatically as the result of an IMAP user logging in to the IMAP service for the first time. Following conversion, the IMAP folder and message data maintained by folder references is initially synchronized with the Domino 6 IMAP information. However, as the Router delivers new messages to the mail file, folder references are not updated. |
| IMAPDisableFTI ImmedUpdate Applies to: Servers | Specifies whether or how the IMAP server will do an immediate FTI update after a new message is appended. This is required for searching for new messages immediately. By default, the IMAP server does an immediate FTI update after a new message is appended. 1 – Suppress the update request (by default, the update suppression time is 15 minutes) 2 – Disable FTI update | IMAPDisableFTI ImmedUpdate = value | There is no UI equivalent. |
| IMAPDisableMsgCache Applies to: Servers | Specifies whether the IMAP server will cache the last fetched message. By default, the IMAP server caches the last fetched message. 1 – Disable the cache | IMAPDisableMsgCache = value | There is no UI equivalent. |
| IMAPGreeting Applies to: Servers | Customizes the greeting the IMAP server sends to clients connecting over TCP/IP. There is no default, although without the setting the following greeting is used: * OK Domino IMAP4 Server V5.0 ready Mon, 10 May 1999 17:57:13 -0500 | IMAPGreeting = greeting | There is no UI equivalent. |
| IMAPNotesPort Applies to: Servers | Specifies the name of the Notes network port for TCP/IP that you are linking the IMAP service with. This setting is required for a partitioned server hosting IMAP, and for a single server hosting it if the server more than one Notes port for TCP/IP. There is no default setting. For information on binding an Internet service to an IP address, see the chapter “Setting Up the Domino Network” in the Domino Administration Help. | IMAPNotesPort = port name | There is no UI equivalent. |
| IMAPRedirect SSLGreeting Applies to: Servers | Customizes the message the IMAP server sends to clients attempting to connect over TCP/IP when the TCP/IP port is configured to Redirect to SSL. There is no default setting, although without the setting the following greeting is used: IMAP Server configured for SSL Connections only. Please reconnect using the SSL Port portnumber. | IMAPRedirect SSLGreeting = greeting | There is no UI equivalent. |
| IMAP_Session _Timeout Applies to: Servers | Specifies when the IMAP server drops idle IMAP client sessions. We recommend specifying a setting greater than ten minutes; many IMAP clients poll for new mail every ten minutes and the overhead of supporting idle session is less than the overhead required to support clients logging on and opening mailboxes. There is no default setting, although without this setting, the server drops idle sessions after 30 minutes. | IMAP_Session _Timeout = number of minutes | There is no UI equivalent. |
| IMAPShowIdleStatus Applies to: Servers | If enabled, the command “sh task” at the server console will show idle IMAP threads. By default, this is disabled. Set the variable to 1 to enable the display of idle IMAP threads. | IMAPShowIdleStatus = value | There is no UI equivalent. |
| IMAPSSLGreeting Applies to: Servers | Customizes the greeting the IMAP server sends to clients connecting over SSL. There is no default, although without the setting the following greeting is used: * OK Domino IMAP4 Server V4.6 ready Mon, 12 May 1997 17:57:13 -0500 | IMAPSSLGreeting = greeting | There is no UI equivalent. |
| IM_No_Setup Applies to: Clients | Use this variable to allow users to bypass IM Configuration. If this setting is enabled (IM_No_Setup = 1), the IM Config dialog box will not appear during new client setup or client upgrade. In addition, if this variable is enabled, any IM variables in a scripted client setup will be ignored. The default setting is 0 (disabled). | IM_No_Setup = value | There is no UI equivalent. |
| IM_USE_CANONICAL _NAME Applies to: Clients | Use this variable when your IBM Lotus Instant Messaging server is configured to lookup names in the Notes canonical hierarchical form (for example: CN= John Smith/OU= Sales/O= Acme). The default setting is 0 – Lookup names in the Notes abbreviated hierarchical form (for example: “John Smith/Sales/Acme”). | IM_USE_CANONICAL _NAME = 1 | The “Use a canonical name for instant messaging status lookup” on the Instant Messaging – General pane in the User Preferences dialog box. |
| Incoming Mail Sound NOTE: This variable name contains spaces. Applies to: Clients | Specifies the tune that plays when mail arrives. The file is a sound file, usually a WAV file. There is no default setting. | IncomDefault: None | The Play a Sound field on the Mail tab in the User Preferences dialog box. |
| INET_Authenticate _with_Secondary Applies to: Servers | Allows a Domino POP3 server to use passwords stored in directories other than the primary for services other than HTTP, such as LDAP, IMAP, and POP3. The default setting is 1. 0 – Disables this setting 1 – Enables this setting | INET_Authenticate _with_Secondary = value | There is no UI equivalent. |
| iNotes_WA_Areas Applies to: Clients | Applies to Domino Web Access clients. Use this setting to disable any combination of the six functional areas in Domino Web Access: Welcome, Mail, Calendar, To Do, Contacts, or Notebook. Each area can contain a value of 0 to disable an area, or 1 to enable an area. The format is iNotes_WA_Areas = ABCDEF where:
Example: In this example, all sections except for Mail and Contacts are disabled: iNotes_WA_Areas = 010010. The default setting is 111111 — if this setting is not used, all functional areas are enabled by default. | iNotes_WA_Areas = value | There is no UI equivalent. Added in 8.0 |
| iNotes_WA _AuthTokenName Applies to: Clients | Applies to Domino Web Access clients. Set to the name of an authentication token cookie if you are using something other than an LTPA token. The default setting is LTPAToken. | iNotes_WA _AuthTokenName = token name | There is no UI equivalent. Added in 7.0 |
| iNotes_WA _AutoUseWebmail Applies to: Clients | Applies to all Domino Web Access clients. Use this setting to bypass the browser block and automatically go to WebMail, if Domino Web Access is not supported by the browser, and Webmail is. The default setting is 0. 0 – Does not fail over to Webmail when using a browser that is not supported by Domino Web Access. 1 – Automatically invokes Webmail if Domino Web Access is not supported by the browser in use. | iNotes_WA _AutoUseWebmail = value | There is no UI equivalent. |
| iNotes_WA _ConfirmBlockedActiveX Applies to: Clients | Applies to Domino Web Access clients. If a user has not installed the latest Domino Web Access ActiveX control and if the installation is blocked by the browser, they will be asked once per session to confirm that Domino Web Access should continue to try to utilize the ActiveX control on subsequent pages (which is necessary to get the control installed). This setting provides a way to disable this prompt and for Domino Web Access to not use the Domino Web Access ActiveX control on subsequent pages (if it isn’t already installed). 0 – Suppresses confirmation box. 1 (default) – Confirmation box displays. If the confirmation box is suppressed, a user can now install the ActiveX control from the Domino Web Access Preferences dialog. | iNotes_WA _ConfirmBlocked ActiveX = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA_ ConvertPlainTextMemo Applies to: Clients | Applies to Domino Web Access clients. Use this setting to disable performing MIME-CD conversion when sending plain text messages. 0 – Disables conversion 1 (default) – MIME-CD conversion is used when sending plain text messages | iNotes_WA_ ConvertPlainTextMemo = value | There is no UI equivalent. |
| iNotes_WA _DefaultDictionary Applies to: Clients | Applies to Domino Web Access clients. This value can be set by the administrator to specify the default spell check dictionary for Domino Web Access users. When used, it should be set to one of the dictionary file names found in the Domino server’s data directory (for example, us.dic). Users can override this default by selecting a default dictionary from Domino Web Access Preferences. The default setting is None; wpdic.dic is used if no dictionary is supplied. | iNotes_WA _DefaultDictionary = dictionary name | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _DefaultFormat PlainText Applies to: Clients | Applies to Domino Web Access clients. Use this setting to set the default mail format preference to plain text. When this variable is set to 1 and the user has not set the default format in preferences, messages are automatically sent in plain text. If Domino Web Access users have indicated the user preference “prompt me when sending,” the default format on the prompt is also set to plain text. This setting does not prevent users from setting a DWA user preference for how to format mail. 0 (default) – No default text format is set. | iNotes_WA _DefaultFormat PlainText = value | There is no UI equivalent. Added in 7.0. |
| iNotes_wa_DefaultUI Applies to: Clients | Applies to Domino Web Access clients. Set this option to WebMail so that the default UI for mail files for WebHybrid applications is WebMail. The default, if this option is not set, is to use the Domino Web Access UI. | iNotes_wa_DefaultUI = webmail | There is no UI equivalent. |
| iNotes_WA _DisableActCntSecurity Applies to: Clients | Applies to Domino Web Access clients. Use this setting to disable the Active Content Filter. The Active Content Filter removes potentially harmful active content (JavaScript, Java, ActiveX) from HTML in mail messages prior to display in a browser. Active content filtering can reduce server performance because it requires a full parse of HTML content and a rewrite of the content. 0 – (or omitting this setting from the server’s NOTES.INI file; default) enables the filter. 1 – Disables the filter. | iNotes_WA _DisableActCntSecurity = value | There is no UI equivalent. |
| iNotes_WA _DisableBothFormats Applies to: Clients | All Domino Web Access clients using mail templates that are iNotes6.NTF or later. Use this setting to turn off a user’s ability to send a message in both plain text and HTML format. 0 (default) – on (the user cannot send in both formats) 1 – off | iNotes_WA _DisableBothFormats = value | There is no UI equivalent. |
| iNotes_WA_Disable ExpiresForSTLinks Applies to: Clients | Applies to Domino Web Access 8.0 clients. In 8.0, Domino Web Access returns a maximum Expires value for some static STLinks files, to more efficiently cache them on the browser. This INI setting provides a means of disabling this feature. 0 – (default) 1 – Web site rule to return expires header for files in stlnks directory is not created. | iNotes_WA_Disable ExpiresForSTLinks = value | There is no UI equivalent. |
| iNotes_WA_Disable ForceBasicAuthForAtom Applies to: Clients | Applies to Domino Web Access clients. Most external feed readers cannot handle session authentication. Domino Web Access 8.0 simulates a Web site rule that forces basic authentication for Atom Feed URLs. Use this setting to disable this automatic rule, and to force basic authentication for the Domino Web Access inbox. 0 – (default) 1 – Forces basic authentication for Domino Web Access inbox. Atom requests are not created. | iNotes_WA_Disable ForceBasicAuthForAtom = value | There is no UI equivalent. |
| iNotes_WA_Disable ForceBasicAuthForFeeds Applies to: Clients | Applies to Domino Web Access clients. Most external feed readers cannot handle session authentication. Domino Web Access 8.0 simulates a Web site rule that forces basic authentication for all feed URLs. Use this setting to disable this automatic rule, and to force basic authentication for the Domino Web Access inbox. 0 – (default) 1 – Forces basic authentication for Domino Web Access inbox. Atom and RSS requests are not created. | iNotes_WA_Disable ForceBasicAuthForFeeds = value | There is no UI equivalent. |
| iNotes_WA_Disable ForceBasicAuthForRSS Applies to: Clients | Applies to Domino Web Access clients. Most external feed readers cannot handle session authentication. Domino Web Access 8.0 simulates a Web site rule that forces basic authentication for RSS Feed URLs. Use this setting to disable this automatic rule, and to force basic authentication for the Domino Web Access inbox. 0 – (default) 1 – Forces basic authentication for Domino Web Access Inbox. RSS requests are not created. | iNotes_WA_Disable ForceBasicAuthForRSS = value | There is no UI equivalent. |
| iNotes_WA _DisableRecode MIMECharset Applies to: Clients | Applies to all Domino Web Access clients using mail templates that are iNotes6.NTF or later. By default, Domino Web Access recodes charsets for any text parts if their charset is not the default charset for the charset group. Use this setting to turn off such behavior. 0 (default) – on 1 – off | iNotes_WA _DisableRecode MIMECharset = value | There is no UI equivalent. |
| inotes_WA _DisableReuse ChildWindows Applies to: Clients | Applies to all Domino Web Access clients. By default, Domino Web Access users can set a preference to reuse child windows. If you do not want users to be able to set this preference, set this variable to 1. When set (enabled) the Reuse Child Windows user preference does not appear in the client preferences, and child windows are never reused. 0 (default) – disabled; end users can set a preference to reuse child windows 1 – enabled; the end user preference is not displayed | iNotes_WA _DisableReuse ChildWindows = value | There is no UI equivalent to disable child windows globally. You can, however, enable this feature globally, which enforces it for all users. |
| iNotes_WA _DisplayArchiveList Applies to: Clients | Applies to Domino Web Access clients. Use this setting when users may have more than one private archive policy and/or the administrator has assigned an archive policy to the user. When this variable is set to one, a dialog opens when the user clicks on the Archives button or tries to perform an archive operation on a selected document from the virtual list or from an open message. The dialog displays a list of archive criteria that the user has set and/or the archive criteria settings as assigned through an archive policy by the administrator. The user can select the desired archive on which to perform the archive operation. 0 (default) – Disables this setting 1 – Enables this setting | iNotes_WA _DisplayArchiveList = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA_Feeds Applies to: Clients | Applies to Domino Web Access clients. Use this setting to enable the advertisement and access to various Inbox feed formats for Domino Web Access mail files. Possible values are:
By default, no feeds are enabled or advertised. | iNotes_WA_Feeds = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _FeedsProtocol Applies to: Clients | Applies to Domino Web Access clients. Use this setting to have further control of the feed protocol advertised by the Inbox page. It is applicable only when iNotes_WA_FeedsSecured is disabled (set to 0). Possible values are:
By default, the feed protocol is not specified. The advertised feed uses the same protocol as the current page on which the feed advertisement occurs. | iNotes_WA _FeedsProtocol = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _FeedsSecured Applies to: Clients | Applies to Domino Web Access clients. Use this setting to enable non-HTTP (non-secure) feeds. By default only secure feeds are enabled to the mail file. This is to avoid insecure authentication occurring as part of a feed retrieval. 0 – Use this setting to allow non-secure feeds. 1 (default) – Use to allow feeds to be accessed via http rather than https. | iNotes_WA _FeedsSecured = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA_FixDoubleSpace Applies to: Clients | Applies to Domino Web Access clients. If the setting “Prefers Notes Rich Text” is set in a user’s Person document, extra lines are added during conversion to Notes Rich Text. Set this option to 1 to prevent extra lines from being added to messages during MIME-CD conversion. 0 – (default) 1 – No extra lines are inserted in MIME-CD conversion. | iNotes_WA_FixDoubleSpace = value | There is no UI equivalent. |
| iNotes_wa_GZIP _Content_Types _Excluded Applies to: Clients | Applies to all Domino Web Access clients. Use this setting to define which types of content you do not want compress. For example, to exclude XML data so that it will not be compressed: iNotes_wa_GZIP_Content_Types _Excluded = “image/*;text/xml” The default setting is “image/*;application/pdf”. | iNotes_wa_GZIP _Content_Types _Excluded = value | There is no UI equivalent. |
| iNotes_wa_GZIP _Content_Types _Included Applies to: Clients | Applies to all Domino Web Access clients. Use this setting to define which types of content you want to compress. For example, to compress all text: iNotes_wa_GZIP_Content_Types _Included = “text/*” The default setting is “text/*;application/*”. | iNotes_wa_GZIP _Content_Types _Included = value | There is no UI equivalent. |
| iNotes_wa _GZIP_Disable Applies to: Clients | Applies to all Domino Web Access clients. Use this setting to turn compression on and off. 0 (default)- Enables this setting. 1 – Disables this setting. | iNotes_wa _GZIP_Disable = value | You can also specify this setting in the Domino Web Access tab of the Configuration Settings document in the Domino Directory, under Other Settings – Compress HTTP response data. |
| iNotes_WA _LogoutRedirect Applies to: Clients | Applies to all Domino Web Access clients. Use this setting to specify a URL to redirect users to a Web page after logging out from server. The setting provides normal cache clearing with the Domino Web Access control, and clearing of browser credentials. It also allows sites that perform additional actions on a logout, such as logging out of a reverse proxy server, to specify a URL to do this additional activity. You can use this variable to return people to an initial login page. Example: iNotes_WA_LogoutRedirect = http://www.ibm.com | iNotes_WA _LogoutRedirect = URL | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _LogoutScrubType Applies to: Clients | Applies to Domino Web Access IE clients using the Domino Web Access Control. Sets the automatic cache clearing level for the Domino Web Access server.
| iNotes_WA _LogoutScrubType = value | If you enable Browser Cache Management, you can use the “Default cache scrubbing level” setting in the Configuration Settings document, Domino Web Access tab. See the section “Setting Up Domino Web Access” in the Domino Administration Help. |
| iNotes_WA _MaxRowsPerLine Applies to: Clients | Applies to Domino Web Access clients using Internet Explorer. For IE only, use this setting to specify the maximum number of lines per view entry. You can set this so that a view entry in a list view will span more than one line. For example, a long subject line in the Inbox may require three lines to show the entire content. In this case, setting the iNotes_WA_MaxRowsPerLine to 3 allows the entire subject to be shown. Note, however, that there may be some performance degradation if the value is greater than 1. Default setting is 1. | iNotes_WA _MaxRowsPerLine = number of lines | There is no UI equivalent. Added in 7.0. |
| iNotes_WA _MaxTotalAttachments SizeKB Applies to: Clients | Applies to Domino Web Access clients. Use this setting to specify the total maximum size of attachments in KB when the Domino Web Access server Configuration Settings document field Domino Web Access ActiveX file attachment utility is enabled. For example, to limit the combined size of attachments to 5000KB, use the following setting: <code>iNotes_WA_MaxTotalAttachmentsSizeKB = 5000</code>. Exceptions: Imbedded graphics (inline) are not checked by this setting. The default setting is 0 (no limit). | iNotes_WA _MaxTotalAttachments SizeKB = attachment size in KB | There is no UI equivalent. |
| iNotes_WA _MessageMarkingPrefs Applies to: Clients | Applies to Domino Web Access clients. Use this setting to enable the Mail – Message Marking user preference in Domino Web Access, so that users can set a user preference to display icons in Mail views that indicate whether they were the only recipient, or one of many. For mail sent to the user’s Notes-style address, these icons indicate whether the user’s name is the only name in the To field, whether it is listed with others in the To field, or whether it is in the cc field. 0 – (default) Domino Web Access users will not be able to set message marking preferences, nor will they be able to modify message marking preferences set in the Notes client. 1 – Domino Web Access users will be able to set message marking preferences, and will they be able to modify message marking preferences set in the Notes client. If users previously set this feature in the IBM Lotus Notes client, the icons also display in Domino Web Access whether this setting is enabled or not. However, this setting must be enabled to allow users to set or modify this setting from Domino Web Access user preferences. | iNotes_WA _MessageMarkingPrefs = value | There is no UI equivalent. |
| iNotes_WA _NameLookupMax NumMatch Applies to: Clients | Applies to Domino Web Access clients. Use this setting to specify the maximum number of names to return on name lookups. Reduce the number to improve server performance. Default setting is 200. | iNotes_WA _NameLookupMax NumMatch = value | There is no UI equivalent. |
| iNotes_WA _NamePickerSearch AccentInsensitive Applies to: Clients | Applies to Domino Web Access clients. In Domino Web Access, search in the Name Picker is accent (diacritical mark) insensitive. That is, search recognizes Muller and MÜller as the same name. You can set this variable to make search accent sensitive, so that search will recognize Muller and MÜller as two different names. 0 – Search is accent sensitive. 1 (default) – Search ignores accent marks. | iNotes_WA _NamePickerSearch AccentInsensitive = <td>value</td> | There is no UI equivalent. In previous releases, the default behavior of the Name Picker was sensitive, with a default value of 0. If you set this variable previously, you may need to change the value. Added in 7.0. |
| iNotes_WA_NoVert LineReplyForward Applies to: Clients | Applies to Domino Web Access clients.Set this option to 1 to prevent the addition of vertical lines in front of history text in messages when forwarding/replying with history. 0 (default) – Vertical lines are added. 1 – No vertical lines are added. | iNotes_WA_NoVert LineReplyForward = value | There is no UI equivalent. |
| iNotes_WA _NoWebmail Applies to: Clients | Applies to Domino Web Access clients. Prevents Domino Web Access from offering a choice to fall back to Webmail when the browser is not supported. 0 (default) – Allows Domino Web Access to invoke Webmail when using an unsupported browser. 1 – Prevents fail over to Webmail. | iNotes_WA _NoWebmail = value | There is no UI equivalent. |
| iNotes_WA_Online MeetingProtocol Applies to: Clients | Applies to Domino Web Access clients.Use this setting to switch the protocol (http: or https:) for the online meeting place URL.
| iNotes_WA_Online MeetingProtocol = value | There is no UI equivalent. |
| iNotes_WA _OpenElementNoStore Applies to: Clients | Applies to Domino Web Access clients. Enabled by default or if no variable is present, this setting prevents documents (attachments and images) in a Domino Web Access user’s mail file from being left behind in the browser’s cache, even if the user fails to logout. You can set this value to 0 to disable it. 0 – Disabled (attachments and images may be left behind in the browser’s cache if user does not logout) 1 (default) – Enabled (documents are not cached) | iNotes_WA _OpenElementNoStore = value | There is no UI equivalent. |
| iNotes_WA _PortalLogout Applies to: Clients | Applies to Domino Web Access IE clients using the Domino Web Access Control. Set to 1 to offer the logout option on portals. 0 (default) – Disables this setting. 1 – Enables this setting. | iNotes_WA _PortalLogout = value | There is no UI equivalent. |
| iNotes_WA _PortalOffline Applies to: Clients | Applies to Domino Web Access IE clients using the Domino Web Access Control. In a portal, users must be able to go offline to archive locally. Set to 1 to inlcude the offline and archive options in portals. 0 (default) – Offline and Archive options do not display. 1 – Offline and Archive options are included in a portal. | iNotes_WA _PortalOffline = value | There is no UI equivalent. |
| iNotes_WA _PortalSkipEnd IESession Applies to: Clients | Applies to Domino Web Access IE clients using the Domino Web Access Control. Use this setting to avoid logging out of other web applications when logging out of Domino Web Access during a portal session (when using &ui=portal session). 0 (default) – Disables this setting. 1 – Enables this setting. | iNotes_WA _PortalSkipEnd IESession = value | There is no UI equivalent. |
| iNotes_WA _PreferWebEngine CacheControl Applies to: Clients | Applies to Domino Web Access clients. Domino Web Access now sets Cache-Control response headers that prevent the Domino Web Engine from remapping them in certain scenarios. Previously, the default Domino Web Engine logic did not allow returning a Cache-Control response header for HTTP 1.0 requests, which lead to content being left in the browser cache unintentionally. Use this setting to revert to the prior behavior. 0 (default) – Disables this setting 1 – Enables this setting | iNotes_WA _PreferWebEngine CacheControl = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _PreferXMLHttp Request Applies to: Clients | Applies to Domino Web Access clients. Set this variable to 1 to use Microsoft.XMLHTTP ActiveX object instead of load() method of <xml> tag where possible. 0 (default) – Disables this setting 1 – Enables this setting | iNotes_WA _PreferXMLHttp Request = value | There is no UI equivalent. Added in 8.0. |
| iNotes_WA _PrintUserStyleSheet Applies to: Clients | Applies to Domino Web Access. Set this variable to 1, so that you can specify a special user-defined style sheet to control font sizes when printing. For example, in some Linux environments if the display resolution is set lower than default (by editing XF86Config file), text prints larger than expected. When that happens, you can adjust font size using a user-defined style sheet. The style sheet is a file resource named “userPrint.css” in FORMS7.nsf. You can use the style rules in userPrint.css as a template and adjust the style by editing it. To l earn how you can control styles, see the comments in userPrint.css. To edit the style sheet, open FORMS7.nsf in Domino Designer and locate the file in Shared Resources – Files. 0 (default) – Disabled 1 – Enabled. You can specify a user style sheet | iNotes_WA _PrintUserStyleSheet = value | There is no UI equivalent. Added in 7.0. |
| iNotes_WA _QueryAgents Applies to: Clients | Applies to Domino Web Access. Use this setting to invoke QueryOpen and QuerySave agents when accessing Domino Web Access documents. When this setting is enabled and a $$QuerySaveAgent or $$QueryOpenAgent value is encountered while opening or saving a note, the agent pecified within this item is invoked. The agent must reside within the mail database, not the Forms file. 0 (default) – Disabled. Web query agents are not invoked 1 – Enable Web query agents | iNotes_WA _Query Agents = value | There is no UI equivalent. Added in 7.0. |
| iNotes_WA _SametimeName Format Applies to: Clients | Applies to Domino Web Access clients using templates that are iNotes6.NTF or later. Allows you to adjust the format of the name that is passed to Sametime for login, for awareness checking, and whether to pass RFC821 names. The value can contain up to 4 numeric digits in sequence. The default setting is 011.If you set this variable, you override the Configuration Settings document setting “Directory type used by IBM Lotus Sametime server.” Example: iNotes_WA_SametimeNameFormat = 1011 where the following values apply: First digit (left most) — controls the format of the name passed to Sametime routines that prepare links and start chat sessions: 0 – Use abbreviated canonical format (for example, Joe User/Acme) [the default] 1 – Use full canonical format (for example, CN=Joe User/O=Acme) 2 – Use canonical format but use a comma ( , ) as a separator for the name components (for example, CN=Joe User,O=Acme) 3 – Use only the common name (for example, Joe User) 2nd digit — controls whether RFC821 addresses (for example, Joe User@acme.com) should be sent to Sametime: 3rd digit — controls the format of the name passed to Sametime login routines: | iNotes_WA _SametimeName Format = value | In Domino 7 or later, you can use the setting “Directory type used by IBM Lotus Sametime server” in the Configuration Settings document, Domino Web Access tab. However, using this NOTES.INI variable overrides the Configuration Settings document setting. |
| iNotes_WA _SametimeProtocol Applies to: Clients | Applies to all Domino Web Access clients using mail templates that are iNotes6.NTF or later. Set the value to https: or http: if you do not want to use the current Web page’s protocol to access the Instant Messaging server. For example, if the current protocol is http and you want to force the use of https: iNotes_WA_SametimeProtocol = https. The default setting is the current Web page protocol. | iNotes_WA _SametimeProtocol = value | There is no UI equivalent. |
| iNotes_WA_Sametime RemoteToken Applies to: Clients | Applies to Domino Web Access clients. Use this setting when the Domino Web Access server is used in conjunction with a reverse proxy server (such as Tivoli Access Manager) where LtpaToken authentication is not being used. In such scenarios, Domino Web Access must query the server for the authentication Token (as it is not available at the client). When set, this option queries the server for the token name.
| iNotes_WA_Sametime RemoteToken = tokenname | There is no UI equivalent. |
| iNotes_wa _SecMailPreferNotes Applies to: Clients | Applies to all Domino Web Access clients. By default, Domino Web Access uses S/MIME sign and encryption when both Notes and S/MIME sign and encryption are possible. This could cause problems in a mixed environment that includes both Domino 7 and pre-Domino 7 servers. Pre-Domino 7 servers do not support S/MIME, so messages sent S/MIME signed or encrypted could not be verified or decrypted. Use this setting to turn on Notes sign and encryption when both S/MIME and Notes sign and encryption are possible. 0 – off (default – When both Notes and S/MIME sign and encryption are possible, use S/MIME sign and encryption) 1 – on (When both Notes and S/MIME sign and encryption are possible, use Notes sign/encryption) | iNotes_wa _SecMailPreferNotes = value | There is no UI equivalent. This setting is not supported offline. |
| iNotes_WA _SkipEndIESession Applies to: Clients | Applies to Domino Web Access IE clients using the Domino Web Access Control. Use this setting to avoid issues with other open Web pages being negatively impacted by a Domino Web Access logout. When the Domino Web Access control is in use, Domino Web Access makes a call to end the IE session as part of a Domino Web Access logout. This clears any login credentials stored in IE memory and in memory cookies being used within this IE process (or any child processes spawned from this process). It is preferable for users to log in to other web sites through a separate instance of IE, instead of using this setting. Users can start the additional instances from the desktop, the quick launch toolbar, or the start menu. When users start additional instances in this way, logging out of Domino Web Access does impact the other IE windows. 0 (default) – Disables this setting. 1 – Enables this setting. | iNotes_WA _SkipEndIESession = value | There is no UI equivalent. |
| iNotes_WA _UseInternetAddr ForXsp Applies to: Clients | Applies to Domino Web Access clients. Use this setting in an xSP server environment, to force the From and Principal fields to use the “Internet address” format when sending email. 0 (default) – off 1 – on | iNotes_WA _UseInternetAddr ForXsp = value | There is no UI equivalent. Added in 7.0 and 6.5.4. |
| iNotes_WA_UseST ServerForOnlineMeeting Applies to: Clients | Applies to Domino Web Access clients. Use this setting to specify the online meeting server when the Sametime server is accessible only through reverse proxy. 0 (default) – Use Sametime server setting that is specified in the Online Meeting Place resource when the meeting is scheduled. 1 – Use the Sametime server setting in Domino Web Access tab of the Configuration Settings document for the online meeting place server. | iNotes_WA_UseST ServerForOnlineMeeting = value | There is no UI equivalent. |
| InstallType Applies to: Clients | Applies to workstations. Smart Upgrade can determine whether to install a Notes client only, or all clients — Notes, Designer, and Administrator — for each user. The installer sets the value of the InstallType = setting in the NOTES.INI file each time a Notes client or All client install/upgrade is performed. Smart Upgrade compares the Install Type value in the Smart Upgrade kit document to the InstallType field in the NOTES.INI file and installs the update kit that matches the Install Type specified in the NOTES.INI file: 2 – All client install (including Designer and Administrator) 6 – Notes client only There is no default setting. | InstallType = value | There is no UI equivalent. |
| Notes.ini settings: J |
| Setting | Description | Example | Comment |
| JavaEnableJIT Applies to: Servers | Enabled by default. To disable the JIT, specify the JavaEnableJIT variable and set its value to 0. Default setting is 1. Caution: JITs can be unstable and can lead to unexpected crashes. | JavaEnableJIT = value | There is no UI equivalent. |
| JavaJITName Applies to: Servers | Enables the specified JIT. You must provide the named JIT or an error is reported by the Java Virtual Machine (JVM), although execution continues without the named JIT. Use the JavaJITName setting to load a JIT other than the default JIT (if one is provided). JITs can be unstable and lead to unexpected crashes. There is no default. | JavaJITName = name | There is no UI equivalent. |
| JavaMaxHeapSize Applies to: Servers | Specifies the maximum — not initial — size the Java heap can reach. The Java Virtual Machine (JVM) starts out at 16MB of heap space and most of it is uncommitted. If the JVM needs more heap than it currently has, it will expand the heap in increments but will not exceed the maximum. Exceptions such as “java.lang.OutOfMemoryError” indicate that a heap has reached its maximum size. You can specify the number of bytes directly or use the suffix “MB” to indicate megabytes, for example, specifying “64MB” is the same as specifying “67108864.” The default setting is 64 MB. | JavaMaxHeapSize = number of bytes | There is no UI equivalent. |
| JavaMinHeapSize Applies to: Servers | Specifies the initial size of the Java heap at Java Virtual Machine (JVM) startup. If the JVM needs more heap than it currently has, it will expand the heap in increments but will not exceed the maximum. You can specify the number of bytes directly or use the suffix “MB” to indicate megabytes, for example, specifying “16MB” is the same as specifying “16777216.” Default is 16 MB. | JavaMinHeapSize = number of bytes | There is no UI equivalent. |
| JavaNoAsyncGC Applies to: Servers | Prevents the Java Virtual Machine (JVM) from running the garbage collection (GC) mechanism in a separate background thread. Specify 1 as the JavaNoAsyncGC value to debug internal JVM problems. Default setting is 0. | JavaNoAsyncGC = value | There is no UI equivalent. |
| JavaNoClassGC Applies to: Servers | Prevents the garbage collection (GC) mechanism of classes, which protects static fields. Specify 1 as the value to enable the JavaNoClassGC setting. Default setting is 0. | JavaNoClassGC = value | There is no UI equivalent. |
| JavaStackSize Applies to: Servers | Specifies the size of each Java thread’s execution stack. You may need to increase the default number of bytes if you need deeply-nested call stacks, but otherwise you should not need to change the default. Default setting is 409600. | JavaStackSize = number of bytes | There is no UI equivalent. |
| JavaUserClasses Applies to: Servers | Allows code-sharing across agents and applets. The value list is a list of directories, JAR files, or ZIP files that are added to the Java Virtual Machine’s internal classpath so that classes can be found via the system loader (rather than via attachment to the agent or applet). Note that this doesn’t replicate and requires access to the file system on the server. Use a semicolon (;) to separate list items for Win32 and OS/2 systems and use a colon (:) to separate list items for UNIX systems; for example, a valid list for Win32 is: <code>c:\classes; d:\appxyz\stuff.jar</code>. There is no default setting. | JavaUserClasses = list | There is no UI equivalent. |
| JavaVerbose Applies to: Servers | Enables the verbose setting of the Java Virtual Machine (JVM), which causes the JVM to issue many messages while it runs. Specify 1 as the JavaVerbose value to troubleshoot runtime problems. Default setting is 0. | JavaVerbose = value | There is no UI equivalent. |
| JavaVerboseGC Applies to: Servers | Enables the verbose setting of the garbage collection (GC) mechanism in Java Virtual Machine (JVM), which causes the JVM to issue many messages about memory usage as GC runs. Specify 1 as the JavaVerboseGC value to enable this setting. Default value is 0. | JavaVerboseGC = value | There is no UI equivalent. |
| JournalRecipients Applies to: Servers | Allows for the capture of expanded recipient names . 0 (default) — Disabled 1 -Enabled | JournalRecipients = value | There is no UI equivalent. |
| Notes.ini settings: K |
| Setting | Description | Syntax | Comment |
| KeyFileName Applies to: Servers and clients | Specifies the location of the server ID or the user ID file. This setting lets an administrator use one ID to run the server. For example:
The default setting is the ID for the administrator that you specify when you set up the server. See ServerKeyFileName for information on specifying a server ID file for a machine that runs both the Notes workstation and Domino server programs. | KeyFileName = path | There is no UI equivalent. |
| KitType Applies to: Servers and clients | Specifies which program you are running: 1 – Workstation 2 – Server The default value is specified during the Install program. You can install the workstation, the server, or both the workstation and server. The value when you install the server and workstation on the same machine is 2. | KitType = value | There is no UI equivalent. |
| Notes.ini settings: L |
| Setting | Description | Syntax | Comment |
| LANnumber Applies to: Servers and clients | Specifies information about network ports on servers and workstations. For example:
The LAN0 port is configured for an SPX network connection. The LAN1 port is configured for a NetBIOS connection and contains additional port setup information. Exclude the _ or i prefix and the .DLL extension from the port driver name. The default is specified during the Install program. | LANnumber = port_driver, unit_ID, not_used, buffer_size | On a workstation, File – Preferences – User Preferences – Ports; on a server, the Ports tab in the Server document. |
| LDAPBatchAdds Applies to: Servers | Specifies which views in the Domino Directory the LDAP service updates after processing an LDAP write operation: 0 – After a write operation the LDAP service updates all the Domino Directory views it uses 1 – After a write operation the LDAP service updates only the ($LDAPRDNHier) view and waits for the Update task to update the other views it uses There is no default setting, although without this setting, after processing an LDAP write operation the LDAP service updates all the views it uses. | LDAPBatchAdds = value | There is no UI equivalent. Use LDAPBatchAdds = 1 before doing batch LDAP adds of 100 entries or more so that so that the additions are processed more quickly. When the LDAP adds are complete, immediately remove the setting or change it back to LDAPBatchAdds = 0. Failure to immediately remove or change this setting back to 0 after completing the batch processing will cause subsequent LDAP operations to be unreliable. |
| LDAPConfigUpdate Interval Applies to: Servers | Specifies the interval at which the LDAP service detects and puts into effect changes to these configuration settings:
You must always restart the LDAP task to put into effect changes to these settings:
Without this setting the interval is three minutes. | LDAPConfigUpdate Interval = number of minutes | There is no UI equivalent. |
| LDAPGroupMembership Applies to: Servers | The LDAP service always searches Domino groups specified as “Multi-purpose,” “Access Control List only,” “Servers only,” or “Deny List only” groups because it can do so quickly. However because searches of Domino groups specified as “Mail only” groups or of groups that do not have a value for the GroupType attribute can be slow, by default the LDAP service does not always search these types of groups. The LDAP service does not search these types of groups if a search query meets all of the following criteria, indicating a query that is typically used for authentication: A search query uses the equality filter objectclass=value, where value is one of these object classes: groupOfNames, groupOfUniqueNames, dominoGroup, or group. A search query uses an equality filter with one of these attributes: member, uniqueMember, or members. The two filters above are concatenated using the AND operator. For example, by default the LDAP service does not search Domino “Mail only” groups and groups that do not have values for the GroupType attribute if search queries such as these are specified: (&(objectclass=dominoGroup) (member=cn=jack brown,o=acme)) (|(&(objectclass=groupOfUniqueNames) (uniqueMember=cn=jack brown,o=acme)) (&(objectclass=groupOfNames) (member=cn=jack brown,o=acme))) However, by default the LDAP service does search these groups if search queries such as these are specified: (&(objectclass=dominoGroup)(member=*br*)) (member=cn=jack brown,o=acme)(|(&(objectclass=dominoGroup)(member=cn=jack brown,o=acme))(cn=*groupname*)) To change the LDAP service default behavior for group searches, specify one of these values for this setting:1 – Always search all groups that meet specified search criteria. If you choose this setting, full-text indexing the directory is recommended to improve the speed of searches of Domino “Mail only” groups and groups that do not use the GroupType attribute. 2 – Never search Domino “Mail only” groups or groups that do not use the GroupType attribute. There is no default setting. | LDAPGroupMembership = value | There is no UI equivalent. |
| LDAPIdleSession ExtendedTimeout Applies to: Servers | Specify the idle session timeout period for clients specified by the Notes.INI variable LDAPIdleSessionExtendedTimeoutClients. This variable will be ignored if LDAPIdleSessionExtendedTimeoutClients is not set. The default is 120 minutes, if LDAPIdleSessionExtendedTimeoutClients is set but this variable is not. | LDAPIdleSession ExtendedTimeout = time in minutes | There is no UI equivalent. |
| LDAPIdleSessionExtended TimeoutClients Applies to: Servers | Specify a comma-delimited list of clients – expressed as IP address or DNS names – to which the timeout period specified by LDAPIdleSessionExtendedTimeout applies. There is no default. | LDAPIdleSessionExtended TimeoutClients = list of clients | There is no UI equivalent. |
| LDAPIdleSessionTimeout Applies to: Servers | Allows the system administrator to set the default idle timeout for LDAP sessions. The timeout occurs when a client hasn’t sent a packet during the time specified by this variable. The default is 30 minutes, if this .INI variable is not set. | LDAPIdleSessionTimeout = time in minutes | There is no UI equivalent. |
| LDAPNotesPort Applies to: Servers | Specifies the name of the Notes network port for TCP/IP that you are linking the LDAP service with. This setting is required for a partitioned server hosting LDAP, and for a single server hosting it if the server more than one Notes port for TCP/IP. There is no default. For information on binding an Internet service to an IP address, see the Domino Adminstrator Help. | LDAPNotesPort = port name | There is no UI equivalent. |
| LDAPPre55Outlook Applies to: Servers and clients | If set to LDAPPre55Outlook = 1, if the LDAP service receives a search query that specifies country (c=xx) as a search base, it converts the search base to root (“”). This setting is designed for use with pre-5.5 Microsoft Outlook Express clients which, when users don’t specify a search, automatically use the country associated with the software version as a search base. Since it’s likely that pre-5.5 users who don’t specify a search base intend a root search rather than one using the client-supplied country search base, use this setting if the clients that use the LDAP service are primarily pre-5.5 Microsoft Outlook Express clients. There is no default. | LDAPPre55Outlook = value | There is no UI equivalent. |
| LDAPName_Update _Suppress_Time Applies to: Servers | Specifies the maximum length of time that that the results of a query to an LDAP directory, which has been marked for group expansion, will be cached for use in building nameslists. Upon expiration, the cached entries will be considered invalid and the creation of a nameslist will result in queries being sent to the LDAP directory. This addresses the situation, prior to Domino 6, in which the cache did not detect changes that occurred in LDAP directories that had been marked for group expansion, thus serving up stale data which had been cached from those directories indefinitely. 0 – Updates to the LDAP directory are not detected and the group cache is flushed based only on updates to those Domino Directory(ies) that are enabled for group expansion. integer – This value is interpreted as the lifetime of information from remote LDAP directories in 1/100ths of a second. Thus, if this value is set to 6000 then the information from the LDAP server will only be considered valid for 1 minute. If the LDAP server was marked for group expansion in the DA database this would mean that group cache would be considered stale after one minute. Settings below 6000 (3000 if the LDAP server task is running) are probably not useful as these servers are subject to a 1 minute (30 seconds if the LDAP server task is running) threshold and should be avoided. The default setting is 60 minutes [60*60*100 (360000)]. | LDAPName_Update _Suppress_Time = value | There is no UI equivalent. |
| Location Applies to: Clients | Identifies the user’s current location. There is no default. | Location = location_name | UI equivalent: File – Mobile – Choose Current Location. |
| Log Applies to: Servers and clients | Specifies the contents of the log file and controls other logging actions:
For example: | Log = logfilename, log_option, not_used, days, size | There is no UI equivalent. |
| Log_AgentManager Applies to: Servers | Specifies whether or not the start of agent execution is recorded in the log file and shown on the server console: 0 – Do not log agent execution events 1 – Log agent execution events (partially and completely successful) 2 – Log agent execution events (completely successful only) There is no default setting. | Log_AgentManager = value | UI equivalent: None, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Log_Authentication Applies to: Servers and clients | Specifies whether or not authentication logging is enabled on the server. To enable authentication logging, set Log_Authentication to a value of 1. For example, if you specify the following NOTES.INI settings: Log_Authentication=1 (to enable logging)Debug_Console=1 (to write output to the console window)Debug_Outfile=c:\debug\debug.txt (to write output to the specified text file)This is sample output from client NOTES.INI: Authenticate: CN=CLEVES01/OU= Cleveland/OU=A/O=Acme T:64 E:1: S:64:22 A:4:1 L:N:N:N Authenticate: CN=ACCOUNT/OU= Memphis/OU=A/O=Acme T:64 E:1: S:64:22 A:4:1 L:N:I:N Authenticate: CN=CLEVES02/OU= Cleveland/OU=A/O=Acme T:128 E:1: S:128:22 A:4:1 L:N:N:N and this is sample output from server NOTES.INI: Authenticate: CN=Jane Ochoa/O=Acme T:128 E:1: S:128:22 A:4:1 L:N:N:N You can use the following table to interpret the output. Field Description T Ticket Width Examples of values are 64 and 128. E Encryption Bit Examples of values are 1 (Encrypted), 0 (Not encrypted), and 1:e (Escrow for International). S Encryption Strength The first value is the key length; for example, 128, 64, and 40. The second value is the algorithm; for example, 22 (RC4) and 2F (RC2). A Algorithm Examples of values are 4:1 (RC4) and 2:0 (RC2). L License Info The first value applies to the local ID (that is, local client or server); the second value applies to the remote ID (that is, the server); and the third value applies to the version of local software. Examples of values are N (North American/Global) and I (International). Default: None | Log_Authentication = value | There is no UI equivalent. |
| Log_Catalog Applies to: Servers | Controls catalog output. If Log_Catalog is not set, the default value 0 is used. 0 (default) – No log or console output is generated. 1 – All output is added to the log or displayed on the console. | Log_Catalog = value | There is no UI equivalent. |
| Log_Connections Applies to: Servers | Specifies whether or not connection logging is enabled on the server. When connection logging is enabled, the server console displays the Notes network port, the network address of the requesting system, and the network address of the destination server. 0 – Do not log connections 1 – Log connections There is no default setting. | Log_Connections = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Log_Console Applies to: Servers | Security administrators can use this setting to enforce the logging of server console command output, which can otherwise be prevented if the command is prefixed with an exclamation point (!). 0 – Console command logging turned off 1 – Console command output logged, unless it’s prefixed with an exclamation point 2 – Console command output logged, whether prefixed with the “!” or not There is no default setting, but in the absence of this setting console command output is logged unless it’s prefixed with an exclamation point. | Log_Console = value | There is no UI equivalent. |
| Log_DirCat Applies to: Servers | Use this setting to display additional information to the server console when the Dircat task runs. This includes when the task starts and finishes, what directory its aggregating, the domain name of the directory, and how many entries were processed. For more verbose information, including the names of all the entries that are processed, you can set log_dircat=3. However, this setting may slow performance and fill up the server log file, so its use is not recommended | Log_DirCat = value | There is no UI equivalent. |
| LogFile_Dir Applies to: Servers | Specifies the directory for the Console Log file (CONSOLE.LOG, by default). If both this setting and the Debug_Outfile setting exist and Debug_Outfile contains a fully qualified path name, then LogFile_Dir is not used. If neither Debug_Outfile or LogFile_Dir exist, then the default path \DATADIRECTORY\ IBM_TECHNICAL_SUPPORT is used. There is no default setting. | LogFile_Dir = directory name | There is no UI equivalent. |
| Log_Replication Applies to: Servers | Specifies the level of logging of replication events performed by the current server: 0 – Do not log replication events 1 – Log that a database is replicating 2 – Log information about each replicated database 3 – Log information about each replicated document (both design and data documents) 4 – Log information about each replicated field 5 – Log summary information about replication events There is no default setting. | Log_Replication = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Log_Sessions Applies to: Servers | Specifies whether individual sessions are recorded in the log file and displayed on the console: 0 – Do not log individual sessions 1 – Log individual sessions There is no default setting. | Log_Sessions = value | The UI equivalent for this setting is the Log All Client Events setting, an advanced server setup option. You can also specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| LogStatusBar Applies to: Clients | Applies to Notes Client and Domino Designer. Controls the default behavior for logging client status bar messages. For use by administrators and developers for debug purposes. To view the logged messages, open the file, LOG.NSF, and then click the Miscellaneous Events view. Status bar messages are appended with “Status Msg.” To write the status bar messages to an external file, use the NOTES.INI setting Debug_Outfile = path to file along with this NOTES.INI setting. Use the following values to set this variable: 0 (default) – do not log status bar messages (default); 1 – log status bar messages to log.nsf. Messages will still be displayed on the status bar. | LogStatusBar = value | There is no UI equivalent. |
| Log_Tasks Applies to: Servers | Specifies whether the current status of server tasks is recorded in the log file and displayed on the console: 0 – Do not send status information 1 – Send the status of server tasks to the log file and to the console There is no default setting. | Log_Tasks = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Log_Update Applies to: Servers | Specifies the level of detail of Indexer, Update and Updall events displayed at the server console and in the log file. The following values apply to Indexer: 0 (default) – Records when the Indexer starts and shuts down. 1 – Records when the Indexer starts and shuts down and when the Indexer updates views and full text indexes for specific databases. 2 – Records when the Indexer starts and shuts down and when the Indexer updates views and full text indexes for specific databases. Also records the names of views the Indexer is updating. | Log_Update = value | There is no UI equivalent. |
| Log_View_Events Applies to: Servers | Specifies whether messages generated when views are rebuilt are recorded in the log file: 0 – Do not log messages when views are rebuilt 1 – Log messages when views are rebuilt Removing this setting from the NOTES.INI file also disables logging of these messages. There is no default setting. | Log_View_Events = value | There is no UI equivalent. |
| Notes.ini settings: M |
| Setting | Description | Example | Comment |
| MailBoxDisable TXNLogging Applies to: Servers | Allows mail.boxes created by server during startup to be created with transaction logging disabled when set to any non-zero value. The default setting is 0 (transaction logging is enabled for mail.boxes created at server startup). | MailBoxDisable TXNLogging = value | There is no UI equivalent. |
| MailCharSet Applies to: Servers | Specifies the character set a POP3 server uses when downloading mail messages to a POP3 client. Value corresponds to a character set listed in the side file, “MailCharSet values.” If you do not use this setting, the POP3 server looks for a WWWDSP_Codepage value, if this setting is added. (WWWDSP_Codepage controls the character set used by the Web Navigator and accepts the same values as MailCharSet.) Default: None, although if this setting is omitted and there is no WWWDSP_Codepage setting, the POP3 server uses the us-ascii character set. | MailCharSet = value | There is no UI equivalent. |
| MailCompactDisabled Applies to: Servers | Enables or disables the routine compacting of the server’s MAIL.BOX. Without this setting in the NOTES.INI file, MAIL.BOX is compacted routinely when the Compact server task runs: 0 – Enables compacting of MAIL.BOX 1 – Disables compacting of MAIL.BOX There is no default setting. | MailCompactDisabled = value | There is no UI equivalent. |
| MailCompactHour Applies to: Servers | Use this setting to specify the time at which the router should perform mailbox compaction. Value is based on a 24-hour clock. For example, MailCompactHour=22 will cause compaction to initiate around 10 pm. There is no default setting. In the absence of the setting, the router will perform mailbox compaction at 4 am. | MailCompactHour = value | There is no UI equivalent. |
| MailConvertMIME onTransfer Applies to: Servers | Enables or disables MIME message conversion on the router. This can help minimize conversion overhead on the server running the SMTP listener task. 0 (default) – Router does not perform conversions for MIME messages 1 – Router performs conversions for MIME messages | MailConvertMIME onTransfer = value | There is no UI equivalent. |
| Mail_Disable_Implicit _Sender_Key Applies to: Clients | Determines whether to encrypt an encrypted message with the sender’s public key: 0 (default) – Does not encrypt the encrypted message with the sender’s public key 1 – Encrypt the encrypted message with the sender’s public key | Mail_Disable_Implicit _Sender_Key = value | There is no UI equivalent. |
| MailDisablePriority Applies to: Servers | When set to 1, the MailDisablePriority setting causes the Mail Router to ignore the delivery priority of mail messages. This causes all messages to be delivered with normal priority. If this parameter is set to 0, mail routes according to the parameter determined by the sender. There is no default setting. | MailDisablePriority = value | There is no UI equivalent. |
| MailLogToEventsOnly Applies to: Servers and clients | Use this variable to increase performance for logging mail event messages: 0 (default) – Enables logging of mail event messages to the Domino console. 1 -Disables logging of mail event messages to the Domino console. | MailLogToEventsOnly = value | There is no UI equivalent. |
| Mail_Log_To _MiscEvents Applies to: Servers and clients | Determines whether all mail event messages are displayed in the Miscellaneous Events view of the log file: 0 – The router determines whether to log messages to the Mail Events view, the Miscellaneous Events view, or to both views. This is also true if this variable is not defined. 1 – The router ensures that all messages are logged to the Miscellaneous Events view. If a message is typically logged only to the Mail Events view, it would now be logged to both the Miscellaneous Events view and the Mail Events view. To prevent logging to the Domino Console, the NOTES.INI variable MailLogToEventsOnly can be set to a value of 1. There is no NOTES.INI setting to prevent logging to the Miscellaneous Events view. There is no default setting, although if this setting is omitted, mail events are not displayed in the Miscellaneous Events view. For information on the variable MailLogToEventsOnly, see the listing for MailLogToEventsOnly. | Mail_Log_To _MiscEvents = value | There is no UI equivalent. |
| MailServer Applies to: Servers and clients | Specifies the server where the user’s mail file resides. There is no default setting. | MailServer = server | UI equivalent: The Mail Server field in the Mail tab of the Person document in the Domino Directory. |
| MailSetup Applies to: Clients | Used in Seamless Mail Upgrade for controlling the upgrade of the design of a user’s mail file. The value of this variable is set during the upgrade process, when the user is prompted to upgrade by the “Upgrade Mail File Design” dialog box. If the user clicks Upgrade, and the upgrade is successful, the value of this variable is set to the same value as the environment variable Setup in the upgraded Notes Client. For example, if a client is upgraded to Notes version 6.04, the variable is set like this: MailSetup = 600400 If the user clicks Cancel, but does not select “Don’t show this message again,” the value of this variable is set to 1. When the user opens their mail file, the Upgrade Mail File Design dialog will appear again. If the user clicks Cancel, and also selects “Don’t show this message again,” a dialog box appears informing the user to contact their administrator about upgrading the mail file. If the user clicks OK in this dialog box, the value of this variable is set to -1. The Upgrade Mail File Design dialog box does not appear again. There is no default setting. | MailSetup = value | |
| Mail_Skip _NoKey_Dialog Applies to: Clients | Specifies whether to display the Encryption Failure dialog when Notes cannot locate the public key to sign or encrypt a message: 0 – The “Don’t show signature or encryption failures again and continue sending” dialog appears when Notes cannot find the public key. 1 – The “Don’t show signature or encryption failures again and continue sending” dialog does not appear when Notes cannot find the public key. Notes then sends the message unsigned and/or unencrypted. There is no default setting. | Mail_Skip _NoKey_Dialog = value | UI equivalent: The “Don’t show signature or encryption failures again and continue sending” checkbox in the Encryption Failure dialog box. |
| MailSystem Applies to: Servers and clients | Specifies the mail system that the user selected during the workstation setup procedure: 0 – Notes mail 1 – cc:Mail or a non-Lotus mail system There is no default setting. | MailSystem = value | UI equivalent: The mail system selection made during workstation setup. |
| MailTimeout Applies to: Servers | Specifies the number of days after which the server returns undelivered mail to the sender. Increase this setting when you have a lot of mail returned in one day or when you are sending mail to foreign domains. To specify a period of less than one day, use the NOTES.INI setting MailTimeoutMinutes. There is no default setting, although if this setting is omitted, undelivered mail is returned after one day. | MailTimeout = number of days | UI equivalent: None, but you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| MailTimeoutMinutes Applies to: Servers | Specifies the number of minutes after which the server returns undelivered mail to the sender. The maximum number of minutes is 1440 (24 hours). To specify a time greater than one day, use the NOTES.INI setting MailTimeout. There is no default setting. | MailTimeoutMinutes = number of minutes | There is no UI equivalent. |
| MailUpgradeFolder Applies to: Clients | Used in Seamless Mail Upgrade for controlling the upgrade of the design of a user’s mail file folders. The value of this variable is set during the upgrade process, when the user is prompted to respond to the “Upgrade Folder Design” dialog box. If the user has upgraded their mail file successfully, the value of this variable is set to 1 when the user logs in to the Notes client for the first time since the upgrade. When the user opens the mail file, the Upgrade Folder Design dialog box appears. If the user clicks Automatic Upgrade, the folder design will be upgraded to the default Notes 6 folder style, and the MailUpgradeFolder variable will be set to the same value as the value of the environment variable Setup in the upgraded Notes Client. If the user clicks Manual Upgrade, the user will be prompted to select the mail folders to upgrade, as well as the design to upgrade the selected folders to. The MailUpgradeFolder variable will not change. If the user clicks Cancel, the folder design will not be upgraded and the MailUpgradeFolder variable will not change. There is no default setting. | MailUpgradeFolder = value | There is no UI equivalent. |
| Map_Retry_Delay Applies to: Servers | Specifies the number of minutes that a server waits after an unsuccessful attempt to call another server before it tries again. There is no default setting. | Map_Retry_Delay = number of minutes | There is no UI equivalent. |
| Max_Config_Files Applies to: Servers | During server initialization, system information from several documents and files is saved. In order to avoid consuming excessive disk space, the number of files collected can be limited. By default, a maximum of ten file of each type, ncluding NSD, is collected. If Max_Config_Files is reduced, then the appropriate number of files is deleted. This variable is checked only when the server starts or if there is a configuration change. If the variable Max_NSDInfo_Files exists, its value is used instead of Max_Config_Files. Default setting is 10 files. | Max_Config_Files = number of files | There is no UI equivalent. |
| Max_NSDInfo_Files Applies to: Servers | During server initialization, system information from several documents and files is saved. In order to avoid consuming excessive disk space, the number of files collected can be limited. By default, a maximum of ten file of each type, including NSD, is collected. The maximum number of NSD files can be overridden with this variable. Default setting is 10 files. | Max_NSDInfo_Files = number of files | There is no UI equivalent. |
| MinNewMailPoll Applies to: Servers | Determines how often workstations can contact the server to see if new mail has arrived for the user. This setting overrides the user’s selection in the Mail Setup dialog box. You can increase the mail polling interval if there are a large number of mail users on your server, and you want to prevent frequent polling from affecting server performance. There is no default setting. | MinNewMailPoll = number of minutes | There is no UI equivalent. |
| Move_Mail_File _Expiration_Days Applies to: Servers | Specifies the number of days that the Notes client updates mail file related Change Requests. After this time period, these become obsolete Change Requests. For example: Move_Mail_File_Expiration_Days=30. There is no default setting. | Move_Mail_File _Expiration_Days = number of days | There is no UI equivalent. |
| MSAACompatibility Applies to: Clients | Due to some changes in the accessibility interface between Notes 6 and R5, some screen readers will announce no values when reading a document, but will duplicate field names. Notes 6 can be made to emulate the R5 behavior by setting this .ini file variable to V5. Screen reader vendors are aware of this issue and should be contacted about the current status of their products. There is no default setting. | MSAACompatibility = V5 | There is no UI equivalent. |
| MSAAFieldNameHelp Applies to: Clients | By default, when the Notes client provides information to an accessibility aid it will re-use the field’s name as the field description if the description is blank. Likewise, it will use the field description as the field name if there is no field name. This behavior can be disabled by setting this .ini file variable to -1. For usability purposes, it may be important for field name and field description to be distinct. In this case the application developer will need to provide HTML ‘Titles’ (field name) and field help (for field descriptions) explicitly. There is no default setting. | MSAAFieldNameHelp = -1 | There is no UI equivalent. |
| MTCDailyTasksHour Applies to: Servers | Specifies the time, in 24-hour format, when the Mail Tracking Collector (MTC) task performs the daily compaction of the Domino MailTracker Store database (MTSTORE.NSF). Any value between 0 and 23 is an effective value. In the absence of this setting, the Domino server sets the value to 2, and compaction occurs nightly at 2 AM. It is not necessary to specify the value for minutes. For example: MTCDailyTasksHour=18:00 | MTCDailyTasksHour = time | There is no UI equivalent. |
| MTMaxResponses Applies to: Servers | Specifies the maximum number of message tracking responses returned from a query. The number of responses returned will be less than or equal to the MTMaxResponses value. Whenever a query returns more than the MTMaxResponses limit, a message indicating this appears on the Admininstration panel status line. There is no default, although if this setting is omitted, the maximum number of message tracking responses returned from a query is 100. | MTMaxResponses = number of responses | There is no UI equivalent. |
| Notes.ini settings: N |
| Setting | Description | Syntax | Comment |
| Names Applies to: Servers | Specifies the names of the secondary Domino Directories that Domino searches to verify recipient names in mail messages. By default, Domino searches only the primary Domino Directory, which is typically named NAMES.NSF. It is strongly recommended that you use directory assistance rather than this setting to do lookups in secondary Domino Directories. This NOTES.INI setting allows additional directories to be searched in the order in which they appear and stops searching when it finds a match in one of the databases. The file names can be up to 256 characters. Separate the list of directories with commas. Do not specify the NSF file extension.The server does not use this feature to look up additional Connection, Domain, or Server documents specified in additional directories. Ensure you create all of the necessary Connection, Domain, and Server documents in the primary Domino Directory.
Do not add the name of a condensed Directory Catalog as a value for this setting. Use the Basics tab of the Server document in the Domino Directory to set up a server to use a condensed Directory Catalog. | Names = name(s) | There is no UI equivalent. |
| NB_Collect_Response _Times Applies to: Servers | Add this NOTES.INI setting to the NOTES.INI file on the test driver to enable output of per-command response time. The resulting file is added to the Results Directory and is assigned a file name RespTime_OutFile#, where # represents the driver number. Use NB_Collect_Response_Times with the ResultsDirectory NOTES.INI setting. For example, the NOTES.INI would contain these settings: NB_Collect_Response_Times=1RESULTSDIRECTORY=Z:\The setting is for general use with all workloads and custom scripts. To disable response data collecting, enter the NOTES.INI setting with a value of zero. There is no default setting. | NB_Collect_Response _Times = 1 | There is no UI equivalent. |
| NB_SSL_Option Applies to: Servers | Secure Socket Layer (SSL) is enabled for the R6IMAP workload. Add this NOTES.INI setting to the client driver’s NOTES.INI file to enable SSL. To disable SSL in the R6IMAP workload, remove the NOTES.INI setting. There is no default setting. | NB_SSL_Option = Use_SSL | There is no UI equivalent. |
| NetWareSocket Applies to: Servers | Specifies the IPX socket number used by the Domino server. There is no default setting – Domino lets the IPX/SPX protocol stack assign a socket number dynamically. | NetWareSocket = socket number | There is no UI equivalent. |
| NetWareSpxSettings Applies to: Servers | Specifies the decimal value of the Domino server’s IPX socket. There is no default setting. | NetWareSpxSettings = value | There is no UI equivalent. |
| NewMailInterval Applies to: Clients | Defines how often (in minutes) Notes checks the user’s Inbox for new mail. Default setting is 1 minute. | NewMailInterval = number of minutes | UI equivalent: File – Preferences – User Preferences – Mail – Check for new mail every x minutes. |
| NewUserServer Applies to: Servers | Specifies the registration server for a Domino domain, if this has not been specified in Administration Preferences. There is no default setting. | NewUserServer = server | There is no UI equivalent. |
| NLCACHE_VERSION Applies to: Servers | Introduced in Domino 7.0.3.This Notes.ini variable is a fix to an enhancement to the NAMELookup cache that invalidates individual entries rather than entire groups. This enhancement is not enabled by default, and will only be enabled if the NAMELookup cache version has been increased to 4 by setting the value of this variable to 4. The default setting for the NAMELookup cache in Domino 7x is version 2. | NLCACHE_VERSION = 4 | There is no UI equivalent. |
| NoDesignMenu Applies to: Clients | Hides the Design menu on workstations. There is no default setting, although if this setting is omitted, the Design menu appears. 0 – Shows the Design menu 1 – Hides the Design menu | NoDesignMenu = value | There is no UI equivalent. |
| NoExternalApps Applies to: Clients | Protects against “mail bomb” viruses by disabling the following workstation features:
Use the following values to set this variable: There is no default setting, although if this setting is omitted, these workstation features are enabled. | NoExternalApps = value | There is no UI equivalent. |
| No_Force_Activity _Logging Applies to: Servers | Controls whether the Statlog task automatically enables activity logging on all databases: 0 – Allows automatic activity logging on all databases 1 – Prevents automatic activity logging on all databases Even when activity is not being recorded for the database, the information is still recorded in the Activity entry of the Database Usage view in the server’s log file. There is no default setting, although if this setting is omitted, the Statlog server task enables the Record Activity option for every database on the server and adds 64K to each database. | No_Force_Activity_Logging = value | UI equivalent: None, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| NoMailMenu Applies to: Clients | Hides the Mail menu. When set to 1, the Mail menu doesn’t appear on workstations. This setting also sets the user’s mail system to None. There is no default setting, although if this setting is omitted, the Notes Mail menu appears. | NoMailMenu = value | There is no UI equivalent. |
| NoMsgCache Applies to: Servers | Disables per-user message caching by the IMAP task. This can improve capacity (number of users) on a server by reducing memory consumption. There is no default setting, although if this setting is omitted, IMAP per-user message caching will be enabled. | NoMsgCache = value | There is no UI equivalent. |
| NotesStreamPlatform Default Applies to: Servers and clients | The backend class NotesStream open method accepts a charset parameter of “UTF-16″, for use with files containing serialized, 2-byte (16-bit) Unicode characters. If the file contains no leading byte-order-mark (“BOM”) identifying the high/low ordering of each pair of bytes, the default NotesStream behavior for a “UTF-16″ charset is to treat the file as having big-endian byte ordering. This will be wrong some percentage of the time. In situations where that percentage is high, an alternate default may be enabled with this Notes.ini setting. There is no default setting. Setting this variable to 1 will cause NotesStream to treat “UTF-16″ charset files as big-endian on big-endian platforms, and little-endian on little-endian platforms. As before, the “UTF-16BE” and “UTF-16LE” charset values may be used (instead of the ambiguous “UTF-16″) to influence which endian assumption is applied on a file-by-file basis. | NotesStreamPlatform Default = 1 | There is no UI equivalent. |
| NSF_Buffer _Pool_Size Applies to: Servers and clients | Specifies the maximum size (in bytes) of the NSF buffer pool, a section of memory dedicated to buffering I/O transfers between Domino and disk storage. The maximum size depends on any limitations of the operating system, and the amount of system memory available. The minimum size is 4MB. You can also use NSF_Buffer_Pool_Size_MB to set the maximum size of the NSF buffer pool. This is the same as NSF_Buffer_Pool_Size, except it specifies the size in megabytes instead of bytes. Use NSF_Buffer_Pool_Size_MB to avoid the 2GB limitation that exists for NSF_Buffer_Pool_Size due to NOTES.INI variable limits. (NOTES.INI variables are signed variables, and cannot be larger than 2GB.) The default setting is determined automatically by the server or workstation. (This is strongly recommended, except on partitioned servers.) The more memory is available, the larger the server sets the default NSF_Buffer_Pool_Size. On workstations, the maximum setting of the NSF_Buffer_Pool_Size is 8MB (4MB for MAC). On the server, the default maximum is determined to be between 1/8 and 3/8 of available physical memory, depending on the overall size of physical memory. The defaults are not automatically adjusted on partitioned servers, so it will usually be necessary to adjust the maximum values in each partition to a fraction of memory such that the memory used by all partitions adds up to approximately 1/4 to 3/8 of memory. | NSF_Buffer _Pool_Size = number of bytes | There is no UI equivalent. |
| NSF_DbCache _Disable Applies to: Servers | Controls whether the database cache is enabled on a server. The database cache is enabled by default. There is no default setting. 0 – Enables the database cache 1 – Disables the database cache | NSF_DbCache _Disable = value | There is no UI equivalent. |
| NSF_DbCache _Maxentries Applies to: Servers | Determines the number of databases that a server can hold in its database cache at one time, where n is the number of databases. Increasing the database cache size can improve system performance but requires additional memory. The minimum number of databases allowed in the cache at one time is 25; the maximum is approximately 2000, depending on the server platform. There is no default setting, although if this setting is omitted, the number of databases that the server can hold in its cache at one time is either 25, or the NSF_Buffer_Pool_Size value divided by 300K (whichever is greater). | NSF_DbCache _Maxentries = number of databases | There is no UI equivalent. |
| NSF_Quota_Method Applies to: Servers | This variable reflects the mail file database quota enforcement method enabled in the Server document, where n indicates the specific method. If quota enforcement methods are enabled, whenever the Router delivers mail, it compares the current size of the destination mail file against its configured database quota or threshold. If the size exceeds one of these, the Router takes appropriate action. There is no default setting. 1 – check space used in file when adding a note 2 – check file size when extending the file 3 – check file size when adding a note | NSF_Quota_Method = value | UI equivalent: None, although you can specify this setting in the Quota enforcement field on the Transactional Logging tab of the Server document. |
| Num_Compact _Rename_Retries Applies to: Servers | Domino attempts only once to rename a database that was copy-style compacted. You can request additional attempts by specifying a value in the Num_Compact_Rename_Retries setting in the NOTES.INI file. Domino tries to rename until it succeeds or the number of retries is exhausted. For example, to request that Domino try once again to rename, specify Num_Compact_Rename_Retries = 1; to request that Domino try 5 more times to rename, specify Num_Compact_Rename_Retries = 5. There is no default entry but in the absence of the setting, Domino attempts just once to rename a database that was copy-style compacted. | Num_Compact _Rename_Retries = number of times to retry | There is no UI equivalent. |
| NWNDSPassword Applies to: Servers | Specifies the password for Domino to log in to the Novell Directory Service (NDS) tree on system start-up. Until this setting is added to the NOTES.INI file, an administrator must log in to the NDS tree before starting the Domino server. There is no default setting. | NWNDSPassword = NDS password | There is no UI equivalent. |
| NWNDSUserID Applies to: Servers | Specifies the user ID for Domino to log into the Novell Directory Service (NDS) tree on system start-up. Until this setting is added to the NOTES.INI file, an administrator must log into the NDS tree before starting the Domino server. There is no default setting. | NWNDSUserID = NDS user ID | There is no UI equivalent. |
| Notes.ini settings: P |
| Setting | Description | Example | Comment |
| Passthru_Hangup _Delay Applies to: Servers | Specifies how long in seconds a passthru server maintains a dialup connection after its last dialup session ends. Default setting is 120 seconds. | Passthru_Hangup _Delay = number of seconds | There is no UI equivalent. |
| Passthru_LogLevel Applies to: Servers and clients | Specifies the level of trace information recorded for all network connections (including passthru) in the Miscellaneous Events view of the log file. 0 (default) – No information is recorded 1 – Only errors are recorded 2 – Summary progress information is recorded 3 – Detailed progress information is recorded 4 – Full trace information is recorded 5 – Full trace information plus driver messages are recorded | Passthru_LogLevel = value | UI equivalent: File – Preferences – User Preferences – Ports – Trace – Notes Log options |
| PercentAvail SysResources Applies to: Servers and clients | Determines approximately how much physical memory is available in the server. This parameter was implemented to try to prevent too much virtual memory from being allocated, which can degrade performance by going to/from the disk. Domino makes an operating system (OS) API call to see how much physical memory is being used. Then, depending on the ratio of how much physical memory is being used by the system at that point in time, Domino makes certain decisions as to how much memory can or should be used by various processes. When the API call is made determines how much physical memory Domino will allow to be allocated. Because of this, it will not be 100% accurate at any given time, but it should improve performance if implemented correctly. It is not recommended to set PercentAvailSysResources to an extremely high number, such as 90, as the operating system and any other applications running on the machine will take a portion of the total physical memory. This variable is not supported on z/OS. You must set the NSF buffer pool size explicitly. Default setting is 0. | PercentAvail SysResources = value | There is no UI equivalent. |
| PhoneLog Applies to: Servers and clients | Specifies whether phone calls are recorded in the log file: 0 – Does not record phone calls to the log file 1 – Records all calls, except those that fail because of a busy signal 2 (default)- Records all phone calls | PhoneLog = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| PKCS11_Library Applies to: Servers | Specifies the location of the server’s locally installed PKCS#11 file for enabling Smartcards. There is no default setting. For example: PKCS11_Library = C:\Program Files\Schlumberger\Smart Cards and Terminals\Common Files\slbck.dll | PKCS11_Library = path | UI equivalent: The Smartcard installation wizard will prompt the user to install the appropriate DLL for the Smartcard. |
| Platform_Statistics _Disabled Applies to: Servers | By default, Domino tracks performance metrics of the operating system and captures the results in the Domino server. To disable statistic reporting, set the value of this variable to 1. You must remove the setting from the NOTES.INI file altogether to re-enable platform statistic reporting. | Platform_Statistics _Disabled = value | There is no UI equivalent. |
| POP3Config UpdateInterval Applies to: Servers | Determines how often (per minute) the POP3 server will update its configuration information. Default setting is 2 minutes. | POP3Config UpdateInterval = number of minutes | There is no UI equivalent. |
| POP3_Disable _Cache Applies to: Servers | Enables/disables message caching for users. 0 (default) – Enables message caching 1 – Disables message caching | POP3_Disable _Cache = value | There is no UI equivalent. |
| POP3DNSLookup Applies to: Servers | Enables/disables reverse DNS lookups of client host names. 0 (default) – Disables reverse DNS lookups of client host names 1 – Enables reverse DNS lookups of client host names | POP3DNSLookup = value | There is no UI equivalent. |
| POP3Domain Applies to: Servers | Specifies the name of the Internet domain to use as the gateway to send mail to the Internet for local addresses. (All local addresses are converted to Internet addresses.) If this setting is included in the NOTES.INI file, it overrides the DNS value. There is no default setting. | POP3Domain = domain name | There is no UI equivalent. |
| POP3_Enable _Cache_Stats Applies to: Servers | Enables/disables message caching statistics. 0 (default) – Disables message caching statistics 1 – Enables message caching statistics | POP3_Enable _Cache_Stats = value | There is no UI equivalent. |
| POP3MarkRead Applies to: Servers | Specifies whether POP3 messages should be marked as read after downloading. A value of 1 instructs the server to mark the messages as read. 0 (default) – Do not mark POP3 messages as read 1 – Mark POP3 messages as read | POP3MarkRead = value | There is no UI equivalent. |
| POP3_Message_Stat _Cache_NumPerUser Applies to: Servers | Limits the number of message statistics that can be cached for a single user. Message statistics caches contain UNIDs and saved message sizes. Each cache entry consumes CPU time and server memory. Reducing this number can improve server performance. Default setting is 50. | POP3_Message_Stat _Cache_NumPerUser = number of message statistics | There is no UI equivalent. |
| POP3NotesPort Applies to: Servers | Specifies the name of the Notes network port for TCP/IP that you are linking the POP3 service with. This setting is required for a partitioned server hosting POP3, and for a single server hosting it if the server has more than one Notes port for TCP/IP. | POP3NotesPort = port name | There is no UI equivalent. |
| portname _MaxSessions Applies to: Servers | Restricts the number of sessions on a specified. There is no default setting. | portname _MaxSessions = number of sessions | There is no UI equivalent. |
| Ports Applies to: Servers and clients | This setting indicates which ports are enabled for the server or workstation. Ports are enabled/disabled by a two-step process s using the Setup Ports dialog box and then using Server documents (for servers) or the User Preferences dialog box (for workstations). The order in which ports are listed in this setting can affect how Notes workstations and Domino servers connect to a system. There is no default setting. | Ports = port name(s) | UI equivalent: On a workstation, see the Ports tab in the User Preferences dialog box (choose File – Preferences – User Preferences). On a server, the Configuration tab’s Tools pane, Server – Setup Ports option, and then see the Ports – Notes Network Ports tab in the Server document. |
| PrinterPixelPreview Applies to: Clients | When set, this variable causes Notes print preview to be completely accurate in where page breaks occur in the preview. There is a loss of speed in previewing when using the variable, but it is small. Users wanting absolute preview accuracy should enable this variable. There is no default setting. | PrinterPixelPreview = 1 | There is no UI equivalent. |
| Process_Monitor _Disabled Applies to: Servers | Disables the Process Monitor server task, which ensures that all of the processes that Domino expects to be present are, in fact, running. This server task runs automatically; the administrator must disable it either using this .ini variable or by setting STX9. There is no default setting. Setting this variable to 1 disables the Process Monitor task. | Process_Monitor _Disabled = value | There is no UI equivalent. |
| ProgramMode Applies to: Clients | If the user sets up Notes with a Notes mail ID or switches to a Notes mail ID (not a Lotus Notes desktop ID), a value is written to the NOTES.INI ProgramMode setting, as follows: 0 (default) – Full Notes 1 – Notes Mail 8 – Desktop | ProgramMode = value | There is no UI equivalent. |
| Notes.ini settings: R |
| Setting | Description | Example | Comment |
| Repl_Error _Tolerance Applies to: Servers | Specifies the number of replication errors of the same type that can occur between two databases before the server terminates replication. Default setting is 2. | Repl_Error _Tolerance = number of replication errors | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| ReplicationTime Limit Applies to: Servers | Specifies a time limit (in minutes) for replication between one server and another. If this setting is not included in the NOTES.INI file, there is no time limit. There is no default setting. | ReplicationTime Limit = number of minutes | UI equivalent: The Replication Time Limit field in the Routing/Replication tab in the Connection document in the Domino Directory. |
| Replicators Applies to: Servers | Specifies the number of Replicator tasks that can run concurrently on the server. You must shut down and restart the server for this setting to take effect. Default setting is 1. | Replicators = number of tasks | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Repl_Obeys _Quotas Applies to: Servers | Specifies whether the Replicator obeys quotas. 0 (default) – Disables the Replicator from obeying quotas 1 – Enables the Replicator to obey quotas | Repl_Obeys _Quotas = value | There is no UI equivalent. |
| Report_DB Applies to: Servers | When the Monitoring Configuration database (EVENTS4.NSF) is created, it is placed in the Domino Data directory. Use this setting to specify the location of the database if it is located somewhere other than in the Domino Data directory. There is no default setting, but in the absence of any Report_DB setting in the NOTES.INI file, the default path is Lotus\Domino\Data\events4.nsf. | Report_DB = path | There is no UI equivalent. |
| ReportUseMail Applies to: Servers | Allows the Reporter task to use the Router to send statistics to another server in the same domain: 1 – Use the Router 0 – Use the network Using the Router can be useful for reporting statistics over dial-up connections to a central collection server. There is no default setting, although without this variable, the Reporter task uses the network to report statistics. | ReportUseMail = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Retain_Mirror_Logs Applies to: Servers | Prevents the deletion of previous mirror files when Domino starts. Existing mirror files are deleted if the NOTES.INI setting, Retain_Mirror_Logs, has not been set. Retain_Mirror_Logs is disabled by default. 0 or not present (default) – Disables retaining the mirror logs 1 – Enables retaining the mirror logs | Retain_Mirror_Logs = 1 | There is no UI equivalent.” |
| RouterAllow ConcurrentXferToAll Applies to: Servers | Use this setting to enable/disable multiple concurrent transfer threads for inter-domain Notes routing. There is no default setting, but if the setting does not appear in the NOTES.INI file, Domino’s default behavior is to disable multiple concurrent transfer threads for inter-domain Notes routing. 1 – Enables 0 – Disables | RouterAllow ConcurrentXferToAll = value | There is no UI equivalent. |
| RouterDisableMail ToGroups Applies to: Servers | Specifies whether the router should allow or deny mail addressed to a group. 0 (default) – Allow the Router to expand groups and forward a message to the group members. 1 – Router will not expand any groups. It will return the message as a failure report to the sender – rejected for policy reasons. | RouterDisableMail ToGroups = value | There is no UI equivalent. |
| RouterDelayNotify EachInterval Applies to: Servers | Specify whether a Delay report is to be sent for the same message at every subsequent interval of the delay. 0 — Sends a Delay report for the same message at every subsequent interval of the delay. 1(default) – Send only one Delay report per delayed message on a server. | RouterDelayNotify EachInterval = value | There is no UI equivalent. |
| RouterDSNForNull ReversePath Applies to: Servers | Specifies whether the router should return delivery status notifications (DSNs) for messages received over SMTP with null RFC 821 reverse paths. 0 (default) – Don’t return a failed DSN. Create the non-delivery report, but mark it as DEAD. The Administrator can then delete these messages or release them. 1 – Create and send the delivery status notification. 2 – Do not create a delivery status notification. | RouterDSNForNull ReversePath = value | There is no UI equivalent. |
| RouterEnableMail ByDest Applies to: Servers | Use this setting to generate verbose mail routing statistics per destination. These statistics may be useful when attempting to troubleshoot routing problems. There is no default setting. 0 – No destination based statistics are generated by the router. 1 – Router maintains statistics for each mail routing destination, which include the last successful/unsuccessful transfer time, total number of messages routed, and the total number of failures. | RouterEnableMail ByDest = value | There is no UI equivalent. |
| RouterUserRule ForwardReversePath Applies to: Servers | Specify the reverse-path setting for messages that are forwarded by a user mail rule “send copy to” action. 0 (default) – Set reverse path to null. 1 – Preserve existing value. 2 – Use recipients Internet address. 3 – Construct nondeliverable return address. | RouterUserRule ForwardReversePath = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| RTR_Logging Applies to: Servers | Enables or disables monitoring of Cluster Replicator activity. There is no default setting. 0 – Disables monitoring of the Cluster Replicator 1 – Enables monitoring of the Cluster Replicator | RTR_Logging = value | There is no UI equivalent. |
| Notes.ini settings: S |
| Setting | Description | Syntax | Comment |
| Sched_Dialing _Enabled Applies to: Clients | Enables or disables dialing out to check Busy Time. 0 (default) – Disables dialing out to check Busy Time 1 – Enables dialing out to check Busy Time | Sched_Dialing _Enabled = value | There is no UI equivalent. |
| Sched_Purge _Interval Applies to: Servers | Specifies how many days prior to the current day to keep busytime data. A value of 0 means data is never purged. Default setting is 7. | Sched_Purge _Interval = number of days | There is no UI equivalent. |
| Schedule_Check _Entries_When _Validating Applies to: Servers | Enables or disables whether SchedMgr validates its busytime database entry on a user by user basis, as follows: 0 (default) – Disables validation 1 – Enables validation Validation should not be required under normal conditions. | Schedule_Check _Entries_When _Validating = value | There is no UI equivalent. |
| Schedule_No _CalcStats Applies to: Servers | Enables or disables whether SchedMgr updates/calculates statistics on an hourly daily basis, as follows: 0 (default) – Enables update/calculation 1 – Disables update/calculation | Schedule_No _CalcStats = value | There is no UI equivalent. |
| Schedule_No _Validate Applies to: Servers | Enables or disables whether SchedMgr validates its busytime database entry on a daily basis, as follows: 0 (default) – Enables validation 1 – Disables validation Validation should be enabled under normal conditions. | Schedule_No _Validate = value | There is no UI equivalent. |
| Schema_Daemon _Breaktime Applies to: Servers | Specifies how often (in seconds) the schema daemon spawned by the LDAP service checks if it should shut down because its parent LDAP task is shutting down. In most situations there is no need to change the breaktime interval. In rare situations, you might increase this value as a way to free up CPU resources on a heavily used server. Increasing the breaktime value also increases the time it takes the LDAP service to shut down. There is no default setting, although without this setting, the schema daemon checks the status of its parent LDAP task every 15 seconds. | Schema_Daemon _Breaktime = number of seconds | There is no UI equivalent. |
| Schema_Daemon _Idletime Applies to: Servers | Specifies how long (in minutes) the schema daemon spawned by the LDAP service remains idle after it has completed its tasks. After the schema daemon has been idle for the specified interval, it begins its tasks again. There is no default setting, although without this setting, the schema daemon remains idle for 15 minutes. | Schema_Daemon _Idletime = number of minutes | There is no UI equivalent. |
| Schema_Daemon _Reloadtime Applies to: Servers | Specifies how often (in hours) the schema daemon spawned by the LDAP service adds schema elements for new or changed Domino Directory forms and fields to its in-memory schema. This operation occurs only on the administration server for the Domino Directory and not on other servers in the domain that run the LDAP service. Reloading in-memory schema to reflect new or changed Domino Directory forms and fields is a CPU-intensive operation. You might set different intervals for Schema_Daemon_Reloadtime and Schema_Daemon_Resynctime so the two operations occur at different times. Or you might increase the interval during periods when there are no schema changes. Schema_Daemon_Idletime, rather than Schema_Daemon_Reloadtime, controls how often the schema daemon loads new schema elements defined in the Domino LDAP Schema database into memory. There is no default setting, although without this setting the schema daemon reload interval is 24 hours. | Schema_Daemon _Reloadtime = number of hours | There is no UI equivalent. |
| Schema_Daemon _Resynctime Applies to: Servers | Specifies how often (in hours) the schema daemon spawned by the LDAP service updates the schema published in the Domino LDAP Schema database with a newer in-memory schema. This operation occurs only on the Domino Directory administration server, and not other servers in the domain that run the LDAP service. Synchronizing the Schema database with in-memory schema is a CPU-intensive operation. You might set different intervals for Schema_Daemon_Reloadtime and Schema_Daemon_Resynctime so the two operations occur at different times. Or you might increase the interval during periods when there are no schema changes. There is no default setting, although without this setting the schema daemon resync interval is 24 hours. | Schema_Daemon _Resynctime = number of hours | There is no UI equivalent. |
| ScriptCountryID Applies to: Servers and clients | Used only for IME-related functions. Notes.ini setting is not present by default; default country code is US (01). | ScriptCountryID = two-digit country code | There is no UI equivalent. |
| ScriptLanguageID Applies to: Servers and clients | Determines the LotusScript resource .dlls that are used to display day, month names, and date formats appropriate for specified locale. Also determines the ID resource .dll used to determine the strings that appear in the IDE user interface. Notes.ini setting is not present by default; default language code is English (“en”). | ScriptLanguageID = two-digit language code | There is no UI equivalent. |
| Secure_Disable _FullAdmin Applies to: Servers | Allows administrators to disable the Full Access Administrators field in the Server document, causing the server to ignore any entries in that field. 1 – Disables the Full Access Administrators field in the Server document 0 (default) – Does not disable Full Access Administrators field in the Server document | Secure_Disable _FullAdmin = value | There is no UI equivalent. |
| SecureMail Applies to: Clients | Entering 1 as the value forces the mail program to sign and encrypt all mail sent from the workstation. There is no default value, although if this setting is omitted, the Sign and Encrypt options appear. 1 – Removes the Sign and Encrypt options from all dialog boxes 0 – Restores the Sign and Encrypt options | SecureMail = value | UI equivalent: File – Preferences – User Preferences – Mail – Encrypt sent mail |
| Server_Availability _Threshold Applies to: Servers | Specifies the acceptable level of system resources available to a server. By setting this value for each server in a cluster, you determine how the workload is distributed among cluster members. Valid values are 0 to 100. Domino compares this value against a server’s availability index; when the availability index falls below the Server_Availability_Threshold value, the server becomes BUSY. A Server_Availability_Threshold value of zero (0) indicates a fully available state and workload balancing is disabled; a value of 100 indicates the server is BUSY (since the availability index can never be greater than 100) and the Cluster Manager then tries to redirect user requests to more available cluster members. Default value is 0. | Server_Availability _Threshold = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Server_cluster _auxiliary_ports Applies to: Servers | Specifies the port through which the server can be reached, in the event of failure of the port specified by Server_Cluster_Default_Port. Specify a comma delimited list in the auxiliary port line and the ports in the list will be checked for the desired server. If the user does not specify a Server_Cluster_Default_Port or a server_cluster_auxiliary_port, all ports will be tried. | Server_cluster _auxiliary_ports = port name | There is no UI equivalent. |
| Server_Cluster _Default_Port Applies to: Servers | Specifies the port used for intracluster network traffic. The value should be a port name–for example, TCP–as specified in the Ports tab of the Server document. There is no default value. | Server_Cluster _Default_Port = port name | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Server_Console _Password Applies to: Servers | For the encrypted_password to be written to this setting in the NOTES.INI file, you must use the Set Configuration server command to specify the password. The password can be a combination of letters and numbers. When this setting is added to the NOTES.INI file, Domino activates the Set Secure command to secure the server console. The password provided should be different from the administrator’s user password. If you forget the console password, delete this setting from the NOTES.INI file, and then re-specify a password. There is no default value. | Server_Console _Password = encrypted password | There is no UI equivalent. |
| ServerKeyFileName Applies to: Servers | Specifies the server ID file to use on a machine that runs both the Notes workstation program and the Domino server program. Then, you edit the NOTES.INI KeyFileName setting to specify your user ID as the ID to use when you run the Notes workstation or API programs on the server machine. There is no default value. | ServerKeyFileName = ID_file | There is no UI equivalent. |
| Server_Max _Concurrent_Trans Applies to: Servers | Sets the limit for the number of concurrently scheduled transactions on a server. Do not change this variable unless advised to do so by technical support. Default number of transactions is 20. | Server_Max _Concurrent_Trans = number of transactions | There is no UI equivalent. |
| Server_MaxSessions Applies to: Servers | Specifies the maximum number of sessions that can run concurrently on the server. To prevent server overload, decrease this number if you set up multiple Replicators or Routers. There is no default setting. | Server_MaxSessions = number of sessions | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Server_MaxUsers Applies to: Servers | Sets the maximum number of users that are allowed to access a server. When this number is reached, the server state becomes MAXUSERS, and the server stops accepting new Database Open requests. There is no default value. 0 – Unlimited access to server by users number – Restricts number of active users to the number you specify | Server_MaxUsers = number | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| ServerName Applies to: Servers | Specifies the full hierarchical name of the server. There is no default setting. | ServerName = name | UI equivalent: The Server Name field in the Server document. |
| ServerNoRepl Requests Applies to: Servers | Forces the server to refuse all replication requests from other servers. When this feature is enabled, to replicate with this server, the requesting server must perform pull-push replication: 0 – Accepts replication requests from other servers 1 – Refuses replication requests from other servers There is no default setting, although omitting this setting allows the server to accept replication requests. | ServerNoRepl Requests = value | There is no UI equivalent. |
| ServerPullReplication Applies to: Servers | Specifies that all scheduled replication initiated from this server must be pull-push replication. This server will not replicate back to the other servers. This setting affects only scheduled replication. 0 – Scheduled replication occurs normally (push-pull replication is not forced) 1 – This server pulls changes from other servers, but other servers cannot pull changes from this server. For example, to reduce the workload on a hub server, specify 1 for the ServerPullReplication setting on all spoke servers in a hub-and-spoke system. There is no default value, although omitting this setting allows for normally scheduled replication. | ServerPullReplication = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| ServerPushReplication Applies to: Servers | Specifies that all scheduled replication initiated from this server must be push-pull replication. This server does not request that the other server replicate back. There is no default value, although omitting this setting allows for normally scheduled replication. 0 – Scheduled replication occurs normally (push-pull replication is not forced) 1 – Other servers pull changes from this server, but this server cannot pull changes from other servers | ServerPushReplication = value | There is no UI equivalent. |
| Server_Restart_Delay Applies to: Servers | Specifies the amount of time (in seconds) the server waits before restarting with the ‘restart server’ console command. Default: None, although by default, Domino waits 10 seconds. | Server_Restart_Delay = number of seconds | There is no UI equivalent. |
| Server_Restricted Applies to: Servers | Enables or disables server access to a server. If access is disabled, the server does not accept new Open Database requests. For Domino 6.0 and subsequent releases, any administrator can still open databases, even if this variable is used to restrict server access. There is no default value. 0 – Server access is unrestricted. 1 – Server access is restricted for the current server session. Restarting the server clears the setting. 2 – Server access is restricted persistently, even after server restarts. | Server_Restricted = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Server_Session _Timeout Applies to: Servers | Specifies the number of minutes of inactivity after which the server automatically terminates network and mobile connections. The minimum recommended setting is 30-45 minutes. A lower setting may negatively impact server performance. The ideal setting depends on factors such as server load and the number of concurrent users on the server. For mobile connections, XPC has its own internal time-out. If the XPC time-out value is shorter than the Server_Session_Timeout value, the XPC time-out takes precedence. There is no default entry, but in the absence of the setting, Domino terminates a session connection after 240 minutes of inactivity (four hours). | Server_Session _Timeout = number of minutes | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Server_Show _Performance Applies to: Servers | Specifies whether or not server performance events are displayed on the console. There is no default value. Set this variable to 1 to display server performance events on console. | Server_Show _Performance = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| ServerTasks Applies to: Servers | Specifies the tasks that begin automatically at server startup and continue until the server is shut down. For example: ServerTasks=Replica, Router, Update, Stats, AMgr, Adminp, Sched, CalConn, Collect, MTC, RunJava ISpy The server runs the Replicator, Router, Indexer, Stats, Agent Manager, Administration Process, Schedule Manager, Calendar Connector, Collector, Mail Tracker Collector, and Mail Probe server tasks. Each task increases the server’s load and may adversely affect server performance. Note that the ISpy server task name is case sensitive and must be specified exactly as shown. Default values for this setting are: Replica, Router, Update, Stats, AMgr, Adminp, Sched, CalConn, Billing. | ServerTasks = name(s) | There is no UI equivalent. |
| ServerTasksAthour Applies to: Servers | Schedules automatic server and database maintenance functions. Enter the time in 24-hour format, where 0 is 12 AM (midnight) and 23 is 11 PM. For example:ServerTasksAt3=CatalogServerTasksAt7=UpdallServerTasksAt16=Catalog, Updall, StatlogAt 3 AM, the server runs the Catalog task. At 7 AM, the server runs the Updall task. At 4 PM, the server runs the Catalog, Updall, and Statistics tasks. The default settings are:
| ServerTasksAthour = name(s) | There is no UI equivalent. |
| Server_TransInfo _Range Applies to: Servers | SERVER_TRANSINFO_RANGE is used to adjust the Availability Index (AI) calculation to match the speed of your server. To adjust the Availability Index calculation for your server using this variable, monitor your system during a period of heavy usage and note the values of Expansion Factor. Use the console command show stat server.expansionfactor Select a value for SERVER_TRANSINFO_RANGE such that 2 raised to the power SERVER_TRANSINFO_RANGE is a reasonable upper bound for expansion factor values. For example, if SERVER_TRANSINFO_RANGE=6, then we expect that the expansion factor values will not rise about 64. Monitor your system during periods of heavy usage to note what value of AI you want to set for your threshold. Select a value which matches the drop in response time at which you want failover to occur. You can also use the console command show ai to display the server’s expansion factor and AI histories and suggest an appropriate value for this variable. | Server_TransInfo _Range = value | There is no UI equivalent. |
| Setup Applies to: Servers and clients | Identifies the version number of the software. The setting is used by the Install program to determine whether or not to run the Setup program. This variable also provides an upgrade audit. There is no default setting. | Setup = revision number | There is no UI equivalent. |
| SetupDB Applies to: Servers | Identifies the setup database for HTTP server setup mode. This must always be setupweb.nsf. When this is included in NOTES.INI, the administrator can start the server in HTTP server setup mode by including the argument HTTPSetup when starting the server. If this variable is missing, the server will not enter HTTP server setup mode. There is no default setting. | SetupDB = setupweb.nsf | There is no UI equivalent. |
| Setup_First_Server _Public_Key_Width Applies to: Servers | In Domino 7, the server ID created during first server install is 1024 bits wide. If a Notes 5 client tries to access the server, it fails. Use this NOTES.INI to immediately rollover the server key to 630 bits if R5 users need to access it. There is no default setting. | Setup_First_Server _Public_Key_Width = 630 | There is no UI equivalent. |
| SetupServerAddress Applies to: Clients | Identifies the address of the setup server. This can be either a DNS name, or a telephone number (XPC or DUN) to connect to the server. SetupServerAddress, together with SetupServerName, instruct the Notes setup program to obtain setup information from the specified server. If either variable is missing from NOTES.INI, the setup program prompts the user for setup information. There is no default setting. | SetupServerAddress = address | There is no UI equivalent. |
| SetupServerName Applies to: Clients | Identifies the name of the setup server. SetupServerName, together with SetupServerAddress, instructs the Notes setup program to obtain setup information from the specified server. If either variable is missing from NOTES.INI, the setup program prompts the user for setup information. There is no default setting. | SetupServerName = name | There is no UI equivalent. |
| Shutdown_Monitor _Disabled Applies to: Servers | When the “quit” or “restart server” command is issued to the server, and the server doesn’t terminate in the alloted time, then the server will forcefully terminate and an NSD log will be generated before termination. The time limit is specified in the “Automatic Server Restart” section of the server document in the Basics tab; the default is 5 minutes. This time limit is the time that no shutdown activity occurs; when a process successfully terminates then the timer restarts. This feature can be disabled using the Notes.INI setting SHUTDOWN_MONITOR_DISABLED. There is no default setting. | Shutdown_Monitor _Disabled = 1 | There is no UI equivalent. |
| SMIME_Strong _Algorithm Applies to: Clients | Specifies the encryption method for encrypting MIME messages to recipients whose public keys are longer than 512 bits, but do not have the special “strong encryption” flag in their certificates. There is no default value. Possible values are:
| SMIME_Strong _Algorithm = value | There is no UI equivalent. |
| SMIME_Weak _Algorithm Applies to: Clients | Specifies the encryption method for encrypting MIME messages to recipients whose public keys are shorter than 512 bits. There is no default value. Possible values are:
| SMIME_Weak _Algorithm = value | There is no UI equivalent. |
| SMTPAllHosts External Applies to: Servers | Use this setting to determine whether all hosts should be subject to the anti-spam controls specified for the server. In the absence of the setting, any internal hosts would be exempt from the controls. 0 – Exempts internal hosts from anti-spam controls. 1 – Internal hosts included for anti-spam controls. | SMTPAllHosts External = value | UI equivalent: In the server’s Configuration Settings document, first click the Router/SMTP tab, then the Restrictions and Controls tab, and finally the SMTP Inbound Controls tab. In the Inbound Relay Enforcement section’s “Perform Anti-Relay enforcement for these connecting hosts” field, select “All connecting hosts” or “External hosts.” |
| SMTP_Config _Update_Interval Applies to: Servers | Determines how often (in minutes) Domino checks to determine whether the user has updated SMTP configuration information. You can change Configuration documents while servers are running. For the change to take effect, the server must periodically check the Configuration document for changes. If the server discovers a change, it rereads all settings. This setting lets you change the server’s checking interval. A shorter time results in slightly higher overhead for checking, but changes are noticed more quickly. Default setting is 2. | SMTP_Config _Update_Interval = number of minutes | There is no UI equivalent. |
| SMTPDebug Applies to: Servers | Controls the level of console logging performed by the SMTP task. 0 (default) – No logging 1 – Log errors 2 – Log Protocol commands | SMTPDebug = value | There is no UI equivalent. |
| SMTPDebugIO Applies to: Servers | Enables the logging of all data sent and received by the SMTP task. Logging is cumulative; each level provides all information as described for previous levels when value is greater than 1. 0 (default) – No logging of I/O 1 – Number of bytes sent and received during various stages of SMTP conversation 3 – Logs all data received by the SMTP task, including SMTP commands received and responses sent 4 – RFC822 data (message data) Use SMTPDebugIO only when necessary and disable it again as soon as possible. It can cause the log file to grow very large, and logs the contents of received messages. | SMTPDebugIO = value | There is no UI equivalent. |
| SMTPDenyMail ToGroups Applies to: Servers | Specify whether to allow mail to be sent to a group name returned during directory lookups. 0 (default) – Disable denying mail to groups. 1 – Enable denying mail to groups for all connecting hosts. 2 – Enable denying mail to groups for all possible relay hosts. | SMTPDenyMail ToGroups = value | There is no UI equivalent. |
| SMTPDenyNot UniqueRcpt Applies to: Servers | Specify whether to reject ambiguous names that are returned during directory lookups. 0 (default) – Disable rejecting ambiguous names. 1 – Enable rejecting ambiguous names. | SMTPDenyNot UniqueRcpt = value | There is no UI equivalent. |
| SMTPErrorLimit Applies to: Servers | Specify the number of protocol errors that can be returned for a session before the session connection is terminated. By default, this setting is set to 0 (zero) designating that an unlimited number of protocol errors can be returned. | SMTPErrorLimit = maximum number of protocol errors | There is no UI equivalent. |
| SMTPExpand DNSBLStats Applies to: Servers | Use this setting to generate DNS Blacklist Filter statistics for each connecting host found in a DNS blacklist site. There is no default setting, but in the absence of this setting, the SMTP task maintains statistics that track the total number of connecting hosts that were found on the combined DNSBL of all sites combined, as well as how many were found on the DNSBL of each configured site. 0 – Host specific DNS Blacklist Filter statistics are not generated by the SMTP server. 1 – SMTP server generates host specific DNS Blacklist Filter statistics which indicate the total number of hits per DNSBL site, per connecting host’s IP address | SMTPExpand DNSBLStats = value | There is no UI equivalent. |
| SMTPExpand DNSWLStats Applies to: Servers | Use this setting to generate DNS Whitelist Filter statistics for each connecting host found in a DNS Whitelist site. There is no default setting, but in the absence of this setting, the SMTP task maintains statistics that track the total number of connecting hosts that were found on the combined DNSWL of all sites combined, as well as how many were found on the DNSWL of each configured site. 0 – Host specific DNS Whitelist Filter statistics are not generated by the SMTP server. 1 – SMTP server generates host specific DNS Whitelist Filter statistics which indicate the total number of hits per DNSWL site, per connecting host’s IP address. | SMTPExpand DNSWLStats = value | There is no UI equivalent. |
| SMTPGreeting Applies to: Servers | Specifies a text message sent to SMTP clients when they connect to the SMTP server. The message must contain the string “%s” which is replaced by the current date/time when the connection is made. The default value is “host-name ESMTP Service (Lotus Domino build-name) ready at %s”. | SMTPGreeting = string | There is no UI equivalent. |
| SMTPNotesPort Applies to: Servers | Specifies the port for the SMTP service, where port name is the name of the Domino port for TCP/IP. This is required for partitioned servers, and single servers that have more than one TCP/IP port. There is no default setting. | SMTPNotesPort = port name | There is no UI equivalent. |
| SMTPNoVersion InRcvdHdr Applies to: Servers | Use this setting to prevent Domino server product information from being disclosed in SMTP Received headers. In the absence of this setting (default), received headers added by the Domino server will include product information such as the server version. 0 – Domino-generated SMTP Received header will contain Domino server product information, which includes the server version. 1 – Domino-generated SMTP Received header will not contain Domino server product information. | SMTPNoVersion InRcvdHdr = value | There is no UI equivalent. |
| SMTPMaxFor Recipients Applies to: Servers | Determines how many addresses can be added when the SMTP task adds received headers to messages received. Default setting is 0 messages. | SMTPMaxFor Recipients = number of addresses | There is no UI equivalent. |
| SMTPMTA_Space _Repl_Char Applies to: Clients | Specifies the character the SMTP MTA uses to replace spaces in names. Choices are underline (_) or period (.). The following restrictions apply to using periods as replacement characters: User names in the Domino Directory cannot contain periods. For example, John R. Doe is not valid. You cannot use periods as the domain name separator if you configure Domino domains to appear to the left of the @ sign in mail addresses. If you do, a user name with periods replacing spaces can be confused with domain names separated by periods. The default setting is underline. | SMTPMTA_Space _Repl_Char = character | There is no UI equivalent. |
| SMTPRelayHosts andDomains Applies to: Servers | Forces servers to abide by Domino 5 rules to resolve conflicts between Allow and Deny list entries in the SMTP inbound relay controls. 0 (default) – Entries in the Allow field of the SMTP inbound relay controls take precedence over entries in the Deny fields when there is a conflict between them. For example, given the following entries: Deny messages to be sent to the following external Internet domains xyz.comAllow messages only from the following Internet hosts to be sent to external Internet domains relay.abc.comthe host relay.abc.com can always relay to any destination, including destinations in the domain xyz.com. 1 – Entries in the Deny fields of the SMTP inbound relay controls take precedence over entries in the Allow fields in the event of a conflict. Using the preceding example, if you deny relays to xyz.com, the host relay.abc.com cannot relay to the denied domain. | SMTPRelayHosts andDomains = value | There is no UI equivalent. |
| SMTPSaveImport Errors Applies to: Servers | Specifies whether mail message import errors are recorded, as follows: 0 (default) – No messages are recorded. 1 – When an arriving message fails to be written as a note in MAIL.BOX, Domino writes the data stream to a temporary directory, and logs the name of the file. 2 – All arriving messages have their data streams written to the temporary directory. This feature can use a great deal of disk space because the saved messages continue to accumulate until you delete them. Also, the content of the messages is accessible to anyone with the privileges to read files in the temporary directory. | SMTPSaveImport Errors = value | There is no UI equivalent. |
| SMTPStrict821 AddressSyntax Applies to: Servers | Specifies whether the SMTP task requires addresses that appear in MAIL FROM commands or RCPT TO commands be properly formed according to the 821 standard (must contain <>): 0 (default) – Does not enforce 821 standard 1 – Enforces 821 standard | SMTPStrict821Address Syntax = value | There is no UI equivalent. |
| SMTPStrict821 LineSyntax Applies to: Servers | Specifies whether the SMTP task requires all protocol text be terminated by CRLF: 0 (default) – 821 standard is not enforced (LF is accepted as a line terminator) 1 – 821 standard is enforced | SMTPStrict821 LineSyntax = value | There is no UI equivalent. |
| SMTPTimeout Multiplier Applies to: Servers | Multiplies the SMTP time-out wait value by the specified number. Each SMTP protocol exchange has a time-out wait value. If the client does not respond within the time-out period, the connection is broken. You can increase the time-out period by specifying a multiplier value. For example, a value of 2 doubles all time-out periods. Default value is 1. | SMTPTimeout Multiplier = value | There is no UI equivalent. |
| SMTPVerify AuthenticatedSender Applies to: Servers | The SMTPVerifyAuthenticatedSender = NOTES.INI setting designates whether mail that is sent during an authenticated SMTP session must be from the Internet address of the authenticated users. The intent is to verify that the user is not attempting to spoof the “From” field. This feature is most useful when a Domino SMTP server is configured to enforce authentication, but that is not a requirement. 0 (default) – Do not require the sender to use their Internet address. 1- Require the Sender, or From, if Sender header does not exist, to match the Internet address of the authenticated server. 2 – Require the RFC822 From header to match the Internet address of the authenticated user. Sender is not checked, just From is checked. | SMTPVerify AuthenticatedSender = value | This setting does not affect the Router, nor does it affect messages that are not submitted via SMTP. The SMTPVerifyAuthenticated Sender setting does not work when SMTPTranslateAddresses is configured. Mail is rejected if addresses are translated because the match fails. The features can only be used with single-address entries in the From or Sender field. |
| SSLCipherSpec Applies to: Servers | (SSL users only) Determines which SSL-compliant cipher to use to encrypt files on the server. Specification numbers correspond to the following ciphers:
To enter multiple ciphers, enter each cipher specification value, including leading zeros. Do not include spaces between values. For example: | SSLCipherSpec = value1value2value3… | UI equivalent: SSL ciphers field for each Internet protocol in the Ports – Internet Ports of the Server document. The settings in this field are overridden by the SSLCipherSpec NOTES.INI setting. Specifying a 128-bit cipher for a server with an international license has no effect. |
| SSL_Resumable _Sessions Applies to: Servers | Specifies the number of resumable SSL sessions that will be cached on the server. Setting this variable to 1 disables SSL session resumption on the server. The default number of sessions is 50. | SSL_Resumable _Sessions = number of sessions cached | There is no UI equivalent. |
| SSL_Trace _KeyFileRead Applies to: Servers | Enables viewing of information on the current keyring in use on a Domino server. To enable viewing, set SSL_Trace_KeyFileRead to a value of 1. This enables viewing of protocols other than HTTP to see if there is a valid keyring file present in the server’s Server document or Internet site documents from the server console. There is no default setting. | SSL_Trace _KeyFileRead = value | There is no UI equivalent. |
| SwapPath Applies to: Servers | Specifies the location of the server’s swap file. If this setting exists in the NOTES.INI file, the Reporter or Collector server task uses this location for the Server.Path.Swap statistic. There is no default setting. | SwapPath = location | UI equivalent: None, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Notes.ini settings: T |
| Setting | Description | Example | Comment | |
| TCP_DefaultZone Applies to: Servers | Use this setting to define the default zone for a link local address when IPv6 addressing is being used on a server. Zone is a required parameter for link local and site local addresses, and is used to specify the interface on which the IPv6 address is valid. The zone value can also be specified at the end of the address string specified in the Notes.ini variable TCPIPportname _TCPIPAddress, separated by a percent sign. For example: fe80::209:6bff:fecd:5b93%4 included in the local bound address. | TCP_DefaultZone = value | There is no UI equivalent. | |
| TCP_EnableIPV6 Applies to: Servers | Use this setting to enable Domino for IPv6. There is no default setting, but in the absence of the setting, IPV6 is disabled. 0 – disables the feature 1 – enables the feature | TCP_EnableIPV6 = value | There is no UI equivalent. | |
| TCP/IPportname _PortMappingNN Applies to: Servers | Specifies the TCP/IP port number of each partitioned server sharing the IP address of the port mapping server. TCP/IPportname is the name of the TCP/IP port that is specified in the NOTES.INI file by the settings Ports = TCPIP. This entry is only valid in the NOTES.INI file of the port mapper server. NN is any number from 00, 01, 02, and so on to 99; only 00 to 04 are currently supported. Numbers must be assigned in ascending order as an invalid break in the number sequence causes subsequent entries in the NOTES.INI file to be ignored. For example:
The last number is the port number assigned to each partitioned server. This number must be an available number as specified in Assigned Numbers RFC 1340. When setting NOTES.INI variables for port mapping, do not inclde a zone in a port-mapped address. The zone is only valid locally. There is no default setting. | TCP/IPportname _PortMappingNN = CN=servername/ O=organization, IPaddress:TCP/IP portnumber | There is no UI equivalent. | |
| TCP/IPportname _TCPIPAddress Applies to: Servers | Defines the IP address and port number for a Domino server. TCP/IPportname is the name of the TCP/IP port which is specified in the NOTES.INI file by the setting Ports = TCPIP. For example: TCP/IPportname _TCPIPAddress = 0, 192.94.222.169:1352. There is no default setting. | TCP/IPportname _TCPIPAddress = 0,IPaddress:TCP/IP portnumber | There is no UI equivalent. | |
| Temp_Index _Max_Doc Applies to: Servers | Specifies the maximum number of results (up to 2147483647) that can be retrieved at one time — by an agent running on a server — on a database without any index. For example, specifying Temp_Index_Max_Doc = 10000 allows a single NotesDatabase or NotesDocumentCollection “FTSearch” running on a server to return up to 10000 entries. To use the Temp_Index_Max_Doc setting for an agent running on a server, you must also use the FT_Max_Search_Results setting and specify the same value, for example FT_Max_Search_Results = 10000. Default setting is 5000. | Temp_Index _Max_Doc = number of entries | There is no UI equivalent. | |
| TimeSeparator Applies to: Servers | Specifies the character used to separate values for time – for example 12:01. Any characters can be used as separators. There is no default setting. | TimeSeparator = character | There is no UI equivalent. | |
| TimeZone Applies to: Servers and clients | Specifies the time zone for a server or workstation. Time zones begin at Greenwich, England (0 = Greenwich Mean Time) and move westward around the world. The time zones can be 15, 30, 45, or 60 minutes apart (not all zones are an hour apart). For example:
The default setting is defined during the workstation or server setup procedure. | TimeZone = value | UI equivalent: On a workstation, the Local time zone field in the Location document; on a server, the Local time zone field in the Server document. | |
| Topology _WorkInterval Applies to: Servers | Use this setting to specify how often the Maps server add-in task updates the topology map data in the Domino Directory. Once set, it will refresh n hours after the maps add-in program is started, and every n hours after that. You should not use the setting to refresh too frequently, because the map data is stored in your Domino Directory and updates are replicated throughout the domain. There is no default setting, however the Topology maps task normally refreshes topology information once a day, every night at 2 am. | Topology _WorkInterval = number of hours | There is no UI equivalent. | |
| TransLog_MaxSize Applies to: Servers | The maximum size, in MB, for the transaction log. A value of at least 192 MB is recommended. If you don’t specify a value, the system determines a log size approximately three times the size of the server’s RAM. There is no default setting. | TransLog_MaxSize = number of megabytes | UI equivalent: “Maximum log space” field in the Transactional Logging tab of the Server document. | |
| TransLog_Path Applies to: Servers | Specifies the path to the transaction log. The default location is \logdir in the server’s data directory – for example c:\data\logdir. However, it is strongly recommended to store the transaction log on a separate mirrored device, such as a RAID level 0 or 1 device with a dedicated controller. If you change this field and have an existing transaction log, you must use the operating system to move all the log files to the new log path. | TransLog_Path = path | UI equivalent: “Log path” field in the Transactional Logging tab of the Server document. | |
| TransLog _Performance Applies to: Servers | Specifies the trade-off between transactional log runtime and restart recovery time, as follows: 1 – Favor runtime. The system stores more database changes in memory writes fewer changes to the transaction log. Fewer writes to disk improves server runtime. 2 – Standard (default) 3 – Favor restart recovery time. The system stores fewer database changes in memory and writes more changes to the transaction log. More writes to the transaction log improves restart recovery time. | TransLog _Performance = value | UI equivalent: “Runtime/Restart performance” field in the Transactional Logging tab of the Server document. | |
| TransLog_Status Applies to: Servers | Enables transaction logging for all Domino databases on the server, as follows: 0 (default) – Disabled 1 – Enabled | TransLog_Status = value | UI equivalent: “Transactional logging” field in the Transactional Logging tab of the Server document. | |
| TransLog_Style Applies to: Servers | Specifies the type of transaction logging. Options are as follows: 0 (default) – Circular. The system continuously reuses the extent log files, overwriting old transactions. 1 – Archive. The system does not reuse extent log files and allows you to use a backup utility to archive log files. This is recommended. | TransLog_Style = value | UI equivalent: “Logging style” field in the Transactional Logging tab of the Server document. | |
| TransLog_UseAll Applies to: Servers | Specifies whether or not to use all available disk space on the log device, as follows: 0 (default) – The system uses the default or specified value in “TransLog_MaxSize.” 1 – Use all available space on the disk for the transaction log extent. This is recommended if you use a separate device dedicated to storing the extent. | TransLog_UseAll = value | UI equivalent: “Use all available space on log device” field in the Transactional Logging tab of the Server document. | |
| Notes.ini settings: U | ||||
| Setting | Description | Example | Comment |
| Update_Disable_Fulltext Applies to: Servers (Domino 7 only) | Set this variable to 1 to disable fulltext indexing for the update server task only. Fulltext indexing will still work in the updall server task. There is no default setting. | Update_Disable_Fulltext = value | There is no UI equivalent. |
| Update_Disable_Views Applies to: Servers (Domino 7 only) | Set this variable to a value of 1 to disable view updating for the update server task only. View updating will still work for the updall server task. There is no default setting. | Update_Disable_Views = value | There is no UI equivalent. |
| Update_Fulltext_Thread Applies to: Servers (Domino 7 only) | Set this variable to 1 to use a separate thread to do full text indexing, so that long full text indexes don’t delay view updates. By default, view updates and FT index updates are driven by the same thread. View updating will still work in updall. There is no default setting. | Update_Fulltext_Thread = value | There is no UI equivalent. |
| Update_Idle_Time Applies to: Servers | Specify the number of seconds between update operations if the update server task is running. Default setting is 5. | Update_Idle_Time = number of seconds | There is no UI equivalent. |
| Update_Idle_Time_MS Applies to: Servers (Domino 7 only) | Specify the number of milliseconds between update operations if the update server task is running. Default setting is 5. | Update_Idle_Time_MS = number of milliseconds | There is no UI equivalent. |
| Update_No_BRP_Files Applies to: Servers | Determines whether or not the Fixup task creates BRP files. When set to 1, the Fixup task will not create a BRP file when it encounters an error in a view index. There is no default setting. | Update_No_BRP_Files = value | There is no UI equivalent. |
| Update_No_Fulltext Applies to: Servers | Turns off full-text indexing on a server. 0 – Turns full-text indexing on 1 – Turns full-text indexing off There is no default setting, although if this setting is omitted, full-text indexing is on. | Update_No_Fulltext = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Updaters Applies to: Servers | Specifies the number of Update server tasks that can run concurrently on the server. You must shut down and restart the server for this setting to take effect. There is no default setting, although if this setting is omitted, only a single Update task can run at a time. | Updaters = number of tasks | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Update_Suppression_Limit Applies to: Servers | The Update Task (indexer) maintains two work queues – an immediate queue and a deferred queue. Deferred update requests are held for 15 minutes before they are processed so that requests to update the same database in that time are ignored as duplicate requests. Updater queues can grow if the server has a high update rate because of heavy database use. Use this variable to limit the size (number of requests) in the Update task’s deferred requests queue. Default setting is 32767. | Update_Suppression_Limit = value | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| Update_Suppression_Time Applies to: Servers | The Update Task (indexer) maintains two work queues – an immediate queue and a deferred queue. Deferred update requests are held for 15 minutes before they are processed so that requests to update the same database in that time are ignored as duplicate requests. Updater queues can grow if the server has a high update rate because of heavy database use. Use this variable to specify the length of time that deferred update requests are held in queue.
The default value is 15. | Update_Suppression_Time = length of time | There is no UI equivalent, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino Directory. |
| UpgradeApps Applies to: Servers | Specifies custom upgrade applications for migrating users to Notes. Domino includes four upgrade applications for migrating users to Notes, one each for cc:Mail, Windows NT, Exchange, and LDIF. In addition, you can use UpgradeApps to add one or more custom upgrade applications (DLL files) to the Registration dialog. Use commas to separate multiple names. Specified files must reside in the Notes program directory. UpgradeApps does not affect the upgrade applications that ship with Domino. There is no default setting. | UpgradeApps = file name1, file name2, file name3… | There is no UI equivalent. |
| UseFontMapper Applies to: Servers and clients | Determines whether the font mapper is used to guess the closest mappings between the font face name in a CGM metafile and the currently installed fonts on a Notes workstation. 1 (default) – Enables the font mapper 0 – Disables the font mapper | UseFontMapper = value | There is no UI equivalent. |
| $Use_ST_IM Applies to: Clients | Applies to Notes Application Plug-in. Specifies which Instant Messaging provider the Notes Application Plug-in (NAP) uses. 1 — Sametime Instant Messaging 0 (default) — Workplace Instant Messaging | $USE_ST_IM = value | UI equivalent: This value can be set through the ‘Instant Messaging Provider’ desktop policy setting, or, in the User Preferences – Additional Options – ‘Use IBM Lotus Sametime Instant Messaging’. |
| Notes.ini settings: V |
| Setting | Description | Example | Comment |
| ViewExpnumber Applies to: Servers and clients | Specifies parameters to be used by file exports done at the view level. There is no default setting.
| ViewExpnumber = value1, value2… | There is no UI equivalent. |
| View_Rebuild_Dir Applies to: Servers | Specifies the directory where temporary files will be created for optimized view rebuilds. For example, to set the directory to my_view_rebuild_directory, enter the following line in the NOTES.INI file: View_Rebuild_Dir=c:\my_view_rebuild_directory There is no default setting, but in the absence of this setting, the system’s temporary storage directory (specified by the TEMP or TMP environment variables) is used. | View_Rebuild_Dir = path | There is no UI equivalent. |
| Notes.ini settings: W |
| Setting | Description | Example | Comment |
| WCT_IM_Use_Lookup Applies to: Servers and clients | Applies to Notes Application plug-in. Specifies which method will be used for IBM Workplace instant messaging name resolution (converting Notes names to Internet names) in the Notes Application Plug-in (NAP). 1 – Domino Directory 0 (default) – IBM Workplace | WCT_IM_USE_LOOKUP = value | This value can be set through the ‘Primary instant messaging name resolution performed by’ desktop policy setting. |
| WebAuth_Verbose_Trace Applies to: Servers | Use this setting to troubleshoot problems with Web server user authentication and Web server group searches for database access verification. With the setting enabled, a Domino Web server records detailed information about specific Web user authentication sessions at the server console. Information includes authentication success or failure, group cache information used to verify Web users’ membership in groups for database access control, and the search filters used to find user and group entries in an LDAP directory. 0 – disabled 1 – enabled After you correct the problem, be sure to disable this feature (or remove the setting altogether), because it slows Web server performance. There is no default setting. | WebAuth_Verbose_Trace = value | There is no UI equivalent. |
| WebSess_Verbose_Trace Applies to: Servers | This setting should be used to troubleshoot both single server and multi-server (single sign-on) session-based authentication problems. When enabled, the setting allows a Domino Web server to record, at the server console, detailed information about specific Web session-based authentication sessions, such as unauthorized, unauthenticated, or session expiration information. 0 – Disabled 1 – Enabled After you correct the problem, be sure to disable this feature (or remove the setting altogether), because it slows Web server performance. There is no default setting. | WebSess_Verbose_Trace = value | There is no UI equivalent. |
| Window_Title Applies to: Servers and clients | Uses the specified text on the title bar. There is no default setting. | Window_Title = text | There is no UI equivalent. |
| WinInfoboxPos Applies to: Clients | Determines the position of the InfoBox. Default setting is 85, 193. | WinInfoboxPos = value1, value2 | There is no UI equivalent. |
| WinSysFontnumber Applies to: Clients | All CGM metafiles contain numeric font identifiers 1 through x, where x is the maximum number of fonts in an optional CGM font face name table. When the font mapper is disabled, these lines list the installed Windows system fonts to which the CGM font numbers are mapped. There is no default setting. | WinSysFontnumber = value1, value2, value3 | There is no UI equivalent. |
| Notes.ini settings: X |
| Setting | Description | Syntax | Comment |
| XPC_Console Applies to: Servers and clients | Displays the XPC console, which shows modem input/output (if logged). 1 – Displays the console 0 (default) – Hides the console | XPC_Console = value | There is no UI equivalent. |
Installing Lotus Domino on Linux
Installing Lotus Domino on Linux
Last month, we tried to make a business case for deploying Domino for Linux within a small to mid-sized enterprise. We hope that this issue will provide you a detailed installation tutorial on getting Domino up and running under Linux. In order to make the article manageable, we had to make some assumptions about your environment and your expertise with operating systems, in particular, Red Hat 6.2 and Domino. If you need any instructions on setting up a Linux environment, there are many great resources online. You can find our recommendations in the product availability section at the end of this article.
System requirements
In order to install Domino R5 under Linux, the following minimum requirements must be met:
- 486 processor or later;
- 64MB RAM or larger (128MB is recommended);
- Swap file of two times the physical RAM or greater;
- 750MB free space hard drive space or larger;
- Linux kernel version 2.2.5. This installation has been certified on Red Hat 6.0 and above.
Installing Red Hat 6.2
Before installing Domino, the Linux environment needs to be installed and configured. The good news is that Red Hat is very straightforward to install. Just follow these steps:
- Obtain Red Hat 6.2. Every version of Red Hat provides different features and levels of support. For our installations, we used the standard version;
- Boot from CD. If your system doesn’t provide this support, boot from the floppy disk provided by Red Hat;
- Use the “Server” installation. Red Hat provides different customized installations of Linux. Simply follow the steps throughout the installer.
System preparation
Before getting started with Domino installation, a few tasks must be completed. These tasks include shutting down both the SendMail SMTP (Simple Mail Transfer Protocol) Server and the Apache Web Server.
Disable SendMail
Since Domino provides its own set of SMTP services, we need to disable the standard SendMail service within Linux. First, log in to your system as “root.” In order to stop SendMail, type the command:
/etc/rc.d/init.d/sendmail stop |
This will disable the SendMail server. Note that this doesn’t uninstall the program; it will only shut it down. The next step is to keep it from running automatically after the system reboots. Open the file /etc/rc.d/init.d/sendmail in your favorite editor. Then find the lines:
echo -n "Starting sendmail:" daemon /usr/sbin/sendmail -bd -qlh echo touch /var/lock/subsys/sendmail ; ; |
Comment them out by typing a “# ” at the beginning of each line and save the file.
Disable Apache Web Server
In addition to the SendMail service, we need to disable the Apache Web Server, if it’s installed. First, log in to your system as “root.” To stop the Apache Web Server, type the command:
/etc/rc.d/init.d/httpd stop |
As with the SendMail server, we now need to prevent the Apache Web Server from starting when the server is rebooted. To do this, type the following command:
rm /etc/rc.d/init.d/httpd |
Using Linuxconf to disable Daemons
Linuxconf is a powerful tool that can be used to monitor system activities, add and remove users, adjust system variables, and control the way your system starts. Linuxconf can be run from the command line, a Web interface, or within X-Windows.
If you’re unfamiliar with the command line and prefer a more graphical tool, you can use Linuxconf to disable servers.
To disable SendMail and Apache using Linuxconf, start Linuxconf from either the command line, GUI (Graphical User Interface) icon (in X-Windows), or by pointing your browser to http://machinename:98. (You must have enabled Web access for Linuxconf to use this method).
From the main menu, choose Control. Next, choose Control Service Activity. You should see a long list of services with two columns labeled “Enabled” or “Disabled.” To disable Apache, find the httpd entry and switch the column from Enabled to Disabled. To disable SendMail, find the SendMail entry and choose Disabled. Save and set your changes to “Active.”
Acquiring the software
Lotus provides a couple of ways that you can obtain your very own copy of Domino for Linux. As we talked about last month, IBM is providing an exceptional deal called the Small Business Pack for Linux. One of the components of the suite is Domino R5 Application Server for Linux. If you’re interested in a 90-day trial of R5, you can download a packaged file from Notes.Net at http://www.notes.net/linux.
Creating a user for Domino
Under Linux, each user “owns” specific processes, so we need to create a user for Domino. Again, log in as “root.” Create a new user. For example, you could call the user “notes,” in which case you’d type in”adduser notes”. Then you have to set the password for the new user. Type in, for example: “passwd notes”.
Installing partitioned servers
As with other distributions of Domino, during the installation process you’ll be asked if you want to install more than one Domino server on a single computer. For each server you want to run, a different user name needs to be used to distinguish between processes.
Installing Domino
There are different instructions on installing Domino depending on how you obtained the software.
Software on CD
If you have the software on CD, log in as “root”. Before you can use the CD under Linux, you need to mount the drive. Insert the CD in the drive and type: “mount /mnt/cdrom”. Change directories to CD with, “cd /mnt/cdrom”. Change directories to the Linux installer with “cd Linux”. Finally, run the installer with “./install”.
Software on the .TAR file
If the software is on the .TAR file, again log in as “root”. In order to put the .TAR file on the server, you can FTP it to the server or download it directly on the server. (See http://www.wu-ftpd.org/ on how to install an FTP server and see http://www.linuxdoc.org/HOWTO/mini/FTP.html for how to use the FTP command.) Where ever you downloaded the file to, for example “/tmp/domino”, change to that location with “cd /tmp/domino”. In order to run the installer, we need to uncompress the files. If your file was called, “domino.tar”, execute the following command: “tar xvf domino.tar”. Change directories to the Linux installer with “cd Linux” and run the installer with “./install”.
Software agreement
The installer will prompt you with several screens about the Lotus Notes and Domino Software Agreement. Simply press Tab to continue forward and Escape to go back to the previous screen in the installation process. These two keystrokes will be used throughout the installation process to navigate the screens.
Server type
Domino provides three different types of server setups. Choose from the Domino Mail Server, Domino Application Server, or Domino Enterprise Server.
Program directory
Next, Domino asks you about where you want to install the program files for this installation. The default is “/opt/lotus/”. If you want to change this option, press Enter to edit the path.
Installing partitioned servers
As with other distributions of Domino, during the installation process you’ll be asked if you want to install more than one Domino server on a single computer. The default is “No.” However, if you want to run partitioned servers, you’ll need a different user name for each instance of the Domino server. Linux gives each a distinctive user name to distinguish between processes.
Data directory
The installation program will next ask for the location you want to install the data files for this instance of the server. The default is “/local/notesdata/”.
Domino user name and group
Previously, you should have created a user that will own the Domino data files and the server processes. Simply specify the user name and group that you will use. The user name must be a member of the group that you specify. The default is “notes.”
Let it rip
Finally, everything has been configured for the installation, and you’re ready to install the files. Press either the Escape key to re-configure your settings or the Tab key to begin the installation process. After the installation is complete, logoff as the “root” user.
Running the Domino Server Setup
Log into the system as the user name you created before, i.e., “notes.” Change directories to the notes data directory:
cd /local/notesdata |
To launch the HTTP setup, use this:
/opt/lotus/http httpsetup |
Upon execution of the HTTP setup, you should see a log of your activities with date and time stamps.
Completing the configuration
To continue on with the configuration, you need to finish the setup on a computer with a Web browser. Simply connect to the server by specifying the server’s address and port via a browser. For example: http://someserver.somecompany.com:8081.
Is it looking familiar yet? You should see the standard Domino configuration screen, as pictured in Figure A.
Here’s the standard Domino configuration screen. Roll over picture for a larger image.
As you’ve done before, follow the instructions and complete the installation, as seen in Figure B.
FIGURE B
Follow the instructions and complete the installation. Roll over picture for a larger image.
Starting the server
Log into the system as the user name you created previously, i.e., “notes.” Change directories to the notes data directory:
cd /local/notesdata |
Launch the server with:
/opt/lotus/bin/server |
Getting the administrator’s ID file
Once the HTTP service has started, you need to point a Web browser to the server’s address book to get your ID file with something like http://someserver.somecompany.com/names.nsf. Log into the server using the administrator’s name and password and go to the “People” view to find your document. Attached to the document will be the ID file, i.e., “user.id.” Note: The “server.id” and “cert.id” are located in the Notes data directory.
Since you now have your ID file, you can open your Notes client and continue to configure and administrate the server.
Tools of the trade
During the administration of Linux servers, we have found a few gems that really assist us in configuration and daily administration.
- WebMin (at http://www.webmin.com): If you’ve been enjoying the convenience of the Domino Web administration tool, you’ll love this tool. One of our personal favorites is this powerful Web-based administration interface for Unix systems like Linux. This daemon allows you to configure DNS, Samba, NFS, and local/remote file systems, and it even lets you reboot your server.
- OpenSSH (at http://www.openssh.com): This is a free version of the SSH (Secure Shell) Server. OpenSSH replaces telnet and ftp with a secure client that encrypts transmissions between the client and server. Most importantly, the SSH Server avoids sending passwords directly and instead sends an encrypted key to the server which allows you to login.
- Tera Term Pro and TTSSH Plug-in (at http://www.priz.net/support/ttssh.html): This is a powerful freeware telnet client. The TTSSH plug in is a freely available add-on that will allow you to connect to your remote server using the SSH protocol
Instalando Domino 7.0.1 en Ubuntu
En Ubuntu necesitas las librerias: (Un de las librerias no la necesité pero no me acuerdo cual)
- Libstdc++
- Libc6.1-1.so.2
- Libglibz.0-0
- Java SDK 5
- Java SDK 6
Dar de Alta el grupo Notes
Dar de Alta un usuario para ese grupo (con el home en /local/notesdata)
Ir a una pantalla shell o consola
Copiar el instalador a un directorio. Yo lo copie a /opt/dom701
Con usuario root ir al directorio donde esta el instalador e iniciarlo:
/opt/dom701/linux/./install
Dejé todas las opciones de Default salvo estas dos :
- Current program directory settings: /opt/lotus
- Current data directory settings: /local/notesdata (directorio home del usuario notes)
- Current UNIX user setting : notes (usuario para notes)
- Tipo de instalacion : Local Server Setup
Si falta alguna librería aca te va a decir que te fijes en ????? (algo de noteslog o install), hay que instalar las librerias y comenzar nuevamente
Una vez que termina la instalación, cambiar el usuario por notes, sobre el directorio home del usuario iniciamos el setup : /opt/lotus/bin/server
Una vez configurado se inicia como el punto anterior con el usuario notes /opt/lotus/bin/server
Cómo usar un modem en gnu/linux
Hay muchos modems que funcionan sin problema en gnu/linux. Lo primero que haremos será determinar en qué puerto debe funcionar nuestro modem dial up. Antiguamente los modems traían puentes dentro de su placa que permitían cambiar manualmente su configuración. Esto, en la actualidad es solo historia, ya que no hay tal cosa.
Normalmente los modems se instalan en puertos serie directamente conectados al motherboard o bien, si son modems externos lo harán a un puerto que tiene un conector ubicado en la parte de atrás del gabinete de la computadora.
Para conocer qué puerto serie asigna nuestro sistema operativo a un determinado modem, debemos ir al directorio ‘/dev’ donde se encuentran los dispositivos y desde allí con el comando ‘ls’ listar los dispositivos existentes.
Allí buscaremos los puertos serie que aparecerán como ‘tty’ junto al correspondiente número de puerto. Veamos las equivalencias de puertos entre Gnu/Linux y DOS
| Dispositivo gnu/linux | Nombre en Dos | dirección e interrupción |
| /dev/ttyS0 | COM1 | 0×3F8….IRQ4 |
| /dev/ttyS1 | COM2 | 0×2F8…..IRQ3 |
| /dev/ttyS2 | COM3 | 0×3E8…..IRQ4 |
| /dev/ttyS3 | COM4 | 0×2E8…..IRQ3 |
Debemos tomar en cuenta que algunos modems -conocidos como winmodem tienen limitaciones para su funcionamiento en gnu/linux. Estos modem en realidad no realizan todas las funciones necesarias dejando parte de su trabajo al microprocesador.
Si bien existen formas de solucionar el problema y numerosos desarrolladores han realizado trabajos para que estos funcionen también en gnu/linux, no todos funcionan.
Además tanto en gnu/linux como en cualquier Sistema Operativo (aún en Windows para el que fueron creados) su rendimiento es siempre inferior al de un modem clásico. Normalmente todos los modem externos funcionan sin problema en gnu/linux y tienen un rendimiento muy superior a cualquier Winmodem, aunque son más caros. También los modem antiguos de placas tipo ISA por lo general funcionan sin problema, y aunque su velocidad nominal (por ser antiguos) pueda ser menor, seguramente lograrán mejor velocidad que algunos modem más modernos con velocidad nominal superior pero winmodem.
1.1 Usando el comando dmesg para comprobar el puerto serie:
Lo primero que haremos será ver si los puertos serie están activados y para esto utilizaremos el comando dmesg . Este comando nos muestra en un documento lo mismo que vemos en la pantalla a gran velocidad durante el inicio. Es de gran ayuda a la hora de ver errores e intentar configuraciones nuevas.
Normalmente hay un path por lo que con solo tipear ‘dmesg’ en la línea de comandos alcanzará. De no ser así podemos utilizar la ruta completa ‘/var/log/dmesg’.
‘dmesg’ es un archivo grande -nos muestra todos los controladores y puertos funcionando- por lo que debemos saber qué buscar.
Por ejemplo escribiendo ‘dmesg’ en línea de comandos de mi computadora encuentro entre muchas otras cosas lo siguiente:
……..
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0×3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0×3f8 (irq = 4) is a 16550A
……
En otra computadora tal vez podría haber encontrado:
Serial driver version 5.24 with no serial options enabled
Una forma práctica de encontrar lo que buscamos con rapidez puede ser:
dmesg | grep serial
En este caso lo que correspondería es habilitar el dispositivo serial. También es posible que no haya ninguna referencia a un dispositivo de este tipo por lo que habría que crearlo mediante makedev. De la página de man makedev extraemos lo siguiente:
DESCRIPCIÓN:
MAKEDEV es un script que va a crear los dispositivos en /dev usados como interface con drivers en el kernel.
Note que los programas que den un error ‘‘ENOENT: No such file or direc‐
tory’’ normalmente significan que el archivo de dispositivo está perdido o que no está configurado o cargado el driver.
OPCIONES MÁS COMUNES
-n No actualizar los dispositivos, solamente informe las acciones que van a ser realizadas.
-d Borra los dispositivos.
-v Verboso. Nos muestra las acciones a medida que estas se van realizando, es similar a la salida generada por -n.
PERSONALIZACIÓN
Tomando en cuenta que lo normal es que no hay estandarización sobre el nombre utilizado para usuarios y grupos del sistema, es posible que usted necesite modificar MAKEDEV para que refleje la configuración de su host. Cerca de la parte de arriba del archivo hay un mapeo del dispositivo al usuario, grupo, y permisos (ejemplo: todos los dispositivos de CD ROM estan configurados como una variable y por lo tanto escritos como $cdrom).
Si deseamos cambiar la forma predeterminada, esta es la sección para editar.
OPCIONES GENERALES
update
Esto solo funciona en kernels que tienen /proc/interrupts (intro‐
ducidos durante 1.1.x). Este archivo es escaneado para ver qué dispositivos están configurados corrientemente en el kernel y esto
es comparado con la configuración previa almacenada en el archivo llamado ‘Devices’.
Dispositivos que son nuevos o tienen numeración diferente son creados, y aquellos que no están más configuradas son borradas.
generic
Crea una subconfiguración de dispositivos genéricos. Esta subconfiguración es en realidad un conjunto de dispositivos estandar, además de drives de disqueteras, varios discos rígidos, CD.ROM, pseudo teminales de consola, terminales de consola, dispositivos de audio, puertos de impresora, etc. Esta subconfiguración puede variar de acuerdo a la arquitectura.
DISPOSITIVOS ESTANDAR
std Crea este grupo de dispositivos estandar:
mem para acceso físico a la memoria
kmem para acceso a la memoria virtual
null device puerto para acceso a I/O ports (puertos de entrada/salida),
DISPOSITIVOS SERIALES
ttyS{0..63}
Puertos seriales estandar. ttyS{0..3} es creado en las opciones genéricas en la mayor parte de las arquitecturas.
El manual es mucho más largo y tiene mucha información por lo que si en algun momento necesitamos generar un dispositivo lo ideal es ir a man makedev
Creando los dispositivos
./MAKEDEV -v generic: Creará dispositivos genéricos. Normalmente, estos dispositivos son todos los que se necesitan. Es posible que no se encuentre algún dispositivo más bien especial, y en ese caso se puede crear mediante
./MAKEDEV -v <device>. Donde <device> será el nombre del dispostivo a crear.
Para saber más sobre makedev, podemos ver el manual en línea que tenemos en nuestra computadora escribiendo en línea de comandos:
man makedev
1.2 Probamos el modem con el comando ‘echo’
Debemos seguir los siguiente pasos:
a) Como root, y con el modem conectado y si es interno activado en el BIOS, conectamos también a la línea telefónica.
b) Desde el manual del modem averiguamos cual es el puerto habilitado. Si el mismo aparece con nomenclatura para Windows, utilizamos la tabla anterior para elegir el tty adecuado.
c) Desde consola escribimos lo siguiente:
echo ATDT/n > /dev/ttySN
Habrá que esperar no más de 10 segundos y se deberá escuchar el tono de acceso telefónico.
No todos los modem tienen normalizados los comandos AT. Por este motivo conviene tomar como referencia el propio manual del modem o bien entrar en la página del fabricante para saber si estamos utilizando un comando AT adecuado.
1.3 Activando el servicio de acceso telefónico
Buscaremos el soporte PPP y para esto vamos a escribir en línea de comandos:
dmesg | grep PPP
Si este no estuviese habrá que instalarlo lo que en algún caso puede llevarnos a tener que compilar un kernel. Es posible que en kernel más nuevos no se encuentre esta utilidad, ya que cada vez son más los que utilizan otros estándares de comunicación. Como modem adsl (con protocolo pppoe o PPP over ethernet), o placa de red para conexión a una red, etc.
Para realizar la comunicación tipo dial-up con nuestro proveedor de servicios de internet (ISP) necesitamos dos programas:
*Programa de marcado telefónico y logueo con nuestro ISP (chat)
*Programa que establezca la comunicación PPP conocido como demonio PPP (pppd)
1.4 Activando el modem
Si las cosas no resultaron con las instrucciones anteriores, veremos un paso a paso un poco detallado para winmodems a continuación:
Lo primero que haremos será averiguar cual es el chipset de nuestro modem. ¿qué es el chipset? Es ese pequeño circuito integrado (normalmente negro con muchas patas) que encontramos en la placa del modem. Si no tenemos acceso a nuestro CPU, (para ver directamente el número del chip) ya sea por la faja de garantía o porque no nos animamos a abrirlo, nos podremos fijar en la documentación del modem. También es posible desde http://linmodems.technion.ac.il/packages/scanModem.gz
bajar una herramienta llamada ‘SCANMODEM TOOL’ Luego de bajada haremos lo siguiente para instalarla:
# gzip -d scanModem.gz
luego de descomprimido nos ocuparemos de los permisos mediante:
# chmod +x scanModem
y finalmente lo pondremos en marcha
# ./scanModem
Como vemos existen diferentes maneras de llegar a saber qué chipset tiene nuestro modem.
Ahora la pregunta sería ¿para qué quiero saber cual es el chipset de mi modem? Muchas marcas de modem utilizan el mismo chipset. En realidad es como si un mismo ‘motor de automovil’ funcionara en diferente carrocería con diferentes marcas.
Realmente lo que nos interesa es el ‘chipset’ y no la marca.
También podemos buscar dentro de nuestra computadora. Por ejemplo si nuestro modem es interno y es PCI podemos usar el comando ‘lspci’ Veamos como:
root@losindios:~# lspci
Y aquí vemos una posible respuesta:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] AC’97 Modem Controller (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC’97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1)
root@losindios:~#
En este caso hemos tenido suerte ya que la línea 6 dice (indicada en negrita):
00:02.6 Modem: Silicon Integrated Systems [SiS] AC’97 Modem Controller (rev a0)
Para modem muy antiguos que funcionan en tarjetas tipo ISA existen comandos como isapnp o pnpdump pero no todas las distribuciones las traen ya que se trata de modems muy viejos.
De todos modos es bueno saber que los modem ISA en general, aunque de poca velocidad no son winmodem y por lo tanto funcionan muy bien en gnu/linux.
Si el modem funcionara por medio de una tarjeta PCMCIA (especialmente para notebooks) el comando sería:
root@losindios:~# cardctl ident
En este caso no hay PCMCIA en la máquina por lo tanto no figura nada en /proc/devices
El mensaje que aparecerá será algo así:
no pcmcia driver in /proc/devices
root@losindios:~#
Finalmente con alguno de estos métodos encontramos el chipset y entonces podemos desde Internet con algún buscador encontrar si tenemos algún driver diseñado para gnu/linux.
Cada modem tiene una forma diferente de instalarse así, que vamos a tomar uno bastante común, pero en todos los casos seguramente se podrá encontrar un archivo README dentro del paquete del driver que nos orientará cómo realizar el trabajo.
En nuestro caso vamos a referirnos al modem que hemos detectado (Modem: Silicon Integrated Systems [SiS] AC’97)
Utilizando el programa ScanModem de linmodems.org reconoce el modem como via 82XX- con un controlador de sonido ac’97; esto en rigor a la verdad no es del todo correcto ya que se trata de un SIS y no de un VIA, pero de todos modos nos orienta en la búsqueda. En Internet en:
http://linmodems.technion.ac.il/pctel-linux/welcome.html
pctel-0.9.7-9.rht-6.tar.gz
Esta versión (6) es una modificación de pctel-0.9.7-9.rht-5.tar.gz para poder trabajar con el núcleo 2.6.16 y otros de versión 2.6.
Instalación
Como root vamos a descomprimir el paquete en cuestión
# gzip -d pctel-0.9.7-9-rht-6.tar.gz
Una vez que descomprimimos desempaquetamos con .tar
# tar -xvf pctel-0.9.7-9-rht-6.tar
luego nos posicionamos en el directorio recién creado a fin de utilizar ./configure
# cd pctel-0.9.7-9-rht-6/src
y luego utilizaremos ‘configure de la siguiente manera:
# ./configure -auto
Finalizado el trabajo de configuración abrimos el paquete ’setup’, el que una vez ejecutado conectará nuestra máquina a Internet.
Cada vez que conecto a Internet debo ejecutar setup, aunque tal vez sea posible hacer un script que lo automatice. Eso ya sería otra historia.
1.5 Configurar el servicio de fax del modem
Podemos utilizar efax para esta tarea. También es posible utilizar mgetty y sendfax. Hay buena información sobre qué software utilizar en
http://freshmeat.net
Los paquetes de efax se encuentran con synaptics para Ubuntu sin problema.
Para la configuración modificaremos el script de fax que podemos ubicar en /usr/bin/fax. Mediante nuestro editor de texto preferido vamos a editar el archivo en cuestión:
Buscamos la ruta para los programas de efax y confirmamos que sea la siguiente:
FAX=/usr/bin/fax
EFAX=/usr/bin/efax
EFIX=/usr/bin/efix
De acuerdo al puerto serie que vayamos a utilizar debemos modificar la línea que hace referencia a este. Por ejemplo para un puerto serie ttyS0 debería decir:
DEV=ttyS0
Seleccionaremos una sola CLASS
Especificamos nuestro número de teléfono
FROM=<número de teléfono>
Incluimos nuestro nombre o el de nuestra empresa
NAME=<nombre-de-la-empresa>
Indicamos el tamaño de la página de fax predeterminada, comentando todo lo que no nos sirva mediante el signo ‘#’ (sin las comillas), por ejemplo
PAGE=a4
Solo debe quedar especificado un tamaño
Dejar una línea libre al final y guardar.
Para probar la configuración del fax escribimos por medio de la opción de línea de comandos test del script fax:
#fax test
Este script imprimirá tres páginas de información en la pantalla. También en lugar de imprimir la salida podermos redireccionarla de la siguiente manera:
#fax test >> /home/<ususario>/Desktop/test.txt
Si hubiese algún error debemos volver al script y modificarlo. Un puerto serie mal indicado, o especificar más de un CLASS,etc.
Finalmente, vamos a enviar un fax correspondiente a un documento de texto. Para esto utilizaremos desde línea de comandos de la siguiente manera:
# fax send afax<numero_de -telefono> /home/<usuario>/Desktop/text.txt
o el lugar donde se encuentre el archivo a enviar.
Para imprimir un fax recibido desde línea de comandos se puede escribir:
# fax print <nombre_de_archivo_del_fax>
Useful commands for the Linux command line
This short guide shows some important commands for
your daily work on the Linux command line.
arch
Outputs the processor architecture.
$ arch
i686
cat
Outputs the contents of a file.
$ cat lorem.txt
sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut
labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud
exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute
irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat
nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa
qui officia deserunt mollit anim id est laborum.
cd
Change the working directory.
$ cd /bin
chgrp
Change group ownership of files.
$ chgrp games moo.txt
chmod
Change access permissions of files.
$ chmod +x helloworld
chown
Change file owner and group.
# chown root lorem.txt
cksum
each file.
$ cksum lorem.txt moo.txt
lorem.txt
4294967295 0 moo.txt
cp
Copies a file.
$ cp lorem.txt copy_of_lorem.txt
date
Outputs the current date and time.
$ date
3 12:07:09 GMT 2007
df
and available on filesystems.
$ df
/dev/simfs 39845888 218048 39627840 1% /
dir
List directory contents.
$ dir
lorem.txt moo.txt www
du
Estimate file space usage.
$ du -h /bin
7.8M /bin
echo
Display a line of text.
$ echo foobar
foobar
exit
Cause the shell to exit.
$ exit
fgrep
file.
$ fgrep “irure dolor” lorem.txt
consequat. Duis aute irure dolor in reprehenderit in voluptate
find
hierarchy.
$ find hello*
hello_world.c
free
in the system.
$ free
total
used free
shared buffers cached
Mem:
8299892 8287708 12184 0 2641772 1731236
Low:
3581300 3572764 8536
High: 4718592 4714944
3648
-/+
buffers/cache: 3914700 4385192
Swap: 8193140 2335664 5857476
grep
Print lines matching a pattern.
$ grep -i apple fruitlist.txt
apple
groups
account belongs to.
$ groups
games users
head
Output the first part of files.
$ head -2 lorem.txt
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
hostname
network.
$ hostname
anapnea.net
id
your account.
$ id
gid=100(users) groups=35(games),100(users)
kill
End a process.
$ kill -9 18298
(18298) – Operation not permitted
killall
Kill processes by name.
$ killall irssi
Operation not permitted
irssi(13372): Operation not permitted
irssi(22048): Operation not permitted
irssi: no process killed
last
Show listing of last logged in users.
$ last -n 3
Fri May 18 16:17 still logged in
bob pts/2 64.233.183.103
Fri May 18 16:17 still logged in
clare pts/6 72.5.124.61 Fri
May 18 15:54 – 15:55 (00:01)
ldd
Print shared library dependencies.
$ ldd /bin/bash
=> /lib/libncurses.so.5 (0×40023000)
libdl.so.2 =>
/lib/libdl.so.2 (0×40065000)
libc.so.6 => /lib/libc.so.6
(0×40069000)
/lib/ld-linux.so.2 (0×40000000)
ln
Make links between files.
$ ln -s data.txt symlink.txt
logname
Print user’s login name.
$ logname
smallfoot
ls
List directory contents.
$ ls
lorem.txt moo.txt www
man
function.
$ man bash
md5sum
Outputs the MD5 hash sum of a file.
$ md5sum lorem.txt
56da9e37259af34345895883e6fd1a27 lorem.txt
mkdir
Makes a directory.
$ mkdir foobar
mv
Moves a file.
$ mv lorem.txt ipsum.txt
nl
Number lines of files.
$ nl lorem.txt
ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
2 tempor incididunt ut labore et
dolore magna aliqua. Ut enim ad minim
3 veniam, quis nostrud exercitation
ullamco laboris nisi ut aliquip ex ea
4 commodo consequat. Duis aute irure
dolor in reprehenderit in voluptate
5 velit esse cillum dolore eu fugiat
nulla pariatur. Excepteur sint
6 occaecat cupidatat non proident,
sunt in culpa qui officia deserunt
7 mollit anim id est laborum.
nm
List symbols from object files.
$ nm hello_world
_DYNAMIC
0804956c D _GLOBAL_OFFSET_TABLE_
08048474 R _IO_stdin_used
w _Jv_RegisterClasses
08049490 d __CTOR_END__
0804948c d __CTOR_LIST__
08049498 d __DTOR_END__
…
od
Dump files in octal and other formats.
$ od -t x /bin/sh
2376640 00098020 000054d4 00000000 00000000
2376660 00000020 00000000 000000c7 00000008
2376700 00000003 080e6500 0009d4f4 00004ae8
…
pidof
program.
$ pidof fetchmail
22392
ping
Pings a host.
$ ping -c 2 127.0.0.1
(127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.052 ms
— 127.0.0.1 ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.048/0.050/0.052/0.002 ms
ps
Outputs running processes.
$ ps
21542 pts/12 00:00:00 bash
27706 pts/12 00:00:00 ps
pstree
Display a tree of processes.
$ pstree
|-3*[bash---sleep]
|-fetchmail
|-screen-+-bash—irssi
| `-bash—ctorrent
|-screen-+-bash—lisp.run
| |-bash—vi
| |-2*[bash]
| `-bash—lynx
|-2*[screen---bash---irssi]
|-screen—irssi
|-screen—bash
|-screen-+-bash
| `-irssi
|-skjerm—irssi
|-sshd-+-5*[sshd---sshd---bash---irssi]
| |-8*[sshd---sshd---bash]
| |-sshd—sshd—bash—screen
| |-sshd—sshd
| `-sshd—sshd—bash—pstree
`-syslog-ng
pwd
directory.
$ pwd
/home/smallfoot
rm
Removes a file or directory.
$ rm lorem.txt
rmdir
Removes a directory.
$ rmdir foobar
sed
transforming text.
-e ’s/Bob/Mittens/g’
is Mittens
sha1sum
Outputs the SHA1 hash sum of a file.
$ sha1sum lorem.txt
c942ddebd142ec8bacac9213d48096e74bab4957 lorem.txt
shutdown
All logged-in users are notified that the system is going down.
$ shutdown now
size
List section sizes and total size.
$ size /bin/bash
621233 22712 19176 663121 a1e51 /bin/bash
stat
Outputs file status.
$ stat lorem.txt
Size: 453 Blocks: 8 IO Block: 4096 regular file
Device: 77h/119d Inode: 27312217 Links: 1
Access: (0644/-rw-r–r–) Uid: ( 1478/smallfoot) Gid: ( 100/ users)
Access: 2007-03-03 12:24:39.000000000 +0000
Modify: 2007-03-03 12:24:39.000000000 +0000
Change: 2007-03-03 12:24:39.000000000 +0000
strings
characters in files.
$ strings hello_world
_Jv_RegisterClasses
__gmon_start__
libc.so.6
puts
_IO_stdin_used
__libc_start_main
GLIBC_2.0
PTRh%
[^_]
Hello World!
tail
Output the last part of files.
$ tail -2 lorem.txt
cupidatat non proident, sunt in culpa qui officia deserunt
mollit anim id est laborum.
talk
Talk to another user.
$ talk bob Lookout for the dopefish!
touch
timestamps. If file does not exist, create it.
$ touch lorem.txt
tty
terminal.
$ tty
/dev/pts/16
uname
kernel version, date and timp, and processor.
$ uname -a
anapnea.net 2.6.9 #1 SMP Wed Jul 19 16:24:18 MSD 2006 i686 Intel(R) Xeon(TM)
CPU 2.80GHz GenuineIntel GNU/Linux
uptime
Outputs the system uptime.
$ uptime
up 7 days, 17:52, 18 users, load average: 0.08, 0.02, 0.01
users
logged in to the current host.
$ users
charlie eve
vdir
List directory contents.
$ vdir
-rw-r–r– 1 smallfoot users 453 Mar 3 12:32 copy_of_lorem.txt
-rw-r–r– 1 smallfoot users 453 Mar 3 12:24 lorem.txt
-rw-r–r– 1 smallfoot users 0 Mar 3 12:32 moo.txt
lrwxr-xr-x 1 root root 18 Feb 27
19:33 www -> /var/www/smallfoot
w
doing.
$ w
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
charlie pts/0 Fri21 3:26m 2.52s 2.52s irssi
alice pts/2 Wed17 30:21m 0.00s 0.00s -bash
emma pts/4 11:37 36:57 0.00s 0.00s -bash
frank pts/5 11:48 11:03 0.00s 0.00s -bash
smallfoo pts/12 12:01 0.00s 0.04s 0.01s w
wall
Send a message to everybody’s terminal.
one
wc
Counts lines in a file.
$ wc -l lorem.txt
7 lorem.txt
whatis
words.
$ whatis bash
(1) - GNU Bourne-Again SHell
bash [builtins] (1) - bash
built-in commands, see bash(1)
who
system.
$ who
alice pts/2 Feb 28 17:48 (147.21.16.3)
emma pts/4 Mar 3 11:37 (32.84-48-181.uac.com)
frank pts/5 Mar 3 11:48 (port-212-202-233-2.foobar.org)
smallfoot pts/12 Mar 3 12:01 (c-12776f4.cust.example.net)
whereis
page files for a command.
$ whereis bash
/bin/bash /etc/bash /usr/share/man/man1/bash.1.gz
whoami
account.
$ whoami
smallfoot
