meljun_cortes_building the ibm lotus domino 8.5 infrastructure - instructor guide

8/3/2019 MELJUN_CORTES_Building the IBM Lotus Domino 8.5 Infrastructure - Instructor Guide

1/397

Building the IBMLotusDomino8.5 InfrastructureInstructor Guide


2/397

Building the IBMLotusDomino8.5 InfrastructureInstructor Guide


3/397

Building the IBMLotusDomino8.5Infrastructure

Course Edition: 1.0

Notices

DISCLAIMER: You may not copy, reproduce, translate, or reduce to any electronic medium or machine-readable form, in whole or in part, any documents, software, or files provided to you without prior writtenconsent of IBM Corporation, except in the manner described in the documentation.While every reasonableprecaution has been taken in the preparation of this manual, the author and publishers assume noresponsibility for errors or omissions, nor for the uses made of the material contained herein and the decisionsbased on such use. Neither the author nor the publishers make any representations, warranties, or guaranteesof any kind, either express or implied (including, without limitation, any warranties of merchantability, fitness fora particular purpose, or title). Neither the author nor the publishers shall be liable for any indirect, special,incidental, or consequential damages arising out of the use or inability to use the contents of this book, and

each of their total liability for monetary damages shall not exceed the total amount paid to such party for thisbook.

TRADEMARK NOTICES The following terms are trademarks or service marks of International BusinessMachines Corporation in the United States, other countries, or both: DB2, Domino, Domino Designer,Domino.Doc, Everyplace, ibm.com, K-station, LearningSpace, Lotus, Lotus Discovery Server, LotusEnterprise Integrator, Lotus Notes, Lotus Workflow, Mobile Notes, Netfinity, QuickPlace, Rational,Sametime, Tivoli, VisualAge, WebSphere, Workplace, Workplace Messaging, and WorkPlace Shell.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc., in the UnitedStates, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Copyright 2009 IBM Corporation.

Lotus software, IBM Software Group

One Rogers Street

Cambridge, MA 02142

Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced,translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the priorwritten consent of IBM, except in the manner described in the documentation or the applicable licensingagreement governing the use of the software.

All rights reserved.

Licensed Materials - Property of IBM

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corporation.

You must purchase one copy of the appropriate kit for each student and each instructor. For all other educationproducts you must acquire one copy for each user or you must acquire a license for each copy provided to auser.

Part Number: IBMD8L76


4/397

Building the IBMLotusDomino8.5 Infrastructure


5/397

Table of Contents


Lesson 1: Setting Up the First Server andAdministrator

Topic A. Analyzing a Deployment Plan . . . . . . . . . . . . . . . . . . . . . . . . . 2

Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Planning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

The Worldwide Corporation Deployment Plan . . . . . . . . . . . . . . 13

Supported Platforms and System Requirements . . . . . . . . . . . . . 13

Topic B. Installing the IBM Lotus Domino Server Software . . . . . . . 13

Lotus Domino Server Installation Types . . . . . . . . . . . . . . . . . . . . . 14

Topic C. Installing the IBM Lotus Domino Administrator ClientSoftware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

The Lotus Notes 8.5 Client Standard and Basic Configurations. . 18

What is Eclipse? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Client Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

What is Lotus Expeditor? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Expeditor Component Packaging . . . . . . . . . . . . . . . . . . . . . . . . 21

Eclipse Update Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Automated Installation Options for Eclipse Components. . . . . . 22

Multiple Users Sharing One Workstation. . . . . . . . . . . . . . . . . . . . . 22

Topic D. Launching and Configuring the First Server . . . . . . . . . . . . . . 25

The Server Setup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

The Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Replicas of the Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . 26

Comparing Domains and Organizations . . . . . . . . . . . . . . . . . . . 27

Purposes of Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Alternatives to Organizational Units. . . . . . . . . . . . . . . . . . . . . . . . 30

Descendants of the Organization Certifier . . . . . . . . . . . . . . . . . . 32

Organization Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Organization Certifier ID Security . . . . . . . . . . . . . . . . . . . . . . . . . . 32Authentication Between Organizations . . . . . . . . . . . . . . . . . . . . 33

Country Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Server Audience Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

The Lotus Domino Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Administrator Group Security Options . . . . . . . . . . . . . . . . . . . . . . 36

Copyright IBM Corporation 2009.


6/397

Topic E. Configuring the First Workstation. . . . . . . . . . . . . . . . . . . . . . . . 40

The Client Configuration Program . . . . . . . . . . . . . . . . . . . . . . . . . 40

Topic F. Assigning Roles to Administrators and Servers . . . . . . . . . . . . 41

Access in the Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

The Special Privilege of the LocalDomainAdmins Group . . . . . . 42

Privileges the LocalDomainAdmins Group Lacks. . . . . . . . . . . . . 42

Lesson 2: Adding IBMLotusDominoServers

Topic A. Registering Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

The Server Registration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Domino Directory Access for Registering Servers . . . . . . . . . . . . . 47

Need for Selecting a Registration Server . . . . . . . . . . . . . . . . . . . 47

Server ID File Storage Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Topic B. Configuring and Starting Additional IBM Lotus Domino

Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

The Standard Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 51

The Central Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Replicating a Subset of Documents in the Domino Directory. . . 53

Server Setup Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Clearing the Server ID Password. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Lesson 3: Adding IBMLotus NotesClients

Topic A. Creating an Organizational Unit Certifier . . . . . . . . . . . . . . . . 60The Certifier Registration Process . . . . . . . . . . . . . . . . . . . . . . . . . . 61

The Certification Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Administrator Access to Register OU Certifiers . . . . . . . . . . . . . . . 62

Need for Selecting a Registration Server. . . . . . . . . . . . . . . . . . . . 62

Topic B. Registering New Administrators . . . . . . . . . . . . . . . . . . . . . . . . 64

User Registration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Administrator Access to Register Users . . . . . . . . . . . . . . . . . . . . . 66

The License Tracking Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Internet Password Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Internet Password Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67ID File Distribution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Topic C. Registering Users from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

User Registration Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

How to Register Users from a Text File . . . . . . . . . . . . . . . . . . . . . . . 72




7/397

Topic D. Replicating Server Document Changes . . . . . . . . . . . . . . . . . 72

Domino Directory Document Synchronization. . . . . . . . . . . . . . . 73

Topic E. Setting Up an Administrator Workstation . . . . . . . . . . . . . . . . . 75

Workstation Setup for Additional Workstations . . . . . . . . . . . . . . . 75

Topic F. Verifying the IBM Lotus Domino Installation . . . . . . . . . . . . 77

The Lotus Domino Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Topic G. Creating Replicas on Multiple Servers . . . . . . . . . . . . . . . . . . 79

The Administration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Components of the Administration Process . . . . . . . . . . . . . . . . . 79

Database Tools in Domino Administrator . . . . . . . . . . . . . . . . . . . 80

Timing and Execution of Administration Process Requests . . . . . 80

Lesson 4: Administering Users

Topic A. Creating Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Nested Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

