Instructor Guide ND760 - CT3UBNA

7/31/2019 Instructor Guide ND760 - CT3UBNA

1/363

Building the IBMLotusDomino7 InfrastructureInstructor Guide


2/363

Building the IBMLotusDomino7 InfrastructureInstructor Guide


3/363

Building the IBMLotusDomino7Infrastructure

ACKNOWLEDGMENTS

Project Team

Instructional Designers: Vincent Iglesias-Cardinale, Bethany Snyder and Eric Heller Content Manager: SeanBengry Graphic Designer: Elaine Blakeman Project Coordinator: Trina Simpson Content Editor: Angie J.French Materials Editor: Lance Anderson Subject Matter Expert: Gary Leenhouts Project TechnicalSupport: Mike Toscano

NOTICESDISCLAIMER: 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, andeach 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 2006 IBM Corporation.

Part Number: N7D760Course Edition: 1.0


4/363

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.

Copyright IBM Corporation 2006.

Lotus software, IBM Software Group

One Rogers StreetCambridge, MA 02142

All rights reserved. Printed in Ireland.

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.


5/363

Table Of Contents

Building the IBMLotusDomino7 Infrastructure

Lesson 1: Setting Up the First Server andAdministrator

Topic A: Deployment Plan Implementation . . . . . . . . . . . . . . . . . 2

Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The Worldwide Corporation Deployment Plan . . . . . . . . . . . . . . 9

Locating Supported Platforms and System Requirements . . . . . 10

Topic B: Install the Lotus Domino Server Software . . . . . . . . . . . . . 11

Lotus Domino Server Installation Types . . . . . . . . . . . . . . . . . . . . . 12

Topic C: Install the Lotus Domino Administrator Client Software. 14

Client Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Multiple Users Sharing One Workstation . . . . . . . . . . . . . . . . . . . . 15

Topic D: Set Up and Launch the First Server . . . . . . . . . . . . . . . . . . 17

First Server Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

The Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Domains versus Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Purposes of Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Alternatives to Organizational Units. . . . . . . . . . . . . . . . . . . . . . . . 23

Organization Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Descendants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Authentication Between Organizations . . . . . . . . . . . . . . . . . . . . 25

Country Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Server Audience Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Administrators Group Security Options . . . . . . . . . . . . . . . . . . . . . 27

Topic E: Set Up the First Workstation . . . . . . . . . . . . . . . . . . . . . . . . 30

The Workstation Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Topic F: Tracking Certified Lotus Notes User and IDs. . . . . . . . . . . 32

Organization Certifier ID Security . . . . . . . . . . . . . . . . . . . . . . . . . . 32

The Certification Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33The License Tracking Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

The Lotus Domino Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33



6/363

Topic G: Assign Roles to Administrators and Servers . . . . . . . . . . 33

Access in the Lotus Domino Directory . . . . . . . . . . . . . . . . . . . . . . 34

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

What Privileges Does the LocalDomainAdmins Group Lack? . . 34

Lesson 2: Adding Lotus Domino Servers

Topic A: Register Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

The Server Registration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Domino Directory Access for Registering Servers. . . . . . . . . . . . . 39

Always Select a Registration Server . . . . . . . . . . . . . . . . . . . . . . . . 39

Server ID File Storage Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Topic B: Set Up and Start an Additional Lotus Domino Server . . . 42Replicating a Subset of Documents in the Lotus Domino

Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43The Standard Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . 44

The Central Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Server Setup Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Clearing the Server ID Password. . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Lesson 3: Adding Lotus Notes Clients

Topic A: Create an Organizational Unit Certifier. . . . . . . . . . . . . . 52

Directory Entries for Organizational Units. . . . . . . . . . . . . . . . . . . . 53

Administrator Access to Register OU Certifiers . . . . . . . . . . . . . . . 53

Need for Selecting a Registration Server. . . . . . . . . . . . . . . . . . . . 53

Topic B: Register New Administrators. . . . . . . . . . . . . . . . . . . . . . . 55

User Registration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Administrator Access to Register Users . . . . . . . . . . . . . . . . . . . . . 56

Internet Password Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

ID File Distribution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Topic C: Register Users from a File . . . . . . . . . . . . . . . . . . . . . . . . . 58

User Registration Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Topic D: Replicate Server Document Changes . . . . . . . . . . . . . . 61

Lotus Domino Directory Document Synchronization. . . . . . . . . . 61

Topic E: Set Up an Administrator Workstation . . . . . . . . . . . . . . . . 62

The Workstation Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Topic F: Utilize Lotus Domino Administrator . . . . . . . . . . . . . . . . . . 64

The Lotus Domino Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . 65




7/363

Topic G: Create Replicas on Multiple Servers . . . . . . . . . . . . . . . . 67

The Administration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Components of the Administration Process . . . . . . . . . . . . . . . . . 69

Using Database Tools in Domino Administrator . . . . . . . . . . . . . . 70

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

Lesson 4: Administering Users

Topic A: Create and Nest Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 74

Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Nested Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Group Precedence in Database Access . . . . . . . . . . . . . . . . . . . 76

The Deny List Only Group Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Topic B: Create an Organizational Policy . . . . . . . . . . . . . . . . . . . 79

Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Settings Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Use of an Organizational Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Topic C: Create and Assign an Explicit Policy. . . . . . . . . . . . . . . . 84

Policy Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

The Effect of Multiple Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Policy Assignment When Registering Users . . . . . . . . . . . . . . . . . . 85

Topic D: Set Up ID File Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

ID File Backup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Setting Up ID File Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Topic E: Recover an ID File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Recovering an ID File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Lost ID Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Lesson 5: Setting Up Server Administration

Topic A: Select Domain and Registration Preferences. . . . . . . . . 96

Administration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Topic B: Customize Colors in the Server Console . . . . . . . . . . . . . 99

