Abstract: This white paper addresses the issues most frequently reported by customersto IBM Technical Support regarding IBM® Lotus® Domino® server deployment. Thegoal of this document is to enable Domino Administrators who are relatively new to theDomino products to help themselves with specific Lotus Domino installation andupgrade questions. In short, this is a "how to" guide (cookbook) for Lotus Domino install,setup, and upgrade tasks.
Table of Contents1 Introduction ......................................................................................................... 2 2 Basics of setting up a standalone Domino server .............................................. 2
2.1 Minimum requirements for Lotus Domino ................................................... 2 2.2 Detailed installation steps ........................................................................... 3 2.3 Detailed setup steps .................................................................................... 7 2.4 Troubleshooting the Domino server install or setup .................................. 17
3 Installing and setting up an additional Domino server in an existing domain ... 18 3.1 Troubleshooting the secondary Domino server install or setup ................ 23
4 Upgrading a Domino server .............................................................................. 24 4.1 Incremental upgrades ............................................................................... 24 4.2 Installing a fix pack .................................................................................... 26 4.3 Installing a hot fix ...................................................................................... 29
5 Conclusion ........................................................................................................ 32 6 Resources ........................................................................................................ 32 7 About the author ............................................................................................... 33
1 IntroductionThis paper focuses specifically on installing IBM Lotus Domino on the Microsoft®Windows® server OS; it does not go into depth on subjects such as the differencesbetween 32-bit and 64-bit OS Domino installs. In such cases, you'll be referred to thepertinent IBM Support Technotes in the knowledge base.
Also, as this is a guide for deploying the Domino server, it does not cover how to installand set up programs such as the Notes client, Domino Designer client, or DominoAdministrator client, or how to connect to the server through a Web browser. Thatinformation is covered elsewhere in training materials and other technical content (seethe Resources section of this paper).
To help you quickly find the task you need to perform, the paper is divided into sectionsas follows: First server install, Adding Domino servers to an existing domain, andIncremental upgrades, fix packs, and hot fixes.
2 Basics of setting up a standalone Domino serverLet's start with a discussion of the prerequisites involved.
2.1 Minimum requirements for Lotus DominoIn order for an operating system to meet the minimum standard supported configuration,it means IBM has rigorously tested the Domino server version in question with thatspecific OS and can confirm that it works robustly. Even though a Domino server can beinstalled and started on an untested version of a software OS, such as Windows XP, itplaces your software in an unsupported configuration and will limit its supportability byIBM.
The currently supported versions of the Domino server at the time of this writing areDomino 6.5.X, Domino 7.0.X, and Domino 8.0.X.
Microsoft Windows 2000 is a supported OS for Domino 6.5.X and Domino 7.0.X, andWindows 2003 SP2 is a supported OS for Domino 6.5.X, Domino 7.0.X, and Domino8.0.X.
The current versions of Domino server software requirements can be found in the IBMSupport Techdocs titled, “Detailed system requirements - Lotus Domino 7.0.3” and “Domino 8.0.2 Detailed System Requirements”.
Once you confirm the required hardware minimums are met and that you're installingDomino on a supported OS, you now must decide what the purpose of your Dominoserver install is. It can be licensed as a utility server, messaging server, or an enterpriseserver, the definitions of which are in the Administrator Help file:
“When you install each server, you must select one of the following installation options:
• Domino Utility Server -- Installs a Domino server that provides application services only, withsupport for Domino clusters. Note that it does NOT include support for messaging services.
• Domino Messaging Server -- Installs a Domino server that provides messaging services. Note
that it does NOT include support for application services or Domino clusters.
• Domino Enterprise Server -- Installs a Domino server that provides both messaging andapplication services, with support for Domino clusters. Only the Domino Enterprise Serversupports a service provider (xSP) environment.”
Table 1 is a partial list of part numbers for the Domino Server products. All the items aredownloadable from the Passport Advantage Web site.
Table 1. Domino part numbersName: OS Language Part # SizeIBM Lotus Domino Utility Server 6.5.6 Windows 2000 and 2003 English C99HWEN 435mbIBM Lotus Domino Utility Server 7.0.2 Windows 2000 and 2003 English C94QBEN 520mbIBM Lotus Domino Utility Server 7.0.3 Windows 2000 and 2003 English C17YMEN 501mbIBM Lotus Domino Utility Server 8.0 Windows 2003 English C13NGEN 500mbIBM Lotus Domino Utility Server 8.0.1 Windows 2003 English C18XPEN 466mb
IBM Lotus Domino Messaging Server 7.0.2 Windows 2000 and 2003 English C94QBEN 520mbIBM Lotus Domino Messaging Server 8.0 Windows 2003 English C13NGEN 500mb
IBM Lotus Domino Enterprise Server 7.0.2 Windows 2000 and 2003 English C94QBEN 520mbIBM Lotus Domino Enterprise Server 8.0 Windows 2003 English C13NGEN 500mb
IBM Lotus Domino 8.0.2 32 bit Windows 2003 English C1K38EN 472mbIBM Lotus Domino 8.0.2 64 bit Windows 2003 English C1K39EN 502mb
In our first detailed walk through of the program install below, the screenshots are takenfrom an Enterprise Domino 8.0.1 server installed on a Windows 2003 SP2 OS.
The formal detailed instructions for the Domino server installation and setup processwithout the screenshots can be found in the Lotus Domino Administrator 7 Help.
2.2 Detailed installation stepsFigures 1 and 2 show the first two screens that appear after you double-click theDomino server executable, giving you the URL for our product and requiring you toconfirm that you've read the Domino server software license agreement, respectively.
Figure 1. InstallShield Wizard Welcome page with URL
Figure 2. License Agreement
Next, determine where the Domino program files (see figure 3) and data files (see figure4) will be installed. The program files and data can be placed in different directories andeven on different drive letters, but the default is to place the data directory within theDomino folder.
Figure 3. Choose the install directory
Figure 4. Choose the data file location
Now, you must determine which version of the Domino server you will install. In ourexample, we're installing the Domino Enterprise server setup type (see figure 5).
Figure 5. Choose the setup type
Click Next; you see the Installing Lotus Domino progress screen (see figure 6).
Figure 6. Install progress
When the install completes, you'll see the final wizard screen (see figure 7)with themessage “The InstallShield Wizard has successfully installed Lotus Domino....”
Figure 7. Success screen
2.3 Detailed setup stepsNow that the Domino server install is complete, you should see a Domino server icon onthe Windows server desktop. Double-click this icon to start the Domino server setupwizard; the Setup Welcome screen displays (see figure 8).
Figure 8. Setup Welcome screen
The Domino server that we're setting up is called “FirstServer”; the name of ourcompany in this case is “LotusIBM”; and because this is a lab environment, the name ofthe Domino domain will be “Test”. The Windows OS Name is “Windows2003.”
As this is a demonstration of the first server install, select the “Set up the first server orstand-alone server” radio button before clicking next (see figure 9).
Figure 9. Choose first or additional server
Now, you are asked to choose the name of your server (see figure 10). Simply put, theDomino server name does not need to match the OS server name, but the name shouldhelp you remember what the server is and what it does.
Note the comment here warning that, once the Domino server name has been chosen, itis difficult to change at a later date.
Figure 10. Choose your server name
The IBM Support Technote #1086045 titled “Recommended naming conventions for server names or domain names” has some additional guidance on naming Dominoservers and Domino domain names and includes additional details about what would berequired to change the Domino name itself after the server setup is complete.
The Organization name is commonly your company name and is included in the fullhierarchical name of users and servers registered later (see figure 11).
At this point, after picking the Organization name and a sufficiently complex passwordfor the cert.id, you can click the Customize button to see some additional choices. TheAdvanced Organizational Settings screen displays (see figure 12).
Figure 12. Optionally specify an OU
For instance, if your company name is Acme, but there's a branch of Acme on the EastCoast and one on the West Coast, you can chose to create additional OrganizationalUnits (OU) that help further define the users, servers, and groups. OU's do not need tobe specified at this time, however, and are usually registered after the first Dominoserver install is complete. In our example, we click Cancel to proceed to the next screen.
Finally, the Domino domain name is defined by the people, servers, and groups that areall in the same directory or address book. Type in the Domino domain name and clickNext (see figure 13). (Once the Domino server is set up and running, the DominoDirectory is also sometimes called by its file name, Names.nsf.)
Figure 13. Choose domain name
Now, let's create our first Person document for the Domino directory. Since this is theonly person that is in our newly created Names.nsf file, by default it will also be theAdministrative Account for the Domino server. We name our account ADMIN SYSTEM(see figure 14).
Figure 14. Specifying Admin ID
When the ADMIN SYSTEM account is registered, the ID is saved as an attachment inthe Names.nsf in the Person document. In this case, let's also enable the check box“Also save a local copy of the ID file” to specify a different location on the network andmake a backup copy of the ID.
Now you must decide what Internet services your server will provide: Web browser,Internet Mail Clients, or Directory services (see figure 15). Because the first server in theDomain is also the administrative server, it's a good idea to limit it to that purpose, andto install additional SMTP and mail servers later for Web clients.
Figure 15. Select the Internet services the server will provide
If, however, this will be the only Domino server in your domain and, as such, must be aWeb server, SMTP server, and administration server, then enable all three options. Inour case, only the default “Directory services (LDAP services)” check box is leftenabled.
If you click the Customize button, the Advanced Domino Services screen displays, inwhich you can add or remove additional services to your Domino server (see figure 16).Clicking each one of these entries provides a more detailed description of what they do.
Figure 16. Add/remove additional services
From here, click Cancel to return to the previous screen (recall figure 15 above).
In our server environment and in most customer environments, NetBIOS is not used onthe OS, so you can disable the NetBIOS over TCP/IP option in the “Enabled portdrivers” field (see figure 17) by clicking the Customize button.
Figure 17. Network settings
Now you see the Advanced Network Settings screen (see figure 18); deselect the checkbox for the NetBIOS over TCP/IP option.
Figure 18. Deselect NetBIOS
Note that the “Enabled port drivers” field now lists only TCP/IP (see figure 19).
Figure 19. TCP/IP the only enabled port driver
Click Next; the Secure Domino Server screen displays (see figure 20), in which you canspecify Access Control List settings to limit access for databases created on this server,as well as create the “LocalDomainAdmins” group as a manager to all databases.Leave both these options enabled (the default).
Figure 20. Securing the Domino server
The summary screen displays (see figure 21), listing the setting choices we've made sofar (Server name, Server type, etc). Confirm the settings and click the Setup button.
Figure 21. Confirm your setup options
The program finishes creating and registering files, and completes (see figure 22).
Figure 22. Setup complete
Click the Finish button; you should see an icon on your desktop for the newly installedDomino server. Double-click it to launch Lotus Domino for the first time.
If you receive a dialog box asking whether you want to run the program as a service oran application, you can pick either; however, in our demonstration, Lotus Domino 8.0.1picks the service as a default.
Click Next; you should see a Domino console screen similar to that shown in figure 23,if the Domino server starts successfully.
Figure 23. Successful Start console screen
2.4 Troubleshooting the Domino server install or setupIf, for whatever reason, the Domino server installation or setup fails and you get an errormessage, make sure to record it. You can search the Lotus Domino Support Web site,using key words from the error, to find a document that provides direction on how torecover from the error.
If your search is not fruitful, one of the best initial troubleshooting steps is to remove anyvariables that you can from the environment in which Domino is being installed:
• Are you local or remote? If attempting to install the software remotely, try going tothe server itself, or use a different remote program to access the server in question. Ifyou're logged on to the OS directly, check the permissions of the account with whichyou logged on to the OS, to ensure the account has enough required permission toinstall software on the OS.
• Temporarily stop or remove all third-party products and services that may interfacewith the Domino server, such as anti-virus products, backup software, and spamfilters, and try to re-run the program.
3 Installing and setting up an additional Domino serverin an existing domainIn this example, we add an additional Domino server to a separate Windows OS that'sconnected across the network to the existing Domino server. Installing an additional
server in an existing Domino domain is the same as installing a new server on the OS;however, there are differences in the server setup.
The first step in this process is to launch the Administration client and register a newserver ID. When registering the new server, be sure the new server.id has a differentname from the old server.id if saving to the network location, to make sure the firstserver ID isn't over written.
Because the installation process for a single Domino server install and an additionalDomino server install is the same, we'll skip right to the Domino server setup. Theimages here are for a server setup that's run from an Enterprise Domino 8.0.1 serverand installed on a Windows 2003 SP2 OS.
First, double-click the new Domino icon from the desktop to see the Welcome toDomino Server Setup screen (recall figure 8); click Next.
At this screen (see figure 24), make sure to select the “Set up an additional server” radiobutton; click Next.
Figure 24. Select to set up additional server
Select the option for “The server ID file is stored on a floppy disk, CD or network drive” to point to where the server ID is located on the network (see figure 25). (If the secondDomino server ID is stored in the Server document in the Names.nsf file, feel free tochoose the option “The server ID file is stored in the Domino Directory” instead.) Click Next.
Figure 25. Specify where server ID is located
Assuming we chose a valid server ID, the name of the second server will appear greyedout in the Server name field of the “Provide the registered name of this additionalDomino server” screen (see figure 26).
Figure 26. Registered name
On the next screen, keep only the default “Directory services (LDAP services)” optionchecked, unless you specifically want to enable Web access or SMTP services (seefigure 27). Click Next.
Figure 27. Enable only “Directory services (LDAP services)”
Then click the Customize button on the Domino network settings screen to enable onlythe TCP/IP port on this server (see figure 28).
Figure 28. Keep only the TCP/IP port enabled
Since we're setting up a new server in an existing domain, this server setup needs theprimary Domino server information, that is, Other Domino server name and Optionalnetwork address (see figure 29). Note that, even though the network IP address is listedas optional, it's usually a good idea to provide it, if possible.
Figure 29. System databases for this Domino server
The most common point of failure during a secondary Domino server install is when thenew server attempts to connect to the primary server. If your server cannot connecteven when the primary server IP address is provided, then put the Names.nsf on thehard drive of the local server, enable the option “Get system databases from CD orother media,” and then browse to where the new server setup can find the Names.nsflocally.
In the next screen you must specify the type of Domino Directory for your server (seefigure 30). If you keep the default “Set up as a primary Domino Directory” option, theserver will make a complete Names.nsf local to this server. Unless there's a goodreason to change this, keep the default. Click Next.
Figure 30. Specify the type of Domino Directory
The next four screens that display are the same as those for first server setup. Similarly,if you're prompted the first time you click the Domino server icon from the OS desktop,decide whether to run it as a service or application.
Domino 8.0.1 picks the service as a default, and you should see the same type of serverconsole screen when the Domino server starts as you saw for the first server.
3.1 Troubleshooting the secondary Domino server install orsetupThe troubleshooting steps for a secondary server in the Domino Domain are quitesimilar to those for the first server, so you can use the same resources cited in Section2.4 above.
Again, when troubleshooting the problem, remove as many variables as you can, and tryto stop all services that may impair the Domino server from installing cleanly. Additionalthings to check are:
● As this server also must be able to reach the primary server across the network,make sure that TCP/IP is running from the OS, and that you can connect to the otherserver on an OS-to-OS level, such as by using the “ping” command.
● Confirm that any firewalls or network routing devices between these servers allowtraffic across port 1352, which is the default port Domino and Notes use.
4 Upgrading a Domino serverSo far, we've demonstrated only how to run a full install of the Domino product on an OSthat doesn't have Domino previously installed on it. Upgrading a major release of LotusDomino, such as from 6.5.x to 7.0.x, or from Domino 7.0.x to 8.0.x, requires overwritingDomino server program directories and upgrading the files.
The steps to perform an upgrade to a new major release of Domino are addressed in anumber of IBM Redpaper and Redbooks publications, the most recent of which aretitled, “Lotus Notes and Domino 7 Enterprise Upgrade Best Practices” and “IBM Lotus Notes and Domino 8 Deployment Guide.”
4.1 Incremental upgrades An incremental upgrade, on the other hand, is minor version update such as upgradingfrom Domino 6.5.3 to Domino 6.5.4. Historically, incremental upgrades have mainlybeen combinations of bug fixes; however, starting with Domino 7.0.3, new features andfunctionality are also included in incremental releases, as in major releases.
Here's a partial list of existing incremental upgrades:
Name OS Language Part # SizeIBM Lotus Domino Server Incremental Install 7.0.0 to 7.0.1 Fix Pack 1 Windows 2000 and 2003 English C90CSNA 21 MBIBM Lotus Domino Server Incremental Install 7.0.2 to 7.0.3 Windows 2000 and 2003 English C185LEN 368 MBIBM Lotus Domino Server Incremental Install 8.0 to 8.0.1 Windows 2003 English C1A62EN 355 MB
To install an incremental upgrade to a Domino server, first shut down the existingDomino server, and then double-click the executable to launch the installation program.
In the License Agreement screen, select “I accept” after reading the fine print; click Next(see figure 31).
Select where the data files are found from the pull-down menu on the Welcome screen(see figure 32); click Next.
Figure 32. Select data file location
The installer proceeds with the upgrade, indicating its progress, and finishing with asuccess screen.
The most common reason for an incremental upgrade to fail is due to attempting toinstall it on to a Domino server on which a fix pack is installed. If you get a failure screenstating “checksum failure” or “incorrect version,” confirm there are no hot fixes installedon the Domino server, and then retry the incremental install.
Another possible means to upgrade a Domino server, if the incremental install fails or ifyou want to upgrade a number of incremental versions at once (such as to go from 6.5.3to 6.5.6), is to download the full version install of the Domino program for the upgrade.
This process follows the same steps that are in the Redpaper and Redbookspublications cited at the beginning of Section 4.
To uninstall an incremental upgrade, double-click the same incremental upgradeexecutable you used to install it and follow the prompts.
4.2 Installing a fix packHere's a partial list of existing fix packs:
Name OS Language Part # SizeIBM Lotus Domino Server 6.5.5 Fix Pack 2 Windows NT, 2000, 2003 English C97E6EN 27 MBIBM Lotus Domino Server 6.5.5 Fix Pack 3 Windows NT, 2000, 2003 English C10LSEN 28 MBBM Lotus Domino Server 6.5.6 Fix Pack 1 Windows 2000, 2003 English C118QEN 2 MBIBM Lotus Domino Server 6.5.6 Fix Pack 3 Windows 2000, 2003 English C1D60EN 12 MBIBM Lotus Domino Server 7.0.2 Fix Pack 1 Windows 2000, 2003 English C97GDEN 18 MBBM Lotus Domino Server 7.0.2 Fix Pack 2 Windows 2000, 2003 English C11AQEN 20 MBIBM Lotus Domino Server 7.0.2 Fix Pack 3 Windows 2000, 2003 English C185RZZ 22 MB
Fix pack upgrades, such as from Domino 6.5.3 to 6.5.3 FP1, also require the Dominoserver to be shut down before you double-click the fix pack executable.
A Domino Fix Pack install uses executable screens similar to those for the IncrementalUpgrade process. The first screen you encounter asks you to accept the terms andconditions and click Next; the second screen asks you to confirm where the Domino filesare found and whether you want to install the fix pack there; the third screen tells youwhich DLL's are being replaced and gives you a progress bar for the installation; and thefinal screen let you know when the install completes successfully.
Uninstalling a fix pack is just as easy; just double-click the executable and, whenprompted, select the previous version of Lotus Domino to roll back the version of thesoftware (see figure 33).
Figure 33. Selecting release version to revert to
4.3 Installing a hot fixHot fixes are software patches released by IBM to resolve a specific bug. Hot fixes arebuilt for--and can only be installed on--a specific version of Domino and are written for aspecific OS as well. Because of the nature of hot fixes, they are unavailable from thePassport Advantage Web site; you can only obtain them by contacting Domino Technical Support directly.
If at all possible, it is significantly better to upgrade Domino using a fix pack instead of ahot fix because most of the identified bugs are addressed in fix packs and resolve anumber of issues at the same time.
The installer program for a hot fix is similar to the process for installing a fix pack; thatis, stop the Domino server, double-click the executable, and then click Next as needed.This demonstration uses a fix pack that was specifically written for Domino 6.5.3 FP1 ona Windows OS.
The executable screens for installing a Domino hot fix are almost identical to thescreens from the Incremental Upgrade process and the Fix Pack installation process:
The first screen that displays asks you to accept the terms and conditions and clickNext; the second screen asks you to confirm where the Domino files are found andwhether you want to install the fix pack there; the third screen shows you a progress barfor the installation; and the final screen lets you know when the install completessuccessfully.
NOTE: Once you've installed a hot fix, Lotus Domino is unable to upgrade to the next fixpack until the hot fix is uninstalled. The uninstall process is the same as the installprocess: Double-click the hot fix executable, select the previous version of Domino, andclick Next.
5 ConclusionIf you are a relatively new Lotus Domino Administrator, hopefully this white paper hasenabled you to help yourself with specific Domino installation and upgrade questions.It's not meant to be a comprehensive guide, however, so be sure to consult theadditional resources linked in the section below for more detailed solutions.
Lotus Training and Certification site:http://www-01.ibm.com/software/lotus/training/
7 About the authorEd Nordmeyer found his way into the computer science field in the 1980's, when he wasan English Major and was “fired” by the Dean of the English Department for wanting totake Calculus and Computer classes. Ed later received his Bachelor's degree inNetwork Systems Management, and he is currently a member of the Enterprise ServerCore team for IBM's Lotus Software brand. You can reach Ed [email protected].
Trademarks• Domino, IBM, Lotus, and Notes are trademarks or registered trademarks of IBM Corporation
in the United States, other countries, or both.• Microsoft and Windows are registered trademarks of Microsoft Corporation in the United
States, other countries, or both.• Other company, product, and service names may be trademarks or service marks of others.
