Novell GROUPWISE 7 Interoperability Guide

Interoperability Guide

Novell®

novdocx (en) 11 July 2008

AUTHORIZED DOCUMENTATION

GroupWise

June 25, 2008

www.novell.com

GroupWise 7 Interoperability Guide

Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

novdocx (en) 11 July 2008

Copyright © 2003-2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc. 404 Wyman Street, Suite 500 Waltham, MA 02451 U.S.A. www.novell.com

Online Documentation: To access the online documentation for this and other Novell products, and to get

updates, see the Novell Documentation Web site (http://www.novell.com/documentation).

Novell Trademarks

For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/

trademarks/tmlist.html).

Third-Party Materials

All third-party trademarks are the property of their respective owners.

novdocx (en) 11 July 2008

Contents

About This Guide 17

Part I Novell Cluster Services on NetWare 19

1 Introduction to GroupWise 7 and Novell Cluster Services on NetWare 21

2 Planning GroupWise in a NetWare Cluster 23

2.1 Meeting Software Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.2 Installing Novell Cluster Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.4 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.5 Planning a New Library for a Clustered Post Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.6 Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise . . . . . . . . . . . 27

2.7 Ensuring Successful Name Resolution for GroupWise Volumes . . . . . . . . . . . . . . . . . . . . . . . 29

2.8 Deciding How to Install and Configure the Agents in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 31

2.8.1 Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the

Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.8.2 Determining Appropriate Failover Paths for the Agents . . . . . . . . . . . . . . . . . . . . . . 33

2.8.3 Deciding Where to Install the Agent Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.8.4 Deciding Whether to Run the Agents in Protected Memory . . . . . . . . . . . . . . . . . . . 36

2.8.5 Planning the NetWare Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.9 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.9.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.9.2 IP Address Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2.9.3 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

novdocx (en) 11 July 2008

3 Setting Up a Domain and Post Office in a NetWare Cluster 43

3.1 Preparing the Cluster for GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1.1 Ensuring Required Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1.2 Cluster-Enabling Shared Volumes for Use with GroupWise . . . . . . . . . . . . . . . . . . . 43

3.1.3 Configuring Short Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2 Setting Up a New GroupWise System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.3 Creating a New Secondary Domain in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.4 Creating a New Post Office in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.5 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.5.1 Installing the Agent Software in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.5.2 Editing Clustered Agent Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.5.3 Configuring the GroupWise Volume Resource to Load and Unload the Agents . . . . 53

3.5.4 Setting Up New Instances of the Agents without Installing the Agent Software . . . . 57

3.6 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.7 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.7.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . . 60

3.7.2 Using Novell Remote Manager on NetWare 6.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

3.7.3 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . . 64

3.8 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3.9 Clustering Quick Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3.9.1 GroupWise System Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Contents 5

3.9.2 Domain Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3.9.3 Post Office Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4 Implementing the Internet Agent in a NetWare Cluster 69

4.1 Planning the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4.1.2 Deciding Whether to Cluster-Enable the Internet Agent Volume. . . . . . . . . . . . . . . . 70

4.1.3 Determining an Appropriate Failover Path for the Internet Agent Volume. . . . . . . . . 70

4.1.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the Internet

Agent and Its MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.1.5 Preparing Your Firewall for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.1.6 Deciding Where to Install the Internet Agent and Its MTA. . . . . . . . . . . . . . . . . . . . . 72

4.1.7 Deciding Whether to Run the Internet Agent and Its MTA in Protected Memory. . . . 72

4.1.8 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4.1.9 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4.2 Setting Up the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4.2.1 Cluster-Enabling a Shared Volume for Use with the Internet Agent . . . . . . . . . . . . . 73

4.2.2 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.2.3 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4.2.4 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . 74

4.2.5 Testing the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4.3 Managing the Internet Agent in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4.3.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . . 83

4.3.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . . 84

4.4 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4.5 Internet Agent Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

novdocx (en) 11 July 2008

5 Implementing WebAccess in a NetWare Cluster 89

5.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

5.2 Planning WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

5.2.1 Planning a New Domain for the WebAccess Agent. . . . . . . . . . . . . . . . . . . . . . . . . . 90

5.2.2 Deciding Whether to Cluster-Enable the WebAccess Agent Volume . . . . . . . . . . . . 90

5.2.3 Determining an Appropriate Failover Path for the WebAccess Agent Volume . . . . . 91

5.2.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the

WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

5.2.5 Deciding Where to Install the WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . . 91

5.2.6 Deciding Whether to Run the WebAccess Agent and Its MTA in Protected Memory 92

5.2.7 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

5.2.8 Planning the WebAccess Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

5.3 Setting Up WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5.3.1 Cluster-Enabling a Shared Volume for Use with the WebAccess Agent . . . . . . . . . . 93

5.3.2 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

5.3.3 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . 94

5.3.4 Installing and Configuring the WebAccess Agent in a Cluster. . . . . . . . . . . . . . . . . . 94

5.3.5 Testing Your Clustered WebAccess Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

5.4 Managing WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

5.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 101

5.4.2 Knowing What to Expect in WebAccess Failover Situations . . . . . . . . . . . . . . . . . . 102

5.4.3 Updating the WebAccess Agent Configuration File (commgr.cfg). . . . . . . . . . . . . . 102

5.5 WebAccess Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

5.6 WebAccess Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6 GroupWise 7 Interoperability Guide

6 Implementing GroupWise Gateways in a Novell Cluster 107

7 Monitoring a GroupWise System in a NetWare Cluster 109

8 Backing Up a GroupWise System in a NetWare Cluster 111

8.1 Using GWTSA in a NetWare 5.1 Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8.2 Using TSAFSGW in a NetWare 6.x Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9 Updating a GroupWise System in a NetWare Cluster 115

10 Moving an Existing GroupWise 7 System into a NetWare Cluster 117

11 Implementing Messenger in a NetWare Cluster 119

11.1 Planning Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

11.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

11.1.2 Planning Messenger Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

11.1.3 Deciding Where to Install the Messenger Agent Software . . . . . . . . . . . . . . . . . . . 120

11.1.4 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

11.2 Setting Up Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

11.2.1 Installing to Each Node in the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

11.2.2 Installing to a Messenger Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

11.3 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

novdocx (en) 11 July 2008

Part II Novell Cluster Services on Linux 129

12 Introduction to GroupWise 7 and Novell Cluster Services on Linux 131

13 Planning GroupWise in a Linux Cluster 133

13.1 Installing Novell Cluster Services on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

13.2 Planning a Clustered Software Distribution Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

13.3 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

13.4 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