The Deny List Only Group Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Group Precedence in Database Access . . . . . . . . . . . . . . . . . . . 89

Auto-populated Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Topic B. Creating an Organizational Policy. . . . . . . . . . . . . . . . . . . . . . 93

Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Policy Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Policy Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Settings Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Policy Precedence Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Static and Dynamic Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Policy Management Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Policy Management Development Tools . . . . . . . . . . . . . . . . . . . 97

Use of an Organizational Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Topic C. Creating and Assigning an Explicit Policy . . . . . . . . . . . . . . . 98

Policy Assignment Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Policy Assignment During Registration. . . . . . . . . . . . . . . . . . . . . . 99

Dynamic Policy Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102The Effect of Multiple Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102



8/397

Lesson 5: Setting Up Server Administration

Topic A. Customizing the IBM Lotus Domino Administrator WorkEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Administration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Lotus Domino Server Console Administration Tasks . . . . . . . . . . . 109

Message Color-Coding on the Server Console . . . . . . . . . . . . . . 109

Topic B. Setting Access to Create Databases on the Server . . . . . . . . 1 1 3

Server Access Control Mechanisms. . . . . . . . . . . . . . . . . . . . . . . . 113

Restrictions for Authorizing Server Access . . . . . . . . . . . . . . . . . . . 113

User Access to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

When to Restart the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Topic C. Setting Administration Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Administration Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Administration Level Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118The Full Access Administrator Level . . . . . . . . . . . . . . . . . . . . . . . . 119

Full Access Administrator Best Practices . . . . . . . . . . . . . . . . . . . . 119

The Domino Web Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Administration Levels and the Lotus Domino WebAdministrator Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Topic D. Setting Logging Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

The Domino Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

The Notes.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Lesson 6: Synchronizing IBMLotusDomino

System Databases

Topic A. Creating Server Groups for Replication. . . . . . . . . . . . . . . . . . 130

Server Databases to Replicate. . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Server Groups and Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Topic B. Creating a Connection Document . . . . . . . . . . . . . . . . . . . . . 132

Replication Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Replication Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Methods for Forcing Replication . . . . . . . . . . . . . . . . . . . . . . . . . . 136Pull Push Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Multiple Replication Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Critical Application Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Replication Schedule Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139




9/397

Lesson 7: Configuring Basic Intranet Mail Routing

Topic A. Configuring Notes Named Networks. . . . . . . . . . . . . . . . . . . . 148

Checklist for Configuring Basic Intranet Mail Routing . . . . . . . . . 149

Mail Routing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Mail Routing Behavior Within and Between NNNs . . . . . . . . . . . . 152

Topic B. Implementing a Hub-and-Spoke Mail Routing Topology . . . 158

The Hub-and-Spoke Mail Routing Topology . . . . . . . . . . . . . . . . . 159

How Mail Routes in the Hub-and-Spoke Topology . . . . . . . . . . . . 159

Opportunistic Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Connection Document Mail Routing Options . . . . . . . . . . . . . . . 161

Router Types and Connection Documents . . . . . . . . . . . . . . . . . 161

Topic C. Selecting a Mail Storage Format for Incoming Mail . . . . . . . . 165

Mail Storage Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Lesson 8: Configuring Mail Routing to the Internet

Topic A. Enabling the SMTP Listener Task . . . . . . . . . . . . . . . . . . . . . . . . 172

Checklist for Configuring Mail Routing to the Internet . . . . . . . . . 173

SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

SMTP Implementation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 175

SMTP Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Internet Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

The SMTP Listener and Router Tasks . . . . . . . . . . . . . . . . . . . . . . . . 178

Methods for Enabling SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Topic B. Configuring Basic SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . 179

SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Topic C. Restricting Internet Mail Delivery . . . . . . . . . . . . . . . . . . . . . . . 184

SMTP Inbound Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

SMTP Outbound Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Message Relay Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185



10/397

Topic D. Enabling Whitelist and Blacklist Filters . . . . . . . . . . . . . . . . . . . 188

What Are DNS Whitelist Filters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

The DNS Whitelist Filter Query Process . . . . . . . . . . . . . . . . . . . . . . 188

Enabling DNS Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

What Happens When a Host is Found in the DNS Whitelist?. . . . . 189DNS Whitelist Filter Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

What are DNS Blacklist Filters?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Enabling DNS Blacklist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

What Happens When a Host is Found in the DNS Blacklist? . . . . . 192

What are Private Whitelist Filters? . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Enabling Private Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

What Happens When a Host is Found in the Private Whitelist? . . 194

What Are Private Blacklist Filters? . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Enabling Private Blacklist Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

What Happens When a Host is Found in the Private Blacklist?. . . 196Order of Whitelist and Blacklist Precedence. . . . . . . . . . . . . . . . . 197

How to Enable Whitelist and Blacklist Filters . . . . . . . . . . . . . . . . . . 197

Topic E. Configuring Extended SMTP (E/SMTP) Options . . . . . . . . . . . . 199

E/SMTP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Topic F. Configuring Internet Addressing. . . . . . . . . . . . . . . . . . . . . . . . 199

When to Set Internet Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Internet Address Lookup Options. . . . . . . . . . . . . . . . . . . . . . . . . . 200

Topic G. Testing SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

An Implementation of SMTP Routing . . . . . . . . . . . . . . . . . . . . . . . 203

Lesson 9: Establishing Mail Controls

Topic A. Configuring Router Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 208

Mail Restrictions and Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Topic B. Implementing Message Disclaimers . . . . . . . . . . . . . . . . . . . . 211

Message Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

The Message Disclaimer Implementation Process. . . . . . . . . . . . 211

Options for Attaching Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . 212

Enabling Server Message Disclaimers . . . . . . . . . . . . . . . . . . . . . . 212Creating Message Disclaimer Policy Settings . . . . . . . . . . . . . . . . 213

Using Message Disclaimers in S/MIME Messages . . . . . . . . . . . . . 213

Topic C. Implementing Mail Delivery Controls . . . . . . . . . . . . . . . . . . . 215

Delivery Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215




11/397

Topic D. Implementing Mail Transfer Controls . . . . . . . . . . . . . . . . . . . 218

Mail Transfer Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Topic E. Configuring Multiple Server Mailboxes . . . . . . . . . . . . . . . . . . 220

Benefits of Multiple Mailboxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Lesson 10: Implementing Mail Rules and StorageLimits

Topic A. Creating and Activating a Server Mail Rule . . . . . . . . . . . . . . 224

Mail Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

How Mail Rules Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Mail Rule Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Activating a Server Mail Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Topic B. Enabling Mail Journaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Mail Journaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Journaling and Mail Rules Interactions . . . . . . . . . . . . . . . . . . . . . 231

Journaling and Mail Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Journaling and Server Configuration . . . . . . . . . . . . . . . . . . . . . . 232

Topic C. Implementing Blacklist Tag and Whitelist Tag Mail RuleConditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Tag Mail Rule Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Field Names Associated with Tags . . . . . . . . . . . . . . . . . . . . . . . . . 237

Options for Creating Rules with Blacklist or Whitelist Tags. . . . . . . 237