Message Color-Coding on the Server Console . . . . . . . . . . . . . . 100Topic C: Set Access to Create Databases on the Server . . . . . . . 101

Server Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Restrictions for Authorizing Server Access . . . . . . . . . . . . . . . . . . . 102

User Access to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103



8/363

Topic D: Restart the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Lotus Domino Server Console Administration Tasks . . . . . . . . . . . 105

Topic E: Set Administration Levels. . . . . . . . . . . . . . . . . . . . . . . . . . 105

Administration Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Details of the Administration Levels . . . . . . . . . . . . . . . . . . . . . . . . 106

The Full Access Administrator Level . . . . . . . . . . . . . . . . . . . . . . . . 108Administration Levels and the Lotus Domino WebAdministrator Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Topic F: Set Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

The Domino Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Lesson 6: Synchronizing Lotus Domino SystemDatabases

Topic A: Create Groups for Replication . . . . . . . . . . . . . . . . . . . . . 118Server Groups and Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Sample Server Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Topic B: Create a Connection Document . . . . . . . . . . . . . . . . . . . 121

Replication Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Replication Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Pull Push Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Multiple Replication Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Streaming Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

When to Use Streaming Replication . . . . . . . . . . . . . . . . . . . . . . . 127

Critical Application Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Replication Schedule Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Lesson 7: Configuring Basic Intranet Mail Routing

Topic A: Set Up Domino Named Networks . . . . . . . . . . . . . . . . . . 136

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

Mail Routing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Topic B: Implement a Hub-and-Spoke Mail Routing Topology. . 145

Mail Routing Between DNNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Hub-and-Spoke Mail Routing Topology . . . . . . . . . . . . . . . . . . . . 146Opportunistic Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Connection Document Mail Routing Options . . . . . . . . . . . . . . . 148

Router Types and Connection Documents . . . . . . . . . . . . . . . . . 149

Topic C: Select a Mail Storage Format for Incoming Mail . . . . . . 153

Mail Storage Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154




9/363

Lesson 8: Configuring Mail Routing to the Internet

Topic A: Enable the SMTP Listener Task . . . . . . . . . . . . . . . . . . . . . 160

SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Scenarios for Implementing the Use of SMTP . . . . . . . . . . . . . . . . 163Best Practices for SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Internet Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

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

The SMTP Listener Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

The SMTP listener and router tasks . . . . . . . . . . . . . . . . . . . . . . . . . 167

Topic B: Configure Basic SMTP Settings . . . . . . . . . . . . . . . . . . . . . 168

SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Topic C: Restrict Mail From or To the Internet . . . . . . . . . . . . . . . . . 171

SMTP Inbound Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

SMTP Outbound Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Prevent Relaying of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Topic D: Enable Whitelist and Blacklist Filters . . . . . . . . . . . . . . . . 175

What Are DNS Whitelist Filters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

DNS Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Enabling DNS Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

DNS Whitelist Filter Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

DNS Blacklist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Enabling DNS Blacklist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Private Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Enabling Private Whitelist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Private Blacklist Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Enabling Private Blacklist Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Whitelist and Blacklist Filter Configuration. . . . . . . . . . . . . . . . . . . 185

Topic E: Configure E/SMTP Options. . . . . . . . . . . . . . . . . . . . . . . . . 187

E/SMTP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Topic F: Configure Internet Addressing . . . . . . . . . . . . . . . . . . . . . 187

When to Set Internet Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Topic G: Test SMTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Worldwides Implementation of SMTP. . . . . . . . . . . . . . . . . . . . . . 191

Lesson 9: Establishing Mail Controls

Topic A: Configure Router Restrictions. . . . . . . . . . . . . . . . . . . . . . 196

Mail Restrictions and Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197



10/363


11/363

Topic B: Enable Mail Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Mail Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Topic C: Enable Message Tracking . . . . . . . . . . . . . . . . . . . . . . . . 241

Message Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Lesson 12: Resolving Common Mail RoutingProblems

Topic A: Send a Mail Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

The Mail Trace Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Topic B: Restart the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Restarting the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Topic C: Force Mail Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

When to Force Mail Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Topic D: Resolve Undelivered and Dead Mail. . . . . . . . . . . . . . . . 253

Undelivered and Dead Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Appendix A: Solutions to Practice Activities

Appendix B: Worldwide Corporation InfrastructurePlan

Topic A: The Worldwide Corporation Infrastructure Plan . . . . . . . 281

About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Organization Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

User Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Servers By Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Servers By Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Network Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Directory Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Replication Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Application Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Mail Routing Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Worldwide Corporation Naming Conventions . . . . . . . . . . . . . . 291

Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Server Configurations and Security . . . . . . . . . . . . . . . . . . . . . . . . 295

Client Configurations and Security . . . . . . . . . . . . . . . . . . . . . . . . 299

Implementing the Deployment Plan . . . . . . . . . . . . . . . . . . . . . . . 300



12/363

Appendix C: Additional Setup Information

Appendix D: Bibliography

Appendix E: Certification and Exam Competencies

Appendix F: Instructor Preparation

Additional Instructor Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333




13/363


14/363

Course DescriptionThis course covers installing and configuring a basic IBM Lotus

Domino 7 and IBM Lotus Notes 7 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 aclassroom. The course materials provide extensive background informa-tion, procedural tables, and best practice tips.

Upon completion of this course, students should be able to:

Consider deployment scenarios.

Install and set up Lotus Domino servers and Lotus Notes clients.

Implement a hierarchical naming scheme.

Create groups.

Specify desktop settings using policies.

Back up ID files.

Allow and restrict server access.

Allow administrators access to the Domino Directory.

Record server activity in the Domino Log file.

Set up the replication schedule to synchronize Domino system data-bases in the domain.

Configure intranet Domino mail routing.

Configure Internet mail routing.

Enable message controls.

Enable server and messaging monitoring.

Troubleshoot common mail setup problems.


