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. Read the release notes or system requirements tech note for software and hardware specifications for the systems on which you or your users will be installing. See the hardware and software requirements section of the release notes for details, including the Notes installation matrix release note.
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 release notes "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 Activities server if you will be enabling users to create, edit, or view activity documents from Notes. For Activities 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 http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp.
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) Install the WebSphere Portal composite application support for Notes on the WebSphere Portal server if you will be enabling users to create, edit, or view composite applications that contain portlets.
13. (Optional) Use policy settings, NOTES.INI file settings, and the Notes tuner to specify available user settings.
14. (Optional) 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 specify which Notes features users can install and optionally how and if those features will appear on the Notes feature installation panel.
15. (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.
16. Determine how you will make HTTP (Eclipse, non-Domino) and NRPC (Domino server-based) component and application updates available to Notes client systems.
For information about configuring component update using composite applications or the NSF-based update site, see the "Configuring component update for composite applications" and "Creating and using an NSF-based update site" topics in this guide
17. Place the Notes installation kit in an accessible location.
18. Uninstall any Notes 8x beta instances.
19. Shut down all applications before installing or upgrading to this release of Notes.
20. Install Notes on the user client systems or communicate to users how they are to install (or upgrade) Notes.
Related topics