Topic D. Establishing Mail Quotas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Quota Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Quota Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

How to Establish Mail Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Topic E. Controlling Inbox Size with Inbox Maintenance . . . . . . . . . . . 2 4 2

Inbox Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Use the Inbox Maintenance Feature to Control Inbox Size . . . . . 243

Topic F. Archiving Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Benefits of Archiving and Policies. . . . . . . . . . . . . . . . . . . . . . . . . . 247

Archive Policy Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

The Archive Policy Settings Document . . . . . . . . . . . . . . . . . . . . . 248

Archive Criteria Settings Document . . . . . . . . . . . . . . . . . . . . . . . 249



12/397

Lesson 11: Monitoring Mail

Topic A. Verifying Routing and Checking Mail Delivery. . . . . . . . . . . . 258

Checklist for Verifying Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . 259

Checklist for Monitoring Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Types of Misdelivered Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Checking Mail Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Topic B. Enabling Mail Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Mail Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Topic C. Enabling Message Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Message Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Topic D. Configuring Message Recall . . . . . . . . . . . . . . . . . . . . . . . . . . 266

What is Message Recall?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Message Recall Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Configuring the Message Recall Feature . . . . . . . . . . . . . . . . . . . 267

Lesson 12: Resolving Common Mail RoutingProblems

Topic A. Sending a Mail Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Common Causes for Mail Routing and Delivery Problems . . . . . 273

Troubleshooting Stages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

The Mail Trace Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Topic B. Restarting the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275When to Restart the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Topic C. Forcing Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

When to Force Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Topic D. Resolving Undelivered and Dead Mail . . . . . . . . . . . . . . . . . . 278

The Delivery Failure Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix A: Solutions to Practice Activities

Topic A. About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Lesson Lab Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290




13/397

Appendix B: The Worldwide CorporationInfrastructure Plan

Appendix C: Certification and Exam Competencies

Appendix D: Instructor Preparation

Additional Instructor Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365



14/397

About This CourseAs an IBM Lotus Domino administrator, it is possible that you might beasked to assist in the installation and management of IBM Lotus Dominoand Lotus Notes.

This course covers installing and configuring a basic IBM Lotus

Domino 8.5 and IBM Lotus Notes 8.5 infrastructure with a singledomain using an existing deployment plan. This course also covers set-ting up replication and mail routing in the single-domain environment.

This two-day course is instructor-led, classroom training where theinstructor presents course materials to a group of students in a class-room. The course materials provide extensive background information,procedural tables, and best practice tips.

Course Description

Target StudentThe target audience for this course is system administrators who arenew to Lotus Domino 8.5, who have a general understanding of theLotus Domino and Lotus Notes administration environment, and who willbe responsible for initial installation and configuration of a basic LotusDomino and Lotus Notes 8.5 infrastructure, as well as configuration ofDomino mail servers in corporate intranet and extranet (i.e. Internet)environments.

Course PrerequisitesThe prerequisites for this course include completion of the IBMLotus

Domino 8.5 System Administration Operating Fundamentals (D8L75)course, or equivalent knowledge, skills, and experience.


Introduction

Introduction i


15/397

How to Use This Book

As a Learning GuideEach lesson covers one broad topic or set of related topics. Lessons arearranged in order of increasing proficiency with Lotus Domino and LotusNotes; skills you practice in one lesson are used and developed in subse-quent lessons. For this reason, you should work through the lessons insequence.

Each lesson is organized into results-oriented topics. Topics include all therelevant and supporting information you need to master Lotus Domino andLotus Notes, and activities allow you to apply this information to practicalhands-on examples.

As a Review ToolSome of the information covered in class may not be relevant to your envi-ronment immediately, but it may become important later on. For this reason,we encourage you to spend some time reviewing the topics and activitiesafter the course. The course can also be used in preparation for Lotus certi-fication exams.

As a ReferenceThe organization and layout of the book make it easy to use as a learningtool and as an after-class reference. You can use this book as a first source

for definitions of terms, background information on given topics, and sum-maries of procedures.


Introduction

ii Introduction


16/397

Course ObjectivesAfter completing this course, you should be able to:

Set up the first server and the administrator.

Add Lotus Domino servers.

Add Lotus Notes clients.

Administer users by creating groups and implementing policies.

Set up server administration.

Synchronize Lotus Domino system databases.

Configure basic intranet mail routing.

Configure mail routing to the Internet.

Establish mail controls.

Implement mail rules and storage limits.

Monitor mail.

Resolve common mail routing problems.


Introduction

Introduction iii


17/397

Course Requirements

Hardware

Instructor (Hub) Server

The following list identifies the hardware requirements for the instructor(Hub) server.

512 MB of RAM or more is required; 1 GB of RAM is recommended.

A Pentium Class or higher processor and compatibles; a Pentium 4,2.6 GHz or higher processor is recommended.

An SVGA (or better) video card and monitor. Support for 256 colors,800 x 600 resolution.

At least 2 GB of free hard disk space per partition; 4 GB is recom-

mended. A mouse or other pointing device.

A CD-ROM drive or access to a network file server for installation.

A projection system or mechanism for the instructors computer screen.

IP networking capabilities.

Internet access (recommended).

Synchronize system time with all classroom machines.

The classroom setup

allows for up to 12students, where each

student has a client and

a server on one physical

machine. While this is

not the best installation

practice, it allows for

each student to have the

same experience. If you

prefer to install the client

and sever on separate

machines, you may do

so. However:

Students may have

to share machines. You may need to

revise some activities

and exercises.


Introduction

iv Introduction


18/397

Instructor Client

It is strongly recommended that you have a separate computer to install asthe instructors Lotus Notes and Lotus Domino Administrator client. If you donot have a separate client computer, you can install the client software on

the instructors Domino server, but this is not the optimal configuration. Thefollowing requirements assume that you will have a separate client computerfor the instructor.

At least 512 MB of RAM; 1 GB is recommended.

A Pentium Class processor.

An SVGA (or better) video card and color monitor. Support for 256 col-ors, 1024 x 768 resolution.

At least 2 GB of free hard disk space.

A mouse or other pointing device.


A projection system or mechanism for the instructors computer screen. IP networking capabilities.


Student Machines

Each student will have one computer on which to install and configure boththe Domino server software and the Lotus Notes and Domino Administratorclient software. The following list identifies the hardware requirements forthe student machines.

At least 1 GB of RAM; 2 GB is recommended.

A Pentium Class or higher processor and compatibles; a Pentium 4, 2.6GHz or higher processor is recommended.

An SVGA (or better) video card and monitor. Support for 256 colors,800 x 600 resolution.

At least 3 GB of free hard disk space.

A mouse or other pointing device.


IP networking capabilities.


Client requirements are

per client software

installed on machine. If

more than one client

type is required on

certain machines, add

the individual client type

requirements together.


Introduction

Introduction v


19/397

Software

Instructor (Hub) Server

The following list identifies the software requirements for the instructor

server machine. Please note that proper licensing for all software is requiredand is the responsibility of the training organization.