Introduction

Introduction i


15/363

Audience

The target audience for this course is system administrators new to LotusDomino who are responsible for initial installation and setup of a basic LotusDomino and Lotus Notes 7 infrastructure and the set up of Domino Mailservers in the corporate intranet and extranet (i.e. Internet) environment.

Course Prerequisites

The prerequisites for this course include completion of the IBM Lotus

Domino 7 System Administration Operating Fundamentals course orequivalent knowledge, skills, and experience.

Course Strategy

Approach

The business context for this course is a small- to medium-sized companythat is using Lotus Notes and Lotus Domino as their basic mailinfrastructure. The course uses the fictitious company Worldwide Corpora-tion to provide scenarios for installing and setting up the infrastructure. Thecompany uses a single domain with Notes mail internally and SMTPexternally. This course assumes a classroom of 12 student machines. Toprovide all students with a comprehensive hands-on experience, we havedesigned this course so that all students administer their own servers. Toaccommodate this, we instruct students to use the client and server soft-

ware on the same machine. The Domino server and Notes client softwaresupports this configuration provided that the server and client software isinstalled in separate directories on the machine. While we recognize thatthis is not an optimal nor a recommended configuration to deploy in a realworld environment, we use this environment in the classroom to provide allstudents with the experience of administering their own servers.

Scenario

The course scenario is presented throughout the course materials. TheWorldwide Corporation scenario used in the Lotus Domino and Lotus Notescourses is here as an example.

Worldwide Corporation is a fictitious company that uses Lotus Domino andLotus Notes software. It operates a chain of retail stores in cities worldwide.In addition, the company runs an Internet-based retail operation, offerssmall-scale services, and has started a certification program for employees


Introduction

ii Introduction


16/363

and customers who want to become skilled potters. Lotus Domino andLotus Notes is Worldwide Corporations global standard for electronic mailand for developing and deploying groupware applications. Currently, thecompany uses Lotus Domino and Lotus Notes to:

Provide messaging and e-mail services to its deskless employees. Facilitate collaboration and communication among its geographically dis-

persed work force.

Communicate and coordinate relationships with its vendors andcustomers.

Communicate with a sibling subsidiary, a retail organization that special-izes in recorded music products.

Note: The sample screen captures and tasks presented in this plan areintended to support the course scenario. The fictitious user names, docu-ments, course titles, and store locations are used solely to simulate theLotus Domino and Lotus Notes environment and to demonstrate functions

and features. They are not intended to depict real people, content, or com-pany policies. Any likeness to real persons, content, or companies iscoincidental and unintended.

How to Use This Book

As a Learning Guide

Each lesson covers one broad topic or set of related topics. Lessons arearranged in order of increasing proficiency with Lotus Domino and Lotus

Notes; 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 Tool

Some of the information covered in class may not be relevant to your Lotus

Domino and Lotus Notes environment immediately, but it may becomeimportant later on. For this reason, we encourage you to spend some timereviewing the topics and activities after the course. The course can also beused in preparation for Lotus certification exams.


Introduction

Introduction iii


17/363

As a Reference

The 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 sourcefor definitions of terms, background information on given topics, and sum-maries of procedures.

Machine Requirements

Hardware

Instructor and Student Server Hardware Requirements

The following list identifies the hardware requirements for the instructor andstudent server machines.

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

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

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

At least 1.6 GB free hard disk space per partition, 40 GB isrecommended.

A mouse or other pointing device.

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

Internet access (recommended).

Note:

The requirements for the

student servers is sufficient

to support running a Lotus

Domino server and a Lotus

Domino Administrator client.


Introduction

iv Introduction


18/363

Instructor and Student Client Hardware Requirements

The following list identifies the hardware requirements for the instructor andstudent client machines.

At least 128 MB of RAM, 1 GB is recommended.

A Pentium Class processor.

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

At least 250 MB of free hard disk space.

A mouse or other pointing device.

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

Synchronize system time with all classroom machines.

Internet access (recommended).

Software

Instructor Server Software Requirements

The following list identifies the software requirements for the instructorserver machine and 12 student machines. Please note that proper licensingfor all software is required and is the responsibility of the trainingorganization.

Microsoft Windows 2003 Server (Service Pack 1 is not required butrecommended) or Microsoft Windows Server 2000 with Service Pack4.

Lotus Domino 7 Enterprise Server.

TCP/IP using either Hosts file or DNS with server and domain namesdefined in the TCP/IP protocol configuration.

Instructor and Student Client Software Requirements

The following list identifies the software requirements for the instructormachine and 12 student machines. Please note that proper licensing for allsoftware is required and is the responsibility of the training organization.

Microsoft Windows 2000 Professional with Service Pack 4 orMicrosoft Windows XP Professional with Service Pack 1 (Servicepack 2 is not required but recommended).

Lotus Domino Administrator 7. Netscape Navigator 4.7 or above or Microsoft Internet Explorer 5.5

or above.

TCP/IP using either Hosts file or DNS with server and domain namesdefined in the TCP/IP protocol configuration.

Microsoft Powerpoint Viewer (instructor only).

Note:

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.

Note:

The classroom setup allows

for up to 12 students, 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 toshare machines.

You may need to revise

some activities and

exercises.


Introduction

Introduction v


19/363

Classroom Setup

Lotus Domino naming used in the course

This course uses the following hierarchical naming scheme.

Table 0-1: Domino naming scheme

Naming Compo-

nent Classroom Implementation

Organization cer-tifier

/WWCorp

Domain WWCorp

Organizational

unit certifiers

SVR/WWCorp

East/WWCorpWest/WWCorp

Servers Administrators

Instructor Hub/SVR/WWCorp Doctor Notes/WWCorp

Students East01/SVR/WWCorp

East02/SVR/WWCorp