13.5 Planning a New Library for a Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

13.6 Deciding How to Install and Configure the Linux Agents in a Cluster . . . . . . . . . . . . . . . . . . 138

13.6.1 Recording Secondary IP Addresses for the Agents . . . . . . . . . . . . . . . . . . . . . . . . 138

13.6.2 Determining Appropriate Failover Lists for the Agents . . . . . . . . . . . . . . . . . . . . . . 138

13.6.3 Determining Cluster Resource Information for the Linux Agents. . . . . . . . . . . . . . . 139

13.6.4 Planning the Linux Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

13.7 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

13.7.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

13.7.2 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

14 Setting Up a Domain and a Post Office in a Linux Cluster 143

14.1 Setting Up a New GroupWise System in a Linux Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

14.2 Creating a New Secondary Domain in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

14.3 Creating a New Post Office in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

14.4 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 146

14.4.1 Installing and Setting Up the Agents in Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . 146

Contents 7

14.4.2 Changing Agent Paths to Locations on GroupWise Partitions . . . . . . . . . . . . . . . . 150

14.4.3 Configuring GroupWise Cluster Resources to Load and Unload the Agents . . . . . 152

14.4.4 Setting Up New Instances of the Agents without Installing the Agent Software . . . 158

14.5 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

14.6 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

14.6.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 161

14.6.2 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . 163

14.7 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

14.8 Clustering Quick Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

14.8.1 GroupWise System Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

14.8.2 Domain Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

14.8.3 Post Office Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

15 Implementing the Internet Agent in a Linux Cluster 167

15.1 Planning the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

15.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

15.1.2 Selecting the Internet Agent Partition and Secondary IP Address . . . . . . . . . . . . . 168

15.1.3 Determining an Appropriate Failover List for the Internet Agent . . . . . . . . . . . . . . . 169

15.1.4 Determining Cluster Resource Information for the Internet Agent . . . . . . . . . . . . . . 169

15.1.5 Preparing DNS for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

15.1.6 Preparing Your Firewall for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . 169

15.1.7 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

15.1.8 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

15.2 Setting Up the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

15.2.1 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

15.2.2 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 171

15.2.3 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . 171

15.3 Testing the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

15.4 Managing the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

15.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 183

15.4.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . 184

15.5 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

15.6 Internet Agent Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

novdocx (en) 11 July 2008

16 Implementing WebAccess in a Linux Cluster 187

16.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

16.2 Planning the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

16.2.1 Planning a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

16.2.2 Selecting the WebAccess Agent Partition and Secondary IP Address . . . . . . . . . . 189

16.2.3 Determining an Appropriate Failover List for the WebAccess Agent . . . . . . . . . . . . 189

16.2.4 Determining Cluster Resource Information for the WebAccess Agent . . . . . . . . . . 189

16.2.5 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.2.6 Planning the WebAccess Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.2.7 Planning the WebAccess Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.3 Setting Up the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.3.1 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

16.3.2 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . 191

16.3.3 Installing and Configuring the WebAccess Agent in a Cluster. . . . . . . . . . . . . . . . . 191

16.3.4 Installing and Configuring the WebAccess Application in a Cluster . . . . . . . . . . . . 201

16.4 Testing the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

16.5 Managing the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

16.5.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 203

16.5.2 Knowing What to Expect in a WebAccess Agent Failover Situation . . . . . . . . . . . . 204

16.6 WebAccess Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

8 GroupWise 7 Interoperability Guide

16.7 WebAccess Agent Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

17 Implementing GroupWise Monitor in a Linux Cluster 207

17.1 Understanding the Monitor Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

17.2 Planning GroupWise Monitor in a Linux Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

17.2.1 Selecting a Domain for Access during Monitor Agent Installation . . . . . . . . . . . . . . 208

17.2.2 Selecting an MTA for the Monitor Agent to Access after Installation. . . . . . . . . . . . 208

17.2.3 Selecting the Monitor Agent Partition and Secondary IP Address. . . . . . . . . . . . . . 209

17.2.4 Determining an Appropriate Failover List for the Monitor Agent . . . . . . . . . . . . . . . 209

17.2.5 Determining Cluster Resource Information for the Monitor Agent . . . . . . . . . . . . . . 209

17.2.6 Planning the Monitor Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

17.3 Setting Up GroupWise Monitor in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

17.3.1 Installing and Configuring the Monitor Agent on Each Node in Your Cluster . . . . . 210

17.3.2 Configuring the Monitor Agent Cluster Resource to Load and Unload the Monitor

Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

17.4 Testing the Monitor Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

17.5 Managing the Monitor Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

17.6 Monitor Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

17.7 Monitor Agent Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

novdocx (en) 11 July 2008

18 Backing Up a GroupWise System in a Linux Cluster 221

19 Updating a GroupWise System in a Linux Cluster 223

20 Moving an Existing Linux GroupWise 7 System into a Linux Cluster 225

21 Moving a Clustered GroupWise 7 System from NetWare to Linux 227

22 Implementing Messenger in a Linux Cluster 229

22.1 Planning Your Messenger System in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

22.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

22.1.2 Selecting the Messenger Partition and Secondary IP Address . . . . . . . . . . . . . . . . 230

22.1.3 Determining an Appropriate Failover List for the Messenger Agents . . . . . . . . . . . 230

22.1.4 Determining Cluster Resource Information for the Messenger Agents . . . . . . . . . . 230

22.1.5 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

22.2 Setting Up Your Messenger System in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

22.2.1 Creating Your Messenger System and Installing the Messenger Agents . . . . . . . . 231

22.2.2 Changing Messenger Paths to Locations on the Messenger Partition . . . . . . . . . . 233

22.2.3 Configuring the Messenger Cluster Resource to Load and Unload the Messenger

Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

22.3 Testing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

22.4 Managing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

22.5 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

22.6 Messenger Clustering Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Part III Novell Teaming and Conferencing 243

23 Using GroupWise with Novell Teaming 245

23.1 Understanding How Novell Teaming Interacts with eDirectory and GroupWise . . . . . . . . . . 245

Contents 9

23.2 Meeting Novell Teaming System Requirements on OES 2 or SLES 10 SP1 Servers. . . . . . 245

23.2.1 Linux Open File Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

23.2.2 Java Development Kit Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

23.2.3 MySQL Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

23.2.4 Potential Web Server Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

23.3 Installing Novell Teaming with GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

23.3.1 Preparing for the Novell Teaming Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

23.3.2 Performing the Novell Teaming Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

23.4 Configuring LDAP Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

23.5 Configuring GroupWise to Support Your Teaming Installation. . . . . . . . . . . . . . . . . . . . . . . . 249