Microsoft Windows Server 2003 Standard Edition (Service Pack 1 isnot required but recommended), Microsoft Windows Server 2003Enterprise Edition with Service Pack 2, or Microsoft Windows Server2008 Standard or Enterprise Edition.

The latest version of Java.

Lotus Domino 8.5 Enterprise Server.

A host name resolution mechanism, either through DNS or a hosts file.

Instructor Client

The following list identifies the software requirements for the instructor clientmachine. Please note that proper licensing for all software is required and isthe responsibility of the training organization.

Microsoft Windows XP Professional with Service Pack 2. (If you pre-fer to use Windows Vista, be aware that the course was notdeveloped and tested using that configuration.)

The latest version of Java.

IBM Domino Administrator 8.5.

IBM Lotus Notes 8.5, Standard configuration.

A host name resolution mechanism, either through DNS or a hosts file. IBM Lotus Symphony Presentations or Microsoft PowerPoint

Viewer.

Student Machines

The following list identifies the software requirements for the studentmachines. Please note that proper licensing for all software is required andis the responsibility of the training organization.

Microsoft Windows Server 2003 Standard Edition (Service Pack 1 is notrequired but recommended), Microsoft Windows Server 2003 EnterpriseEdition with Service Pack 2, or Microsoft Windows Server 2008 Stan-

dard or Enterprise Edition. The latest version of Java.

Lotus Domino 8.5 Enterprise Server.

IBM Domino Administrator 8.5.

IBM Lotus Notes 8.5, Standard configuration.

A host name resolution mechanism, either through DNS or a hosts file.


Introduction

vi Introduction


20/397

Version Note

This course was tested using the GA release of IBM Lotus Domino 8.5.

Class Setup

Preparing for an ILO Class ExperienceInstead of a traditional classroom instructor-led class, you may be takingthis course as an instructor-led online class. If you are participating in anonline class experience, you should:

Verify that you have the dial-in number for participants.

If necessary, verify that you have the conference reference name ornumber and password, if required, to the conference.

Verify that you have the appropriate support contact information:

Technical support: To help resolve connection issues.

Content support: To answer questions about the materials pre-sented in class.

Process support: To assist with understanding how an ILO class iscarried out and assure that participation is appropriate.

Test your ability to connect to the course with the equipment you planto use during the course. This will allow you to:

Test connectivity to the providers server.

Download any applications or plug-ins required. Become familiar with the online interface.

Note: Some training providers will schedule a separate test sessionprior to your course to allow you to test connectivity; otherwise, youshould plan to do this just prior to the courses start time. Your trainingcenter will provide the necessary information and instructions to youprior to your class start date.

Lotus Domino Naming Used in the CourseThis course uses the following hierarchical naming scheme.

Table 0-1: Domino naming scheme

Naming compo-nent

Classroom implementation

Organizationcertifier

/WWCorp

Instructor preparation

information specific to

ILO is provided in the

Instructor Preparation

Appendix.


Introduction

Introduction vii


21/397

Naming compo-nent


Domain WWCorp

Organizationalunit certifiers

SVR/WWCorpEast/WWCorpWest/WWCorp

Domino server names Domino administrator user

names

Instructor Hub/SVR/WWCorp Doctor Notes/WWCorp

Students East01/SVR/WWCorp

East02/SVR/WWCorp

East03/SVR/WWCorp

East04/SVR/WWCorpEast05/SVR/WWCorp

East06/SVR/WWCorp

West01/SVR/WWCorp

West02/SVR/WWCorp

West03/SVR/WWCorp

West04/SVR/WWCorp

West05/SVR/WWCorp

West06/SVR/WWCorp

Admin East01/East/WWCorp



Admin East04/East/WWCorpAdmin East05/East/WWCorp


Admin West01/West/WWCorp






Instructor serv-ers computername

Hub

Instructor serv-ers host name

hub.wwcorp.com

Instructor clientscomputer name

Instructor

Instructor clientshost name

instructor.wwcorp.com

Student com-puter names

East01 through East06and West01 throughWest06


Introduction

viii Introduction


22/397

Naming compo-nent


Student hostnames

east01.wwcorp.comthrough

east06.wwcorp.com andwest01.wwcorp.comthroughwest06.wwcorp.com

List of Course FilesThe following table outlines the files used in the course or provided as addi-tional tools.

Table 0-2: Required course files

File name Function

Reg_East.txt

Reg_West.txtLesson 3 Used for registering usersfrom text files.

Rep_dd.txt Used throughout the course for replicat-ing the Domino Directory to allclassroom servers.

D8L76 Agent.nsf Lesson 2 Used for adding fields to theServer document.

Test.abc Lesson 10 Used for demonstrating

mail rules.

MailAgent.nsf Lesson 11 Used for sending mes-sages for tracking purposes.

D8L76.ppt Instructor presentation file.

Checklist of Classroom Setup TasksComplete the following tasks to set up the classroom prior to the start ofclass or when indicated in an instructor note during the class. Detailed pro-

cedures for each task appear on the following pages.

Table 0-3: Classroom setup tasks

Task Procedure

1 If necessary, uninstall Lotus Domino and Lotus Notes on allservers and clients.


Introduction

Introduction ix


23/397

Task Procedure

2 Create the hosts file.

3 Install the course files.

4 Complete the individual lesson setups for Lessons 3, 8, 10,and 11.

Task 1: If Necessary, Uninstall Lotus Dominoand Lotus Notes on all Servers and ClientsAt the beginning of class, the instructor (Hub) server and all student com-puters should have only Windows Server and Java installed. The instructorclient computer should have only Windows XP Professional, Java, and IBM

Lotus Symphony Presentations or Microsoft PowerPoint

Viewer installed. Ifthe machines have been used as Domino servers or Lotus Notes clients,you will need to uninstall Lotus Domino and Lotus Notes from the machinesto enable guiding students through the installation of both products. See theLotus Domino documentation for detailed steps.

Task 2: Create the Hosts FileUse any text editor to edit the hosts file on each classroom machine toinclude the IP address and server names as shown in the following table.You can use any IP addresses that are appropriate for your classroom envi-ronment.

Table 0-4: IP addresses and server names for the hosts file

IP address Hierarchical name Host name

HubIPaddress Hub/SVR/WWCorp hub.wwcorp.com

IPaddress East01/SVR/WWCorp East01.wwcorp.com






IPaddress West01SVR/WWCorp West01.wwcorp.com

IPaddress West02/SVR/WWCorp West02.wwcorp.com


Introduction

x Introduction


24/397

IP address Hierarchical name Host name





Task 3: Install the Course FilesFollow these steps to install the \D8L76 course folder on the instructorsserver and client.

Table 0-5: Install the course files

Step Action

1 To install the course files from the CD-ROM, insert the course CD intothe instructors server machine.

2 On the CD-ROM, open the D8L76 folder.

3 Double-click the D8L76dd.exe file.

4 Repeat the above steps on the instructor client machine.