East03/SVR/WWCorp

East04/SVR/WWCorp

East05/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/WWCorp

Admin East02/WWCorp

Admin East03/WWCorp

Admin East04/WWCorp

Admin East05/WWCorp

Admin East06/WWCorp

Admin West01/WWCorp

Admin West02/WWCorp

Admin West03/WWCorp

Admin West04/WWCorp

Admin West05/WWCorp

Admin West06/WWCorp

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


Introduction

vi Introduction


20/363

Table 0-2: Required course files

File Name Function

Reg_East.txt

Reg_West.txt

Lesson 3 Used for registering users from

text files.

Rep_dd.txt Used throughout the course of replicating theDomino Directory to all classroom servers.

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

Test.abc Lesson 10 Used for demonstrating mailrules.

MailAgent.nsf Lesson 11 Used for sending messages fortracking purposes.

Checklist of classroom setup tasks

Complete 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 Uninstall Lotus Domino and Lotus Notes on all servers andclients.

2 Create the hosts file.

3 Install the classroom files.

4 Complete Individual Lesson Setup for Lessons 2, 3, 8, 10,and 11.

Task 1: Uninstall Lotus Domino and Lotus Notes on all servers andclients.

Uninstall Lotus Domino and Lotus Notes on all classroom machines toenable guiding students through the installation of both products. See theLotus Domino documentation for detailed steps.


Introduction

Introduction vii


21/363

Task 2: Create the hosts file.

Use 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.

IP addresses and server names

HubIPaddress Hub/SVR/WWCorp hub.wwcorp.com

IPaddress East/SVR/WWCorp East01.wwcorp.com

IPaddress East02/SVR/WWCorp East02.wwcorp.com





IPaddress West01SVR/WWCorp West01.wwcorp.com

IPaddress West02/SVR/WWCorp West02.wwcorp.com





Task 3: Install the classroom files

Follow these steps to install the \N7D760 course folder to the instructorsserver and client.

Step Action

1 To install the course data files from the CD-ROM, put the course CDin the server machine.

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

3 Double-click the N7D760dd.exe file.

4 Repeat the above steps on the instructor client machine.


Introduction

viii Introduction


22/363

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 both the instructor server and instructor clientmachines.

Directory Files Copied

\N7D760 Files:

Rep_dd.txt

Reg_East.txt

Reg_West.txt

N7D760_diag.ppt

Test.abc

Databases:

N7D760 Agent.nsf

MailAgent.nsf

Task 4: Complete Individual Lesson Setup for Lessons 2, 4, 8, 9, and

10.The following tasks should be completed before beginning each lesson orwhen indicated in an instructor note.

Lesson 2

In Lotus Domino 7, the LDAP task starts on the administration server. IfLDAP is not in the ServerTasks line of the Notes.ini file, LDAP is added tothe line. To prevent this behavior, make the following two changes in theNotes.ini of the administration server.

Enter the following on a separate line: DisableLDAPonAdmin=1

Remove the LDAP task from the ServerTasks line.

Lesson 3

Complete the following tasks.

Task Action

1 Copy the Set N7D760 fields agent from the supplied N7D760 Agent.nsf file to the Lotus Domino Directory on Hub/SVR/WWCorp. Selectall Server documents and run the agent to perform the following:

Add LocalDomainServers and Doctor Notes/WWCorp to theServer documentSecurity tabCreate new replicas field toenable the Administration Process to create a new replica.

Remove current contents of the Full Access Administrators field

and 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 program directory.

Note:This guide also includes

instructor notes outlining

tasks to perform before or

during each lesson in order

to set up activities or

demonstrations in the

lesson.


Introduction

Introduction ix


23/363

Task Action

3 Copy the following two files to the instructors client data directory:

Reg_East.txt

Reg_West.txt

4 Provide students the appropriate certifier ID files:

East.id for students in the /East/WWCorp OU

West.id for students in the /West/WWCorp OU

5 After the Register users from a text file demo, but before the Safe-guarding ID Files section, detach the ID from the Person documentfor Michelle Grassi. Create a Location document for this user. Verifythat this users mail file was created on Hub/SVR/WWCorp.

Lesson 8

Complete the following task.

Task Action

1 Add Doctor Notes (or any account you might use) to the ACL of theMail.box on Hub/SVR/WWCorp with Manager access and allpermissions. This enables a demo in this lesson in which you viewdocuments in the Mail.box.

Lesson 10


Task Action

1 Copy Test.abc to instructors server data directory.

2 Create two or three mail rules.

Lesson 11


Task Action

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

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


Introduction

x Introduction


24/363

Task Action

3 Run the message tracking agent to send messages to students fortracking purposes.

Course Icons

The following table explains the icons used in this course:

Table 0-4: Course Icons

Icon Description

Indicates an activity.

Cautions are short, descriptive paragraphs meant to warn ofpotential pitfalls or areas where students could experience prob-lems during class or back on the job.

Indicates an Instructor demo. This text is visible only in the instruc-tor manual.

Instructor notes: Special notes the course developer want to com-municate to the instructor regarding delivery, classroom strategy,classroom tools, exceptions, and other special considerations.These notes are visible only in the instructor manual.

Indicates when to display a specific slide contained in the coursePowerPoint file. These are visible only in the instructor manual.

Indicates scenario information for an activity.

A note or tip provides additional guidance, or a hint, for studentsabout a topic or task.


Introduction

Introduction xi


25/363


26/363

Setting Up the First Server andAdministrator

Topic A: Deployment Plan Implementation

Topic B: Install the Lotus Domino Server Software

Topic C: Install the Lotus Domino Administrator Client Software

Topic D: Set Up and Launch the First Server

Topic E: Set Up the First Workstation

Topic F: Tracking Certified Lotus Notes User and IDs