23.5.1 Configuring Outgoing E-Mail from Teaming to GroupWise . . . . . . . . . . . . . . . . . . . 249

23.5.2 Configuring Incoming E-Mail from GroupWise Users to the Novell Teaming Site . . 251

23.5.3 Testing GroupWise Integration with Novell Teaming. . . . . . . . . . . . . . . . . . . . . . . . 257

23.6 Receiving Notification of Teaming Site Activity in Your GroupWise Client. . . . . . . . . . . . . . . 259

23.7 Receiving Calendar Postings from the Teaming Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

23.8 Adding Portlets to Novell Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

23.8.1 Adding Liferay Portlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

23.8.2 Adding GroupWise Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

24 Using GroupWise with Conferencing 263

novdocx (en) 11 July 2008

24.1 Configuring GroupWise as the Conferencing E-Mail System. . . . . . . . . . . . . . . . . . . . . . . . . 263

24.1.1 Preparing for GroupWise Integration with Conferencing . . . . . . . . . . . . . . . . . . . . . 263

24.1.2 Integrating GroupWise with Novell Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . 263

24.1.3 Testing GroupWise as the Novell Conferencing E-Mail System . . . . . . . . . . . . . . . 264

25 Streamlining Authentication to Teaming or Conferencing 265

25.1 Using iChain for Authenticating to Teaming or Conferencing . . . . . . . . . . . . . . . . . . . . . . . . 265

25.1.1 Meeting iChain Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

25.1.2 Setting Up an iChain Web Server Accelerator for Teaming or Conferencing . . . . . 265

25.1.3 Adding the New Web Server Accelerator to the iChain Server Object in

ConsoleOne. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

25.1.4 Using iChain for Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

25.2 Using Novell Access Manager for Authenticating to Teaming or Conferencing. . . . . . . . . . . 267

Part IV Other Novell Products 269

26 GroupWise DirXML Driver for Novell Identity Manager 271

26.1 Identity Manager Warnings in ConsoleOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

26.1.1 Recovering a Deleted GroupWise Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

26.1.2 Grafting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

26.1.3 Converting an External Entity to a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

26.1.4 Converting a User to an External Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

26.1.5 Associating a GroupWise Object with an eDirectory Object . . . . . . . . . . . . . . . . . . 272

26.1.6 Disassociating a GroupWise Object’s Attributes from an eDirectory Object . . . . . . 272

26.1.7 Resolving an Invalid Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

26.1.8 Disabling the DirXML Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

26.1.9 Enabling the DirXML Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

10 GroupWise 7 Interoperability Guide

27 GroupWise Customization Tools 275

28 Novell exteNd 277

Part V Heartbeat on Linux 279

29 Introduction to GroupWise 7 and Heartbeat on Linux 281

29.1 Understanding Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

29.2 Meeting System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

29.3 Installing Heartbeat Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

29.4 Configuring Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

29.5 Starting Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

29.6 Managing Heartbeat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

29.7 Setting Up Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

29.8 Setting Up Node Fencing or Resource Fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

29.9 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

novdocx (en) 11 July 2008

30 Planning GroupWise in a Heartbeat Cluster 285

30.1 Planning Your Heartbeat Cluster for GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

30.1.1 Recording Heartbeat Cluster Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

30.1.2 Planning GroupWise Cluster Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

30.1.3 Planning Cluster Resources and Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . 287

30.1.4 Planning Secondary IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

30.2 Planning a Software Distribution Directory for a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

30.3 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

30.4 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

30.5 Planning a New Library for a Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

30.6 Considering How to Install and Configure the Linux Agents in a Cluster . . . . . . . . . . . . . . . . 290

30.6.1 Recording Secondary IP Addresses for the Agents . . . . . . . . . . . . . . . . . . . . . . . . 290

30.6.2 Determining Appropriate Heartbeat Constraints for GroupWise Cluster Resource

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

30.6.3 Planning the Linux Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

30.7 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

30.7.1 Heartbeat Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

30.7.2 GroupWise Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

31 Setting Up a Heartbeat Cluster 297

31.1 Starting the HA Management Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

31.2 Creating a Cluster Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

31.3 Creating Native Heartbeat Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

31.3.1 EVMS Container Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

31.3.2 File System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

31.3.3 IP Address Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

31.4 Creating Heartbeat Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

31.4.1 Place Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

31.4.2 Order Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

31.4.3 Colocation Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

31.5 Starting the Native Heartbeat Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Contents 11

32 Setting Up a Domain and a Post Office in a Heartbeat Cluster 307

32.1 Setting Up a New GroupWise System in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . 307

32.2 Creating a New Secondary Domain in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 308

32.3 Creating a New Post Office in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

32.4 Installing and Configuring the MTA and the POA in a Heartbeat Cluster. . . . . . . . . . . . . . . . 310

32.4.1 Running the GroupWise Installation Program on the Initial Node . . . . . . . . . . . . . . 311

32.4.2 Running the GroupWise Installation Program on Subsequent Nodes . . . . . . . . . . . 313

32.4.3 Creating and Configuring GroupWise Cluster Resources . . . . . . . . . . . . . . . . . . . . 315

32.4.4 Testing Your Agent Installation on Each Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

32.4.5 Changing Agent Paths to Locations on the Shared Storage Partition . . . . . . . . . . . 318

32.4.6 Setting Up New Instances of the Agents without Installing the Agent Software . . . 319

32.5 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

32.6 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

32.6.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 321

32.6.2 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . 322

32.7 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

33 Implementing the Internet Agent in a Heartbeat Cluster 325

33.1 Planning the Internet Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

33.1.1 Planning a Cluster Resource Group for the Internet Agent . . . . . . . . . . . . . . . . . . . 326

33.1.2 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

33.1.3 Recording the Internet Agent Secondary IP Address . . . . . . . . . . . . . . . . . . . . . . . 327

33.1.4 Determining Appropriate Heartbeat Constraints for the Internet Agent . . . . . . . . . . 327

33.1.5 Preparing DNS for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

33.1.6 Preparing Your Firewall for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . 327

33.1.7 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

33.1.8 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

33.2 Setting Up the Internet Agent in a Heartbeat Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

33.2.1 Setting Up Native Heartbeat Cluster Resources for the Internet Agent. . . . . . . . . . 329

33.2.2 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

33.2.3 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 330

33.2.4 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . 330

33.3 Testing the Internet Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

33.4 Managing the Internet Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

33.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 339

33.4.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . 340

33.5 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

novdocx (en) 11 July 2008

34 Implementing WebAccess in a Heartbeat Cluster 343

34.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

34.2 Planning the WebAccess Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

