Previous Page TOC Next Page



— 10 —


Installing and Configuring Notes Servers



Preparing to Install


To deploy Notes for the first time, or to upgrade an existing Notes installation to Lotus Notes Release 4, you must get an idea about how Notes actually works. Even then, planning your Notes setup is vital, especially for large Notes networks. The better you develop your Notes deployment plan, the less time you will find yourself spending performing administrative maintenance on your network. After you have the preliminaries completed, it is time to deploy and install Notes. This chapter takes a step-by-step look at installing Notes servers. Specifically, it walks you through the Notes installation process on OS/2 and Windows NT servers.

Before you install Lotus Notes, you have to ensure that the computer meets the minimum hardware requirements, the operating system is properly configured, and the necessary operating system network drivers are in place. The importance of planning your Notes network before installation cannot be exaggerated. Planning your Notes network involves architecting and naming your domain(s), organization(s), and Notes Named Network(s); designing a server topology; planning a naming scheme; and deciding names for the servers and users. Changing the design of the Notes network is often a nontrivial task. Notes network design is covered in detail in Chapter 9, "Designing Your Notes Network."

Pre-Installation Planning


Before you still your first production Notes server, be sure to review the following chapters:

It's especially important that you review Chapter 9. If you are migrating from Notes Release 3.x, you also should review Chapter 12, "Migrating from Notes 3.x."

The following sections describe the items that you must plan before installation.

Network Drivers


Lotus Notes is a client/server application that permits groups of people to collaborate by using networks. Server-to-server and client-to-server communications can take place over local area networks (LANs) or wide area networks (WANs). Notes communication also can take place over remote connections, using protocols such as X.25 or X.PC. In order to set up Notes communication on a LAN, the communicating entities (servers and/or workstations) must "speak" the same LAN protocol.

Naming Conventions for Notes Networks


Before setting up the first server in the organization, you should make decisions about the names that you are going to use for the domain, organization, Notes named network, and server. The following sections provide some guidelines for naming conventions and requirements.

Domain Names

A domain name can be up to 31 bytes in length, with no spaces. You shouldn't use periods within the name; reserve periods for compatibility with other mail systems. The author doesn't recommend the use of commas in the domain name, to avoid problems with mail routing. For example, you should use Acme instead of Acme Inc. to avoid using a space and period.

Organization Names

Typically, the organization name is the same as the domain name because, in most cases, a one-to-one correspondence between the domain and the organization is recommended. The organization name becomes the name of the organizational certificate, and it can be up to 64 bytes long. The author also recommends a minimum length of 3 characters.

Notes Named Network Names

A Notes Named Network is a group of servers that are physically connected in the same location (on the same LAN or routed/bridged internetwork), and share the same network protocol. The Notes Named Network name should be 31 bytes or less. For the purpose of clarity, the name should be chosen to identify

The servers within a Notes Named Network appear in the Open Database dialog box of a Notes client on the same Notes Named Network. The name also is used for automatic mail routing and server grouping in the Server view of the Public Address Book.

Server Names

Server names should have their first 15 characters unique within the organization, and otherwise can be up to 79 characters in length. Strive to limit server names to ten characters, however, because short server names are easier to read in the various dialog boxes.

Choose server names carefully; changing the server name later on is an involved procedure, requiring recertification of the ID, and changing the name in the server document, group documents, ACLs, and connection documents. Assigning a generic name like that of the department is useful, versus assigning the name of the server location, which is likely to change. See Chapter 16, "Administering Notes Servers," for details on changing the name of a server.

Although spaces are permitted in a server name, avoiding spaces eases administration; some network protocols have problems identifying the server on the network if the server name contains spaces. You should also avoid underscores in server names to avoid problems using DNS (domain name serving) in TCP/IP networks.

Installation Overview


Typically, Notes server installation requires the following steps:

You must run server setup before you can run the server. Setup actually creates many of the databases and files needed to run a Notes server. The first server setup does the following:

  1. Creates a new domain and Notes Named Network
  2. Creates certifier ID, server ID, and administrator user ID
  3. Creates a new Public Address Book, using the PUBNAMES.NTF template. The Notes administrator and the server are listed as manager by default in the access control list of the database.
  4. Creates a person document in the Public Address Book for the administrator, and attaches the user ID to it
  5. Creates a server document in Public Address Book for the server
  6. Enables the network and/or serial ports
  7. Creates a certificate document for the organizational certificate in the Public Address Book
  8. Creates LocalDomainServers and OtherDomainServers groups and adds the server name to the LocalDomainServers group
  9. Creates the Notes Log database in the data directory
  10. Creates the mail file for the administrator in the mail directory (under the main Notes directory)
  11. Certifies the user.id and server.id with the organizational certificate.


NOTEThe certifier ID, in the hands of any malicious intruder, can seriously breach the security of your Notes network. Store the certifier ID on a floppy disk in a place safe from others, except authorized administrators.



Installation Options


Three options exist for Lotus Notes server installation:


Installing from CD-ROM