The executable will copy the following files to the specified locations, creat-

ing the \lotus_ed\ directory and all necessary sub-directories, if required.These files will be present on both the instructor server and instructor clientmachines.

Table 0-6: Course data files

Directory Files copied

\D8L76 Files:

Rep_dd.txt

Reg_East.txt

Reg_West.txt

D8L76.ppt

Test.abc

Databases:

D8L76 Agent.nsf

MailAgent.nsf


Introduction

Introduction xi


25/397

Task 4: Complete the Individual LessonSetups for Lessons 3, 8, 10, and 11The following tasks should be completed before beginning the specified

lesson or when indicated in an instructor note.Lesson 3

Complete the following tasks.

Table 0-7: Lesson 3 setup tasks

Task Action

1 Use Domino Designer to copy the Set D8L76 fields agent from the sup-plied D8L76 Agent.nsf file to the Domino Directory on Hub/SVR/WWCorp. Use Domino Administrator to select all Server documents andrun the agent to perform the following:

Add LocalDomainServers and Doctor Notes/WWCorp to the Server

documentSecurity tabCreate new replicas field to enable theAdministration Process to create a new replica.

Remove current contents of the Full Access Administrators fieldand add Doctor Notes

Set Adminp interval to 5 minutes.

Set the time that Adminp performs daily requests to noon.

2 Copy Rep_dd.txt to the instructors Domino data directory.

3 Copy the following files to the instructors Notes data directory:

Reg_East.txt

Reg_West.txt

Lesson 8

If necessary, add Doctor Notes (or any account that you might use) to theACL of the Mail.box on Hub/SVR/WWCorp, with Manager access and allpermissions. This enables a demo in this lesson in which you view docu-ments in Mail.box.

Lesson 10

Complete the following tasks.


Task Action

1 Copy Test.abc to the instructors server data directory, or to a locationwhere students will be able to access it.


Introduction

xii Introduction


26/397

Task Action

2 Create two or three mail rules.

Lesson 11Complete the following tasks.


Task Action

1 Send mail that cannot be delivered to show dead and undelivered mail.

2 Copy the Send multiple mail messages for D8L76 agent from thesupplied MailAgent.nsf file to your (Doctor Notes) mail file.

3 Run the agent to send messages to students for tracking purposes.

Course IconsThe following table explains the icons used in this course.

Table 0-10: Course Icons

Icon Description

An activity is a student-centered learning process that allows students tolearn by performing a task. Activities can be instructor-led or completedindependently.

Scenario information is used to introduce an activity problem or goal.Scenarios use fictitious people and organizations to present details, prob-lem statements, and parameters that are used to complete the activity orlab exercise.

Caution statements are included in the courseware to make studentsaware of potential negative consequences of an action, setting, or deci-sion, that are not easily known.

Tips and notes provide additional information, guidance, or a hint about atopic or task.

An Instructor Note is a special comment to the instructor regarding deliv-

ery, classroom strategy, classroom tools, exceptions, and other specialconsiderations. The Instructor Note is included in the Instructor Guideonly.

Display Slide provides a prompt to the instructor to display a specificslide. The Display Slide icon is included in the Instructor Guide only.


Introduction

Introduction xiii


27/397


28/397

Setting Up the First Server andAdministrator

Topic A: Analyzing a Deployment Plan

Topic B: Installing the IBM Lotus Domino Server Software

Topic C: Installing the IBM Lotus Domino Administrator ClientSoftware

Topic D: Launching and Configuring the First Server

Topic E: Configuring the First Workstation

Topic F: Assigning Roles to Administrators and Servers

1

Copyright IBMCorporation2009.


29/397

Introduction

Planning is a critical step in the process of implementing an IBM LotusNotes and IBM Lotus Domino environment.

Worldwide Corporation has decided to use Lotus Notes and Lotus Dominoas their international standard for messaging and collaboration. Worldwidehas gone through extensive planning to determine their mail and applicationrequirements and to identify how Lotus Notes and Lotus Domino canaccommodate those requirements.

As a result of their planning, Worldwide has designed a deployment plan todescribe how they will implement Lotus Notes and Lotus Domino throughoutthe corporation.

This lesson covers basic guidelines and considerations to use when plan-ning a Lotus Notes and Lotus Domino implementation and introducesWorldwides deployment plan and implementation checklist.

Note: Since this is not a planning course, in-depth planning issues are not dis-cussed. This lesson presents high-level planning considerations and guidelines thatwill help position Worldwides deployment plan.

Worldwides implementation checklist is an example of a typical checklist that mightbe used to install and set up a basic Lotus Domino infrastructure. The checklist willbe used as the basis for this course. It will be revisited in each lesson to demon-strate progress.

After completing this lesson, you should be able to:

Review a sample deployment plan implementation.

Install the Lotus Domino server software.

Install the Lotus Domino Administrator client software.

Launch and configure the first server.

Configure the first workstation.

Assign roles to administrators and servers.

Lesson 1 Setting Up the First Server andAdministrator

2 Copyright IBM Corporation 2009.


30/397


Planning Considerations

When planning a Lotus Domino infrastructure:

Determine the business problems to be addressed.

Examine the organizational structure.

Design the Lotus Domino environment around the organizational struc-ture.

The Lotus Domino infrastructure should enhance and support the organiza-tional structure.

Integration with other IBM productsAs you plan the Lotus Domino infrastructure, also consider how it needs tointegrate with other organizational software and systems. Lotus Domino 8.5has been designed specifically to work with the following IBM products:

IBM Lotus Sametime

IBM Lotus Quickr

IBM Lotus Connections

IBM WebSphere Portal

IBM Lotus Notes Traveler

Checklist: Planning the Lotus Domino environmentWorldwide Corporation used the following checklist to plan their infrastruc-ture.

Task Procedure

1 Identify structure of organization.

2 Create planning team.

3 Identify tracking mechanism.

4 Define the business problem.

5 Identify how Lotus Domino can address the business problem.

6 Identify access needs.

7 Identify hardware requirements (site map).

8 Identify server roles.

Planning Considerations

Introduce the topic. Themain goals of this topic

are to:

Emphasize the

importance of creat-

ing a deployment

plan.

Introduce Worldwide

Corporations deploy-

ment plan (see the

Worldwide Corpora-

tion Infrastructure

Plan appendix).

Provide basic guide-lines for planning an

infrastructure.

Introduce World-

wides

implementation

checklist, which stu-

dents will use

throughout the

course to install and

configure the infra-

structure.

Planning Checklist

A





31/397

Task Procedure

9 Select location for servers.

10 Identify network protocol(s) and network changes.

11 Choose replication topology.

12 Identify directory strategy.

13 Select mail routing strategy.

14 Develop naming scheme.

15 Define security.

16 Determine sever configurations.

17 Determine client configurations.

18 Determine rollout strategy.

19 Determine education strategy.

Planning Guidelines

Several areas need to be considered when planning a Lotus Domino infra-structure. It is important to determine and follow guidelines to ensure that alltasks are properly carried out.