Topic G: Assign Roles to Administrators and Servers

1

Copyright IBMCorporation2006.


27/363

Topic A: Deployment PlanImplementationPlanning is a critical step in the process of implementing an IBM LotusNotes and 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 topic covers basic guidelines and considerations to use when planning

a Lotus Notes and Lotus Domino implementation and introduces World-wides deployment plan and implementation checklist.

After completing this topic, you should be able to:

Identify basic planning considerations and guidelines.

Identify the process for implementing a Lotus Domino infrastructure.

Note: Since this is not a planning course, in-depth planning issues are notdiscussed. This lesson presents high-level planning considerations and guidelinesthat will 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 will

be used as the basis for this course. It will be revisited in each lesson to demon-strate progress.

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 organizationalstructure.

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

Checklist: Planning the Domino EnvironmentWorldwide corporation used the following checklist to plan theirinfrastructure.

Note:

Introduce the topic. The

main goals of this topic are

to:

Emphasize the impor-

tance of creating a

deployment plan.

Introduce Worldwide

Corporations deploy-

ment plan (see theWorldwide Corporation

Infrastructure Plan

appendix).

Provide basic guidelines

for planning an

infrastructure.

Introduce Worldwides

implementation checklist,

which students will use

throughout the course to

install and set up the

infrastructure.

Display slide:

Planning Checklist

A

TopicA: Deployment Plan Implementation

Lesson 1 Setting Up the First Server andAdministrator

2 Copyright IBM Corporation 2006.


28/363

Task Procedure

1 Identify structure of organization

2 Create planning team.

3 Identify tracking mechanism.

4 Define the business problem.

5 Identify how Domino can address the business problem.

6 Identify access needs.

7 Identify hardware requirements (site map).

8 Identify server roles.

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.



Copyright IBM Corporation 2006. 3


29/363

Planning guidelinesSeveral areas need to be considered when planning a Lotus Dominoinfrastructure. It is important to determine and follow guidelines to ensurethat all tasks are properly carried out. The following table provides some

guidelines for planning tasks.

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 planningreference.

Task Guidelines

Identify structure of organi-zation:

Examine currentstructure.

Validate with uppermanagement.

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 title to the skills.

Identify gaps in skills and/or human resources.

Ensure approval from upper management.

Note:

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.





30/363

Task Guidelines

Identify tracking mecha-nism to:

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 the information will 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 atest server

Existing project management software

Define the businessproblem.

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





31/363

Task Guidelines

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 infra-structure to support Lotus Domino.

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

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.





32/363

Task Guidelines

Identify network protocol(s)and networking changes.

Identify network connections based on:

Network protocols (recommended protocol

TCP/IP) Network traffic (LANs and WANs) amount of

bandwidth needed depends on:

The amount of mail traffic and databasereplication

How traffic is routed (shared applications onthe same network)

Clustering, if clustered servers areimplemented

Lotus Domino Named Networks, including:

Connection types (protocols available,bandwidth)

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 anapplication that is replicated betweenservers?

Who communicates with whom most often?

What dialup connectivity is required?

Choose replicationtopology.

Identify who needs access to what informationand when.

Identify where to put applications to bereplicated.

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 serv-ers replicate with each other, the frequency ofreplication, and any restrictions that are in place.

Place applications in geographic locations by

workgroups.





33/363

Task Guidelines

Identify directory strategy. Identify domain or domains.

Define directory structure by domain.

Identify how the Lotus Domino Directories willbe used.

Identify the external directories that will beaccessible to Lotus Domino users.

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

Determine whether to use Directory Catalogs(for mobile users).

Select mail routingstrategy.

Identify mail clients.

Identify which mail routing protocol or protocolsto use based on client types.

Determine message format based on clienttypes.

Decide on security mechanism(s).

Determine how mail is routed using a topologymap.

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





34/363

Task Guidelines

Determine serverconfigurations.

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 clientconfigurations.

Identify Lotus Domino client types.

Identify non-Lotus Domino client configurations.

Identify user mail configurations.

Determine rollout strategy. Identify project milestones and deadlines.

Identify who is responsible for projectmilestones.

Determine educationstrategy.

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 Organization athttp:/www.redbooks.ibm.com.

Lotus Domino Administrator 7 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





35/363

Note that the server names in the plan accommodate a mail and applicationenvironment, whereas in this course only the mail servers will beimplemented. Therefore, the server names have been modified from theones presented in the plan.

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

Locating Supported Platforms and System

Requirements

The Release Notes for each version of Lotus Domino contain a section onsupported platforms and system requirements. Refer to the By CategoryThings you need to knowPlatforms and requirements topic in theRelease Notes.

Display slide:

Classroom Implementation

Note:

Provide overview of

classroom implementation.

See Additional Instructor

Notes

Display slide:

Implementation Checklist





36/363

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 Lotus 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 throughoutthe domain.

15 Route mail internally.

16 Route mail to the Internet.

17 Set mail controls.

18 Test mail routing and delivery.

Note:

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

Corporation Infrastructure

Plan in Appendix B.

Because this class focuses

on a basic infrastructure, it

does not include setting upa Web server or configuring

mobile, non-Domino, and

Internet clients.





37/363

Topic B: Install the Lotus DominoServer SoftwareThis topic focuses on the installation of the first server. You will use thecomponents created during the first server setup to set up the rest of theservers and users in the domain in the upcoming lessons.

The administrators for Worldwide Corporation will begin implementation withthe first Lotus Domino server. The following components result from settingup the first server, which will be used to implement the rest of the plan:

Organization certifier

Server name

Administrators name

Directory of resources in the domain


Identify Lotus Domino server installation types.

Install the Lotus Domino server software.

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 Domino Utility server Provides custom database applicationsfor Lotus Notes and Web clients, andLotus Domino database transactionlogging.