Because Lotus Notes ships only on CD-ROM, that's the easiest media from which to install. If you don’t have a CD-ROM in all of the servers you want to install, follow the directions for creating floppy disks, or set up an installation server.

Installing from Floppy Disks


If the computer on which you want to install Notes doesn't have access to a CD-ROM drive, you can create a 3 1/2-inch floppy disk installation set from the Lotus Notes CD-ROM.

Creating a Set of Install Disks for OS/2

Before you begin creating a set of install disks for OS/2, you need 16 high-density floppy disks. Make sure that they are blank and formatted. To create the install disks, perform the following steps:

  1. Insert the Lotus Notes CD-ROM in the CD-ROM drive.
  2. From the OS/2 command prompt, open the OS/2 directory on the CD-ROM (at the time of this writing it is \OS2) and go to the DISK_KIT directory. The DISK_KIT directory has the following subdirectories:
  3. Insert one of the floppy disks into the floppy drive.
  4. Copy the files from one of the directories listed in step 2 to the floppy disk.
  5. Use the LABEL command to label the disk with the name of the directory. The syntax of the command is:
    
    LABEL [<drive>:][<label>]
    
    

    where <drive> is the drive letter and <label> is the directory name.
  6. Remove the disk from the drive and label the disk similarly with a pencil.
  7. Repeat steps 4 through 6 for all the directories.

Creating a Set of Install Disks for Windows NT

Before you begin creating a set of install disks for Windows NT, you need 17 high-density floppy disks. Make sure that they are blank and formatted. To create the install disks, perform the following steps:

  1. Insert the Lotus Notes CD-ROM in the CD-ROM drive.
  2. Insert one of the floppy disks into the floppy drive.
  3. From the Main Program Group in Program Manager, double-click the File Manager icon.
  4. Open up a window for the CD-ROM drive by clicking its icon. Double-click the Win32 directory and open the DISK_KIT subdirectory.
  5. The DISK_KIT directory has 17 subdirectories labeled DISK1 through DISK17. Copy the files from one of these directories to the floppy disk by clicking and dragging the icon of the subdirectory to the icon of the floppy drive.
  6. Remove the disk from the drive and label the disk with the name of the directory, using a pencil.
  7. Repeat steps 5 and 6 for all the subdirectories.

Installing from a Network Distribution File Server


Notes can be installed on a file server so that the actual installation can be done on Notes workstations or servers over the network. By using a file server, you can install on clients without a CD-ROM. You also don't need to hand out copies of the Notes installation media (CD-ROM, floppy disks).

To set up a network distribution server, Notes copies the Notes installation files in compressed form to a file server. Users can access the file server and install a copy of the application on their hard disks. Everything proceeds just as in a regular install from CD-ROM, except that the source of the files is a file server. To install Notes to a network distribution file server, do the following:

  1. Insert the CD-ROM into the drive (or floppy disk, for a disk install)
  2. (Windows NT) Choose File | Run from the Program Manager menu, and in the command-line box enter the following command:
    
    <drive>:\<Install_Path>\Install>
    
    
    where <drive> is the drive letter, and <Install_Path> is the path for the install files.
    or
    (OS/2) Type <drive>:\<Install_Path>\InstPM in the OS/2 window, where <drive> is the drive letter, and <Install_Path> is the path for the install files.
  3. In the dialog box that appears, enter the person's name and company name under which the software has been registered. (Note that the names you supply are for software registration purposes only and aren't used in the actual Notes setup.)
  4. Check the Install on a File Server check box.
  5. Click Next.
    Install asks whether you want to install the files to a file server or create a network distribution.
  6. Click the Network distribution radio button.
  7. Click Next.
    The Specify Distribution Directory dialog box opens.
  8. Specify the drive and the installation folder for the Notes network distribution directory.
  9. Click Next.
    The install program asks whether you want to copy the files to the hard disk.
  10. Click Yes.

The Notes program files are copied to the file server in compressed form. Any user who can access the network drive can run the Notes install program to install Notes on his local machine.

To install from a file server, follow these steps:

  1. Open the directory under which the network distribution files are stored on the file server.
  2. Type Install at the command prompt.
  3. Press Enter.

The install program runs just like the CD-ROM installation (see the later sections on installing the first server, divided by operating system type).

Installing the First Server—OS/2


Lotus Notes for the OS/2 operating system requires OS/2 Warp version 3 or OS/2 Warp Connect Version 3. Installation of a Notes server takes two steps:

  1. Running the installation program.
  2. Running server setup.

Before running the installation program, make sure that you have reviewed the installation options outlined earlier in this chapter.

Running the Installation Program