Note: The Planning Guidelines table presents some basic guidelines to use whenplanning a Lotus Notes and Lotus Domino infrastructure. This course does not coverhow to plan an infrastructure. However, you can use this table as a planning refer-ence.

Guidelines for planning tasksThe following table provides some guidelines for planning tasks.

Planning Guidelines

Introduce the table as a

reference. Instead of

reading the material in

the table, use the table

to emphasize the extent

to which planning should

be performed and the

importance of a planning

effort.





32/397

Task Guidelines

Identify structure oforganization:

Examine current struc-ture.

Validate with upper man-agement.

Design Lotus Dominoinfrastructure aroundorganization.

Determine:

Geographic layout of the organization

Mobile considerations

Number of users and where they are located

Business model

Work environment

Infrastructure

Communication

Future plans

Key departmental considerations

Decision makers

Create planning team. Identify decision makers (based on size of com-

pany, will be different roles).

Identify the skills required to design the LotusDomino infrastructure.

Assign individuals/job titles to the skills.

Identify gaps in skills and/or human resources.

Ensure approval from upper management.

Identify tracking mechanismto:

Record planningprogress.

Allow adjustment ofgoals as necessary.

Keep users informed.

Serve as a project man-agement tool.

Identify:

The types of information to ask:

Dates

Timelines

Budget

How will the information be used?

Who will contribute to it?

How it will be updated and managed?

Suggested tracking mechanisms, such as:

Lotus Domino Web application located on a testserver

Existing project management software





33/397

Task Guidelines

Define the business prob-lem.

Typical business problems include:

Knowledge management

Process

Communication

Extended enterprise

Identify how Lotus Dominocan address the businessproblem.

Basic Lotus Domino solutions include messagingand/or workflow:

E-mail/PIM

Broadcast/Reference

Discussion

Tracking/Workflow

Identify access needs. Identify:

Current and future user information accessrequirements

User location access requirements

Lotus Domino hardware requirements

Changes to existing hardware based on userneeds and Lotus Domino requirements

Identify hardware require-ments (site map).

Identify factors affecting hardware infrastructure,such as budget and expertise.

Determine operating system(s) for Lotus Dominoservers.

Identify Lotus Domino specifications.

Determine need for clustering and/or partitionedservers.

Determine backup strategy.

Identify current hardware infrastructure (create asite map).

Determine changes to current hardware infrastruc-ture to support Lotus Domino.





34/397

Task Guidelines

Identify server roles. Determine the roles of Lotus Domino servers

based on the business problem. For example:

Mail

Application/Web

Hub

Communication

Certificate Authority

Firewall/Gateway

Select location for servers. Assign roles to servers in locations based on:

Organizational structure

Business problem(s)

User needs Hardware requirements

Update the site map by specifying which serversbelong in each location.

Identify network protocol(s)and networking changes.

Identify network connections based on:

Network protocols (recommended protocol TCP/IP)

Network traffic (LANs and WANs) amount ofbandwidth needed depends on:

The amount of mail traffic and database replica-tion

How traffic is routed (shared applications on thesame network)

Clustering, if clustered servers are implemented

Lotus Notes Named Networks, including:

Connection types (protocols available, band-width)

Time zones (when does replication occur?)

Which workgroups exist in multiple sites andare dependent on each other for information?

What is the level of urgency for data within an

application that is replicated between servers?

Who communicates with whom most often?

Is dialup connectivity required?





35/397

Task Guidelines

Choose replication topol-ogy.

Identify who needs access to what information andwhen.

Identify where to put applications to be replicated.

Determine how and when replication occurs.

Use Hub and Spoke topology when possible tomaximize server resources.

Use dedicated replication hubs where possible.Use Pull/Push replication from the hubs.

Create a replication map that shows which serversreplicate with each other, the frequency of replica-tion, and any restrictions that are in place.

Place applications in geographic locations byworkgroups.

Identify directory strategy. Identify domain or domains.

Define directory structure by domain.

Identify how the Lotus Domino Directories will beused.

Identify the external directories that will be acces-sible to Lotus Domino users.

Determine whether to use Central Directory (forbetter performance and efficiency).

Determine whether to use Directory Catalogs (formobile users).

Select mail routing strategy. Identify mail clients.

Identify which mail routing protocol or protocols touse based on client types.

Determine message format based on client types.

Decide on security mechanism(s).

Determine how mail is routed using a topologymap.





36/397

Task Guidelines

Develop naming scheme. Determine organizational units based on:

Location

Departments

Workgroups

Servers common name should:

Be a short, descriptive name.

Contain an abbreviation for the region where itresides.

Not contain any spaces.

Be easily expandable.

Be easily recognizable for the tasks the serverperforms.

Define security. Secure the following infrastructure components:

Workspace

Network

Server

Workstation

Applications

Determine server configura-tions.

Consider standardizing the following for LotusDomino servers:

File directory structure

Database location

Database size quotas

Lotus Domino server types based on the serverrole

Lotus Notes client types based on users jobresponsibilities

Use of the same release of Lotus Domino serversoftware throughout the organization

Determine client configura-

tions.

Identify Lotus Domino client types.

Identify non-Lotus Domino client configurations. Identify user mail configurations.





37/397

Task Guidelines

Determine rollout strategy. Identify project milestones and deadlines.

Identify who is responsible for project milestones.

Determine education strat-egy.

Identify training resources for technical users.

Identify training resources for end users.

Note: For more information on planning, consult these resources:

IBM Redbook: A Roadmap for Deploying Lotus Domino in the Organiza-tion at http:/www.redbooks.ibm.com.

Lotus Domino Administrator 8.5 Help

The Worldwide Corporation Deployment Plan

The complete Worldwide Corporation Infrastructure Plan appears in theWorldwide Corporation Infrastructure Plan appendix. The deployment planincludes three regions for implementation:

Headquarters (Corporate)

East

West

Note that the server names in the plan accommodate a mail and applicationenvironment, whereas in this course only the mail servers will be imple-mented. Therefore, the server names have been modified from the onespresented in the plan.





38/397

This course implements the basic infrastructure based on the deploymentplan. The Lotus Domino and Lotus Notes components for the three regionsappear in the following completed classroom diagram.

Figure 1-1: Completed classroom diagram

ClassroomImplementation

Provide an overview of

the classroom

implementation.

See Additional Instructor

Notes





39/397

Checklist: Building the Lotus Domino environmentThis course implements the following tasks from Worldwide Corporationsdeployment plan.

Task Procedure

1 Set up the first server.

2 Add an administrators workstation.

3 Set up access to the Domino Directory.

4 Add Lotus Domino servers.

5 Add organizational units.

6 Register administrators.

7 Add Lotus Notes clients.

8 Create user groups.

9 Create organizational policy.

10 Register users.

11 Set administration preferences.

12 Set up access to servers.

13 Set up server logging.

14 Synchronize Lotus Domino system databases throughout thedomain.

15 Route mail internally.

16 Route mail to the Internet.