Application services only

Support for Lotus Domino clusters

Note: This does not include support formessaging services.

Lotus Domino Messaging server Provides Lotus Domino and Internetmail services.

Messaging services

Note: This does not include support forapplication services or Lotus Dominoclusters.

Display slide:


Note:

Review checklist. At the end

of this lesson, the following


items will be complete:

Set up the first server.

Add an administrators

workstation.

Set up access to the

Lotus Domino Directory.

B





38/363

Server Type Function

Lotus Domino Enterprise server Both messaging and application

services

Support for Lotus Domino clustersNote: To cluster mail servers, theLotus Domino Enterprise server isrequired.

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 checkbox deselected during installation of the classroomservers.

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 7 Help.





39/363

Activity 1-1: Install the Lotus Domino serversoftware

Scenario: Each server will be a Lotus Domino Enterprise server toallow for all possible configurations.

Installing the Lotus Domino server software copies executables, databasetemplates, and other files to the hard drive. On Microsoft Windows plat-forms, the installation also creates registry entries. Follow these steps toinstall the Lotus Domino Enterprise server software.

Step Action

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

2 On the Welcome screen, click Next.

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

4 Accept the default folder or click Browse to change the drive on whichto install Lotus Domino. Use the following directory structure:

Program files: drive:\Lotus\DominoClick Next.

5 Accept the default folder or click Browse to change the drive on whichto install the Lotus Domino data files. Use the following directorystructure:

Data files: drive:\Lotus\Domino\dataClick Next.

6 Select Enterprise server, and click Next.

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

8 Click Finish to complete the installation.

Note:

Lead students in installing

the Lotus Domino

Enterprise server on all

classroom servers.

Step 1: Direct students to

the appropriate location of

the install executable.

Steps 4 and 5: Provide

students with the correct

drive on which to install the

software.

Step 8: While the softwareis installing, move on to the

next section.





40/363

Topic C: Install the Lotus DominoAdministrator Client SoftwareAdministrators require a client to administer the Lotus Domino servers.Worldwide administrators will use the Lotus Domino Administrator client toperform all administrative tasks.


Install the Lotus Domino Administrator client software.

Client Installation Types

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

Client Type Purpose

Lotus Notes An interface for working with Lotus Notes databasesand Internet data.

Lotus Domino Adminis-trator

An interface for administering Lotus Domino systems.

Lotus DominoDesigner

An interface for adding functionality to new or existingdatabases.

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

Multiple Users Sharing One Workstation

Many environments require different users to share programs on aworkstation. The Lotus Notes workstation installation offers a multi-useroption so that multiple users can share a Lotus Notes client, with each usermaintaining 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 7 Help.

C





41/363

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

Topic C: Install the Lotus DominoAdministrator Client Software




42/363

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 accommodatethis, you will run the client and server software on the same machine. The LotusDomino server and Lotus Notes client software support this configuration providedthat the server and client software is installed in separate directories on the machine.While we recognize that this is not an optimal nor a recommended configuration todeploy in a real world environment, we use this environment in the classroom toprovide you with the experience of administering your own servers.

Scenario: Worldwide administrators will install the Lotus DominoAdministrator client which they will use to administer Lotus Dominoservers.

Follow these steps to install the Domino Administrator client software ondesignated workstations in the classroom.

Step Action

1 Run the Lotus Notes 7 client installation executable, Setup.exe, fromthe location provided by the instructor.


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

4 On the next screen, enter the following information:

User Name:Enter your assigned user name.For example, type Admin East01

Organization: Type WWCorpThen, click Next.

5 On the next screen, select the following folders:

Install program files to the drive:\Notes directory.

Install data files to the drive:\Notes\data directory, where drive isprovided by the instructor.

Then, click Next.

6 On the Custom Setup screen, click Domino Administrator, and selectThis feature, and all subfeatures, will be installed on local hard

drive.Click Next to install the default client components.

7 Click Install to begin copying files.

8 Click Finish to complete the installation.

Note:

Step 1: Direct students to

the appropriate location of

the install executable.

Step 5: Provide students

with the correct drive on

which to install the software.

While the software is

installing, move on to the

next section.





43/363

Topic D: Set Up and Launch the FirstServer


Identify alternatives to organizational units.

Identify how an organization provides security.

Identify how authentication occurs between organizations.

Identify descendants.

Set up and launch the first server.

First Server Setup

After installing the server software, an administrator must launch the serverto configure it. First server setup creates the Lotus Domino environment towhich other servers and users are added.

The first server setup program creates the components described in the fol-lowing table.

Component Stored In

A Lotus Domino Directoryfor the new domain

The servers data subdirectory, as Names.nsf

An organization certifier forthe organization Cert.id file in the Lotus Domino servers data

subdirectory

Certifier document in the Lotus Domino Direc-tory

(Optional) An organiza-tional unit certifier

Oucert.id in the data subdirectory

Certifier document in the Domino Directory

A Server document for theserver

The Domino Directory

A server ID stamped by

the organizations certifier

The Server document and/or the servers data

subdirectory

A Person document for theadministrator


Display slide:

Components from First

Server Setup

D





44/363

Component Stored In

The administrators IDstamped by the organiza-tions certifier

The Person document and/or the servers datasubdirectory

The following figure illustrates the components in the preceding table.

Figure 1-2: Components from first server setup


The Domino Directory is the most important database in the Lotus Dominoenvironment. It contains information about all Lotus Domino resources andhow the resources function, and it is the database that contains the informa-tion created and updated using Lotus Domino Administrator. Each additionalserver in the domain has a replica of the Domino Directory.

Note:

Summarize the key

components created by first

server setup. Use the

diagram shown in Figure

1-2 to illustrate the files

created during the first

server setup.

Note:

Stress the significance of