34.2.1 Planning a Cluster Resource Group for the WebAccess Agent . . . . . . . . . . . . . . . 344

34.2.2 Planning a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

34.2.3 Recording the WebAccess Secondary IP Address . . . . . . . . . . . . . . . . . . . . . . . . . 345

34.2.4 Determining Appropriate Heartbeat Constraints for the WebAccess Agent . . . . . . 345

34.2.5 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

34.2.6 Planning the WebAccess Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

34.2.7 Planning the WebAccess Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 346

34.3 Setting Up the WebAccess Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

34.3.1 Setting Up Native Heartbeat Resources for the WebAccess Agent . . . . . . . . . . . . 347

34.3.2 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

34.3.3 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . 347

34.3.4 Installing and Configuring the WebAccess Agent in a Heartbeat Cluster . . . . . . . . 348

12 GroupWise 7 Interoperability Guide

34.3.5 Installing and Configuring the WebAccess Application on Your Web Server . . . . . 355

34.4 Testing the WebAccess Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

34.5 Managing the WebAccess Agent in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

34.5.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 357

34.5.2 Knowing What to Expect in a WebAccess Agent Failover Situation . . . . . . . . . . . . 357

34.6 WebAccess Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

35 Implementing GroupWise Monitor in a Heartbeat Cluster 361

36 Backing Up a GroupWise System in a Heartbeat Cluster 363

37 Updating a GroupWise System in a Heartbeat Cluster 365

38 Moving an Existing Linux GroupWise 7 System into a Heartbeat Cluster 367

39 Implementing Messenger in a Heartbeat Cluster 369

39.1 Planning Your Messenger System in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

39.1.1 Planning a Cluster Resource Group for the Messenger Agents . . . . . . . . . . . . . . . 369

39.1.2 Recording the Messenger Agents’ Secondary IP Address . . . . . . . . . . . . . . . . . . . 370

39.1.3 Determining Appropriate Constraints for the Messenger Agents . . . . . . . . . . . . . . 370

39.1.4 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

39.2 Setting Up Your Messenger System in a Heartbeat Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 371

39.2.1 Setting Up Native Heartbeat Resources for the Messenger Agents . . . . . . . . . . . . 371

39.2.2 Creating Your Messenger System and Installing the Messenger Agents . . . . . . . . 372

39.2.3 Changing Messenger Paths to Locations on the Messenger Partition . . . . . . . . . . 376

39.3 Testing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

39.4 Managing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

39.5 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

novdocx (en) 11 July 2008

Part VI Microsoft Clustering Services on Windows 381

40 Introduction to GroupWise 7 and Microsoft Clusters 383

41 Planning GroupWise in a Microsoft Cluster 385

41.1 Setting Up Your Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

41.2 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

41.3 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

41.4 Planning a New Library for a Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

41.5 Planning GroupWise Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

41.6 Planning Shared Administrative Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

41.7 Ensuring Successful Name Resolution for GroupWise Resource Groups. . . . . . . . . . . . . . . 389

41.8 Deciding How to Install and Configure the Agents in a Cluster . . . . . . . . . . . . . . . . . . . . . . . 391

41.8.1 Planning Cluster-Unique Port Numbers for Agents in the Cluster . . . . . . . . . . . . . . 391

41.8.2 Deciding Where to Install the Agent Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

41.8.3 Planning the Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

41.8.4 Planning the Windows Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

41.9 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

41.9.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

41.9.2 Network Address Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

41.9.3 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Contents 13

42 Setting Up a Domain and Post Office in a Microsoft Cluster 401

42.1 Preparing the Cluster for GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

42.1.1 Creating GroupWise Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

42.1.2 Creating Agent Service Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

42.1.3 Configuring Short Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

42.2 Setting Up a New GroupWise System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

42.3 Creating a New Secondary Domain in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

42.4 Creating a New Post Office in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

42.5 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 406

42.5.1 Installing the Agent Software in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

42.5.2 Editing Clustered Agent Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

42.5.3 Setting Up New Instances of the Agents without Installing the Agent Software . . . 408

42.6 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

42.7 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

42.7.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 409

42.7.2 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . 410

42.8 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

43 Implementing the Internet Agent in a Microsoft Cluster 413

novdocx (en) 11 July 2008

43.1 Planning the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

43.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

43.1.2 Planning the Internet Agent Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

43.1.3 Planning Cluster-Unique Port Numbers for the Internet Agent and Its MTA . . . . . . 414

43.1.4 Preparing Your Firewall for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

43.1.5 Deciding Where to Install the Internet Agent and Its MTA . . . . . . . . . . . . . . . . . . . . 415

43.1.6 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

43.1.7 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

43.2 Setting Up the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

43.2.1 Setting Up the Internet Agent Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

43.2.2 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

43.2.3 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 417

43.2.4 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . 417

43.2.5 Testing the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

43.3 Managing the Internet Agent in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

43.3.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 420

43.3.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . 421

43.4 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

44 Implementing WebAccess in a Microsoft Cluster 423

44.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

44.2 Planning WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

44.2.1 Setting Up Your Web Server in the Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . 424

44.2.2 Planning a New Domain for the WebAccess Agent. . . . . . . . . . . . . . . . . . . . . . . . . 424

44.2.3 Planning the WebAccess Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

44.2.4 Planning Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA. . . 425

44.2.5 Deciding Where to Install the WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . 426

44.2.6 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

44.2.7 Planning the WebAccess Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

44.3 Setting Up WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

44.3.1 Setting Up the WebAccess Resource Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

44.3.2 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

44.3.3 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . 428

44.3.4 Installing the WebAccess Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

14 GroupWise 7 Interoperability Guide

44.3.5 Installing and Configuring the WebAccess Application in a Cluster . . . . . . . . . . . . 429

44.3.6 Testing Your Clustered WebAccess Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

44.4 Managing WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

44.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 431

44.4.2 Knowing What to Expect in WebAccess Failover Situations . . . . . . . . . . . . . . . . . . 432

44.4.3 Updating the WebAccess Agent Configuration File (commgr.cfg). . . . . . . . . . . . . . 432

44.5 WebAccess Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

45 Implementing GroupWise Gateways in a Microsoft Cluster 435

46 Monitoring a GroupWise System in a Microsoft Cluster 437

47 Backing Up a GroupWise System in a Microsoft Cluster 439

48 Moving an Existing GroupWise 7 System into a Microsoft Cluster 441

49 Implementing Messenger in a Microsoft Cluster 443

49.1 Planning Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

49.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

49.1.2 Planning Messenger Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

49.1.3 Deciding Where to Install the Messenger Agent Software . . . . . . . . . . . . . . . . . . . 444