17 Set mail controls.

18 Test mail routing and delivery.

Implementation

Checklist

Tell students that this is

the checklist they will be

using throughout the

class to implement the

infrastructure. This is a

subset of the

implementation checklist

provided in the

Worldwide CorporationInfrastructure Plan

appendix. Because this

class focuses on a basic

infrastructure, it does

not include setting up a

Web server or

configuring mobile, non-

Domino, and Internet

clients.





40/397

Supported Platforms and System Requirements

The Release Notes for each version of Lotus Domino and Lotus Notes con-tain a section on supported platforms and system requirements. You canalso obtain this information from the IBM Web site. For Lotus Notes andDomino 8.5, the Detailed system requirements Web page can beaccessed from http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg27013072.

Supported Platforms

and System

Requirements





41/397

Topic B: Installing the IBM Lotus

Domino Server SoftwareThis topic focuses on the installation of the first server. You will use thecomponents created during the first server setup to install and configure therest of the servers and users in the domain in the upcoming lessons.

The administrators for Worldwide Corporation will begin implementation withthe first IBM Lotus Domino server. The following components result fromsetting up the first server, and these components will be used to implementthe rest of the plan:

Organization certifier

Organizational unit certifier

Server name

Administrators name

Directory of resources in the domain

Lotus Domino Server Installation Types

To ensure installation of the appropriate server software, administratorsmust select the server type at installation.

The following table describes the different server types.

Server type Function

Lotus DominoUtility Server Provides custom database applications for IBM

LotusNotes and Web clients, and Lotus Domino database trans-action logging.

Application services only

Support for Lotus Domino clusters

Note: This does not include support for messaging services.

Lotus DominoMessagingServer

Provides Lotus Domino and Internet mail services.

Messaging services

Note: This does not include support for application servicesor Lotus Domino clusters.

Implementation

Checklist

Review the checklist. At

the end of this lesson,

the following

Implementation

Checklist items will be

complete:

Set up the first

server.

Add an administra-

tors workstation. Set up access to the

Domino Directory.

Lotus Domino Server

Installation Types

B

Topic B: Installing the IBMLotusDominoServer Software




42/397

Server type Function

Lotus DominoEnterpriseServer

Provides a Lotus Domino server license option for deployingan e-mail and calendar infrastructure along with collabora-tive applications.

Both messaging and application services

Support for Lotus Domino clusters

Note: To cluster mail servers, the Lotus Domino Enterpriseserver is required.

Note: All three server types support Lotus Domino partitioned servers. The installa-tion presents an option for Partitioned Server Installation. This option allows anadministrator to install and configure more than one Lotus Domino server on thesame machine. Worldwide Corporation has chosen to dedicate a machine to eachserver, so we will leave this check box deselected during installation of the class-room servers.

Partitioned servers, clustered servers, and transaction logging are beyond the scopeof this course. For more information on these advanced topics, refer to the LotusDomino Administrator 8.5 Help.

Platform and operating system requirementsThe following table displays the platform and operating system requirementsas they apply specifically to the Lotus Domino 8.5 server and Microsoft

Windows.

Category Requirements

Supported operating system ver-sions

Microsoft Windows Server 2003 Stan-dard Edition

Microsoft Windows Server 2003 EnterpriseEdition with Service Pack 2

Microsoft Windows Server 2003 X64 Edi-tion

Microsoft Windows Server 2008 StandardEdition

Microsoft Windows Server 2008 EnterpriseEdition

Microsoft Windows Server 2008 x64 Stan-

dard Edition Microsoft Windows Server 2008 x64

Enterprise Edition

Platform and Operating

System Requirements





43/397

Category Requirements

Processors supported Intel Pentium or higher and compatibles(32-bit and 64-bit chips as appropriate), orequivalents

RAM 512 MB minimum or more recommended perCPU

Disk space 1.5 GB minimum per partition

Disk swap space Two times the physical RAM installed

Monitors supported Color monitor required

Protocols NetBIOS over IP (32-bit processor only,only Microsoft IP is supported)

NetBIOS over IPX (32-bit processor only)

TCP/IP (includes IPv6)

Topic B: Installing the IBMLotusDominoServer Software




44/397

Activity 1-1: Install the Lotus DominoEnterprise Server Software

ScenarioEach server will be a Lotus Domino Enterprise server to allow for all pos-sible configurations. Installing the Lotus Domino server software copiesexecutables, database templates, and other files to the hard drive. OnMicrosoft Windows platforms, the installation also creates registry entries.

To complete this activity:

Start the installation process.

Accept the license agreement and the default location for the directorynames for program and data files.

Complete the installation of Domino Enterprise Server.

Follow these steps to install the Lotus Domino Enterprise Server software.

Step Action

Start the installation process

1. Run the Lotus Domino 8.5 server installation executable, Setup.exe, fromthe location provided by the instructor.

2. On the Welcome screen, click Next.

Accept the license agreement and the default location for the directorynames for program and data files

3. Click I accept the terms in the license agreement, and then click Next.

4. Click Next to accept the default directory name for program files.

5. Click Next to accept the default directory name for data files.

Complete the installation of Domino Enterprise Server

6. Verify that Domino Enterprise Server is selected, and click Next.

7. Review the selected options and click Next to begin copying files.

8. Click Finish to complete the installation.

Lead students ininstalling the Lotus

Domino Enterprise

Server software on all

classroom servers.

Step 1: Direct students

to the appropriate

location of the install

executable.

Step 8: While the

software is installing,

move on to the next

section.





45/397

Topic C: Installing the IBM Lotus

DominoAdministrator Client SoftwareAdministrators require a client to administer the IBM Lotus Domino serv-ers. Worldwide administrators will use the Lotus Domino Administrator clientto perform all administrative tasks.

The Lotus Notes 8.5 Client Standard and Basic

Configurations

The IBM Lotus Notes 8.5 client comes in two main configurations, ortypes: Basic and Standard. The following table describes each configuration.

Client type Description

Basic Built on the same platform as Lotus Notes 7, the Basicclient resembles Lotus Notes 7 in its interface and func-tionality. The Basic client is one of the options of theStandard client installation.With all the applications residing on Domino servers, theBasic client allows you to access new and recognizableservice offerings for Calendar, Contacts, and Mail, plusfamiliar functionality for instant messaging.The existence of the Basic client is useful if you want torun it in the following circumstances:

Client computers do not have enough RAM or otherhardware resources to run the Standard client at

acceptable performance levels. As an administrator, you do not want to spend the

money for additional technical support or to train userson the new Lotus Notes 8.5 user interface yet.

You are not upgrading the servers on the back end toLotus Domino 8.5 yet, so there is little reason to run theStandard client.

Lotus Notes 8.5 Client

Types

C

Topic C: Installing the IBMLotusDominoAdministrator Client Software




46/397

Client type Description

Standard Supported by IBM Lotus Expeditor and IBM Lotus

Eclipse platforms with Java-enabled, Eclipse, and SWTcapabilities, the J2EE Standard client provides a larger