the Domino Directory.





45/363

Replicas of the Domino DirectoryThe following figure represents Domino Directories on different servers. Thearrows represent replication, keeping the information synchronized.

Figure 1-3: Domino Directories on different servers





46/363

Instructor Activity 1-3: Review domains andorganizations

Complete the following to review.

1. What is a domain?

A domain is a collection of servers and users that share a single Domino

Directory. The domain name is typically the company name.

2. If a company has two domains, how many Domino Directories areneeded?Two Domino Directories are neededone per domain.

3. Does the collection of servers and users in the Domino Directory consti-tute a domain or an organization?

A domain.

4. What is an organization?

An organization is an entity that authorizes users and servers to authenticate

with one another. The primary purpose is security.

5. Does the organization name have to be the same as the domain name?

No. For simplicity, Worldwide Corporation is using WWCorp for the domain

and organization name. The names could be different if needed.

Domains versus Organizations

Note the following differences between a domain and an organization:

A Domino domain is the collection of Domino servers and users thatshare the same Domino Directory.

A Domino organization is defined by the certifier that stamps the IDs ofusers, servers, and other certifiers. There is a trust relationship withinthe organization so that users and servers can communicate and sharedata. The organizational certifier provides security and uniformity in nam-ing of users and servers. The certifier name is part of the hierarchicalname of all users and servers in the organization.

When to use multiple domainsLarge enterprise corporations might consider defining regions or countriesas separate domains in order to keep the Lotus Domino Directory manage-able for administrators, to facilitate name lookup, and to maintain goodserver performance.

Note:

This activity reviews student

knowledge from the IBM

LotusDomino7 System

Administration Operating

Fundamentals course.

Note:

The material represented

here is not new material. It

serves as a review of

prerequisite knowledge.





47/363

Tip: Consider placing Web servers accessible via the Internet in a separate domainand organization to maintain a secure environment.

Purposes of Organizational Units

Dividing an organization into organizational units (OU) allows for:

Management by region or division. For example, database ACLs canspecify different privileges for each OU.

Separation of servers from users. For example, an administrator caneasily:

Cross-certify the OU containing all servers with another organization.

Not cross-certify users with the other organization.

Unique names for users who have the same common name.

Naming requirements for an organizational unitThe organizational unit name can be a maximum of 32 characters and mayinclude alphabetic characters (A - Z), numbers (0 - 9), and the ampersand(&), dash (-), period (.), space ( ), and underscore (_). For information onnaming requirements for this and other Lotus Domino components, refer tothe Lotus Domino Administrator 7 Help document titled Table of NamingRequirements.

Note: The space character is not recommended because programs otherthan the Lotus Notes client may not allow spaces.

Sample organizational structureWorldwide Corporations deployment plan divides /WWCorp into three orga-nizational units.

Worldwide Corporation is using the following organizational structure:

The organization certifier is /WWCorp.

All servers will be in an organizational unit named /SVR/WWCorp.

Users will be in one of the following organizational units:

/East/WWCorp

/West/WWCorp





48/363

The following diagram represents the certifiers in Worldwides Lotus Dominoorganization hierarchy. The organization certifier is /WWCorp and the threeorganizational unit certifiers are descendants of /WWCorp.

Figure 1-4: Worldwides Lotus Domino organization hierarchy

Alternatives to Organizational Units

A company may choose not to use organizational units. There are methodsthat serve similar purposes for those Lotus Domino environments:

Group documents can enable management of subsets of the population.For example, a group document can contain all people in the Eastdivision.

In smaller organizations, servers may not need to be separated fromusers.

Differentiating two users who have the same first and last name andneed to be certified by the same certifier can be accomplished in twoways:

The middle initial can be included as part of the common name.

The user registration dialog has an option to create a unique organi-zational unit. This adds an OU component to the user name, but theOU name does not really exist as a separate certifier.





49/363

Instructor Activity 1-4: Review possiblehierarchical names

Scenario: Each server and end user is certified by a certifier. World-wide will use certifier names that:

Indicate the region where the users work.

Indicate the servers being separate from users.

The following diagram displays Worldwides Lotus Domino organiza-tional hierarchy and the users and servers certified by each certifier.Your instructor will ask you to identify various hierarchical namesbased upon this diagram.

Figure 1-5: Worldwides Lotus Domino organizational hierarchy

Answer the following questions to review.

1. What is the hierarchical name for the Admin East01 user?Admin East01/East/WWCorp

2. What is the hierarchical name for the West02 server?

West02/SVR/WWCorp

3. What is the hierarchical name for the East03 server?East03/SVR/WWCorp

4. What is the hierarchical name for the user Marcus Frank who works inthe eastern division of WWCorp?Marcus Frank/East/WWCorp

Display slide:

Organizational Hierarchy





50/363

5. What is the hierarchical name for a different Marcus Frank who works inthe western division of WWCorp?Marcus Frank/West/WWCorp

Organization SecurityAll users and servers within the /WWCorp hierarchy will be able to authenti-cate with each other. For example, when a user opens a database on aserver, the user and server will check each others certificates to verify thatthey are both descendants of the /WWCorp certifier. If so, the user databasewill open unless another security measure restricts access.

Descendants

The deployment plan calls for setting up one organization hierarchy. There-fore, all names are descendants of the /WWCorp organization certifier.

Certifier IDs stamp server, user, and other certifier IDs with theircertificates. The /WWCorp organization certifier stamps one entity, theuser Doctor Notes.

The /WWCorp certifier stamps the following OU certifiers which willtamp the IDs for other users and servers:

/SVR

/East

/West

Authentication Between Organizations

If Worldwide Corporation merges with another company, for example, AcmeCorporation, the Lotus Notes and Lotus Domino infrastructures would not beable to communicate without administrative intervention. Administrators canperform a technique called cross-certification to establish trust betweenthe two Domino organizations. Refer to the Lotus Domino Administrator 7Help for more information about cross-certification.