49.1.4 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

49.2 Setting Up Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

49.2.1 Installing the Messenger Agents to Each Node in the Cluster. . . . . . . . . . . . . . . . . 446

49.2.2 Installing the Messenger Agents to a Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . 446

49.3 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

novdocx (en) 11 July 2008

Part VII Non-GroupWise Clients 449

50 Outlook Express 451

51 Microsoft Outlook 453

52 Evolution 455

52.1 GroupWise Features Available in Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

52.2 Configuring Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456

Part VIII Mobile Devices 459

53 GroupWise Mobile Server, Powered by Intellisync 461

54 BlackBerry Enterprise Server 463

55 GroupWise PDA Connect 465

55.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

55.2 Downloading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

55.3 Third-Party Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

Contents 15

Part IX Documentation Updates 467

A June 25, 2008 469

B March 14, 2008 (GroupWise 7 SP3) 471

C October 24, 2007 473

D April 16, 2007 (GroupWise 7 SP 2) 475

E September 29, 2006 477

F August 2, 2006 479

G June 15, 2006 (GroupWise 7 SP1) 481

novdocx (en) 11 July 2008

H November 30, 2005 485

16 GroupWise 7 Interoperability Guide

About This Guide

This Novell® GroupWise® 7 Interoperability Guide helps you use GroupWise in the context of other software products. The guide provides assistance with Novell products and third-party products:

Novell Products  Part I, “Novell Cluster Services on NetWare,” on page 19

 Part II, “Novell Cluster Services on Linux,” on page 129

 Part III, “Novell Teaming and Conferencing,” on page 243

 Part IV, “Other Novell Products,” on page 269

novdocx (en) 11 July 2008

Third-Party Products

For information about additional GroupWise-related software from GroupWise partners, see the

