Novell GROUPWISE 8 Interoperability Guide
Interoperability Guide
Novell®
novdocx (en) 22 June 2009
AUTHORIZED DOCUMENTATION
GroupWise
8
August 31, 2009
®
www.novell.com
GroupWise 8 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) 22 June 2009
Copyright © 2003-2009 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) 22 June 2009
novdocx (en) 22 June 2009
4 GroupWise 8 Interoperability Guide
Contents
About This Guide 15
Part I Novell Cluster Services on NetWare 17
1 Introduction to GroupWise 8 and Novell Cluster Services on NetWare 19
2 Planning GroupWise in a NetWare Cluster 21
2.1 Meeting Software Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2 Installing Novell Cluster Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5 Planning a New Library for a Clustered Post Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.6 Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise . . . . . . . . . . . 25
2.7 Ensuring Successful Name Resolution for GroupWise Volumes . . . . . . . . . . . . . . . . . . . . . . . 27
2.8 Deciding How to Install and Configure the Agents in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 28
2.8.1 Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the
Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.8.2 Determining Appropriate Failover Paths for the Agents . . . . . . . . . . . . . . . . . . . . . . 31
2.8.3 Deciding Where to Install the Agent Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.8.4 Deciding Whether to Run the Agents in Protected Memory . . . . . . . . . . . . . . . . . . . 34
2.8.5 Planning the NetWare Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.9 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.9.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.9.2 IP Address Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.9.3 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
novdocx (en) 22 June 2009
3 Setting Up a Domain and Post Office in a NetWare Cluster 41
3.1 Preparing the Cluster for GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.1 Ensuring Required Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.2 Cluster-Enabling Shared Volumes for Use with GroupWise . . . . . . . . . . . . . . . . . . . 41
3.1.3 Configuring Short Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2 Setting Up a New GroupWise System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3 Creating a New Secondary Domain in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.4 Creating a New Post Office in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5.1 Installing the Agent Software in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5.2 Editing Clustered Agent Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.5.3 Configuring the GroupWise Volume Resource to Load and Unload the Agents . . . . 50
3.5.4 Setting Up New Instances of the Agents without Installing the Agent Software . . . . 54
3.6 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.7.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . . 57
3.7.2 Using Novell Remote Manager on NetWare 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.7.3 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . . 61
3.8 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.9 Clustering Quick Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.9.1 GroupWise System Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Contents 5
3.9.2 Domain Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.9.3 Post Office Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4 Implementing the Internet Agent in a NetWare Cluster 67
4.1 Planning the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.1.2 Deciding Whether to Cluster-Enable the Internet Agent Volume. . . . . . . . . . . . . . . . 68
4.1.3 Determining an Appropriate Failover Path for the Internet Agent Volume. . . . . . . . . 68
4.1.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the Internet
Agent and Its MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.1.5 Preparing Your Firewall for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.1.6 Deciding Where to Install the Internet Agent and Its MTA. . . . . . . . . . . . . . . . . . . . . 70
4.1.7 Deciding Whether to Run the Internet Agent and Its MTA in Protected Memory. . . . 70
4.1.8 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.9 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.2 Setting Up the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.2.1 Cluster-Enabling a Shared Volume for Use with the Internet Agent . . . . . . . . . . . . . 71
4.2.2 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.2.3 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.2.4 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . 72
4.2.5 Testing the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.3 Managing the Internet Agent in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.3.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . . 81
4.3.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . . 82
4.4 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.5 Internet Agent Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
novdocx (en) 22 June 2009
5 Implementing WebAccess in a NetWare Cluster 85
5.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.2 Planning WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.2.1 Planning a New Domain for the WebAccess Agent. . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.2.2 Deciding Whether to Cluster-Enable the WebAccess Agent Volume . . . . . . . . . . . . 86
5.2.3 Determining an Appropriate Failover Path for the WebAccess Agent Volume . . . . . 87
5.2.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the
WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.2.5 Deciding Where to Install the WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . . 87
5.2.6 Deciding Whether to Run the WebAccess Agent and Its MTA in Protected Memory 88
5.2.7 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2.8 Planning the WebAccess Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.3 Setting Up WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.3.1 Cluster-Enabling a Shared Volume for Use with the WebAccess Agent . . . . . . . . . . 89
5.3.2 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
5.3.3 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . 90
5.3.4 Installing and Configuring the WebAccess Agent in a Cluster. . . . . . . . . . . . . . . . . . 90
5.3.5 Testing Your Clustered WebAccess Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.4 Managing WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . . 97
5.4.2 Knowing What to Expect in WebAccess Failover Situations . . . . . . . . . . . . . . . . . . . 98
5.4.3 Updating the WebAccess Agent Configuration File (commgr.cfg). . . . . . . . . . . . . . . 98
5.5 WebAccess Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.6 WebAccess Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6 GroupWise 8 Interoperability Guide
6 Implementing GroupWise Gateways in a NetWare Cluster 103
7 Monitoring a GroupWise System in a NetWare Cluster 105
8 Backing Up a GroupWise System in a NetWare Cluster 107
9 Updating a GroupWise System in a NetWare Cluster 109
10 Moving an Existing GroupWise 8 System into a NetWare Cluster 111
11 Implementing Messenger in a NetWare Cluster 113
11.1 Planning Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
11.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
11.1.2 Planning Messenger Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
11.1.3 Deciding Where to Install the Messenger Agent Software . . . . . . . . . . . . . . . . . . . 114
11.1.4 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
11.2 Setting Up Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
11.2.1 Installing to Each Node in the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.2.2 Installing to a Messenger Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.3 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
novdocx (en) 22 June 2009
Part II Novell Cluster Services on Linux 123
12 Introduction to GroupWise 8 and Novell Cluster Services on Linux 125
13 Planning GroupWise in a Linux Cluster 127
13.1 Installing Novell Cluster Services on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
13.2 Planning a Clustered Software Distribution Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13.3 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
13.4 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
13.5 Planning a New Library for a Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
13.6 Deciding How to Install and Configure the Linux Agents in a Cluster . . . . . . . . . . . . . . . . . . 132
13.6.1 Recording Secondary IP Addresses for the Agents . . . . . . . . . . . . . . . . . . . . . . . . 132
13.6.2 Determining Appropriate Failover Lists for the Agents . . . . . . . . . . . . . . . . . . . . . . 132
13.6.3 Determining Cluster Resource Information for the Linux Agents. . . . . . . . . . . . . . . 133
13.6.4 Planning the Linux Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
13.7 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
13.7.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
13.7.2 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
14 Setting Up a Domain and a Post Office in a Linux Cluster 137
14.1 Setting Up a New GroupWise System in a Linux Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
14.2 Creating a New Secondary Domain in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
14.3 Creating a New Post Office in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
14.4 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 140
14.4.1 Installing and Setting Up the Agents in Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . 140
14.4.2 Changing Agent Paths to Locations on GroupWise Partitions . . . . . . . . . . . . . . . . 144
14.4.3 Configuring GroupWise Cluster Resources to Load and Unload the Agents . . . . . 146
14.4.4 Setting Up New Instances of the Agents without Installing the Agent Software . . . 152
Contents 7
14.5 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
14.6 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
14.6.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 155
14.6.2 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . 157
14.7 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
14.8 Clustering Quick Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
14.8.1 GroupWise System Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
14.8.2 Domain Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
14.8.3 Post Office Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
15 Implementing the Internet Agent in a Linux Cluster 161
15.1 Planning the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
15.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
15.1.2 Selecting the Internet Agent Partition and Secondary IP Address . . . . . . . . . . . . . 162
15.1.3 Determining an Appropriate Failover List for the Internet Agent . . . . . . . . . . . . . . . 163
15.1.4 Determining Cluster Resource Information for the Internet Agent . . . . . . . . . . . . . . 163
15.1.5 Preparing DNS for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
15.1.6 Preparing Your Firewall for the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . 163
15.1.7 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
15.1.8 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
15.2 Setting Up the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.2.1 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.2.2 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.2.3 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . 165
15.3 Testing the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
15.4 Managing the Internet Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
15.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 177
15.4.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . 178
15.5 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
15.6 Internet Agent Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
novdocx (en) 22 June 2009
16 Implementing WebAccess in a Linux Cluster 181
16.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
16.2 Planning the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
16.2.1 Planning a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
16.2.2 Selecting the WebAccess Agent Partition and Secondary IP Address . . . . . . . . . . 183
16.2.3 Determining an Appropriate Failover List for the WebAccess Agent . . . . . . . . . . . . 183
16.2.4 Determining Cluster Resource Information for the WebAccess Agent . . . . . . . . . . 183
16.2.5 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
16.2.6 Planning the WebAccess Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
16.2.7 Planning the WebAccess Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 184
16.3 Setting Up the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
16.3.1 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
16.3.2 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . 185
16.3.3 Installing and Configuring the WebAccess Agent in a Cluster. . . . . . . . . . . . . . . . . 185
16.3.4 Installing and Configuring the WebAccess Application in a Cluster . . . . . . . . . . . . 194
16.4 Testing the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
16.5 Managing the WebAccess Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
16.5.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 196
16.5.2 Knowing What to Expect in a WebAccess Agent Failover Situation . . . . . . . . . . . . 197
16.6 WebAccess Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
16.7 WebAccess Agent Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
8 GroupWise 8 Interoperability Guide
17 Implementing GroupWise Monitor in a Linux Cluster 201
17.1 Understanding the Monitor Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
17.2 Planning GroupWise Monitor in a Linux Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
17.2.1 Selecting a Domain for Access during Monitor Agent Installation . . . . . . . . . . . . . . 202
17.2.2 Selecting an MTA for the Monitor Agent to Access after Installation. . . . . . . . . . . . 202
17.2.3 Selecting the Monitor Agent Partition and Secondary IP Address. . . . . . . . . . . . . . 203
17.2.4 Determining an Appropriate Failover List for the Monitor Agent . . . . . . . . . . . . . . . 203
17.2.5 Determining Cluster Resource Information for the Monitor Agent . . . . . . . . . . . . . . 203
17.2.6 Planning the Monitor Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
17.3 Setting Up GroupWise Monitor in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
17.3.1 Installing and Configuring the Monitor Agent on Each Node in Your Cluster . . . . . 204
17.3.2 Configuring the Monitor Agent Cluster Resource to Load and Unload the Monitor
Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
17.4 Testing the Monitor Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
17.5 Managing the Monitor Agent in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
17.6 Monitor Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
17.7 Monitor Agent Quick Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
18 Backing Up a GroupWise System in a Linux Cluster 215
novdocx (en) 22 June 2009
19 Updating a GroupWise System in a Linux Cluster 217
20 Moving an Existing Linux GroupWise 8 System into a Linux Cluster 219
21 Moving a Clustered GroupWise 8 System from NetWare to Linux 221
22 Implementing Messenger in a Linux Cluster 223
22.1 Planning Your Messenger System in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
22.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
22.1.2 Selecting the Messenger Partition and Secondary IP Address . . . . . . . . . . . . . . . . 224
22.1.3 Determining an Appropriate Failover List for the Messenger Agents . . . . . . . . . . . 224
22.1.4 Determining Cluster Resource Information for the Messenger Agents . . . . . . . . . . 224
22.1.5 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
22.2 Setting Up Your Messenger System in a Linux Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
22.2.1 Creating Your Messenger System and Installing the Messenger Agents . . . . . . . . 225
22.2.2 Changing Messenger Paths to Locations on the Messenger Partition . . . . . . . . . . 227
22.2.3 Configuring the Messenger Cluster Resource to Load and Unload the Messenger
Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
22.3 Testing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
22.4 Managing Your Clustered Messenger System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
22.5 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
22.6 Messenger Clustering Quick Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Part III Novell Teaming and Conferencing 237
23 Using GroupWise with Novell Teaming 239
23.1 Understanding How Novell Teaming Interacts with eDirectory and GroupWise . . . . . . . . . . 239
23.2 Using eDirectory as the Teaming LDAP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
23.3 Using GroupWise as the Teaming E-Mail System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
23.4 Enabling GroupWise/Teaming Integration for GroupWise Windows Client Users . . . . . . . . . 240
Contents 9
23.5 Accessing Teaming from the GroupWise Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
23.5.1 Accessing Teaming through the Novell Teaming Folder . . . . . . . . . . . . . . . . . . . . . 242
23.5.2 Accessing Teaming from a GroupWise Web Panel. . . . . . . . . . . . . . . . . . . . . . . . . 242
24 Using GroupWise with Conferencing 243
24.1 Configuring GroupWise as the Conferencing E-Mail System. . . . . . . . . . . . . . . . . . . . . . . . . 243
24.1.1 Preparing for GroupWise Integration with Conferencing . . . . . . . . . . . . . . . . . . . . . 243
24.1.2 Integrating GroupWise with Novell Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . 243
24.1.3 Testing GroupWise as the Novell Conferencing E-Mail System . . . . . . . . . . . . . . . 244
25 Streamlining Authentication to Teaming or Conferencing 245
25.1 Using iChain for Authenticating to Teaming or Conferencing . . . . . . . . . . . . . . . . . . . . . . . . 245
25.1.1 Meeting iChain Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
25.1.2 Setting Up an iChain Web Server Accelerator for Teaming or Conferencing . . . . . 245
25.1.3 Adding the New Web Server Accelerator to the iChain Server Object in
ConsoleOne. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
25.1.4 Using iChain for Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
25.2 Using Novell Access Manager for Authenticating to Teaming or Conferencing. . . . . . . . . . . 247
novdocx (en) 22 June 2009
Part IV Novell ZENworks 249
26 Using ZENworks Desktop Management to Distribute the GroupWise Windows
Client 251
26.1 Creating a GroupWise Client Application Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
26.2 Using GroupWise 8 Tuner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
26.3 Configuring ZENworks to Use a Transform File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
27 Using ZENworks Linux Management to Distribute the GroupWise Linux/Mac
Client 259
28 ZENworks Application Virtualization for GroupWise and Messenger 261
Part V Other Novell Products 263
29 GroupWise DirXML Driver for Novell Identity Manager 265
29.1 Identity Manager Warnings in ConsoleOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
29.1.1 Recovering a Deleted GroupWise Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
29.1.2 Grafting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
29.1.3 Converting an External Entity to a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
29.1.4 Converting a User to an External Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
29.1.5 Associating a GroupWise Object with an eDirectory Object . . . . . . . . . . . . . . . . . . 266
29.1.6 Disassociating a GroupWise Object’s Attributes from an eDirectory Object . . . . . . 266
29.1.7 Resolving an Invalid Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
29.1.8 Disabling the DirXML Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
29.1.9 Enabling the DirXML Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
10 GroupWise 8 Interoperability Guide
30 GroupWise Customization Tools 269
31 Novell exteNd 271
Part VI Microsoft Clustering Services on Windows 273
32 Introduction to GroupWise 8 and Microsoft Clusters 275
33 Planning GroupWise in a Microsoft Cluster 277
33.1 Setting Up Your Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
33.2 Planning a New Clustered Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
33.3 Planning a New Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
33.4 Planning a New Library for a Clustered Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
33.5 Planning GroupWise Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
33.6 Planning Shared Administrative Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
33.7 Ensuring Successful Name Resolution for GroupWise Resource Groups. . . . . . . . . . . . . . . 281
33.8 Deciding How to Install and Configure the Agents in a Cluster . . . . . . . . . . . . . . . . . . . . . . . 283
33.8.1 Planning Cluster-Unique Port Numbers for Agents in the Cluster . . . . . . . . . . . . . . 283
33.8.2 Deciding Where to Install the Agent Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
33.8.3 Planning the Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
33.8.4 Planning the Windows Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
33.9 GroupWise Clustering Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
33.9.1 System Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
33.9.2 Network Address Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
33.9.3 Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
novdocx (en) 22 June 2009
34 Setting Up a Domain and Post Office in a Microsoft Cluster 293
34.1 Preparing the Cluster for GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
34.1.1 Creating GroupWise Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
34.1.2 Creating Agent Service Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
34.1.3 Configuring Short Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
34.2 Setting Up a New GroupWise System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
34.3 Creating a New Secondary Domain in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
34.4 Creating a New Post Office in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
34.5 Installing and Configuring the MTA and the POA in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . 298
34.5.1 Installing the Agent Software in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
34.5.2 Editing Clustered Agent Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
34.5.3 Setting Up New Instances of the Agents without Installing the Agent Software . . . 300
34.6 Testing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
34.7 Managing Your Clustered GroupWise System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
34.7.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 301
34.7.2 Knowing What to Expect in MTA and POA Failover Situations . . . . . . . . . . . . . . . . 302
34.8 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
35 Implementing the Internet Agent in a Microsoft Cluster 305
35.1 Planning the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
35.1.1 Planning a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
35.1.2 Planning the Internet Agent Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
35.1.3 Planning Cluster-Unique Port Numbers for the Internet Agent and Its MTA . . . . . . 306
35.1.4 Preparing Your Firewall for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Contents 11
35.1.5 Deciding Where to Install the Internet Agent and Its MTA . . . . . . . . . . . . . . . . . . . . 307
35.1.6 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
35.1.7 Planning the Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
35.2 Setting Up the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
35.2.1 Setting Up the Internet Agent Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
35.2.2 Creating a Domain for the Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
35.2.3 Installing the MTA for the Internet Agent Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 309
35.2.4 Installing and Configuring the Internet Agent in a Cluster . . . . . . . . . . . . . . . . . . . . 309
35.2.5 Testing the Clustered Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
35.3 Managing the Internet Agent in a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
35.3.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 312
35.3.2 Knowing What to Expect in an Internet Agent Failover Situation . . . . . . . . . . . . . . 313
35.4 Internet Agent Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
36 Implementing WebAccess in a Microsoft Cluster 315
36.1 Understanding the WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
36.2 Planning WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
36.2.1 Setting Up Your Web Server in the Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . 316
36.2.2 Planning a New Domain for the WebAccess Agent. . . . . . . . . . . . . . . . . . . . . . . . . 316
36.2.3 Planning the WebAccess Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
36.2.4 Planning Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA. . . 317
36.2.5 Deciding Where to Install the WebAccess Agent and Its MTA . . . . . . . . . . . . . . . . 318
36.2.6 Planning the MTA Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
36.2.7 Planning the WebAccess Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
36.3 Setting Up WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
36.3.1 Setting Up the WebAccess Resource Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
36.3.2 Creating a Domain for the WebAccess Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
36.3.3 Installing the MTA for the WebAccess Agent Domain . . . . . . . . . . . . . . . . . . . . . . . 320
36.3.4 Installing the WebAccess Agent in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
36.3.5 Installing and Configuring the WebAccess Application in a Cluster . . . . . . . . . . . . 321
36.3.6 Testing Your Clustered WebAccess Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
36.4 Managing WebAccess in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
36.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions . . . . . . . . . . . . . . 323
36.4.2 Knowing What to Expect in WebAccess Failover Situations . . . . . . . . . . . . . . . . . . 324
36.4.3 Updating the WebAccess Agent Configuration File (commgr.cfg). . . . . . . . . . . . . . 324
36.5 WebAccess Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
novdocx (en) 22 June 2009
37 Implementing GroupWise Gateways in a Microsoft Cluster 327
38 Monitoring a GroupWise System in a Microsoft Cluster 329
39 Backing Up a GroupWise System in a Microsoft Cluster 331
40 Moving an Existing GroupWise 8 System into a Microsoft Cluster 333
41 Implementing Messenger in a Microsoft Cluster 335
41.1 Planning Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
41.1.1 Understanding Your Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
41.1.2 Planning Messenger Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
41.1.3 Deciding Where to Install the Messenger Agent Software . . . . . . . . . . . . . . . . . . . 336
41.1.4 Planning the Messenger Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
41.2 Setting Up Your Messenger System in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
12 GroupWise 8 Interoperability Guide
41.2.1 Installing the Messenger Agents to Each Node in the Cluster. . . . . . . . . . . . . . . . . 338
41.2.2 Installing the Messenger Agents to a Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . 338
41.3 Messenger Clustering Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Part VII Non-GroupWise Clients 341
42 Outlook Express 343
43 Microsoft Outlook 345
44 Evolution 347
44.1 GroupWise Features Available in Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
44.2 Configuring Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Part VIII Mobile Devices 351
45 GroupWise Mobile Server, Powered by Intellisync 353
novdocx (en) 22 June 2009
46 BlackBerry Enterprise Server 355
Part IX Documentation Updates 357
A August 31, 2009 (GroupWise 8 SP1) 359
Contents 13
novdocx (en) 22 June 2009
14 GroupWise 8 Interoperability Guide
About This Guide
This Novell® GroupWise® 8 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 “Novell Cluster Services on NetWare” on page 17
“Novell Cluster Services on Linux” on page 123
“Novell Teaming and Conferencing” on page 237
“Novell ZENworks” on page 249
“Other Novell Products” on page 263
novdocx (en) 22 June 2009
Third-Party Products
For information about additional GroupWise-related software from GroupWise partners, see the
Novell Partner Product Guide (http://www.novell.com/partnerguide).
For troubleshooting assistance, see:
GroupWise 8 Troubleshooting 1: Error Messages
GroupWise 8 Troubleshooting 2: Solutions to Common Problems
GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure
Novell Support and Knowledgebase (http://www.novell.com/support)
To search the GroupWise documentation from the Novell Support Web site, click Advanced
Search, select Documentation in the Search In drop-down list, select GroupWise in the
Products drop-down list, type the search string, then click Search.
GroupWise 8 Support Forums (http://forums.novell.com/novell-product-support-forums/
groupwise)
GroupWise Support Community (http://www.novell.com/support/products/groupwise)
GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)
“Microsoft Clustering Services on Windows” on page 273
“Non-GroupWise Clients” on page 341
“Mobile Devices” on page 351
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.
About This Guide 15
Documentation Updates
For the most recent version of the GroupWise 8 Interoperability Guide, visit the Novell GroupWise
8 documentation Web site (http://www.novell.com/documentation/gw8).
Additional Documentation
For additional GroupWise documentation, see the following guides at the Novell GroupWise 8
documentation Web site (http://www.novell.com/documentation/gw8):
Installation Guide
Administration Guide
Multi-System Administration Guide
Troubleshooting Guides
GroupWise Client User Guides
GroupWise Client Frequently Asked Questions (FAQ)
Documentation Conventions
novdocx (en) 22 June 2009
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 (TM, ®, 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.
16 GroupWise 8 Interoperability Guide
I
Novell Cluster Services on
NetWare
Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on
page 19
Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 21
Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,” on page 41
Chapter 4, “Implementing the Internet Agent in a NetWare Cluster,” on page 67
Chapter 5, “Implementing WebAccess in a NetWare Cluster,” on page 85
Chapter 6, “Implementing GroupWise Gateways in a NetWare Cluster,” on page 103
Chapter 7, “Monitoring a GroupWise System in a NetWare Cluster,” on page 105
Chapter 8, “Backing Up a GroupWise System in a NetWare Cluster,” on page 107
Chapter 9, “Updating a GroupWise System in a NetWare Cluster,” on page 109
novdocx (en) 22 June 2009
Chapter 10, “Moving an Existing GroupWise 8 System into a NetWare Cluster,” on page 111
Chapter 11, “Implementing Messenger in a NetWare Cluster,” on page 113
Novell Cluster Services on NetWareI17
novdocx (en) 22 June 2009
18 GroupWise 8 Interoperability Guide
1
Introduction to GroupWise 8 and
novdocx (en) 22 June 2009
Novell Cluster Services on
NetWare
Before implementing GroupWise® 8 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)
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
1
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.
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.
Introduction to GroupWise 8 and Novell Cluster Services on NetWare
19
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) 22 June 2009
cluster-enabled shared volume: A shared volume for which a Volume Resource object has been
TM
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.
20 GroupWise 8 Interoperability Guide
2
Planning GroupWise in a NetWare
novdocx (en) 22 June 2009
Cluster
The majority of this part of the GroupWise 8 Interoperability Guide (Chapter 2, “Planning
GroupWise in a NetWare Cluster,” on page 21 through Chapter 8, “Backing Up a GroupWise
System in a NetWare Cluster,” on page 107) is designed for those who are creating a new
GroupWise
Services
a newly installed cluster, see Chapter 10, “Moving an Existing GroupWise 8 System into a NetWare
Cluster,” on page 111.
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 8 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
TM
. If you already have an existing GroupWise 8 system and need to configure it to work in
2
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
created
might or might not need to run the agents in protected memory.
The “System Clustering Worksheet” on page 35 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:
After you have completed the tasks and filled out “System Clustering Worksheet” on page 35, you
are ready to continue with Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”
on page 41.
vol:\system
Section 2.1, “Meeting Software Version Requirements,” on page 22
Section 2.2, “Installing Novell Cluster Services,” on page 22
Section 2.3, “Planning a New Clustered Domain,” on page 23
Section 2.4, “Planning a New Clustered Post Office,” on page 24
Section 2.5, “Planning a New Library for a Clustered Post Office,” on page 25
Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes Used by GroupWise,”
on page 25
Section 2.7, “Ensuring Successful Name Resolution for GroupWise Volumes,” on page 27
Section 2.8, “Deciding How to Install and Configure the Agents in a Cluster,” on page 28
Section 2.9, “GroupWise Clustering Worksheets,” on page 35
directories on shared volumes where domains and post offices reside. You
sys:\system
directories or to manually
Planning GroupWise in a NetWare Cluster
21
2.1 Meeting Software Version Requirements
GroupWise 8 can be clustered on a system that meets the following requirements:
GroupWise 8
A supported version of NetWare
OES NetWare
NetWare 6.5
®
with the latest Support Pack
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.
2.2 Installing Novell Cluster Services
novdocx (en) 22 June 2009
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 8 and Novell Cluster
Services on NetWare,” on page 19.
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
TM
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.
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.
22 GroupWise 8 Interoperability Guide
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.
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.
novdocx (en) 22 June 2009
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 a Basic GroupWise System”, then print and fill out the “Basic
GroupWise System Summary Sheet” in “Installing a Basic GroupWise System” in the
GroupWise 8 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 8 Administration Guide.
Planning GroupWise in a NetWare Cluster 23
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 Post Office Settings. If you are filling out the Domain Worksheet, stop with Domain
Administrator.
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) 22 June 2009
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 41.
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 8 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 41.
24 GroupWise 8 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 8
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 41.
novdocx (en) 22 June 2009
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 8 and Novell Cluster Services on NetWare,” on page 19.
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 25
Table 2-1 eDirectory Objects Used in a Cluster
novdocx (en) 22 June 2009
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 22, 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.
26 GroupWise 8 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) 22 June 2009
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
TM
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 27
Table 2-2 Short Name Resolution Methods
Short Name
Resolution
Method
eDirectory You can use eDirectory to resolve short names into specific network addresses.
Hosts File Windows uses the following files when performing short name resolution at the
Description
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.
workstation:
Windows XP\Vista:
\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.
novdocx (en) 22 June 2009
DNS Perhaps the most common short name resolution option is Domain Name Service (DNS).
As with the
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.
SLP NetWare 6.5 uses 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.5, Novell Cluster Services
propagates virtual server information into SLP by default.
hosts
file, it is good practice to place all of your virtual servers into DNS.
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 41.
2.8 Deciding How to Install and Configure the Agents in a Cluster
There are several cluster-specific issues to consider as you plan to install the NetWare MTA and
POA in your clustered GroupWise system:
Section 2.8.1, “Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents
in the Cluster,” on page 29
Section 2.8.2, “Determining Appropriate Failover Paths for the Agents,” on page 31
Section 2.8.3, “Deciding Where to Install the Agent Software,” on page 31
28 GroupWise 8 Interoperability Guide
Section 2.8.4, “Deciding Whether to Run the Agents in Protected Memory,” on page 34
Section 2.8.5, “Planning the NetWare Agent Installation,” on page 34
2.8.1 Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster
The GroupWise agents listen on all IP addresses, both primary and secondary, that are bound to the
server on their specified port numbers. This means that any time there is a possibility of two of the
same type of agent loading on the same node, it is important that each agent use a cluster-unique port
number, even though each agent is using a unique secondary IP address. The best way for you to
avoid port conflicts is to plan your cluster so that each agent in the cluster runs on a cluster-unique
port. Print out a copy of the “IP Address Worksheet” on page 37 to help you plan secondary IP
addresses and cluster-unique port numbers for all GroupWise agents.
The following filled-out version of the IP Address Worksheet illustrates one way this can be done:
Domain Information
novdocx (en) 22 June 2009
Domain
Provo1 172.16.5.81 7100 7180
MTA
IP Address
MTA
MTP Port
MTA
HTTP Port
Post Office Information
Post Office
Development (same as MTA) 1677 7101 7181
Manufacturing 172.16.5.82 1678 7102 7182
POA
IP Address
POA
C/S Port
POA
MTP Port
POA
HTTP Port
Internet Agent Information
Internet Agent
GWIA Domain
MTA
Internet Agent
(GWIA)
GWIA
IP Address
172.16.5.83 7110 7677 7183 N/A
(same as MTA) N/A N/A N/A 9850
MTA
MTP Port
MTA Live
Remote Port
MTA
HTTP
Port
GWIA
HTTP Port
Planning GroupWise in a NetWare Cluster 29
WebAccess Information
novdocx (en) 22 June 2009
WebAccess Agent
WebAccess
Domain MTA
WebAccess Agent
(GWINTER)
WebAccess
IP Address
172.16.5.84 7120 7184 N/A N/A
(same as MTA) N/A N/A 7205 7205
MTA
MTP Port
MTA
HTTP Port
WebAccess
Agent Port
WebAccess
HTTP Port
(same as agent)
This example places the Development post office on the same node and on the same GroupWise
volume with the Provo1 domain; therefore, the Provo1 MTA and the Development POA can use the
same secondary IP address. The Manufacturing post office is placed on a different node on a
different GroupWise volume, so that the Manufacturing post office has a different secondary IP
address.
The example also illustrates that the MTA, the POA, and the Internet Agent use different port
numbers for agent ports and HTTP ports. In contrast, the WebAccess Agent uses the same port
number for the agent port and the HTTP port.
The example uses default port numbers where possible. For example, the default MTA message
transfer port is 7100 and the default POA client/server port is 1677. Incrementing port numbers are
used in the example when multiple components have the same type of ports. For example, port
numbers 1677 and 1678 are both POA client/server ports and port numbers 7180 through 7184 are
all HTTP ports. Incrementing from the default port numbers generates unique, though related, port
numbers.
If you are going to set up a GroupWise name server to help GroupWise clients locate their post
offices, make sure that the default POA port number of 1677 is used somewhere in the cluster. For
more information, see “Simplifying Client/Server Access with a GroupWise Name Server” in “Post
Office Agent” in the GroupWise 8 Administration Guide.
IP ADDRESS WORKSHEET
Fill out the “IP Address Worksheet” on page 37 to help you plan secondary IP addresses and cluster-
unique port numbers for all GroupWise agents in the cluster. (MTA, POA, Internet Agent, WebAccess
Agent).
After you have filled out the IP Address Worksheet, transfer the secondary IP addresses and clusterunique port numbers from the IP Address Worksheet to the System Clustering Worksheet and the
Agent Clustering Worksheet so that they are available in the sequence in which you will need them
as you set up GroupWise in a cluster.
30 GroupWise 8 Interoperability Guide
Loading...