NOTES CLIENT INSTALLATION AND SMART UPGRADE


Lotus Notes pre-installation checklist
This IBM® Lotus® Notes® release includes both new and familiar functionality for mail, calendar, and contacts, with a new user interface capable of operating within a combination IBM® Lotus® Domino™ server and IBM® WebSphere® Portal server deployment. It includes the optional installation of the Composite Applications Editor, IBM® Lotus® Productivity Tools, Activities, IBM® Lotus® Sametime® (integrated), and any custom or third-party Eclipse features that you choose to add.

This checklist lists the main steps you need to complete, or at least consider, before installing or upgrading to this Lotus Notes release.

1. Check the recommended 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.

2. Read the topic Products to install and order of installation.

3. Read the topic Considerations before installing Notes on Windows or Considerations before installing Notes on Linux.

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 (Lotus 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 Lotus 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 Lotus Notes users that specifies information such as their default WebSphere Portal server name, port, and authentication information.

For information about specifying a Home Portal account, see the topics Specifying the home portal account using policy and Specifying the home portal account using preferences.

12. (Optional) Install the WebSphere Portal composite application support for Lotus Notes on the WebSphere Portal server if you will be enabling users to create, edit, or view composite applications that contain portlets.

For information about WebSphere Portal composite application support for Lotus Notes, see the topic Installing the WebSphere Portal composite application support for Lotus Notes.

13. (Optional) Use policy settings, NOTES.INI file settings, and the Lotus Notes tuner to specify available user settings.

For information about customizing the Notes client installation, see the topic Customizing client installations.

14. (Optional) Modify the Lotus Notes install media kit's install manifest (deploy\install.xml) and zipped update site (deploy\updateSite.zip, including the site index file SITE.XML) to specify which Lotus Notes features users can install and optionally how and if those features will appear on the Lotus Notes feature installation panel.

For information about customizing the installation of supplied Notes features, see the topic Customizing Notes installation using the install manifest.

15. (Optional) If you have custom or third-party Eclipse components to install with Lotus Notes, modify the Lotus Notes install media 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.

For information about adding custom or third-party features to the Notes install, see the topic Customizing Notes installation using the install manifest.

16. Determine how you will make HTTP (Eclipse, non-Domino) and NRPC (Domino server-based) component and application updates available to Lotus Notes client systems.

For information about configuring component update using composite applications or the NSF-based update site, see the topics Configuring component update for composite applications and Creating and using an NSF-based update site.

17. Place the Lotus Notes installation media kit in an accessible location.

18. Uninstall any existing instance of Notes 8 Beta 1 or Beta 2 from the systems on which you will install this Lotus Notes 8 release.


For information about uninstalling Notes or cleaning a previous Notes install from the client, see the topic Uninstalling Notes .

19. Shut down all applications before installing or upgrading to this release of Lotus Notes.

20. Install Lotus Notes on the user client systems or communicate to users how they are to install (or upgrade) Lotus Notes.

For information about installing Notes, see the topics Installing Notes in a single user environment, Installing Notes in a multi-user environment and Automating client installation.

See also