Installing and Managing Domino 6.5 for iSeries Lotus software

Lotus software

Lotus Domino 6.5 for iSeries

Installing and Managing Domino 6.5 for iSeries

®

Copyright and Trademark Information

Disclaimer; No Warranty

THIS INFORMATION AND ALL OTHER DOCUMENTATION (IN PRINTED

OR ELECTRONIC FORM) ARE PROVIDED FOR REFERENCE PURPOSES

ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS

AND ACCURACY OF THIS INFORMATION, THIS INFORMATION AND ALL

OTHER DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT ANY

WARRANTY WHATSOEVER AND TO THE MAXIMUM EXTENT

PERMITTED, LOTUS AND IBM DISCLAIM ALL WARRANTIES,

INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF

MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A

PARTICULAR PURPOSE, WITH RESPECT TO THE SAME. LOTUS AND IBM

SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES, INCLUDING

WITHOUT LIMITATION, DIRECT, INDIRECT, CONSEQUENTIAL OR

INCIDENTAL DAMAGES, ARISING OUT OF THE USE OF, OR OTHERWISE

RELATED TO, THIS INFORMATION OR ANY OTHER DOCUMENTATION.

NOTWITHSTANDING ANYTHING TO THE CONTRARY, NOTHING

CONTAINED IN THIS INFORMATION OR ANY OTHER DOCUMENTATION

IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY

WARRANTIES OR REPRESENTATIONS FROM LOTUS AND IBM (OR

THEIR SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND

CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING

THE USE OF THIS SOFTWARE.

Under the copyright laws, neither this 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 prior written consent of

IBM Corporation, except in the manner described in the documentation or the applicable licensing agreement governing the use of the software.

© Copyright IBM Corporation 1998, 2003

All rights reserved. Printed in the United States.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GS ADP Schedule Contract with IBM Corp.

Lotus Software, IBM Software Group

One Rogers Street

Cambridge, MA 02142

Trademarks

iSeries and iSeries Client Access Express are trademarks and IBM, Operating

System/400, and PowerPC are registered trademarks of International Business

Machines Corporation. Domino, Sametime Connect, and QuickPlace are trademarks and Lotus, Lotus Notes, and Sametime are registered trademarks of Lotus

Development Corporation and/or IBM Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of

Sun Microsystems, Inc. in the United States, other countries, or both. MeetingPlace is a trademark of Latitude Communications, Inc. Microsoft, NetMeeting, Outlook,

Windows, Windows NT, and the Windows logo are trademarks of Microsoft

Corporation in the United States, other countries, or both. Pentium is a registered trademark of Intel Corporation in the United States, other countries, or both. Other product and company names mentioned herein may be the trademarks or registered trademarks of their respective owners.

Contents

1 Getting Started With Domino for iSeries

. . . . . . . . . . . . . . . . . . . . . . . . .

What is Lotus Domino for iSeries?

What's new in Domino 6 for iSeries?

. . . . . . . . . .

. . . . . . . . .

How do I administer Domino on iSeries?

Domino for iSeries server requirements

. . . . . . .

. . . . . . . .

Where do I find more information?

How do I get fixes?

. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

1

1

1

3

4

6

7

2 Upgrading the Domino Software

.

9

Considerations for upgrading from previous versions of Domino

. . . . . . . . . . . . . . . .

Considerations for upgrading to future releases

. .

9

12

What happens when the Domino software is upgraded?

. . . . . . . . . . . . . . . . . . . .

Ending Directory Synchronization tasks

Ending the MSF and SMTP services

. . . . . .

. . . . . . . . .

Moving from Mail Server Framework to Native

Notes

. . . . . . . . . . . . . . . . . . . . . . .

Verifying that all mail is delivered

Performing the Domino upgrade

. . . . . . . . . .

. . . . . . . . . . .

How do I upgrade the Domino for iSeries

Navigator plug-in?

. . . . . . . . . . . . . . .

3 Installing Domino On Your iSeries Server

. . . . . . . . . . . . . . . . . .

OS/400 authorities required to install and configure

Domino

. . . . . . . . . . . . . . . . . . . . . .

Verifying the installed iSeries software

. . . . . . .

What should I know before I install Domino?

Is my iSeries server properly sized?

. . .

. . . . . . . . .

Installing the Domino software

. . . . . . . . . . . .

What software should I install?

. . . . . . . . . .

13

14

14

15

17

17

18

21

21

23

23

25

26

26

How do I install the Domino software?

. . . . .

What happens when the Domino software is installed?

. . . . . . . . . . . . . . . . . . . . .

Verifying that the Domino software is installed

. .

4 Planning the Domino for iSeries

Environment

. . . . . . . . . . . . . . . . . . .

How should I set up TCP/IP for Domino for iSeries?

. . . . . . . . . . . . . . . . . . . . . .

Verifying the iSeries TCP/IP setup and status

Determining if TCP/IP is set up

. . .

. . . . . . . . .

Determining the Internet address and host name to use for Domino

. . . . . . . . . . . . . . . .

Starting TCP/IP

. . . . . . . . . . . . . . . . . . .

Verifying TCP/IP interface status

. . . . . . . .

How does Domino interact with other programs on my iSeries server?

. . . . . . . . . . . . . . .

5 Preparing the Administrator's

Workstation

. . . . . . . . . . . . . . . . . . . .

Installing iSeries Navigator

. . . . . . . . . . . . . .

Verifying that NetServer is running

. . . . . . .

Verifying access to the NetServer file share

Installing the Domino plug-in

. .

. . . . . . . . . . .

6 Setting Up a First Domino Server

Deciding what to specify for server characteristics

What happens during first server setup?

. . . . . . .

7 Setting Up Multiple Domino

Servers On the Same iSeries Server

What is Domino partitioning?

. . . . . . . . . . . .

Preparing the TCP/IP network for partitioned

Domino servers

. . . . . . . . . . . . . . . . .

Configuring a partitioned Domino server

. . . .

27

30

31

33

35

35

36

33

34

34

36

41

42

48

37

38

38

39

40

51

51

52

53

iii

8 Setting Up an Additional Domino

Server

. . . . . . . . . . . . . . . . . . . . . . . .

Registering the additional server

. . . . . . . . . . .

Verifying the TCP/IP connections to the iSeries server

. . . . . . . . . . . . . . . . . . . . . . .

Copying the ID files for the additional server to the iSeries server

. . . . . . . . . . . . . . . . . .

Setting up an additional server using iSeries

Navigator

. . . . . . . . . . . . . . . . . . . .

What happens during additional server configuration?

. . . . . . . . . . . . . . . . . .

9 Managing the Domino Server

Overview

. . . . . . . . . . . . . . . . . . . . . .

Ways of managing a Domino server on an iSeries server

. . . . . . . . . . . . . . . . . . . . . . .

iSeries server authority requirements for Domino administrators

. . . . . . . . . . . . . . . . . .

Overview of using iSeries Navigator to manage a

Domino server

. . . . . . . . . . . . . . . . . .

Overview of using the Java Server Console to manage a Domino server

. . . . . . . . . . .

Overview of using the Domino Administrator client to manage a Domino server

. . . . . . . . . .

Using the Verity KeyView filter

Fault recovery operation

. . . . . . . . . . .

. . . . . . . . . . . . . . . .

10 Managing a Domino Server

Using iSeries Navigator

. . . . . . . . . .

Starting a Domino server using iSeries Navigator

.

Stopping a Domino server using iSeries Navigator

Stopping a Domino subsystem using iSeries

Navigator

. . . . . . . . . . . . . . . . . . . .

Starting the Java Server Controller

. . . . . . . . . .

Determining the server status using iSeries

Navigator

. . . . . . . . . . . . . . . . . . . .

Changing a Domino server's properties using iSeries Navigator

. . . . . . . . . . . . . . . .

Editing the NOTES.INI file using iSeries Navigator

Why are partial server properties displayed?

. . . .

55

56

57

58

60

63

65

65

66

68

68

72

73

74

74

75

75

71

71

72

69

69

70

Installing the Domino Administrator client

Launching the Domino Administrator client

. . . . .

. . . .

11 Registering and Managing

Users

. . . . . . . . . . . . . . . . . . . . . . . . .

Setting up Domino for iSeries users

. . . . . . . . .

Using iSeries Navigator to add users

About Domino for iSeries Single Logon

. . . . . . . .

. . . . . .

76

76

12 Using Domino for iSeries

Multi-version Capabilities

. . . . . . . .

Overview of multi-version terms and concepts

. . .

Preparing for multi-version capable releases

Installing multi-version capable releases

. . . .

. . . . . .

Updating to a multi-version capable release from a release that is not multi-version capable

. . . . . . . . . . . . . . . . . . . . . .

Installing multiple releases of Domino

. . . . . . .

Removing multi-version capable releases

Managing multi-version capable releases

. . . . . .

. . . . . .

Using applications with multi-version capable releases

. . . . . . . . . . . . . . . . . . . . . .

13 Domino for iSeries Security

Overview

. . . . . . . . . . . . . . . . . . . . . .

About the QNOTES user profile

. . . . . . . . . . .

83

83

85

86

88

88

89

90

93

97

97

About OS/400 support for Domino access control

. . . . . . . . . . . . . . . . . . . . . .

100

14 Integrating Domino for iSeries

With Other Database Management

Systems

. . . . . . . . . . . . . . . . . . . . . . .

Setting up DECS

. . . . . . . . . . . . . . . . . . . .

105

106

About authority when Domino applications access DB2 UDB for iSeries

. . . . . . . . .

107

15 Using Domino as a Mail Server

Overview of Domino mail

. . . . . . . . . . . . . . .

Configuring multiple instances of SMTP

. . . . . .

.

113

113

114

Settings for Domino SMTP support

. . . . . . . . .

Modifying the existing Domino configuration

. . .

115

116

79

79

80

81

iv

16 Using Domino as a Web Server

WebSphere and Domino integration

HTTP server options

. . . . . . . . .

. . . . . . . . . . . . . . . . . .

119

119

120

Avoiding conflicts between the iSeries HTTP server and the Domino HTTP server

. . . . .

121

Serving documents from the QSYS.LIB file system

Setting up CGI-BIN programs

. . . . . . . . . . . .

Defining the location of a CGI-BIN program

Creating SSL key ring files

. .

. . . . . . . . . . . . . .

122

123

123

124

17 About Directory Services and

Domino

. . . . . . . . . . . . . . . . . . . . . . . .

Directory synchronization

. . . . . . . . . . . . . . .

Using a centralized directory architecture

. . . . . .

Using LDAP with Domino

Using xSP Hosting

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

127

127

127

128

129

18 Managing Backup and Recovery

About backing up a Domino for iSeries server

Backup tips

. . .

. . . . . . . . . . . . . . . . . . . . .

131

131

132

Libraries and directories for the Domino for iSeries product

. . . . . . . . . . . . . . . . .

133

Backing up Domino programs and product files

Backing up all Domino databases

. . . . . . . .

Backing up mail databases

Backing up specific databases

. . . . . . . . . . . .

. . . . . . . . . .

134

134

136

137

Backing up changed objects from your Domino for iSeries server

. . . . . . . . . . . . . . . .

Recovery of Domino for iSeries

. . . . . . . . . . .

139

141

Recovering an entire Domino for iSeries server

Recovering Domino Directories

Recovering Domino mail

. . . . . . . . .

. . . . . . . . . . . . .

Recovering Domino databases

. . . . . . . . . .

142

142

143

144

Recovering changed objects to a Domino for iSeries server

. . . . . . . . . . . . . . . . . .

About user-defined file systems and availability

Configuring and using BRMS for Domino

. .

. . . . .

Configuring BRMS integration components

. . . .

145

147

148

150

Incremental online backup

. . . . . . . . . . . . . .

Determining the device and media class to use

. . .

Adding media to the media class scratch pool

Excluding databases from your online backup

. . .

. . .

Excluding databases from your system backup

Starting a backup

. .

. . . . . . . . . . . . . . . . . . . .

154

154

155

157

158

159

Recovering all the databases for all your Domino servers

. . . . . . . . . . . . . . . . . . . . . .

160

Recovering all the databases for a specific Domino server

. . . . . . . . . . . . . . . . . . . . . . .

Recovering a single database

. . . . . . . . . . . . .

160

161

Performance considerations and configuration options

. . . . . . . . . . . . . . . . . . . . . .

BRMS restriction

. . . . . . . . . . . . . . . . . . . .

161

162

19 Setting Up Remote LAN

Services

. . . . . . . . . . . . . . . . . . . . . . .

163 iSeries server requirements for remote LAN service

Creating a PPP profile for remote LAN service

163

. .

164

Adding the Connection document for remote LAN service

. . . . . . . . . . . . . . . . . . . . . .

165

Adding a Server document for remote LAN service

Remote LAN service errors

167

. . . . . . . . . . . . . .

167

20 Integrating iSeries Collection

Services With Domino

. . . . . . . . . . .

Starting Domino Collection Services

Stopping Domino Collection Services

. . . . . .

. . . . . .

Domino Collection Services properties

Exporting and viewing the statistics

. . . . .

. . . . . . .

169

170

170

170

170

21 Using National Language

Versions of Domino

. . . . . . . . . . . . .

175

Using other languages on English versions of

Domino

. . . . . . . . . . . . . . . . . . . . . .

Language dictionary files

. . . . . . . . . . . . . . .

175

177

Changing the date and time formats and separators 179

Installing the translated Domino plug-in for iSeries

Navigator

. . . . . . . . . . . . . . . . . . . .

Installing the translated Domino plug-in

. . . .

180

182

v

About running Domino using a secondary language 183

Appendix A Domino for iSeries

Diagrams

. . . . . . . . . . . . . . . . . . . . . .

Domino installation options

Domino configuration options

. . . . . . . . . . . . . .

. . . . . . . . . . . .

185

185

185

Appendix B Installing Domino In

Batch Mode

. . . . . . . . . . . . . . . . . . . .

187

Appendix C Using OS/400

Commands With Domino for iSeries

191

Typical administrative tasks and their equivalent

Domino commands

. . . . . . . . . . . . . . .

198

Index

. . . . . . . . . . . . . . . . . . . . . . . . . .

201

vi

Chapter 1

Getting Started With Domino for iSeries

Welcome to IBM ® Lotus ® Domino TM 6.5 for iSeries TM ! This document will help you set up a Domino environment for your organization, so you can take advantage of its advanced Web serving technology, messaging, groupware, and application development capabilities.

What is Lotus Domino for iSeries?

Lotus Domino is a middleware solution that provides an infrastructure to enhance communications and knowledge sharing throughout your organization. Lotus

Domino and iSeries are an ideal combination for deploying such an infrastructure.

Together, they provide a reliable, scalable, integrated solution providing high availability so your users can access their applications when they need them.

What's new in Domino 6 for iSeries?

This section describes aspects that are new specifically for Domino 6 for iSeries.

For more information on new features not specific to the iSeries server, see the

Release Notes for Domino/Notes 6 (readme.nsf), available on the product CD-ROM or in the Lotus Developer Domain at the following Web address: http://www.ibm.com/lotus/ldd

•

Domino 6 for iSeries uses the licensed product ID 5733LD6 for the 6.0.x releases, and 5733L65 for the 6.5.x releases, and is only available through the IBM Passport Advantage process. For more information on

Passport Advantage, see the following Web site: http://www.ibm.com/lotus/passport

•

For Domino 6, the published Release Notes are not platform independent. Lotus now produces a single set of Release Notes with separate chapters for platform independent information.

•

Beginning with Domino 6.0.3 and 6.5.0, each release is defined as it’s own product option. For more information, see “Domino for iSeries server requirements” in this chapter.

Chapter 1: Getting Started With Domino for iSeries 1

•

Beginning with Domino 6.0.3 and 6.5.0, Domino for iSeries introduces multi-version capabilities and supports multiple releases of Domino on the same

OS/400 partition. For more information, see Chapter 12 “Using Domino for iSeries Multi-version Capabilities .”

•

Domino 6 for iSeries includes a new installation option based on InstallShield

(ISMP 4.0). Using this Java-based, GUI interface you have the option of installing the product from the iSeries server or from a remote workstation.

•

Support for Domino and OS/400 mail integration using Mail Server

Framework/AnyMail integration has been removed. Your server must now be set up to use separate SMTP servers for both Domino and OS/400, and each server must be bound to a unique IP address.

•

Support for Domino running on the original OS/400 HTTP server has been removed. This has been replaced with improved support for the HTTP server powered by Apache. Depending on your current environment, you may need a plug-in to use the HTTP server powered by Apache. For detailed information, see the following Web site: http://www.ibm.com/eserver/iseries/domino/apache.html

•

Support for Directory Synchronization between OS/400 System Distribution

Directory and Domino has been removed.

•

Although the CL commands, menus, panels, and messages are not translated for

Domino 6, the iSeries Navigator plug-in interface is translated into Brazilian

Portuguese, French, Italian, German, Japanese, Korean, Simplified Chinese,

Traditional Chinese, and Spanish. The translated interfaces are installed as part of the Language Pack installation process.

Note Starting with OS/400 V5R2, Operations Navigator, the graphical user interface for managing your iSeries server, was renamed to iSeries Navigator.

This document refers to this product with its new name. If you are working with

V5R1, you will be using Operations Navigator, and minor differences may appear between the documented procedures and what you experience on your screen.

•

Locales are no longer shipped with Domino. Instead, Domino uses the OS/400 locales included with your iSeries server.

•

Fully translated versions of Domino are no longer available for any platforms in

Domino 6. You must now first install the English version and then install language support from a separate Language Pack CD. See Chapter 21 “Using

National Language Versions of Domino ” for more details.

2 Installing and Managing Domino 6.5 for iSeries

How do I administer Domino on iSeries?

Domino 6 includes many improvements to help you administer your Domino server.

You can use either the Domino Administrator client or the Web Administrator client.

Domino Administrator client

The Domino Administrator client can be installed on a remote workstation allowing the administrator access to functions through a Notes interface. The Domino

Administrator client allows an administrator to change server settings, set user settings, set policies, register users, and control client upgrades.

Web Administrator client

The Web Administrator client can be accessed from any workstation through a Web browser. The administrator is authenticated by the user ID and password used to log onto the server. The interface changes depending on the roles assigned to the user

ID. Using the Web Administrator client, administrators can perform most of the same tasks as the Domino Administrator client, such as repairing Access Control

Lists, registering users, and changing server properties.

iSeries Navigator

iSeries Navigator is part of the IBM iSeries Access family of products, and runs on a workstation that is communicating with your iSeries server through TCP/IP. It allows you to perform administrative functions for both Domino and OS/400 using one graphical user interface.

OS/400 CL commands

OS/400 CL commands allow you to initiate system functions using a terminal directly connected with your server, or a workstation communicating with your server using a session such as a 5250 emulator window.

For more information on administering Domino on iSeries, including client setup, starting, using, and troubleshooting, see the Lotus Domino Administrator 6 Help online or the Domino Administrator Help database (HELP65_ADMIN.NSF).


Domino for iSeries server requirements

Domino for iSeries requires the following hardware and software.

Hardware

•

IBM iSeries server based on PowerPC TM (RISC) technology.

Although a Domino server can run on any PowerPC model, the iSeries server models are optimized for client/server applications such as Domino.

•

Minimum 288MB memory, 512MB recommended.

•

Minimum 1.6GB free disk space, 2GB recommended.

Note Use these values as general guidelines for minimum memory and disk space. The requirements for your environment may be different. For more information about sizing an iSeries server for Domino, use the IBM Workload

Estimator for iSeries. The Estimator is available at the following Web site: http://www.ibm.com/eserver/iseries/support/estimator

OS/400 software

•

IBM Operating System/400® (OS/400®), 5722SS1, Version 5 Release 1 or later with the latest PTFs applied.

For more information on the latest PTFs, see http://www.ibm.com/eserver/iseries/domino/support or http://www.ibm.com/eserver/iseries/support

•

OS/400 - Host Servers, 5722SS1 option 12

•

TCP/IP Connectivity Utilities, 5722TC1

•

IBM Developer Kit for Java TM , 5722JV1 plus the 1.3 JDK option for 5722JV1, which is option 5

•

OS/400 - QShell Interpreter, 5722SS1 option 30

Domino software

•

Lotus Domino 6 for iSeries software. For the 6.0.x releases, the product number is 5733LD6. For the 6.5.x releases, the product number is 5733L65.

Beginning with 6.0.3 and 6.5.0, you must install the *BASE option, and the option that defines the release.

For the 6.0.x releases, the following table lists the planned option numbering:

Release

6.0.3

6.0.4

6.0.5

Option

13

14

15


For the 6.5.x releases, the following table lists the planned option numbering:

Release

6.5.0

6.5.1

6.5.2

Option

10

11

12

In addition to the above options, you can install option 1, which contains the C

API related files. If you want to run any application that uses the new C API interfaces, you must install this software.

Note The C API option is not multi-version capable. Only one instance of this option can be installed on an OS/400 partition at a time. For more information, see “Installing multiple releases of Domino” in Chapter 12.

For more information on installing the Domino software, see Chapter 3 “Installing

Domino On Your iSeries Server.”

Optional software

As your environment grows more complex, you may want to add software that is not necessarily required in order to run Domino for iSeries. You have many options for complementing the Domino software to create a productive environment.

If you will be doing any application development with Domino 6, you may want to install the following software:

•

OS/400 - System Openness Includes, 5722SS1 option 13

•

ILE C Compiler, 5722WDS option 51

If you would like to manage your Domino environment using iSeries Navigator, the graphical user interface for managing an iSeries server, you must install the following additional software:

•

IBM Client Access Windows Family Base, 5722XW1 (V5R1) or IBM iSeries

Access Base, 5722XW1 (V5R2)

•

IBM Client Access Express for Windows, 5722XE1 (V5R1) or IBM iSeries

Access for Windows, 5722XE1 (V5R2)

Note Starting with OS/400 V5R2, Operations Navigator was renamed to iSeries

Navigator. This document refers to this product with its new name. If you are working with V5R1, you will be using Operations Navigator, and minor differences may appear between the documented procedures and what you experience on your screen.


Where do I find more information?

Before installing and configuring Lotus Domino for iSeries, be sure to review the

Readme file located on the product CD-ROM or in the Lotus Developer Domain at the following Web address: http://www.ibm.com/lotus/ldd

In addition, review the Domino for iSeries Web site that includes the most up-to-date information on sizing recommendations and installation tips. The Web site is located at the following address: http://www.ibm.com/eserver/iseries/domino

You may also find the following resources helpful:

•

The Lotus Domino home page: http://www.ibm.com/lotus/domino

•

Lotus support for Domino and Notes: http://www.ibm.com/software/lotus/support

•

The latest Domino and Domino for iSeries documentation: http://www.ibm.com/lotus/ldd/doc

•

Lotus products for iSeries: http://www.ibm.com/eserver/iseries/domino/

•

Domino for iSeries partner and education information: http://www.ibm.com/eserver/iseries/developer/domino/

•

IBM “Redbooks” including Domino and iSeries information: http://www.ibm.com/redbooks

•

The iSeries Information Center CD-ROM, which is provided with your iSeries server, has details about installing, setting up, and using TCP/IP. It also provides an overview of using IBM iSeries Access and iSeries Navigator. The latest version of the Information Center is located at the following Web address: http://www.ibm.com/eserver/iseries/infocenter


How do I get fixes?

IBM provides fixes to the Domino product in the form of Maintenance Releases and

Critical Fix Packs. Maintenance Releases typically follow a four month development cycle and are available for download from the Internet. Critical Fix

Packs are released as necessary and are also available for download from the

Internet.

For the latest information on Maintenance Releases and Critical Fix Packs, see the following Web site: http://www.ibm.com/eserver/iseries/domino/support

Lotus Domino for iSeries also requires cumulative Program Temporary

Fix (PTF) packages and individual PTFs for IBM OS/400. Other PTF packages, also known as group PTFs, are available to support specific types of Domino for iSeries operations. Each cumulative PTF package or individual PTF includes installation instructions. For the latest information on PTFs required for OS/400, see the following Web site: http://www.ibm.com/eserver/iseries/support

From the iSeries support page, click Fixes -> Recommended Fixes. Choose your OS/400 release and select Domino from the pull-down list.


Chapter 2

Upgrading the Domino Software

If you already have Domino servers set up on your iSeries server, you can upgrade those servers to a later release of Domino by installing the new Domino for iSeries software. The software for each server is automatically upgraded during the installation process.

Whether you are upgrading from a version prior to Domino 6, or are upgrading to a new Maintenance Release, there are special considerations to keep in mind, as highlighted in the following two sections.

You do not need to go through the server setup procedure again when you upgrade to a new Domino for iSeries release. However, you may want to change the server configuration to take advantage of new features provided by the new Domino release.

For more details, see “Installing the Domino software” in Chapter 3 and “Changing a Domino server’s properties using iSeries Navigator” in Chapter 10.

Considerations for upgrading from previous versions of Domino

You should carefully consider what features you want to use with

Domino 6 before upgrading, as this may have an impact on how you complete the upgrade. The following is a list of things to consider before starting the upgrade process.

•

There are a number of Domino upgrade considerations documented by Lotus that are not specific to the iSeries platform. It is strongly recommended that you read the information on upgrading in the following documents:

•

The Lotus book, Upgrade Guide, which is included in the Lotus Domino

Administrator 6 Help database, and available from the Lotus Developer

Domain at the following Web address: http://www.ibm.com/lotus/ldd/doc

•

Domino administration documentation or the Lotus Domino Administrator 6

Help database (HELP65_ADMIN.NSF).

•

Release Notes for Domino/Notes 6 (README.NSF).

Chapter 2: Upgrading the Domino Software 9

•

Beginning with 6.0.3 and 6.5.0, each release is defined by its own product option. In addition, the seven product options available in R5 have been reduced to two, *BASE and the C API (option 1). These options were changed as outlined in the following table:

R5 feature

Single Logon (in option 1)

Directory Synchronization (in option 1)

C++ API and toolkit (option 4)

LSX toolkit (option 5)

HiTest C API (option 6)

Operations Navigator plug-in

(in option 1)

Advanced services (option 7)

C API (option 3)

Change made

Removed from product





No longer a separate option

No longer a separate option

No longer option 3

Domino 6 solution

Available as download

Not supported on Domino 6



Not supported on Domino 6

Included in each release’s own product option

Included in each release’s own product option and controlled by the license agreement

Moved to option 1

Note All of the downloadable features mentioned in the table can be found at the Lotus Developer Domain at the following Web address: http://www.ibm.com/lotus/ldd

•

The directory synchronization feature has been removed in Domino 6 for iSeries. If you currently use directory synchronization, you must stop all tasks associated with it before attempting an upgrade. For more information, see

“Ending Directory Synchronization tasks” later in this chapter.

•

Support for the OS/400 Mail Server Framework (MSF)/AnyMail integration has been removed for Domino 6 for iSeries. If you currently use OS/400

MSF/AnyMail integration with OS/400 SMTP support and Domino in your environment, prior to upgrading to Domino 6, you must reconfigure your

Domino servers to not use MSF.

Additionally, as Domino 6 for iSeries no longer supports integration with

OfficeVision/400 using the OS/400 MSF, it is no longer possible to route mail between the Domino server and an OS/400 mail application using MSF. It is still possible to route mail between the Domino for iSeries server and a different

OS/400 mail application, but the mail is now routed between the OS/400 SMTP server and the Domino SMTP server. To activate this change, you must reconfigure the Domino server and the OS/400 mail application to use separate

TCP/IP addresses.

Note This only applies to an upgrade from Domino 5.x. If you are upgrading from Domino 4.6x, you must remove the MSF and iSeries SMTP completely.

For more information, see “Moving from Mail Server Framework to Native

Notes” later in this chapter.


•

Not all Lotus Domino dependent products that run on R5 may be supported on

Domino 6. For example, beginning with Domino 6, a matching version of LEI must be used, such as LEI 6.5 with Domino 6.5. Previous versions of LEI (such as 3.0) are not supported on Domino 6.

To see the latest compatibility statements for Lotus products with Domino 6, see the following Web site: http://www.ibm.com/eserver/iseries/domino/domino6/releasesupport.pdf

•

Before upgrading your servers, you must verify that all mail has been delivered. For more information, see “Verifying that all mail is delivered” later in this chapter.

•

Support for Domino running under the OS/400 HTTP server has been modified.

You can no longer run under the original OS/400 HTTP server. You can either setup your Domino server to use the Domino HTTP server, or the OS/400

HTTP server powered by Apache.

•

Before upgrading your servers, make sure you properly back up all server data.

For more information on backing up your server data, see Chapter 18

“Managing Backup and Recovery.”

•

After installing the software, compact the Domino Directory file

(NAMES.NSF). When compacting the file for the first time, you must run the compact operation while the Domino server is down. Compacting the database will convert it to the new format, which offers performance and functional enhancements. After the initial compaction, you can compact the Domino

Directory file while the server is active.

To compact the Domino Directory file, type the following command at any

OS/400 command line, and press Enter:

rundomcmd server(servername) cmd(call pgm(qnotes/compact) parm(NAMES.NSF))

where servername is the name of your Domino server instance.

•

Make sure you also upgrade the Domino Directory template to the new version.

You will be prompted in the server console to upgrade the template when you start each Domino server.

•

Beginning with releases 6.0.3 and 6.5.0, the Domino plug-in for iSeries

Navigator was changed from C++ based to Java based. If you use iSeries

Navigator, you must uninstall the Domino plug-in from any release prior to 6.0.3 and 6.5.0, and install the version of the Domino plug-in supplied with

Domino 6.0.3 or 6.5.0, or you will not be able to work with your upgraded

Domino servers.

•

If the server you are upgrading uses DECS, after upgrading, you must manually replace the design on the DECS administrator prior to running activities. For more information, see the DECS Installation and User Guide (decsdoc6.nsf).


•

Fully translated versions of Domino are no longer available for any platforms in

Domino 6. You must now first install the English version and then install language support from a separate Language Pack CD. If you are currently running a non-English version of Domino and continue to need that language in

Domino 6, you should not upgrade until you have the necessary Domino 6

Language Pack CD.

Considerations for upgrading to future releases

In the future you may want to upgrade your Domino 6 servers to the latest

Maintenance Release (MR) of the software. IBM Lotus typically releases a new MR every four months. The following are items to consider when you upgrade to future releases:

•

Before attempting to upgrade, stop all Domino servers and Domino subsytems on your iSeries server. For more information on stopping Domino servers and subsytems, see Chapter 10 “Managing a Domino Server Using iSeries

Navigator.”

•

Verify that no users are attempting to run any Domino commands or tasks.

•

Verify that all mail is delivered.

•

Properly back up all server data for each Domino server.

For more information on obtaining MRs from IBM, see the following Web site: http://www.ibm.com/eserver/iseries/domino/qmrinfo.htm


What happens when the Domino software is upgraded?

When you upgrade to Domino 6 for iSeries, the following occur:

•

The code copies files into the system first. When installing the *BASE option, some objects are placed into the QNOTES library and the directory

/QIBM/Userdata/Lotus/Notes. When installing a release’s option, the objects are placed into the release-specific library and directory. For example, when installing the 6.0.3 release option, option 13, the objects are placed into the QDOMINO603 library and the /QIBM/ProdData/Lotus/DOMINO603 directory. When installing the 6.5.0 release option, option 10, the objects are placed into the QDOMINO650 library and the

/QIBM/ProdData/Lotus/DOMINO650 directory.

Note If you are installing multiple releases on the same OS/400 partition, a

/QIBM/ProdData/Lotus/Notes symbolic link is created to point to the directory of the primary release. For more information on installing multiple releases on the same OS/400 partition, see Chapter 12 "Using Domino for iSeries

Multi-version Capabilities.”

•

If the release being updated was not multi-version capable, the new Domino 6 software goes through and updates every existing Domino server on your iSeries server, then proceeds to copy files into each server’s data directories.

•

If it seems like the upgrade process has stalled, you may need to go into the

Domino console to answer a prompt on whether to upgrade the Domino

Directory to the new design, as it will wait until this is done. You can access the

Domino console through the OS/400 command WRKDOMSVR.

•

During the software upgrade, Domino 6 will detect whether or not your

Domino servers use the Domino Mail Transfer Agent (MTA) or MSF. If the upgrade program detects an R4.6x SMTPMTA and OS/400 SMTP with MSF server, or that an R5.0x OS/400 SMTP with MSF server is configured, it will halt the installation. When the installation is halted, the user is notified and must either remove the configuration of the R4.6x SMTPMTA and OS/400 SMTP with MSF server, or change or remove the R5.0x OS/400 SMTP with MSF server, whichever is detected.

For more information on making these changes, see the section “Moving from

Mail Server Framework to Native Notes” later in this chapter.

Ending Directory Synchronization tasks

If you are not using Directory Synchronization (R5 only) with Domino, skip this section.

End all Directory Synchronization tasks by following these steps:


1. Using a Notes client, open the Directory Synchronization configuration database.

•

Choose File -> Database -> Open.

•

In the server field, enter the name of the Domino server.

•

Select the Directory Sync Configuration (NNDIRSYC.NSF).

•

Click Open.

2. Click Configurations.

3. Select the configuration document for the configuration that you want to end and click Edit Configuration.

4. Change the status of the configuration to Disabled or Suspended.

5. Click Save and Close.

Note Directory Synchronization may take several minutes to end.

Ending the MSF and SMTP services

If you are not using MSF/AnyMail with Domino, skip this section.

To end the Mail Server Framework, type the following command at any OS/400 command line and press Enter:

ENDMSF

By default, the MSF jobs will end after all MSF messages are processed or within 30 seconds.

To end the iSeries SMTP server, type the following command at any OS/400 command line and press Enter:

ENDTCPSVR *SMTP


Moving from Mail Server Framework to Native Notes

If your current Domino server uses the Mail Server Framework (MSF) with iSeries

SMTP support, you must change the server to use Domino SMTP before upgrading to Domino 6 for iSeries if your Domino server is currently at R5.0x, and it must be removed if your Domino server is at R4.6x.

If you attempt to upgrade without changing your R4.6x SMTPMTA with OS/400

SMTP and MSF supported server, the upgrade process will stop immediately and issue the following escape message:

CPF9897 "R4.6X *MSF SMTPMTA CONFIGURED SERVERS HAVE BEEN

DETECTED ON THIS SYSTEM. CONSULT THE DOMINO 6 FOR ISERIES

INSTALLATION GUIDE FOR DETAILED INFORMATION AND

INSTRUCTIONS FOR UPGRADING YOUR R4.6X *MSF SMTPMTA MAIL

SERVERS."

You must remove the SMTPMTA configuration before proceeding by typing the following command and pressing Enter:

CFGDOMSVR SERVER(servername) MAIL(*NONE)

where servername is the name of your current Domino server.

If you attempt to upgrade without changing your R5.0x OS/400 SMTP and MSF supported server, the upgrade process will stop immediately and issue the following escape message:

CPF9897 "R5.0X *MSF SMTP CONFIGURED SERVERS HAVE BEEN

DETECTED ON THIS SYSTEM. CONSULT THE DOMINO 6 FOR ISERIES

INSTALLATION GUIDE FOR DETAILED INFORMATION AND

INSTRUCTIONS FOR UPGRADING YOUR R5.0X *MSF SMTP MAIL

SERVERS.

You must either remove this server or change it to use Domino SMTP before proceeding with the upgrade.

To change your server to use Domino SMTP using iSeries Navigator, make sure your Domino server is stopped and follow these steps:

1. Open your iSeries server where you will upgrade to Domino 6.

2. Click Network.

3. Click Servers.

4. Click Domino.

5. Right-click the Domino server you need to change, and select Properties.


6. On the Mail tab, select the check box that indicates Simple Message Transfer

Protocol (SMTP) and click OK.

7. Restart your Domino server to make the changes take effect.

Tip You can also use the CHGDOMSVR SMTP(*DOMINO) command to change your Domino server to use Domino SMTP. For more information on the

CHGDOMSVR command, see Appendix C “Using OS/400 Commands With

Domino for iSeries.”


Verifying that all mail is delivered

Prior to upgrading to Domino 6 for iSeries, you should verify that all R5 mail has been delivered. If you find that mail still exists in the IFS directories, then you must find another way to deliver the mail. To verify that all mail has been delivered using iSeries Navigator, follow these steps:

1. Open the inbound and outbound mail directories in the iSeries IFS.

•

Open the iSeries server where you are upgrading Domino.

•

Click File Systems.

•

Click Integrated File System.

•

Click Root.

•

Open the /QIBM/userdata/lotus/smtpmta/inbound directory

Note To verify that there are no outbound messages, open the

/QIBM/userdata/lotus/smtpmta/outbound directory.

2. Verify that no messages are in the directory.

3. If you see files located in either directory, then you must deliver the messages using an alternate method.

Performing the Domino upgrade

Once you have satisfied all upgrade prerequisites, you are ready to upgrade your

Domino servers.

There are several ways you can upgrade your Domino servers. Each way provides a slightly different experience. This section will only document the upgrade steps using iSeries Navigator. For a general idea of the other upgrade path options, see

Chapter 3 “Installing Domino On Your iSeries Server.”

To upgrade to Domino 6 using iSeries Navigator, follow these steps:

1. Open your iSeries server where you will upgrade your Domino servers.


3. Right-click Servers and select Install and Configure Domino.


Follow the directions on each panel of the wizard. For help with a particular setting, click Help.

Tip You can also use the LODRUN command or run the setup.exe program from the root directory of the product CD-ROM. For more details, see Chapter 3

“Installing Domino On Your iSeries Server.”

How do I upgrade the Domino for iSeries Navigator plug-in?

If you previously installed the Lotus Domino plug-in for iSeries Navigator (part of

IBM iSeries Access), upgrade the plug-in components on the client workstation.

Whenever you install a new release of Domino (including maintenance releases), you should always upgrade the Domino plug-in component on the client workstation or you may not be able to use some new Domino plug-in administration features when working with the new Domino server release. Newer Domino plug-in versions are backward compatible with prior versions of Domino.

To upgrade the Domino for iSeries Navigator plug-in, follow these steps:

1. Connect the client to the iSeries where you installed the Domino software.


2. From the client, set up this iSeries as your Administration system.

•

If you are using iSeries Access for Windows, choose:

Start -> IBM iSeries Access -> iSeries Access Properties

Click the Administration System tab and change the Administration system to the iSeries with the old Domino software. Then click Apply.

•

If you are using iSeries Access for Web, choose:

Start -> IBM iSeries Access -> iSeries Access Properties

Click the Administration System tab and set the Source Directory to the share that you used to access the iSeries when you added the Domino plug-in; for example, \\myiseries\QIBM. Then click Apply.

If the share does not exist, you must recreate it. For an example, see steps 1 through 5 in the procedure for adding the Domino plug-in on a workstation using iSeries Access.

For details on adding the Domino plug-in and creating a share on a workstation that is using iSeries Access, see Chapter 5 “Preparing the

Administrator’s Workstation.”

3. Start the Check Version program. This program may start automatically, depending on the settings on the Service tab of the iSeries Access Properties

(see the previous step).

To force the Check Version program to run, choose:

Start -> IBM iSeries Access -> Service -> Check Service Pack Level

4. When the Check Version program runs, read the messages carefully. Depending on the level of iSeries Access on the client and level on the current managing server, you could receive warnings.

•

You can ignore warnings that the iSeries Access level on your managing server is at an earlier level than your client.

•

Follow the instructions about updates for iSeries Navigator plug-ins. Check

Version will copy the plug-in files to your client workstation.

5. Once the updated plug-in is on your client, the plug-in must be applied for each iSeries in your iSeries Navigator tree. To apply the plug-in, open each iSeries in iSeries Navigator. iSeries Navigator detects the change and “scans” the iSeries to automatically apply the change.


Chapter 3

Installing Domino On Your iSeries Server

This chapter will help you install the Domino software on your iSeries server. It also describes the special authorities needed by your user profile, and the necessary steps to verify the installation.

OS/400 authorities required to install and configure Domino

OS/400 has extensive security restrictions to prevent unauthorized access to OS/400 functions and data. The administrator who installs and configures Domino must sign on to the iSeries server with a user profile that has the required authorities.

To install the Domino software, your user profile must have the following special authorities:

•

All object access (*ALLOBJ)

•

Security administration (*SECADM)

To configure a Domino server, your user profile must have the following special authorities:

•

All object access (*ALLOBJ)

•

System configuration (*IOSYSCFG)

•

Job control (*JOBCTL)

•

Security administration (*SECADM)

Checking your user profile using iSeries Navigator

The OS/400 security officer has the required authorities to install and configure

Domino. If you are not the security officer, check to see if your user profile has the required authorities by following these steps:

Open your iSeries server where you will install Domino.

•

Click Users and Groups.

•

Click All Users.

•

Right-click user-id where user-id is the name of your user profile.

•

Click Properties.

•

Click Capabilities.

Chapter 3: Installing Domino On Your iSeries Server 21

The authorities granted to your user profile are displayed on the Privileges tab.

If your user profile does not have the required authorities, ask the security officer to either install and configure Domino or add the required authorities to your user profile.

Checking your user profile using commands

The OS/400 security officer has the required authorities to install and configure

Domino. If you are not the security officer, use the Display User Profile

(DSPUSRPRF) command to determine if your user profile has the required authorities. To check your user profile, follow these steps:

1. At any command prompt, type the following OS/400 command and press Enter:

DSPUSRPRF user-id

where user-id is the name of your user profile.

2. Press the PAGE DOWN key and look for the special authority field to display the special authorities for the user profile.

If your user profile does not have the required authorities, ask the security officer to either do the installation and configuration or to add the required authorities to your user profile.


Verifying the installed iSeries software

You can determine what software is installed on your iSeries by using iSeries

Navigator or by entering CL commands.

Checking for installed software using iSeries Navigator

To verify your software using iSeries Navigator, follow these steps:

Verify the release of the installed software.

•

Open your iSeries where you will install Domino.

•

Click Configuration and Service.

•

Click Software.

•

Click Installed Products.

On the right, you will see a list of the products installed on your iSeries.

To find the release of Domino you are running, look for 5769LNT (R5), 5733LD6

(Domino 6), or 5733L65 (Domino 6.5) in the Product column. Look under the

Release column to see which release of Domino you are running.

Checking for installed software using commands

To determine what software is currently installed on your iSeries server, type the following command and press Enter:

DSPSFWRSC

The Resource ID column shows the program number, such as 5769LNT, 5733LD6, or 5733L65 for Domino. Press F11 to see the version and release of the software.

What should I know before I install Domino?

This section highlights some of the decisions administrators should make before they install Domino on their iSeries server.

Before you install and set up your first Domino server, you must plan server and organizational naming and security. In addition, you must understand your existing network configuration and how Domino will fit into the network. If you are new to the Domino family of products, review the Lotus Domino Administration documentation for more information on planning issues. This documentation is available from the Lotus Developer Domain at the following Web address: http://www.ibm.com/lotus/ldd/doc


Note You can also access this information after installation from the following location on your iSeries server:

/QIBM/ProdData/LOTUS/DOMINO65x/DATA/HELP/help65_admin.nsf

where DOMINO65x corresponds to the directory path for your release of

Domino.

Domino servers and subsystems must be stopped while installing software

If you already have Domino servers configured on your iSeries server, make sure you stop these servers and all Domino subsystems before installing the Domino for iSeries software.

Note If all configured servers are multi-version capable servers, you can install the

Domino software while they are still running.

For more information on stopping Domino servers and subsystems, see Chapter 10

“Managing a Domino Server Using iSeries Navigator.”

Server data directory should not be in QIBM directory

When setting up a Domino server, do not specify the Domino product directory

(/QIBM/ProdData/...) or the Domino user directory (/QIBM/UserData/...) for the location of the server data directory. Putting the server data directory within the product directory could cause problems when operating the server, especially if you run more than one Domino server on your iSeries.

A commonly used location for the server data directory is:

/lotus/domino/data

If you have more than one Domino server on your iSeries, you could specify a location such as:

/lotus/domino/servername/data where servername is the name you specify for each server.

Note In Domino 6 and later versions, use of the Domino product directory

(/QIBM/ProdData/...), the Domino user directory (/QIBM/UserData/...) or the root directory in the Data Directory parameter (DTADIR) on the Configure Domino

Server (CFGDOMSVR) command is checked. If found, a failure of the command with message LNT0102 (Path specified not valid) will occur. This will also cause the GUI server setup wizard to fail if the Domino product directory

(/QIBM/ProdData/...), the Domino user directory (/QIBM/UserData/...) or the root directory is specified. The setup wizard also invokes the CFGDOMSVR command.

Network communications error

If network communications are not set up correctly, you will receive the following error message during installation using Installshield or server setup using the setup wizard:


Make sure you satisfy all the requirements in this message before attempting the installation again. For more information, see Chapter 4 “Planning the Domino for iSeries Environment .”

QNOTES user profile requirements

In order to function correctly, Domino for iSeries requires *RWX (read, write, and execute) access to the root integrated file system directory. For example, when creating new Domino servers, a new directory needs to be created off of the root directory for the associated new Domino data directory. By default, OS/400 sets the public access to the root integrated file system directory to *RWX. However, for security reasons, some administrators may decide to restrict public access. For example, public access may be set to *X (execute). In this case, the QNOTES user profile should be given *RWX access to the root integrated file system directory.

Is my iSeries server properly sized?

Properly sizing your iSeries server is crucial to the success of your Domino environment. IBM provides an on-line tool, the IBM Workload Estimator, to help you assess your environment and provide sizing recommendations. This tool is located at the following Web address: http://www.ibm.com/eserver/iseries/support/estimator


Installing the Domino software

Before installing the Domino software, verify the following:

•

You have an OS/400 user profile with the required authorities to install and configure Domino. For more information about required authorities, see

“OS/400 authorities required to install and configure Domino” earlier in this chapter.

•

You have installed the required hardware and software. For more information, see “Domino for iSeries server requirements” in Chapter 1.

•

Any previous beta or pre-release versions of Domino 6 have been removed.

•

TCP/IP is set up and active on your iSeries server. For more information about setting up TCP/IP, see the iSeries Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

What software should I install?

When you install the Domino server software, you can also install OS/400 integration software and application development software. Decide which of the following product options you want to install.

Note You can install the application development software later if you are not sure you need it.

Lotus Domino for iSeries (*BASE option) defines the product options that can be installed for a specific product ID. This option must be installed before any product option can be installed.

Product Option contains the programs, data, and template files needed to run a specific release of Domino. You must select this option to install and run a Domino server on your iSeries. This option includes all Domino help databases. For example, 5733L65 option 10 is the product option for 6.5.0, and 5733LD6 option 13 is the product option for 6.0.3.

C API (option 1) contains the header files and modules for creating Notes C applications that can run on a Domino server on iSeries.

Note The C API option is not multi-version capable. Only one instance of this option can be installed on an OS/400 partition at a time. For more information, see “Installing multiple releases of Domino” in Chapter 12.

To determine if a more recent version of the C API is available, check the Domino

Developer Tools section of the following Web site: http://www.ibm.com/eserver/iseries/domino/devresources.htm


Language support

With Domino 6 for iSeries, you can run more than one language on a server or can have Domino servers running with differing languages using the Domino Language

Pack and multi-lingual database support. If you plan to run more than one language on a Domino server, you must install the language pack in addition to the Domino software. During the Domino installation process, you have the opportunity to specify whether or not you will be using multiple languages. If so, the language pack installation process will automatically be launched. For more information on using multiple languages, see Chapter 21 “Using National Language Versions of

Domino.”

How do I install the Domino software?

There are several ways you can begin the installation of the Domino software. Each way provides a slightly different experience, but all accomplish the same tasks. You can install the Domino software using any of the following methods:

•

Launch the Domino Server Installation and Setup Wizard through EZ Setup.

This method uses the InstallShield GUI and allows the product CD-ROM to be in either the workstation or iSeries optical drive.

•

Launch the Domino Server Installation and Setup Wizard through iSeries

Navigator. This method uses the InstallShield GUI and allows the product

CD-ROM to be in either the workstation or iSeries optical drive.

•

Use the InstallShield GUI directly by running the setup.exe file from the product CD-ROM. This method allows the product CD-ROM to be in either the workstation or iSeries optical drive.

•

Use the LODRUN command through the OS/400 command interface. This method requires the product CD-ROM to be in the iSeries optical drive.

•

Use the RSTLICPGM command through the OS/400 command interface. This method requires the product to be in the save file form. This is typically used for installing images from the Web or for performing batch installations.

Note For more information on performing batch installations, see Appendix B

“Installing Domino In Batch Mode.”


Using iSeries Navigator to launch the Domino Server Installation

Wizard

To install and configure a Domino server using iSeries Navigator, follow these steps:

1. Open iSeries Navigator.

2. Open your iSeries server where you will install and configure a Domino server.


4. Right-click Servers and select Install and Configure Domino.

Follow the directions on each panel of the wizard. For help with a particular setting, click Help.

Using EZ Setup to launch the Domino Server Installation Wizard

The EZ Setup CD-ROM was shipped with your iSeries server. You can use EZ

Setup to configure basic system values, security settings, and aspects about your network environment. During the EZ Setup process, you can indicate that Domino will be used on your iSeries server. Indicating this will launch the Domino Server

Installation Wizard automatically.


Using InstallShield from the product CD-ROM

You can launch the InstallShield wizard by running the setup.exe file from the

Domino product CD-ROM using a workstation with Windows installed. The setup.exe file is in the root directory of the CD-ROM. For example, the file will be found at the following location:

d:\setup.exe

where d is the letter assigned to your CD-ROM drive.

Once you complete the installation using InstallShield, you are given the option to launch the Domino Server Setup Wizard.

Using the LODRUN command through the OS/400 command interface

To install the Domino software using the LODRUN command, follow these steps:

1. Insert the Domino for iSeries CD-ROM in the iSeries CD-ROM drive.

2. On any OS/400 command line, type the following command and press Enter:

lodrun dev(*opt) dir('/os400')

3. Select each product option that you want to install by typing a 1 beside the product option. Selecting the option that defines the release you want to install will automatically install the *BASE option if it is not already installed. Select

Option 1 if you want to take advantage of the C API functions.

4. Press Enter to install the product options that you selected.

Using the RSTLICPGM command through the OS/400 command interface

The Restore Licensed Program command can be used to install the Domino software if you downloaded it as a save file. To use the RSTLICPGM command, follow these steps:

1. On any OS/400 command line, type the following command and press Enter:

RSTLICPGM


2. On the Restore Licensed Program display, enter the following values into the fields provided:

Field

Product

Device

Description

Specify the Domino licensed product number

Value

5733LD6 for Domino

6.0.x or 5733L65 for

Domino 6.5.x

*SAVF

Optional part to be restored

Specify the device used for restoring the software

Specify the options you want to restore

*BASE, 1, release

option

For the remaining fields, you can accept the default values provided, or enter the values appropriate for your specific environment.

Note If the primary language of your iSeries server is not English 2924, you should change the LNG value from the default (*PRIMARY) to 2924, or you will get an error stating that the LNG objects for the product were not found on the save file.

3. Press Enter to run the restore command.

What happens when the Domino software is installed?

•

OS/400 objects, such as programs (*PGM) and service programs (*SRVPGM), are placed in the release-specific library, such as QDOMINO603 or

QDOMINO650.

•

Miscellaneous objects, such as the following, are placed in the QUSRNOTES library:

•

All the Domino subsystem descriptions

•

All the data queues and job queues for the servers

•

The status of the servers

•

Basic Domino files, such as .nsf and .ntf types, and files that contain symbolic links to the programs, service programs, and other objects in the release-specific library are created in the release-specific directory, such as

/QIBM/PRODDATA/LOTUS/DOMINO603 or

/QIBM/PRODDATA/LOTUS/DOMINO650 in the iSeries integrated file system. These symbolic links provide access to the objects in the release-specific library from the integrated file system.

The iSeries integrated file system provides a directory structure similar to

Windows or UNIX operating systems.

•

The /QIBM/USERDATA/LOTUS/NOTES directory is created in the integrated file system. Users who create programs to be accessed by Domino must add symbolic links to their programs in this directory.


•

The QNOTES user profile is created for use by Domino and Notes application programs that run on iSeries. This user profile is intended for system functions and for integration with the underlying OS/400 security mechanisms.

Therefore, it does not have a password. Individual users cannot use the

QNOTES user profile to sign onto the iSeries server.

Verifying that the Domino software is installed

To verify that the Domino software is installed using iSeries Navigator, follow these steps:

1. Open your iSeries where you installed the Domino software.

2. Click Configuration and Service.

3. Click Software.

4. Click Installed Products.

In the right-hand pane, you will see a list of products installed on your iSeries server. In the Product column, look for 5733LD6 or 5733L65. There should be at least one item with this product code for each option that you installed.

To see the version that is installed on your iSeries, look under the Release column. For example, release 6.0.3 is displayed as V6R0M3, and 6.5.0 is displayed as V6R5M0.

To verify that the Domino software is installed using OS/400 commands, follow these steps:

5. Enter the following OS/400 command to display a list of installed software:

dspsfwrsc

6. Look for items that have a Resource ID of 5733LD6 or 5733L65. There should be at least one item with this Resource ID for each product option that you installed.

To see the Domino for iSeries version that is installed on your iSeries, press the

F11 key. The Release column indicates the version. For example, release 6.0.3

is displayed as V6R0M3 and 6.5.0 is displayed as V6R5M0.


Chapter 4

Planning the Domino for iSeries Environment

Domino 6 for iSeries uses the TCP/IP protocol for the Notes client and server connections. As you set up your TCP/IP and Domino environment, keep the following items in mind:

•

You can configure your Domino server to start automatically after TCP/IP is started on your iSeries server. The default for this setting is No, but you can change this during server setup.

•

Since OS/400 and Domino both provide some of the same Internet protocols, it is possible to get port conflicts if not configured correctly. Services such as

SMTP, POP3, HTTP, and LDAP need to be configured so that they do not conflict. For more information on configuring services to avoid port conflicts, see Chapter 15 “Using Domino as a Mail Server,” Chapter 16 “Using Domino as a Web Server” and Chapter 17 "About Directory Services and Domino."

How should I set up TCP/IP for Domino for iSeries?

This section provides a simple list of steps that must be performed in order to set up

TCP/IP for Domino on your iSeries server. For more information on setting up a

TCP/IP environment, see the documentation for TCP/IP in the iSeries Information

Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

To set up TCP/IP for Domino on your iSeries server, follow these procedures:

1. Create a line description for your TCP/IP interface.

2. Add a TCP/IP interface.

3. Start the TCP/IP support on your iSeries server, then start the new TCP/IP interface.

4. Verify that the TCP/IP connection is active.

Chapter 4: Planning the Domino for iSeries Environment 33

Verifying the iSeries TCP/IP setup and status

The Domino server on iSeries communicates with Notes workstations and other external resources, such as the Internet, through TCP/IP. For the Domino server to work properly, TCP/IP must be set up and active on your iSeries server.

TCP/IP configuration greatly impacts server performance. For more information on tuning your network for optimal performance, see the book TCP/IP Configuration

and Reference (SC40-5420-04). You can access this book online through the iSeries

Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

Determining if TCP/IP is set up

TCP/IP may already be set up on your iSeries server. To verify that it is set up as needed for the Domino server using iSeries Navigator, follow these steps:

1. Open your iSeries server where you installed Domino.


3. Click TCP/IP Configuration.

4. Click Interfaces.

5. On the right, you will see a list of TCP/IP interfaces configured on your iSeries server. Look for an Internet address that does not have a line description of

Loopback.

•

If you do not see an Internet address other than the address associated with

Loopback, you must set up TCP/IP. For more information, see one of the following:

•

The iSeries EZ-Setup CD

•

The book Getting Your AS/400 Working for You (SC41-5161)

•

The iSeries Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

•

If you see an Internet address other than the address associated with Loopback,

TCP/IP is already configured. Continue to the following procedure.

Tip You can also use the CFGTCP command to determine if TCP/IP is set up.

From the Configure TCP/IP display, select option 1.


Determining the Internet address and host name to use for Domino

1. Record an Internet address from the previous procedure that is not associated with Loopback.

Tip If there is more than one Internet address, choose one of the addresses to use for your Domino server. It is recommended that you use a unique Internet address for each Domino server.

2. Find the host name that is associated with the Internet address:

•

If you are using a Domain Name Service (DNS), look in the DNS server for the host name that is associated with the Internet address.

•

If you are using host tables for your TCP/IP network, use the TCP/IP host table entries on your iSeries to find the host name that is associated with the

Internet address. To view the host table entries using iSeries Navigator, right-click TCP/IP Configuration and select Properties. On the TCP/IP

Configuration properties display, select the Host Table tab.

3. Record the TCP/IP host name you will use for the Domino server.

By using an existing host name and Internet address for the Domino server, you can take advantage of the existing TCP/IP configuration and avoid additional configuration.

Tip You can also use the CFGTCP command to determine the Internet address and host name to use for Domino. From the Configure TCP/IP display, select option 10.

Starting TCP/IP

Once TCP/IP is set up for your iSeries, make sure TCP/IP is started. To start TCP/IP using iSeries Navigator, follow these steps:

1. Open your iSeries where you installed Domino.


3. Right-click TCP/IP Configuration and select Start.

4. Periodically press F5 to refresh your screen and wait for the TCP/IP status to be

Started.

Tip You can also use the CFGTCP command to start TCP/IP. From the Configure

TCP/IP display, select option 1, then type a 9 next to the TCP/IP address you want to start and press Enter.

Note If TCP/IP is already started, the system responds with a message that indicates TCP/IP is currently active.

Chapter 4: Planning the Domino for iSeries Environment 35

Verifying TCP/IP interface status

To verify the status of any TCP/IP interface on your iSeries server using iSeries

Navigator, follow these steps:



3. Click TCP/IP Configuration.

4. Click Interfaces.

On the right, you will see a list of all the TCP/IP interfaces configured on your iSeries server. Look under the Status column to determine the status of the TCP/IP interface.

Tip You can also use the CFGTCP command to determine the status of your

TCP/IP interface. From the Configure TCP/IP display, select option 1, then type a 5 next to the TCP/IP interface.

How does Domino interact with other programs on my iSeries server?

Since Domino easily integrates with many other software programs, it is very common to have an environment with many applications working together for complete enterprise solutions. If you currently have an environment with multiple applications integrated with Domino (such as IBM Lotus Sametime

®

or IBM Lotus

QuickPlace TM ) you should check the documentation for those products for their compatibility with Domino 6.


Chapter 5

Preparing the Administrator's Workstation

To manage your Domino server on iSeries, you must set up an administrator’s workstation to communicate with your iSeries server through TCP/IP. Once you have a workstation communicating with your iSeries server, you can choose any of the following methods for managing your Domino environment:

iSeries Navigator

Using iSeries Navigator to administer your Domino environment provides a unique advantage when running Domino on the iSeries platform. This tool allows you to perform administrative functions for both Domino and OS/400 using one interface, integrating many functions for a seamless administration experience.

Domino Administrator client

The Domino Administrator client is a separate installable tool, allowing you to perform administration functions through a Notes interface. Using the Domino

Administrator client, you have access to all administration functions for Domino, but no ability to manage your OS/400 environment.

Caution You must use the Domino Administrator 6 client to manage Domino 6 servers. Do not attempt to use an R5 Administrator client.

Domino Web Administrator

The Web Administrator provides a way to manage your Domino environment through a Web browser. Although this tool does not have all of the administration capabilities of iSeries Navigator and the Domino Administrator client, you can administer your Domino servers from any workstation, without having to install specific software. To access the Web Administrator from any workstation, open a browser and enter the following Web address: http://servername/webadmin.nsf

where servername is the name of your Domino server.

When prompted, type the Administrator’s ID and password and click OK.

Chapter 5: Preparing the Administrator's Workstation 37

Installing iSeries Navigator

The preferred way to manage your Domino environment is through iSeries

Navigator. iSeries Navigator is part of the IBM iSeries Access family of products, and runs on a workstation that is communicating with your iSeries server through

TCP/IP.

To use iSeries Navigator, you must install iSeries Access on a workstation that is running a Microsoft Windows operating system. All of the software needed for running iSeries Access is included in the OS/400 software that is pre-loaded on your iSeries server.

For detailed information on installing iSeries Access and iSeries Navigator on your workstation, see the iSeries Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

Verifying that NetServer is running

NetServer allows you to access OS/400 directories from your workstation. To verify that the NetServer is running, follow these steps:


2. Open the iSeries server where you installed the Domino software.



5. Click TCP/IP.

On the right, you will see a list of servers that should include iSeries NetServer.

If the iSeries NetServer status is Started, then proceed to “Verifying access to the NetServer file share.”

If the iSeries NetServer status is not Started, right-click iSeries NetServer and select Start.

Tip You can also use the STRTCPSVR *NETSVR command to start iSeries

NetServer.

If you do not see iSeries NetServer on the list, see the Client Access Express for

Windows - Setup documentation (SC41-5507) for information on configuring iSeries NetServer.

6. Right-click iSeries NetServer and select Properties.

7. Record the name of the NetServer, as you will need this information in the next section.


Verifying access to the NetServer file share

To verify access to the iSeries NetServer file share, follow these steps:

1. Open the iSeries where you installed the Domino software in iSeries Navigator.

2. Click File Systems.

3. Click Integrated File System.

4. Click Root.

A NetServer file share already exists for QIBM if you see a hand holding the

QIBM folder.

If a share does not exist, right-click the QIBM folder and select

Sharing -> New Share. When the iSeries NetServer File Share dialog box appears, click OK.

5. On your Windows workstation, click the Start button and select

Search -> For Files or Folders.

6. On the Search Results dialog box, click the Tools pull-down menu and select

Map Network Drive.

7. Select the drive letter that you want to use for the NetServer file share.

8. In the Folder field, type the following and press Enter:

\\servername\QIBM where servername is the name of the NetServer.

You will see a message indicating that your workstation is communicating with the file share.

Caution You should not map the Domino server data directory on the iSeries as a network drive from a Notes client workstation. When the Notes client accesses the data directory of the Domino server through a mapped network drive, the

NOTES.INI file of the server may be overwritten with the path of the client data directory. In addition, if a user on the client double-clicks a Domino database that resides on the mapped network drive, then corruption of the NOTES.INI is possible.

One possible consequence of this corruption is that the next time the server is stopped and restarted, the server ends with an error of X’00000108’ in the

QNNINSTS job log. The client can write over the NOTES.INI of the server even if the server is not running.

If your workstation is unable to connect to your iSeries NetServer file share, see the

Client Access Express for Windows - Setup documentation (SC41-5507) for information on configuring iSeries NetServer.

Chapter 5: Preparing the Administrator's Workstation 39

Installing the Domino plug-in

The Domino plug-in for iSeries Navigator is needed if you want to manage your

Domino environment using iSeries Navigator. Installing the plug-in adds folders and objects to the hierarchy tree, choices to menus, and additional property pages to the property sheet for a folder or object in iSeries Navigator.

Once you have installed iSeries Navigator on your workstation, and the Domino software is installed on your iSeries server, you can install the Domino plug-in on your workstation by following these steps:


2. Click the File pull-down menu and select Install Options -> Install Plug-ins.

3. On the Install Plug-ins display, choose the server where you installed the

Domino software and click OK.

4. Follow the prompts in the iSeries Access selective setup wizard to install the

Domino plug-in.

Tip Every time you install a new release of Domino onto your iSeries server, you should update the Domino plug-in to the new version shipped with the new release of Domino.


Chapter 6

Setting Up a First Domino Server

If you are setting up a Domino domain in your organization for the first time, or are creating a new domain, follow the instructions in this chapter for setting up a first

Domino server. If you are adding a new server to an existing Domino domain, see

Chapter 8 “Setting Up an Additional Domino Server.”

You can choose to set up your first Domino server using iSeries Navigator, EZ

Setup, or OS/400 commands. You can also start a setup wizard by opening executable files directly from the product CD-ROM.

Using iSeries Navigator

To set up the first Domino server on your iSeries server using iSeries Navigator, follow these steps:


2. Open your iSeries server where you installed the Domino software.



5. Right-click Domino and select New Domino Server.

The Java-based Setup Wizard will be launched. Complete the fields in the wizard using the information in the next section “Deciding what to specify for server characteristics.”

Tip You can also use the CFGDOMSVR command to set up a Domino server on your iSeries server. For more information on the CFGDOMSVR command, see

Appendix C “Using OS/400 Commands With Domino for iSeries.”

Using the Domino Server Setup Wizard

You can launch the Domino Server Setup Wizard directly from the product

CD-ROM by running the domwzd.exe file. This file is located in the root directory of the CD-ROM and can be run from the workstation. For example, the file can be found at the following location:

d:\domwzd.exe

where d is the letter assigned to your CD-ROM drive.

Chapter 6: Setting Up a First Domino Server 41

Tip You can now use a record/playback feature for using a server setup profile and performing silent setups of Domino servers. For example, to record a setup script, open a DOS prompt on your workstation and enter the following command:

domwzd.exe -record -os400

To play back the setup script, enter the following command:

domwzd.exe -playback -os400

For more information on using a server setup profile, see the Lotus Domino

Administrator 6 Help online or the Domino Administrator Help database

(HELP65_ADMIN.NSF)

Deciding what to specify for server characteristics

When you set up the first Domino server, you must provide information that defines the key characteristics of the server. These characteristics include the name of the server, the location of the server’s data directory, the name of your organization, and details about the person who is the server administrator. Before starting the setup, decide what to use for those key characteristics. Here are some recommendations.

For more information, see the Domino administration documentation or the Lotus

Domino Administrator 6 Help database (HELP65_ADMIN.NSF).

Server name

To avoid additional TCP/IP configuration, use the TCP/IP host name of your iSeries as the server name.

Each Domino server has a unique name that is maintained in its own ID file.

Domino creates the server ID automatically during the server setup processing.

For more information about setting up TCP/IP, see the previous discussion of

“Verifying the iSeries TCP/IP setup and status” in Chapter 4.

Option

This field allows you to select whether this is the first Domino server, an additional

Domino server, or if you are removing a Domino server.

For your first Domino server, specify *FIRST in this field.


Data directory

The data directory contains files used by the Domino server and users of the server.

On a PC-based platform, the data directory typically has the directory path:

x:\notes\data

where x is the drive letter.

On iSeries, the files are stored in the integrated file system, which supports a directory structure similar to DOS or Windows. To make the path easy to remember, specify a similar directory path on your iSeries server. For example:

/domino/servername/data


Note Be sure to use a forward slash (/) to specify a path in the iSeries integrated file system.

Each server must have its own data directory. Therefore, if you set up more than one

Domino server (partitioned servers) on your iSeries, be sure to specify the unique server name in the directory path for the second and subsequent servers.

Note If you use an existing directory as the data directory, make sure that you set up the necessary authorities to the directory. The QNOTES user profile must have

*RWX data authority as well as *OBJEXIST and *OBJMGT object authority to the directory. The owner of the data directory and subdirectories must have

*OBJEXIST and *OBJMGT authority to the directory.

Organization (This option only available for first server setup)

Typically, the organization name is the name of your company or a major division within your company.

Each organization has a Certifier ID that is stored in a file named CERT.ID. During the server setup processing, Domino creates the organization Certifier ID automatically using the organization name you specify and an optional country code. When you register new users or servers, Domino uses the Certifier ID to certify each user or server. You also use the organization Certifier ID when you create organizational unit certifiers for a hierarchical name scheme.


Administrator (This option only available for first server setup)

The administrator can perform operations on the Domino server, such as starting and stopping the server. Although you only need to provide a last name, use a first name and, if needed, a middle name to make sure the administrator’s name is unique. Make sure you keep a record of the name and password that you specify for the administrator. Also provide an Internet password if you plan to manage the server from a Web browser.

Domino creates a user ID for the administrator during the setup processing.

Time zone

The Time zone field determines the time stamp that the server uses for documents and databases.

Daylight savings time

Use this option to select whether or not your server should adjust for Daylight savings time.

Get Domino Directory from (This option only available for additional server setup)

Select which server will be used for replicating the Domino Directory to this server.

Domino Directory type (This option only available for additional server setup)

Select the type of Domino Directory you are using.

Additional server ID (This option only available for additional server setup)

Specify the name and password for the additional Domino server ID.

Web browsers

Use this option to set up the HTTP Web server feature, the Internet Inter-ORB

Protocol (IIOP) feature, or both. Both features enable Web browsers to access the

Domino server. The HTTP server feature only supports transmission of text. The

IIOP feature enables Web browsers and servers to exchange complex objects, including both Notes objects and Object Request Broker (ORB) objects.

For more information about the HTTP Web server, see Chapter 16 “Using Domino as a Web Server.”

Internet mail packages

Use this option to set up one or more mail protocols, such as IMAP, POP3, and

SMTP. Select SMTP if you plan to use Domino mail or want to exchange mail with mail systems that are based on OS/400, such as OfficeVision/400 TM .

Directory services

Use this option to set up Lightweight Directory Access Protocol (LDAP) support on the server.

Connection services

Specify whether or not to include the Domino Enterprise Connection Services

(DECS) in the server configuration.


Advanced Services

If you selected the Domino Enterprise Server type of installation, use this option to include one or more Advanced Services features, such as billing and clustering.

Default ACL settings

Specify what access control list configuration will be applied to all databases and templates on this server.

Text description

If you want, enter a text description of this Domino server.

SMTP services

In Domino 6, this option is obsolete and will only allow the *DOMINO value. Any other value entered in this field will be ignored.

News readers

In Domino 6, this option is obsolete and will only allow the *NONE value. Any other value entered in this field will be ignored.

Replace configuration

This option allows you to choose whether or not the Domino server configuration files in the specified data directory will be overwritten by the new files for this server.

Domain name

Specify the domain name for the Domino server.

Network name

Specify the Notes named network to which this Domino server belongs.

Country or region code

Specify a two-character country or region code to be added to the certifier ID for this Domino server.

Organizational unit (This option only available for first server setup)

Use this field if you want to specify an organizational unit and ID for the server.

You can choose an existing ID file, or have a new one created for you. This file is saved in the data directory specified earlier.


Certifier ID (This option only available for first server setup)

Specify the certifier ID file to be used. You can choose an existing file, or have a new one created for you. This file is saved in the data directory specified earlier and automatically certifies the first server’s ID and the administrator’s user ID.

Administrator ID (This option only available for first server setup)

Specify the user ID for the Domino Administrator.

Server ID (This option only available for first server setup)

Specify the server ID to be used for this server. You can choose an existing file, or have a new one created for you. This file is saved in the data directory specified earlier.

Start server

Use this option to have the system start the server automatically when the setup is completed.

Note If using the CFGDOMSVR command, you also have the option of starting the Java Server Controller (*JSC) or both the server and its JSC (*ALL) when the setup is completed.

Start when TCP/IP started

Specify whether or not this server should be started automatically when TCP/IP is started on your iSeries server.

Note If using the STRTCP, STRTCPSVR SERVER(*AUTOSTART), or

STRTCPSVR SERVER(*DOMINO) commands, you also have the option of starting the Java Server Controller (*JSC) or both the server and its JSC (*ALL) when the setup is completed.

Log replication events

Specify whether or not you want the replication events logged in the LOG.NSF file for this Domino server.

Log client session events

Specify whether or not you want the client session events logged in the LOG.NSF

file for this Domino server.

TCP/IP port options

Use this TCP/IP port option to specify an Internet (IP) address for the server’s port.

For example, if you are setting up the server as a partitioned server, you can use this option to specify a separate IP address for the server.

For more information, see Chapter 7 “Setting Up Multiple Domino Servers On the

Same iSeries Server.”

Server host name

Specify the host name used by this Domino server.


Subsystem and object names

Use this option if you want to use a specific name for the OS/400 subsystem and associated objects that are used by the server. Each Domino server runs in a separate

OS/400 subsystem. Unless you specify a different name, the system generates a name of “DOMINO” followed by a two-character sequence number, such as

DOMINO01.

Collation

Use this option to specify a collation code that defines how characters are sorted.

Different national languages may sort characters differently.

Copy administrator’s ID file

Use this option to specify where the setup program should put the ID file for the server administrator. Unless you specify differently, the setup program attaches the ID file to the Person document for the administrator in the server’s Domino Directory and also copies the ID file to the server’s data directory.

Additional services

Use this option to set up additional services for the server beyond the default services. Services selected will appear in the NOTES.INI file on the “ServerTasks=” line. If you accept the default value, which is no additional services (*NONE), the

ServerTasks line will include the following:

COLSRV400, Update, Replica, Router, Stats, AMgr, AdminP, Sched,

CalConn

You can also remove the default services by removing values from the list in the wizard or by specifying the value *MINIMUM using OS/400 commands. In this case, the ServerTasks line will only include the minimum necessary services for

Domino. These services are COLSRV400 and Update.

If you select any specific services, this overrides the default, and these services will appear in the ServerTasks line with COLSRV400 and Update. For example, if you specifically select Agent Manager (*AMGR) and Router (*ROUTER), the

ServerTasks line will only include the following:

COLSRV400, Update, AMgr, Router

Note When adding services using OS/400 commands, there are some considerations to follow. When specifying *NONE, *MINIMUM or *ALL, no other values can be specified. In addition, you can not enter the same value more than once, such as *ADMINP *ADMINP.

Allow Domino Off-Line Services

Specify whether or not you want to allow this server to support DOLS.

Service provider configuration

Specify whether or not you want the service provider configuration to be enabled.

The service provider configuration provides services (mail and applications) to multiple hosted companies or organizations within a single Domino domain.


What happens during first server setup?

The first server setup does the following:

•

Creates a new domain for the Domino servers.

•

Creates the certification log file, names it CERTLOG.NSF, and saves it in the

Domino data directory.

•

Enables the appropriate network and serial ports.

•

Creates the Domino Directory for the domain. The setup program creates the

Domino Directory in the data directory that you specify for the Domino server and gives it the default name NAMES.NSF.

Note The Domino Directory is also known as the Public Address Book and the Name and Address Book (NAB).

•

Creates a Certifier ID for your organization. The setup program saves the

Certifier ID in the same directory you chose for Domino data files and gives it the default name CERT.ID.

•

Creates a Certifier document in the Domino Directory. This document describes the Certifier ID.

•

Creates a server ID for the new server. The setup program saves the server ID in the same directory you choose for Domino data files and gives it the default name SERVER.ID. The setup program creates the server ID with no password.

If needed later, you can require a password for the server ID.

•

Certifies the server ID with the organization Certifier ID.

•

Creates a Server document in the Domino Directory. This document describes the first server based on information that you specify during setup.

•

Creates a Person document in the Domino Directory for the Domino administrator specified during setup.

•

Creates a user ID and a password for the Domino administrator and does one or both of the following, depending on what you specified:

•

Attaches the user ID as a file named USER.ID to the administrator’s Person document in the Domino Directory.

•

Copies the user ID file to the data directory.

•

Certifies the administrator’s user ID with the organization Certifier ID.

•

Adds the administrator’s name and the server’s name as managers in the access control list of the Domino Directory.

•

Adds the server name to the LocalDomainServers group in the Domino

Directory.

•

Creates the log file for the server in the same directory you specify for Domino data files and gives it the default name LOG.NSF.


•

Creates a mail directory in the Domino data directory and a mail file in that directory for the Domino administrator.

•

Sets up the additional options that you specified.

•

Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino data directory.

•

Updates network settings in the Server document of the Domino Directory.

•

Configures SMTP during the setup program.

•

If “DOLS Domino Off-Line Services” was selected during the setup program, creates the Offline Services file, names it DOLADMIN.NSF, and saves it in the


•

Updates the Access Control List in all databases and templates in the Domino data directory tree to remove Anonymous access and/or add

LocalDomainAdmin access, depending on the selections made during the setup program.

•

Configures xSP Service Provider information, if selected during the setup program.


Chapter 7

Setting Up Multiple Domino Servers On the Same iSeries Server

This chapter discusses setting up multiple Domino servers on the same iSeries server.

What is Domino partitioning?

Domino server partitioning lets you run multiple Domino servers on a single iSeries server. Using partitioned servers reduces hardware expenses and minimizes the number of computers that you have to administer. Each partitioned server has its own Domino data directory and NOTES.INI file, but all partitioned servers share the same Domino program files. Partitioned servers can help you make more efficient use of your iSeries server.

For example, instead of purchasing multiple small computers to run Domino servers that might not take advantage of the resources available to them, you can purchase a single, more powerful iSeries server and run multiple Domino servers on that single server, allowing you to easily allocate resources among the Domino servers running on that iSeries server.

Setting up partitioned servers is particularly effective when the servers are in different domains. For example, on one computer you can dedicate multiple domains to multiple customers or set up multiple Web sites.

In an enterprise network, partitioned servers can provide the scalability you need while also providing security. As your system grows, you can migrate users from individual servers to partitioned servers. A partitioned server can also be a member of a cluster if you require high availability of databases. Security for a partitioned server is the same as for a server on its own iSeries.

If one partitioned server shuts down, the others continue to run. Therefore, the applications you run on the other partitioned servers are more reliable. If a partitioned server encounters a fatal error, you can restart that partitioned server without restarting your iSeries server or other Domino servers.

In order to set up multiple Domino servers on the same iSeries server, you must:

•

Prepare the TCP/IP network for partitioned Domino servers

•

Configure the Domino server in one of two ways:

Chapter 7: Setting Up Multiple Domino Servers On the Same iSeries Server 51

•

As a first Domino server

•

As an additional server in an existing Domino domain

Preparing the TCP/IP network for partitioned Domino servers

Before you configure a partitioned server, you must complete the following steps:

1. Obtain a unique TCP/IP address and host name for the server to use.

2. Update either the Domain Name Service (DNS) or the host table of each server and client with the TCP/IP address and host name of the server.

To set up TCP/IP addresses and host names using iSeries Navigator, follow these steps:

•

Open the iSeries server where you will configure the partitioned Domino server.

•

Click Network.

•

Click TCP/IP Configuration.

•

Click IPV4 or IPV6 (if you use OS/400 V5R2).

Note IPV6 is not currently supported with Domino for iSeries.

•

Right-click Interfaces, select New Interface, and select a type of interface.

A TCP/IP interface wizard takes you through the steps needed to set up a

TCP/IP interface for the iSeries server.

3. When you set up the partitioned server, specify the unique TCP/IP address in the Internet address field of the TCP/IP port options.

If the server is already set up, reconfigure the server using iSeries Navigator or the CHGDOMSVR command and add the TCP/IP address in the Internet address field of the TCP/IP port options.

Tip You can also use the CFGTCP command to add a new TCP/IP interface. From the Configure TCP/IP display, select option 1 and enter a 1 next to the blank

Internet address field.

For more information about setting up partitioned servers, see the

Domino 6 administration documentation or the Lotus Domino Administrator 6 Help database (HELP65_ADMIN.NSF). Return to this documentation when you are ready to configure the partitioned Domino server.

Configuring a partitioned Domino server

You may configure a partitioned server as either a first Domino server or as an additional Domino server. However, when you configure each Domino server, make sure you do the following:

•

Specify a unique TCP/IP address for each Domino server running on the same iSeries server


•

Enable the Partitioning option on each Domino server running on the same iSeries server

•

Configure each Domino server to use one TCP/IP address by enabling the Bind to Host name option, if you plan on running multiple HTTP servers on your iSeries server

For more information on configuring your partitioned server as a first Domino server, see Chapter 6 “Setting Up a First Domino Server.”

For more information on configuring your partitioned server as an additional

Domino server, see Chapter 8 “Setting Up an Additional Domino Server.”

Chapter 7: Setting Up Multiple Domino Servers On the Same iSeries Server 53

Chapter 8

Setting Up an Additional Domino Server

Use this procedure if you want to add another Domino server to an existing Domino domain. When you add a Domino server to a Domino domain, the additional server uses the same Domino Directory as other servers in the Domain. For example, set up the Domino server as an additional server if:

•

You already have a Domino server on another system and you want the new

Domino server on your iSeries server to use the same Domino Directory.

•

You already have a Domino server on an Integrated xSeries Server for iSeries and you want the new Domino server to use the same Domino Directory.

•

You already have a Domino server set up on your iSeries server and you want to add a second server that uses the same Domino Directory.

Setting up an additional Domino server involves these tasks:

1. Prepare the OS/400 environment for the Domino server. If you previously set up your first Domino server on the same iSeries server, you already set up the

OS/400 environment.

For more information, see Chapter 4 “Planning the Domino for iSeries

Environment.”

2. Use an existing server in the Domino domain to register the additional server.

For more information on registering a server, see the next section, “Registering the additional server.”

3. Verify the TCP/IP connection from the registration server and its administrator workstation to the iSeries server.

4. Copy the server ID file for the additional server to your iSeries server, if you saved the server ID in a file when you registered the server.

5. Set up the additional server on your iSeries.

Chapter 8: Setting Up an Additional Domino Server 55

Registering the additional server

Before adding a Domino server to an existing Domino domain, you must register the additional server in the domain. When you register the server, specify the iSeries

TCP/IP host name as the server name, unless you already have a Domino server that uses the same iSeries TCP/IP host name.

For instructions on determining the iSeries TCP/IP host name, see “Verifying the iSeries TCP/IP setup and status” in Chapter 4.

1. Select an existing server in the Domino domain and use that server (the registration server) to register the additional server. For information about registering the additional server, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database (HELP65_ADMIN.NSF).

The server registration process creates a Server document in the Domino

Directory of the registration server and creates a server ID. Unless you specify differently, the server ID is encrypted and attached to the Server document in the Domino Directory. You have the option of storing the server ID in a file.

•

If you store the server ID in the Domino Directory, you must provide a password. Keep a record of the password in a secure place. When you set up the additional server, you must provide the password. Domino copies the

Domino Directory, including the server ID, to the new server during the setup processing.

You must also specify the password every time you start the additional server. Therefore, after you issue the start request, you must start the

Domino server console (using the OS/400 WRKDOMCSL command) and enter the password.

•

If you store the server ID in a file, you do not need to provide a password.

However, you must manually copy the file to the iSeries where you plan to set up the additional server. You must copy the server ID file before you set up the server.

Tip If you plan to manage the new server remotely, do not specify a password and specify 0 as the minimum password length for the server. Otherwise, you must open the Domino server console for the server and enter the password each time you start the server.

2. Record the names that identify the registration server and the additional server that you registered.

•

For the registration server, record the simple name; for example, Server1.

•

For the additional server, record the full hierarchical name; for example,

Server2/Chicago/Acme.

3. Record the TCP/IP host name of the registration server. This host name is usually the same as the server name.


4. Record the location of the server ID file, if you chose to store the server ID in a file.

Verifying the TCP/IP connections to the iSeries server

When you set up the additional Domino server on your iSeries server, Domino copies the Domino Directory from the registration server to the new server.

Therefore, your iSeries server must have an active TCP/IP connection to the registration server. Similarly, the administrator workstation for the domain must be able to communicate with the iSeries.

Verifying the TCP/IP connection between the registration server and your iSeries server

1. Make sure the registration server is started.

2. From any OS/400 command line, enter this command:

ping registration-server-host-name

where registration-server-host-name is the TCP/IP host name of the registration server. You recorded this host name as part of the procedure to register the additional server. The host name of the registration server may be different from the TCP/IP host name of the system on which the registration server is running.

•

If the registration server responds to the PING, the TCP/IP connection between the registration server and your iSeries server is operational.

•

If the PING is not successful, verify the TCP/IP configuration on your iSeries server and the system containing the registration server. Also verify that your iSeries and the other system are properly connected to the network and that the network is operational.

Note If you are using a firewall, the PING technique does not work.

However, you may still be able to complete the server setup.

Caution If the registration server for the domain is running on an Integrated xSeries Server for iSeries on the same iSeries as the additional server, you may need to do additional configuration.


Verifying the TCP/IP connection between the workstation and your iSeries server

To manage the additional server from your current administrator workstation, you must be able to communicate with your iSeries server through TCP/IP. If you are using a network protocol other than TCP/IP to administer your current servers, you must set up TCP/IP on the workstation.

1. Install and set up TCP/IP on the workstation. For instructions, see the documentation for the TCP/IP product.

Tip If you are using Microsoft Windows 95, Windows 98, or

Windows NT, you may want to refer to the iSeries book Client Access for

Windows 95/NT - Setup (SC41-3512). This book contains a helpful chapter on configuring Microsoft TCP/IP for Windows. You can access this book from the iSeries Online Library at the following Web site: http://www.ibm.com/eserver/iseries/library

2. Verify the TCP/IP connection to your iSeries server.

•

From the administrator’s workstation, type the following OS/400 command at any command prompt:

ping hostname

where hostname is the TCP/IP host name of your iSeries server.

•

If the PING is successful, the workstation is communicating with your iSeries server. If the PING is not successful, review the steps you followed to set up TCP/IP on the workstation and iSeries.

Copying the ID files for the additional server to the iSeries server

If you stored the server ID in a file, you must copy the file to the iSeries server where you plan to set up the additional server.

Note Skip this procedure if you stored the server ID in the Domino Directory.

1. Make sure you are working from the system (server or workstation) that contains the server ID file.

2. Change to the directory that contains the server ID file. You recorded the directory path as part of the procedure to register the additional server.


3. Copy the server ID file to the iSeries server where you plan to set up the additional server. Use any method that you typically use to copy files between systems. For example, you can use:

•

The TCP/IP File Transfer Protocol (FTP).

•

The Windows Network Neighborhood in combination with either iSeries

Access or iSeries NetServer support to map a network drive between systems. Then you can copy the file by using any method that copies files from one directory to another on the same system.

• iSeries Navigator. Click File Systems -> Integrated File Systems -> Root and select the server’s data directory, such as /domino/servername/data. Then copy the ID files to a local directory on the workstation.

To use any of these methods, you must have TCP/IP communications set up and active between the workstation and the iSeries.

4. Change the OS/400 authorities to secure the server ID file but still allow the

Domino server to access the file. To change the OS/400 authorities using iSeries Navigator, follow these steps:

•

Click File Systems.

•

Click Integrated File Systems.

•

Click Root.

•

Right-click the server ID file and select Permissions.

•

Click the Owner button, select Qnotes from the list in the “Select new owner” field, and click OK.

Note Qnotes is found under the “All Users” group.

•

Make sure the Exclude check box is selected for (Public).

•

Make sure every check box except Exclude is selected for Qnotes.


Tip You can also use the CHGOWN command to change the owner of the Server

ID file. For example, type the following at any OS/400 command line and press

Enter:

CHGOWN OBJ('/domino/servername/data/server.id')

NEWOWN(QNOTES)


Setting up an additional server using iSeries Navigator

Use the Java-based Setup Wizard to configure an additional server on your iSeries server. To start the setup process, follow these steps:


2. Open your iSeries server where you will add the additional Domino server.




5. Right-click Domino and select New Domino Server.

The Java-based Setup Wizard will be launched. Complete the fields in the wizard using the information in the section “Deciding what to specify for server characteristics” in Chapter 6.

Tip You can also use the CFGDOMSVR command to set up a Domino server on your iSeries server. For more information on the CFGDOMSVR command, see Appendix C “Using OS/400 Commands With Domino for iSeries.”

6. When prompted, enter your OS/400 user ID and password.

Tip The setup wizard will enter predefined defaults that typical servers use.

You can change advanced server settings to customize the server to fit your specific environment.

7. Follow the setup panels, selecting the options or providing the information that matches your desired server characteristics.

You must provide the following information:

Choose Additional Server when asked for the type of Domino server to be configured.

Server ID: Choose whether the server ID is in a file on the iSeries server or in the Domino Directory.

If you specified a password when you registered the additional server, provide the password.

Server name: Specify the full hierarchical name of the Domino server. For example:

Server2/Chicago/Acme

Data directory: Specify the directory path for the server’s data directory in the integrated file system. For example, specify:

/domino/Server2/data

Internet services: Specify any desired Internet services that this Domino server will provide.

Advanced settings: Specify any advanced server settings you want to apply to this server.

Network settings: Specify any network settings for this Domino server. For example, click the Customize button and specify a fully qualified Internet host name for this Domino server.

Local time zone: Select the time zone to be used for the server’s time stamp.


Get Domino databases: You can choose to provide system databases from another Domino server, or from another local media source. Either option requires that you enter a server name in the “Other Domino server name” field.

Another new feature is the ability to connect to the other Domino server through a proxy connection. To do this, specify a proxy server address, port, and type.

Note If a proxy server address is specified, you must select a port and type.

Domino Directory: Specify the type of Domino Directory this server will use.

8. When the setup is complete, use iSeries Navigator to determine the status of the server by following these steps:

•

Click Network.

•

Click Servers.

•

Click Domino.

On the right, you will see a list of Domino servers on your iSeries server.

Look under the Status column to see the status of the Domino server you just configured.

9. If the server is stopped, start it by right-clicking and selecting Start.

Note The server document may have been created with the default host name of your iSeries server and needs to be changed after you start the Domino server. You may have problems accessing your Domino server via IIOP if you do not update this value. To do this, open the server document using the Domino Administrator client and change the IP address and fully qualified host name to match your newly configured Domino server, then stop and restart your server to make the changes take effect.

For details on using iSeries Navigator to perform operations on a Domino server, see Chapter 10 “Managing a Domino Server Using iSeries Navigator.”


What happens during additional server configuration?

Configuring an additional server does the following:

•

Copies the Domino Directory, if a file location was specified during the setup program, names it NAMES.NSF, and saves it in the Domino data directory.

•

Copies the server’s ID from the location specified during the setup program, either from a file, a copy of the directory, or the existing Domino server’s directory, names it SERVER.ID, and saves it in the Domino data directory.

•

Retrieves the Domain name and Administrator name from the Server document in the Domino Directory.

•

Creates the log file, names it LOG.NSF, and saves it in the Domino data directory.

•

Copies or replicates the Administration Requests file, names it ADMIN4.NSF, and saves it in the Domino data directory.

•

Copies or replicates the Monitoring Configuration file, names it

EVENTS4.NSF, and saves it in the Domino data directory.

•

Replicates the Domino Directory, if it doesn’t already exist, names it

NAMES.NSF, and saves it in the Domino data directory.

•

Creates a Connection document to the existing Domino server in the Domino

Directory.

•

Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino data directory.

•

Updates network settings in the Server document of the Domino Directory.

•

Configures SMTP during the setup program.

•

If “DOLS Domino Off-Line Services” was selected during the setup program, creates the Offline Services file, names it DOLADMIN.NSF, and saves it in the


•

Updates the Access Control List in all databases and templates in the Domino data directory tree to remove Anonymous access and/or add

LocalDomainAdmin access, depending on the selections made during the setup program.

•

Configures xSP Service Provider information, if selected during the setup program.

•

Replicates changes made to the Server document with the existing server, if any.

•

Removes the SERVER.ID attachment from the Domino Directory, if applicable.


Chapter 9

Managing the Domino Server Overview

Domino for iSeries provides administrative functions for managing a Domino server on iSeries. For example, you could start or stop a server using one of two interfaces:

• iSeries Navigator

You may prefer to use iSeries Navigator if you are more familiar with a graphical user interface such as Windows.

For more information, see Chapter 10, “Managing the Domino Server Using iSeries Navigator.”

•

Individual commands that you enter using the OS/400 command interface

You may prefer to use commands if you are familiar with the OS/400 command interface. OS/400 commands provide some capabilities that are not currently available in iSeries Navigator.

For more information, see Appendix C, “Using OS/400 Commands With


Ways of managing a Domino server on an iSeries server

Typically, you manage a Domino server from a Notes client. The Notes client interface provides the full set of Domino administration functions. The Notes client is used on a remote workstation since a Domino server on iSeries does not have a local Notes client. Domino for iSeries also supports the Domino Web

Administration tool. This tool allows you to perform a subset of the Domino administration tasks from a Web browser. For more information, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database

(HELP65_ADMIN.NSF).

To help you manage a Domino server, Domino for iSeries allows you to use the following alternative methods to perform common administration tasks:

• iSeries Navigator: This graphical interface is part of the workstation support provided by IBM iSeries Access.

•

OS/400 commands: These commands allow you to interact directly with the iSeries operating system (OS/400) through its native command interface.

Chapter 9: Managing the Domino Server Overview 65

•

Java Server Console: This Java-based application allows you to manage your

Domino servers from a workstation, even when your Domino servers are not currently running.

You must use iSeries Navigator, OS/400 commands, or the Java Server Console to do a few Domino server tasks, such as starting or stopping the server.

If you are familiar with a graphical user interface, such as Windows, you may prefer to use iSeries Navigator. For some tasks, using iSeries Navigator is easier than using commands or the Notes administrator functions. For example, iSeries Navigator allows you to add both a Notes user and an OS/400 user at the same time. However, iSeries Navigator does require iSeries Access and additional setup on the workstation.

If you are familiar with OS/400, the commands provide a direct and convenient way of managing both iSeries and a Domino server running on iSeries. You can run the commands from any display or workstation that is communicating with the OS/400 operating system. No additional setup is required.

Note The primary OS/400 command used to manage a Domino server is

WRKDOMSVR. For more information on the WRKDOMSVR command, see

Appendix C “Using OS/400 Commands With Domino for iSeries.”

Whether you use iSeries Navigator, OS/400 commands, or the Java Server Console to manage a Domino server, you must have an OS/400 user profile that has the necessary authority to perform each administrative operation.

iSeries server authority requirements for Domino administrators

The person who manages Domino servers on iSeries must sign on to your iSeries server using a user profile that has the OS/400 authorities required to perform each administrative task. To give a user special authorities, change the special authority field in the user’s profile. The OS/400 security officer can use either iSeries

Navigator or the Change User Profile (CHGUSRPRF) command to change a user’s profile.

•

Starting and stopping (ending) a Domino server.

The administrator can start and end a server by using either iSeries Navigator or

OS/400 commands (STRDOMSVR, ENDDOMSVR, or WRKDOMSVR).

Both interfaces require *JOBCTL special authority to start or end a server.


•

Working with the Domino console.

The administrator can access the Domino console through an OS/400 command

(WRKDOMCSL). The administrator can issue server commands from this console. To work with the Domino console, the administrator needs either

*ALLOBJ special authority or the following specific authorities:

•

*USE authority to the QNNINCSS program in the QNOTES library.

•

*USE authority to the WRKDOMCSL command in the QSYS library.

•

*X data authority to the Domino server’s data directory (and its parent directories if the directory is not directly under the root directory).

The OS/400 security officer can grant these specific authorities by typing the following OS/400 commands:

GRTOBJAUT OBJ(qnotes/qnnincss) OBJTYPE(*pgm)

USER(admin-profile-name) AUT(*use) REPLACE(*yes)

GRTOBJAUT OBJ(qsys/wrkdomcsl) OBJTYPE(*cmd)

USER(admin-profile-name) AUT(*use) REPLACE(*yes)

CHGAUT OBJ('server_data_directory')

USER(admin-profile-name) DTAAUT(*X)

where server_data_directory is the Domino server’s data directory.

Note The CHGAUT command must be used on each parent directory above the Domino server’s data directory.

To display the Domino console, the administrator needs either *ALLOBJ special authority or *X data authority to the Domino server’s data directory

(and its parent directories if the directory is not directly under the root directory).

•

Changing a Domino server.

After a Domino server is set up, the administrator can use an OS/400 command

(CHGDOMSVR) to change the configuration of the server. Changing the server requires *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM special authorities.

•

Removing a Domino server.

Removing a Domino server removes the data directory used by the server. The data directory may also contain user data. The administrator can use an OS/400 command (CFGDOMSVR) to remove a Domino server. The administrator must have *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM special authorities.


Overview of using iSeries Navigator to manage a Domino server

iSeries Navigator enables you to use your Notes administrator workstation to manage both your iSeries server and the Domino servers on your iSeries. Through the Domino for iSeries support in iSeries Navigator, you can:

•

Determine the status of all Domino servers on your iSeries server.

•

Perform administrative tasks on the servers, such as starting, stopping, and deleting servers.

•

View and change server properties, including the NOTES.INI files.

iSeries Navigator works through the iSeries Access support. Therefore, you must install iSeries Access on your iSeries server and the administrator workstation. You must also install the Domino plug-in for iSeries Navigator on the administrator workstation.

For more information, see Chapter 5 “Preparing the Administrator’s Workstation.”

Overview of using the Java Server Console to manage a Domino server

The Java Server Console allows you to manage your Domino servers through any workstation that supports Java applications. To use the Java Server Console, you must first start the Java Server Controller (JSC) on your iSeries server. You can start the JSC when starting a Domino server from iSeries Navigator or the

STRDOMSVR command.

Note The JSC can also be started when running the STRTCP, STRTCPSVR

SERVER(*AUTOSTART), or STRTCPSVR SERVER(*DOMINO) commands if

*JSC or *ALL was selected in the AUTOSTART parameter during server configuration.

The Java Server Controller is a stand-alone Java program that listens for requests from the remote Java Server Console. It also listens for “heart beat” information from the Domino server.

Note When starting a Domino server and the Java Server Controller, you will now see a QJVAEXEC job instead of a SERVER job in the OS/400 job log.

For more information on using the Java Server Console, see the IBM Redbook

Domino 6 for iSeries Implementation available from the following Web address: http://www.ibm.com/redbooks


Overview of using the Domino Administrator client to manage a Domino server

The Domino Administrator is the administration client for Notes and Domino. You can use the Domino Administrator to perform a variety of administration tasks.

For example, you can:

•

Start and stop server tasks

•

View, search, and analyze the server’s log file

•

Monitor server status and availability

•

Access real-time performance charts

•

Manage detailed server settings

Using the Verity KeyView filter

Domino for iSeries uses the Verity KeyView filter for retrieving text from binary attachments. Supported formats include Adobe Acrobat PDF, Microsoft Word,

Corel® WordPerfect®, Lotus 1-2-3®, Microsoft Excel, Lotus Freelance Graphics®,

Microsoft PowerPoint®, HTML, and many others.

Note Lotus Word Pro® attachments cannot be indexed.

To enable this feature, a database must be full-text indexed with the option to index binary attachments. Indexing attachments as raw text will continue to operate as before, and does not use the KeyView filter. The KeyView filter can be enabled or disabled for the entire server by specifying one of the following settings in the

NOTES.INI file:

•

FT_BINARY_FILTER_OFF=1 indicates the KeyView filter will not be used.

•

FT_BINARY_FILTER_OFF=0, or no setting at all, indicates the KeyView filter will be used. This is the default setting.

This NOTES.INI setting allows administrators to shut off the filter without having to change the indexing options on all databases that have the binary attachment option turned on.

Note Domino for iSeries does not support full text indexing of EBCDIC file systems.


Fault recovery operation

The fault recovery system in Domino 6 is configured the same as on UNIX platforms, with the exception that the fault recovery system is enabled by default on iSeries. There have been changes from the way this was configured in Domino 5. In particular, note that the fault recovery settings are now controlled from the server’s configuration document, accessible via the Configuration tab from the Domino

Administrator. Also note that the AS400_DOMSVR_RESTART environment variable is no longer supported and has been replaced by the “Maximum Fault

Limits” settings in the server’s configuration document.

See the “Fault Recovery” section in the Lotus Domino Administrator 6 Help database for more information.

When upgrading from a previous version of Domino to Domino 6, the current server settings for fault recovery are retained and the server’s configuration document is updated accordingly.

Specifying a diagnostic program for fault recovery

There is no longer a “Cleanup Script Name” field in the server configuration document in which you must place “CALL QNOTES/NSD”. This has been replaced by the “Run This Script After Server Fault/Crash” field in which you may configure a call to your own recovery diagnostic program, such as “CALL

MYLIB/MYDIAG”. If you do not have one, this field should be blank. Any user diagnostic will be run before the Domino NSD program.

The Domino NSD program can be turned on and off by the “Run NSD To Collect

Diagnostic Information” field. This should normally be enabled so that crtitical diagnostic information will be generated. This information is useful to the Lotus and

IBM support team for solving server problems.


Chapter 10

Managing a Domino Server Using iSeries Navigator

To enable iSeries Navigator for Domino, you must add the Domino plug-in for iSeries Navigator. For more details see “Installing the Domino plug-in” in

Chapter 5.

This chapter provides you with the steps to complete the following tasks using iSeries Navigator:

•

Starting a Domino server

•

Stopping a Domino server

•

Stopping a Domino subsystem

•

Starting the Java Server Controller

•

Determining server status

•

Changing a Domino server’s properties

•

Editing the NOTES.INI file

•

Launching the Domino Administrator client

Tip You can also perform most of these functions using the WRKDOMSVR command.

Starting a Domino server using iSeries Navigator

To start a Domino server using iSeries Navigator, follow these steps:


2. Open the iSeries server where you installed Domino.




Chapter 10: Managing a Domino Server Using iSeries Navigator 71

6. Right-click the Domino server and select Start.

Note Starting the Domino server may take a few minutes.

Tip You can also use the following OS/400 command to start a Domino server:

STRDOMSVR SERVER(servername)


Note A new feature in Domino 6 allows you to start all Domino servers on your iSeries server. To do this, right-click Domino and select Start all Domino servers.

Stopping a Domino server using iSeries Navigator

To stop a Domino server using iSeries Navigator, follow these steps:






6. Right-click the Domino server and select Stop.

Note Stopping the Domino server may take a few minutes.

Tip You can also use the following OS/400 command to stop a Domino server:

ENDDOMSVR SERVER(servername)


Note A new feature in Domino 6 allows you to stop all Domino servers on your iSeries server. To do this, right-click Domino and select Stop all Domino servers.

Stopping a Domino subsystem using iSeries Navigator

To stop a Domino subsystem using iSeries Navigator, follow these steps:



3. Click Work Management.

4. Click Subsystems.

5. Right-click the Domino subsystem you want to stop and select Stop.

6. On the Stop Subsystem display, select Controlled and click the Stop button.

Note If the subsystem does not stop in 20 minutes, follow these steps again, but select Immediate instead of Controlled.


Starting the Java Server Controller

To start the Java Server Controller using iSeries Navigator, follow these steps:





5. Right-click the Domino server and select Start controller.

Note When you start the Java Server Controller, the Domino job that is normally called SERVER will now be called QJVAEXEC. When viewing the job log, be sure to look for this job under the new name.

A new feature with Domino 6 allows you to start all Java Server Controllers on your iSeries server. To do this, right-click Domino and select Start all controllers.

Tip You can also use the following OS/400 command to start a Java Server

Controller:

STRDOMSVR SERVER(servername) JSC(*YES)


The JSC can also be started when running the STRTCP, STRTCPSVR

SERVER(*AUTOSTART), or STRTCPSVR SERVER(*DOMINO) commands if *JSC or *ALL was selected in the AUTOSTART parameter during server configuration.

For more information on using the Java Server Controller, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database

(HELP65_ADMIN.NSF).


Determining the server status using iSeries Navigator

To determine the status of a Domino server using iSeries Navigator, follow these steps:






On the right, there is a list of all Domino servers configured on your iSeries server.

Look under the Status column to determine the status of your Domino server.

Tip You can also use the following OS/400 command to check the status of

Domino servers:

WRKDOMSVR

The following table shows the possible values and their meanings:

Status

Starting

Started

Stopping

Stopped

Unknown

Meaning

The server is being started. However, it is not yet available for use by Notes clients.

The server is running and can be accessed from a workstation.

The server is in the process of stopping.

The server is not active. All server tasks are stopped. This status may also be displayed if a server is configured to use a release that is not currently installed on this OS/400 partition.

The system cannot determine the status of the server.

Changing a Domino server's properties using iSeries Navigator

To change a Domino server’s properties using iSeries Navigator, follow these steps:






6. Right-click the Domino server and select Properties.

7. Edit the properties of the server as needed, then click OK to save your changes.


Tip You can also use the following OS/400 command to change the properties of a Domino server:

CHGDOMSVR SERVER(servername)


For more information on server settings, see “Deciding what to specify for server characteristics” in Chapter 6.

Editing the NOTES.INI file using iSeries Navigator

Depending on your operating environment, you may need to change settings in the

NOTES.INI file. To make changes to the NOTES.INI file using iSeries Navigator, follow these steps:

Caution Making changes to the NOTES.INI file is only recommended for experienced administrators. Even minor changes to the NOTES.INI file can introduce errors into the file and impair the operation of a Domino server.







7. Select the Initialization File tab and click Edit.

Note If the Edit button is dimmed, you cannot change this file.

8. When finished editing, click OK.

Why are partial server properties displayed?

If you are unable to see all of the server properties when using iSeries Navigator, the issue is most likely with your OS/400 authorities. When using iSeries Navigator to manage your Domino server, the OS/400 user profile is authenticated. Make sure you are using an OS/400 user profile with the correct authorities.

For more information on this topic, see Chapter 3 “Installing Domino On Your iSeries Server.”


Installing the Domino Administrator client

To manage your Domino environment using the Domino Administrator client, you must install and configure at least one workstation to act as the Administration workstation. To install and configure your workstation, follow these steps:

1. Insert the Notes Client CD-ROM into your workstation’s optical drive.

2. When the installation wizard appears, follow the instructions to install the Notes client and Domino Administrator client. If you need help with any display in the wizard, click the Help button.

3. Using FTP or the drag-and-drop method in iSeries Navigator, copy the certifier

ID and administrator ID files from the Domino data directory on your iSeries server to the Notes data directory on the Administrator workstation.

4. Open Lotus Notes and follow the instructions on the setup wizard to configure the Notes client.

Caution You must use the Domino Administrator 6 client to manage Domino 6 servers. Do not attempt to use an R5 Administrator client.

For detailed information on setting up the Domino Administrator client, see the

Lotus Domino Administrator 6 Help online or the Domino Administrator Help database (HELP65_ADMIN.NSF).

Launching the Domino Administrator client

If you want to manage your Domino server using the Domino Administrator client, you can open the client interface either from the Notes client or from iSeries

Navigator.

Launching the Domino Administrator client from Notes

To launch the Domino Administrator client from Notes, simply click the Domino

Administrator icon from the navigation bar on the left.

Launching the Domino Administrator client using iSeries Navigator

To launch the Domino Administrator client using iSeries Navigator, follow these steps:







6. Right-click the Domino server and select Server Administration.

The Domino Administrator client will launch and connect to the server document for your Domino server.

For more information about using the Domino Administrator client, see the Domino

Administrator documentation or the Lotus Domino

Administrator 6 Help database (HELP65_ADMIN.NSF).


Chapter 11

Registering and Managing Users

A Domino server on iSeries can have three types of users:

•

Domino-only users. These users connect to the Domino server from a Notes client or a browser. They do not use any OS/400 functions except the Domino for iSeries server. These users do not need an OS/400 user profile.

•

Domino and iSeries users. These users connect to the server from a Notes client or a browser. They also access your iSeries in other ways, such as with 5250 workstation emulation or iSeries Access. These users need both an

OS/400 user profile and a Domino registration.

•

Domino users who need DB2 UDB for iSeries access. These users might not appear to run an OS/400 application. However, they might use a Notes application that accesses DB2 UDB for iSeries data. Whether they need an

OS/400 user profile depends on how you design your Notes application.

Note Only US ASCII characters are supported for an Internet mail address. There is no support for accented characters. Therefore, users who are registered as Notes users using accented characters must have an equivalent Internet address using only

US ASCII characters. If the Internet address contains accented characters that do not have US ASCII equivalents (as with Greek or Cyrillic), the Internet address is left blank. The Domino administrator must manually enter a US ASCII Internet address.

Setting up Domino for iSeries users

When you set up a new Domino user on a server, the server application creates the following:

•

A Person document in the server Domino Directory.

•

An ID file for the user. The ID file contains the certificate that the Notes client uses to authenticate with the server. The user’s workstation must have a copy of this ID file for the user to connect to the server successfully.

Chapter 11: Registering and Managing Users 79

Two options are available for setting up Domino for iSeries users:

•

From a Notes client workstation connected to the Domino server, you can use the administration function that is part of Domino to set up a new user. This method does not create an OS/400 user profile for the Domino user.

•

From an administrator workstation connected to the iSeries, you can use iSeries

Navigator to create an OS/400 user profile and register the user for Domino at the same time. You can also use this method to register an existing iSeries user as a Domino user. An administrator workstation needs a Notes client connection to the iSeries and an iSeries Access for Windows connection to the iSeries server.

To create an OS/400 user profile, your Domino administrator’s OS/400 user profile must have *SECADM special authority. To give a user *SECADM special authority, change the special authority field in the user’s profile.

Using iSeries Navigator to add users

Note In order to add or view users for a particular server, your current Notes user

ID must be cross-certified on that server.

Use the following steps to authorize an existing iSeries user to use a Domino server.


2. Open your iSeries server where you installed the Domino software.

3. Click Users and Groups.

4. Click All Users.

5. You can either add an existing iSeries user as a Domino user or you can create a new iSeries and Domino user at the same time.

•

To add an existing iSeries user as a Domino user, right-click the user you want to work with and select Properties. On the User Properties dialog, enter any group, personal, security, and job information.

•

To create a new iSeries and Domino user at the same time, right-click All

Users and select New User. (If the new user will be very similar to an existing user, it may be easier to right-click the existing user and select New

Based On.) On the New User dialog, enter any group, personal, security, and job information.

6. Click the Networks button.


7. On the Networks dialog, click the Domino Registration tab.

The dialog automatically searches each of the servers for the name of the user you selected based on the existing personal information. The registrations display as they are found, one per line. In the list, the server name appears on the left and the user’s registration name appears on the right. If you want to see registrations for the current user on a particular server immediately, double-click the server name and searching starts on that server. If you are not currently signed onto the server, you will be prompted for your password.

8. Select the server where you want to register the user.

9. You may be asked for a password.

10. Click Add.

11. Enter the information as required on the pages. The Other tab allows you to specify where to save the user’s ID file.

12. Click OK to complete the registration. Status messages display as the process continues, which may take a few minutes.

A confirmation message appears to let you know that the user’s ID file has been created. Remember, you need to download the ID file to the user’s workstation.

You may also copy the user ID file to a diskette for the user.

Tip For help on filling in the required fields, click the Help button.

13. You can register the user on another server or click Cancel to return to the

Networks dialog.

14. On the Networks dialog, click OK. The main user dialog appears.

•

If you added an existing iSeries user to the Domino server, the user properties dialog appears. Click OK.

•

If you are creating a new iSeries and Domino user, the new user dialog appears. Click Add.

About Domino for iSeries Single Logon

Domino for iSeries Single Logon is a security feature that provides password synchronization for users of Microsoft Windows, Lotus Notes, and OS/400. This capability allows users to log on once and not have to separately log on to the Notes client or to iSeries Access.

You can obtain the Single Logon feature and installation instructions from the following Web site: http://www.ibm.com/eserver/iseries/domino/singlelogon.htm

Chapter 11: Registering and Managing Users 81

After you install Single Logon on the workstation and log onto Windows, the

Windows password is used for authentication so that iSeries Access for Windows security can automatically connect to iSeries servers. Single Logon also integrates with the Lotus Notes security to provide the Windows password when opening

Notes databases. The user IDs for logging onto Windows and OS/400 do not have to be the same as those for Lotus Notes, but the user IDs must all have the same password.

Note The Windows and OS/400 user IDs must be the same in order to log on to your iSeries server.

When it is time to change passwords, Single Logon synchronizes Windows, Notes, and selected OS/400 passwords. While changing the Lotus Notes password, the

Windows and OS/400 passwords are also synchronized to the same value. This one-step process provides easy password management of all passwords and allows the Windows password to be used later for single logon. Windows 95 and 98 users can also choose to change passwords using the Windows password services.

For an updated list of the Windows clients supported with this feature, see the following Web site: http://www.ibm.com/eserver/iseries/domino/slinstall.htm


Chapter 12

Using Domino for iSeries Multi-version Capabilities

With the 6.0.3 and 6.5.0 releases of Domino, IBM introduces multi-version capabilities for Domino on the iSeries platform. Previous implementations of multiple Domino releases on one iSeries server required separate OS/400 logical partitions (LPARs), which is not always a viable solution for some users. Starting with 6.0.3 and 6.5.0, Domino for iSeries will support multiple releases of Domino on the same LPAR.

This added capability is designed to allow increased flexibility for Domino for iSeries customers. You can now run different applications on different release levels of Domino in one OS/400 partition. One significant advantage of this capability is that you do not have to end servers of one release in order to install another release.

Since the existing servers that are configured to use one release are not automatically updated when installing a different release, these servers can remain active. This provides a very useful environment for running production servers on one release and testing new servers and applications on another release without impacting each other. Operating in this mixed environment can help increase the stability of both testing and production environments.

Installing and using multiple versions of Domino on one OS/400 partition is optional. You can still operate in a single version environment, but there may be some action you need to take to make sure your environment works with these multi-version enabled releases. For more information, see “Preparing for multi-version capable releases” later in this chapter.

Overview of multi-version terms and concepts

This section describes terms and concepts that are important in a multi-version capable environment.

Release

A major release, also called version, of Domino such as Domino 6 or Domino 6.5

includes significant changes or enhancements to the product. Each version has

Maintenance Releases, also called MRs. For example, MRs of Domino 6 are referred to as 6.0.x.

Chapter 12: Using Domino for iSeries Multi-version Capabilities 83

In a multi-version capable environment, any number of multi-version capable

Domino versions and releases can be installed at the same time. For example, you can install Domino 6.5.0, 6.5.1, 6.0.3 and 6.0.4 on the same OS/400 partition. These releases and versions do not have to be installed or removed in any particular order.

Note You cannot install multi-version capable releases on the same OS/400 partition as releases that are not multi-version capable. For example, you cannot install Domino 6.0.2 on the same OS/400 partition where 6.0.3 or 6.5.0 are installed.

For more information and considerations for installing the first multi-version capable release, see “Installing multi-version capable releases” later in this chapter.

Primary release

For systems with multiple versions installed, the term primary release is a way of indicating which installed release provides the most function. The primary release is always the most recently shipped release installed on an OS/400 partition. For example, on a server with Domino 6.0.3 and 6.5.0 installed, 6.5.0 is the primary release. If 6.0.4 is installed later, 6.0.4 becomes the primary release.

There are some situations where Domino will default settings to those of the primary release. In these situations, manual steps are required to manipulate the settings of a server with a release other than the primary release. For more information, see “Managing multi-version capable releases” later in this chapter.

Multi-version capable

This term refers to releases of Domino 6.0.3 and later, and Domino 6.5.0 and later.

All releases of Domino prior to 6.0.3 and 6.5.0, including all R5 releases, are not multi-version capable.

Logical partition (LPAR)

Logical partitions allow you to distribute resources within a single iSeries server to make it function as if it were two or more independent servers. LPAR technology allows for virtual and shared resources, dynamic load balancing, and much more.

For more information on LPAR technology, see the following Web site: http://www.ibm.com/eserver/iseries/lpar

OS/400 partition

This term is used synonymously with LPAR. If you are not using multiple LPARs on your iSeries server, then the term OS/400 partition would be the same as your iSeries server.

Updating a Domino server

The term “updating” is typically used synonymously with “upgrading.” These two terms are emerging to imply two different things. Updating refers to applying a newer release of software, while upgrading refers to hardware.


With multi-version capable releases of Domino for iSeries, the product is no longer updated automatically during installation. The only exception to this is when installing a multi-version capable release over a release that is not multi-version capable. For more information on this situation, see “Installing multi-version capable releases” later in this chapter.

Preparing for multi-version capable releases

For Domino releases that are not multi-version capable releases, the software is installed into the library QNOTES and uses /QIBM/PRODDATA/LOTUS/NOTES as the path. To enable multiple versions, several significant changes were made which will be seen by all administrators and developers whether they choose to install one or multiple releases of Domino:

•

Beginning with Domino 6.0.3 and 6.5.0, every forthcoming Domino release is now multi-version capable and is installed into its own unique library and directory. For example, Domino 6.5.0 is installed into library QDOMINO650 and directory /QIBM/PRODDATA/LOTUS/DOMINO650. Domino 6.0.3 is installed into library QDOMINO603 and directory

/QIBM/PRODDATA/LOTUS/DOMINO603.

Prior to multi-versioning support, all Domino releases installed into library

QNOTES and directory /QIBM/PRODDATA/LOTUS/NOTES. The QNOTES library and /QIBM/PRODDATA/LOTUS/NOTES path still exist but are shared among multi-version capable releases.

•

Every new release of Domino is packaged as a Domino product option so that when it is installed, it uses its own product library and product directory. For example, release 6.0.3 for 5733LD6 is installed using option 13 of that product.

Release 6.5.0 for 5733L65 is installed using option 10 of that product. New releases of these products will be installed with their own options for that product.

•

For major new versions of Domino, new licensed product IDs are used. For example, Domino 6.0.x uses 5733LD6 and Domino 6.5.x uses 5733L65.


The multi-versioning support was developed with the intent of impacting customer environments as little as possible. However, based upon how you use Domino or how your applications may be written, some changes may be required. Please review the sections below as necessary to make sure you understand the possible impacts.

Installing a multi-version capable release on the same OS/400 partition as Domino

R5 or a release of Domino 6 prior to 6.0.3/6.5.0 will mean that all the existing servers configured on that partition will be updated during installation. These servers should be backed up before the new release of Domino is installed. Once the servers are updated as part of the installation of the new release, there is no way to revert the server and its configuration if it had not been saved. For more information on backing up a Domino server that is not multi-version capable, see either

Installing and Managing Domino for AS/400 (as400hlp.pdf) or Installing and

Managing Domino 6 for iSeries (i400help.pdf). These guides are available from the

Lotus Developer Domain Documentation Library at the following Web site: http://www.ibm.com/lotus/ldd/doc

Installing multi-version capable releases

Installing a multi-version capable release of Domino for iSeries usually consists of installing the *BASE option of the product, then installing the option with the specific release, such as 6.5.0. This differs from R5 and early Domino 6 releases in that the release of the product was also packaged in the *BASE option. Since these releases were not multi-version capable, it was acceptable that each new release installation would overwrite the release already installed.

Since the installed release is no longer overwritten when you install an updated release, doing so will result in having multiple releases on the same OS/400 partition. If you do not wish to have multiple versions installed on the same OS/400 partition, you must manually remove one of the releases. For more information on removing a multi-version capable release, see “Removing multi-version capable releases” later in this chapter.

To install a multi-version capable release of Domino for iSeries, you must first install the *BASE option of the product if it is not already installed. For example, if you install the *BASE option from the 6.5.0 media, you can install option 10, which is the 6.5.0 release. Since option 11 is not available in this *BASE option, you cannot install the 6.5.1 release. However, if you install the *BASE option from the

6.5.1 media, both options 10 and 11 are available, allowing you to install both 6.5.0

and 6.5.1 releases.


Installing a multi-version capable release

You can either install a multi-version capable release from the product CD-ROM using the LODRUN command, or from a save file using the RSTLICPGM command.

•

If you choose to use install the release from the product CD-ROM with the

LODRUN command, the installation process will determine if the *BASE option for that release is already installed. If that particular release’s *BASE option is not installed, the LODRUN command will install the *BASE option from the CD-ROM. After that option has been installed, it will install the release option of Domino, such as option 10 for Domino 6.5.0.

•

Installing the release from a save file using the RSTLICPGM command involves a few additional steps. If the *BASE option for this release is not already installed on this OS/400 partition, you must install it before installing the release option. To install the *BASE option using the RSTLICPGM command, type the following at any OS/400 command line and press Enter:

RSTLICPGM LICPGM(productid) DEV(*SAVF) OPTION(*BASE)

LNG(2924) SAVF(QNOTES)

where productid is the Licensed Program identifier, such as 5733L65.

Once the *BASE option is installed, you can install the release option by typing the following command and pressing Enter:

RSTLICPGM LICPGM(productid) DEV(*SAVF) OPTION(10) LNG(2924)

SAVF(QNOTESRL)

where productid is the same Licensed Program identifier you used above.

In this example, option 10 is specified, which installs the 6.5.0 release of

5733L65 to the save file QNOTESRL. The actual option you specify depends on which release you are installing.

Note You can remove this release of Domino and leave all other multi-version capable releases of Domino on the OS/400 partition by removing the release option only. For example, to remove only the 6.5.0 release of Domino, type the following command and press Enter:

DLTLICPGM LICPGM(5733L65) OPTION(10)

For more information on removing releases of Domino, see “Removing multi-version capable releases” later in this chapter.


Installing a release that is not multi-version capable after installing a multi-version capable release

In order to install a release that is not multi-version capable after installing a multi-version capable release, you must first remove the multi-version capable release. To remove a multi-version capable release, type the following at any

OS/400 command line and press Enter:

DLTLICPGM LICPGM(productid) OPTION(*ALL)


Note Any Domino servers that are configured to use the multi-version capable release will still be configured to use that release, but you will not be able to use them until that multi-version capable release is reinstalled on that OS/400 partition.

Updating to a multi-version capable release from a release that is not multi-version capable

As you install your first multi-version capable release on an iSeries server with

Domino servers already configured, all releases that are not multi-version capable will automatically be updated. For example, if you install Domino 6.5.0 on an

OS/400 partition that has Domino 6.0.2 servers, they will all be updated to the 6.5.0

release.

To perform this update, all servers configured to run a Domino release prior to 6.5.0 must be ended before you can install the *BASE option of the multi-version capable release. After the *BASE option has been installed, as you install the multi-version release’s option, all existing servers configured to use a release prior to 6.0.3/6.5.0 will automatically be updated to use this new release.

Note You can not run multi-version capable releases of Domino on the same

OS/400 partition as releases that are not multi-version capable.

Installing multiple releases of Domino

To use multiple releases of Domino on the same OS/400 partition, the option for each release must be installed. To install the option for a particular release, the

*BASE option that defines that option must be installed. For example, the *BASE option for 6.5.0 defines option 10. If you only have this *BASE option installed on your OS/400 partition, you can not install option 11, which is Domino 6.5.1.

However, if you have the *BASE option for 6.5.1 installed, it defines the both options 10 and 11, allowing you to install either 6.5.0 or 6.5.1 by specifying the appropriate option during installation.

This approach to defining and packaging every new maintenance release of Domino as options will continue as each one becomes available. With each new maintenance release, the *BASE option that defines it will also be made available.


Domino 6.5 for iSeries is defined and packaged in the same way. Each maintenance release is defined as options of the 5733L65 product. The first release of Domino 6.5

for iSeries is 6.5.0, and its corresponding option is 10. For example, to install this release using the LODRUN command, place the product CD-ROM in the optical drive of your iSeries server, type the following command and press Enter:

LODRUN DEV(*OPT) DIR('/OS400')

When a second multi-version capable release is installed, servers that are configured to use any other multi-version capable release should not have to be ended. If a multi-version capable release is reinstalled, any servers that are configured to use that release must first be ended.

Note You can use multi-version capable releases of Domino for iSeries from both the 5733LD6 and 5733L65 products on the same OS/400 partition. The order in which you install the different releases between the two products does not matter.

C API restriction with multiple releases installed

The C API option of the Domino product (option 1) is not multi-version capable, so installing the C API option for one release completely overwrites the C API for another release. For example, if the C API option for 6.5.0 is installed, then the C

API option for 6.0.3 is installed, the 6.0.3 version becomes the only installed version. This is important for users that develop applications that use a specific C

API release.

If you need to change the installed release of the C API option, simply install (or reinstall) the option from the release you want, as this option can be installed or reinstalled in any order.

Removing multi-version capable releases

There are some special considerations to keep in mind for removing multi-version capable releases of Domino for iSeries.

Any Domino servers that are configured to use a multi-version capable release must be ended before that release’s option can be removed. Failure to end a Domino server before attempting to remove that release’s option will result in an error message notifying you that the server must be ended.

Once a particular release has been removed, any remaining Domino servers configured to use that release will not start. To use these Domino servers again, you must either update the server to a release of Domino that is installed, or reinstall the release option.


Multi-version capable releases of Domino can be removed in any order. For example, if your OS/400 partition has both 6.5.0 and 6.5.1 releases installed, you can remove either release without affecting the other. For example, release 6.5.1 can be installed while 6.5.0 servers remain active.

Note When a Domino server’s release is the primary release on an OS/400 partition, some objects are copied to QSYS and QNOTES during installation. If this release is removed, these common objects are also removed from QSYS and

QNOTES. If other releases of Domino are installed on the same OS/400 partition, objects from the next primary release are automatically copied into QSYS and

QNOTES.

To completely remove Domino for iSeries, you must remove every option including

*BASE. To do this, type the following at any OS/400 command line and press

Enter:

DLTLICPGM LICPGM(productid) OPTION(*ALL)


Managing multi-version capable releases

One significant change to consider when dealing with multi-version capable releases, is how the installed releases are integrated with each other. There are certain objects that can only exist once on an OS/400 partition. The multi-version capable releases are designed to recognize this and accommodate this as part of their installation. Whenever a more recent multi-version capable release is installed, its commands, panel groups, and message files are copied to QSYS and QNOTES.

When these commands are used on the iSeries in an interactive session or a batch program, the primary release version of the commands are used.

Other commands can be used against any release, no matter which release the command originated from. For example, the command ENDDOMSVR

SERVER(*ALL) will end all active servers on the OS/400 partition that are currently running. It does not matter which release of Domino the servers are configured to use, or which release of Domino defined the command.


Note Even when a library qualified use of this command is entered, all currently active servers on that OS/400 partition are ended, no matter which release they are configured to use. For example, on a server with Domino 6.5.0 and 6.0.3 installed, the following command would still end all active servers:

QDOMINO603/ENDDOMSVR SERVER(*ALL)

The following subsections detail how different commands work in a multi-version capable environment. There are also details on a new command, UPDDOMSVR.

WRKDOMSVR

Issuing the WRKDOMSVR command displays all configured Domino servers on a particular OS/400 partition, regardless of which release a server is configured to use.

To display a server’s configured release library and Domino release level, press F11 from the main display for the WRKDOMSVR command.

If any server is configured to use a specific release of Domino that is not installed, the server’s status will show *UNAVAIL.

All functions of the WRKDOMSVR display are supported and all can be used against any server displayed.

Note There are two exceptions. You cannot start or change a Domino server with a status of *UNAVAIL. Attempting to start it will fail with message LNT0218, and attempting to change it will fail with message LNT0215.

The following shows a sample of the WRKDOMSVR display after pressing F11.


CFGDOMSVR

When multiple releases of Domino are installed on one OS/400 partition, new

Domino servers can be configured to use any of the installed releases of Domino.

The CFGDOMSVR command is one that can be library qualified and run against specific releases.

If you use CFGDOMSVR without library qualifying it, it will use the primary release of Domino installed. For example, if you have both Domino 6.5.0 and 6.5.1

installed on your OS/400 partition, the following command will only create servers that are configured to use 6.5.1:

CFGDOMSVR SERVER(servername)


If you library qualify the CFGDOMSVR command, you can configure a server to use any installed Domino release. For example, to configure a Domino 6.5.0 server in the above environment, you would use the following command:

QDOMINO650/CFGDOMSVR SERVER(servername)


Using the *REMOVE option in any multi-version capable release can be used to remove any configured Domino server. Therefore, if the specific release that a

Domino server is configured to use is no longer installed, you can still remove that server using the following command:

CFGDOMSVR SERVER(servername) OPTION(*REMOVE)

where servername is the name of the Domino server you are removing.

CHGDOMSVR

The CHGDOMSVR command is used to change the configuration of existing

Domino servers. You can use this command on any server, from any installed library. This command detects the release of the server you specify and displays the appropriate parameter options for that server’s release. This means that you must have that server’s release currently installed on your OS/400 partition for this command to work properly. If a server’s release is not installed, and you try to change its configuration, you will receive the error message LNT0218. You can either update your server to an installed release, using the UPDDOMSVR command, or install the appropriate release for that server.


UPDDOMSVR

The UPDDOMSVR command allows you to update specific Domino servers to newer releases. You can update all servers, or select specific servers, allowing you to control which servers are configured for specific Domino releases.

Note You must end the Domino server before attempting to update it.

You can only update a Domino server to a release that is currently installed on your

OS/400 partition. While it is not possible to update a Domino server to a previous release, you can update a Domino server to its own release.

For more information on the UPDDOMSVR command, see Appendix C “Using

OS/400 Commands With Domino for iSeries.”

Using applications with multi-version capable releases

The intent of this section is to provide a brief overview of ways you can more easily use Domino applications in a multi-version capable environment. For more detailed information on these and other application development issues, see the book

Application Development Guide (apdev400.pdf) which is available from the Lotus

Developer Domain Documentation Library at the following address: http://www.ibm.com/lotus/ldd/doc

In many circumstances, Domino applications continue to function in a multi-version capable environment as they did previously. There are some things to consider in regard to applications, and actions you can take to ensure your applications work as expected in a multi-version capable environment.

The primary issue for making sure your applications run correctly is ensuring they use the proper path. In previous releases, Domino set the path for applications to

/QIBM/PRODDATA/LOTUS/NOTES. With multi-version capable releases, this path still exists as a symbolic link to the most recent release’s path. The actual path for a given release now contains the specific release name. For example, Domino

6.0.3 will set the path to /QIBM/PRODDATA/LOTUS/DOMINO603. Therefore, if your application has the old path hard coded, it will only refer to the path of the most recent release installed and may fail in a multi-version capable environment.


To make sure your applications function correctly in a multi-version capable environment, you must correctly set up your Domino run time environment. Your applications should be designed to work with any Domino server, no matter which release it is configured to use. The application should be coded so that the run time environment set up checks the server’s current configuration and automatically sets up the environment to be consistent with the server’s configured release. The following commands and APIs are useful tools to help you accomplish this in your applications:

Note All of these commands and APIs are available beginning with Domino

5.0.12 and 6.0.1. You can use these in your applications even if you are not yet using multiple versions of Domino on the same OS/400 partition.

RUNDOMCMD

The Run Domino Command utility runs a given program against a server after setting up the environment for a particular server. When this command is run interactively, it will restore the current environment back to what it was before issuing the RUNDOMCMD utility.

For example, to use the RUNDOMCMD utility to run the C API called “acllog” type the following at any OS/400 command line and press Enter:

RUNDOMCMD SERVER(servername) CMD(call PGM(qnotessdk/acllog) parm(acllog.nsf)) BATCH(*NO)

where servername is the name of your Domino server where you are running this

API.

Note In Domino R5, RUNDOMCMD was installed into a library. This example assumes that the library is in the Library List for the job. With Domino 6, the

RUNDOMCMD utility is copied into the QSYS library.

SETDOMENV

The Set Domino Environment command is installed automatically into QNOTES and copied into the QSYS library with Domino 6 for iSeries. This command is used to set the current environment for the specified server and specific job. Unlike the

RUNDOMCMD utility, there is no command parameter. Once the SETDOMENV command has been issued, the environment is set until the job ends.

The possible parameters for SETDOMENV are as follows:

•

SERVER - You must enter the name of the Domino server where information about the environment is retrieved.


•

USER - You must specify one of the following two options:

•

*CURRENT specifies that the user profile will not be switched.

•

*SERVER specifies that the user profile associated with the server configuration should be switched for the current profile. For any Domino server using any release of Domino for iSeries, this user profile is restricted to be QNOTES.

Note If SETDOMENV is used to switch the profile to QNOTES in an interactive job, the command line can no longer be used since

QNOTES is a restricted profile. Sign-off will still work from the command line.

•

PATH - You must specify one of the following three options:

•

*REPLACE specifies that the current environment variable path will be set to the server’s data directory, executable directory, and Domino user directory.

•

*APPEND specifies that the server’s data directory, executable directory, and user directory names will be appended to the current value for the path environment variable.

Note If there are other Domino directory names in the path ahead of your server’s, Domino may open a database in one of those other directories instead of your server’s directory.

•

*PREPEND specifies that the server’s data directory, executable directory, and Domino user directory names will be prepended to the current value for the path environment variable. They will appear first in the path environment variable.

For example, to use the SETDOMENV command, type the following at any OS/400 command line and press Enter:

SETDOMENV SERVER(servername) USER(*SERVER) PATH(*REPLACE)


QnninSetDominoEnv

QnninSetDominoEnv is a Domino for iSeries API included in the *BASE option for

Domino 6. This API is provided by the QNOTES/QNNINLDS SRVPGM, and works in a similar manner as the SETDOMENV command, but with a few differences. The API sets the environment for a specific Domino server, but it saves the current job environment. The API must be run again to reset the environment back to its original profile before it can be run again in the same job.

This API is useful for developers, as it removes the necessity for knowing specific environment information about each Domino server.


Using these APIs allows an application to set the Domino environment that is appropriate to a server’s current configuration. The application doesn’t have to be aware that different servers might be configured to use different releases of Domino or that a server has been updated to use a new release of Domino.

Writing applications to use existing environment variables

Applications can be written to correctly set the Domino environment so that a server can access Domino tasks or data in a Domino database, even without using the provided APIs. The environment must be specific to the server that owns the tasks or databases which the application needs to access. This must be done for every

Domino server accessed in the same job before the server is accessed.

Applications should not be written with specific directory path names that are associated with Domino servers, as these path names change as the servers are updated to newer releases.

One exception to this rule is the Domino user directory. This directory should always be last in the path environment variable an does not change based on a server’s current configuration. The Domino user directory path is

/QIBM/USERDATA/LOTUS/NOTES.

To correctly set the Domino environment, the application should be written using

QnninRtvDominoServerI (Retrieve Domino Server Information). This API is provided by the QNOTES/QNNINLDS SRVPGM. Given the server’s name, this

API will retrieve the server’s executable directory path and data directory path. The application can be written to use these returned values to always set up the correct environment for any Domino server.

For more information on using the QnninSetDominoEnv and

QnninRtvDominoServerI APIs, see the Application Development Guide

(apdev400.pdf), which is available from the following Web site: http://www.ibm.com/lotus/ldd/doc


Chapter 13

Domino for iSeries Security Overview

A key strength of deploying Domino on an iSeries server is the security that these two products provide. This chapter highlights the security built into both Domino and iSeries.

About the QNOTES user profile

Every OS/400 job runs under an OS/400 user profile. The user profile defines operational characteristics for the job. The user profile is also the source for privileges (special authorities) that the job needs for system functions and for the authority that the job needs to perform operations on OS/400 objects.

Domino for iSeries includes an OS/400 user profile called QNOTES. The QNOTES user profile provides the mechanism for Domino access control to work with the underlying OS/400 security. To function correctly, all Domino applications must run under the QNOTES user profile. You should not change the QNOTES user profile.

For more information, see “About OS/400 support for Domino access control” later in this chapter.

Processes that automatically run under the QNOTES user profile

The following Domino processes run under the QNOTES user profile:

•

The Domino server

•

Programs that the Domino server starts as a result of ServerTasks or

ServerTasksAt settings in the NOTES.INI file

•

Programs that start as a result of Program documents in the Domino Directory

•

Hook drivers and extension managers that run in the Domino server

•

Agents that run in the Domino server

•

Programs that start when you enter the Load command at the Domino server console

Ensuring that your Domino application runs under the QNOTES user profile

If your Domino application is not designed to run in a process that automatically runs under the QNOTES user profile, use one of the following techniques to ensure that your application runs under the QNOTES user profile:

Chapter 13: Domino for iSeries Security Overview 97

•

Use the OS/400 Submit Job (SBMJOB) command to run the job in the background (in batch) under the QNOTES user profile. The SBMJOB command has a parameter to specify the user profile that the job should run under. Following is an example for using the SBMJOB command to run the

CUSTSVC program in the CUSTPGM library:

sbmjob cmd(call pgm(custpgm/custsvc)) user(qnotes)

To submit a job that runs under QNOTES, the user must have *USE authority to the QNOTES user profile. In general, you should avoid giving users authority to the QNOTES user profile because the QNOTES user profile has the authority to change or delete any object on your Domino server.

•

Inside your application, swap to the QNOTES user profile by using the following OS/400 system APIs:

•

QSYGETPH - get profile handle

•

QWTSETP - set profile

If you use this technique, be aware of the following:

•

When the program swaps to the QNOTES user profile, the program will not have access to typical programmer functions such as debug commands. To minimize potential security exposures, the QNOTES user profile provides only *USER level authority to OS/400 functions.

•

The program should include an exception or cancel handler to swap back from the QNOTES profile in the event the program aborts or is canceled.

For more information, see “About authority when OS/400 programs access

Domino databases ” in this chapter.

•

Use the RUNDOMCMD utility that ships with Domino.

This utility switches to the QNOTES user profile, runs your application, then switches back to the user profile you were using. Using this utility, you do not need to write additional code in your applications. For more information on the

RUNDOMCMD utility, see Appendix C “Using OS/400 Commands With



Example: Swapping to the QNOTES user profile

Following is a coding example for using the OS/400 APIs to swap to the QNOTES user profile:

/* header files to include */

#include <qsygetph.cleinc> /* Header file for the

QSYGETPH */

#include <qwtsetp.cleinc> /* Header file for the QWTSETP

*/

#include <qusec.h> /* Error code structure */

#include <qsnapi.h> /* Error code structure */

/* declarations */

Qus_EC_t err_code; char cur_user[11] = "*CURRENT "; char qnotes_user[11] = "QNOTES "; char qnotes_password[11] = "*NOPWD "; char user_prof_handle[13]; char qnotes_prof_handle[13];

/* get the handle to the QNOTES profile */

QSYGETPH(qnotes_user,

qnotes_password,

qnotes_prof_handle,

&err_code);

if(err_code.Bytes_Available)

{

/* Error retrieving handle to QNOTES user profile. */

return -1;

}

/* get the handle to the profile we are currently running under */

QSYGETPH(cur_user,

NULL,

user_prof_handle,

&err_code);



{

/* Error retrieving handle to current user profile. */

return -1;

}

/* switch to QNOTES user profile */

QWTSETP(qnotes_prof_handle,&err_code);


{

/* Error switching to QNOTES user profile. */

return -1;

}

/*******************************/

/* do notes APIs or functions */

/*******************************/

/* switch back to current user */

QWTSETP(user_prof_handle,&err_code);


{

/* Error switching to current user profile. */

return -1;

}

About OS/400 support for Domino access control

Domino security and the underlying OS/400 security work together to achieve two objectives:

•

The portability of Domino applications: access control for Domino for iSeries must work just like it does on other Domino server platforms.

•

The security and integrity of other applications that might share the same iSeries server: Domino for iSeries must follow the security rules that apply to every other OS/400 application.

To understand how Domino security and OS/400 work together to achieve these objectives, you need some basic information about how Domino security works and about how OS/400 stores Domino databases.


•

Domino provides the capability to define an access control list for every Domino database. Access control lists provide authorities that are similar to OS/400 object authorities. For example, in Domino, editor authority lets a user change any document in a database. However, an editor cannot delete a database or give other users authority to the database.

Similarly, in DB2 UDB for iSeries, *CHANGE authority lets a user add, change, or delete records in a database file. However, *CHANGE authority does not allow a user to delete the file or authorize others to use the file.

•

When you configure a Domino for iSeries server, you specify the data directory for server databases. For example, you might specify /NOTES/DATA. Domino for iSeries databases (files with an .NSF extension) always reside in the OS/400 integrated file system.

Domino for iSeries creates the Domino data directory with public authority set to *EXCLUDE. Whenever a Domino user creates a new database, the public authority for the new database is *EXCLUDE. This prevents OS/400 users from accessing Domino databases outside of Domino.

Note A user with *ALLOBJ special authority can access or delete any database.

•

Domino for iSeries provides a user profile called QNOTES, which owns the

Domino data directory and all the objects in the directory. The QNOTES user profile has *ALL authority to the objects. Domino server jobs run using the

QNOTES user profile.

Note By default, the QNOTES user profile owns the Domino data directory.

You can change the owner, but you must ensure that the QNOTES user profile has *ALL authority to the directory and the objects in it or your server will not function properly.

Now you can put the pieces together and see what happens when a Notes user tries to access a Domino database:

1. OS/400 checks to see whether the user has authority to the object in the integrated file system (such as /NOTES/DATA/MYDB.NSF). To OS/400, the user appears to be the QNOTES user profile, which owns all of the objects in the /NOTES/DATA/ path. Therefore, OS/400 allows access.

2. Control passes to Domino for iSeries. Domino knows the Notes user who has established a connection with the server and provided authentication. The

Domino server checks that user’s authority on the access control list for the database. If the user has the correct authority, Domino for iSeries allows the user’s request to proceed.


About authority when OS/400 programs access Domino databases

The database integration between Domino and iSeries works in both directions.

Your Domino applications can retrieve (and potentially update) DB2 UDB for iSeries databases. Similarly, OS/400 applications can retrieve (and potentially update) information in Domino databases. Following are the basic steps to gain access to a Domino database from an OS/400 program:

1. To access a Domino database, an OS/400 program uses Domino application programming interfaces (APIs). These Domino APIs are available for C, C++, and Java programming languages.

2. Domino processes the database request as a server program (not a client/server program). Therefore, the Domino user for the database request is the user who is associated with the server.

3. A Domino server can have more than one NOTES.INI file. The NOTES.INI

file specifies the user for server jobs for that INI file.

4. Your OS/400 program can use an API to point to the INI file that is appropriate for the Domino databases that the program wants to access. If your OS/400 program does not explicitly specify an INI file, Domino uses the default user for the server.

5. The Domino user must have the necessary authority to the Domino database.

6. To gain access to the Domino server and the NOTES.INI file, the OS/400 program that contains the APIs must run under the QNOTES user profile. This program cannot use adopted authority because adopted authority does not work with the integrated file system. (Domino databases reside in the integrated file system on iSeries.)

For your Domino server to function properly, the QNOTES user profile must have

*ALL authority to all of the Domino objects. Therefore, you should avoid giving users authority to the QNOTES user profile, either directly or indirectly. Instead, use specific programs for specific functions and use profile swapping. The topic that follows provides an example of this technique.


Setting up authority for accessing Domino databases from OS/400 programs

Following is an example for providing access to Domino data from an OS/400 program while protecting the QNOTES user profile:

1. Create an OS/400 program that contains the API instructions to access specific

Domino databases. For the example, the program is a C++ program called

ACCESSDOM. Following are the security characteristics of the ACCESSDOM program:

•

Public authority is *EXCLUDE.

•

The QNOTES user profile owns the program.

•

The program does not adopt authority.

•

No users have private authority to the program.

2. Create a program that provides the OS/400 user interface. The program might display information from both OS/400 databases and a Domino database. For the example, the program is an RPG program called USERDB1. Following are the security characteristics of the USERDB1 program:

•

Public authority is *EXCLUDE.

•

The QNOTES user profile owns the program.

•

The program adopts the authority of the QNOTES user profile.

•

Authorized users have private authority to the program.

3. Provide access to the Domino database through the following steps:

•

An authorized user runs the USERDB1 program.

•

Program USERDB1 uses an OS/400 API to swap to the QNOTES user profile. (The user does not have direct authority to swap to the QNOTES user profile. However, the USERDB1 program adopts the authority of the

QNOTES profile and, therefore, has sufficient authority to swap to the

QNOTES user profile.)

•

Program USERDB1 calls the ACCESSDOM program and passes parameters about the database request.

•

The ACCESSDOM program runs the Domino APIs to retrieve the Domino data and return it to the USERDB1 program.

•

The USERDB1 program swaps back to the user profile of the requesting user. It displays the Domino data for the user.

Following is a summary of the security features of this example:

•

Public authority to the ACCESSDOM program is *EXCLUDE. No user (except a user with *ALLOBJ special authority) can run this program directly.

Therefore, OS/400 users cannot gain access to Domino databases outside the control of the USERDB1 program.


•

Public authority to the USERDB1 program is also *EXCLUDE. Only specific

OS/400 users have the authority to run the program.

•

The ACCESSDOM program can specify a NOTES.INI file. The NOTES.INI

file can point to a Domino user who has the desired database authorities.

•

This example does not require that any OS/400 users have *USE authority to the QNOTES user profile.

For more information and a coding example, see “Example: Swapping to the

QNOTES user profile” earlier in this chapter.

Security recommendations for Domino for iSeries

Following are recommendations to protect both your Domino server and your other

OS/400 applications and data when you run Domino for iSeries on your iSeries server:

•

The QNOTES user profile owns all of the objects in the Domino data directory.

It has the capability to change or delete any Domino database. The settings for the QNOTES user profile are designed to protect your Domino data. For example, the QNOTES user profile does not have a password. Its initial menu is

*SIGNOFF. You should not change the QNOTES user profile.

•

Public authority to the QNOTES user profile is *EXCLUDE. This prevents users from submitting jobs that run under the QNOTES user profile. You should not change the public authority to the QNOTES user profile. Grant private authority to the QNOTES user profile with extreme caution.

Note To ensure that users cannot submit jobs under the QNOTES user profile, the security level (QSECURITY system value) for your system must be 40 or higher. Otherwise, a job description that runs under the QNOTES user profile represents a security exposure.

•

The QNOTES user profile owns the Domino database directory and the objects in it. To ensure that Domino applications run properly, you should not change the ownership to these objects.

•

Public authority to the Domino database directory and the objects in it is

*EXCLUDE. To ensure that Domino security works correctly, you should not change the public authority to the directory or the objects.

Note The Domino data directory is the directory that you specify when you configure the Domino server, such as /NOTES/DATA.


Chapter 14

Integrating Domino for iSeries With Other Database

Management Systems

Domino 6 for iSeries has the flexibility to integrate with many other Database

Management Systems, enhancing your existing environment.

About DECS

The Domino Enterprise Connection Services (DECS) is a forms-based technology in Domino that provides the capability to integrate live data from OS/400 into

Domino applications. Using DECS, you can build live links from Domino pages and forms to data in the DB2® Universal Database TM for iSeries. The DB2 UDB for iSeries database can be on either the local iSeries or a remote iSeries. For details on setting up DECS, see “Setting up DECS” later in this chapter.

About LEI

Lotus Enterprise Integrator (LEI) is a server-based data distribution product that enables a high performance, scalable exchange of data between Lotus Domino and other host and relational applications. LEI allows you to schedule data synchronization for high volume transfers when server usage is low. For more information on LEI, see the following Web site: http://www.ibm.com/eserver/iseries/domino/related/lei.htm

Note Beginning with Domino 6, the LEI version used must match the Domino version. For example, LEI 6.5 must be used with Domino 6.5. Previous versions of

LEI (such as 3.0) are not supported on Domino 6.

About LS:DO

LotusScript Data Object provides properties and methods for accessing and updating tables in external databases using LotusScript. LS:DO is easy to learn and integrate with OS/400.

Chapter 14: Integrating Domino for iSeries With Other Database Management Systems 105

About DB2 UDB

DB2 Universal Database for iSeries is a fully integrated relational database manager that provides functions and features such as triggers, stored procedures, and dynamic bitmapped indexing that serve a wide variety of application types. These applications range from traditional host-based applications to client/server solutions to business intelligence applications. For more information on DB2 UDB for iSeries, see the database section of the iSeries Information Center at the following

Web address: http://www.ibm.com/eserver/iseries/infocenter

Setting up DECS

The DECS software is installed as part of the BASE installation of Domino for iSeries. When you set up the Domino server, use the Connection services option to make DECS available on the server.

Note For details on installing the Domino software on your iSeries server and setting up a Domino server, see Chapter 3 “Installing Domino On Your iSeries

Server.”

If you want to enable DECS for an existing Domino server using iSeries Navigator, follow these steps:

1. Open your iSeries server with the Domino server you want to change.





6. On the Properties display, click the Services tab.

7. Check the box next to Domino Enterprise Connection Services (DECS) to enable DECS.

Tip You can also use the CHGDOMSVR command to enable DECS on a Domino server. For more information on the CHGDOMSVR command, see Appendix C

“Using OS/400 Commands With Domino for iSeries.”

The DECS files that are installed include a DECS Administrator database template

(DECSADM.NTF) and three documentation databases:

•

Domino Connectors Setup Guide (LCCON.NSF)

•

Domino Enterprise Connection Services User’s Guide (DECSDOC.NSF)

•

LotusScript® Extension for Domino Connectors Reference Guide

(LSXLC.NSF)


The three documentation databases are installed in the DOC subdirectory of the data directory for your server. The User’s Guide contains more information about DECS.

When you restart the server after enabling DECS, the DECS Administrator database

(DECSADM.NSF) is created from the DECSADM.NTF template the first time the

DECS server task is loaded. The DECS Administrator database is then available to add to your Notes workspace. Use the DECS Administrator database to define connections and real-time relationships.

About authority when Domino applications access DB2 UDB for iSeries

An important feature of Domino for iSeries is the integration between Domino and

DB2 UDB for iSeries databases. Several methods are available for Domino applications to access (and potentially update) DB2 UDB for iSeries databases:

•

LotusScript applications use LS:DO (LotusScript Data Object) as an interface to DB2 UDB for iSeries data.

•

Agents written using the Domino formula language can use @Db instructions to interact with a relational database, including DB2 UDB for iSeries.

•

Domino Enterprise Connection Services (DECS) provides real-time access to

DB2 UDB for iSeries data through a Domino application.

All of these methods for accessing DB2 UDB for iSeries from Domino establish a connection from Domino to OS/400. The connection specifies both the user profile whose authority the system uses to access DB2 UDB for iSeries database files and a password for that user profile.

Authority when Domino applications use LS:DO or @Db to access DB2

UDB for iSeries

A Domino application can use either LS:DO (LotusScript Data Object) or @Db functions to provide access to DB2 UDB for iSeries databases. With both methods, the application establishes a connection with the DB2 UDB for iSeries database. The connection specifies an OS/400 user profile and password. Before allowing the connection, OS/400 checks for the following:

•

A valid user profile and password combination.

•

The user’s authority to the DB2 UDB for iSeries database file.

Following are security considerations for protecting your DB2 UDB for iSeries databases when you provide access from Domino applications.


1. For real-time applications (applications connected to a client), decide which

OS/400 user profile the Domino applications will use to access DB2 UDB for iSeries data. You might decide based either on the Domino application or on the

DB2 UDB for iSeries database. Following are the options:

•

Use the user profile of the user who is running the Domino application. With this method, you need an OS/400 user profile for every Domino user who needs to run an application that accesses DB2 UDB for iSeries data.

“Connecting a Domino application to DB2 UDB for iSeries with a matching

OS/400 user profile” describes how your Domino application can provide the OS/400 user profile and password.

•

Set up special OS/400 user profiles whose only function is to provide

Domino access to OS/400 data. This eliminates the need for each Domino user to have an OS/400 user profile. “Connecting a Domino application to

DB2 UDB for iSeries with a special OS/400 user profile” discusses considerations for this method.

•

Use a combination of these methods. Create special user profiles to provide the equivalent of public (or anonymous) access to Domino users. This technique might be appropriate for database files that every user can view.

Rely on the Domino user’s OS/400 user profile either for higher levels of access or for confidential files.

2. For scheduled applications (such as agents), you also need to provide an

OS/400 user profile when you connect to DB2 UDB for iSeries. Scheduled applications run on the server without a connected client. Therefore, the application cannot request a user ID and password from a Domino user. See

“Connecting a Domino application to DB2 UDB for iSeries with a special

OS/400 user profile” for alternatives.

Consider using adopted authority to provide tighter control over the actions a

Domino program can perform on DB2 UDB for iSeries data.

Connecting a Domino application to DB2 UDB for iSeries with a matching

OS/400 user profile

When a Domino application accesses a DB2 UDB for iSeries database, the Domino application needs to establish a connection with DB2 UDB for iSeries. The connection requires a valid OS/400 user profile and password.


When you want your Domino application to connect by using the Domino user’s

OS/400 profile, do one of the following:

•

Prompt the user: Your application can prompt the Domino user for an OS/400 user profile name and password during the first connection within a session. Be sure that your application protects this information carefully. You should avoid storing the passwords for individual OS/400 user profiles on your server.

•

Store the user ID and password: You can provide a form and database for your Domino users who need OS/400 database access. The form would prompt the user for the OS/400 user profile name and password. The application would encrypt the information and store it in a secure database on the client.

Therefore, only the user or an application running on that user’s behalf would be able to decrypt the password.

When you use this method, your users do not need to enter their OS/400 user profile and password every time they make a connection from Domino to DB2

UDB for iSeries. They will, however, need to use the form to update their database record when they change their OS/400 password.

Connecting a Domino application to DB2 UDB for iSeries with a special OS/400 user profile

When a Domino application accesses a DB2 UDB for iSeries database, the Domino application needs to establish a connection with DB2 UDB for iSeries The connection requires a valid OS/400 user profile and password.

You might want to create special user profiles for the purpose of providing connections between Domino applications and DB2 UDB for iSeries databases. Do the following for your special user profiles:

1. Decide how many special user profiles to create. Possible options are:

•

A single OS/400 user profile to provide anonymous (or public) access to non-confidential databases.

•

Multiple special-purpose profiles to provide access to DB2 UDB for iSeries data. You might think of these user profiles as similar to group profiles.

Their role is to simplify the management of authority. Keep in mind that with this method, OS/400 does not know anything about the real Domino user. The Domino application sets the user profile name. You are relying on the Domino administrator to control who can use the application.


2. Decide whether to use passwords for the connection. Possible options are:

•

Your connection can specify a user profile name and *NOPWD. The

QNOTES user profile must have *USE authority to the user profile. With this method, any Domino application can use this OS/400 user profile to attempt to access data.

•

Your application can store the user profile name and a password. You can protect this information so that only trusted programmers can view and update it. However, you must update the application whenever the OS/400 password changes.

With this method, only Domino users who have authority to the program that contains the user profile and password can attempt to access DB2 UDB for iSeries data with it. The QNOTES profile does not need *USE authority to the user profile.

3. Set up the user profile to protect it from unintended use:

•

Set the initial program to *NONE.

•

Set the initial menu to *SIGNOFF.

Using adopted authority for Domino access to DB2 UDB for iSeries data

On your iSeries, you might use adopted authority to manage how users update information. For example, the typical user might have *USE authority to the open order file (which allows viewing but not creating, changing, or deleting). However, you want to make sure that only certain users can create or change orders. You want to make sure that a new order passes edit checks before it goes into the open order file. You accomplish this kind of control on iSeries with adopted authority. A user profile with *CHANGE authority to the open order file owns the program that provides the create and change function. Certain users have *USE authority to run the program.

To use a similar technique when you want to manage the ability to update DB2

UDB for iSeries data from Domino applications, do the following:

1. If necessary, design and create OS/400 programs that perform the desired tasks

(such as changing a specific record in a database). You can probably adapt programs that you already have.

2. Set up the programs to adopt the authority of a user profile that has appropriate authority to the database file. Do the following:

•

To transfer ownership of the program to the appropriate user profile, use the

Change Object Owner (CHGOBJOWN) command.

•

To specify that the program should adopt authority, use the Change Program

(CHGPGM) command. Specify *OWNER for the User Profile (USRPRF) parameter.


3. Define the programs as stored procedures for the DB2 UDB for iSeries database files that you want to update.

4. Design and create your Domino programs to use the stored procedures to update the DB2 UDB for iSeries database files.

5. When your Domino programs connect to DB2 UDB for iSeries, specify a user profile name that has *USE authority to the stored-procedure programs.


Chapter 15

Using Domino as a Mail Server

Domino 6 includes improvements to the security and performance of your Internet and Notes mail.

Overview of Domino mail

The mail features in Domino 6 for iSeries boast a streamlined deployment that improves performance and eases administration. Using the Domino SMTP function, each server in your environment can be bound to its own IP address, boosting server performance by reducing the infrastructure overhead.

The options you specify when you set up the Domino server define the type of mail support that is used for the server. Whether you set up the server using the Domino

Server Setup Wizard (domwzd.exe) or the OS/400 Configure Domino Server

(CFGDOMSVR) command, the options you specify are essentially the same. You can set up your Domino server to have SMTP, IMAP, and POP3 services.

When setting up Domino, specify which type of mail support you want:

•

For Internet mail packages, specify SMTP, IMAP, or POP3.

•

For SMTP services, Domino is the default, and the only accepted value.

Note

If the server is already set up, you can reconfigure the server by using either iSeries Navigator or the Change Domino Server (CHGDOMSVR) command.

If you set up more than one server on the same iSeries with SMTP enabled, each server must have a separate Internet (IP) address. Otherwise, they may compete for the same communications port, creating a port conflict.

The setup process creates or changes documents in the Domino Directory for the server. No additional setup is needed.

Once the SMTP mail support is set up, you can verify that the support is active by checking the status of the Domino SMTP. If you are also running OS/400 SMTP on the same iSeries, make sure it binds to a specific IP address, or it will compete with the Domino SMTP for the same communications port. If these two versions of

SMTP are bound to the same IP address, they may not function simultaneously on the same server.

Chapter 15: Using Domino as a Mail Server 113

Configuring multiple instances of SMTP

With Domino 6 for iSeries, you have the option of configuring multiple Domino

SMTP servers and one OS/400 SMTP server on the same iSeries server. This type of setup allows for more granular control over servers and users, increases server scalability, and lowers your total cost of ownership.

Planning the deployment of this type of configuration is very important. The OS/400

SMTP server and each Domino SMTP server must bind to a specific TCP/IP address. Once this is configured, the Domino SMTP servers can send and receive mail with the OS/400 SMTP server, as if they were communicating over the

Internet. The following illustrates this configuration.

To configure multiple instances of SMTP, you must ensure the following:

•

Domino partitioning must be enabled

•

Each instance must bind to a specific IP address


Follow these steps to bind your servers to specific TCP/IP addresses for configuring multiple SMTP servers on your iSeries server:

Note The following steps do not include steps for setting up a complex network environment. It is important to understand your network and plan your environment accordingly. For help with setting up a complex network environment, see the

Networking section of the iSeries Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

1. Obtain all of the necessary TCP/IP addresses required for the configuration.

One address is required for each Domino SMTP server and the OS/400 SMTP server.

2. Update the Host Table entries for each server. You can either use iSeries

Navigator or the CFGTCP command, selecting option 10.

3. Update the Domain information for each server. You can either use iSeries

Navigator or the CFGTCP command, selecting option 12.

4. Edit the NOTES.INI file for each Domino SMTP server. Set the variable

TCPIP_TcpIpAddress for each Domino SMTP server to the address you assigned to it earlier. For example, edit the NOTES.INI variable as follows:

TCPIP_TcpIpAddress=0,9.xx.xx.100

where 9.xx.xx.100 is the IP address of your Domino SMTP server.

5. Bind the OS/400 SMTP server to a specific IP address using the ADDSMTPLE command. For example, issue the following two commands, substituting your

IP address for the one given:

ADDSMTPLE TYPE(*SVRBIND) INTNETADR('9.xx.xx.50')

ADDSMTPLE TYPE(*CLTBIND) INTNETADR('9.xx.xx.50')

Settings for Domino SMTP support

When you set up mail support using the built-in Domino SMTP, the setup processing creates or changes two documents in the Domino Directory for the

Domino server:

•

Server document

•

Configuration document

The following tables summarize the key settings in each document. The tables show the tab that contains the setting, the name of the field, and the setting.


Server document

Tab

Basics

Basics

Basics

Field

Routing tasks

SMTP Listener task

Fully qualified Internet host name

Setting

SMTP Mail Routing is added

Set to Enabled

Set to the fully qualified Internet host name, which is retrieved from the system TCP/IP configuration settings

Configuration document

Tab

Basics

Router/SMTP

Field

Group or Server name

SMTP used when sending messages outside of the local

Internet domain

Setting

Set to server name that was specified in the server setup

Set to Enabled

Modifying the existing Domino configuration

If you are upgrading to Domino 6 from an environment with MSF, you must reconfigure each Domino server to use a unique TCP/IP address, following these steps:

1. Using a Domino Administrator client, edit the server settings in the Server document so that the Domino SMTP server binds to a resolvable Host Name.

•

Click File.

•

Select Database.

•

Select Open.

•

In the server field of the Open Database dialog, specify the server name that you just configured.

•

Open the Domino directory. In the File name field, type the following and click Open:

names.nsf

•

In the left pane of the Domino directory, click Server.

•

Click Servers.

•

Select the Domino server.


2. Enter values for the following fields:

Tab

Basics

Basics

Basics

Field

Routing tasks

SMTP Listener task

Fully qualified Internet host name

Setting

SMTP Mail Routing is added

Set to Enabled

Set to the fully qualified Internet host name, which is retrieved from the system TCP/IP configuration settings

3. In the Configuration Document, enter values for the following fields:

Tab

Basics

Router/SMTP

Field

Group or Server name

SMTP used when sending messages outside of the local Internet domain

Setting

Set to server name that was specified in the server setup

Set to Enabled

4. Stop and restart the Domino server to make the changes take effect.


Chapter 16

Using Domino as a Web Server

The Domino server includes HTTP server technology that transforms Domino into a

Web applications server. In general, you set up and use a Domino Web server on iSeries in the same way that you would a Domino Web server on any other platform. However, there are some issues you need to know about:

•

WebSphere and Domino integration

•

HTTP server options

•

Avoiding HTTP server conflicts between iSeries and Domino

•

Serving documents from the QSYS.LIB file system

•

Setting up CGI-BIN programs

•

Creating SSL key ring files

For more information about the Domino Web server, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database

(HELP65_ADMIN.NSF).

WebSphere and Domino integration

Although Domino 6 ships a servlet engine as part of the base product, it is limited in its capabilities. If you want to use advanced servlet functions, including Java Server

Pages (JSP), Enterprise Java Beans (EJB), and single signon, you must configure a servlet engine that supports those functions.

The following table details the supported integration points for WebSphere

Application Server and Domino 6.5.

ACC

X

HTTP

X

SSO WAS product

WAS 3.5.x Standard

Edition

WAS 3.5.x Advanced

Edition

WAS 4.0.x Advanced

Single Server Edition

X

X

X

X

X

continued

Chapter 16: Using Domino as a Web Server 119

WAS product

WAS 4.0.x Advanced

Edition

WAS 5.0.x Express

WAS 5.0.x Base Edition

WAS 5.0.x Network

Deployment Edition

ACC

X

X

X

X

HTTP

X

X

X

X

SSO

X

X

X

X

Note The headings in this table represent the following:

ACC - Access to Domino Data from WebSphere applications

HTTP - Use of Domino HTTP server to access WebSphere resources

(Domino plug-in)

SSO - Single signon between Domino and WebSphere applications

Using these two products together allows you to serve both Domino and WAS Web content. For updated information on integrating Domino 6 with WebSphere, see the

Domino 6 Release Notes and the following Web site: http://www.ibm.com/eserver/iseries/domino/domws.htm

For more information on the WebSphere Application Server product, see the following Web site: http://www.ibm.com/eserver/iseries/websphere

HTTP server options

In Domino 6 for iSeries, the original OS/400 HTTP server is not supported. Instead, you may choose either the Domino HTTP server, or the OS/400 HTTP server powered by Apache. The OS/400 HTTP server powered by Apache ships a plug-in that allows local or remote use by Domino.

Note WebSphere Application Server also ships a plug-in that allows WebSphere to use the Domino HTTP server. This allows you to use the Domino HTTP server as the primary Web server for your system, handling both Domino and WebSphere

HTTP traffic.

The OS/400 HTTP server powered by Apache also provides the capability to serve both Domino and WebSphere HTTP traffic through a single Web server. Depending on your current environment, you may need one of these plug-ins to provide these functions.

Each version of HTTP provides some unique advantages. For example, while the

Domino HTTP server provides simple administration and may reduce the total number of required Internet ports, the HTTP server powered by Apache provides improved SSL and failover capabilities.


For more information on configuring Domino to use the HTTP server powered by

Apache, see the following Web site or the Domino 6 Release Notes that shipped with the product: http://www.ibm.com/eserver/iseries/domino/apache.html

Avoiding conflicts between the iSeries HTTP server and the Domino HTTP server

OS/400 includes several TCP/IP application servers, including an HTTP server that is known as OS/400 HTTP server powered by Apache. This HTTP server processes

HTML documents, CGI scripts, and Java scripts for home pages. Domino for iSeries also provides an HTTP server capability, which enables Notes databases to be seen as HTML documents on the Web.

You can have both HTTP servers installed and running. However, the Domino

HTTP server and the HTTP server powered by Apache are both set up to use

TCP/IP port 80. Because both HTTP servers use the same port, the second server that is started will have a problem accessing the port. To eliminate this problem, do one of the following:

Change the OS/400 HTTP server so that it uses a port other than port 80.

Change the OS/400 HTTP server by following these steps:

1. End the OS/400 HTTP server by entering the following OS/400 command:

endtcpsvr *http

2. Use the OS/400 WRKHTTPCFG command to change the port number for the

OS/400 HTTP server.

Configure each server to listen on port 80 but at a different IP address.

Configure the OS/400 HTTP server by following these steps:

1. End the OS/400 HTTP server by entering the following command:

endtcpsvr *http

2. Use the BindSpecific and HostName directives in the WRKHTTPCFG command to change the TCP/IP server so that it binds to a specific IP address.


3. Enable the “Bind to host name” field in the Server document in the Domino

Directory and specify an IP address that is different from the IP address used for the OS/400 server.

Note When configuring new Domino servers (using either the Setup Wizard or the

CFGDOMSVR command), there is an option you can specify during server setup for binding the HTTP port to the IP address that the Domino server uses.

Change the Domino HTTP server so that it uses a port number other than port 80.

You change the HTTP server port number in the server document of the Domino

Directory for the Domino server.

Serving documents from the QSYS.LIB file system

Domino for iSeries can serve HTML documents from the integrated file system, including the QSYS.LIB file system. When serving HTML files and CGI-BINs that are not Notes databases, be aware of the following:

•

You must add the appropriate MAP and PASS directives to the domcfg.nsf

database (or to the HTTPD.CNF configuration file in the Domino data directory). The data in the HTTPD.CNF file is ASCII. To edit the file, use the

OS/400 EDTF command or copy the file to an ASCII system. Make sure the

QNOTES user profile has the authority to read HTTPD.CNF after making changes. Use the OS/400 Work with Object Links (WRKLNK) command to change the authority as follows:

•

Display the contents of the data directory for the server. For example:

wrklnk '/notes/data/*'

•

Enter a 9 (Work with authority) next to the HTTPD.CNF file.

•

Verify that either QNOTES or *PUBLIC has at least read (*R) data authority. If necessary, you can use option 1 or 2 to correct the authority for the file.

•

If you serve files from the QSYS.LIB file system, the suffix is either .mbr or

.MBR. You must add an AddType directive to the HTTPD.CNF file for the

.MBR and .mbr suffix to set the appropriate type. For example, add the following line to the HTTPD.CNF file to allow data in the QSYS.LIB file system to be served as an HTML document:

AddType .MBR text/html 8bit 1.0 # QSYS file system

•

Data served from the QSYS.LIB file system is mapped from the file EBCDIC code page to ASCII.


•

In addition to authenticating access to Domino databases, Domino for iSeries can also authenticate users for access to files in the integrated file system, including QSYS.LIB. You can use the PasswdFile subdirective to indicate how the authentication should be done.

The PasswdFile subdirective can contain either %%SYSTEM%% or the name of a validation list object. %%SYSTEM%% is used to indicate all valid OS/400 users. The validation list object is the OS/400 substitute for a password file.

You can build a validation list object that contains “Internet” users; that is, names that have an associated password but cannot sign onto the iSeries server.

You can build the validation list object using OS/400 APIs. Here are examples of using the PasswdFile subdirective.

To specify that you want to use OS/400 user profiles to validate user names and passwords:

PasswdFile %%SYSTEM%%

To specify that you want validation list object VLDL in library QUSRSYS to be used for a protection mechanism:

PasswdFile QUSRSYS/VLDL

Setting up CGI-BIN programs

There are two ways in which you can define the location in which the server should look for a CGI-BIN program:

•

Change the Server document in the Domino Directory to specify the desired directory (location).

•

Use the Mapping form in the Domino Configuration database (DOMCFG.NSF) to map the CGI-BIN URL to the desired directory (location) and specify

EXECUTE access.

You can also use ILE RPG and ILE COBOL programs as CGI-BIN programs.

Defining the location of a CGI-BIN program

The ILE C CGI-BIN program named MYLIB/CGIEXMP is referenced from an

HTML document with the following tag:

<form method=POST action = "/cgi-bin/cgiexmp.pgm">

This example assumes that the default CGI-BIN path is /cgi-bin. To have the server pick up the desired CGI-BIN program, use one of the following procedures:


Change the server document in the Domino Directory

1. Open the server document for the Web server in the Domino Directory.

2. In the HTTP Server section, type in the CGI directory field:

/qsys.lib/mylib.lib

3. Save the document and restart the Web server.

Change the Domino Configuration database

1. Open the Domino Configuration database (DOMCFG.NSF) and choose

Create -> Mapping URL -> Directory.

2. In the URL path field, type:

/cgi-bin

3. In the directory field, type:

/qsys.lib/mylib.lib

4. Click Execute.

5. If you are creating a mapping for a virtual server, specify its IP address in the IP address field.

6. Save the document and restart the Web server.

Creating SSL key ring files

The Certificate Authority application (CERTCA.NSF) allows you to establish a

Certification Authority (CA) within your organization. As an internal CA, you are responsible for handling certificate requests from Domino server administrators within your organization and adding client certificates to the Domino Directory.

Setting up an internal CA simplifies the process of creating and managing certificates when your users do not need to communicate with external servers or when external users do not need to access your servers. In addition, setting up an internal CA allows you to avoid unnecessary fees that external CAs charge to create and recertify certificates.

The Certificate Authority application allows you to create the CA certificate and key ring file, sign server certificates, and add client certificates to the Domino Directory.

Before you can use the Certificate Authority application, you must create the database using the Certificate Authority template (CERTCA.NTF) and enforce database and server security.


To use the Server Certificate Administration application for your Domino server on iSeries, you need to map a network drive to your OS/400 data directory and specify that drive when creating your key ring and certificate files. To map a network drive, you must have either of the following on the workstation:

• iSeries Access support

For more information about iSeries Access, see one of the following:

•

The iSeries Access documentation, iSeries Access for Windows - Setup

(SC41-5507-03)

•

The EZ Setup CD-ROM that is provided with your iSeries server

• iSeries NetServer support

For more information about iSeries NetServer, see the iSeries NetServer Web site at the following address: http://www.ibm.com/eserver/iseries/netserver

If the workstation has the Windows 95, Windows 98, or Windows NT operating system, you can use the Network Neighborhood to map the network drive. See the

Windows online help for instructions.

It is more secure to run the Certificate Authority application from a workstation and keep the certificate authority CA key ring on the workstation. In other words, the

Certificate Authority database (CERTCA.NSF) resides on the Domino server (for

Web availability) but the CA key ring file resides on the workstation hard disk. For detailed descriptions of how to set up SSL certificates, see the Lotus Domino 6

Release Notes and the Domino administration documentation or the Lotus Domino

Administrator 6 Help database (HELP65_ADMIN.NSF).

You can also use the following methods to manage your key ring and certificate files:

•

Create the key ring files and certificates using Domino on another platform and then use FTP to copy them in binary mode to your Domino data directory on your iSeries server. Make sure the QNOTES user profile has read (*R) authority to the files after you copy them to the data directory.

•

Use the HTTP server powered by Apache to create your key ring files and certificates. For more information, see the following Web site: http://www.ibm.com/eserver/iseries/http


Chapter 17

About Directory Services and Domino

Domino 6 for iSeries provides directory services to help you get the most out of your environment, including support for the following services:

•

Centralized Directory

•

Lightweight Directory Access Protocol (LDAP)

•

Active Directory

• xSP Hosting

Directory synchronization

In Domino 6 for iSeries, support for directory synchronization between the OS/400

System Distribution Directory (SDD) and the Domino Directory has been removed.

If you want to deploy a similar solution in Domino 6, you can set up an iSeries

LDAP server so that the SDD publishes information to the iSeries LDAP server.

Then set up your Domino Directory to use the iSeries LDAP directory. You can set up a replication schedule to provide a similar solution to the former directory synchronization support.

Using a centralized directory architecture

In a centralized directory architecture, a relatively few number of servers in the domain have replicas of a central directory that contains the entire contents of the

Domino Directory. The other servers in the domain have smaller, selective replicas of the central directory, known as configuration directories, that contain only documents used for Domino configuration. A server with a configuration directory looks up user, group, and any customer-defined entries in a central directory.

Configuration directories can be beneficial because they require less disk space, less replication, and less view indexing than the primary Domino Directory in the traditional distributed directory architecture.

For information on setting up and using a centralized directory with Domino, see the

Domino administration documentation or the Lotus Domino Administrator 6 Help database (HELP65_ADMIN.NSF).

Chapter 17: About Directory Services and Domino 127

Using LDAP with Domino

You can set up Domino to use a new or existing Lightweight Directory Access

Protocol (LDAP) directory. In Domino 6 for iSeries, the following improvements were made to better interact with IBM Directory Server:

•

Client authentication against IBM Directory Server for all Internet services

•

A new schema database simplifies schema extension

•

A schema daemon maintains consistency across the entire domain

For information on setting up and using an LDAP directory with Domino, see the

Domino administration documentation or the Lotus Domino Administrator 6 Help database (HELP65_ADMIN.NSF).

LDAP port conflict

With OS/400 V5R1 or later, system directory services (LDAP) is always started by default when TCP is started and will bind port 389 to all configured IP addresses.

When starting a Domino server that has the directory configured, it will attempt to bind to port 389. A port conflict will result and the following message will be shown:

LDAP Server: Listener failure: The requested TCP/IP port is in use on this system.

In order to allow the Domino server’s directory task to serve LDAP client requests, the OS/400 administrator must end the system directory services and configure the system to not automatically start the OS/400 Directory service.

If the IBM Directory Server on OS/400 is required in addition to running the

Domino Directory task, then one of the following steps will be necessary:

•

Change the port number used for the Domino server’s directory support (in the server document) to another unused IP port.

•

End OS/400 system directory services and change the port number used from

389 to another unused IP port and then restart system directory services.

For more information, see the following Web site: http://www.ibm.com/eserver/iseries/ldap

Changing the default directory port number to a value other than 389 also requires that all LDAP clients configured to connect via port 389 must also be reconfigured to use the new IP port number in order to allow their directory requests to be served via the new port.

If changing the port number is not an option, consider modifying the Domino

Directory and the IBM Directory Server on OS/400 directory services to each bind port 389 to a specific IP address.


With V5R2, the function to bind the IBM Directory Server on OS/400 to a specific

IP address is included. If you are using V5R1, you need to apply the OS/400 IBM

Directory PTF SI03067. For more information on obtaining PTFs, see the following

Web site: http://www.ibm.com/eserver/iseries/service

Note During an upgrade from Domino 5.0.x, or during a new server setup,

Domino 6 will detect whether or not your environment uses an LDAP server. If your environment does not, Domino 6 will disable the listener port to eliminate this conflict. However, if you later decide you would like to use an LDAP server, you will have to enable the listener port, and follow one of the steps above to eliminate the potential conflict.

Using xSP Hosting

A new feature in Domino 6 is the ability to use xSP Hosting. This provides a secure avenue for hosting multiple organizations with one instance of Domino. By creating virtual directories, multiple organizations can utilize one Domino directory, independent of each other. The Extended Access Control List (xACL) capabilities help refine user access to the Domino directory so organizations can easily be isolated from one another.

For more information on the xSP Hosting environment, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database

(HELP65_ADMIN.NSF).

Chapter 17: About Directory Services and Domino 129

Chapter 18

Managing Backup and Recovery

There are many options available for backup and recovery procedures on the iSeries. You can save and restore objects by using a magnetic tape, optical media, or a save file. You can even take advantage of a networked environment to save and restore objects with another system outside of your iSeries server.

There are also a number of independent products available for helping you implement a backup and recovery strategy.

One product that works well with Domino for iSeries is Backup Recovery and

Media Services (BRMS) for iSeries. For more information about BRMS for iSeries, see the section, “Configuring and using BRMS for Domino” later in this chapter.

About backing up a Domino for iSeries server

A Domino server often contains important business information that may not exist elsewhere in your organization. For example, users may rely on e-mail for important communications that are not documented anywhere else. Similarly, an on-line customer service application might contain records that do not exist in printed form.

To protect the data from disasters (such as a site loss or hardware loss) and from human error, such as accidentally deleting a critical database, develop a good strategy for regularly backing up the information on your Domino server. Make a plan to back up the following:

•

Objects that change infrequently, such as programs for the Domino product.

•

Objects that change regularly, such as Domino databases.

“Backing up Domino programs and product files” in this chapter describes options for backing up the relatively static (unchanging) parts of your Domino server.

“Backing up all Domino databases” describes the options for backing up the dynamic (changing) parts of your Domino server.

Chapter 18: Managing Backup and Recovery 131

Domino for iSeries takes advantage of the OS/400 single-level store architecture.

Domino databases and programs are spread across all the iSeries disk units, along with other OS/400 objects. The OS/400 operating system automatically manages the allocation of disk space so that you do not need to. To back up information on iSeries, you back up logically (by library or directory), not physically (by disk unit).

To plan a backup strategy, you need to understand the logical location of your

Domino for iSeries databases and programs.

For more information, see “Libraries and directories for the Domino for iSeries product.”

Backup tips

For information about planning a backup strategy for your iSeries server, see the

Backup and Recovery book (SC41-5304-06). If you are new to the iSeries, also see the descriptions of using the Save menu and using the SAVxxx and RSTxxx commands. This book comes with your OS/400 software. It is also available in the iSeries supplemental manual library in the iSeries Information Center.

Here is some additional information that might be helpful in planning backup strategies for your Domino for iSeries servers:

•

Options 21, 22, and 23 from the Save menu place the system in a restricted state, which includes stopping all active subsystems with the End Subsystem

(ENDSBS) command. The ENDSBS command is not the preferred method for ending Domino servers because it might result in data loss or corruption.

Therefore, before you run option 21, 22, or 23 from the Save menu, end all of your Domino servers with the ENDDOMSVR command or by issuing the Quit server command at the Domino console for each server.

•

When you run an OS/400 save command with the SAVACT (save while active) option, the system does not save files that are open for write. From an OS/400 perspective, any Domino database that is in use is open for write. Therefore, to ensure that you completely save your Domino databases, make sure the databases are not open. Before saving your Domino databases, either end the

Domino servers or use the Drop All server command followed by the Dbcache

Flush server command.


Libraries and directories for the Domino for iSeries product

OS/400 libraries contain programs for the Domino for iSeries server product, programs that are available for your Domino developers to copy to their workstations, and customization information such as subsystem descriptions. The following table lists the Domino libraries:

Item

Domino for iSeries product

C APIs

C++ APIs

LotusScript Extensions

Objects common to all multi-version capable releases

Customization information (such as subsystem descriptions and job descriptions)

OS/400 Library

QDOMINOxxx

QNOTESAPI

QNOTESCPP

QNOTESLSKT

QNOTES

QUSRNOTES

Path for Library

/qsys.lib/qdominoxxx.lib

/qsys.lib/qnotesapi.lib

/qsys.lib/qnotescpp.lib

/qsys.lib/qnoteslskt.lib

/qsys.lib/qnotes.lib

/qsys.lib/qusrnotes.lib

where xxx corresponds to the release of your Domino server.

Directories in the iSeries integrated file system contain product information, customization files, and databases. The following table lists the Domino directories:

Item

Release specific product information

Common product information (symbolic link to Primary release)

Customization information

Directory for databases on the server

Path

/QIBM/ProdData/Lotus/DOMINOxxx

/QIBM/ProdData/Lotus/Notes

/QIBM/UserData/Lotus/Notes

Specified when you set up the server

(usually /NOTES/DATA) where xxx corresponds to the release of your Domino server.


Backing up Domino programs and product files

After you install the Domino for iSeries product, including its optional features, you should save a copy of the product offline. You should also save a copy of the product periodically; for example, when you update to a new release or apply fixes.

Following are two options for backing up the libraries and directories that contain the relatively static information for your Domino for iSeries server.

Note If your iSeries is already running other applications, you probably already use one of these options.

•

To back up your entire iSeries system, including your Domino programs, product files, and databases, use option 21 (Entire system) from the Save menu.

You access the Save menu by typing GO SAVE from a command line of an

OS/400 session.

•

To back up only product libraries and directories that contain information for iSeries licensed programs, including Domino for iSeries, use option 22 (System data only) from the Save menu. Option 22 saves the QDOMINOxxx libraries and the /QIBM/ProdData/Lotus/DOMINOxxx directory, where xxx corresponds to the release of Domino.

Backing up all Domino databases

Develop a plan to back up all Domino databases, including users’ mail databases and system databases, such as the Domino Directory.

When you configure a Domino server, you specify the directory for that server, such as /NOTES/DATA. By default, all the databases for the server are in that path. Your

Domino administrators might have the authority to place a Domino database in another path (by using an integrated file system command). Typically, end users cannot create Domino databases in any location except the default path for the server.

If you are responsible for backing up a Domino for iSeries server, you should develop a backup strategy that matches your policy for where information is stored.

Choose one of the following:

Limiting the location of Domino databases

Use a combination of policies and security to keep all Domino databases within the default directory (path) for the Domino server. With this approach, you need to back up only the data directory and the directory that contains customization information

(/QIBM/UserData/Lotus/Notes).

Following is an example of the steps to back up the data directory for your Domino for iSeries server and the directory with customization information. Substitute the name of your tape device for TAP01 and the name of your Domino server data directory for /NOTES/DATA.


1. Sign onto your iSeries using a user profile that has *JOBCTL and *SAVSYS special authorities.

2. To ensure that you get a complete copy of your server, stop the server before you start the save operation. Use the following command:

enddomsvr server(servername)

where servername is the actual name of your Domino server.

3. To back up the directories, use the following command. Substitute your directory name for /NOTES/DATA.

sav dev('/qsys.lib/tap01.devd') obj(('/notes/data/*')

('/QIBM/UserData/Lotus/Notes/*'))

Note If you already use option 21 or option 23 from the Save menu regularly, you do not need to back up your Domino server separately.

Backing up everything

With this approach, you assume that Domino databases might exist anywhere in the integrated file system (in either the root directory or the /QOpenSys directory).

Therefore, you need to back up the entire root directory and /QOpenSys directory.

Use any of the following methods:

•

Back up your entire system (option 21 from the Save menu).

•

Back up all user data (option 23 from the Save menu).

•

Use the SAV (Save Object) command to back up everything except the

QSYS.LIB file system, the QDLS file system, and directories that contain static program product information. Substitute your tape device name for TAP01.

sav dev('/qsys.lib/tap01.devd') obj(('/*') ('qsys.lib'

*omit) ('/qdls.lib' omit) ('/QIBM/ProdData' *omit)

('QOpenSys/QIBM/ProdData' *omit)) updhist(*yes)

Note When you use option 21 or 23 from the Save menu, the system automatically stops all activity (goes to a restricted state). When you use commands (instead of the Save menu) to back up your server information, you must stop the server before you back up. This ensures that the databases are in a known state for the backup operation. You can use the End Domino Server

(ENDDOMSVR) command to stop the server.


Backing up mail databases

This topic describes specifically how to back up mail from your Domino for iSeries server. If you already have a strategy for backing up all the user information from your Domino server, you probably do not need a separate procedure for backing up only mail. However, you might discover that your backup interval for your entire server is not frequent enough for e-mail because mail is so volatile.

Your Domino server stores mail in multiple databases:

•

The MAIL.BOX database on each server contains mail for the server to route to individual user mailboxes or to another server.

•

Each Lotus Notes user has an individual mail database. The name of the mail database is typically the user’s ID with the NSF extension. (The Domino administrator has the option to use different names for mail databases.) For example, the mail database for user GNELSON is GNELSON.NSF. Typically, all the individual mail databases are in a dedicated subdirectory, such as

/NOTES/DATA/MAIL.

To back up mail, do the following:


2. From a command line, use the following command to stop the Domino server:

enddomsvr server(servername)

where servername is the actual name of your Domino server.

To back up a database, the iSeries must be able to lock the database so that no changes occur during the backup operation. To successfully back up Notes mail, you will need to stop the Domino server that contains the mail databases.

3. Mount the appropriate backup tape in the tape device.

4. Use the Save Object (SAV) command to back up the mail databases. Following is an example. Substitute your server directory name for /NOTES/DATA.

Substitute your tape device name for TAP01.

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/mail/*.nsf')


Examples: Backing up mail from your Domino server

Following are examples of using the Save Object (SAV) command to back up mail from your Domino server. Substitute your server directory name for

/NOTES/DATA. Substitute your tape device name for TAP01.

•

To back up a specific database, such as the MAIL.BOX database, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/mail.box')

•

To back up all the files of a specific type in the MAIL subdirectory, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/mail/*.nsf')

•

To back up a specific user’s mail database, such as GNELSON’s mail database, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/mail/gnelson.nsf')

Notes about the examples:

1. To back up a database, the iSeries must be able to lock the database so that no changes occur during the backup operation. To successfully back up Notes mail, do one of the following before you use the SAV command:

•

Stop the Domino server that contains the mail databases. (Use the

ENDDOMSVR (End Domino Server) command to stop the server.)

•

Stop activity on the databases file by using drop all and dbcache flush.

However, with this method, any attempted mail delivery during the backup operation results in the mail being returned to the user with a message that the server is busy/in use.

2. To reduce the downtime of your server during backups, use clustered servers.

iSeries can support clustered servers on the same system.

Backing up specific databases

You might want to back up a specific Domino database to tape for several reasons.

For example:

•

To create a backup copy before you make programming changes or test a new agent.

•

To create an archive copy at the end of an accounting period.


To back up a specific database or group of databases from your Domino server, do the following:


2. Ensure that no one is using the database. You want a copy at a known point when no changes are occurring to the database.

3. Mount a tape for the backup operation.

4. Use the SAV (Save Object) command for the database. For example, to back up a database called CUSTINF.NSF in the /NOTES/DATA directory, use the following command. Substitute your tape device name for TAP01:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/custinf.nsf')

Examples: Backing up a specific Domino database

Following are examples for using the Save Object (SAV) command to back up specific Domino databases to tape. Substitute your server directory name for

/NOTES/DATA. Substitute your tape device name for TAP01.

•

To back up all the Domino databases in the DEPT57 subdirectory (folder), use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/dept57/*.nsf')

•

To back up the HRINFO database from the HRDPT directory, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/hrdpt/hrinfo.nsf')

•

To back up all the HR files (not in a specific subdirectory), use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/hr*.nsf')

Notes about the examples

1. To back up a database, the iSeries must be able to lock the database so that no changes occur during the backup operation. Either make sure that no one has the database open or stop the server for the backup operation.

2. To reduce the downtime of your server during backups, use clustered servers.



Backing up changed objects from your Domino for iSeries server

iSeries provides the capability to back up only objects that have changed either since a specific date and time or since the last backup operation. This type of backup capability is sometimes called an incremental backup. You might find a combination of complete backup and incremental backup particularly useful if your Domino server has many databases that do not change very often.

Strategies for incremental backup

Following are the two most common strategies for incremental backups:

•

Backing up changes since last full backup. With this strategy, you back up everything that has changed since you last backed up all the databases from your Domino server. For example, assume that you back up your entire server on Saturday night. On Sunday night, you would back up everything that has changed since Saturday night. On Monday night, you would back up everything that has changed since Saturday night. On Tuesday night, you would back up everything that has changed since Saturday night, and so on.

The advantage to this strategy is that it makes recovery simple. When you need to recover, you need to use only your tapes from your full backup and your tapes from your most recent incremental backup. The disadvantage to this strategy is that your backups grow larger (both in media usage and duration) each day until your next complete backup.

•

Backing up changes since the last incremental backup. With this strategy, you back up only objects that have changed since the most recent backup. For example, assume that you back up your entire server on Saturday night. On

Sunday night, you would back up everything that has changed since Saturday night. On Monday night, you back up everything that has changed since Sunday night. On Tuesday night, you back up everything that has changed since

Monday night, and so on.

The advantage to this strategy is that the size of your incremental backup is smaller (both in media usage and duration). The disadvantage is that recovery is more complex. When you need to recover, you need to use your tapes from your full backup and your tapes from each incremental backup.

Examples: Backing up changed objects from your Domino server

Following are examples for backing up changed objects from your Domino server.

Substitute your server directory name for /NOTES/DATA. Substitute your tape device name for TAP01.

Backing up all changes (since previous full backup)

To perform a nightly incremental backup of all changes that have occurred since that last full backup, do the following:


1. On Saturday evening, perform a complete backup (for example, by using option 23 from the Save menu). Make sure that you specify UPDHST(*YES) on the SAV command so that the system updates the object information with the time and day of the most recent backup.

2. On Sunday evening, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/*.*') chgperiod(*lastsave) updhst(*yes)

3. On Monday evening, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/*.*') chgperiod(*lastsave) updhst(*yes)

Continue using the same command every night until your next full backup.

Backing up one day’s changes

To perform a nightly incremental backup of what has changed since the previous incremental backup, you need to adjust the CHGPERIOD parameter each night.

Following is an example:

1. On Saturday evening at 8 PM, perform a complete backup (for example, by using option 23 from the Save menu). Make sure that you specify

UPDHST(*YES) on the SAV command so that the system updates the object information with the time and day of the most recent backup.

2. On Sunday evening, November 9 at 10 PM, use the following command:

sav dev('/qsys.lib/tap01.devd') obj('/notes/data/*.*') chgperiod('11/08/97' 200000) updhst(*yes)

3. On Monday evening, November 10 at 9 PM, use the following command:


4. On Tuesday evening, November 11 at 8 PM, use the following command:


5. Each evening, run the SAV command. Alter the Change Period parameter to the time and date of the previous backup.


•

To back up a database, the iSeries must be able to lock the database so that no changes occur during the backup operation. To successfully back up Domino databases, you must either ensure that no one is using the databases or stop the

Domino server that contains the databases. (Use the ENDDOMSVR (End

Domino Server) command to stop the server.)

•

To reduce the downtime of your server during backups, use clustered servers.



Recovery of Domino for iSeries

Domino for iSeries programs and product files reside in libraries in the QSYS.LIB

file system on your iSeries server. Domino databases reside in the integrated file system in a directory path that you specify when you configure your server. Your backup strategy for Domino for iSeries should include backing up both the libraries

(infrequently) and the database directories (frequently).

You might need to recover Domino for a variety of reasons, for example:

•

Damage to your server, such as fire or flooding

•

Hardware problems, such as a disk failure

Note iSeries provides disk protection options (mirrored protection and device parity protection) both to increase availability and to ensure that disk failures do not cause loss of data. You can find out more about disk protection in the

Backup and Recovery book (SC41-5304-06).

•

User or operator error, such as deleting a database or running a month-end procedure twice

Sometimes, you must recover your entire server. At other times, you must recover a specific directory. The following topics provide general information about recovery steps for Domino for iSeries:

•

Recovering an entire Domino server

•

Recovering Domino mail

•

Recovering Domino databases

•

Restoring changed objects to a Domino server

For complete procedures and considerations, see the Backup and Recovery book

(SC41-5304-06) and the Domino documentation.

Recovering an entire Domino for iSeries server

If you are faced with a system disaster, such as a site loss or the failure of an unprotected disk unit, you must recover (restore) your entire iSeries server from a backup. Because iSeries is a highly integrated system, you must recover objects in the correct sequence to rebuild the proper links between objects. The Backup and

Recovery book (SC41-5304-06) provides complete instructions for performing a full system recovery.

If you are faced with a problem that requires recovering only your Domino for iSeries server, not your entire iSeries server, you can use the Restore Object (RST) command to recover your Domino directories from tape. Following is an example of the steps:


1. Sign onto your iSeries using a user profile that has *SAVSYS and *JOBCTL special authority.

2. To make sure that no one is using the server that you plan to recover, stop the server. Use the End Domino Server (ENDDOMSVR) command.

3. Mount the tape that has the most recent backup copy of the directories for the server.

4. Use the appropriate restore (RST) command for your Domino directory. For example, if your Domino directory is /NOTES/DATA and your tape device is

TAP01, use the following command:

rst dev('qsys.lib/tap01.devd') obj('/notes/data/*')

This process restores the physical contents of the data directory for your server to your iSeries disk storage. Consult the Domino documentation for any special recovery activities that you might need to perform after you have restored the directories.

Recovering Domino Directories

If possible, you should recover both the Domino Directory and the iSeries system distribution directory from backup tapes that were created at the same time.

To recover the iSeries system distribution directory, use the following restore command:

rstobj obj(qaok*) savlib(qusrsys) objtype(*file) dev(tap01)


Recovering Domino mail

If you need to recover one or more mail databases from your backup tapes, use the

Restore Object (RST) command. Following is an example of the steps:

1. Sign onto your iSeries with a user profile that has *SAVSYS and *JOBCTL special authority.

2. Stop the server that contains the mail databases that you want to recover; for example, use the End Domino Server (ENDDOMSVR) command.

3. Mount the tape that has the most recent backup of the mail databases.

4. Use the appropriate Restore Object (RST) command for the mail databases that you want to recover. For example, to recover all the databases to the MAIL subdirectory from device TAP01, use the following command:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/mail/*')

Examples: Recovering Domino mail

The name of a user’s mail database is usually the user’s ID (short name) with the

.NSF extension. (The Domino administrator has the option to use different names for mail database files.)

•

To recover a specific user’s mail database, such as the mail database for user

GNELSON, use the RST command and specify the database name:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/mail/gnelson.nsf')

•

You can specify more than one file on the RST command. To recover mail databases for GNELSON, LSMITH, and JPETERS, use the following command:

rst dev('/qsys.lib/tap01.devd') obj(('/notes/data/mail/gnelson.nsf')

('/notes/data/mail/lsmith.nsf')('/notes/data/mail/jpeters.n

sf'))


•

You cannot restore over a database that is in use. All users must close the database before you can restore a backup copy.

•

All of the examples assume that the directory for your Domino server is

/NOTES/DATA.

•

Substitute the name of your iSeries tape device for TAP01.


Recovering Domino databases

You might need to recover a specific Domino database or a group of databases. Use the Restore Object (RST) command. Following is an example of the steps for recovering all the files to the HRDPT subdirectory:

1. Sign onto your iSeries using a user profile that has *SAVSYS and *JOBCTL special authority.

2. Stop the server that contains the databases that you want to recover. Use the

End Domino Server (ENDDOMSVR) command. (You can restore a database when the server is running. However, you need to make sure that no one is using the database. Stopping the server is the best way to ensure that no one is using the database.)

3. Mount the tape that has the most recent backup of the databases.

4. Use the appropriate Restore Object (RST) command for the mail files that you want to recover. For example, to recover all the files to the HRDPT subdirectory from device TAP01, use the following command:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/hrdpt/*.nsf')

Examples: Recovering Domino databases

In the examples, substitute your server directory for /NOTES/DATA. Substitute your tape device name for TAP01.

•

To recover a specific database named HRINFO to the HRDPT subdirectory

(folder), use the following:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/hrdpt/hrinfo.nsf')

•

To recover all the Domino databases to the CUSTSVC subdirectory, use the following:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/custsvc/*.nsf')

•

To recover all the Domino databases that have names beginning with INV to the main directory for your server, use the following:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/inv*.nsf')

Note You cannot restore over a database that is in use. All users must close the database before you can restore a backup copy. The best way to ensure that databases are not in use is to stop the server.


Recovering changed objects to a Domino for iSeries server

To reduce the length of your backup window, your backup strategy might include backing up only changed objects from your Domino server during the business week. When you need to use these backup tapes to recover, you must decide on your recovery sequence and determine the location of the most recent copy of each database.

Examples: Recovering changed objects to a Domino server

Following are examples of different recovery scenarios and an overview of the recovery steps for each. Substitute your server data directory for /NOTES/DATA.


Recovering all changed Domino objects from a cumulative backup

Assume that your strategy for backing up changed objects is cumulative (each night you back up everything that changed since the last complete backup). To recover your entire Domino data directory, do the following:


2. To ensure that no one is using the databases, stop the Domino server; for example, use the End Domino Server (ENDDOMSVR) command.

3. Locate the tapes from your most recent complete backup. Mount the correct tape in the tape unit.

4. To recover the entire Domino data directory, use the Restore Object (RST) command. For example,

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/*')

Substitute your Domino data directory for /NOTES/DATA and your tape device name for TAP01.

5. Locate and mount your most recent backup tapes (from backing up changed objects).

6. To recover all the changed objects on the tape (everything that has changed since your full backup), use the following command:




Recovering all changed Domino objects from a nightly backup

Assume that your strategy for backing up changed objects is nightly (each night you back up only objects that have changed since the previous night). To recover your entire Domino data directory, do the following:




4. To recover the entire Domino data directory, use the Restore Object (RST) command. For example,



5. Locate and mount your first backup tapes (from backing up changed objects).

For example, if you back up everything on Saturday night, locate your backup tapes from Sunday night.

6. To recover all the changed objects on the tape (everything that has changed since the previous night), use the following command:



7. Repeat steps 5 and 6 for each nightly backup tape until your directory is current. For example, if you are recovering on Thursday, you need to use the tapes for Monday, Tuesday, and Wednesday nights.

Recovering a specific Domino database from an incremental backup

To recover a specific database named HRINFO to the HRDPT subdirectory (folder), do the following:



3. Locate the most recent tape that has the database. Do one of the following:

•

Consult the log that the system creates during the save operation.

•

Use the Display Tape (DSPTAP) command to display the contents of the tape.

4. Mount the tape in the tape unit.


5. To recover the database, use the following command:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/hrdpt/hrinfo.nsf')


Recovering changed objects to a specific Domino subdirectory

To recover all the Domino databases to the CUSTSVC subdirectory, use the same approach that you use to recover the entire server. Do the following:




4. To recover the entire directory from the tapes from your last full backup, use the RST (Restore Object) command. For example, to recover objects in the

CUSTSVC subdirectory from the TAP01 device, use the following command:

rst dev('/qsys.lib/tap01.devd') obj('/notes/data/custsvc/*')

5. If your incremental backup tapes are cumulative, mount your most recent incremental backup tape. Use the same restore command (step 4) to recover the changes.

Otherwise, if your backup tapes are nightly, repeat this step for each incremental backup tape. Start with the oldest tape and work forward, using the

RST command from step 4.

About user-defined file systems and availability

Normally, all disk units attached to an iSeries server are treated as a single logical disk unit. The operating system places data across the disk units to optimize performance and disk utilization. However, an OS/400 administrator has the option to create logical groupings of disk units, called auxiliary storage pools or ASPs.

Auxiliary storage pools provide several possible benefits, for example:

•

ASPs provide the option for different strategies for backup and disk protection.

For example, you might have large history databases that do not change very often. By segregating them in a separate ASP, you can easily set up a less frequent backup schedule. You might also choose not to use RAID5 disk units for this ASP if availability of the information is not time-critical.

•

ASPs provide the option to isolate database journals from the databases both for protection from data loss and for performance.


If you want to place your Domino data directory in a user ASP, you need to create a user-defined file system (UDFS) to map the integrated file system directory to the correct ASP.

You can read more about ASPs and creating user-defined file systems in the Backup

and Recovery book (SC41-5304-06).

Configuring and using BRMS for Domino

BRMS is an IBM iSeries licensed program that is designed to help with your backup and recovery efforts. Domino for iSeries allows the configuration of a basic set of defaults for use with BRMS, enabling you to back up databases for your Domino server while the server is active. To use these functions, you must install the following on your iSeries server:

•

OS/400 V5R1 (5722SS1) or later

•

Backup Recovery and Media Services (5722BR1) or later

•

The latest PTFs available for your BRMS release

Note Backing up your Domino server databases should not replace your occasional complete system backups. For instructions on doing a complete system backup through BRMS, see the iSeries BRMS documentation, available through the Information Center at the following Web address: http://www.ibm.com/eserver/iseries/infocenter

To use BRMS to perform an online backup of your Domino database, you should understand the following concepts:

•

Media - Removable storage, such as a tape cartridge.

•

Media identifier - A name given to a physical piece of media.

•

Media class - A logical grouping of media with similar physical or logical characteristics, such as density.

•

Control group - A grouping of items (such as libraries or stream files) to back up and attributes associated with how to back them up.

•

Policies - A set of defaults that are commonly used (such as device and media class). The BRMS system policy contains general use defaults. The BRMS backup policy contains defaults related to backups.

Before you can back up Domino for iSeries, you need to create the BRMS components to enable you to back up your Domino databases while the server is active and to exclude Domino databases from other system backups. For more information, see “Configuring BRMS integration components” later in this chapter.


Performing an online backup of Domino databases

Using BRMS to perform an online backup of your Domino databases involves the following steps:

1. Determine the device and media class to use.

2. Add media to the media class scratch pool.

3. Start the backup.

Backing up database indexes

When you back up a Domino database via BRMS (using the SAVDOMBRM command), its index is not saved. If you want to back up the database index files, you need to save them using the method that you use to back up other files in the iSeries integrated file system, such as the SAV command. If you save both the database and index files at the same time and restore them both at the same time, the index should be up to date with the database. However, if a database with an index is restored to a previous version of the database and the index is not restored, the index may have inaccurate links. To ensure that indexed databases are accurate after a restore, rebuild the index.

Excluding Domino databases from your online backup

You may want to exclude Domino databases from your online backup. For example, you may not need to back up the Domino help databases (such as HELP.NSF). You can exclude Domino databases from your online backup by changing the control group for the Domino server to omit the databases by name.

Excluding Domino databases from other system backups

In addition to backing up your Domino databases, you should also use BRMS to back up the rest of your system so that you can recover all of your data through

BRMS. To allow your Domino databases to be used while you back up the rest of your system, you should exclude the Domino databases from the backup. To do this, you’ll need to change your backup control group to use the QDOMEXCL link list.


Recovering your Domino data

After a successful backup, BRMS will help you plan for a complete recovery of your system by allowing you to print a complete disaster recovery plan. To enable recovery of all your data, use BRMS to back up the rest of your system in addition to your Domino server databases. See the iSeries BRMS documentation for more information on performing a complete backup and recovery of your iSeries.

To recover Domino databases, you can perform one of following types of recovery:

•

Recover your entire system. Refer to the BRMS documentation for the steps to recover your entire system.

•

Recover all databases for all of your Domino servers.

•

Recover all databases for a specific Domino server.

•

Recover a single database.

Performance Considerations

Because of performance limitations of the tape media devices, Domino databases are packaged and saved in groups. By default, five databases are put in backup mode and are then saved. The changes that occurred to all five databases while being backed up are also saved along with the databases. The number of files in the group (the default is five) can be configured to optimize backup and recovery time for your Domino server.

Configuring BRMS integration components

To enable the BRMS integration feature for a server, the following components need to be created to enable backup using BRMS:

•

A control group for performing an online backup of the databases for a Domino server.

•

A BRMS link list to exclude Domino databases when backing up OS/400 directories.

•

A control group for performing an online backup of the databases for all

Domino servers. This control group is optional and is not needed if you have only one Domino server on your iSeries.

The following are example procedures for each situation.


Control group for online backup of databases for a Domino server

This control group will be defined to perform an online backup of all databases for a specific Domino server. You can use any name for the control group. However, we recommend that you use the name of the iSeries subsystem in which the Domino server runs. You can determine the subsystem name by entering the following

OS/400 command:

wrkdomsvr

In the following procedure, we represent the control group name by dominox.

Substitute the actual server subsystem name for dominox.

1. Type the following OS/400 command and press Enter:

go brms

2. Type a 2 at the command prompt and press Enter to select Backup.

3. On the Backup display, type a 1 and press Enter.

4. On the Backup Planning display, type a 2 and press Enter.

5. On the Work with Backup Control Groups display, type a 1 in the Opt column to create a control group.

6. Type dominox in the Control Group column and press Enter.

7. On the resulting display, enter the following sets of Seq values:

•

Type 10 in the Seq column, *exit in the Backup Items column, and *dftact in the Weekly Activity SMTWTFS column. Press Enter.

•


•


8. Position the cursor to the Seq 20 entry and press F10.

9. In the Command field, type savdombrm and press F4.

10. In the Server name field, type the name of your Domino server; for example, domserv1.

11. In the Control Group field, type the name that you specified in step 6; for example, dominox.

12. If desired, position the cursor to the Files to omit field and specify the location of objects that you want to omit (databases you do not want saved). You must specify the location of the objects as the directory path relative to the server data directory. For example, if you want to omit the file named mydb.nsf that is located in the server data directory /notes/data, type mydb.nsf in the Files to omit field, not /notes/data/mydb.nsf. You can use the wildcard character (*) in the object name.

13. Press Enter twice.


14. Press F3.

15. Select option 1 and press Enter to save and exit the session.

16. Press F3 four times.

BRMS link list to exclude Domino databases

Because Domino databases are backed up using other control groups created by the

BRMS integration feature, they should be excluded from backups of the rest of the iSeries integrated file system. This will allow your Domino server to remain active while the rest of the file system is backed up. You can define the QDOMEXCL link list to allow exclusion of Domino databases from backups of the rest of the file system. To create the QDOMEXCL link list, follow these steps:


go brms




5. On the Work with Backup Lists display, type a 1 in the Opt column to add a

Backup list, QDOMEXCL in the List Name column, *BKU in the Use column, and *LNK in the Type column.

6. Press Enter.

7. Type a text description, such as “All integrated file system objects except

Domino server databases” and press Enter.

8. Type a 2 next to the QDOMEXCL list name and press Enter.

9. Use sets of the Name field and Include or omit field to define the system objects in the list. For example:

•

Include all of the iSeries integrated file system. Type ’/*’ in one of the Name fields and type *INCLUDE in the associated Include or omit field.

•

Omit the QSYS.LIB file system. Type ’/QSYS.LIB’ in a Name field and type *OMIT in the associated Include or omit field.

•

Omit the QDLS file system. Type ’/QDLS’ in a Name field and type *OMIT in the associated Include or omit field.

•

Omit all of the file extensions for Domino databases (*.nt* and *.ns*). Use fully qualified path names to specify the location of these databases. For example, if you want to omit the *.ns* databases that are located in the server data directory at /notes/data, type ’/notes/data/*.ns*’ in the Name field.


You can now use this list in a control group instead of the *LINK special value. In

BRMS, *LINK means all objects in the iSeries integrated file system. If you are doing an online backup of Domino databases, you do not need to include them in a backup of the entire integrated file system. However, you should do a full system backup each week. This means using the *LINK value to include the entire integrated file system.

Control group for online backup of databases for all Domino servers (optional)

This control group will be defined to perform an online backup of all databases for all Domino servers. For the control group name, we use qdomino. You can use a different name.


go brms




5. On the Work with Control Groups display, type a 1 in the Opt column and type qdomino in the Control Group column.

6. Press Enter.

7. On the resulting display, enter the following sets of Seq values:

•


•

Type 20 in the Seq column, *exit in the Backup Items column, and *dftact in the Weekly Activity SMTWTFS column. Press Enter. This Seq entry will represent the first Domino server that you want to back up.

•

Type 30 in the Seq column, *exit in the Backup Items column, and *dftact in the Weekly Activity SMTWTFS column. Press Enter. This Seq entry will represent the second Domino server that you want to back up.

•

Add additional Seq entries until you have one entry for each Domino server that you want to back up. Type xx in the Seq column, where xx is a number such as 40 or 50. Like the previous Seq entries, type *exit in the Backup

Items column and *dftact in the Weekly Activity SMTWTFS column. Press

Enter after typing in the values for each Seq entry.

8. Position the cursor to the Seq 20 entry and press F10.

9. In the Command field, type savdombrm and press F4.

10. In the Server name field, type the name of your Domino server; for example, domserv1.

11. In the Control Group field, type the control group name you specified in step 5; for example, qdomino.


12. If desired, position the cursor on the Files to omit field and specify the location of objects that you want to omit (databases you do not want saved). You must specify the location of the objects as the directory path relative to the server data directory. For example, if you want to omit the file named mydb.nsf that is located in the server data directory at /server1/data, type mydb.nsf in the Files to omit field, not /server1/data/mydb.nsf. You can use the wildcard character

(*) in the object name.


14. Repeat steps 8 through 11 for each Seq entry that represents a Domino server that you want to back up. Specify the appropriate Domino server name and the control group name from step 5. Also specify any objects to omit.

15. Add a final Seq entry that has *exit in the Backup Items column and *dftact in the Weekly Activity SMTWTFS column, but does not invoke the

SAVDOMBRM command. That is, for this final Seq entry, skip steps 8 though 11.

16. Press F3.

17. Select option 1 and press Enter to save and exit the session.


Incremental online backup

BRMS has been enhanced to include incremental save and restore of Domino server files. This allows file changes since the previous backup or restore to be managed.

Determining the device and media class to use

During the installation process, BRMS chooses a default device based on the fastest and most automated tape drive attached to your system.

BRMS also creates media classes based upon the devices attached to your system.

For example, if you have a 6380 tape device attached to your system, media classes such as QIC2GB would be created (6380 uses a media format called *QIC2GB).

To review the system policy and to determine the default device and media class, follow these steps:


go brms

2. Type an 11 at the command prompt and press Enter.

3. On the Policy Administration display, type a 1 and press Enter.

4. On the System Policy display, type a 1 and press Enter.


5. On the Change System Policy display, look at the values in the Devices and

Media class fields. To use a different device or media class, see the instructions in the iSeries BRMS documentation.

6. Press F3 four times.

Adding media to the media class scratch pool

Adding media to a BRMS media class allows BRMS to use, track, and protect active data on the media. You should add pre-initialized media to BRMS by using the steps outlined in this section. Once media is added to a media class of available media,

BRMS will drive backup operations and use this media, requesting you to load tapes as necessary.

Note If your media is not pre-initialized, see the iSeries BRMS documentation for details on how to add existing media content information into the BRMS catalog of information.

It is important to have sufficient media enrolled in the media class before performing a backup operation. It is recommended that you enroll at least three pieces of media, for example three tapes. In determining the number of media to add, you should consider the capacity of your media and the size of your Domino server data.

To add media, use one of the following methods based on the type of device you have:

A tape library device is an enclosed unit with many pieces of media that allows for random access to any piece of media. If you will be backing up using a tape library device, perform the following steps:

1. Make sure that your media is in the automated tape library.


go brms

3. Type a 1 at the command prompt and press Enter.

4. On the Media Management display, type a 9 and press Enter.

5. On the Work with Media Libraries display, type an 8 and press Enter three times to work with the current inventory of the automated tape library.

6. Type a 1 next to the media to be added and press Enter.

7. Type the media class you recorded when you determined the device and media class from the system policy. See “Determining the device and media class to use” earlier in this chapter.

8. Press Enter twice.


9. Repeat steps 6 through 8 until you have enrolled the recommended number of media.

10. Press F3 three times.

Tip You can also use the Add Media Library Media to BRMS (ADDMLMBRM) command to perform this operation.

If you are not using a tape library device, you are backing up to a stand-alone device. Therefore, perform the following steps:

11. Type the following OS/400 command and press Enter:

go brms

12. Type a 1 at the command prompt and press Enter.

13. On the Media Management display, type a 2 and press Enter twice to work with the BRMS media inventory.

14. On the Work With Media display, type a 1 in the Opt column and press Enter.

15. Type the volume identifier from the media label and the media class that you recorded from the system policy. See “Determining the device and media class to use” earlier in this chapter.


17. Repeat steps 4 through 6 until you have enrolled the recommended number of media.


Tip You can also use the Add Media to BRMS (ADDMEDBRM) command to perform this operation.


Excluding databases from your online backup

The section, “Configuring BRMS Integration components,” described how to create a control group for your Domino for iSeries server. This control group can be used to back up all the Domino databases in the data directory for your Domino server on your iSeries. You can exclude databases from these backups by changing the control group entries. To change your control group entries, perform the following steps:


go brms


3. On the Backup display, type a 1.

4. On the Backup Planning display, type a 2.

5. Position the cursor in the Opt column next to the control group you want to change. To change the control group that is used to back up all your Domino servers, position the cursor next to the QDOMINO entry.

6. Type a 2 and press Enter to edit the entries.

7. Press F11.

8. Position the cursor on the line where the value for Exit command column starts with SAVDOMBRM and the value in the SERVER parameter is the same as your Domino server name.

9. Press F10.

10. Press F4.

11. Position the cursor to the Files to omit field and specify the location of objects that you want to omit (databases you do not want saved). You must specify the location of the objects as the directory path relative to the server data directory.

For example, if you want to omit the file named mydb.nsf that is located in the server data directory at /notes/data, type mydb.nsf in the Files to omit field, not

/notes/data/mydb.nsf. You can use the wildcard character (*) in the object name.


13. Press F3.

14. Press Enter.



Excluding databases from your system backup

The QDOMEXCL link list is designed to allow backup of the iSeries integrated file system excluding Domino databases. If you use the QDOMEXCL link list during your backup processing, your Domino databases will continue to be accessible while a backup of the rest of the integrated file system is being performed. To create a new control group that uses QDOMEXCL based on an existing control group, perform the following steps:


go brms


3. On the Backup display, type a 1.

4. On the Backup Planning display, type a 2.

5. Position the cursor in the Opt column next to the control group you want to use as the basis for the new control group,

6. Type a 3 and press Enter.

7. Type a name for the new control group and press Enter.

8. Position the cursor next to the newly created control group, type a 2, and press

Enter.

9. Note the sequence number value for the Backup Item listed as *LINK.

10. Type a value for the blank Seq field that is one greater than the sequence number noted in step 9. Type QDOMEXCL for the Backup Items field and

*LNK for the List Type field.

11. Position the cursor next to the Backup Item listed as *LINK and space over the sequence number.


13. Press F3.




Starting a backup

To start the online backup of all databases for your Domino server, load a tape and use the Start Backup BRMS command as follows:

strbkubrm ctlgrp(dominox) sbmjob(*no)

where dominox corresponds to the control group you created for a specific

Domino server.

During the backup processing, you may encounter certain errors that require user intervention, such as loading a tape. A message at the bottom of the screen may appear indicating that a message has been sent to the system operator for a reply.

While the cursor is on any OS/400 message text, you can press F1 to see more information about the message.

The processing time of the backup operation depends on system processor size, device capabilities, amount of data being saved, and activity associated with your

Domino server.

During the backup and recovery process, BRMS for Domino creates a subdirectory in the server’s data directory called “brms” in which it stores temporary files

(*.brmschgs files). These files store changes made to a database that occurred while the database was being saved or backed up. These files were previously stored in the same directory as their associated database.

When the backup operation is complete, review the job log to make sure that the backup was successful. To display the job log, type the following OS/400 command and press Enter:

dspjoblog

On the display, press F10 and page up to see the details of any messages logged during backup processing.

To see the BRMS catalog of what has been backed up, follow these steps:


go brms



4. On the Display Backup Activity display, type a 3 and press Enter.

5. On the Display Backup History display, type a 1 and press Enter three times to see the contents of your backup media.


6. Press F3 five times.

Note When you back up an integrated file system object, such as a Domino database, the object will appear as a saved item of *LINK.

Tip You can also use the Work with Media Information (WRKMEDIBRM) command to perform this operation.

Recovering all the databases for all your Domino servers

Use the Start Recovery using BRM (STRRCYBRM) command to recover all databases in the data directories of all Domino servers:


strrcybrm option(*ctlgrp) action(*restore) ctlgrp(qdomino)

2. Type a 1 next to the items matching the version of backup that you want to restore. Use F16 to select all items. A saved item will appear for each database saved.

Note The order in which you restore files during a recovery is important.

Because the backup of Domino databases can happen while the server is active, the changes that occur to the database while it is being saved are saved separately and need to be restored to the database when it is recovered. To accomplish the complete recovery of the database, the Domino APIs are used.

In order for these APIs to be used, certain conditions and files must exist. For example, the NOTES.INI file must be present and available and the server data directory must be valid. If the server data directory is damaged or non-database files are missing, restore the non-database files first before trying to restore

Domino databases. Non-database files are saved along with other files in the iSeries integrated file system.

Recovering all the databases for a specific Domino server

Perform the following steps to recover all databases for a specific Domino server:


strrcybrm option(*ctlgrp) action(*restore) ctlgrp(control-group-name)

For control-group-name, substitute the name of the control group (such as dominox) that you created for the Domino server.

2. Type a 1 next to the items matching the version of backup that you want to restore. Use F16 to select all items. A saved item will appear for each database saved.


Recovering a single database

Use the Restore Object using BRM (RSTBRM) command to recover a specific

Domino database through BRMS. In this command, you must provide the name of the iSeries device, the name of the database you want to restore, and the path to the

OS/400 directory where you want to restore the database. For example, to recover the catalog.nsf database in the /notes/data directory, assuming a device of tap01, type the following OS/400 command and press Enter:

rstbrm dev(tap01) obj('/notes/data/catalog.nsf')

When the recovery operation is complete, review the job log to make sure that the database was successfully recovered. To display the job log, type the following

OS/400 command and press Enter:

dspjoblog

On the display, press F10 and page up to see the details of any messages logged during recovery processing.

Note Multiple objects may be associated with a Domino database when it is backed up while online; therefore, multiple messages may appear during recovery.

Performance considerations and configuration options

Because of performance impacts of writing individual Domino databases to physical devices, such as tape, the databases are backed up in groups (5 is the default). You can change this group value by adding the following entry in the NOTES.INI file for the server:

SAVDOMBRM_FILES_IN_GROUP=X

where X is the number of files to group in one BRMS package.

As you increase this number, your Domino server is backed up more quickly.

However, all databases in the group will be journaled during the backup, with the changes backed up separately. Because all the databases in the group are journaled until all databases in the group are backed up, the time during which changes to the databases can occur is increased and the size of the changes backed up will increase.

When the databases are recovered, the changes to the database that occurred during the backup will be reapplied. This process takes longer as the number of changes increases.


If your server is being backed up during heavy server usage, you will want to keep this group value relatively small (3 to 7), so that fewer changes occur to the database during the backup operation. As a result, recovery of the database can occur in a reasonable amount of time.

If your server is being backed up during off hours when server use is low, you can set the group value higher (10 to 20 or even higher) to speed up the backup operation, while keeping the recovery time reasonable. The maximum group value is 120.

BRMS restriction

The following restriction applies when using the Domino BRMS support.

•

Domino BRMS support does not save Domino database files residing in a

“link” subdirectory under the server data directory. Link subdirectories can be created via Domino Administration by selecting Tools -> Folders -> New

Link.


Chapter 19

Setting Up Remote LAN Services

The remote LAN service allows a Domino server to communicate with a remote

Domino server through phone lines. Of course, both servers must be connected to the phone lines through modems. You can use a remote LAN service to perform tasks such as remote Domino server replication or mail routing between two

Domino servers. This capability does not affect a remote connection between a

Notes client and a Domino server.

Setting up a remote LAN service for iSeries is similar to Domino in a Windows environment. You need to perform the following tasks:

•

Create the PPP profiles that define the connections for the remote LAN service.

•

Add a Connection document in the Domino Directory for the Domino server on the calling system.

•

Add a Server document in the Domino Directory for the Domino server on the calling system.

For more information on setting up a remote LAN service, see the Domino administration documentation or the Lotus Domino Administrator 6 Help database

(HELP65_ADMIN.NSF).

iSeries server requirements for remote LAN service

To use a remote LAN service with Domino 6, your iSeries server must have the following hardware and software:

Hardware

•

2629 IOP

•

2699 IOA

•

2720 PCI WAN/Twinaxial IOA

•

2721 PCI Two-line WAN IOA

•

Modems

•

Modem cables

Chapter 19: Setting Up Remote LAN Services 163

Software

•

OS/400 Version 5 Release 1 or later with the latest cumulative PTF package applied.

• iSeries Access for Windows, 5722XW1 Version 5 Release 1 or later. You use iSeries Navigator in iSeries Access to create the Point-to-Point Protocol (PPP) profiles.

Creating a PPP profile for remote LAN service

iSeries supports Dial on Demand, which is a function that allows the use of a specific TCP/IP route to signal OS/400 to initiate a dial connection over that route automatically. Domino for iSeries is not enabled to use this feature. The Domino

Dialup Network capability is supported using PPP dial connections.

Use iSeries Navigator on a Windows workstation to create the PPP connection profiles:

•

Create a *DIAL profile on your iSeries server that is the calling system. The remote LAN service will start the *DIAL connection.

•

If an iSeries server is the receiving system, create an *ANS profile on that iSeries. You can also use iSeries Navigator to start the *ANS connection.

If an iSeries server is both a calling system and a receiving system, create both a

*DIAL profile and an *ANS profile. Here are procedures for using iSeries

Navigator to create a *DIAL profile and an *ANS profile. For other details on creating a profile, see the iSeries Access help.

Creating the *DIAL profile

To create the *DIAL profile using iSeries Navigator, follow these steps:

1. Open the iSeries server where you will create the PPP profile.


3. Click Remote Access Services.

4. Right-click Originator Connection Profiles and select New Profile.

5. On the New Point-to-Point Connection Profile Setup dialog, make sure PPP is selected and the Operating Mode is set to Dial and click OK.

6. On the New Point-to-Point Profile Properties dialog, specify a name and description of this profile on the General tab.

7. On the Connection tab, specify a Line name, and click Add to specify a phone number of the remote system. If you want to allow this line to both dial and answer, click the check box next to Enable multilink protocol and fill in the appropriate fields in the resulting dialog.


8. On the DNS tab, choose Dynamically assign for both the Local IP address and the Remote IP address. On most systems, the answering system assigns an IP address to an incoming call.

9. If dialing into a Windows NT system, click the Authentication tab and make the following selections:

•

Click Allow the remote system to verify the identity of this iSeries.

•

Click Require unencrypted password (PAP).

•

Specify the User name and Password of a user on the Windows NT system: for example, the Administrator Password.

10. Click OK to create the *DIAL profile.

Creating the *ANS profile

To create the *ANS profile using iSeries Navigator, follow these steps:

1. Open the iSeries server where you will create the PPP profile.


3. Click Remote Access Services.

4. Right-click Receiver Connection Profiles and select New Profile.

5. On the New Point-to-Point Connection Profile Setup dialog, make sure PPP is selected and the Operating Mode is set to Answer and click OK.

6. On the New Point-to-Point Profile Properties dialog, specify a name and description of this profile on the General tab.

7. On the TCP/IP Settings tab, specify an IP address for both the Local IP address and the Remote IP address. For example, specify 199.xx.xx.1 and 199.xx.xx.2.

8. Click OK to create the *ANS profile.

Starting the *ANS profile

Once you have created a PPP profile using iSeries Navigator, you can start it through iSeries Navigator by right-clicking the profile and selecting Start.

Adding the Connection document for remote LAN service

Use the Domino Administrator client on your workstation to add the Connection document for the calling server:

1. From the Notes workspace, choose File -> Tools -> Server Administration.

2. When the Domino Administrator client opens, click the Configuration tab.

3. Click Server.

4. Click Connections.

5. Click the Add Connection button.


6. Specify the values shown in the table below.

Note The login name and password are ignored by the remote LAN program on iSeries. The system administrator must set up the profiles with the correct user information (usually none) to ensure security of the system. Domino has built-in security which ensures that users must have a proper ID to access the server.

7. Enable or Disable Mail Routing and Replication for this connection.

If the Mail Routing and Replication is enabled, the Domino server automatically loads LIBRAS.SRVPGM. Once loaded, this program tries to connect to the remote system using the *DIAL profile name that is specified for the Remote connection name in the Connection document.

Note If you want to set up a schedule, make sure you set the Schedule field to

ENABLED in the Scheduled Connection section.


Entry

Connection type:

Remote LAN port

Source server:

Source domain:

Destination server name:

Destination domain name:

Choose a service type:

Remote LAN service configuration:

Remote connection name:

Login name:

Password:

Phone number:

Optional network address:

Value

Remote LAN service

TCPIP

Local Domino server name (for example,

Server1)

Local Domino domain name (for example,

Acme1)

Remote Domino server name (for example,

Server2)

Remote Domino domain name (for example,

Acme2)

Microsoft Remote Access Service (RAS)

To see the service types, click Choose a Service

Type.

To see the configuration fields, click Modify

Remote LAN Service Configuration.

Name of *DIAL profile you created

Ignored

Ignored

Phone number of remote system (overrides the phone number in the *DIAL profile if it is different)

IP address of remote system (for example,

199.xx.xx.5)


Adding a Server document for remote LAN service

To add a Server document for the remote server in the Domino Directory of the calling server using the Domino Administrator client, follow these steps:

1. Click the Configuration tab.

2. Click Server.

3. Click All Server Documents.

4. Click the Add Server Document button.

5. Choose Create -> Server -> Server.

6. Specify the server settings for a remote server. Make sure you provide information for the Network Configuration. For an example of the Network

Configuration settings, see the table below.


Port

TCPIP

Notes Network

NETWORK1

Net Address

199.xx.xx.4

Enabled

ENABLED

Remote LAN service errors

The Domino console shows any errors that occur during connection. The errors begin with:

RAS 400: xxx.


Chapter 20

Integrating iSeries Collection Services With Domino

A new feature available when using Domino 6 and OS/400 V5R2 is the ability to integrate Domino with the iSeries Collection Services. This service can run continuously and store broad statistics about your iSeries server performance. By integrating this service with Domino, you can store Domino statistics within this system repository.

You can configure the service to store Domino statistics over days or even months.

The data can then be exported to DB2 files and cross referenced with other

Collection Services data such as CPU use or disk use.

A pre-defined set of Domino statistics is stored in Collection Services. This pre-defined set was determined to be the most useful set of statistics during times of problem determination or problem prevention. The complete set of Domino statistics is available through new APIs in V5R2, or by running the following command from the Domino console:

show stat

For more information and examples on using this data, see the Domino for iSeries Application Development Guide (DOMAPPDEV.NSF).

When you install or upgrade to Domino 6, the new COLSRV400 addin task is automatically added to the ServerTasks parameter in the NOTES.INI file. It is used to gather statistics for that Domino server as required for Collection Services. When

Collection Services is not running or is not set up to collect Domino statistics, the addin task does nothing. To completely disable this feature from a particular

Domino server, the COLSRV400 task can be removed from the ServerTasks entry in that Domino server’s NOTES.INI file. However, it is recommended that this is left in the NOTES.INI file.

Note If Domino 6 is running with OS/400 V5R1, COLSRV400 will end shortly after it starts, since this service is not supported with V5R1.

For more information on iSeries Collection Services, see the iSeries Information

Center for V5R2 at the following Web address, and click Systems Management ->

Performance -> Applications for Performance Management -> Collection

Services: http://www.ibm.com/eserver/iseries/infocenter

Chapter 20: Integrating iSeries Collection Services With Domino 169

Starting Domino Collection Services

To start the Domino Collection Services, follow these steps:


2. Open the iSeries server where you configured Domino.


4. Right-click Collection Services and select Start Collecting.

Stopping Domino Collection Services

To stop the Domino Collection Services, follow these steps:




4. Right-click Collection Services and select Stop Collecting.

Domino Collection Services properties

To view the Domino Collection Services properties, follow these steps:




4. Right-click Collection Services and select Properties.

5. On the General tab, specify the collection interval and a time for the recycle.

The default settings will collect data every 5 minutes, and create a collection object every day at 12 AM.

6. On the Data to Collect tab, make sure Domino is listed and selected to be collected at the interval you want. The default is every 5 minutes.

Exporting and viewing the statistics

To export the statistics to a DB2 file for viewing, follow these steps:




4. Click Collection Services.

5. In the right pane, right-click a Collection Name with the Cycled status and select Create Database Files now.


6. You will be prompted to choose a location for creating the database files, the categories you want to export from, and the time interval to export from. In the

Data to include field, make sure to at least select Domino Collection Services.

You can now use your favorite DB2 query tool to view the data. The file

QAPMDOMINO will contain the Domino data. An example query of “select * from qpfrdata/QAPMDOMINO” would show something similar to the following:

Collected Statistics

The following Domino statistics are collected by Collection Services:

Note Data Types: C(x) = Character (characters), B(x,y) = Binary (Digits, Decimal

Places), PD(x,y) = Packed Decimal (Digits, Decimal Places)

Field Name

ITMNUM

DTETIM

INTSEC

DTECEN

DMSUBS

DMJNAM

DMJUSR

DMJNBR

DMSRVN

DMSSDT

DMDBPM

DMDBPP

Description

Interval number: the nth sample database interval based on the start time specified in the CRTPFRDTA command.

Interval date (yymmdd) and time (hhmmss): The date and time of the sample interval.

Elapsed interval seconds: The number of seconds since the last sample interval.

Century digit: where 0 indicates 19XX and 1 indicates 20XX.

Server Subsystem

Server job name

Server job user

Server job number

Server Name (first 25 characters if the name is longer than this field)

Server start date time (yyyymmddhhmmss):

Database.BufferPool.Maximum.Megabytes: The configured maximum size for database control pools that may be used.

Database.BufferPool.Peak.Megabytes:Maximum amount of the buffer pool that has been used by

Domino over the life of the server.

Data Type

PD (5,0)

C (12)

PD (7,0)

C (1)

C (10)

C (10)

C (10)

C (6)

C (12)

C (14)

B (9,0)

B (9,0)

continued


Field Name

DMDBPR

DMDBCH

DMDBCL

DMNLCH

DMNLCL

DMASPN

DMASPU

DMASPB

DMTRNS

DMUSRO

DMUSRP

DMUSRT

DMMLCP

Description

Database.Database.BufferPool.PerCentReadsInBuffer:

Percentage of database reads present in buffer pool.

Database.DbCache.Hits: Number of hits to the database cache.

Database.DbCache.Lookups: Number of lookups to the database cache.

Database.NAMELookupCacheHits: Number of cache hits when doing name lookups in the server’s name and address book.

Database.NAMELookupCacheLookups: Number of lookups in the server’s name and address book.

Platform.LogicalDisk.1.AuxStoragePool: The number of the Auxilery Storage Pool that includes the Domino data directory.

Platform.LogicalDisk.1.PctUsed: Percent of total disk space used in the ASP that includes the Domino data directory.

This metric is calculated by the server and is based on an internal sample interval as configured for the server.

Platform.LogicalDisk.1.PctUtil: Percent of time the drives are busy reading or writing in the ASP that includes the Domino data directory.

This metric is calculated by the server and is based on an internal sample interval as configured for the server.

Server.Trans.Total: Number of transactions

Server.Users: Number of users with open sessions on the server. (this is the current value at time data was sampled)

Server.Users.Peak: Peak number of concurrent users since server was started.

Server.Users.Peak.Time: Time that last peak users occurred (YYYYMMDDHHMMSS).

Mail.TotalPending: Number of outbound mail messages in this server’s MAIL.BOX waiting to be processed by the Domino Router job. Mail will be pending until the Router job wakes up and moves outgoing mail from MAIL.BOX to the destination mail servers. If a mail server cannot be contacted, the message will remain pending in MAIL.BOX (this is the current value at the time data was sampled).

Data Type

B (5,2)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (4,0)

B (5,2)

B (5,2)

B (18,0)

B (9,0)

B (9,0)

C (14)

B (9,0)

continued


Field Name

DMMLWR

DMMLBX

DMCMCD

DMCMDD

DMCMED

DMCMOA

DMCMOB

DMCMOD

DMCMOF

DMCMOI

DMCMOV

DMCMSD

DMCMTU

DMRQ1M

DMNPT1

DMNBR1

Description

Mail.WaitingRecipients: Number of inbound mail messages in this server’s MAIL.BOX waiting to be processed by the Domino Router job. Mail will be waiting until the Router job wakes up and moves incoming mail from MAIL.BOX into user mail files

(this is the current value at time data was sampled).

Mail.Delivered: Combined number of inbound and outbound mail messages placed into this server’s

MAIL.BOX.

Domino.Command.CreateDocument: Count of

’CreateDocument’ URLs that have come into the server.

Domino.Command.DeleteDocument: Count of

’DeleteDocument’ URLs that have come into the server.

Domino.Command.EditDocument: Count of

’EditDocument’ URLs that have come into the server.

Domino.Command.OpenAgent: Count of ’OpenAgent’

URLs that have come into the server.

Domino.Command.OpenDatabase: Count of

’OpenDatabase’ URLs that have come into the server.

Domino.Command.OpenDocument: Count of

’OpenDocument’ URLs that have come into the server.

Domino.Command.OpenForm: Count of ’OpenForm’


Domino.Command.OpenImageResource: Count of

’OpenImageResource’ URLs that have come into the server.

Domino.Command.OpenView: Count of ’OpenView’


Domino.Command.SaveDocument: Count of

’SaveDocument’ URLs that have come into the server.

Domino.Command.Total: Count of all URLs that have come into the server.

Domino.Requests.Per1Minute.Total: Total requests over the past minute. Value as recorded at sample time.

NET.*.Port 1: Domino port (1 of 4) for which data is being reported.

NET.*.BytesReceived 1: Number of network bytes received for this port.

Data Type

B (9,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (18,0)

B (9,0)

C (32)

B (18,0)

continued


Field Name

DMNBS1

DMNSI1

DMNSO1

DMN*

Description

NET.*.BytesSent 1: Number of network bytes sent for this port.

NET.*.SessionsEstablished.Incoming 1: Number of

Incoming sessions established for this port.

NET.*.SessionsEstablished.Outgoing 1: Number of

Outgoing sessions established for this port.

The above 5 fields are repeated for ports 2, 3, and 4.

Data Type

B (18,0)

B (9,0)

B (9,0)


Chapter 21

Using National Language Versions of Domino

With Domino 6 for iSeries, fully translated versions of the product are not available.

Instead, to deploy Domino in a language other than English, you must first install and configure the English version of Domino and then add the translated language objects from the Language Pack CD-ROM.

A new feature with Domino 6 is the ability to deploy more than one language on a

Domino server or have Domino servers with differing languages through the use of a language pack and multi-lingual database support. For additional information on this type of environment, see the readme.txt file on the Language Pack CD-ROM.

Although the CL commands, menus, panels, and messages are not translated for

Domino 6, the iSeries Navigator plug-in interface is translated into Brazilian

Portuguese, French, Italian, German, Japanese, Korean, Simplified Chinese,

Traditional Chinese, and Spanish. For all other languages, the plug-in will default to

English. The translated interfaces are installed as part of the Language Pack installation process.

Using other languages on English versions of Domino

To enter and display other languages on English versions of Domino for iSeries, you need to specify that all locale-specific job attributes should be picked up from the locale of the language, by following these steps:

1. Stop the Domino server.

2. Change the locale value of the QNOTES user profile that is used to run Domino tasks (jobs). The locale name is /QSYS.LIB/xxxx.locale where xxxx.locale is the value specified in the third column of the table below.

Use the OS/400 CHGUSRPRF command to change the locale value. For example, to set the locale for German, use the following command:

chgusrprf qnotes locale('/qsys.lib/de_de.locale') setjobatr(*ccsid *datfmt *datsep *decfmt *srtseq *timsep)

Note You may receive an informational message in your job log indicating that the job attribute for sort sequence (*srtseq) was not set for the locale. This will not affect the behavior of your server, and can be ignored.

Chapter 21: Using National Language Versions of Domino 175

To enter and display text in:

Albanian

Arabic

Belgian English

Belgian French

Belgian French (Euro)

Bulgarian

Canadian French (MNCS)

Chinese, Simplified

Chinese, Traditional

Croatian

Czech

Danish

Dutch

Dutch (Euro)

Dutch (MNCS)

Dutch (MNCS - Euro)

English (UK)

English (US)

Estonian

Finnish

Finnish (Euro)

French (Euro)

French (France)

French (MNCS)

German (Euro)

German (Germany)

German (MNCS)

Greek

Hebrew

Hungarian

Icelandic

Italian (Euro)

Italian (Italy)

Japanese (Latin)

Korean

Latvian

Lithuanian

Macedonian

Norwegian

Polish

Portuguese (Brazil)

Portuguese (Euro)

Default locale

For the English version of Domino for iSeries, the default locale is set to the value listed for “English (US).”

870

277

37

1140

500

1148

285

37

1122

278

1143

1147

297

500

1141

273

500

875

424

870

871

1144

280

5035

933

1112

1112

1025

277

870

37

1140

Using CCSID:

500

420

500

500

1148

1025

500

935

937

870

Change QNOTES locale to:

SQ_AL.LOCALE

AR_AA.LOCALE

EN_BE.LOCALE

FR_BE.LOCALE

FR_BE_E.LOCALE

BG_BG_L.LOCALE

FR_CA.LOCALE

ZH_CN.LOCALE

ZH_TW.LOCALE

HR_HR.LOCALE

CS_CZ.LOCALE

DA_DK.LOCALE

NL_NL.LOCALE

NL_NL_E.LOCALE

NL_BE.LOCALE

NL_BE_E.LOCALE

EN_GB.LOCALE

EN_US.LOCALE

ET_EE.LOCALE

FI_FI.LOCALE

FI_FI_E.LOCALE

FR_FR_E.LOCALE

FR_FR.LOCALE

FR_CH_L.LOCALE

DE_DE_E.LOCALE

DE_DE.LOCALE

DE_CH_L.LOCALE

EL_GR.LOCALE

IW_IL.LOCALE

HU_HU.LOCALE

IS_IS.LOCALE

IT_IT_E.LOCALE

IT_IT.LOCALE

JA_5035.LOCALE

KO_KR.LOCALE

LV_LV.LOCALE

LT_LT.LOCALE

MK_MK_L.LOCALE

NO_NO.LOCALE

PL_PL.LOCALE

PT_BR.LOCALE

PT_PT_E.LOCALE

continued


To enter and display text in:

Portuguese (Portugal)

Romanian

Russian

Serbian (Cyrillic)

Serbian (Latin)

Slovak

Slovene

Spanish

Spanish (Euro)

Swedish

Thai

Turkish

Ukrain

870

284

1145

278

838

1026

1025

Using CCSID:

37

870

1025

1025

870

870

Change QNOTES locale to:

PT_PT.LOCALE

RO_RO.LOCALE

RU_RU.LOCALE

SR_SP_L.LOCALE

SH_SP.LOCALE

SK_SK.LOCALE

SL_SI.LOCALE

ES_ES.LOCALE

ES_ES_E.LOCALE

SV_SE.LOCALE

TH_TH.LOCALE

TR_TR.LOCALE

UK_UA.LOCALE

Language dictionary files

The language dictionary files are used for spell-checking within Notes and Domino.

The English version of Domino for iSeries installs the following language dictionary files.

• canadien.dic

• uk.dic

• us.dic

• wpdic.dic

Domino for iSeries installs these files in the product directory

/QIBM/ProdData/Lotus/Notes/shared/<dict-name>.dic along with symbolic links to the dictionary files in each server’s data directory:

Additional dictionary files are contained in the dictions.exe or dictionaries.exe file which may be obtained from the \APPS\DICTIONARIES directory of the Notes or

Notes/Domino Designer CD-ROM.

If you want to use one of the dictionary files listed in the table below and find that it has not been installed automatically by Domino, decompress the contents of the self-extracting file to a temporary directory on your PC’s hard drive. End your

Domino server(s) and then transfer the dictionary file(s) using FTP (or another file transfer method) to your Domino server’s data directory. The owner of the file should be changed to QNOTES as shown:

CHGOWN OBJ('<server-data-directory-path>'/<dict-name>.dic')

NEWOWN(QNOTES)


The dictionary file must be added to the data directory of each server that should have access to the dictionary. Then restart your Domino server(s).

As always, if you add dictionary files to customize your Domino installation, you should save (back up) your Domino server(s) after the dictionary file(s) have been added.

If spell check for International languages does not work, check for the following conditions:

•

Ensure you have the appropriate language dictionaries in either the product directory (with a SYMBOLIC link in your server’s data directory for dictionaries installed by Domino) or each server’s data directory (for dictionaries installed manually).

•

Check your International User Preferences (choose File -> Preferences -> User

Preferences -> International) to ensure you are using the correct international spelling dictionary.

Language

Afrikaans

Arabic

Catalan

Czech

Danish

Dutch

Dutch Belgian

Dutch Preferred

English (Australia)

English (Canada)

English (Caribbean)

English (Jamaica)

English (New Zealand)

English (United States)

English (Ireland)

English (South Africa)

English (United Kingdom)

Finnish

French (Belgium)

French (Luxembourg)

French (Standard)

French (Switzerland)

French (Canada)

German (Austria)

German (Liechtenstein)

German (Luxembourg)

German (Standard)

German (Reform)

Dictionary File Name

AFRIKAAN.DIC

ARABIC.DIC

CATALA.DIC

CZECH.DIC

DANSK.DIC

NEDERLND.DIC

NEDPLUS.DIC

AUS.DIC

US.DIC

UK.DIC

SUOMI.DIC

FRANCAIS.DIC

CANADIEN.DIC

DEUTSCH.DIC

DEUTSCH2.DIC

continued


Language

German (Switzerland)

Hebrew

Hungarian

Icelandic

Italian (Standard)

Italian (Switzerland)

Medical (American)

Medical (British)

Medical (British IZE)

Norwegian (Bokmal)

Norwegian (Nynorsk)

Polish

Portuguese (Brazil)

Portuguese (Standard)

Spanish

Spanish (Argentina)

Spanish (Bolivia)

Spanish (Chile)

Spanish (Colombia)

Spanish (Costa Rica)

Spanish (Dominican Republic)

Spanish (Equador)

Spanish (Guatemala)

Spanish (Mexico)

Spanish (Modern Sort)

Spanish (Panama)

Spanish (Paraguay)

Spanish (Peru)

Spanish (Uruguay)

Spanish (Venezuela)

Swedish

Turkish

Dictionary File Name

DSCHWEIZ.DIC

HEBREW.DIC

MAGYAR.DIC

ISLENSK.DIC

ITALIANO.DIC

US.MED

NORBOK.DIC

NORNYN.DIC

POLSKA.DIC

BRASIL.DIC

PORTUGAL.DIC

ESPANA.DIC

SVENSK.DIC

TURKIYE.DIC

Changing the date and time formats and separators

International users may need to add the following entries into the NOTES.INI file to customize how Domino displays the date and time format and separators.

Date format

The English version of Domino sets the date order to MDY (Month Day Year) and sets the date separator to a “/” (forward slash).


To override the default date order, specify one of the following in the NOTES.INI

file:

dateorder=DMY dateorder=YMD dateorder=MDY

To override the default date separator, specify:

dateseparator=x

where x is any character. For example, to set the date separator to a “.” (period), specify:

dateseparator=.

Time format

The English version of Domino sets the time format to a 24-hour clock and sets the time separator to a “:” (colon). Note that this is different from Domino R5, in which the default time format was a 12-hour clock.

To override the default time format, specify one of the following in the NOTES.INI

file:

ClockType = 24_HOUR

ClockType = 12_HOUR

To override the default time separator, specify the following:

timeseparator=x

where x is any character. For example, to set the time separator to a “.” (period), specify:

timeseparator=.

Installing the translated Domino plug-in for iSeries Navigator

Installing the translated Domino Plug-in for iSeries Navigator allows you to view the Domino GUI components in the same language as your translated iSeries

Navigator interface. Since the plug-in ships with Domino for iSeries rather than with iSeries Access for Windows (previously called Client Access in OS/400 V5R1), the

Domino plug-in must be installed from an iSeries server on which Domino has been installed.

If you want the Domino plug-in to be in a translated language, you must add that corresponding language pack to your Domino base code, otherwise you will be using the English Domino plug-in.


To be able to install and use the Domino plug-in in a translated version, the iSeries

Navigator code must be installed for the same language as Domino for iSeries.

Language feature codes available for the Domino plug-in for iSeries

The iSeries Navigator Domino plug-in is translated into the languages shown in the following table. These are the languages for which a translated version of the

Domino plug-in for iSeries Navigator exists and works with the iSeries Navigator of that OS/400 national language version.Only the OS/400 national language versions listed in this table provide translated Domino plug-in support for iSeries Navigator.

Language

Arabic

Brazilian Portuguese

Iberian Portuguese

Czech

Danish

Dutch

English

Finnish

French

German

Greek

Hebrew

Hungarian

Italian

Japanese DBCS

Korean

Norwegian

Polish

Russian

Simplified Chinese DBCS

Traditional Chinese DBCS

Spanish

Swedish

Turkish

Thai

2959

2961

2976

2932

2962

2986

2933

2978

2979

2989

2987

2931

2937

2956

2972

OS/400 language feature code

2954

2980

2922

2975

2926

2923

2924

2925

2928

2929

If the OS/400 national language version is not included in the list of Domino language feature codes in the table above, then a symbolic link (symlnk) is created and points to the English Domino plug-in by default. You can, however, install one of the OS/400 national language versions contained in the list of Domino language feature codes as a secondary language, and then make use of that translated Domino plug-in for that version.


Installing the translated Domino plug-in

To install a translated Domino plug-in for iSeries Navigator, follow these steps:

1. Install the language pack for the language you want for iSeries Navigator. For more information on installing the language packs, see the readme.txt file on the Language Pack CD-ROM.

During installation of the language pack, a directory called MRIxxxx is added to the following directory:

/QIBM/ProdData/OpNavplugin/LOTUS.DOMINO

where xxxx is the OS/400 feature code for that translated version.

2. Make sure the QIBM folder is set up as a shared folder. If it is not, using iSeries

Navigator, right-click the QIBM folder and select Sharing -> New Share.

3. Open Windows Explorer and select the following directory:

C:\Program Files\IBM\Client Access\MRIxxxx where xxxx is the OS/400 feature code.

4. Click File and select New -> Folder.

5. Name the folder lotus.domino.

6. Go to the OS/400 directory of

/QIBM/ProdData/OpNavplugin/LOTUS.DOMINO, and look for the directory

MRIxxxx, where xxxx is the OS/400 feature code for that translated version.

7. Copy the six files included in this directory into the directory you created on your C: drive.

8. In iSeries Navigator, select your iSeries server.


10. Click Servers.

11. Click Domino.

12. Right-click any Domino server displayed in the list, and you should see a translated interface for the displayed menu.


About running Domino using a secondary language

The following are special considerations to keep in mind if you are running Domino in a language other than English.

Support for Chinese Standard GB18030

Domino 6 supports the Chinese character set standard, GB18030, for the first phase of the Chinese Government conformance requirements. This feature is only available on OS/400 V5R1 and later releases. With OS/400 V5R1, PTFs MF26800,

MF27456, MF27457, SI02503, SI 02498, SI02750, SI02775, SI02930, SI02969,

SI01416, and SI01482 must also be applied to your system for full enablement.

Support for bi-directional languages

Domino 6 for iSeries continues to support the use of bi-directional languages. To use bi-directional languages, follow these steps:

1. Install the Notes client on a BiDi (bi-directional) Windows workstation.

2. Run the client to complete the setup and verify that everything works properly.

3. To turn on BiDi support, choose File -> Preferences -> User Preferences ->

International -> Bidirectional -> Support bidirectional languages.

Note The Bidirectional tab on the International display will only appear if

BiDi is enabled on your system. If you are using Windows 2000, and Arabic or

Hebrew locales are added to the system (using the Regional setting in the control panel) then the BiDi support will be active even if the default locale is not BiDi. On Windows NT, Windows 98, and Windows 95, the user must be running a BiDi version of Windows, and the default regional setting must to be set to a BiDi language.

4. Hebrew users who want to force all equations to flow from left to right should also add:

EnableHebrewEquations=1

These settings will be enabled by default in Arabic and Hebrew localized versions of Notes.

Additional BiDi relevant settings may be customized by choosing File ->

Preferences -> User Preferences -> International -> Bidirectional -> Support

bidirectional languages.


Appendix A

Domino for iSeries Diagrams

This appendix includes some diagrams that will help explain a few concepts and procedures covered earlier in this document.

Domino installation options

This diagram illustrates the various options available for installing the Domino software on your iSeries server. Although there are several ways to initiate the installation, all use the same underlying code in the RSTLICPGM command to perform the actual installation.

Domino configuration options

This diagram illustrates the various configuration options available with Domino for iSeries. Although there are several tools that can be used for configuring a Domino server, all methods use the underlying code in the CFGDOMSVR command to perform the actual configuration.

185

Appendix B

Installing Domino In Batch Mode

If you plan to install the Domino software using OS/400 commands instead of iSeries Navigator, you have the option of installing the software in batch mode.

Instead of having the LODRUN command prompt you for the language version and software options, you can specify this information as part of the command. Then the command installs the software without requiring any additional action from you.

This batch method is particularly useful for multiple installations in remote locations that do not have skilled administrators or that require unattended installation during off-hours.

Note If you already have Domino servers on your iSeries server, do the preliminary tasks described in the procedure for installing the software interactively.

The following table details the directories to use for the different installation options. Use the directory appropriate for your environment when issuing the batch command.

Directory

/OS400/intleng/BATCH

/OS400/intleng/BATCH/CAPI

/OS400/intleng/BATCH/MAIL

/OS400/intleng/BATCH/MAIL/BASE

/OS400/intleng/BATCH/UTIL

/OS400/intleng/BATCH/UTIL/BASE

/OS400/intleng/BATCH/ENT

/OS400/intleng/BATCH/ENT/BASE

Software installed

Domino 6 (*BASE option) with Domino

Messaging Server and C API (option 1)

C API (option 1)


Messaging Server and C API (option 1)


Messaging Server


Utility Server and C API (option 1)


Utility Server


Enterprise Server and C API (option 1)


Enterprise Server

Appendix B: Installing Domino In Batch Mode 187

Local batch installation

Use this method if you are submitting the LODRUN command directly to the iSeries where you are installing the software.

1. Insert the Domino for iSeries CD-ROM in the iSeries optical drive.

2. Install the software using the batch command. For example, issue the following command to install the Domino Utility Server and C API option:

lodrun dev(*opt) dir('/os400/intleng/batch/util')

Note You can put the LODRUN commands in an OS/400 control language

(CL) program and then call the program to run all of the commands. If you have an existing R5 level batch command, this will still work with Domino 6.

Options specified in the command that have been removed in Domino 6 will still be recognized, but will be ignored and an error message will be sent explaining that the option is no longer valid.

Remote batch installation using the remote CD-ROM drive

Use this method to install Domino for iSeries software on a remote iSeries server that is connected to your system.

1. Insert the Domino for iSeries CD-ROM in the optical drive on the remote system.

2. Make sure that the Remote Execution (REXEC) TCP/IP server is running on both your iSeries server and the remote iSeries server. To start the REXEC server, enter the following command:

strtcpsvr server(*rexec)

Note For more information about the REXEC server, see the iSeries book

TCP/IP Configuration and Reference (SC41-5420-04).

3. Use the OS/400 command called Run Remote Command (RUNRMTCMD) to submit the installation command or commands. For example, to install the

Domino Enterprise Server and the C API option, enter the following command:

runrmtcmd cmd('lodrun dev(*opt) dir(''/os400/intleng/batch/ent'')') rmtlocname(remote-name

*ip) rmtuser(myuserid) rmtpwd('password')

In this example, remote-name is the host name or Internet address of the remote system, myuserid is a user profile on the remote system, and password is the password for that user profile. The user profile and password must exist on the remote system. The user profile must have the OS/400 authorities that are required to install the Domino for iSeries software.


Remote installation without using the remote CD-ROM drive

Use this method to install Domino for iSeries at remote locations without requiring the CD-ROM at the remote location.

1. Install Domino for iSeries on the central system.

2. Use the Create Library (CRTLIB) command to create a library for the save files that will contain the Domino software:

crtlib lib(library-name)

Substitute your library name for library-name. For example:

crtlib lib(mylib)

3. Use the Create Save File (CRTSAVF) command to create a save file to hold the

Domino software:

crtsavf file(library-name/save-file-name)

Substitute an actual name for library-name and for save-file-name. For example:

crtsavf file(mylib/dominob)

Note You must create a separate save file for each Domino option that you want to save. For example, create save file DOMINOB for the base software and create save file DOMINO1 for the C API option 1.

4. Use the Save Licensed Program (SAVLICPGM) command to save the base

Domino for iSeries software to the save file. For example:

savlicpgm licpgm(5733LD6) dev(*savf) savf(mylib/dominob)

5. For each additional software option that you want to save, use the

SAVLICPGM command and a new save file. For example, use this command to save option 1:

savlicpgm licpgm(5733LD6) option(1) dev(*savf) savf(mylib/domino1)

6. Use the Send Network File (SNDNETF) command or FTP to copy the save files to the remote system where you want to install Domino for iSeries.

7. Access the remote system and use the Restore Licensed Program

(RSTLICPGM) command to install Domino for iSeries from the save files. You must install each Domino option separately. For example, use this command to install the base software:

rstlicpgm licpgm(5733LD6) dev(*savf) savf(mylib/dominob)

You can access the remote system by remotely signing on or by using the

RUNRMTCMD command to submit the RSTLICPGM commands.

8. If necessary, use the Change User Profile (CHGUSRPRF) command to set the locale for the QNOTES user profile:

chgusrprf usrprf(qnotes) locale(new-locale)

Appendix B: Installing Domino In Batch Mode 189

Appendix C

Using OS/400 Commands With Domino for iSeries

An alternative to managing your Domino environment through the GUI interface is using OS/400 commands.

You start the OS/400 command interface by signing on to your iSeries server, such as from a 5250 emulator window on a workstation that is communicating with the system. To enter a command, type the command on any line following the symbol

===> and press Enter. To have the system prompt you for details of a command, type the command name (such as DSPSFWRSC) and press F4 instead of Enter.

The following are the most commonly used commands when managing your

Domino environment using the OS/400 command interface.

Note Help is available for any command or keyword by pressing F1 when your cursor is on the command or keyword.

CFGDOMSVR

The Configure Domino Server command allows you to either set up a Domino server to run natively on your iSeries server, or completely remove a Domino server.

When setting up a Domino server, you have the option of setting up a first Domino server, or adding a Domino server to an existing Domino domain. For more information on either of these options, see Chapter 6 “Setting up a first Domino server” and Chapter 8 “Setting up an additional Domino server.”

You can set the following parameters when using the CFGDOMSVR command:

•

Data directory

•

Organization

•

Administrator

•

Time zone

•

Daylight savings time

•

Get Domino Directory from (*ADD only)

•

Domino Directory Type (*ADD only)

•

Additional server ID (*ADD only)

•

Web browsers

•

Internet mail packages

Appendix C: Using OS/400 Commands With Domino for iSeries 191

•

SMTP services (With Domino 6, values entered into this field are ignored, and an informational message is sent)

•

Directory services

•

News readers (With Domino 6, values entered into this field are ignored, and an informational message is sent)

•

Connection services

•

Advanced services

•

Default ACL settings

•

Text description

By pressing F10, you can set the following additional parameters:

•

Replace configuration

•

Domain name

•

Network name

•

Country/region code

•

Organizational unit

•

Certifier ID

•

Administrator ID

•

Server ID

•

Start server

•

Start when TCP/IP is started

•

Log replication events

•

Log client session events

•

TCP/IP port options

•

Server host name

•

Subsystem and object names

•

Collation

•

Copy Administrator ID file

•

Additional services

•

Allow Domino Off-Line Services

•

Service provider configuration


To use the CFGDOMSVR command, you must have the following special authorities:

•

*SECADM

•

*ALLOBJ

•

*JOBCTL

•

*IOSYSCFG

CHGDOMSVR

The Change Domino Server command allows you to change the configuration of an existing Domino server on your iSeries server. The following parameters can all be modified using the CHGDOMSVR command:

•

Server ID file password

•

Time zone

•

Daylight savings time

•

Web browsers

•

Internet mail packages

•

Directory services

•

Connection services

•

Advanced services

•

Log replication events

•

Log client session events

•

TCP/IP port options

•

Server host name

•

Subsystem and object names

•

Additional services

•

Collation

•

Text description

By pressing F10, you can modify the following additional parameters:

•

SMTP services (With Domino 6, values entered into this field are ignored, and an informational message is sent)

•

News readers (With Domino 6, values entered into this field are ignored, and an informational message is sent)

•

Start when TCP/IP started

•

Allow Domino Off-Line Services


To use the CHGDOMSVR command, you need the following special authorities:

*SECADM

*ALLOBJ

*JOBCTL

*IOSYSCFG

DLTLICPGM

The Delete Licensed Program command allows you to delete all of the objects that make up a licensed program. When using this command to delete the Domino software, you can choose to delete the entire product or specific options of the product.

To use the DLTLICPGM command, you must have *ALLOBJ special authority.

DSPDOMCSL

The Display Domino Console command provides a way to view the status and jobs of a Domino server. When using this command, you can not submit Domino subcommands to the Domino server.

To run this command, you must have either of the following:

•

*X data authority to the Domino server’s data directory (and its parent directories, if the directory is not directly under the root directory)

•

*ALLOBJ special authority

DSPSFWRSC

The Display Software Resources command allows you to view, print, or write to an output file the list of installed software resources. This command is useful when verifying what software versions are already installed on your iSeries server. When you enter this command, you will see a display that lists the product ID, option, feature code, and a text description of each item. To see the library and release for each item, press F11.


ENDDOMSVR

The End Domino Server command allows you to stop a Domino server that is currently running. You can choose to stop all (*ALL) Domino servers on your iSeries server, or a specific Domino server. There are two additional options that allow you to stop a Domino server in a controlled manner, or immediately.

•

*CNTRLD stops all OS/400 jobs used by the Domino server, but the subsystem used by the server remains operational.

•

*IMMED stops all processing by the Domino server and the subsystem used by the server immediately. Since data could be lost, this option should only be used when the Domino server fails to shut down using the *CNTRLD option.

You can also choose whether or not to stop the Java Server Controller related to your Domino server when the server stops.

To stop a Domino server, you must have *JOBCTL special authority.

LODRUN

The Load and Run Media Program command is commonly used during the installation process of a software product. You can use this command to install a product from tape, diskette, or optical device.

To use the LODRUN command, you must have *SAVSYS special authority.

RUNDOMCMD

The Run Domino Command (RUNDOMCMD) runs an OS/400 CL command in the context of a particular Domino server for iSeries. This command sets up the environment that allows the command to be run whether the Domino server is active or not. The setup includes setting the PATH environment variable for the server, setting the directory for the job to the data directory of the server, and running the requested command under the QNOTES user profile.

Caution If you use RUNDOMCMD in batch, specifying BATCH(*YES), the

RUNDOMCMD setup does not set the current working directory for the job to the server data directory. Instead, the home directory of the QNOTES user profile is used.

To use the RUNDOMCMD command, you must have either of the following:

•


•

*USE authority to the RUNDOMCMD object (object type *CMD) in the QSYS library and *USE authority to the QNNINRUN object (object type *PGM) in the QNOTES library


RSTLICPGM

The Restore Licensed Program command provides a way to load a licensed program whether you are installing for the first time, updating to a new release of a product, or recovering from a lost or damaged state.

When using the RSTLICPGM command, you must specify a device to use to restore the data. The possible devices are:

•

*SAVF - a save file on your iSeries server

•

*OPT - optical drive

•

*TAP - tape drive

To use the RSTLICPGM command, you must have *SECADM and *ALLOBJ special authorities.

SBMDOMCMD

The Submit Domino Command provides a way to submit Domino server commands to run on a Domino server on your iSeries server. Unless you redirect it, the output from a Domino server command is displayed on the Domino console.

When submitting a Domino server command, you will need to specify the name of the Domino server to which you want to submit the serve command.

To use this command, you must have either of the following:

•

*USE authority to the SBMDOMCMD object (object type *CMD) in the QSYS library and *USE authority to the QNNINSDC object (object type *PGM) in the QNOTES library

•


SETDOMENV

The Set Domino Environment command sets the OS/400 job environment to the context of particular Domino server. It sets the PATH environment variable, the active directory to the data directory, and can optionally switch to the user profile associated with the server. The server’s product library is added to the library list of this job.

To use this command, you must have either of the following:

•

*Use authority to the SETDOMENV object in the QSYS library and *USE authority to the QNNINRUN object in the Domino product library

•



STRDOMSVR

The Start Domino Server command allows you to start a Domino server. You can choose to start all (*ALL) Domino servers on your iSeries server, or a specific

Domino server. In addition, you can choose whether or not you want to activate the

Java Server Controller when you start your Domino server.

To start a Domino server, you must have *JOBCTL special authority.

UPDDOMSVR

The Update Domino Server command allows you to update specific Domino servers to newer releases. You can update all servers, or select specific servers, allowing you to control which servers are configured for specific Domino releases.

There are two parameters for this command, SERVER and TORLS. The SERVER parameter allows you to update specific servers or all servers. The TORLS parameter allows you to specify the release to which you want these servers updated.

To use the UPDDOMSVR command, you must have *SECADM, *ALLOBJ,

*JOBCTL and *IOSYSCFG special authorities.

WRKDOMCSL

The Work with Domino Console command provides a way to submit Domino server commands to a specific Domino server. When using the Domino console, you can immediately see the responses from the Domino server.

Only one job can be running the WRKDOMCSL command for a specific Domino server. Other jobs can use the Display Domino Console (DSPDOMCSL) command to view the console messages for the same server.

To use the WRKDOMCSL command, you must have either of the following:

•

*USE authority to the WRKDOMCSL object (object type *CMD) in the QSYS library, *USE authority to the QNNINCSS object (object type *PGM) in the

QNOTES library, and *X data authority to the Domino data directory (and its parent directories if the directory is not directly under the root directory)

•



WRKDOMSVR

The Work with Domino Servers command provides a way to manipulate certain aspects of the Domino servers on your iSeries server. From this display, you can do any of the following to one or more Domino servers:

•

Start a server

•

End a server

•

Change the server configuration

•

Display the server console

•

Work with the server console

•

Work with OS/400 jobs being used by the server

•

Change the working directory

•

Work with OS/400 object links that are associated with the server

•

Edit the NOTES.INI file

A new function (F10) was added to the WRKDOMSVR command that allows you to sort the list of Domino servers in this display either alphabetically, or by the date the server was created.

The special authorities required to execute the different options on the

WRKDOMSVR display vary from function to function.

WRKSBS

The Work with Subsystems command allows you to end a subsystem, display the subsystem description, and work with subsystem jobs. Before upgrading from a previous version of Domino, all Domino subsystems must be stopped. When stopping a subsystem, first attempt to stop it using *CNTRLD.

If after 20 minutes the subsystem has not stopped, use the *IMMED option.

Typical administrative tasks and their equivalent Domino commands

The following table lists typical administrative tasks for a Domino server (called

DOMSERV1) and shows the OS/400 command that you can use to perform the task.

To do this:

Start a server

Use command:

STRDOMSVR

End a server normally ENDDOMSVR

Example:

For the server named DOMSERV1, type: strdomsvr domserv1

For the server named DOMSERV1, type: enddomsvr domserv1

continued


To do this:

End the server subsystem

Determine if a server is active

Use command:

ENDDOMSVR

WRKDOMSVR

DSPDOMCSL

WRKDOMCSL

Example:

First end the DOMSERV1 server, type: enddomsvr domserv1

Wait for the server to end and then type: enddomsvr domserv1 *immed

For the server named DOMSERV1, type: wrkdomsvr domserv1

Look under the Domino Status column to determine if the server is active.

For the DOMSERV1 server, type: dspdomcsl domserv1

For the DOMSERV1 server, type: wrkdomcsl domserv1

Display server activities only

Display server activities and enter server commands

Change a server CHGDOMSVR

Request a working display for controlling

Domino servers

Update a server

WRKDOMSVR

UPDDOMSVR

For the DOMSERV1 server, type: chgdomsvr domserv1

Press F4 to display the current properties.

After changing the desired properties, press

Enter.

For the DOMSERV1 server, type: wrkdomsvr domserv1

Remove a Domino server

Set the Domino environment

CFGDOMSVR

SETDOMENV

For the DOMSERV1 server, type: upddomsvr server(domser1) torls(6.5.1)

This updates DOMSERV1 to the 6.5.1

release.

To remove the DOMSERV1 server, type: cfgdomsvr server(domserv1) option(*delete)

To set the DOMSERV1 environment to run under the server’s user profile with a PATH environment variable reset to the server’s configured execution, data, and user directories, type:

SETDOMENV SERVER(domserv1)

USER(*SERVER)

PATH(*REPLACE)


Index

B

Backup, 131, 134, 136, 137, 139

BRMS, 148, 150, 154, 162

C

C API, 26

CCSID, 175

Collection Services, 169, 170, 171

Configuring additional server, 55, 60 first server, 41, 48

D

DB2 UDB, 105, 107, 110

DECS, 105, 106

Directory centralized, 127

LDAP, 128

Directory Synchronization, 14, 127

Domino

Administrator, 3, 37, 69, 76

Web Administrator, 3, 37

F

Fixes, 7

H

Host name, 34

I

Installing, 23, 26, 27, 30, 31, 38, 40, 76 batch, 187 iSeries Access, 38 iSeries Navigator, 23, 37, 38, 41, 60, 65,

68, 71, 80

J

Java Server Console, 65, 68

Java Server Controller, 73

L

LAN, 163, 164, 165, 167

Languages, 175, 177, 183

LEI, 105

Locales, 175

LS:DO, 105, 107

M

Managing Domino, 65, 68, 69, 70, 71

MSF/Anymail, 14

N

NetServer, 38, 39

O

OS/400 commands, 65, 191, 198 user profile, 21, 66

P

Partitioning, 51, 52, 53

Passport Advantage, 1

Plug-ins, 18, 40

Q

QNOTES, 97, 103, 104

R

Recovery, 70, 131, 142, 143, 144, 145,

160, 161

Registering, 56

Requirements, 4, 148, 163

S

Security, 97, 100, 102, 103, 104, 107

Server

HTTP, 119, 120, 121 mail, 113 properties, 74, 75 starting, 71 status, 74 stopping, 72

Web, 119

Server characteristics, 42

Single Logon, 81

SMTP, 113, 115 multiple, 114

T

TCP/IP, 33, 34, 52, 57

U

Upgrading, 17, 18 considerations, 9, 12

Users, 79, 80

V

Verity KeyView filter, 69

W

WebSphere, 119

201

No results