networking environment with increased functionality andinnovation opportunities.The Standard client enables you to access applications onboth Domino servers and IBM WebSphere Portal serv-ers. With a fully redesigned user interface, the Standardclient offers new and improved mail, calendar, contacts,and instant messaging functionality, while introducing youto engaging application and tool integration.The J2EE Standard client is the preferential configurationto support an all-inclusive new features and functionalityupgrade from Lotus Notes 7 to Lotus Notes 8.5.

Other client optionsIn addition to using the Basic and Standard client configurations, users canalso access Notes mail and other features by using IBM Lotus iNotes,which is a browser-based access method that is offered in three modes.The following table describes the iNotes modes.

Note: The former name of Lotus iNotes was Domino Web Access.

iNotes mode Description

Full Provides a full set of features including Mail,Calendar, Notebook, Contacts, and To Dolist.

Lite Optimized for performance in bandwidth-constrained environments, and providesaccess to Mail and Contacts in a stream-lined user interface.

Ultralite Designed for use on mobile devices such asthe Apple iPhone or iPod touch.





47/397

What is Eclipse?

The Eclipse platform is designed for building integrated development envi-ronments (IDEs) that provide template-driven design and CSS-basedcustomization. It is an open-source Java-based platform for end-user anddeveloper products. Because of its open architecture, Eclipse has becomethe foundation for rich client platform (RCP) development.

The Lotus Notes 8.5 client includes all the code that is Lotus Notes withinthe Eclipse environment. The Eclipse platform incorporates technology thatis expressed through a well-defined design and implementation framework.It can be used to create diverse end-to-end computing solutions for multipleexecution environments.

Client Installation Types

When you run the client installation software, the Custom Setup screen

lists the available client installation options. By default, Notes Client andSametime (integrated) are selected, and you have the option of selectingany or all of the following client components for installation:

IBM Lotus Domino Designer

Lotus Domino Administrator

Activities

Composite Application Editor

IBM Lotus Symphony

Lotus Notes 8.5 is also available as a client-only installation kit, which canbe acquired via the Web, snail mail, and in stores on CD- and DVD-ROMs.

Note: IBM Lotus Sametime is an integrated installation option and cannot bedeselected when installing the Notes 8.5 client.

The workstation installation offers three Lotus Notes-based clients, asshown in the following table.

Client type Purpose

Lotus Notes An interface for working with LotusNotes applications and Internet data.

Lotus Domino Administrator An interface for administering LotusDomino systems.

Lotus Domino Designer An interface for adding functionality tonew or existing applications.

What is Eclipse?

Client Installation Types





48/397

Note: Selecting either the Lotus Domino Administrator client or the Lotus DominoDesigner client also installs a Lotus Notes client.

What is Lotus Expeditor?

Lotus Expeditor is a client platform for end-to-end smart client applicationsolutions. Expeditor extends Lotus Notes 8.5 by providing services to installand manage applications. Additionally, users are allowed to easily launchand switch among these applications.

Expeditor builds reusable clients on top of Eclipse and leverages Eclipsetechnology to provide a client solution that runs on multiple operating sys-tems. As a rich client, Lotus Notes 8.5 inherits a great deal of its behaviorfrom Expeditor, created by IBM as a generalized rich client with strong man-ageability features.

InstallShield Tuner capabilitiesLotus Notes 8.5 does support InstallShield Tuner capabilities to configureand customize client installations. Lotus Notes tuning files include notes.ini,templates, and databases.

Expeditor Component Packaging

Expeditor component packaging is a method by which you can customizeclient installation for Lotus Notes. This type of packaging is used to add avariety of the supplementary client-supported functionality provided by IBMfor Lotus Notes 8.5.

Note: Composite applications can be packaged as J2EE code in .war files or asXML definitions in Lotus Notes .nsf databases. Expeditor can open either.

Eclipse Update Sites

Eclipse Update Sites are catalogs that contain features and plug-ins forEclipse/RCP applications. They are published in a specific form to locatenew and updated versions to download during installation.

Eclipse is capable of installing or updating features placed on the remote

servers. The features and plug-ins must be packaged in JAR files and havea manifest (site.xml) file that links them together. These files collectivelyform an Eclipse Update Site.

What is Lotus

Expeditor?

Expeditor Component

Packaging

Eclipse Update Sites





49/397

Eclipse Update Sites offer a convenient way of delivering new plug-ins andupdates of existing ones. Collections of plug-ins are provided that logicallygo together. They are assembled in such a way to enable easy transportover the network, have necessary legal and security mechanisms, and aremodular to allow hierarchical product building.

Automated Installation Options for Eclipse Components

Automated client installation supports the IBM Lotus Domino clients andsimplifies installation for end users because it presents very few or none ofthe installation windows. This process is therefore known as a silent installa-tion.

You can automate an installation for Lotus Notes 8.5 clients using any of thefollowing methods:

Tuning the installer for automated install.

Configuring the installer content via features and install manifest. Scripting the installer for specific options and silent install.

Using the installer in conjunction with Smart Upgrade.

Using the installer in conjunction with other deployment systems.

Multiple Users Sharing One Workstation

Many environments require different users to share programs on a worksta-tion. The Lotus Notes workstation installation offers a multi-user option sothat multiple users can share a Lotus Notes client, with each user maintain-ing a separate environment. There are two considerations:

The operating system must support multiple user profiles.

The Lotus Domino Designer client and the Lotus Domino Administratorclient do not support multi-user.

Worldwide Corporation has chosen not to implement multi-user worksta-tions, so this option will be deselected during installation of the classroomworkstations. For more information on multi-user workstations, refer to theLotus Domino Administrator 8.5 Help.

Note: Further discussion of multi-user workstations is beyond the scope of thiscourse. Refer to the Lotus Domino Administrator 8.5 Help for more information onthis subject.

Automated Installation

Options

Workstation Sharing

Considerations





50/397

Activity 1-2: Install the Lotus DominoAdministrator Client Software

Note: To provide all students with a comprehensive hands-on experience, we havedesigned this course so that students administer their own servers. To accommo-date this, you will run the client and server software on the same machine. TheLotus Domino server and Lotus Notes client software support this configuration pro-vided that the server and client software is installed in separate directories on themachine. While we recognize that this is not an optimal nor a recommended con-figuration to deploy in a real world environment, we use this environment in theclassroom to provide you with the experience of administering your own servers.

Scenario

Before the Worldwide administrators can use the Lotus Domino Administra-tor client to administer Lotus Domino servers, the client software needs to

be installed.

To complete this activity:

Begin the installation of the client software.

Select the client components to be installed.

Complete the installation.

Follow these steps to install the Domino Administrator client and relatedsoftware.

Step Action

Begin the installation of the client software1. Run the Lotus Notes 8.5 client installation executable, Setup.exe, from the

location provided by the instructor.

2. On the Welcome screen, click Next.

3. Select I accept the terms in the license agreement, and click Next.

4. On the Customer Information screen,