51/363

Country Codes

In an international organization, using country codes requires creating mul-tiple organization certifiers (one for each country code). For example, ifWorldwide Corporation chose to use country codes for branches in the US,Great Britain, and Brazil, there would be three organizations:

/WWCorp/US

/WWCorp/GB

/WWCorp/BR

A country code does not replace the organization component, but rather isan additional, higher-level component in a hierarchical name. The organiza-tion is the grandparent, while the country code is the great-grandparent.

Note: Using country codes increases administrative work. Recommendations foraccommodating regions using organizational units describes an alternative to using

country codes.

Country codes and hierarchical namingThe country codes position, furthest to the right in the hierarchical name,makes it the highest-level component of the hierarchy.

Each certifier that uses a country code is a separate hierarchy, even ifthe organization name is the same.

Users and servers in different hierarchies cannot automaticallyauthenticate. They must be cross-certified.

An administrator must cross-certify the organizations with country codes,

requiring additional administrative work.

For example, users and servers under /WWCorp/US and /WWCorp/GB can-not automatically authenticate because they are separate hierarchies.

Recommendations for accommodating regions using orga-nizational unitsUse the following guidelines for deciding on organizational units:

As an alternative to using country codes, use the first OU level to desig-nate the country, for example, /US/WWCorp.

Use the second OU level for region or department names to further dis-

tinguish users, for example: /East/GB/WWCorp, or

/ISS/GB/WWCorp

A hierarchical name can be comprised of up to four organizational units.However, in general, do not use more than three organizational units.

Note:

Describe classroom

implementation. Remind

students that Worldwide

Corporation has chosen to

indicate regions, rather thancountries, in OU names and

not to use country codes.





52/363

Server Audience Types

The audience selected during server setup determines the server tasks thatwill run on the Lotus Domino server to accommodate the type of users whowill access the server. The following table describes the types of serveraudiences.

Server Audience Description

Web browsers For Web browsers, such as Microsoft InternetExplorer and Netscape Navigator, to access data onthe server.

Internet mail packages For Internet mail clients using the following protocolsto access mail on the server:

POP3 (Post Office Protocol 3)

IMAP (Internet Message Access Protocol) SMTP (Simple Mail Transfer Protocol)

Directory Services For clients using LDAP (Lightweight Directory AccessProtocol). The LDAP task starts automatically on theadministration server of the Domino Directory.

Selecting Internet Protocols during setupFor convenience, the server setup program offers the ability to selectInternet protocols that will load automatically during server startup. Thesecan be configured later if not selected during server setup.

Administrators Group Security Options

The server setup program contains options for adding entries to ACLs.

The Prohibit anonymous access option adds an ACL entry calledAnonymous to all databases, and gives it the No Access ACL setting.

The LocalDomainAdmins option creates a group that gives some or alladministrators Manager access to all databases. This is accomplishedas follows:

A group named LocalDomainAdmins is created in the Domino Direc-

tory and is given Manager access to all databases created on theserver.

The first servers administrator is added to LocalDomainAdmins dur-ing first server setup. Other administrators can be added to thegroup later.





53/363

Setting up and launching the first server

Follow these steps to set up the first server.

Task Procedure

1 Start the Domino server to run the setup program. From Windows,choose StartProgramsLotus ApplicationsLotus DominoServer.

Note: Options for accessing the Domino Server Setup program varyby platform, and are covered in the appropriate installation guide.

2 On the next screen, select Start Domino as a regular application,check the Dont ask me again box, and click OK.


4 Select Set up the first server or a stand-alone server, and click Next.

5 Enter the following information:

The designated name of the server.

(Optional) Enter a title. For example, enter a description of theservers purpose.

(Optional) Select I want to use an existing server ID file, to usea server ID file from a previous installation.

Then, click Next.

6 Enter the following information for the organization:

Organization name: Enter the designated organization name.

Organization Certifier password: Enter the designated organiza-tion password for the organizations certifier ID file.

Confirm password: Enter the same password.

(Optional) Select I want to use an existing certifier ID file, touse an organization certifier ID file from a previous installation.

(Optional) Click Customize and enter the following information:

Organizational Unit name: The designated organizational unitname.

Org. Unit Certifier password: Enter the designated passwordfor the organizational units certifier ID file.

Confirm password: Enter the same password.

(Optional) Select I want to use an existing organizationalunit certifier ID file, to use an organizational unit certifier IDfile from a previous installation.

(Optional) Select a country code.

Click OK.Then, click Next.

Demo:

Demonstrate this procedure

using the Additional

Instructor Notes.

See Additional Instructor

Notes

Note:Step 6: Point out the

following information about

the organizational unit (OU)

certifier ID file:

The file name of this OU

certifier ID file is always

Oucert.id. The file name

can be changed at the

operating system later, if

needed.

The dialog box provides

examples of a servers

final name and a users

final name. The user

example is Bob/SVR/

WWCorp. Tell students

that they will create dif-

ferent OUs for the users

and that the /SVR/

WWCorp OU will be for

servers only.

The first Administrative

user will be certified at

the organization level,

and will not be in an OU.





54/363

Task Procedure

7 Enter the designated domain name, and click Next.

8 Provide the following information about the administrator of the server:

Enter the designated first and last names of the administrator. Enter the administrators password and confirm the password.

(Optional) Select Also save a local copy of the ID file.

(Optional) Select I want to use an existing Administrator IDfile, to use an administrator ID file from a previous installation.

Then, click Next.

9 Select the appropriate Internet service types, or click Customize

Instructor Guide ND760 - CT3UBNA

Documents

Transcript of Instructor Guide ND760 - CT3UBNA