Domino® server setup program

The Domino® server setup program guides you through the choices you make to configure a Domino® server. Setting up the first Domino® server in a domain establishes a framework that consists of the Domino® Directory, ID files, and documents. When you set up additional servers, you build upon this framework.

The first Domino® server setup creates IDs with a default public key width of 1024 bits. If a different key width is required, run SETUP.EXE to install the Domino® files but before starting the server, open the server's NOTES.INI file, and then set SETUP_FIRST_SERVER_PUBLIC_KEY_WIDTH to the desired key width. The public key width can be set to either 630 or 1024 when using the NOTES.INI variable.

For information on using Domino Off-Line Services (DOLS) with IBM® iNotes®, see the IBM® iNotes® administration product documentation in the related links.

Setting up the first Domino® server does the following:

  • Creates a Domino® domain.
  • Creates the certification log file, names it certlog.nsf, and saves it in the Domino® data directory.
  • Uses the pubnames.ntf template to create the Domino® Directory for the domain, names the directory names.nsf, and places it in the Domino® data directory.
  • Creates an organization certifier ID, names it CERT.ID, and saves it in the Domino® data directory.
  • Optionally creates an organizational unit certifier ID, names it OUCERT.ID, and stores it in the Domino® Directory.
  • Creates a Certifier document, which describes the organization certifier ID, in the Domino® Directory.
  • Creates a server ID, names it SERVER.ID, and saves it in the Domino® data directory.
  • Uses the organization certifier ID to certify the server ID.
  • Creates a Server document in the Domino® Directory and includes in it information that you specified during the setup program.
  • Creates a Person document in the Domino® Directory for the Domino® Administrator that you specified during the setup program.
  • Creates a user ID and password for the Domino® Administrator and attaches it as a file named USER.ID to the administrator's Person document in the Domino® Directory.
  • Uses the organization certifier ID to certify the administrator's user ID.
  • Gives the administrator and the server Manager access in the ACL of the Domino® Directory.
  • Adds the server name to the LocalDomainServers group in the Domino® Directory.
  • Creates the log file, names it log.nsf, and saves it in the Domino® data directory.
  • Enables the appropriate network and serial ports.
  • Creates a mail directory in the Domino® data directory and creates a mail file in that directory for the Domino® Administrator.
  • Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino® data directory.
  • Updates network settings in the Server document of the Domino® Directory.
  • Configures SMTP, if selected during the setup program.
  • If DOLS Domino Off Line Services was selected during the setup program, creates the Off-Line Services file, names it doladmin.nsf, and saves it in the Domino® data directory,
  • Updates the Access Control List in all databases and templates in the Domino® data directory tree to remove Anonymous access and/or add LocalDomainAdmin access, depending on the selections made during the setup program.

Setting up an additional Domino® server does the following:

  • Copies the Domino® Directory, if a file location was specified during the setup program, names it names.nsf, and saves it in the Domino® data directory.
  • Copies the server's ID from the location specified during the setup program, either from a file, a copy of the directory, or the existing Domino® server's directory; names it SERVER.ID; and saves it in the Domino® data directory.
  • Retrieves the Domain name and Administrator name from the Server document in the Domino® Directory.
  • Creates the log file, names it log.nsf, and saves it in the Domino® data directory.
  • Copies or replicates the Administration Requests file, names it admin4.nsf, and saves it in the Domino® data directory.
  • Copies or replicates the Monitoring Configuration file, names it events4.nsf, and saves it in the Domino® data directory.
  • Replicates the Domino® Directory, if it doesn't already exist, names it names.nsf, and saves it in the Domino® data directory.
  • Creates a Connection document to the existing Domino® server in the Domino® Directory.
  • Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino® data directory.
  • Updates network settings in the Server document of the Domino® Directory.
  • Configures SMTP, if selected during the setup program.
  • If DOLS Domino Off-Line Services was selected during the setup program, creates the Off-Line Services file, names it doladmin.nsf, and saves it in the Domino® data directory.
  • Updates the Access Control List in all databases and templates in the Domino® data directory tree to remove Anonymous access and/or add LocalDomainAdmin access, depending on the selections made during the setup program.
  • Replicates changes made to the Server document with the existing server, if any.
  • Removes the SERVER.ID attachment from the Domino® Directory, if applicable.