Novell Partner Product Guide (http://www.novell.com/partnerguide).

Audience

This guide is intended for network administrators who install and administer GroupWise.

Feedback

We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comment feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.

Documentation Updates

For the most recent version of the GroupWise 7 Interoperability Guide, visit the Novell GroupWise

7 documentation Web site (http://www.novell.com/documentation/gw7).

 Part V, “Heartbeat on Linux,” on page 279

 Part VI, “Microsoft Clustering Services on Windows,” on page 381

 Part VII, “Non-GroupWise Clients,” on page 449

Additional Documentation

For additional GroupWise documentation, see the following guides at the Novell GroupWise 7

documentation Web site (http://www.novell.com/documentation/gw7):

 Installation Guide

 Administration Guide

 Multi-System Administration Guide

 Troubleshooting Guides

 GroupWise Client User Guides

 GroupWise Client Frequently Asked Questions (FAQ)

About This Guide 17

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.

A trademark symbol (

, ®, etc.) denotes a Novell trademark. An asterisk denotes a third-party

trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux*, should use forward slashes as required by your software.

When a startup switch can be written with a forward slash for some platforms or a double hyphen for other platforms, the startup switch is presented with a forward slash. Users of platforms that require a double hyphen, such as Linux, should use double hyphens as required by your software.

novdocx (en) 11 July 2008

18 GroupWise 7 Interoperability Guide

Novell Cluster Services on NetWare

 Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page 21

 Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 23

 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,” on page 43

 Chapter 4, “Implementing the Internet Agent in a NetWare Cluster,” on page 69

 Chapter 5, “Implementing WebAccess in a NetWare Cluster,” on page 89

 Chapter 6, “Implementing GroupWise Gateways in a Novell Cluster,” on page 107

 Chapter 7, “Monitoring a GroupWise System in a NetWare Cluster,” on page 109

 Chapter 8, “Backing Up a GroupWise System in a NetWare Cluster,” on page 111

 Chapter 9, “Updating a GroupWise System in a NetWare Cluster,” on page 115

 Chapter 10, “Moving an Existing GroupWise 7 System into a NetWare Cluster,” on page 117

novdocx (en) 11 July 2008

 Chapter 11, “Implementing Messenger in a NetWare Cluster,” on page 119

Novell Cluster Services on NetWareI19

novdocx (en) 11 July 2008

20 GroupWise 7 Interoperability Guide

Introduction to GroupWise 7 and

novdocx (en) 11 July 2008

Novell Cluster Services on NetWare

Before implementing GroupWise® 7 with Novell® Cluster ServicesTM, make sure you have a solid understanding of Novell Cluster Services by reviewing the following information resources:

 AppNote: An Introduction to Novell Cluster Services (http://developer.novell.com/research/

appnotes/1999/may/01/a990501_.pdf)

 Novell Open Enterprise Server (OES) Product Documentation: OES Novell Cluster

Services 1.8 Administration Guide for NetWare (http://www.novell.com/documentation/oes/ cluster_admin/data/h4hgu4hs.html#bktitle)

 NetWare 6.5 Product Documentation: Novell Cluster Services (http://www.novell.com/

documentation/ncs65)

 NetWare 6 Product Documentation: Novell Cluster Services (http://www.novell.com/

documentation/ncs6p)

 NetWare 5.1 Product Documentation: Novell Cluster Services (http://www.novell.com/

documentation/ncs)

When you review the information resources recommended above, you discover that clustering employs very specialized terminology. The following brief glossary provides basic definitions of clustering terms and relates them to your GroupWise system:

cluster: A grouping of from 2 to 32 NetWare that data storage locations and applications can transfer from one server to another without interrupting their availability to users.

servers configured using Novell Cluster Services so

node: A clustered server; in other words, a single NetWare server that is part of a cluster.

resource: An IP address, volume, application, service, and so on, that can function successfully

anywhere in the cluster. The volumes where domains and post offices reside are a specific type of cluster resources termed “volume resources.” In this section, the terms “cluster resource” and “volume resource” are used instead of “resource” to avoid confusion with GroupWise resources (such as conference rooms and projectors).

failover: The process of moving cluster resources from a failed node to a functional node so that availability to users is uninterrupted. For example, if the node where the POA is running goes down, the POA and its post office fail over to a secondary node so that users can continue to use GroupWise. When setting up cluster resources, you need to consider what components need to fail over together in order to continue functioning.

fan-out-failover: The configuration where cluster resources from a failed node fail over to different nodes in order to distribute the load from the failed node across multiple nodes. For example, if a node runs a cluster resource consisting of a domain and its MTA, another cluster resource consisting of a post office and its POA, and a third cluster resource for WebAccess, each cluster resource can be configured to fail over separately to different secondary nodes.

Introduction to GroupWise 7 and Novell Cluster Services on NetWare

failback: The process of returning cluster resources to their preferred node after the situation causing the failover has been resolved. For example, if a POA and its post office fail over to a secondary node, that cluster resource can be configured to fail back to its preferred node when the problem is resolved.

migration: The process of manually moving a cluster resource from its preferred node to a secondary node for the purpose of performing maintenance on the preferred node, temporarily lightening the load on the preferred node, and so on.

shared disk system: The hardware housing the physical disk volumes that are shared among the cluster nodes.

shared volume: A volume in a shared disk system that can be accessed from any cluster node that needs the data stored on it.

novdocx (en) 11 July 2008

cluster-enabled shared volume: A shared volume for which a Volume Resource object has been

created in Novell eDirectory

. The properties of the Volume Resource object provide load and unload scripts for programs installed on the volume, failover/failback/migration policies for the volume, and the failover path for the volume. Cluster-enabling is highly recommended for GroupWise.

GroupWise volume: As used in this section, a cluster-enabled shared volume that is used for GroupWise, such as for storing a domain, post office, software distribution directory, and so on. This section also uses the terms Internet Agent volume, WebAccess Agent volume, Messenger volume, and gateway volume in a similar manner.

storage area network (SAN): The cluster nodes together with their shared disk system and shared volumes.

virtual server: A logical server, rather than a physical server, to which cluster-enabled shared volumes are tied.

active/active mode: The configuration of a clustered application where the application runs simultaneously on multiple nodes in the cluster. Active/active mode is recommended when the GroupWise MTA, POA, Internet Agent, and WebAccess Agent run in protected memory because protected memory isolates them from each other, even if they are running on the same node.

active/passive mode: The configuration of a clustered application where the application runs on only one node at a time in the cluster. The GroupWise MTA, POA, Internet Agent, and WebAccess Agent must run in active/passive mode if they are not running in protected memory because only one instance of each agent/database combination can be running at the same time in the cluster.

22 GroupWise 7 Interoperability Guide

Planning GroupWise in a NetWare

novdocx (en) 11 July 2008

Cluster

The majority of this part of the GroupWise 7 Interoperability Guide (Chapter 2, “Planning

GroupWise in a NetWare Cluster,” on page 23 through Chapter 8, “Backing Up a GroupWise System in a NetWare Cluster,” on page 111) is designed for those who are creating a new

GroupWise Services a newly installed cluster, see Chapter 10, “Moving an Existing GroupWise 7 System into a NetWare

Cluster,” on page 117.

When you implement a new GroupWise system or a new domain or post office in a clustering environment, overall GroupWise system design does not need to change substantially. For a review, see “Installing a Basic GroupWise System” in the GroupWise 7 Installation Guide. However, the configuration of individual components of your GroupWise system will be significantly different. This section helps you plan the following GroupWise components in a cluster:

 A new GroupWise system consisting of the primary domain and the initial post office

 A new secondary domain

 A new post office

 The GroupWise agents (MTA and POA)

system, or at least new domains and post offices, in the context of Novell® Cluster

. If you already have an existing GroupWise 7 system and need to configure it to work in

During the planning process, component configuration alternatives are explained. For example, you might want the domain and post office together on the same shared volume or on different shared volumes. You might want to install the agents to standard sys:\system directories or to manually created vol:\system directories on shared volumes where domains and post offices reside. You might or might not need to run the agents in protected memory.

The “System Clustering Worksheet” on page 37 lists all the information you need as you set up GroupWise in a clustering environment. You should print the worksheet and fill it out as you complete the tasks listed below:

 Section 2.1, “Meeting Software Version Requirements,” on page 24

 Section 2.2, “Installing Novell Cluster Services,” on page 24

 Section 2.3, “Planning a New Clustered Domain,” on page 25

 Section 2.4, “Planning a New Clustered Post Office,” on page 26

 Section 2.5, “Planning a New Library for a Clustered Post Office,” on page 27

 Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise,”

on page 27

 Section 2.7, “Ensuring Successful Name Resolution for GroupWise Volumes,” on page 29

 Section 2.8, “Deciding How to Install and Configure the Agents in a Cluster,” on page 31

 Section 2.9, “GroupWise Clustering Worksheets,” on page 37

After you have completed the tasks and filled out “System Clustering Worksheet” on page 37, you are ready to continue with Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”

on page 43.

Planning GroupWise in a NetWare Cluster

2.1 Meeting Software Version Requirements

GroupWise 7 can be clustered on a system that meets the following requirements:

 GroupWise 7

 A supported version of NetWare

 OES NetWare

 NetWare 6.5

 NetWare 6

 NetWare 5.1

IMPORTANT: Novell Cluster Services does not support mixed NetWare versions within a cluster.

SYSTEM CLUSTERING WORKSHEET

Under Item 1: Software Version Updates for Cluster, mark any updates required for nodes in the cluster to ensure that all nodes in the cluster are running the same version of NetWare.

with the latest Support Pack

novdocx (en) 11 July 2008

2.2 Installing Novell Cluster Services

Install Novell Cluster Services by following the instructions provided in the documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster

Services on NetWare,” on page 21.

The installation process includes:

 Meeting hardware and software requirements

 Setting up a shared disk system

 Creating a new NetWare Cluster object to represent the cluster in Novell eDirectory

 Adding nodes to the cluster

 Installing the Novell Cluster Services software on all nodes in the cluster

 Mounting the shared volumes where you will set up GroupWise domains and post offices and

install the GroupWise agents

As you install Novell Cluster Services, record key information about the cluster on the System Clustering Worksheet:

SYSTEM CLUSTERING WORKSHEET

Under Item 2: eDirectory Tree for Cluster, record the name of the eDirectory tree where the new NetWare Cluster object has been created.

Under Item 3: Cluster Name, record the name of the NetWare Cluster object that you created for your GroupWise system.

Under Item 4: Cluster Context, record the full context of the NetWare Cluster object.

Under Item 5: Nodes in Cluster, list the nodes that you have added to the cluster.

24 GroupWise 7 Interoperability Guide

The number of nodes and shared volumes that are available in the cluster strongly influences where you place GroupWise domains and post offices. You have several alternatives:

 Your whole GroupWise system can run in a single cluster.

 Parts of your GroupWise system can run in one cluster while other parts of it run in one or more

other clusters.

 Parts of your GroupWise system can run in a cluster while other parts run outside of the cluster,

on non-clustered servers.

If you do not have the system resources to run all of your GroupWise system in a clustering environment, you must decide which parts have the most urgent need for the high availability provided by clustering. Here are some suggestions:

 Post offices and their POAs must be available in order for users to access their GroupWise

mailboxes. Therefore, post offices and their POAs are excellent candidates for the high availability provided by clustering.

 In a like manner, WebAccess provides user access to GroupWise mailboxes across the Internet

through users’ Web browsers. It is another good candidate for clustering.

 Domains and their MTAs are less noticeable to users when they are unavailable (unless users in

different post offices happen to be actively engaged in an e-mail discussion when the MTA goes down). On the other hand, domains and their MTAs are critical to GroupWise administrators, although administrators might be more tolerant of a down server than end users are. Critical domains in your system would be the primary domain and, if you have one, a hub or routing domain. These domains should be in the cluster, even if other domains are not.

novdocx (en) 11 July 2008

 The Internet Agent might or might not require high availability in your GroupWise system,

depending on the importance of immediate messaging across the Internet and the use of POP3 or IMAP4 clients by GroupWise users.

There is no right or wrong way to implement GroupWise in a clustering environment. It all depends on the specific needs of your particular GroupWise system and its users.

2.3 Planning a New Clustered Domain

The considerations involved in planning a new domain in a clustering environment are essentially the same as for any other environment.

 Primary Domain: If you are setting up a new GroupWise system in a clustering environment,

you will be creating the primary domain as you complete the tasks in this section. In preparation, review “Planning Your Basic GroupWise System”, then print and fill out the “Basic GroupWise System Worksheet” in “Installing a Basic GroupWise System” in the

GroupWise 7 Installation Guide. This covers planning the primary domain and an initial post

office in the primary domain.

 Secondary Domain: If your GroupWise system already exists, you will be creating a new

secondary domain. In preparation, review “Planning a New Domain”, then print and fill out the “Domain Worksheet” in “Domains” in the GroupWise 7 Administration Guide.

Planning GroupWise in a NetWare Cluster 25

Regardless of the type of domain you are creating, keep in mind the following cluster-specific details as you fill out the worksheet you need:

 When you specify the location for the domain directory (and for a new GroupWise system, the

post office directory) on the worksheet, include the shared volume where you want the directory to reside.

 Do not concern yourself with the GroupWise agent information on the worksheet. You will

plan the agent installation later. If you are filling out the Basic GroupWise System Worksheet, stop with item 17. If you are filling out the Domain Worksheet, stop with item 10.

When you have completed the worksheet, transfer the key information from the Basic GroupWise System Worksheet or the Domain Worksheet to the System Clustering Worksheet.

SYSTEM CLUSTERING WORKSHEET

Under Item 10: Domain Name, transfer the domain name and database directory to the System Clustering Worksheet.

Under Item 7: Shared Volume for Domain, transfer the domain location to the System Clustering Worksheet. You will fill out the rest of the information under item 7 later.

novdocx (en) 11 July 2008

IMPORTANT: Do not create the new domain until you are instructed to do so in Chapter 3,

“Setting Up a Domain and Post Office in a NetWare Cluster,” on page 43.

2.4 Planning a New Clustered Post Office

The considerations involved in planning a new post office in a clustering environment are essentially the same as for any other environment. The initial post office in a new GroupWise system is planned on the Basic GroupWise System Worksheet. To plan additional new post offices, review “Planning a New Post Office ”, then print and fill out the “Post Office Worksheet” in “Post

Offices” in the GroupWise 7 Administration Guide. When you specify the locations for the post

office directories, include the shared volumes where you want the post office directories to reside.

When you have completed the worksheet, transfer key information from the Basic GroupWise System Worksheet or the Post Office Worksheet to the System Clustering Worksheet.

SYSTEM CLUSTERING WORKSHEET

Under Item 11: Post Office Name, transfer the post office name and database location to the System Clustering Worksheet.

If you will create the post office on a different shared volume from where the domain is located, under

Item 8: Shared Volume for Post Office, transfer the post office location to the System Clustering

Worksheet. You will fill out the rest of the information under item 8 later.

IMPORTANT: Do not create the new post office until you are instructed to do so in Chapter 3,

“Setting Up a Domain and Post Office in a NetWare Cluster,” on page 43.

26 GroupWise 7 Interoperability Guide

2.5 Planning a New Library for a Clustered Post Office

The considerations involved in planning a new library in a clustering environment are essentially the same as for any other environment. You can plan a library for a clustered post office by following the standard instructions provided in “Creating and Managing Libraries” in the GroupWise 7

Administration Guide and filling out the “Basic Library Worksheet” or the “Full-Service Library

Worksh ee t”. Then provide the library information on the System Clustering Worksheet.

SYSTEM CLUSTERING WORKSHEET

Under Item 14: Library Location, mark where you want to create the library’s document storage area.

If the document storage area will be located outside the post office directory structure, specify a user name and password that the POA can use to access the volume where the document storage area will reside.

IMPORTANT: Do not create the new library until you are instructed to do so in Chapter 3, “Setting

Up a Domain and Post Office in a NetWare Cluster,” on page 43.

novdocx (en) 11 July 2008

2.6 Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise

Cluster-enabling the shared volumes where domains and post offices reside greatly simplifies GroupWise administration. If you are creating a new GroupWise system, you might also want to cluster-enable shared volumes for the GroupWise administration snap-ins to ConsoleOne the GroupWise software distribution directory so that these locations are always available within the cluster. To review the concept of cluster-enabled shared volumes, see the applicable section of clustering documentation for your version of NetWare, as listed in Chapter 1, “Introduction to

GroupWise 7 and Novell Cluster Services on NetWare,” on page 21.

The advantages of cluster-enabling GroupWise volumes include:

 Drive mappings always occur through the virtual server associated with the cluster-enabled

volume, rather than through a physical server. This guarantees that you can always map a drive to the domain or post office database no matter which node it is currently located on.

 The GroupWise snap-ins to ConsoleOne always work no matter which node is running

ConsoleOne.

 Cluster-enabling the domain volume and installing the GroupWise agents to this volume

guarantees that the GroupWise snap-ins to ConsoleOne can always find the configuration files that they need to access.

 When you rebuild a domain database or a post office database, you do not need to determine

which node the database is currently located on.

 Help desk personnel do not need to be trained to determine where GroupWise is running before

they connect to a domain to create a new GroupWise user.

and for

When you cluster-enable a volume, additional eDirectory objects are created:

Planning GroupWise in a NetWare Cluster 27

Table 2-1 eDirectory Objects Used in a Cluster

novdocx (en) 11 July 2008

eDirectory Object

Object Name and Description

clustername_volumename (default object name) A new Volume object represents the cluster-enabled volume. It is created by renaming the original Volume object that was tied to a physical server and associating it with a virtual server instead.

For example, if your cluster name is GWCLUSTER and your original volume name is gwvol1, the new Volume object representing the cluster-enabled volume is named gwcluster_gwvol1.

clustername_volumename_SERVER (default object name) A new Server object represents the virtual server to which the new cluster-enabled volume is tied.

Continuing with the above example, the new Server object representing the virtual server is named GWCLUSTER_GWVOL1_SERVER.

volumename_SERVER.clustername (default object name) A new Volume Resource object stores property information for the cluster-enabled volume, such as start, failover, and failback mode information and load/unload scripts. These modes and scripts enable the cluster-enabled volume to function much like an independent server; hence, the SERVER portion of its name. The Volume Resource object is created in the Cluster container object.

Continuing with the above example, the new Volume Resource object is named GWVOL1_SERVER.GWCLUSTER.

IMPORTANT: Notice that the default object names include the underscore (_) character. Some DNS name servers cannot resolve object names that include underscore characters. If you have met the system requirements described in Section 2.1, “Meeting Software Version Requirements,” on

page 24, you can rename these objects as needed when you cluster enable the volume.

Cluster-enabling the shared volumes used by GroupWise is highly recommended. Throughout the rest of this document, the term “GroupWise volume” means “a cluster-enabled shared volume used by GroupWise.”

SYSTEM CLUSTERING WORKSHEET

Under Item 6: Shared Volumes for GroupWise Administration, list any shared volumes you want to use for GroupWise administration purposes. For example, you might have a shared pub: volume with a public directory where you install the GroupWise snap-ins to ConsoleOne instead of installing them on multiple administrator workstations. You might have a shared apps: volume where you create the GroupWise software distribution directory. Mark whether or not you want to cluster-enable the GroupWise administration volumes.

Under Item 7: Shared Volume for Domain, specify the name of the shared volume where you will create the domain. Mark whether or not you want to cluster-enable the domain volume. Also mark whether you will place the post office on the same volume with the domain.

If you want the post office on a different volume from where the domain is located, under Item 8:

Shared Volume for Post Office, specify the name of the shared volume where you will create the post

office. Mark whether or not you want to cluster-enable the post office volume.

28 GroupWise 7 Interoperability Guide

IMPORTANT: Because cluster-enabling the volumes where domains and post offices reside is so strongly recommended, this documentation does not include the steps for setting up domains and post offices on non-cluster-enabled volumes. If you decide not to cluster-enable GroupWise volumes, you should adjust the steps presented in this documentation for your system’s specialized needs. Novell Cluster Services does provide a GroupWise Mail Server template for use when creating GroupWise Cluster Resource objects instead of cluster-enabled Volume Resource objects.

2.7 Ensuring Successful Name Resolution for GroupWise Volumes

Because you are using cluster-enabled volumes for GroupWise domains and post offices, you must ensure that short name resolution is always successful. For example, in ConsoleOne, if you rightclick a Domain object in the GroupWise View and then click Connect, ConsoleOne must be able to resolve the domain database location, as provided in the UNC Path field, to the network address of the current, physical location of that domain within your cluster. It is through short name resolution that all GroupWise cluster resources (such as domain and post office volumes) are accessed and managed in ConsoleOne.

novdocx (en) 11 July 2008

A client program (such as ConsoleOne) that runs on a Windows* workstation, can be configured to use several different short name resolution methods. To see which methods are in use at a particular workstation, view the protocol preferences for the Novell Client workstation:

Figure 2-1 Novell Client Preferences Property Page

that is installed on the Windows

Short name resolution methods that pertain to clustering your GroupWise system are discussed below:

Planning GroupWise in a NetWare Cluster 29

Table 2-2 Short Name Resolution Methods

Short Name Resolution Method Description

eDirectory You can use eDirectory to resolve short names into specific network addresses. However,

when using eDirectory for short name resolution, you must remember to consider current context in the name resolution process. eDirectory short name resolution works only if your current context is the same as the context of the eDirectory object you need to access.

novdocx (en) 11 July 2008

Hosts File

Windows uses the following files when performing short name resolution at the workstation:

 Windows 2000/XP/2003:

\winnt\system32\drivers\etc\hosts

Using these files at the Windows workstation is not a preferred method for TCP/IP name resolution (except perhaps for the administrator’s workstation).

However, whenever you cluster-enable a volume, you should add its virtual server to the sys:\etc\hosts file of all nodes in the cluster.

DNS Perhaps the most common short name resolution option is Domain Name Service (DNS).

As with the hosts file, it is good practice to place all of your virtual servers into DNS.

For short name resolution to work using DNS, the client workstation must either belong to the same DNS zone (such as provo.novell.com) as the cluster resource, or the cluster resource zone must be configured in the client’s DNS suffix search path under TCP/IP settings for the workstation.

The underscore (_) character is part of default cluster-related object names. Because it is not supported by the DNS RFC, some DNS name servers cannot resolve default clusterrelated object names. If you are using such a DNS name server on NetWare 5.1, make sure you have installed the latest Novell Cluster Services snap-in to ConsoleOne, so that you can change cluster-related object names as needed to remove the underscore characters.

SLP NetWare 6.x and NetWare 5.1 both use Service Location Protocol (SLP) to advertise

service information across TCP/IP-based networks, which provides short name resolution of TCP/IP-based cluster resources within the network. On NetWare 6.x, Novell Cluster Services propagates virtual server information into SLP by default.

On NetWare 5.1, Novell Cluster Services does not propagate virtual server information into SLP by default. If you want to propagate virtual server information to SLP on NetWare 5.1, you can run the (unsupported) CVSBIND utility, which gives you reliable short name resolution within your cluster regardless of shortcomings you might encounter with other name resolution methods.

Specific setup instructions for each of these short name resolution methods will be provided in

Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,” on page 43.

30 GroupWise 7 Interoperability Guide

+ 455 hidden pages

Novell GROUPWISE 7 Interoperability Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

GroupWise 7 Interoperability Guide

About This Guide

Introduction to GroupWise 7 and Novell Cluster Services on NetWare

Planning GroupWise in a NetWare Cluster

2.1 Meeting Software Version Requirements

2.2 Installing Novell Cluster Services

2.3 Planning a New Clustered Domain

2.4 Planning a New Clustered Post Office

2.5 Planning a New Library for a Clustered Post Office

2.6 Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise

2.7 Ensuring Successful Name Resolution for GroupWise Volumes