NOTES CLIENT INSTALLATION AND UPGRADE
This checklist lists the main steps you need to complete, or at least consider, before installing or upgrading to this Notes release.
1. Review system requirements for software and hardware specifications at the Lotus Support site.
2. Read the Products to install and order of installation topic in this guide.
3. Read the platform-specific Considerations topics in this guide.
4. Determine how you want to install. For example, will users install the client themselves using an installation kit or a Smart Upgrade procedure, will you install a multi-user or single user environment, and if installing on Microsoft® Windows®, will you use the Notes-only installer or the Allclient (Notes, Domino Administrator and Domino Designer clients) installer.
5. Familiarize yourself with installation and upgrade basics as presented in the "Notes client installation and Smart Upgrade" section of this guide.
6. Install or upgrade your Lotus Domino server.
7. (Optional) If you are installing IBM® DB2, see the "Domino and DB2 supported platforms and hardware and software requirements," "Installing Domino and DB2 on Microsoft Windows platforms" and "Installing Domino and DB2 on IBM® AIX® and Linux® platforms."
8. Set Domino administrator settings for your users.
9. (Optional) Install or upgrade your Connections server if you will be enabling users to create, edit, or view activity documents from Notes. For Connections server setup, see the IBM® Lotus® Connections documentation.
10. (Optional) Install or upgrade your IBM WebSphere Portal server if you will be enabling users to create, edit, or view composite applications that contain portlets. See the WebSphere Portal information center.
11. (Optional) Create a Home Portal account for your Notes users that specifies information such as their default WebSphere Portal server name, port, and authentication information. Read the Home Portal account topics in this guide.
12. (Optional) Configure policy settings, NOTES.INI file settings, and other settings for users. See "Policies," "Pushing notes.ini settings or location document settings," and "Pushing Eclipse preference settings."
13. (Optional) Modify the Notes install kit, and optionally MSI tuner file, to specify which features will be available for Notes install.
14. (Optional) If you have custom or third-party Eclipse components to install with Notes, modify the Notes install kit's install manifest (deploy\install.xml) and zipped update site (deploy\updateSite.zip, including the site index file SITE.XML) to add these features to the install kit.
15. Determine how you will make HTTP (Eclipse, non-Domino) and NRPC (Domino server-based) component and application updates available to Notes client systems.
17. Uninstall any Notes beta instances.
18. Shut down all applications before installing or upgrading to this release of Notes.
19. Install Notes on the user client systems or communicate to users how they are to install (or upgrade) Notes.
Related topics