To run the Notes server software installation for OS/2, follow these steps:

  1. Disable any screen savers and turn off any virus-detection software.
  2. If you are upgrading from an existing version of Notes, back up any of the following files that you have:
  3. Organizational certifier ID (usually cert.id)
  4. Organizational unit certifier IDs (if any)
  5. Server ID(s)
  6. User IDs (if they aren't already stored as attachments to person documents in the Public Address Book)
  7. names.nsf, the Public Address Book
  8. catalog.nsf, the database catalog
  9. notes.ini, the Notes configuration file
  10. log.nsf, the Notes log database
  11. desktop.dsk, the desktop settings file
  12. Any customized template (.NTF), modem (.MDM), script (.SCR), SmartIcons (.SMI or .TBL), or bitmap (.BMP) files
  13. Insert the CD-ROM (or floppy disk for a disk install) into the drive.
  14. Open an OS/2 window, and type the following command
    
    <drive>:\<Install_Path>\InstPM,
    
    
    where <drive> is the drive letter, and <Install_Path> is the path for the install files. Press Enter.
    The initial Notes installation dialog is displayed.
  15. Enter the name and company name under which the software has been registered.
    The names you supply are for software registration purposes only and aren't used in the actual Notes setup.
  16. If you are installing from CD-ROM or floppy disks, make sure that the Install on a File Server check box is unchecked.
  17. Click Next.
  18. (optional) Customize your installation. Select Customized Features—Manual Install to choose the components you want to install. (The author recommends that all the available components be installed.) At the minimum, for a server install, select the Notes Server, Notes Client, and Personal Data components.
  19. Notes offers two install options: Standard Installation and Server Installation. Select Server Install—Notes Server.
  20. Enter the name of the directory and drive where you want your Notes program files and your Notes data files to reside. If the directories you specify don't already exist, Notes creates them for you.
  21. Click Next.
    Notes gives you a choice of having the CONFIG.SYS file updated with the Notes server path information, or doing it yourself after the installation. If you choose to make the changes manually, Notes stores the additions that are to be made into a file named CONFIG.ADD and saves it in the same directory as CONFIG.SYS. Notes also presents an option to overwrite any program files that might be present from a previous installation in the same directory.
  22. If you have backed up your CONFIG.SYS file, select Update Config.SYS. Otherwise, make sure that option isn't selected.
  23. Select OK.
  24. Click Install to begin installation.
    Notes begins to copy the program files to the directories you specified.
  25. After all the files are copied, click OK to complete the installation.

OS/2 requires the computer to be restarted after installation so that the changes that Notes made in the CONFIG.SYS file can take effect.

If you chose not to have Notes update the CONFIG.SYS automatically, the contents of the CONFIG.ADD file should be added to CONFIG.SYS before rebooting.

Running First Server Setup


After the program files have been installed and the computer rebooted for the changes in the NOTES.INI file to take effect, the computer is ready for first server setup. First server software setup involves running the Notes Workstation software. For Notes to be set up successfully, the server setup program has to be completed. If you try to run the Notes server before completing server setup, the server exits with a message:


You must type "Notes" to set up your system.

Follow these steps to complete server setup:

  1. Double-click the Lotus Notes Workstation icon.
    The Notes Server Setup dialog box appears.
  2. Because you are installing Notes for the first time, select The First Lotus Notes Server in Your Organization.
  3. Click OK.
    The First Server setup box appears.


    NOTEIn this dialog box, organization refers to your company. It doesn't necessarily mean the same thing as the specific term Organization used with respect to Notes naming conventions.

  4. Enter a name for the Notes server in the Server Name box.
  5. Enter the name of your company in the Organization box.
  6. Enter the first name, middle initial, and last name for the Notes administrator in the administrator boxes.
  7. Enter a password in the Administration Password box. Because this password is echoed on the screen as you type, you might want to ensure that nobody is looking over your shoulder. The password is case-sensitive.
  8. Select the type of network in the Network Type drop-down list box.
  9. If the administrator plans to use the server as his personal workstation, check the option Server Is Also Administrator's Personal Workstation. This causes Notes to use the administrator's ID when a workstation session is open on the server. If this option isn't selected, the server ID is used on workstation sessions.
  10. If there is a modem on a serial port on the server, select a COM port in the Serial Port box, the type of dialing (tone or pulse), and the type of modem in the Modem Type box.
  11. Click the Advanced button to bring up the Advanced Options dialog box. It contains the following settings:
  12. Click OK.
    Notes displays the Time Zone Setup dialog box.
  13. Select the time zone for the server's location and check Observe Daylight Savings Time April-October if the server's time zone observes Daylight Savings time.
    Because disparate pieces of a Notes network can be global, the time zones for different servers on the network most likely will be different. This fact can be important when communicating on a worldwide scale. For example, replication schedules, especially when they don't all originate from a hub server, have to be designed to take into account the fact that the servers on the schedule are on a different time zone.
  14. Click OK.

Installing Additional OS/2 Servers


The process of installing additional servers to a network involves three steps. They have to be registered, installed, and set up. You can install the new server before or after registering the new server, but you must complete installation and registration before running setup.

You install additional servers using any of the three installation methods outlined earlier in this chapter, in the section "Installation Options."

Registering Additional Servers


The process of registration performs two main tasks:

  1. Creation of a server document in the Public Address Book.
  2. Creation of a server ID for the new server.

To perform additional server registration, you must make a decision about which certifier ID to use for registration. For additional information about hierarchical certification and naming, see Chapter 9, "Designing Your Notes Network."

You can perform additional server registration from a workstation session on the server, or from a Notes client that has network access or remote access to the registration server. Also, you need to have physical access to the certifier ID and its associated password. If you are performing additional server registration from a personal workstation, the registration server must be up and running. If you are registering the additional server from a workstation session on the registration server, the server may or may not be running. In any case, the person performing the registration should have at least author access to the Public Address Book.

The choice of registration server decides which replica of the Public Address Book will receive the changes made by the new server registration process. It is recommended that after the new server is registered, you manually replicate the Public Address Book at the registration server to servers throughout the network. You can perform manual replication by issuing the following command from the server console:


replicate <target_server><public_name_and_address_book>

where <target_server> is the server to receive the updates and <public_name_and_address_book> is the file name of the Public Address Book.

For more information about replication, and for other ways in which you can perform this replication, see Chapter 15, "Administering Replication."

Notes performs these steps during additional server registration:

  1. Notes creates a server ID for the new server and certifies it with the certificate specified by the administrator.
  2. Notes creates a new server document in the Public Address Book of the registration server.
  3. The name of the Notes administrator is added to the Administrators field of the server document. The server ID is encrypted and appended (attached) to the server document or saved in a file as specified by the administrator.
  4. The server name is added to the LocalDomainServers group in the Public Address Book.
  5. An entry for a new server is created in the certification log (if it exists) on the registration server. The certification log is a database that keeps a log of all certified servers and users in a Notes domain. For more information about the certification log, see Chapter 18, "Administering Notes Security."

Follow these steps to register an additional server:

  1. Start the Notes workstation program.
  2. Choose File | Tools | Server Administration.
  3. Select the server which is to be the registration server.
    The registration server must be currently available to complete registration.
  4. Click the Servers icon and select Register Server.
    Notes reminds you that a separate software license is required for each server registered, and asks if you purchased a license.
  5. Click Yes if you purchased a server software license.
    Notes prompts you for the Certifier ID password. Notes always defaults to the last certifier used for registration. If you want to choose another certifier for registration, choose Cancel when you are prompted for the certifier ID password, and Notes displays a dialog box prompting you for the certifier ID to use.
  6. Enter this certifier's password.
  7. Click OK.
    Notes displays the Register Servers dialog box. If you want to choose a different registration server, click the Registration Server button and select the server you will use as the registration server.
  8. Click OK.
  9. Choose North American or International in the Security field.
    Notes relies on RSA public key encryption technology, which the National Security Agency classes as munitions subject to U.S. export controls. You should have decided which license type to use when you designed your Notes network. See Chapter 18, "Administering Notes Security," and Chapter 9, "Designing Your Notes Network," for more information on international licenses.
  10. Enter a certificate expiration date in the Certificate Expiration Date box. The format for the date is mm-dd-yyyy.
    Notes suggests a certificate expiration date one hundred years from the time of registration.
  11. Click Continue.
  12. Enter a name for the server in the Server Name box. For guidelines for naming servers, refer to chapter 9—Designing your Notes Network.
  13. Enter a password for the server ID in the password box. The length of this password has to be at least that specified in the Minimum Password Length box. All passwords are case-sensitive.
  14. Enter a domain name in the Domain box. Notes suggests a default name, which is usually the name of the organizational certificate.
  15. In the Administrator field, enter the name of the administrator for the new server. Notes defaults to the name of the person performing the server registration.
  16. Click on the Other tab at the left side of the dialog box to bring up miscellaneous settings for the new server.
  17. In the Server Title box, enter a title for the new server. This title will be used in the Server Title field of the server document in the Public Address Book.
  18. In the Network field, enter the Notes Named Network to which this server will belong.
  19. Notes can store the server ID of the server as a file or as an attachment to the server document in the Public Address Book. Click the In Address Book check box if you want to store it in the Public Address Book, or the In File check box if you want to store it in a file. You can specify the location of the file by clicking the Set ID File button. This way, you can also store the ID on a network drive.
  20. Click Next to register additional servers and repeat steps 8 through 19 for each additional server.
  21. Click Register to register all the servers you specified.

Setting Up Additional Servers


After you register a server and install Notes program files, you must complete the process of server setup before the server becomes operational.

Notes performs the following steps when additional servers are set up:

  1. The setup process on the new server looks for the Public Address Book on a target server specified by the administrator.
  2. Notes searches the Public Address Book for the server document created during additional server registration.
  3. Notes uses a server ID stored on a floppy disk (or a hard disk or network drive, for that matter) or retrieves the server ID from the server document in the Public Address Book.
  4. Notes creates a replica copy of the Public Address Book in the data directory of the new server.
  5. Other administrative databases such as the Notes log are created on the new server.
  6. Notes sets up the selected network and serial ports on the new server.

Follow these steps to set up additional servers:

  1. Make sure that Notes installed the program files on the new server and that it has been registered.
  2. Double-click the Notes Workstation icon.
  3. Notes asks if this is the first server in your organization or an additional server in your organization. Because this is an additional server, select the latter and click OK.
  4. Notes brings up the Additional Server Setup dialog box. Enter the name of the server in the New Server Name box as you entered it during additional server registration.
  5. Enter the name of the registration server (or one that contains a replica copy of the Public Address Book containing the server document of the new server) in the Get Domain Address Book From Server Name box.
  6. Enter the fully distinguished name if there is more than one server with the same name (perhaps you have two Marketing servers in two different organizations) in the domain.
  7. If the server will connect over the network, select the Via Network radio button.
  8. If the connection will be over a serial port, select the Via Serial Port radio button. Enter the telephone number of the dial-up server.
  9. In the Network Type drop-down list box, select the network protocol to use if connecting over a network, or choose the serial port on which the modem resides if using a dial-up connection. Select a modem type from the Modem Type drop-down list box. Select Tone Dial or Pulse Dial.
  10. If the server's ID resides in a physical file (not attached to the server document in the Public Address Book), select the New Server's ID Supplied in a File check box.
  11. If the administrator plans to use the server as his personal workstation, select the Server Is Also Administrator's Personal Workstation check box.
  12. Click the Advanced button to open the Advanced Server Setup Options dialog box. Check any of the following options:
  13. Click OK to close the Advanced Server Setup Options box.
  14. Click OK again to accept the Additional Server Setup options.
    The new server attempts to connect to the registration server and creates a replica copy of the Public Address Book in its own data directory.
    After the connection is established and the replica copy of the Public Address Book created, Notes asks you to select a time zone for the server. The significance of the time zone is that, because disparate pieces of a Notes network can be global, the time zones for different servers on the network most likely will differ. This can be important when communicating internationally. For example, replication schedules, especially when they don't all originate from a hub server, must be designed to take into account the fact that the servers on the schedule are on different time zones.
  15. Select Observe Daylight Savings Time April-October if the server's time zone observes Daylight Savings time.
  16. Choose OK.
    Notes creates the Notes log database (log.nsf) and adds it to the workspace.

Repeating Server Setup


If you decide to redo the server setup process after the server has been set up, or have made errors during server setup, perform the following steps. This process is called breaking down the server:

  1. Close the Notes workstation program at the server by choosing File | Exit.
  2. Shut down the server by entering the EXIT command at the server console.
  3. Go to the OS/2 command prompt, and change the current directory to the Notes data directory.
  4. Type e notes.ini and press Enter to edit the NOTES.INI file.
  5. Delete all but the first three lines in the file.
  6. The resulting NOTES.INI file is:
    
    [Notes]
    
    Directory=<drive>:\<data_path>
    
    KitType=2
    
    
    where <drive> is the drive where Notes resides and <data_path> is the path of the Notes data directory.
  7. Save the file by choosing File | Save.
  8. Choose File | Exit to exit the editor.
  9. Delete the following files from the Notes data directory:
  10. Start the Notes Workstation software on the server by double-clicking its icon. This will bring up the Notes Server Setup dialog box and begin the server setup process. Follow the steps in the earlier section "Setting Up Additional Servers."

Installing the First Server—Windows NT


Lotus Notes for the Windows NT operating system requires at least Windows NT Server version 3.51. You have the same three options when installing Notes as you do for OS/2. You can install from CD, floppy disks, or a network directory. See the section "Installation Options," earlier in this chapter, for directions on preparing to install Notes using one of these three techniques.

Running the Installation Program


To run the Notes server software installation for Windows NT, follow these steps:

  1. Disable any screen savers and turn off any virus-detection software.
  2. If you are upgrading from an existing version of Notes, back up any of the following files that you have:
  3. Insert the CD-ROM (or floppy disk for a disk install) into the drive.
  4. Choose File | Run from the Program Manager menu and enter the following command in the command-line box:
    n:\<Install_Path>\InstPM
    where n is the drive letter, and <Install_Path> is the path for the install files.
  5. In the dialog box that appears, enter the name and company name under which the software has been registered. The names you supply are for software registration purposes only and aren't used in the actual Notes setup.
  6. Make sure that the Install on a File Server check box is unchecked.
  7. Click Next.
    Notes offers two install options: Standard Installation and Server Installation.
  8. (optional) Select Customized features—Manual Install to choose the components you want installed. It is recommended that all the available components be installed. At the minimum, for a server install, select the Notes Server, Notes Client, and Personal Data components.
  9. Select Server Install—Notes Server.
  10. Enter the name of the directory and drive where you want your Notes program files and your Notes data files to reside. If the directories you specify don't already exist, Notes creates them for you.
  11. If you chose to do manual installation, select the components you want installed, and click OK. Otherwise just click Install.
    Notes begins to copy the program files to the directories you specified.
  12. After all the files are copied, click OK to complete the installation. Lotus Notes for Windows NT doesn't require the computer to be restarted after installation.

Running First Server Setup


After the program files have been installed, the computer is ready for first server setup. First server software setup involves running the Notes Workstation software. Specifically, you must perform the following steps:

  1. Double-click the Lotus Notes Workstation icon.
    The Notes Server Setup dialog box appears.
  2. Because Notes is being installed for the first time, select The First Lotus Notes Server in Your Organization.
  3. Click OK.
    The First Server Setup box opens.
  4. Enter a name for the first server.
  5. Enter the name of your company in the Organization box.


    NOTEIn this dialog box, organization refers to your company. It doesn't mean the same thing as the specific term Organization used with respect to Notes naming conventions.

  6. Enter the First name, middle initial, and last name for the Notes administrator in the administrator boxes.
  7. Enter a password in the Administration Password box. Because this password is echoed on the screen as you type, make sure that that nobody is looking over your shoulder. The password is case-sensitive.
  8. Select the type of network in the Network Type drop-down list box.
  9. If the administrator plans to use the server as his personal workstation, select the option Server Is Also Administrator's Personal Workstation. This action causes Notes to use the administrator's ID when a workstation session is open on the server. If this option isn't selected, Notes uses the server ID on workstation sessions.
  10. If a modem is connected to the server, select a COM port in the Serial port box, the type of dialing (tone or pulse), and the type of modem in the Modem Type box.
  11. Click the Advanced button to bring up the Advanced Options dialog box. It contains the following settings:
  12. Select the time zone for the server and check Observe Daylight Savings Time April-October if the server's time zone observes Daylight Savings time. Because disparate pieces of a Notes network can be global, the time zones for different servers on the network most likely will be different. This fact can be important when communicating on a worldwide scale. For example, replication schedules, especially when they don't all originate from a hub server, must be designed to take into account the fact that the servers on the schedule are on a different time zone.
  13. Click OK.

When Notes completes server setup, you can start the Notes server.

Installing Additional Windows NT Servers


The process of adding additional servers to a network involves three steps. They have to be registered, installed, and set up. You can install the new server before or after registering the new server, but you must complete installation and registration before running setup.

You install additional servers using any of the three methods outlined in the earlier section "Installation Options."

Registering Additional Servers


The process of registration performs two main tasks:

  1. Creation of a server document in the Public Address Book.
  2. Creation of a server ID for the new server.

To perform additional server registration, you must make a decision about which certifier ID to use for registration. Knowing your company's hierarchical naming scheme is useful for this. For additional information about hierarchical certification and naming, see Chapter 9, "Designing Your Notes Network."

You can register additional servers from a workstation session on the server, or from a Notes client that has network access or remote access to the registration server. Also, you need to have physical access to the certifier ID and its associated password. If you are performing additional server registration from a personal workstation, the registration server must be up and running. If you are registering from a workstation session on the registration server, the server may or may not be running. In any case, the person performing the registration should have at least author access to the Public Address Book.

The choice of registration server decides which replica of the Public Address Book will receive the changes made by the new server registration process. It is recommended that, after the new server is registered, you manually replicate the Public Address Book at the registration server to servers throughout the network. You can perform manual replication by issuing the following command from the server console:


replicate <target_server> <public_name_and_address_book>

where <target_server> is the server that will receive the updates and <public_name_and_address_book> is the file name of the Public Address Book.

For more information about replication, and for other ways in which you can perform this replication, see Chapter 15, "Administering Replication."

Notes takes these actions during additional server registration:

  1. Notes creates a server ID for the new server and certifies it with the certifier specified by the administrator.
  2. Notes creates a new server document in the Public Address Book of the registration server.
  3. The name of the Notes administrator is added to the Administrators field of the server document. The server ID is encrypted and appended (attached) to the server document or saved in a file as specified by the administrator.
  4. Notes adds the server name to the LocalDomainServers group in the Public Address Book.
  5. Notes creates an entry for a new server in the certification log (if it exists) on the registration server. The certification log is a database that keeps a log of all certified servers and users in a Notes domain. For more information about the certification log, see Chapter 18, "Administering Notes Security."

Follow these steps to register an additional server:

  1. Start the Notes workstation program.
  2. Choose File | Tools | Server Administration.
  3. Select the server which is to be the registration server.
  4. Click the Server icon and select Register Server.
    Notes reminds you that you need to purchase a separate software license for each server registered and asks if you purchased a license.
  5. Click Yes if you purchased a server software license.
    Notes prompts you for the Certifier ID password. Notes always defaults to the last certifier used for registration.
  6. If you want to choose another certifier for registration, choose Cancel when you are prompted for the certifier ID password. Notes displays a dialog box prompting you for the certifier ID to use.
  7. Enter the certifier's password.
  8. Click OK.
    Notes displays the Register Servers dialog box.
  9. If you want to choose a different registration server, click on the Registration Server button and select the server which you will use as the registration server. The registration server must be available on the network to complete registration.
  10. Click OK.
  11. At this point, you can change the certifier ID to be used for registration. To use a different certifier ID, click the Certifier ID button and select the certifier ID file you want to use. Click OK, enter the password for the certifier ID, and click OK again.
  12. Choose North American or International in the Security field. Notes relies on RSA public key encryption technology, which the National Security Agency classes as munitions subject to U.S. export controls. For more information on international licenses, see Chapter 18, "Administering Notes Security," and Chapter 9, "Designing Your Notes Network."
  13. Enter an expiration date for the certificate. Notes suggests an expiration date a hundred years from the time of registration. You can change this setting in the Certificate Expiration date box. The format for the date is mm-dd-yyyy.
  14. Click Continue.
  15. Enter a name for the server in the Server Name box. For guidelines for naming servers, see Chapter 9, "Designing Your Notes Network."
  16. Enter a case-sensitive password for the server ID in the Password box. The length of this password has to be at least that specified in the Minimum Password Length box.
  17. Enter a domain name in the Domain box (Notes suggests a default name, which is usually the name of the organizational certificate).
  18. In the Administrator field, enter the name of the administrator for the new server. Notes defaults to the name of the person performing the server registration.
  19. Click on the Other tab on the left side of the dialog box to display miscellaneous settings for the new server.
  20. Enter a title for the new server in the Server Title field. This title will be used in the Server Title field of the server document in the Public Address Book.
  21. In the Network field, enter the Notes Named Network to which this server will belong.
  22. Notes can store the server ID of the server as a file or as an attachment to the server document in the Public Address Book. Click the In Address Book check box to store it in the Public Address Book, or click the In file check box to store it in a file. You can specify the location of the file by clicking the Set ID File button. This way, the ID can also be stored on a network drive.
  23. Click Next to register additional servers, and repeat steps 12 through 22 for each additional server.
  24. Click Register to register all the servers you specified.

Setting Up Additional Servers


After registering and installing Notes program files on the new server, the process of server setup has to be completed before the new server becomes operational.

Notes performs the following steps when additional servers are set up:

  1. The setup process on the new server looks for the Public Address Book on a target server specified by the Administrator.
  2. Notes searches the Public Address Book for the server document that was created during additional server setup.
  3. Notes uses the server ID stored on a floppy disk (or a hard disk or network drive, for that matter), or retrieves it from the server document in the Public Address Book.
  4. Notes creates a replica copy of the Public Address Book in the data directory of the new server.
  5. Other administrative databases are created on the new server.
  6. The selected network and serial ports are set up on the new server.

Follow these steps to set up additional servers:

  1. Make sure that the program files have been installed on the new server and that it has been registered.
  2. Double-click the Workstation icon.
  3. Notes asks if this is the first server in your organization or an additional server in your organization. As this is an additional server, select the latter.
  4. Click OK.
  5. Notes brings up the Additional Server Setup dialog box. Enter the name of the server in the New Server Name box as you entered it during additional server registration.
  6. Enter the name of the registration server (or one that contains a replica copy of the Public Address Book containing the server document of the new server) in the Get Domain Address Book From Server Name box. Enter the fully distinguished name more than one server has the same name in the domain.
  7. Select a network connection type. If the server will connect over the network, select the Via Network radio button. If the connection will be over a serial port, select the Via Serial Port radio button and enter the telephone number of the dial-up server.
  8. Select the protocol to use. If connecting over a network, select the protocol from the Network Type drop-down list box. For a dial-up connection, select a modem type from the Modem Type drop-down list box. Select Tone Dial or Pulse Dial.
  9. If the server's ID resides in a physical file (not attached to the Server document in the Public Address Book), select the New Server's ID Supplied in a File check box.
  10. If the administrator plans to use the server as his personal workstation, select the Server Is Also Administrator's Personal Workstation check box.
  11. Click the Advanced button to open the Advanced Server Setup Options dialog box. Check any of the following options:
  12. Click OK to close the Advanced Server Setup Options box.
  13. Click OK again to accept the Additional Server Setup options.
    The new server attempts to connect to the registration server and creates a replica copy of the Public Address Book in its own data directory.
    After the connection is established and the replica copy of the Public Address Book created, Notes asks you to select a time zone for the server. The significance of the time zone is that, because disparate pieces of a Notes network can be global, the time zones for different servers on the network most likely will be different. This fact can be important when communicating internationally. For example, replication schedules, especially when they don't all originate from a hub server, must be designed to take into account the fact that the servers on the schedule are on different time zones.
  14. Check Observe Daylight Savings Time April-October if the server's time zone observes Daylight Savings time.
  15. Click OK.
    Notes creates the Notes log database (log.nsf) and adds it to the workspace. At this point, additional server setup is complete.

Repeating Server Setup


If you decide to redo the server setup process after the server has been set up, or you have made errors during server setup, follow these steps (this process is called breaking down the server):

  1. Close the Notes workstation program at the server by choosing File | Exit.
  2. Shut down the server by entering the EXIT command at the server console.
  3. Go to the command prompt, and change the current directory to the Notes data directory.
  4. Open the NOTES.INI file for editing.
  5. Delete all but the first three lines in the file.
    The resulting NOTES.INI file is:
    
    [Notes]
    
    Directory=<drive>:\<data_path>
    
    KitType=2
    
    
    where <drive> is the drive where Notes resides and <data_path> is the path of the Notes data directory.
  6. Save the file.
  7. Exit the editor.
  8. Delete the following files from the Notes data directory:
  9. Start the Notes Workstation software on the server by double-clicking its icon. This action brings up the Notes Server Setup dialog box and begins the server setup process. Follow the steps in the earlier section "Setting Up Additional Servers."

Uninstalling Notes


Lotus Notes Release 4 comes with an uninstall utility that uninstalls the Notes program files if you don't want Notes on the workstation anymore. This isn't the same as breaking down the server, because breaking down the server doesn't delete Notes program files—only the key files created during server setup.

To uninstall Notes, follow these steps:

  1. Double-click the Notes Uninstall icon in the program group in which the Lotus Notes icons were installed.
  2. When asked to confirm whether you want to uninstall Notes, click Yes.
  3. The uninstall program begins removing Notes program files from the computer. If any files were modified after Notes was originally installed, the uninstall programs asks you to confirm that you want to delete them. Uninstall removes all files in the Notes directory; it doesn't remove the NOTES.INI file, which is stored in the Windows directory.

Running Notes as a Windows NT Service


Notes can be installed and run under Windows NT as a service. The main advantage of this technique is that if Notes is set up to run as an automatic service, then it will run whether or not anyone is logged in at the computer. Also, this option permits the server to be started from a remote location, using Windows NT's remote administration capabilities. Further, in case of a power outage, the Notes server starts automatically when the NT server comes up again. If you are running Notes under Windows NT, I recommend that you start/stop Notes using the services panel only. This method enables you to monitor Notes remotely, using NT administration features.

To run a Notes server as a Windows NT service, follow these steps:

  1. From Windows NT Program Manager, choose File | Run.
  2. In the Command Line box, enter this command:
    
    <drive>:\<notes_dir>\ntsvinst -c
    
    
    where <drive> is the drive where the Notes files reside, and <notes_dir> is the Notes program directory. Click OK.
  3. Open the Main program group in Windows NT Program Manager. Double-click the Control Panel icon. Opening the Services icon shows a list of the installed Windows NT services. Notes Server should now be one of the installed services.
  4. Click Close to close the Services dialog box.

Configuring Notes as a Manual Service


When Notes is configured as a manual Windows NT service, it must be started manually from the Services icon in Control Panel. To run Notes server as a manual service, follow these steps:

  1. Double-click the Main program group from the Windows NT Program Manager.
  2. Open Control Panel by double-clicking the Control Panel icon.
  3. Double-click the Services icon in Control Panel.
  4. From the list of services installed in Windows NT, select the Lotus Notes Server—Manual service.
  5. Click Start to start the Notes server. To shut down the server, click Stop.
  6. Click Close to close the Services dialog box.

Configuring Notes as an Automatic Service


When Notes is configured as an automatic service, it starts whenever the NT server reboots. To run Notes as an automatic Windows NT service, follow these steps:

  1. Double-click the Main program group from the Windows NT Program Manager.
  2. Open Control Panel by double-clicking the Control Panel icon.
  3. Double-click the Services icon in Control Panel.
  4. From the list of services installed in Windows NT, select the Lotus Notes Server—Manual service.
  5. Click the Startup button to select the appropriate startup option.
  6. Select Automatic to enable automatic starting of the Notes Server. Click System Account in the Log On As box.
  7. Select Allow Service to Interact with Desktop. This setting causes the Notes server console to appear when the administrator logs in. Leaving this option deselected causes the server console not to appear.
  8. Click OK.
  9. The Automatic startup option will only take effect the next time the system is started up. If you want the Notes server service to be started immediately, click Start.
  10. Click Close to close the Services dialog box.

Removing Notes Server as a Windows NT Service


If you want to remove the Notes Server program as a Windows NT service, and only run it manually in a login session, perform the following steps:

  1. Shut down the Notes server by typing exit and pressing Enter at the server console.
  2. From the Windows NT Program Manager, choose File | Run.
  3. In the Command Line box, enter this command:
    
    <drive>:\<notes_dir>\ntsvinst -d
    
    
    where <drive> is the drive where the Notes files reside, and <notes_dir> is the Notes program directory. Click OK.
  4. Open Control Panel in the Main program group in Windows NT Program Manager. Double-click the Services icon to show a list of Windows NT services. Notes Server should no longer be one of the installed services.
  5. Click Close to exit the Services dialog box.

Summary


Lotus Notes server installation demands up-front planning to ensure lower maintenance costs after Notes deployment. Planning usually entails making decisions about naming conventions for the Notes network and the hierarchical naming structure of the organization.

Installing the first Notes Server is a two-step process:

  1. Copying Notes program files to the hard disk.
  2. Server setup.

Installing additional Notes servers entails three steps:

  1. Copying Notes program files to the hard disk.
  2. Registering the new server.
  3. Running server setup.

First server installs differ from additional server installs in that the first server install creates a new certifier ID, whereas additional servers use this certifier ID (or others created after first server install). OS/2 and Windows NT installs proceed along the same lines, except for some minor cosmetic differences.

Previous Page Page Top TOC Next Page