1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - INTEROPERABILITY GUIDE
  6. Manual

Novell GROUPWISE 7 - INTEROPERABILITY GUIDE Manual

Hide thumbs
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Interoperability Guide
Novell
®
GroupWise
®
7
June 25, 2008
www.novell.com
GroupWise 7 Interoperability Guide

Advertisement

Table of Contents
loading

Related Manuals for Novell GROUPWISE 7 - INTEROPERABILITY GUIDE

Summary of Contents for Novell GROUPWISE 7 - INTEROPERABILITY GUIDE

  • Page 1 AUTHORIZED DOCUMENTATION Interoperability Guide Novell ® GroupWise ® June 25, 2008 www.novell.com GroupWise 7 Interoperability Guide...
  • Page 2 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.
  • Page 3 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.

  • Page 5: Table Of Contents

    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 .
  • Page 6 3.9.2 Domain Quick Checklist..........66 3.9.3 Post Office Quick Checklist .
  • Page 7 Installing Novell Cluster Services on Linux ........
  • Page 8 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 .
  • Page 9 Messenger Clustering Quick Checklist......... . 241 Part III Novell Teaming and Conferencing 23 Using GroupWise with Novell Teaming 23.1 Understanding How Novell Teaming Interacts with eDirectory and GroupWise ..245 Contents...
  • Page 10 Preparing for the Novell Teaming Installation ......248 23.3.2 Performing the Novell Teaming Installation ....... 248 23.4 Configuring LDAP Authentication.
  • Page 11 27 GroupWise Customization Tools 28 Novell exteNd Part V Heartbeat on Linux 29 Introduction to GroupWise 7 and Heartbeat on Linux 29.1 Understanding Heartbeat ........... . 281 29.2...
  • Page 12 32 Setting Up a Domain and a Post Office in a Heartbeat Cluster 32.1 Setting Up a New GroupWise System in a Heartbeat Cluster ......307 32.2 Creating a New Secondary Domain in a Heartbeat Cluster .
  • Page 13 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 .
  • Page 14 42 Setting Up a Domain and Post Office in a Microsoft Cluster 42.1 Preparing the Cluster for GroupWise ......... . . 401 42.1.1 Creating GroupWise Resource Groups .
  • Page 15 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 .
  • Page 16 Part IX Documentation Updates A June 25, 2008 B March 14, 2008 (GroupWise 7 SP3) C October 24, 2007 D April 16, 2007 (GroupWise 7 SP 2) E September 29, 2006 F August 2, 2006 G June 15, 2006 (GroupWise 7 SP1) H November 30, 2005 GroupWise 7 Interoperability Guide...

  • Page 17: 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,”...
  • Page 18 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.

  • Page 19: Part I Novell Cluster Services On Netware

    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,”...
  • Page 20 GroupWise 7 Interoperability Guide...

  • Page 21: Introduction To Groupwise 7 And Novell Cluster Services On Netware

    Before implementing GroupWise 7 with Novell Cluster Services , 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/...
  • Page 22 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.

  • Page 23: Planning Groupwise In A Netware Cluster

    111) is designed for those who are creating a new ® ® GroupWise system, or at least new domains and post offices, in the context of Novell Cluster Services . If you already have an existing GroupWise 7 system and need to configure it to work in a newly installed cluster, see Chapter 10, “Moving an Existing GroupWise 7 System into a NetWare...

  • Page 24: Meeting Software Version Requirements

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

  • Page 25: Planning A New Clustered Domain

    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.

  • Page 26: Planning A New Clustered Post Office

    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.

  • Page 27: Planning A New Library For A Clustered Post Office

    NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page 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.
  • Page 28 eDirectory Objects Used in a Cluster Table 2-1 eDirectory Object Name and Description Object 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.

  • Page 29: Ensuring Successful Name Resolution For Groupwise 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.
  • Page 30 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.

  • Page 31: Deciding How To Install And Configure The Agents In A Cluster

    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,”...
  • Page 32 Internet Agent Information GWIA MTA Live GWIA Internet Agent HTTP IP Address MTP Port Remote Port HTTP Port Port GWIA Domain 172.16.5.83 7110 7677 7183 Internet Agent (same as MTA) 9850 (GWIA) WebAccess Information WebAccess WebAccess WebAccess WebAccess Agent IP Address MTP Port HTTP Port Agent Port...

  • Page 33: Determining Appropriate Failover Paths For The Agents

    After you have filled out the IP Address Worksheet, transfer the secondary IP addresses and cluster- unique 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.

  • Page 34: Deciding Where To Install The Agent Software

    2.8.3 Deciding Where to Install the Agent Software When you install the NetWare MTA and POA in a clustering environment, you can choose between two different installation locations: Agent Software Installation Locations Table 2-3 Location Description This is the default location provided by the Agent Installation program. Because sys:\system on each node the agents must be installed on each node where they might need to run during...
  • Page 35 If you ever need to add or replace a physical server in the cluster, you only need to install NetWare and Novell Cluster Services to the new server, then add that node to the appropriate failover paths. No extra GroupWise configuration is necessary because there are no sys:\system dependencies for the GroupWise agents.

  • Page 36: Deciding Whether To Run The Agents In Protected Memory

    2.8.4 Deciding Whether to Run the Agents in Protected Memory On a NetWare server, using protected memory allows you to create isolated memory spaces where programs can run without affecting other NLM programs running on the same node. This contributes to the high availability of the cluster. Using protected memory has the following advantages: When using protected memory, the node can restart a specific memory space if any NLM program within that memory space abends.

  • Page 37: Planning The Netware Agent Installation

    2.8.5 Planning the NetWare Agent Installation Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the GroupWise NetWare agents are the same in a clustering environment as for any other environment. Review “Planning the GroupWise Agents”, then print and fill out the...
  • Page 38 Item Explanation 2) eDirectory Tree for Cluster: Record the eDirectory tree where you created the new Novell Cluster object when you installed Novell Cluster Services. For more information, see Section 2.2, “Installing Novell Cluster Services,” on page 24 3) Cluster Name: Record the name of the new NetWare Cluster object that you created for your GroupWise system.
  • Page 39 Item Explanation 7) Shared Volume for Domain: Specify the name (cluster_volume) of the shared volume where the GroupWise domain will reside. Cluster Enabled? For cluster-enabling, specify the IP address of the virtual Yes (highly recommended) server (volume_SERVER.cluster) to which the cluster-enabled volume is tied.

  • Page 40: Ip Address Worksheet

    Item Explanation 12) Document Storage Area Location: If you need a library for a clustered post office, mark where you want to create its document storage area and provide a At the post office directory if necessary. Outside the post office For more information, see Section 2.5, “Planning a New Separate post office...

  • Page 41: Agent Clustering Worksheet

    WebAccess Information WebAccess WebAccess WebAccess WebAccess Agent IP Address MTP Port HTTP Port Agent Port HTTP Port WebAccess Domain MTA WebAccess (same) Agent (GWINTER) 2.9.3 Agent Clustering Worksheet Item Explanation 1) agent installation location: Mark the location where you will install the agent software.
  • Page 42 Item Explanation 7) POA Network Information: Gather the POA network address information from the “IP Address Worksheet” on page POA IP address For more information, see “Planning Secondary IP POA client/server port Addresses and Cluster-Unique Port Numbers for Agents POA message transfer port in the Cluster”...

  • Page 43: Setting Up A Domain And Post Office In A Netware Cluster

    2 Complete the steps in the cluster-enabling section of the cluster documentation for your version ® of NetWare , as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page Setting Up a Domain and Post Office in a NetWare Cluster...

  • Page 44: Configuring Short Name Resolution

    The System Clustering Worksheet provides the volume to cluster-enable for use the GroupWise, the cluster-enabled volume IP address, and the failover path for the GroupWise volume. For a review of the new Novell eDirectory objects that are created when you cluster-enable a shared volume, see Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes...
  • Page 45 Hosts Files Because each GroupWise volume where you plan to create a domain or post office has been associated with a virtual server, you should add lines for the new virtual servers to one or more of the following files as needed: NetWare: sys:\etc\hosts (on all nodes in the cluster;...

  • Page 46: Setting Up A New Groupwise System In A Cluster

    SLP and provides the most reliable name resolution. On NetWare 5.1, Novell Cluster Services does not propagate virtual server information into SLP by default. If you want to use SLP for name resolution on NetWare 5.1, you must download the...
  • Page 47 2 Map a drive to the GroupWise volume for the domain (System Clustering Worksheet item and, if needed, to the GroupWise volume for the post office (System Clustering Worksheet item 8), where the primary domain and the initial post office for your new GroupWise system will be created.

  • Page 48: Creating A New Secondary Domain In A Cluster

    3.3 Creating a New Secondary Domain in a Cluster After you have set up the primary domain and initial post office, as described in Section 3.2, “Setting Up a New GroupWise System in a Cluster,” on page 46, you can create additional secondary domains as needed.

  • Page 49: Creating A New Post Office In A Cluster

    8 Rebuild the domain database for the new domain, following the steps provided in “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. Be sure to browse to the database location (under System Clustering Worksheet item through the virtual server that was created when you cluster-enabled the GroupWise volume.

  • Page 50: Installing And Configuring The Mta And The Poa In A Cluster

    This option creates the document storage area for the library under the post office directory and is not recommended for large libraries. The Configure Link option is selected by default. Select TCP/IP Link from Domain to New Post Office. Refer to the Agent Clustering Worksheet that you filled in during “Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster”...

  • Page 51: Installing The Agent Software In A Cluster

    Section 3.5.3, “Configuring the GroupWise Volume Resource to Load and Unload the Agents,” on page 53 Section 3.5.4, “Setting Up New Instances of the Agents without Installing the Agent Software,” on page 57 Under some circumstances, the agent software has already been installed and you simply need to create a new startup file specific to the new domain or post office.

  • Page 52: Editing Clustered Agent Startup Files

    5 If you need to install the agents to sys:\system on multiple nodes in the cluster: 5a Repeat Step 4, mapping new drives as needed. 5b If you marked Yes for Consolidate Multiple Startup Files on GroupWise Volume? (under Agent Clustering Worksheet item 1), copy one complete set of agent startup files and the grpwise.ncf file to the planned location, then delete all agent startup files, as well as the grpwise.ncf file, from the sys:\system directories to avoid future confusion.

  • Page 53: Configuring The Groupwise Volume Resource To Load And Unload The Agents

    3.5.3 Configuring the GroupWise Volume Resource to Load and Unload the Agents The properties of the Volume Resource object define how the GroupWise volume functions within the cluster, how NLM programs are loaded and unloaded, and how failover and failback situations are handled.
  • Page 54 Transfer the agent load commands from the grpwise.ncf file into the load script. Use Ctrl+C to copy and Ctrl+V to paste text into the load script page. Then delete or rename the grpwise.ncf file to avoid future confusion. load volume:\system\agent.nlm @startup_file If you marked Yes under Load Agents in Protected Memory? (Agent Clustering Worksheet item...
  • Page 55 To set up the unload script: 1 In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Unload to display the default volume resource unload script. 2 Make the following changes to the default unload script: If you marked Yes under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), add an unload address space command for each address...
  • Page 56 3 Click Apply to save the unload script. 4 If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect. 5 Continue with Setting the Failover Path and Policies for the Agents.

  • Page 57: Setting Up New Instances Of The Agents Without Installing The Agent Software

    NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the GroupWise volume resource properties.
  • Page 58 If necessary, click View > Console View to display its contents. 2 Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the volume resource load script for the GroupWise volume. 3 Following the pattern of the existing load commands, add load commands for the new instances of the agents you are setting up.

  • Page 59: Testing Your Clustered Groupwise System

    You might want to review other properties of the Volume Resource object, such as the failover path on the Nodes page and the failover/failback/migration procedures on the Policies page, in light of the fact that an additional domain and/or post office now resides on the GroupWise volume.

  • Page 60: Managing Your Clustered Groupwise System

    Section 3.7.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 60 Section 3.7.2, “Using Novell Remote Manager on NetWare 6.x,” on page 61 Section 3.7.3, “Knowing What to Expect in MTA and POA Failover Situations,” on page 64 3.7.1 Updating GroupWise Objects with Cluster-Specific...

  • Page 61: Using Novell Remote Manager On Netware 6.X

    “Knowing What to Expect in MTA and POA Failover Situations” on page 3.7.2 Using Novell Remote Manager on NetWare 6.x On NetWare 6.x, you can use Novell Remote Manager to manage many aspects of your GroupWise cluster from your Web browser. For instructions on setting up and accessing this useful network administration utility, see the NetWare 6.x Novell Remote Manager Administration Guide at the...
  • Page 62 After you have accessed Novell Remote Manager, you might find that many GroupWise cluster management tasks are easier to perform with Novell Remote Manager than with ConsoleOne. The following sections help you configure and manage the cluster using Novell Remote Manager: “Configuring Your GroupWise Cluster”...
  • Page 63 Cluster Volume object. Managing Your GroupWise Cluster On the main Novell Remote Manager page: 1 In the left frame, scroll down to the Clustering section, then click Cluster Management. The Cluster Status page displays the nodes and volume resources in the cluster. The master node in the cluster is marked with a yellow ball.

  • Page 64: Knowing What To Expect In Mta And Poa Failover Situations

    2 Select a page refresh rate, then click Begin Refresh so that the page automatically refreshes at the selected rate. 3 Click a cluster resource to bring it online, take it offline, or migrate it to another node. To take the currently running volume resource offline, click Offline. To migrate the volume resource, select a node from the drop-down list, then click Migrate.

  • Page 65: Clustering Quick Checklists

    “Implementing WebAccess in a NetWare Cluster,” on page Connecting your clustered GroupWise system to other e-mail systems through GroupWise gateways. See Chapter 6, “Implementing GroupWise Gateways in a Novell Cluster,” on page 107. Monitoring the status of your clustered GroupWise system from your Web browser. See Chapter 7, “Monitoring a GroupWise System in a NetWare Cluster,”...

  • Page 66: Domain Quick Checklist

    Add the cvsbind del command if you used the cvsbind add command in the load script (NetWare 5.1 only; optional) Remove the trustmig command “Modifying the Volume Resource Unload Script for the Agents” on page Set up the volume failover path(s) and policies. “Setting the Failover Path and Policies for the Agents”...

  • Page 67: Post Office Quick Checklist

    Add the cvsbind del command if you used the cvsbind add command in the load script (NetWare 5.1 only; optional) Remove the trustmig command “Modifying the Volume Resource Unload Script for the Agents” on page Set up the domain volume failover path and policies. “Setting the Failover Path and Policies for the Agents”...
  • Page 68 Modify the post office volume resource unload script: Add the POA or address space unload command Add the cvsbind del command if you used the cvsbind add command in the load script (NetWare 5.1 only; optional) Remove the trustmig command “Modifying the Volume Resource Unload Script for the Agents”...

  • Page 69: Implementing The Internet Agent In A Netware Cluster

    Implementing the Internet Agent in a NetWare Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 23 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”...

  • Page 70: Planning A Domain For The Internet Agent

    4.1.1 Planning a Domain for the Internet Agent The considerations involved in planning a domain for the Internet Agent are much the same as planning any other domain. In preparation, review “Planning a New Domain”, then print and fill out “Domain Worksheet”...

  • Page 71: Agent And Its Mta

    INTERNET AGENT CLUSTERING WORKSHEET Under Item 3: Internet Agent Failover Path, list the nodes that you want to have in the Internet Agent volume failover path. 4.1.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the Internet Agent and Its MTA As with the MTA and the POA, the Internet Agent needs a secondary IP address and cluster-unique port numbers.

  • Page 72: Deciding Where To Install The Internet Agent And Its Mta

    If the Internet Agent has a large number of nodes on its failover path, you could configure the Internet Agent to send outgoing messages to a relay host, which would then send them out through the firewall using its own IP address rather than the address of the particular node where the Internet Agent was running.

  • Page 73: Planning The Mta Installation

    1 Complete the cluster-enabling steps in the applicable section of the cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page The Internet Agent Clustering Worksheet provides the volume to cluster-enable, the cluster- enabled volume IP address, and the failover path for the Internet Agent volume.

  • Page 74: Creating A Domain For The Internet Agent

    ® If you have installed the latest version of ConsoleOne and the Novell Cluster Services snap- in, you can rename the cluster-related objects in case your DNS name server cannot resolve object names that include the underscore (_) character. 2 To ensure successful short name resolution, add entries for the Internet Agent virtual server to support your preferred methods of short name resolution, as described in “Configuring Short...
  • Page 75 2 If you selected vol:\system on Internet Agent Volume as the Internet Agent installation location (Internet Agent Clustering Worksheet item 6), create the vol:\system directory on the Internet Agent volume accessed in Step If you selected sys:\system on Each Node, decide which node you will install the Internet Agent to first, then map a drive to sys:\system on that node.
  • Page 76 To set up the load script: 1 In ConsoleOne, browse to and select the Cluster object. If necessary, click View > Console View to display its contents. 2 Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the default volume resource load script for the Internet Agent volume.
  • Page 77 Transfer the Internet Agent load command from the gwia.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page. Then delete or rename the gwia.ncf file to avoid future confusion.
  • Page 78 To set up the unload script: 1 In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Unload to display the default volume resource unload script. The next step assumes that this is the first time you have edited this unload script. If other GroupWise agents are already running from this volume, some of the modifications have already been made.
  • Page 79 3 Click Apply to save the unload script. 4 If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect. 5 Continue with Setting the Failover Path and Policies for the Internet Agent.
  • Page 80 If you are considering changing these defaults, see the applicable section about failover and failback modes in the cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the Internet Agent volume resource properties.
  • Page 81 2 Right-click the Internet Agent object, then click Properties. 3 Continue with Verifying the Reference to the Volume Resource. Verifying the Reference to the Volume Resource In the Internet Agent object properties pages: 1 Click SMTP/MIME > Settings. 2 Verify the contents of the Hostname/DNS "A Record" Name field. It displays the hostname as currently configured in DNS.

  • Page 82: Testing The Clustered Internet Agent

    5 Click OK. 6 Continue with Testing the Clustered Internet Agent. 4.2.5 Testing the Clustered Internet Agent After you have configured the Internet Agent volume resource, you can test the load and unload scripts by bringing the Internet Agent volume online and taking it offline again. 1 In ConsoleOne, select the Cluster object, then click View >...

  • Page 83: Managing The Internet Agent In A Cluster

    Internet Agent volume resource online permanently. On NetWare 6.x, these actions can also be performed from your Web browser. See “Using Novell Remote Manager on NetWare 6.x” on page 7 Continue with Managing the Internet Agent in a Cluster.

  • Page 84: Knowing What To Expect In An Internet Agent Failover Situation

    Recording Cluster-Specific Information about the Internet Agent With the contents of the Internet Agent domain still displayed: 1 Right-click the Internet Agent object, then click Properties. 2 Click GroupWise, then click Identification. 3 In the Description field, record the secondary IP address of the cluster-enabled Internet Agent domain volume and the cluster-unique port numbers used by the Internet Agent.
  • Page 85 Item Explanation 3) Internet Agent List other nodes in the cluster where the Internet Agent and its MTA Failover Path: could fail over. For more information, see “Determining an Appropriate Failover Path for the Internet Agent Volume” on page 4) MTA Installation Location: Mark the location where you will install the MTA software.

  • Page 86: Internet Agent Quick Checklist

    4.5 Internet Agent Quick Checklist Plan the new clustered Internet Agent, including the new domain required to house the Internet Agent in a clustering environment. Section 4.1, “Planning the Internet Agent in a Cluster,” on page Make sure your firewall is configured to accommodate the Internet Agent. Section 4.1.5, “Preparing Your Firewall for the Internet Agent,”...
  • Page 87 Test the clustered Internet Agent. Section 4.2.5, “Testing the Clustered Internet Agent,” on page Record cluster-specific information in the properties pages of the GroupWise objects associated with the Internet Agent. Section 4.3.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page Implementing the Internet Agent in a NetWare Cluster...
  • Page 88 GroupWise 7 Interoperability Guide...

  • Page 89: Implementing Webaccess In A Netware Cluster

    Implementing WebAccess in a NetWare Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 23 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”...

  • Page 90: Planning A New Domain For The Webaccess Agent

    Section 5.2.2, “Deciding Whether to Cluster-Enable the WebAccess Agent Volume,” on page 90 Section 5.2.3, “Determining an Appropriate Failover Path for the WebAccess Agent Volume,” on page 91 Section 5.2.4, “Planning a Secondary IP Address and Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA,”...

  • Page 91: Determining An Appropriate Failover Path For The Webaccess Agent Volume

    Cluster-enabling relies on successful short name resolution throughout your system. Review Section 2.7, “Ensuring Successful Name Resolution for GroupWise Volumes,” on page 29, which describes the issues in the context of planning MTA and POA installations. 5.2.3 Determining an Appropriate Failover Path for the WebAccess Agent Volume As with the MTA and the POA, you need to decide which nodes in the cluster are appropriate locations where the WebAccess Agent volume could fail over.

  • Page 92: Deciding Whether To Run The Webaccess Agent And Its Mta In Protected Memory

    WEBACCESS CLUSTERING WORKSHEET Under Item 5: MTA Installation Location Item 7: WebAccess Agent Installation Location, mark whether you will install the WebAccess Agent and its MTA to sys:\system on each node in the cluster or to a vol:\system directory on the WebAccess Agent volume. Also specify where the MTA startup file will be stored.

  • Page 93: Setting Up Webaccess In A Cluster

    1 Complete the cluster-enabling steps in the applicable section of cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page Implementing WebAccess in a NetWare Cluster...

  • Page 94: Creating A Domain For The Webaccess Agent

    The WebAccess Clustering Worksheet provides the volume to cluster-enable, the cluster- enabled volume IP address, and the failover path for the WebAccess volume. For a review of the new Novell eDirectory objects that are created when you cluster-enable a shared volume, see Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes...
  • Page 95 Installing the WebAccess Agent Software in a Cluster The WebAccess Agent is the component of your WebAccess installation that accesses post offices and libraries to retrieve information for WebAccess client users. 1 Map a drive to the WebAccess Agent volume (WebAccess Clustering Worksheet item 1) where the WebAccess domain is located.
  • Page 96 Configuring the WebAccess Agent Volume Resource to Load and Unload the WebAccess Agent and Its MTA The properties of the Volume Resource object define how the WebAccess Agent volume functions within the cluster, how NLM programs are loaded and unloaded, and how failover and failback situations are handled.
  • Page 97 Transfer the MTA load command from the grpwise.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page. Then delete or rename the grpwise.ncf file to avoid future confusion.
  • Page 98 NOTE: The set commands are needed only when the MTA and the WebAccess Agent are not running in protected memory. The address space parameters are needed in the load commands only when the MTA and the WebAccess Agent are running in protected memory. 4 Click Apply to save the load script.
  • Page 99 cvsbind del cluster_volume_SERVER ip_address Remove the trustmig command just like you did in the load script. The result would look similar to the following example: 3 Click Apply to save the unload script. 4 If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

  • Page 100: Testing Your Clustered Webaccess Installation

    NetWare, as listed in Chapter 1, “Introduction to GroupWise 7 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the WebAccess Agent volume resource properties.

  • Page 101: Managing Webaccess In A Cluster

    5.4 Managing WebAccess in a Cluster After you have installed WebAccess in a cluster, you should consider some long-term management issues. Section 5.4.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 101 Section 5.4.2, “Knowing What to Expect in WebAccess Failover Situations,” on page 102 Section 5.4.3, “Updating the WebAccess Agent Configuration File (commgr.cfg),”...

  • Page 102: Knowing What To Expect In Webaccess Failover Situations

    It is also automatically copied to the following Web server subdirectory: sys:\novell\webaccess If you change WebAccess agent configuration information (for example, if you change its ip address), the information is changed in the following file: domain\wpgate\webac70a\commgr.cfg...

  • Page 103: Webaccess Clustering Worksheet

    WebAccess Application is currently running. However, the other nodes on the WebAccess Application failover path are not currently available for update. therefore, you must manually copy the updated commgr.cfg file to the sys:\novell\webaccess subdirectory on each node in the WebAccess Application failover path.

  • Page 104: Webaccess Quick Checklist

    Item Explanation 7) WebAccess Agent Gather the WebAccess Agent network address information from the Network Information: WebAccess section of the “IP Address Worksheet” on page For more information, see “Planning a Secondary IP Address and WebAccess Agent IP Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA” address on page WebAccess Agent HTTP...
  • Page 105 Modify the WebAccess Agent volume resource unload script: Add the MTA and WebAccess Agent or address space unload command(s) Add the cvsbind del command if you used the cvsbind add command in the load script (NetWare 5.1 only; optional) Remove the trustmig command “Modifying the Volume Resource Unload Script for the WebAccess Agent”...
  • Page 106 106 GroupWise 7 Interoperability Guide...

  • Page 107: Implementing Groupwise Gateways In A Novell Cluster

    GroupWise gateways that have not received recent development have not been thoroughly tested in a clustering environment. If you are currently using such GroupWise gateways, you might want to leave them outside of your cluster. Implementing GroupWise Gateways in a Novell Cluster...
  • Page 108 108 GroupWise 7 Interoperability Guide...

  • Page 109: Monitoring A Groupwise System In A Netware Cluster

    Monitoring a GroupWise System in a NetWare Cluster ® ® Because the GroupWise 7 Monitor currently runs on Windows and Linux, rather than NetWare you cannot run GroupWise Monitor in a NetWare cluster. However, GroupWise Monitor can easily monitor a clustered GroupWise system from a vantage point outside the NetWare cluster. When you first install Monitor, it gathers information about agents to monitor from a domain database (wpdomain.db).
  • Page 110 110 GroupWise 7 Interoperability Guide...

  • Page 111: Backing Up A Groupwise System In A Netware Cluster

    Backing Up a GroupWise System in a NetWare Cluster ® The GroupWise Target Service Agent (GWTSA) is a GroupWise-specific API that works with compatible backup software to provide reliable backups of a running GroupWise system on ® NetWare 5.1. On NetWare 6.x, improved functionality is available with the GroupWise Target Service Agent for File Systems (TSAFSGW).

  • Page 112: Using Tsafsgw In A Netware 6.X Cluster

    If the node where GWTSA is running goes down, the backup needs to be rerun when the node is up again, unless the nodes where the domain and post office volumes failed over are also configured to back them up. Using GWTSA, there is currently no way to restart a backup from a checkpoint position.
  • Page 113 software acknowledges the disruption and attempts to reconnect to the next node. When the next node is fully up and responding, the backup recommences, starting with the resource that was being backed up when the disruption occurred. To restore data in a clustering environment, you must run your backup/restore software on the node where the location to restore is currently mounted.
  • Page 114 114 GroupWise 7 Interoperability Guide...

  • Page 115: Updating A Groupwise System In A Netware Cluster

    Updating a GroupWise System in a NetWare Cluster ® ® In a NetWare cluster, you have the option of installing the GroupWise software on each node in the cluster or on a GroupWise volume along with a domain or post office, as described in Section 2.8.3, “Deciding Where to Install the Agent Software,”...
  • Page 116 116 GroupWise 7 Interoperability Guide...

  • Page 117: Moving An Existing Groupwise 7 System Into A Netware Cluster

    If you are adding the high availability benefits of Novell Cluster Services to a GroupWise system that is already up and running, the first step is to install Novell Cluster Services following the ® instructions in the clustering documentation for your version of NetWare...
  • Page 118 Chapter 4, “Implementing the Internet Agent in a NetWare Cluster,” on page 69 Chapter 5, “Implementing WebAccess in a NetWare Cluster,” on page 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,”...

  • Page 119: Implementing Messenger In A Netware Cluster

    Implementing Messenger in a NetWare Cluster ® Novell Messenger does not require the existence of a GroupWise system in the cluster, but presumably one has already been set up as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 23 Chapter 3, “Setting Up a Domain and Post Office in a NetWare...

  • Page 120: Deciding Where To Install The Messenger Agent Software

    MESSENGER CLUSTERING WORKSHEET Under Item 6: Installation Location for Messenger Administration, mark where you want to install the Messenger snap-in to ConsoleOne. If you plan to install the Messenger snap-in to ConsoleOne on a cluster-enabled shared volume, under Item 7: Shared Volume for Messenger Administration, list the IP address of the shared volume and the directory where you want to install the Messenger snap-in.
  • Page 121 Each Node in the Cluster Make sure you have filled out item 5 on the Messenger Clustering Worksheet with a complete list of nodes in the cluster. Skip to “Planning the Messenger Agent Installation” on page 122. Shared Volume For convenience throughout the rest of this section, the term “Messenger volume” means “a cluster- enabled shared volume where the Messenger agents are installed.”...

  • Page 122: Setting Up Your Messenger System In A Cluster

    Yes. This adds the /cluster switch to the agent startup files. The /cluster switch tells the Messenger agents to use the virtual server name of the cluster or the Messenger volume rather than the specific server name in pathnames obtained from agent object properties in Novell eDirectory or from startup switches.

  • Page 123: Installing To Each Node In The Cluster

    “Starting the Messenger Installation Program” and “Creating Your Messenger System” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide. Make each node in the cluster active to make sure that the Messenger agents start successfully. 11.2.2 Installing to a Messenger Volume Complete the following tasks to set up your Messenger system on a Messenger volume: “Preparing the Cluster for Messenger”...
  • Page 124 Messenger system, following the steps provided in “Starting the Messenger Installation Program” and “Creating Your Messenger System” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide. Keep in mind the following cluster-specific details: When you specify the Messenger installation directory, be sure to browse to the location...
  • Page 125 10 Click Apply to save the failover path. 11 Click Policies to display the default start, failover, and failback policies. By default, a volume resource: Fails over automatically if the node it is running on fails Starts automatically on the net node in its failover path Continues running at its failover location even after its most preferred node is again available 12 Change the policies if necessary, then click OK.
  • Page 126 Messenger volume resource online permanently. On NetWare 6.x, these actions can also be performed from your Web browser. See “Using Novell Remote Manager on NetWare 6.x” on page 126 GroupWise 7 Interoperability Guide...

  • Page 127: Messenger Clustering Worksheet

    Latest ConsoleOne Snap-In for Requirements,” on page Novell Cluster Services 2) eDirectory Tree for Cluster: Record the eDirectory tree where you created the Novell Cluster object when you installed Novell Cluster Services. To review the background information provided for GroupWise clustering, see Section 2.2, “Installing Novell Cluster Services,”...
  • Page 128 Item Explanation 7) Shared Volume for Messenger If you plan to install the Messenger snap-in to ConsoleOne on Administration: a shared volume, specify the name (cluster_volume) of the shared volume where you will install it. Cluster Volume IP Address: Specify the IP addresses of the virtual server Installation Location for Messenger (volume_SERVER.cluster) to which the shared volume is tied.
  • Page 129 Novell Cluster Services on Linux Chapter 12, “Introduction to GroupWise 7 and Novell Cluster Services on Linux,” on page 131 Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 133 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,” on page 143 Chapter 15, “Implementing the Internet Agent in a Linux Cluster,”...
  • Page 130 130 GroupWise 7 Interoperability Guide...

  • Page 131: Introduction To Groupwise 7 And Novell Cluster Services On Linux

    GroupWise system: cluster: A grouping of from two to 32 servers configured using Novell Cluster Services so that data storage locations and applications can transfer from one server to another without interrupting their availability to users.
  • Page 132 cluster resource: A shared partition, secondary IP address, application, service, Web server, etc., that can function successfully anywhere in the cluster. Cluster resources include the GroupWise agents and the Messenger agents. failover: The process of moving cluster resources from a failed node to a functional node so that availability to users is uninterrupted.

  • Page 133: Planning Groupwise In A Linux Cluster

    System in a Linux Cluster,” on page 221) is designed for those who are creating a new GroupWise ® system, or at least new domains and post offices, in the context of Novell Cluster Services Linux. If you already have an existing GroupWise 7 system on OES Linux and need to configure it to work in a newly installed cluster, see Chapter 20, “Moving an Existing Linux GroupWise 7 System into a...

  • Page 134: Installing Novell Cluster Services On Linux

    IMPORTANT: Cluster-enabling is required for GroupWise. Mounting the shared partitions where you want to set up GroupWise domains and post offices. As you install Novell Cluster Services on Linux, record key information about the cluster on the System Clustering Worksheet:...

  • Page 135: Planning A Clustered Software Distribution Directory

    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.

  • Page 136: Planning A New Clustered Domain

    SYSTEM CLUSTERING WORKSHEET If you want to have your GroupWise software distribution directory as part of your cluster, under Item 6: GroupWise Partition for Software Distribution Directory, list the GroupWise partition and associated secondary IP address for the software distribution directory. List the full path for the software distribution directory, regardless of whether it is located on a GroupWise partition or on each node in the cluster.

  • Page 137: Planning A New Clustered Post Office

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

  • Page 138: Deciding How To Install And Configure The Linux Agents In A Cluster

    13.6 Deciding How to Install and Configure the Linux Agents in a Cluster There are several cluster-specific issues to consider as you plan to install the Linux MTA and POA in your clustered GroupWise system: Section 13.6.1, “Recording Secondary IP Addresses for the Agents,” on page 138 Section 13.6.2, “Determining Appropriate Failover Lists for the Agents,”...

  • Page 139: Groupwise Clustering Worksheets

    AGENT CLUSTERING WORKSHEET Under Item 2: Domain Failover List, list the nodes that you want to have in the domain partition failover list. The MTA might need to run on any node that the domain partition fails over to. Therefore, you will install the agent software on all of the nodes in the domain failover list.

  • Page 140: System Clustering Worksheet

    13.7.1 System Clustering Worksheet Item Explanation 1) eDirectory Tree for Cluster: Record the eDirectory tree where you created the new Novell Cluster object when you installed Novell Cluster Services. For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134...

  • Page 141: Agent Clustering Worksheet

    Item Explanation 8) GroupWise Partition for Post Office: Specify the name of the shared partition where the GroupWise post office will reside and its secondary IP address. Secondary IP Address: For more information, see Section 13.4, “Planning a New Clustered Post Office,” on page 137.
  • Page 142 Item Explanation 6) POA Network Information: Record the POA network address information for the server where the POA will run. The POA IP address is the same as POA IP address the post office secondary IP address in the cluster. POA client/server port Section 13.6.1, “Recording Secondary IP Addresses for POA message transfer port...

  • Page 143: Setting Up A Domain And A Post Office In A Linux Cluster

    If necessary, you can download ConsoleOne for Linux from the Novell Product Downloads site (http://download.novell.com). ConsoleOne is always installed in /usr/Consoleone. 3 If necessary, mount the GroupWise partition where you want to create the GroupWise software...

  • Page 144: Creating A New Secondary Domain In A Linux Cluster

    IMPORTANT: Do not select the Configure GroupWise for Clustering option at this time. 6 When you set up the software distribution directory, install all the agent software. Although this is not required when creating your initial domain and post office, it makes installation of the other GroupWise agents easier after you have created the initial domain and post office.

  • Page 145: Creating A New Post Office In A Linux Cluster

    7 Rebuild the domain database for the new domain, following the steps provided in “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. The database rebuild is necessary in order to transfer the MTA configuration information and the domain link information into the secondary domain database, because the MTA for the new domain is not yet running.

  • Page 146: Installing And Configuring The Mta And The Poa In A Cluster

    9 Rebuild the post office database for the new post office, following the steps provided in “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. Be sure to browse to the database location (under System Clustering Worksheet item 11) through the GroupWise partition.
  • Page 147 Running the GroupWise Installation Program on the Preferred Node 1 Mount the GroupWise partition for the domain (System Clustering Worksheet item 7) or the post office (System Clustering Worksheet item 2 From the software distribution directory you created in Step 6 Section 14.1, “Setting Up a New GroupWise System in a Linux Cluster,”...
  • Page 148 5 Configure the agents to run as a non-root user, as described in the applicable section of the GroupWise 7 Installation Guide: “Running the Linux GroupWise Agents as a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 6 Continue with Running the GroupWise Installation Program on Subsequent Nodes.
  • Page 149 The GroupWise High Availability service is automatically configured on the current cluster node and its configuration file (gwha.conf) is created in the /etc/opt/ novell/groupwise directory. It is configured specifically for the agents you just selected. Setting Up a Domain and a Post Office in a Linux Cluster 149...

  • Page 150: Changing Agent Paths To Locations On Groupwise Partitions

    6 Configure the agents to run as a non-root user, as described in the applicable section of the GroupWise 7 Installation Guide: “Running the Linux GroupWise Agents as a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Repeat Step 1 through Step 6 for each cluster node in the GroupWise agent failover list.
  • Page 151 Setting the MTA Message Log File Path If you plan to enable message logging, as described in “Enabling MTA Message Logging” in “Message Transfer Agent” in the GroupWise 7 Administration Guide: 1 On the GroupWise partition where the domain is located, create the directory where you want to store MTA message log files.

  • Page 152: Configuring Groupwise Cluster Resources To Load And Unload The Agents

    The cluster resource load script executes whenever the GroupWise partition comes online. On OES Linux, all cluster management activities are performed in Novell iManager. To set up the load script in iManager: 1 Expand Clusters, then click Cluster Options. 2 In the Cluster field, browse to the Cluster object where the GroupWise cluster resource is located.
  • Page 153 4 Select the GroupWise Cluster Resource object that you created when you set up the GroupWise partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d...
  • Page 154 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 155 1 On the Cluster Resource Properties page of the GroupWise cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 156 The result would be similar to the following: 3 If this is a traditional Linux volume, use the following unload script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/grpwise stop domain /etc/init.d/grpwise stop post_office.domain # define the IP address 156 GroupWise 7 Interoperability Guide...
  • Page 157 RESOURCE_IP=172.16.5.18 # define the mount point MOUNT_POINT=/mnt/mount_point sleep 8 ignore_error fuser -k $MOUNT_POINT # del the IP address ignore_error del_secondary_ipaddress $RESOURCE_IP # umount the file system exit_on_error umount $MOUNT_POINT # return status exit 0 Make the following changes to set up the unload script for the agents. 3a Use the following command to stop the MTA: /etc/init.d/grpwise stop domain 3b Use the following command to stop the POA:...

  • Page 158: Setting Up New Instances Of The Agents Without Installing The Agent Software

    “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the domain or post office (under Agent Clustering Worksheet items 3 or 3 Click OK.
  • Page 159 4 Save the new startup file. 5 Edit the GroupWise High Availability service configuration file (/etc/opt/novell/ groupwise/gwha.conf). 6 Make a copy of the section for an existing domain and its MTA or post office and its POA, then modify the information for the new domain or post office and its accompanying agent.

  • Page 160: Testing Your Clustered Groupwise System

    9 Change other Cluster Resource properties as needed. 10 Click OK to save the modified properties. 11 In the Cluster Manager, take the GroupWise partition offline and then bring it online again to test the new startup files and the modified load and unload scripts. If you need assistance with these tasks, see Testing Your Clustered GroupWise System.

  • Page 161: Managing Your Clustered Groupwise System

    3 Select the cluster node where you want to online the GroupWise cluster resource, then click After a moment, the GroupWise cluster resource displays Running in the State column. 4 At the server where the MTA and/or POA are starting, use the following command to see if they are running: /etc/init.d/grpwise status domain /etc/init.d/grpwise status post_office.domain...
  • Page 162 6 In the Description field of the MTA Identification page, record the secondary IP address of the domain’s GroupWise partition. This information appears on the MTA server console, no matter which node in the cluster it is currently running on. 7 Click Apply to save the description.

  • Page 163: Knowing What To Expect In Mta And Poa Failover Situations

    Recording Cluster-Specific Information for a Software Distribution Directory To permanently record important cluster-specific information about a software distribution directory located on a GroupWise partition: 1 In ConsoleOne, click Tools > System Operations > Software Directory Management. 2 Select the software distribution directory, then click Edit. 3 In the description field, record the secondary IP address of the GroupWise partition where the software distribution directory resides.

  • Page 164: Clustering Quick Checklists

    Monitoring the status of your clustered GroupWise system from your Web browser. See Chapter 17, “Implementing GroupWise Monitor in a Linux Cluster,” on page 207. Backing up your clustered GroupWise system. See Chapter 18, “Backing Up a GroupWise System in a Linux Cluster,” on page 221.

  • Page 165: Post Office Quick Checklist

    Modify the domain cluster resource load script. “Modifying the Cluster Resource Load Script for the Agents” on page 152. Modify the domain cluster resource unload script. “Modifying the Cluster Resource Unload Script for the Agents” on page 155. Set up the domain failover list and policies. “Setting the Failover List and Policies for the Agents”...
  • Page 166 166 GroupWise 7 Interoperability Guide...

  • Page 167: Implementing The Internet Agent In A Linux Cluster

    Implementing the Internet Agent in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 133 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 168: Planning A Domain For The Internet Agent

    15.1.1 Planning a Domain for the Internet Agent The considerations involved in planning a domain for the Internet Agent are much the same as planning any other domain. In preparation, review “Planning a New Domain”, then print and fill out “Domain Worksheet”...

  • Page 169: Determining An Appropriate Failover List For The Internet Agent

    15.1.3 Determining an Appropriate Failover List for the Internet Agent By default, a GroupWise partition is configured to have all nodes in the cluster in its failover list, organized in ascending alphanumeric order. Only one node at a time can have a particular GroupWise partition mounted and active.

  • Page 170: Planning The Mta Installation

    Standard Ports Table 15-1 Protocol Standard Port IMAP4 LDAP POP3 SMTP By default, the Internet Agent sends outgoing messages on the primary IP address of the server where it is running. If you decide to use this default configuration, your firewall must be configured to allow outbound TCP/IP traffic from all nodes in the Internet Agent partition failover list.

  • Page 171: Setting Up The Internet Agent In A Linux Cluster

    15.2 Setting Up the Internet Agent in a Linux Cluster You should already have reviewed Section 15.1, “Planning the Internet Agent in a Linux Cluster,” on page 167 and filled out Section 15.5, “Internet Agent Clustering Worksheet,” on page 184. You are now ready to complete the following tasks to set up the Internet Agent in a clustering environment: Section 15.2.1, “Creating a Domain for the Internet Agent,”...
  • Page 172 Installing and Setting Up the Internet Agent Software in Your Cluster The Internet Agent must be installed on each node in its failover list (Internet Agent Clustering Worksheet item “Running the Internet Agent Installation Program on the Preferred Node” on page 172 “Running the Internet Agent Installation Program on Subsequent Nodes”...
  • Page 173 GroupWise 7 Installation Guide: “Running the Linux GroupWise Agents as a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Continue with Running the Internet Agent Installation Program on Subsequent Nodes.
  • Page 174 Because of the existence of the clusterimport.conf file in the gwinst subdirectory of the software distribution directory, a new installation option, Import Clustering Data, is now available on the main GroupWise Installation program page. 3 Install the Internet Agent software on the cluster node as usual, but do not use the Configure option.
  • Page 175 6 Configure the Internet Agent to run as a non-root user, as described in the applicable section of the GroupWise 7 Installation Guide: “Running the Linux GroupWise Agents as a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Repeat Step 1 through Step 6 for each cluster node in the Internet Agent failover list.
  • Page 176 Configuring the Clustered Internet Agent for SSL If you plan to enable SSL, as described in “Securing Internet Agent Connections with SSL” in “Internet Agent” in the GroupWise 7 Administration Guide, you must make the SSL certificate file and key file available to the Internet Agent in the cluster. The default locations for the SSL certificate file and key file are on the cluster nodes along with the GroupWise software, rather than being located with the domain and post office on one or more GroupWise partitions.
  • Page 177 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 178 1 On the Cluster Resource Properties page of the Internet Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 179 2f In the umount command, change /mnt/generic to the mount point directory used in the load script. 3 If this is a traditional Linux volume, use the following unload script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/grpwise stop domain.gwia /etc/init.d/grpwise stop domain # define the IP address RESOURCE_IP=172.16.5.18...
  • Page 180 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Internet Agent (Internet Agent Clustering Worksheet item 3 Click OK.
  • Page 181 2 Right-click the Internet Agent object, then click Properties. 3 Continue with Verifying the Reference to the Internet Agent Cluster Resource. Verifying the Reference to the Internet Agent Cluster Resource In the Internet Agent object properties pages: 1 Click SMTP/MIME > Settings. 2 Verify the contents of the Hostname/DNS “A Record”...

  • Page 182: Testing The Internet Agent In A Linux Cluster

    15.3 Testing the Internet Agent in a Linux Cluster After you have configured the Internet Agent cluster resource, you can test the load and unload scripts by bringing the cluster resource online and taking it offline again. 1 In iManager, expand Clusters, then click Cluster Manager. The new Internet Agent cluster resource shows Offline in the State column.

  • Page 183: Managing The Internet Agent In A Linux Cluster

    5 Select the new Internet Agent cluster resource, then click Offline. The State column for the Internet Agent cluster resource returns to Offline. 6 Use the same command that you used in Step 4 to verify that the Internet Agent has stopped. 7 Repeat Step 2 whenever you are ready to bring the new Internet Agent cluster resource online...

  • Page 184: Knowing What To Expect In An Internet Agent Failover Situation

    7 Click OK to save the MTA description. 8 Continue with Recording Cluster-Specific Information about the Internet Agent. Recording Cluster-Specific Information about the Internet Agent With the contents of the Internet Agent domain still displayed: 1 Right-click the Internet Agent object, then click Properties. 2 Click GroupWise, then click Identification.

  • Page 185: Internet Agent Quick Checklist

    Item Explanation 3) Internet Agent List other nodes in the cluster where the Internet Agent and its MTA Failover List: could fail over. For more information, see Section 15.1.3, “Determining an Appropriate Failover List for the Internet Agent,” on page 169.
  • Page 186 Set up the Internet Agent failover list and policies. “Setting the Failover List and Policies for the Internet Agent and Its MTA” on page 180. Enable Internet Addressing for the clustered Internet Agent. “Enabling Internet Addressing for Your Clustered GroupWise System” on page 180.

  • Page 187: Implementing Webaccess In A Linux Cluster

    Implementing WebAccess in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 133 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 188: Planning A Domain For The Webaccess Agent

    Section 16.6, “WebAccess Agent Clustering Worksheet,” on page 204 lists the information you need as you set up the WebAccess Agent in a clustering environment. You should print the worksheet and fill it out as you complete the tasks listed below: Section 16.2.1, “Planning a Domain for the WebAccess Agent,”...

  • Page 189: Selecting The Webaccess Agent Partition And Secondary Ip Address

    16.2.2 Selecting the WebAccess Agent Partition and Secondary IP Address As with the MTA and the POA, the WebAccess Agent needs a secondary IP address that remains the same no matter which node in the cluster it is running on. You can place the WebAccess Agent and its domain on a GroupWise partition where a domain or post office already reside, which means that...

  • Page 190: Planning The Mta Installation

    WEBACCESS AGENT CLUSTERING WORKSHEET Under Item 4: Cluster Resource Mount Point, list the mount point for the GroupWise partition where the WebAccess Agent domain is located. 16.2.5 Planning the MTA Installation Follow the instructions in Section 13.6.4, “Planning the Linux Agent Installation,” on page 139, then return to this point.

  • Page 191: Creating A Domain For The Webaccess Agent

    16.3.1 Creating a Domain for the WebAccess Agent The WebAccess Agent domain will be a secondary domain. To create it, follow the instructions in Section 14.2, “Creating a New Secondary Domain in a Linux Cluster,” on page 144, taking your information from the WebAccess Agent Clustering Worksheet, rather than the System Clustering Worksheet, then return to this point.
  • Page 192 If this is the first GroupWise agent installed on this cluster node, the GroupWise High Availability service is automatically configured and its configuration file (gwha.conf) is created in the /etc/opt/novell/groupwise directory. If another GroupWise agent has already been installed on this cluster node, the gwha.conf file is updated to include the WebAccess Agent.
  • Page 193 The clusterimport.conf file in the gwinst subdirectory of the software distribution directory from which you ran the GroupWise Installation program is updated, so that the cluster-specific information collected when you configured the WebAccess Agent on the preferred node is available when you install the WebAccess Agent on subsequent nodes.
  • Page 194 The GroupWise High Availability service is automatically configured on the current cluster node and its configuration file (gwha.conf) is created in the /etc/opt/ novell/groupwise directory. It is configured specifically for the agents you just selected. Because the agent startup files and log files are stored on the shared resource, they do not need to be customized for each cluster node.
  • Page 195 /etc/inet.d/grpwise stop webac70a /etc/inet.d/grpwise status webac70a 5 Repeat Step 1 through Step 4for each node in the WebAccess Agent failover list. 6 Continue with “Configuring Clustered Logging” on page 195 Configuring Clustered Logging The default location for the WebAccess Agent log files is on the cluster nodes along with the WebAccess Agent software, rather than being located with the domain on the WebAccess Agent partition.
  • Page 196 4 Select the WebAccess Agent cluster resource that you created when you set up the WebAccess Agent partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d...
  • Page 197 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 198 1 On the Cluster Resource Properties page of the WebAccess Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 199 2f In the umount command, change /mnt/generic to the mount point directory used in the load script. 3 If this is a traditional Linux volume, use the following unload script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/grpwise stop domain.webac70a /etc/init.d/grpwise stop domain # define the IP address RESOURCE_IP=172.16.5.18...
  • Page 200 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the WebAccess Agent (WebAccess Agent Clustering Worksheet item 3 Click OK.

  • Page 201: Installing And Configuring The Webaccess Application In A Cluster

    2 In the TCP/IP Address field, provide the secondary IP address (WebAccess Agent Clustering Worksheet item 1) for the Internet Agent. 3 Select Bind Exclusively to TCP/IP Address. 4 Click OK. 5 Continue with Testing the WebAccess Agent in a Linux Cluster.

  • Page 202: Managing The Webaccess Agent In A Linux Cluster

    3 Select the cluster node where you want to online the WebAccess Agent cluster resource, then click OK. After a moment, the WebAccess Agent cluster resource displays Running in the State column. 4 At the server where the WebAccess Agent is starting, use the following command to see that the Internet Agent has started: /etc/init.d/grpwise status webac70a 5 Select the new WebAccess Agent cluster resource, then click Offline.

  • Page 203: Updating Groupwise Objects With Cluster-Specific Descriptions

    16.5.1 Updating GroupWise Objects with Cluster-Specific Descriptions After installing the WebAccess Agent in your clustered GroupWise system, while the cluster- specific information is fresh in your mind, you should record the cluster-specific information as part of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the information in the GroupWise objects if the configuration of your system changes.

  • Page 204: Knowing What To Expect In A Webaccess Agent Failover Situation

    16.5.2 Knowing What to Expect in a WebAccess Agent Failover Situation The failover behavior of the MTA for the WebAccess Agent domain is the same as for an MTA in a regular domain. See Section 14.6.2, “Knowing What to Expect in MTA and POA Failover Situations,”...

  • Page 205: Webaccess Agent Quick Checklist

    Item Explanation 5) MTA Network Information: Record the MTA network address information that you will need as you install the MTA. MTA IP address For more information, see Section 16.2.5, “Planning the MTA MTA message transfer port Installation,” on page 190.
  • Page 206 Section 16.5.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 203. 206 GroupWise 7 Interoperability Guide...

  • Page 207: Implementing Groupwise Monitor In A Linux Cluster

    Implementing GroupWise Monitor in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 133 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 208: Planning Groupwise Monitor In A Linux Cluster

    17.2 Planning GroupWise Monitor in a Linux Cluster A major system configuration difference between the Monitor Agent and other GroupWise agents is that the Monitor Agent needs access to a domain during installation but does not need permanent access to a domain thereafter. Section 17.6, “Monitor Agent Clustering Worksheet,”...

  • Page 209: Selecting The Monitor Agent Partition And Secondary Ip Address

    17.2.3 Selecting the Monitor Agent Partition and Secondary IP Address As with the MTA and the POA, the Monitor Agent needs a secondary IP address that remains the same no matter which node in the cluster it is running on. You can associate the Monitor Agent with the domain that was accessed during installation or with any other domain, so that they fail over together, or you can associate the Monitor Agent with its own shared partition, so that it fails over independently of any domain.

  • Page 210: Planning The Monitor Agent Installation

    17.2.6 Planning the Monitor Agent Installation Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the Monitor Agent are the same in a clustering environment as for any other environment. Review the installation instructions in “Installing the Linux Monitor Agent”...
  • Page 211 4 Install the Monitor Agent software, following the steps provided in “Installing the Linux Monitor Agent” in “Installing GroupWise Monitor” in the GroupWise 7 Installation Guide. 5 Configure the Monitor Agent, following the steps provided in “Configuring the Linux Monitor Agent”...

  • Page 212: Configuring The Monitor Agent Cluster Resource To Load And Unload The Monitor

    2 From the software distribution directory you created in Step 6 Section 14.1, “Setting Up a New GroupWise System in a Linux Cluster,” on page 143, start the GroupWise Installation program and select Configure GroupWise for Clustering. 3 Install the Monitor Agent software on the cluster node as usual, but do not use the Configure option.

  • Page 213: Agent

    Monitor Agent partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d # start the service exit_on_error /etc/init.d/myservice start...
  • Page 214 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 215 1 On the Cluster Resource Properties page of the Monitor Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 216 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Monitor Agent (Monitor Agent Clustering Worksheet item 3 Click OK.

  • Page 217: Testing The Monitor Agent In A Linux Cluster

    17.4 Testing the Monitor Agent in a Linux Cluster After you have configured the Monitor Agent cluster resource, you can test the load and unload scripts by bringing the Monitor Agent cluster resource online and taking it offline again. 1 In iManager, expand Clusters, then click Cluster Manager. The new Monitor Agent cluster resource shows Offline in the State column.

  • Page 218: Managing The Monitor Agent In A Linux Cluster

    5 Select the new Monitor Agent cluster resource, then click Offline. The State column for the Monitor Agent cluster resource returns to Offline. 6 Use the same command that you used in Step 4 to verify that the Monitor Agent has stopped. 7 Repeat Step 2 whenever you are ready to bring the new Monitor Agent cluster resource online...

  • Page 219: Monitor Agent Quick Checklist

    17.7 Monitor Agent Quick Checklist Plan the new clustered Monitor Agent, including a domain to access during installation to gather information about agents to monitor Section 17.2, “Planning GroupWise Monitor in a Linux Cluster,” on page 208. Install the Monitor Agent on all nodes in the Monitor Agent’s failover list. Section 17.3.1, “Installing and Configuring the Monitor Agent on Each Node in Your Cluster,”...
  • Page 220 220 GroupWise 7 Interoperability Guide...

  • Page 221: Backing Up A Groupwise System In A Linux Cluster

    Backing Up a GroupWise System in a Linux Cluster ® To back up GroupWise data in a Linux cluster, use the GroupWise Database Copy (DBCopy) utility to copy the data from the live GroupWise system to a static location for backup. For more information, see “Backing Up GroupWise Databases”...
  • Page 222 222 GroupWise 7 Interoperability Guide...

  • Page 223: Updating A Groupwise System In A Linux Cluster

    Updating a GroupWise System in a Linux Cluster ® In a Linux cluster, you must install the GroupWise software on each node in the cluster. Before you run the GroupWise Installation program to install updated software, make sure you know all the cluster nodes where the GroupWise software is already installed.
  • Page 224 224 GroupWise 7 Interoperability Guide...

  • Page 225: Moving An Existing Linux Groupwise 7 System Into A Linux Cluster

    If you are adding the high availability benefits of Novell Cluster Services to a GroupWise system that is already up and running, the first step is to install Novell Cluster Services following the instructions in OES Novell Cluster Services 1.8.2 Administration Guide for Linux.
  • Page 226 Chapter 17, “Implementing GroupWise Monitor in a Linux Cluster,” on page 207 Chapter 18, “Backing Up a GroupWise System in a Linux Cluster,” on page 221 226 GroupWise 7 Interoperability Guide...

  • Page 227: Moving A Clustered Groupwise 7 System From Netware To Linux

    NetWare Cluster to Linux” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. It is possible to have a cluster that includes both NetWare and ® Linux servers. Therefore, you can move your GroupWise 7 system from NetWare servers to Linux servers one component at a time.
  • Page 228 228 GroupWise 7 Interoperability Guide...

  • Page 229: Implementing Messenger In A Linux Cluster

    Implementing Messenger in a Linux Cluster ® Novell Messenger does not require the existence of a GroupWise system in the cluster, but presumably one has already been set up as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 133 Chapter 14, “Setting Up a Domain and a Post Office in a Linux...

  • Page 230: Selecting The Messenger Partition And Secondary Ip Address

    22.1.2 Selecting the Messenger Partition and Secondary IP Address If you are not planning to enable archiving, or if you are not anticipating a large Messenger archive, you can use one Messenger partition for both the Messaging Agent and the Archive Agent. If you anticipate archiving a large number of messages so that the Messenger archive grows very large, you might want to have a separate Messenger partition for the Archive Agent and its archive database.

  • Page 231: Planning The Messenger Agent Installation

    Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the Messenger agents are the same in a clustering environment as for any other environment. Review “Planning Your Novell Messenger System”, then print and fill out “Novell Messenger Worksheet”...
  • Page 232 “Creating NSS Volumes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux, you must set up non-root access to those NSS volumes, as described in “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux”...

  • Page 233: Changing Messenger Paths To Locations On The Messenger Partition

    Setting the Store Path The store path is the location where you want the archive created. During installation, the default store path is created in /var/opt/novell/messenger/aa/store on each node, but you need the archive to be stored on the Messenger partition.
  • Page 234 1 Choose a directory for the Messaging Agent queue and create that directory on the Messenger partition. 2 In ConsoleOne, browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server. 3 Right-click the Messaging Agent object, then click Properties.

  • Page 235: Agents

    2 In ConsoleOne, browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server. 3 Right-click the Archive Agent object, then click Properties. 4 Click Agent > Log Settings. 5 In the Log Files Path field, specify the Archive Agent log path, then click OK.
  • Page 236 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 237 /etc/init.d/novell-nmaa start 7 Click Apply to save the load script. Modifying the Cluster Resource Unload Script for the Messenger Agents The cluster resource unload script executes whenever the Messenger cluster resource goes offline. 1 On the Cluster Resource Properties page of the Monitor Agent cluster resource, click Scripts >...
  • Page 238 #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/novell-nmma stop /etc/init.d/novell-nmaa stop # define the IP address RESOURCE_IP=172.16.5.18 # define the mount point MOUNT_POINT=/mnt/mount_point sleep 8 ignore_error fuser -k $MOUNT_POINT # del the IP address ignore_error del_secondary_ipaddress $RESOURCE_IP # umount the file system exit_on_error umount $MOUNT_POINT...

  • Page 239: Testing Your Clustered Messenger System

    “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Messenger agents (under Messenger Clustering Worksheet item 3 Click OK.

  • Page 240: Managing Your Clustered Messenger System

    22.5 Messenger Clustering Worksheet Item Explanation 1) eDirectory Tree for Cluster: Record the eDirectory tree where you created the Novell Cluster object when you installed Novell Cluster Services For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134.

  • Page 241: Messenger Clustering Quick Checklist

    You need this information as you create load Mount point and unload scripts for the Messenger agents. For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134. 5) Shared Partitions in Cluster: List the shared partitions that are available for use in your Messenger system.
  • Page 242 Section 22.2.1, “Creating Your Messenger System and Installing the Messenger Agents,” on page 231. If you use NSS volumes in your cluster, configure the Messenger agents so that they run as a non-root user. “Setting Up Non-root Access on NSS Volumes on Each Node” on page 232.
  • Page 243 Chapter 24, “Using GroupWise with Conferencing,” on page 263 Chapter 25, “Streamlining Authentication to Teaming or Conferencing,” on page 265 For background information about Novell Teaming and Novell Teaming + Conferencing, see the Collaboration Tools and Organizational Success white paper (http://www.novell.com/rc/ docrepository/public/37/basedocument.2007-09-18.8712884885/4622072%20-...
  • Page 244 244 GroupWise 7 Interoperability Guide...

  • Page 245: Using Groupwise With Novell Teaming

    Novell Teaming 1.0 Installation Guide lists the standard system requirements for Novell Teaming. If you are installing Teaming on Novell Open Enterprise (OES) 2 or SUSE Linux Enterprise Server (SLES) 10 SP1, a default operating system installation does not meet these system requirements.

  • Page 246: Linux Open File Limit

    Section 23.2.4, “Potential Web Server Port Conflicts,” on page 247 23.2.1 Linux Open File Limit The default limit on the number of open files on SLES 10 is not sufficient for Novell Teaming. To configure SLES 10 with an appropriate open file limit: 1 Edit the /etc/security/limits.conf file in an ASCII text editor.

  • Page 247: Mysql Setup

    23.2.4 Potential Web Server Port Conflicts Novell Teaming includes its own Web server. If the Linux server where you plan to install Novell Teaming already has a Web server on it, make sure that you specify different, unique port numbers when you install Novell Teaming or remove the existing Web server from the Teaming server.

  • Page 248: Installing Novell Teaming With Groupwise

    Section 23.3.2, “Performing the Novell Teaming Installation,” on page 248 23.3.1 Preparing for the Novell Teaming Installation Before you install Novell Teaming with eDirectory and GroupWise, you need to gather the following system and GroupWise information: The DNS hostname of the server where you plan to install Teaming.

  • Page 249: Configuring Ldap Authentication

    23.5 Configuring GroupWise to Support Your Teaming Installation Novell Teaming requires an integrated e-mail system in order for the Teaming site and the GroupWise system to exchange messages. Section 23.5.1, “Configuring Outgoing E-Mail from Teaming to GroupWise,” on page 249 Section 23.5.2, “Configuring Incoming E-Mail from GroupWise Users to the Novell Teaming...
  • Page 250 Teaming site’s content and messages from Teaming site users sent to GroupWise mailboxes. Your Novell Teaming system needs an administrator e-mail account that is responsible for sending notifications from Teaming folders and e-mail messages from Teaming site users to GroupWise mailboxes.

  • Page 251: Configuring Incoming E-Mail From Groupwise Users To The Novell Teaming Site

    To enable incoming e-mail after installation: 1 As the Teaming Site Manager user (username admin), display the Teaming site Home page. 2 In the Novell Teaming Administration portlet, click Configure Site Incoming Email Schedule. Using GroupWise with Novell Teaming 251...
  • Page 252 3 Select Enable Incoming Mail. 4 Select Every Day. Select Weekly, then select the days of the week when you want the Teaming SMTP server to check for incoming mail. 5 Select Repeat Every. 6 Leave the default of 0.25 hours. This configures the Teaming SMTP server to check the GroupWise Teaming mailbox for incoming messages every 15 minutes.
  • Page 253 1a Double-click the GroupWise icon on your desktop. 1b When prompted for your personal GroupWise password, click Cancel to display the Novell GroupWise Startup dialog box. 1c Replace your username with the username of the Teaming administrator user. Using GroupWise with Novell Teaming 253...
  • Page 254 2 In the upper left corner of the GroupWise client window, click Online > Proxy. 3 Click the Address Book icon, then select the Novell GroupWise Address Book. 4 In the Look For field, start typing the name of the resource until it is highlighted in the Address List, then click OK to proxy into the resource mailbox.
  • Page 255 9 For each e-mail address, click Edit, specify the password for the e-mail account, then click OK. 10 When all the e-mail addresses have passwords associated with them, return to the Teaming home page. Using GroupWise with Novell Teaming 255...
  • Page 256 Configuring the GroupWise Internet Agent for POP or IMAP By default, the GroupWise Internet Agent is configured for both POP and IMAP. Whether your Teaming site uses POP or IMAP is determined by your selection in the Inbound E-Mail Configuration window when you ran the Teaming installer.

  • Page 257: Testing Groupwise Integration With Novell Teaming

    5f Select the distribution list of Teaming resources, then click OK to add the new class of service. 6 Click OK to save the settings. 23.5.3 Testing GroupWise Integration with Novell Teaming After you have configured outgoing and incoming e-mail, you are ready to test your e-mail integration.
  • Page 258 To verify that e-mail is successfully delivered from the GroupWise system to the Teaming site: 1 In the GroupWise client, send a message to one of the nickname addresses you created in “Associating a Resource with a Novell Teaming Folder” on page 254.

  • Page 259: Receiving Notification Of Teaming Site Activity In Your Groupwise Client

    Teaming appointment is placed on your GroupWise calendar. 23.8 Adding Portlets to Novell Teaming Portlets are optional user interface components that you can add to your Novell teaming site to increase its functionality. Section 23.8.1, “Adding Liferay Portlets,” on page 259 Section 23.8.2, “Adding GroupWise Portlets,”...
  • Page 260 /opt/icecore/liferay-portal-tomcat-5.5-jdk5-4.3.0/webapps/ROOT/WEB-INF NOTE: The part of the path before the webapps directory might be different on your system, depending on where you installed Novell Teaming. 1 Edit the liferay-portlet.xml file. Each portlet is defined between <portlet> and </portlet> tags. Each portlet has a name which is a number from 1 to113.
  • Page 261 <category...> and </category> tags. <portlet id="nn" /> where nn is the numeric name of the portlet. To use a Liferay-defined category for the portlet, add a set of lines similar to the following: Using GroupWise with Novell Teaming 261...

  • Page 262: Adding Groupwise Portlets

    2 Step 9 Save and close the liferay-display.xml file. 10 Restart Novell Teaming to make the additional portlets available to Teaming users. 23.8.2 Adding GroupWise Portlets GroupWise Mail and Calendar portlets are available for adding GroupWise functionality into your Teaming site.

  • Page 263: Using Groupwise With Conferencing

    Section 24.1.1, “Preparing for GroupWise Integration with Conferencing,” on page 263 Section 24.1.2, “Integrating GroupWise with Novell Conferencing,” on page 263 Section 24.1.3, “Testing GroupWise as the Novell Conferencing E-Mail System,” on page 264 24.1.1 Preparing for GroupWise Integration with Conferencing...

  • Page 264: Testing Groupwise As The Novell Conferencing E-Mail System

    7b Specify the password for the username, then press Enter. 8 Continue as usual with the Conferencing installation. 24.1.3 Testing GroupWise as the Novell Conferencing E-Mail System 1 Make sure that users receive the Conferencing Welcome e-mail, as described in “Installing the...

  • Page 265: Streamlining Authentication To Teaming Or Conferencing

    You can implement single sign-on for use with Teaming or Conferencing. Section 25.1, “Using iChain for Authenticating to Teaming or Conferencing,” on page 265 Section 25.2, “Using Novell Access Manager for Authenticating to Teaming or Conferencing,” on page 267 25.1 Using iChain for Authenticating to Teaming or Conferencing ®...

  • Page 266: Consoleone

    For example, you might want to call it Teaming or Conferencing, as appropriate. 4 Select Allow Pages to Be Cached at the Browser. 5 Select Enable Multi-Homing. 5a In the Multi-Homing Options dialog box, select Domain-Based Multi-Homing to configure the Teaming or Conferencing URL as a DNS name prepended to your Internet domain name, for example: http://teaming.corporate.net The A record for the DNS name must already exist.

  • Page 267: Using Ichain For Authentication

    Teaming or Conferencing in a single step, using their eDirectory or LDAP passwords. 25.2 Using Novell Access Manager for Authenticating to Teaming or Conferencing Novell Access Manager is not currently supported for use with Novell Teaming or Conferencing. Streamlining Authentication to Teaming or Conferencing 267...
  • Page 268 268 GroupWise 7 Interoperability Guide...

  • Page 269: Part Iv Other Novell Products

    Other Novell Products Chapter 26, “GroupWise DirXML Driver for Novell Identity Manager,” on page 271 Chapter 27, “GroupWise Customization Tools,” on page 275 Chapter 28, “Novell exteNd,” on page 277 Other Novell Products...
  • Page 270 270 GroupWise 7 Interoperability Guide...

  • Page 271: Groupwise Dirxml Driver For Novell Identity Manager

    Section 26.1.9, “Enabling the DirXML Warnings,” on page 273 26.1.1 Recovering a Deleted GroupWise Account 1 Using the DirXML Management role in Novell iManager, stop the GroupWise DirXML driver. 2 Recover the deleted account, as described in “Recovering Deleted GroupWise Accounts”...

  • Page 272: Grafting Users

    3 Using the DirXML Management role, restart the GroupWise DirXML driver. 26.1.4 Converting a User to an External Entity 1 On the DirXML tab of the User object in Novell iManager, disable the association with the GroupWise DirXML driver. 2 Convert the user, as described in “Convert User to External...

  • Page 273: Resolving An Invalid Association

    26.1.7 Resolving an Invalid Association 1 On the DirXML tab of the User object in Novell iManager, disable the association with the GroupWise DirXML driver. 2 Resolve the invalid association, as described in “Invalid Associations” in “System” in the GroupWise 7 Administration Guide.
  • Page 274 274 GroupWise 7 Interoperability Guide...

  • Page 275: Groupwise Customization Tools

    (such as C++). It also supports COM Automation, which is an industry standard for interfacing applications. For more information, see GroupWise Administrative Object API (http://developer.novell.com/wiki/index.php/ GroupWise_Administrative_Object_API). GroupWise C3PO (Custom 3rd-Party Object): Works with C++, Delphi, or Visual Basic to let you add menu and toolbar items to trigger applications.
  • Page 276 The GroupWise WSDL (Service Descriptive Language) combines everything into a GroupWise Web service. For more information, see GroupWise Web Service (SOAP) (http:// developer.novell.com/wiki/index.php/GroupWise_Web_Service_%28SOAP%29). GroupWise MAPI: Uses a set of object-oriented functions that provide messaging capabilities. The Messaging Application Programming Interface (MAPI) is used by mail- enabled applications to create, transfer, and store messages, as well as to handle complex addressing information.

  • Page 277: Novell Extend

    WebAccess, you must copy some of the exteNd template files from the frames directory into the css directory. Refer to the Identity Manager Accessory Portlet Reference Guide (http://developer.novell.com/wiki/index.php/ GroupWise_Controls_for_ActiveX) to determine which exteNd template files you should copy to the css directory.
  • Page 278 278 GroupWise 7 Interoperability Guide...

  • Page 279: Part V Heartbeat On Linux

    Heartbeat on Linux Chapter 29, “Introduction to GroupWise 7 and Heartbeat on Linux,” on page 281 Chapter 30, “Planning GroupWise in a Heartbeat Cluster,” on page 285 Chapter 31, “Setting Up a Heartbeat Cluster,” on page 297 Chapter 32, “Setting Up a Domain and a Post Office in a Heartbeat Cluster,” on page 307 Chapter 33, “Implementing the Internet Agent in a Heartbeat Cluster,”...
  • Page 280 280 GroupWise 7 Interoperability Guide...

  • Page 281: Introduction To Groupwise 7 And Heartbeat On Linux

    The following software is required to set up a GroupWise system in a Heartbeat cluster: SUSE Linux Enterprise Server 10, plus the latest update Heartbeat 2, plus the latest update GroupWise 7, plus Support Pack 2 or later ® Novell eDirectory 8.7 or later, plus the latest Support Pack ® ConsoleOne 1.3.6 or later...

  • Page 282: Installing Heartbeat Packages

    Set up Heartbeat 2 on each node in the cluster by following the instructions provided in Installing a Heartbeat 2 Cluster Using YaST in the SUSE Linux Enterprise Server 10 Installation and Administration Guide (http://www.novell.com/documentation/sles10/pdfdoc/sles_admin/ sles_admin.pdf). The setup process creates basic Heartbeat configuration files: /etc/ha.d/ha.cf (http://www.linux-ha.org/ha.cf) This is the main Heartbeat configuration file.

  • Page 283: Starting Heartbeat

    29.5 Starting Heartbeat The Heartbeat packages must be installed and the configuration files set up on each node in the cluster. Then use the following command to start Heartbeat on each node in the cluster: rcheartbeat start To make sure that Heartbeat starts each time the node restarts, use the following command: chkconfig heartbeat on Two log files provide status information about the functioning of the Heartbeat cluster and can be viewed by using the following commands:...

  • Page 284: Setting Up Node Fencing Or Resource Fencing

    Do the following to prepare partitions for use by GroupWise: Delete any existing partitions. They are not the correct type for use with GroupWise. Create private cluster container partitions. These partitions are cluster aware and prevent two nodes from being active on the same partition at the same time. 29.8 Setting Up Node Fencing or Resource Fencing Although private cluster container partitions protect against two nodes being active on the same...

  • Page 285: Planning Groupwise In A Heartbeat Cluster

    Planning GroupWise in a Heartbeat Cluster The majority of this part of the GroupWise 7 Interoperability Guide (Chapter 30, “Planning GroupWise in a Heartbeat Cluster,” on page 285 through Chapter 36, “Backing Up a GroupWise System in a Heartbeat Cluster,” on page 363) is designed for those who are creating a new ®...

  • Page 286: Recording Heartbeat Cluster Information

    Section 30.1.2, “Planning GroupWise Cluster Organization,” on page 286 Section 30.1.3, “Planning Cluster Resources and Resource Groups,” on page 287 Section 30.1.4, “Planning Secondary IP Addresses,” on page 287 30.1.1 Recording Heartbeat Cluster Information Now that you have installed Heartbeat on Linux, you need to record key information about the cluster.

  • Page 287: Planning Cluster Resources And Resource Groups

    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.

  • Page 288: Planning A Software Distribution Directory For A Cluster

    HEARTBEAT CLUSTERING WORKSHEET Under Item 5: IP Address Resources, list the secondary IP addresses that you want to use for GroupWise agents. The IP address resource also needs a unique name. Initially, you plan one or two secondary IP addresses for the MTA and the POA for the primary domain and initial post office. Later, you plan additional secondary IP addresses for additional resource groups.

  • Page 289: Planning A New Clustered Post Office

    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, remember that it will be on shared storage, not on the node where you will be running the GroupWise Installation program.

  • Page 290: Planning A New Library For A Clustered Post Office

    HEARTBEAT CLUSTERING WORKSHEET Under Item 8: Cluster Resource for Post Office, specify the name of the cluster resource group that will represent the post office (for example, group_po2), the name of the resource for the POA (for example, resource_poa2), and the name of the post office, including its domain (for example, Waltham1.Sales). IMPORTANT: Do not create the new post office until you are instructed to do so in Chapter 32, “Setting Up a Domain and a Post Office in a Heartbeat Cluster,”...

  • Page 291: Groups

    the physical IP address of the node. Secondary IP addresses are created by setting up IP address resources, as described in Section 30.1.4, “Planning Secondary IP Addresses,” on page 287. The IP address resource moves with each agent when it fails over, so that, in the case of the POA, GroupWise clients do not lose their connections to the POA.
  • Page 292 Place Constraint The place constraint controls where nodes in a cluster resource group can fail over. A place constraint includes a score. A score of 100 (the default) means that the resource group to which the constraint is applied should run on the node assigned to the place constraint whenever possible. A score of 50 means that the resource group to which the constraint is applied can fail over to the assigned node when the initial node fails.

  • Page 293: Groupwise Clustering Worksheets

    30.6.3 Planning the Linux Agent Installation Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the GroupWise Linux agents are the same in a clustering environment as for any other environment. Review “Planning the GroupWise Agents”, then print and fill out the “GroupWise Agent Installation...

  • Page 294: Groupwise Clustering Worksheet

    Item Explanation 5) IP Address Resources: List the IP address resources and secondary IP addresses that will be assigned to GroupWise components. For more information, see Section 30.1.4, “Planning Secondary IP Addresses,” on page 287. 6) Cluster Resource Groups for If you want your domain and post office to fail over together, GroupWise Components you need one cluster resource group.
  • Page 295 Item Explanation 2) Domain Name: Specify the name for the domain. Specify the directory on the resource group partition where you want to create the new Domain Directory: domain. Specify the mount point where each node will mount the domain directory. Mount Point: For more information, see Section 13.3, “Planning a New...
  • Page 296 296 GroupWise 7 Interoperability Guide...

  • Page 297: Setting Up A Heartbeat Cluster

    Setting Up a Heartbeat Cluster You use the HA Management Client program to configure your Heartbeat cluster. Section 31.1, “Starting the HA Management Client,” on page 297 Section 31.2, “Creating a Cluster Resource Group,” on page 298 Section 31.3, “Creating Native Heartbeat Resources,” on page 299 Section 31.4, “Creating Heartbeat Constraints,”...

  • Page 298: Creating A Cluster Resource Group

    5 Make sure that all nodes (Heartbeat Clustering Worksheet item 2) are listed. 6 Continue with Creating a Cluster Resource Group. 31.2 Creating a Cluster Resource Group 1 In the HA Management Client, select Resources, then click Add New Item. 2 In the Item Type drop-down list, select group, then click OK.

  • Page 299: Creating Native Heartbeat Resources

    31.3 Creating Native Heartbeat Resources When you create a cluster resource group for use with GroupWise, the group must always include an EVMS container resource, a file system resource, and an IP address resource. These are considered native Heartbeat resources, because all Heartbeat clusters have them. Internally, GroupWise domains and post offices are directory structures containing files and databases that must be housed in a file system on shared storage.

  • Page 300: File System Resources

    4 In the Belong to Group field, select the cluster resource group where you want to create the EVMS contain resource. 5 In the Type list, select evms_failover. 6 In the Parameters list, specify the EVMS container name for the shared storage: 6a Click Add Parameter.

  • Page 301: Ip Address Resources

    6b Set the directory parameter to the mount point (Heartbeat Clustering Worksheet item 6c Set the fstype parameter to the type of file system on the device (Heartbeat Clustering Worksheet item 7 Click Add to create the file system resource. 8 Repeat Step 1 through...

  • Page 302: Creating Heartbeat Constraints

    31.4 Creating Heartbeat Constraints Heartbeat constraints control which nodes in the cluster each resource group can run on and when. In the HA Management Client, constraints are located below nodes and resources. The following sections provide some basics to help you get your GroupWise system set up in a Heartbeat cluster.

  • Page 303: Order Constraints

    4 Click Add Expression to add attributes to the place constraint. 5 Accept the defaults of #uname (name of the node) and eq (equals), in the Value field, select the hostname of the node that you want associated with this place constraint (Heartbeat Clustering Worksheet item 9 for a domain and...

  • Page 304: Colocation Constraints

    You can change the attributes of the order constraint at any time if the needs of your cluster change. 4 Repeat Step 1 through Step 3 for each order constraint that you need in your GroupWise system. 5 Continue with Colocation Constraints.

  • Page 305: Starting The Native Heartbeat Resources

    31.5 Starting the Native Heartbeat Resources In the HA Management Client: 1 In each cluster resource group, select the EVMS container resource, then click Start Resource. 2 Select the file system resource, then click Start Resource. 3 Select the IP address resource, then click Start Resource. When a resource starts successfully, the Status column indicates that it is running.
  • Page 306 306 GroupWise 7 Interoperability Guide...

  • Page 307: Setting Up A Domain And A Post Office In A Heartbeat Cluster

    If necessary, you can download ConsoleOne for Linux from the Novell Product Downloads site (http://download.novell.com). ConsoleOne is always installed in /usr/Consoleone. 3 If necessary, mount the partition where you want to create the GroupWise software distribution directory...

  • Page 308: Creating A New Secondary Domain In A Heartbeat Cluster

    5 From the GroupWise 7 Administrator for Linux CD, run the GroupWise Installation program (install), as described in “Starting the GroupWise Installation Program on Linux” in “Installing a Basic GroupWise System” in the GroupWise 7 Installation Guide. IMPORTANT: Do not select the Configure GroupWise for Clustering option at this time. 6 When you set up the software distribution directory, copy all of the agent software.

  • Page 309: Creating A New Post Office In A Heartbeat Cluster

    To create a new secondary domain in a clustering environment: 1 In the HA Management Client, start the EVMS container resource and the file system resource in order to mount the shared storage partition where the new secondary domain will be created. 2 In ConsoleOne, connect to the primary domain in your GroupWise system, as described in “Connecting to a Domain”...

  • Page 310: Installing And Configuring The Mta And The Poa In A Heartbeat Cluster

    4 Create the new post office, following the steps provided in “Creating the New Post Office” in “Post Offices” in the GroupWise 7 Administration Guide. Use the Post Office Worksheet you filled out in Section 13.4, “Planning a New Clustered Post Office,”...

  • Page 311: Running The Groupwise Installation Program On The Initial Node

    The agents must be installed on each node where the domain might be mounted (Heartbeat Clustering Worksheet item 9) and where the post office might be mounted (Heartbeat Clustering Worksheet item 10). Section 32.4.1, “Running the GroupWise Installation Program on the Initial Node,” on page 311 Section 32.4.2, “Running the GroupWise Installation Program on Subsequent Nodes,”...
  • Page 312 GroupWise agents (POA, MTA, Internet Agent, and WebAccess Agent) and the Messenger agents (Messaging Agent and Archive Agent) in the HA Management Client. The script is installed as part of the novell-groupwise-gwha package and depends on the High Availability service configuration file (gwha.conf) to identify the agents that are being managed by the HA Management Client.

  • Page 313: Running The Groupwise Installation Program On Subsequent Nodes

    A clusterimport.conf file is created in the gwinst subdirectory of the software distribution directory from which you ran the GroupWise Installation program, so that the cluster-specific information collected when you configured the agents on the initial node is available when you install the agents on subsequent nodes. The agents are not configured to start automatically on system startup.
  • Page 314 3 Install the agent software on the node as usual, but do not use the Configure option. You will use the Import Clustering Data option instead of the Configure option. 4 On the main page of the GroupWise Installation program, click Import Clustering Data, then click Next.

  • Page 315: Creating And Configuring Groupwise Cluster Resources

    The GroupWise High Availability service (GWHA) is automatically configured on the current node and its configuration file (gwha.conf) is created in the /etc/opt/ novell/groupwise directory of the node. It is configured specifically for the agents you just selected. The OCF Resource Agent script (GroupWise), required by the HA Management Client to support GroupWise resources, is installed in the /usr/lib/ocf/resource.d/...
  • Page 316 4 In the Belong to Group field, select the cluster resource group where you want to create the GroupWise resource. 5 In the Type list, select GroupWise (ocf/novell). The OCF Resource Agent script (GroupWise) added this item to the list.

  • Page 317: Testing Your Agent Installation On Each Node

    Agents” in the GroupWise 7 Administration Guide. /opt/novell/groupwise/agents/bin/gwmta --show @domain.mta & /opt/novell/groupwise/agents/bin/gwpoa --show @post_office.poa & 2 Stop the agents by clicking File > Exit 3 After you can see that the agents start successfully, test them by starting them as daemons, as described in “Starting the Linux GroupWise Agents as...

  • Page 318: Changing Agent Paths To Locations On The Shared Storage Partition

    If you receive the error Unmanaged on node, then you have failed to test the agents on one or more nodes. On each node, view the gwha.conf file in the /etc/opt/novell/ groupwise directory. Each section should be preceded by the name of a domain for an MTA or a post office and domain for a POA.

  • Page 319: Setting Up New Instances Of The Agents Without Installing The Agent Software

    Setting the MTA Certificate and Key File Path If you plan to enable SSL for the MTA, as described in “Securing the Domain with SSL Connections to the MTA” in “Message Transfer Agent” in the GroupWise 7 Administration Guide: 1 On the shared storage partition of the cluster resource group where the domain is located, create the directory where you want to store the certificate file and key file required for SSL.

  • Page 320: Testing Your Clustered Groupwise System

    4 Save the new startup file. 5 Edit the GroupWise High Availability service configuration file (/etc/opt/novell/ groupwise/gwha.conf). 6 Make a copy of the section for an existing domain and its MTA or post office and its POA, then modify the information for the new domain or post office and its accompanying agent.

  • Page 321: Managing Your Clustered Groupwise System

    WARNING: These last two tests should not be performed in a production system because they can result in damage to GroupWise databases. 32.6 Managing Your Clustered GroupWise System After you have set up a basic clustered GroupWise system, you should consider some long-term management issues.

  • Page 322: Knowing What To Expect In Mta And Poa Failover Situations

    This records this vital information in eDirectory as well as in the MTA startup file. 11 Click OK to save the MTA description and secondary IP address. 12 Continue with Recording Cluster-Specific Information for a Post Office and Its POA. Recording Cluster-Specific Information for a Post Office and Its POA To permanently record important cluster-specific information for a post office: 1 In ConsoleOne, browse to and right-click the Post Office object, then click Properties.

  • Page 323: What's Next

    Typically, the POA returns to full functionality faster than the MTA. This benefits GroupWise client users, who can reconnect to their mailboxes very quickly and probably do not notice if messages to users in other post offices are not delivered immediately. The only time a user needs to restart the GroupWise client is if he or she was actually in the process of sending a message when the POA went down.
  • Page 324 324 GroupWise 7 Interoperability Guide...

  • Page 325: Implementing The Internet Agent In A Heartbeat Cluster

    Implementing the Internet Agent in a Heartbeat Cluster ® You should already have set up at least a basic GroupWise system in your Heartbeat cluster, as described in Chapter 30, “Planning GroupWise in a Heartbeat Cluster,” on page 285, Chapter 31, “Setting Up a Heartbeat Cluster,”...

  • Page 326: Planning A Cluster Resource Group For The Internet Agent

    As with the MTA and the POA, the Internet Agent needs cluster nodes, native Heartbeat resources, GroupWise resources, and a cluster resource group in order to function in your Heartbeat cluster. For a review of these cluster components, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134.

  • Page 327: Recording The Internet Agent Secondary Ip Address

    33.1.3 Recording the Internet Agent Secondary IP Address As with the MTA and the POA, the Internet Agent needs a secondary IP address that remains the same no matter which node in the cluster it is running on. You can place the Internet Agent and its domain in a cluster resource group where a domain or post office already reside, which means that the Internet Agent shares the same secondary IP address as that domain or post office and fails over along with that domain or post office.

  • Page 328: Planning The Mta Installation

    Standard Ports Table 33-1 Protocol Standard Port IMAP4 LDAP POP3 SMTP By default, the Internet Agent sends outgoing messages on the primary IP address of the node where it is running. If you decide to use this default configuration, your firewall must be configured to allow outbound TCP/IP traffic from all nodes where the Internet Agent could fail over.

  • Page 329: Setting Up The Internet Agent In A Heartbeat Cluster

    33.2 Setting Up the Internet Agent in a Heartbeat Cluster You should already have reviewed Section 15.1, “Planning the Internet Agent in a Linux Cluster,” on page 167 and filled out Section 15.5, “Internet Agent Clustering Worksheet,” on page 184. You are now ready to complete the following tasks to set up the Internet Agent in a clustering environment: Section 33.2.1, “Setting Up Native Heartbeat Cluster Resources for the Internet Agent,”...

  • Page 330: Installing The Mta For The Internet Agent Domain

    33.2.3 Installing the MTA for the Internet Agent Domain The MTA for the Internet Agent domain can be installed just like any other MTA in your clustered GroupWise system. Follow the instructions in Section 14.4, “Installing and Configuring the MTA and the POA in a Cluster,”...
  • Page 331 Internet Agent. If it is not already present, the OCF Resource Agent script (GroupWise) is installed in the /usr/lib/ocf/resource.d/novell) directory on the node for use by the HA Management Client. The clusterimport.conf file in the gwinst subdirectory of the software...
  • Page 332 6 For optimum security, configure the Internet Agent to run as a non-root user, as described in “Running the Linux GroupWise Agents as a Non-root User” in “Installing GroupWise Agents” in the GroupWise 7 Installation Guide. 7 Continue with Running the Internet Agent Installation Program on Subsequent Nodes.
  • Page 333 The GroupWise High Availability service (GWHA) is automatically configured on the current node and its configuration file (gwha.conf) is created in the /etc/opt/ novell/groupwise directory. It is configured specifically for the agents you just selected. If it is not already present, the OCF Resource Agent script (GroupWise) is installed in the /usr/lib/ocf/resource.d/novell) directory on the node for use by the HA...
  • Page 334 4 In the Belong to Group field, select the cluster resource group where you want to create the GroupWise resource for the Internet Agent 5 In the Type list, select GroupWise (ocf/novell). The OCF Resource Agent script (GroupWise) added this item to the list.
  • Page 335 “Linux: Starting the Internet Agent” in “Installing the GroupWise Internet Agent” in the GroupWise 7 Installation Guide. /opt/novell/groupwise/agents/bin/gwia --show @gwia.cfg & 2 Stop the Internet Agent by clicking File > Exit. Implementing the Internet Agent in a Heartbeat Cluster 335...
  • Page 336 Agent on one or more nodes. On each node, view the gwha.conf file in the /etc/opt/ novell/groupwise directory. Each Internet Agent section should be preceded by the name of the domain followed by the eDirectory object name of the Internet Agent (GWIA by default).
  • Page 337 7 In the SSL Key File field, browse to and select the key file. 8 Click OK. 9 Continue with Enabling Internet Addressing for Your Clustered GroupWise System. Enabling Internet Addressing for Your Clustered GroupWise System Setting up Internet addressing for a clustered Internet Agent is no different from setting it up for an Internet Agent in any other environment.

  • Page 338: Testing The Internet Agent In A Heartbeat Cluster

    Verifying Post Office Links In the Internet Agent object property page: 1 Click Post Office Links. 2 Verify that the Access Mode column displays C/S (for client/server mode) for all post offices serviced by the Internet Agent. 3 Verify that the Links column displays the secondary IP addresses of the cluster resource groups that the post offices belong to, not the IP addresses of any nodes in the cluster.

  • Page 339: Managing The Internet Agent In A Heartbeat Cluster

    WARNING: These last two tests should not be performed on a production system because they can result in damage to GroupWise databases. 33.4 Managing the Internet Agent in a Heartbeat Cluster After you have installed the Internet Agent in a cluster, you should consider some long-term management issues.

  • Page 340: Knowing What To Expect In An Internet Agent Failover Situation

    2 Click GroupWise > Identification. 3 In the Description field, record the secondary IP address associated with the Internet Agent domain’s cluster resource group. 4 Click OK to save the Internet Agent information. 5 Continue with Knowing What to Expect in an Internet Agent Failover Situation.
  • Page 341 Item Explanation 5) Internet Agent Constraints: Specify the Heartbeat constraints that you want to put on the Internet Agent cluster resource group to control what nodes it can run on. Place For more information, see Section 15.1.3, “Determining an Order Appropriate Failover List for the Internet Agent,”...
  • Page 342 342 GroupWise 7 Interoperability Guide...

  • Page 343: Implementing Webaccess In A Heartbeat Cluster

    Implementing WebAccess in a Heartbeat Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 30, “Planning GroupWise in a Heartbeat Cluster,” on page 285, Chapter 31, “Setting Up a Heartbeat Cluster,” on page 297, and Chapter 32, “Setting Up a Domain and a Post Office in a Heartbeat Cluster,”...

  • Page 344: Planning A Cluster Resource Group For The Webaccess Agent

    As with the MTA and the POA, the WebAccess Agent needs cluster nodes, native Heartbeat resources, GroupWise resources, and a cluster resource group in order to function in your Heartbeat cluster. For a review of these cluster components, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134.

  • Page 345: Recording The Webaccess Secondary Ip Address

    When you have completed the Domain Worksheet, transfer the key information from the Domain Worksheet to the WebAccess Agent Clustering Worksheet. WEBACCESS AGENT CLUSTERING WORKSHEET Under Item 6: WebAccess Agent Domain Name, transfer the domain name and domain directory to the WebAccess Agent Clustering Worksheet.

  • Page 346: Planning The Mta Installation

    34.2.5 Planning the MTA Installation Follow the instructions in Section 13.6.4, “Planning the Linux Agent Installation,” on page 139, then return to this point. After you follow the instructions, you have a filled-out System Clustering Worksheet to use when you install the MTA. IMPORTANT: Do not install the Linux MTA until you are instructed to do so in Section 16.3, “Setting Up the WebAccess Agent in a Linux Cluster,”...

  • Page 347: Setting Up Native Heartbeat Resources For The Webaccess Agent

    34.3.1 Setting Up Native Heartbeat Resources for the WebAccess Agent 1 Start the HA Management Client, as described in Section 31.1, “Starting the HA Management Client,” on page 297. 2 Create a cluster resource group for the WebAccess agent and its domain (WebAccess Agent Clustering Worksheet item 2), as described in...

  • Page 348: Installing And Configuring The Webaccess Agent In A Heartbeat Cluster

    34.3.4 Installing and Configuring the WebAccess Agent in a Heartbeat Cluster After you have created a domain for the WebAccess Agent and installed the MTA for that domain, you are ready to install and configure the WebAccess Agent. The WebAccess Agent must be installed on each node where it is allowed to fail over (WebAccess Agent Clustering Worksheet item “Running the WebAccess Agent Installation Program on the Initial Node”...
  • Page 349 If this is the first GroupWise agent installed on this node, the GroupWise High Availability service (GWHA) is automatically configured and its configuration file (gwha.conf) is created in the /etc/opt/novell/groupwise directory. If another GroupWise agent has already been installed on this node, the gwha.conf file is updated to include the WebAccess Agent.
  • Page 350 Because of the existence of the clusterimport.conf file in the gwinst subdirectory of the software distribution directory, a new installation option, Import Clustering Data, is now available on the main GroupWise Installation program page. 3 Install the WebAccess Agent software on the node as usual, but do not use the Configure option.
  • Page 351 The GroupWise High Availability service is automatically configured on the current node and its configuration file (gwha.conf) is created in the /etc/opt/novell/ groupwise directory. It is configured specifically for the agents you just selected.
  • Page 352 4 In the Belong to Group field, select the cluster resource group where you want to create the GroupWise resource for the WebAccess Agent 5 In the Type list, select GroupWise (ocf/novell). The OCF Resource Agent script (GroupWise) added this item to the list.
  • Page 353 If you receive the error Unmanaged on node, then you have failed to test the WebAccess Agent on one or more nodes. On each node, view the gwha.conf file in the /etc/opt/ novell/groupwise directory. Each WebAccess Agent section should be preceded by WEBAC70A. If any section is preceded by a startup file name (for example, @webac70a.waa), then that WebAccess Agent has not yet been initialized by being run...
  • Page 354 manually. To resolve the problem, you can run the WebAccess Agent manually on that node, or you can replace the @webac70a.waa with WEBAC70A, being sure to follow the same format as the other WebAccess Agent section headings in the gwha.conf file. 8 When you have installed the WebAccess Agent on all of the nodes where you want it to fail over, continue with Configuring Clustered...

  • Page 355: Installing And Configuring The Webaccess Application On Your Web Server

    Verifying WebAccess Agent Object Properties During installation of the WebAccess Agent, the WebAccess Agent object should have been configured correctly. However, it can be helpful to verify certain cluster-specific information in order to familiarize yourself with the configuration of a clustered WebAccess Agent. “Accessing WebAccess Agent Object Properties”...

  • Page 356: Testing The Webaccess Agent In A Heartbeat Cluster

    34.4 Testing the WebAccess Agent in a Heartbeat Cluster After you have installed and configured the WebAccess Agent in your Heartbeat cluster, and the WebAccess Application with your Web server, you can use the following methods to test whether the WebAccess Agent fails over as expected: In the HA Management Client, select a node where the WebAccess Agent is running, then click...

  • Page 357: Updating Groupwise Objects With Cluster-Specific Descriptions

    34.5.1 Updating GroupWise Objects with Cluster-Specific Descriptions After installing the WebAccess Agent in your clustered GroupWise system, while the cluster- specific information is fresh in your mind, you should record the cluster-specific information as part of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the information in the GroupWise objects if the configuration of your system changes.

  • Page 358: Webaccess Agent Clustering Worksheet

    When the WebAccess Agent fails over, the WebAccess client user sees the following message: Unable to communicate with the GroupWise WebAccess Agent The user just needs to be patient. When the WebAccess Agent comes up on the next node, the user can continue working without logging in again and no data is lost.
  • Page 359 Item Explanation 6) WebAccess Agent Specify a unique name for the WebAccess Agent domain. Specify the Domain Name: directory on the shared storage partition where you want to create the new domain. Specify the mount point on each node where you plan to Domain Directory: mount the shared storage partition.
  • Page 360 360 GroupWise 7 Interoperability Guide...

  • Page 361: Implementing Groupwise Monitor In A Heartbeat Cluster

    Implementing GroupWise Monitor in a Heartbeat Cluster Monitor is not currently supported in a Heartbeat cluster. Implementing GroupWise Monitor in a Heartbeat Cluster...
  • Page 362 362 GroupWise 7 Interoperability Guide...

  • Page 363: Backing Up A Groupwise System In A Heartbeat Cluster

    Backing Up a GroupWise System in a Heartbeat Cluster ® To back up GroupWise data in a Heartbeat cluster, use the GroupWise Database Copy (DBCopy) utility to copy the data from the live GroupWise system to a static location for backup. For more information, see “Backing Up GroupWise Databases”...
  • Page 364 364 GroupWise 7 Interoperability Guide...

  • Page 365: Updating A Groupwise System In A Heartbeat Cluster

    Updating a GroupWise System in a Heartbeat Cluster ® In a Heartbeat cluster, you must install the GroupWise software on each node in the cluster. Before you run the GroupWise Installation program to install updated software, make sure you know all the nodes where the GroupWise software is already installed.
  • Page 366 366 GroupWise 7 Interoperability Guide...

  • Page 367: Moving An Existing Linux Groupwise 7 System Into A Heartbeat Cluster

    Moving an Existing Linux GroupWise 7 System into a Heartbeat Cluster ® If you are adding the high availability benefits of Heartbeat to a Linux GroupWise 7 system that is already up and running, the first step is to install Heartbeat, as described in Chapter 29, “Introduction to GroupWise 7 and Heartbeat on Linux,”...
  • Page 368 Move more domains and post offices into the cluster as needed. If you have GroupWise libraries, see Section 13.5, “Planning a New Library for a Clustered Post Office,” on page 137. Add other components to your clustered GroupWise system as needed, following the instructions in: Chapter 33, “Implementing the Internet Agent in a Heartbeat Cluster,”...

  • Page 369: Implementing Messenger In A Heartbeat Cluster

    If you put the Messenger agents in the same cluster resource group, they fail over together. If you put them in separate cluster resource groups, then they fail over separately. For a review of these cluster components, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 134.

  • Page 370: Recording The Messenger Agents' Secondary Ip Address

    Agent and the Archive Agent. The identifiers for the Messenger agents are their full eDirectory object names. You can look them up in the /etc/opt/novell/groupwise/gwha.conf file, which is the configuration file for the GroupWise High Availability service. The required format is .messagingagent.server_nameserver.messengerservice.organization.

  • Page 371: Planning The Messenger Agent Installation

    Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the Messenger agents are the same in a clustering environment as for any other environment. Review “Planning Your Novell Messenger System”, then print and fill out “Novell Messenger Worksheet”...

  • Page 372: Creating Your Messenger System And Installing The Messenger Agents

    2 From the Messenger 2 Administrator for Linux CD, run the Messenger Installation program, following the steps provided in “Starting the Messenger Installation Program on Linux” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide. 3 When asked if you are installing to a cluster, enter y for Yes.
  • Page 373 The Messenger Installation program then accesses the Messenger files that were created on the shared storage partition when the Messenger agents were installed on the initial node. From these files, the Messenger Installation program lists the probable configuration for the Messenger agents you are installing on the current node.
  • Page 374 The OCF Resource Agent script (GroupWise) adds this item to the list. If no GroupWise agents are installed on this node, you can copy the GroupWise script from the /usr/lib/ ocf/resource.d/novell directory from another node to this node so that the GroupWise (ocf/novell) resource type appears in the list.
  • Page 375 If you receive the error Unmanaged on node, then you have failed to test the Messenger agents on one or more nodes. On each node, view the gwha.conf file in the /etc/opt/ novell/groupwise directory. Each Messaging Agent section should be preceded by: .messagingagent.server_nameserver.messengerservice.organization Each Archive Agent section should be preceded by: .archiveagent.server_nameserver.messengerservice.organization.

  • Page 376: Changing Messenger Paths To Locations On The Messenger Partition

    Setting the Store Path The store path is the location where you want the archive created. During installation, the default store path is created in /var/opt/novell/messenger/aa/ store on each node, but you need the archive to be stored on the shared storage partition.
  • Page 377 1 Choose a directory for the Messaging Agent queue and create that directory on the shared storage partition. 2 In ConsoleOne, browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server. 3 Right-click the Messaging Agent object, then click Properties.

  • Page 378: Testing Your Clustered Messenger System

    1 Choose a directory for the Archive Agent queue and create that directory on the shared storage partition. 2 In ConsoleOne, browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server. 3 Right-click the Archive Agent object, then click Properties.

  • Page 379: Messenger Clustering Worksheet

    In comparison to failover, migration typically takes longer because the Messaging Agent methodically terminates its thread as part of its normal shutdown procedure. 39.5 Messenger Clustering Worksheet Item Explanation 1) Messenger Agent Nodes: List the nodes where you want the Messenger agents to fail over.
  • Page 380 Item Explanation 8) Archive Agent Network Information Record the Archive Agent network address information that you will need to install the Messaging Agent. Secondary IP address For more information, see Section 22.1.2, “Selecting the Messenger Partition and Secondary IP Address,” on page 230.

  • Page 381: Part Vi Microsoft Clustering Services On Windows

    Microsoft Clustering Services on Windows Chapter 40, “Introduction to GroupWise 7 and Microsoft Clusters,” on page 383 Chapter 41, “Planning GroupWise in a Microsoft Cluster,” on page 385 Chapter 42, “Setting Up a Domain and Post Office in a Microsoft Cluster,” on page 401 Chapter 43, “Implementing the Internet Agent in a Microsoft Cluster,”...
  • Page 382 382 GroupWise 7 Interoperability Guide...

  • Page 383: Introduction To Groupwise 7 And Microsoft Clusters

    Introduction to GroupWise 7 and Microsoft Clusters ® Before implementing GroupWise 7 in a Microsoft* cluster, make sure you have a solid understanding of Microsoft clustering technologies by reviewing the following information resources: Cluster Technologies Community Center (http://www.microsoft.com/windowsserver2003/ community/centers/clustering/more_resources.asp) Windows 2003 Clustering Services (http://www.microsoft.com/windowsserver2003/ technologies/clustering/default.mspx) Windows 2000 Clustering Technologies (http://www.microsoft.com/windows2000/ technologies/clustering/default.asp)
  • Page 384 fan-out-failover: The configuration where resources and resource groups from a failed node fail over to different nodes in order to distribute the load from the failed node across multiple nodes in the cluster. For example, if a node runs a resource group consisting of a domain and its MTA, another resource group consisting of a post office and its POA, and a third resource group for WebAccess, each resource group could be configured to fail over separately to different nodes in the cluster.

  • Page 385: Planning Groupwise In A Microsoft Cluster

    Planning GroupWise in a Microsoft Cluster The majority of this part of the guide (Chapter 41, “Planning GroupWise in a Microsoft Cluster,” on page 385 through Chapter 47, “Backing Up a GroupWise System in a Microsoft Cluster,” on ® page 439) is designed for those who are creating a new GroupWise system, or at least new domains and post offices, in a Microsoft cluster.

  • Page 386: Setting Up Your Microsoft Cluster

    41.1 Setting Up Your Microsoft Cluster As you set up your Microsoft cluster, record key information about the cluster on the System Clustering Worksheet: SYSTEM CLUSTERING WORKSHEET Under Item 1: Cluster Name, record the name of your Microsoft cluster. Under Item 2: Nodes in Cluster, list the servers that you have added to the cluster.

  • Page 387: Planning A New Clustered Post Office

    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.

  • Page 388: Planning A New Library For A Clustered Post Office

    41.4 Planning a New Library for a Clustered Post Office The considerations involved in planning a library in a Microsoft cluster are essentially the same as for any other environment. You can plan a library for a new clustered post office by following the standard instructions provided in “Creating and Managing Libraries”...

  • Page 389: Planning Shared Administrative Resources

    If a resource group’s current owner node fails, the resource group fails over to the next node in the possible owners list. You should customize the owners list for each GroupWise resource group based on the fan-out-failover principle. When a node fails, its resource groups should not all fail over together to the same node in the cluster.
  • Page 390 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 that is installed on the Windows...

  • Page 391: Deciding How To Install And Configure The Agents In A Cluster

    For short name resolution to work using DNS, the client workstation must either belong to the same DNS zone (such as support.novell.com) as the resource group, or the cluster resource zone must be configured in the client’s DNS suffix search path under TCP/IP settings for the workstation.
  • Page 392 The following filled-out version of the Network Address Worksheet illustrates one way this can be done: Domain Information Domain IP Address MTP Port HTTP Port Provo1 172.16.5.81 7100 7180 Post Office Information Post Office IP Address C/S Port MTP Port HTTP Port Development (same as MTA)

  • Page 393: Deciding Where To Install The Agent Software

    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.
  • Page 394 Because the agents must be installed as Windows services in a Microsoft cluster, you must initially run the Agent Installation program for each node in the cluster so that the Windows services for the agents get created, regardless of where you are planning to run the agents from. However, for updates, you need to run the Agent Installation program only once if you are running the agents from a shared disk.

  • Page 395: Planning The Agent Services

    Even if you choose to install the agents to the c:\grpwise directory of multiple nodes, you can still store the agent startup files on shared disks with the domains and post offices. The significant advantage of this approach is that you only have one startup file to modify per agent. AGENT CLUSTERING WORKSHEET Under Item 1: Agent Installation...

  • Page 396: Groupwise Clustering Worksheets

    GROUPWISE AGENT INSTALLATION WORKSHEET Under Item 2: Agents and Locations, mark POA Local to Post Office and MTA Local to Domain. In a Microsoft cluster, a domain or post office and its agent must be located on the same node in order to fail over together.
  • Page 397 Item Explanation 3) Resources for GroupWise List any shared locations that you want to set up for Administration: ConsoleOne or the software distribution directory. ConsoleOne: For more information, see Section 41.6, “Planning Shared Administrative Resources,” on page 389. Shared disk: Possible owners: Software Distribution Directory: Shared disk:...

  • Page 398: Network Address Worksheet

    Item Explanation 9) Document Storage Area Location: If you need a library for a clustered post office, mark where you want to create its document storage area and provide a At the post office directory if necessary. Outside the post office For more information, see Section 41.4, “Planning a New Separate post office...

  • Page 399: Agent Clustering Worksheet

    WebAccess Information WebAccess WebAccess WebAccess WebAccess Agent IP Address MTP Port HTTP Port Agent Port HTTP Port WebAccess Domain MTA WebAccess (same) Agent (GWINTER) 41.9.3 Agent Clustering Worksheet Item Explanation 1) Agent installation location: Mark the location where you will install the agent software. If necessary, specify the location where you will store agent Shared disk with domain or post startup files on the same shared disk with the domain or post...
  • Page 400 Item Explanation 7) POA Network Information: Gather the POA network address information from the “Network Address Worksheet” on page 398. POA IP address For more information, see “Planning Cluster-Unique Port POA client/server port Numbers for Agents in the Cluster” on page 391.

  • Page 401: Setting Up A Domain And Post Office In A Microsoft Cluster

    Setting Up a Domain and Post Office in a Microsoft Cluster You should have already reviewed “Planning GroupWise in a Microsoft Cluster” on page 385 filled out the “System Clustering Worksheet” on page 396, the “Network Address Worksheet” on page 398, and the “Agent Clustering Worksheet”...

  • Page 402: Configuring Short Name Resolution

    ® ® ConsoleOne uses Novell eDirectory to resolve the UNC path of a domain or post office directory into its network name in the cluster. For example, on the workstation where you run ConsoleOne, you need to map a drive to the location of a domain directory using the network name of the domain resource group so that ConsoleOne can access the domain database no matter which node in the cluster it is active on.

  • Page 403: Setting Up A New Groupwise System In A Cluster

    42.2 Setting Up a New GroupWise System in a Cluster The GroupWise Installation Advisor walks you through setting up the primary domain and an initial post office in the primary domain. You might be creating your primary domain and initial post office in the same resource group or in two different resource groups.

  • Page 404: Creating A New Secondary Domain In A Cluster

    42.3 Creating a New Secondary Domain in a Cluster After you have set up the primary domain and initial post office, as described in Section 42.2, “Setting Up a New GroupWise System in a Cluster,” on page 403, you can create additional secondary domains as needed.

  • Page 405: Creating A New Post Office In A Cluster

    Although a complete mesh link configuration is the most efficient, it might not be feasible in all situations. Set up as many direct TCP/IP links as possible for best MTA performance in the cluster. 9 Make sure you are still connected to the primary domain. 10 Rebuild the domain database for the new domain, following the steps provided in “Rebuilding Domain or Post Office...

  • Page 406: Installing And Configuring The Mta And The Poa In A Cluster

    5 In ConsoleOne, right-click the new Post Office object, then click Properties. 6 Click GroupWise > Post Office Settings, then in the Access Mode field, select Client/Server Only. 7 Right-click the new POA object, then click Properties. On the POA Agent Settings and Scheduled Events pages, you might want to specify unique times for the following POA activities to prevent multiple POAs from performing the same activities on the same node at the same time during a failover situation: Start User Upkeep...

  • Page 407: Installing The Agent Software In A Cluster

    Under some circumstances, the agent software has already been installed in the cluster and you simply need to create a new startup file specific to the new domain or post office. For example: You have created a new domain and/or post office in a GroupWise resource group where the agent software is already installed in the drive:\grpwise directory for the resource group.

  • Page 408: Editing Clustered Agent Startup Files

    7 If you installed the agent software to each node and you selected Yes for Consolidate Startup Files? (under Agent Clustering Worksheet item 1), copy one complete set of agent startup files to the planned location on the shared disk, then delete all agent startup files from the c:\grpwise directories on the nodes to avoid future confusion.

  • Page 409: Testing Your Clustered Groupwise System

    3 Scroll down through the startup file looking for other active (not commented out) startup switches, then modify them as needed for the new instance of the agent. 4 Save the new startup file. 5 Continue with Testing Your Clustered GroupWise System.

  • Page 410: Knowing What To Expect In Mta And Poa Failover Situations

    This information appears on the MTA console, no matter which node in the cluster it is currently running on. 7 Click OK to save the MTA description. 8 Continue with Recording Cluster-Specific Information for a Post Office and Its POA. Recording Cluster-Specific Information for a Post Office and Its POA To permanently record important cluster-specific information for a post office: 1 In ConsoleOne, browse to and right-click the Post Office object, then click Properties.

  • Page 411: What's Next

    “Implementing WebAccess in a NetWare Cluster,” on page Connecting your clustered GroupWise system to other e-mail systems through GroupWise gateways. See Chapter 6, “Implementing GroupWise Gateways in a Novell Cluster,” on page 107. Monitoring the status of your clustered GroupWise system from your Web browser. See Chapter 7, “Monitoring a GroupWise System in a NetWare Cluster,”...
  • Page 412 412 GroupWise 7 Interoperability Guide...

  • Page 413: Implementing The Internet Agent In A Microsoft Cluster

    Implementing the Internet Agent in a Microsoft Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 41, “Planning GroupWise in a Microsoft Cluster,” on page 385 Chapter 42, “Setting Up a Domain and Post Office in a Microsoft Cluster,”...

  • Page 414: Planning The Internet Agent Resource Group

    Keep in mind the following cluster-specific details: When you specify the location for the domain directory on the Domain Worksheet, include the shared disk where you want the domain directory to be located. Do not concern yourself with the GroupWise agent information on the Domain Worksheet. You can stop with item 10.

  • Page 415: Preparing Your Firewall For The Internet Agent

    INTERNET AGENT CLUSTERING WORKSHEET Under Item 5: MTA Network Information, transfer the resource group IP address and cluster-unique port numbers from the Internet Agent section of the Network Address Worksheet to the Internet Agent Clustering Worksheet. Under Item 7: Internet Agent Network Information, transfer the resource group IP address (the same as for its MTA) and the cluster-unique Internet Agent port number from the Internet Agent section of the Network Address Worksheet to the Internet Agent Clustering Worksheet.

  • Page 416: Planning The Mta Installation

    “Deciding Where to Install the Agent Software” on page 393, which describes the issues in the context of planning MTA and POA installations. As with the MTA and POA, the Internet Agent and its MTA must be installed as Windows services. INTERNET AGENT CLUSTERING WORKSHEET Under Item 4: MTA Installation Location...

  • Page 417: Setting Up The Internet Agent Resource Group

    43.2.1 Setting Up the Internet Agent Resource Group 1 Create the Internet Agent resource group and agent services resources (Internet Agent Clustering Worksheet item 1), as planned in “Planning the Internet Agent Resource Group” on page 414. 2 To ensure successful short name resolution, add entries for the Internet Agent network name to support your preferred methods of short name resolution, as described in “Configuring Short Name Resolution”...
  • Page 418 3 If you plan to install the Internet Agent software to the shared disk of the Internet Agent resource group (Internet Agent Clustering Worksheet item 6), create the drive:\grpwise\gwia directory on the shared disk accessed in Step If you plan to install the Internet Agent software to each node in the cluster, create the c:\grpwise\gwia directory on the drive accessed in Step 4 Start the Internet Agent Installation program, following the steps provided in...
  • Page 419 “Verifying the Reference to the Network Name in Directory Paths” on page 419 “Verifying Post Office Links” on page 419 “Forcing Use of the Internet Agent Resource Group IP Address” on page 420 Accessing Internet Agent Object Properties ® 1 In ConsoleOne , browse to and select the Internet Agent domain in order to display its contents.

  • Page 420: Testing The Clustered Internet Agent

    Forcing Use of the Internet Agent Resource Group IP Address If you want the Internet Agent to send outgoing messages on its resource group IP address, rather than using the default the node IP address: 1 Click GroupWise > Network Address. 2 In the TCP/IP Address field, provide the resource group IP address (Internet Agent Clustering Worksheet item...

  • Page 421: Knowing What To Expect In An Internet Agent Failover Situation

    2 In the Description field of the Internet Agent domain Identification page, provide a cluster- specific description of the Internet Agent domain, including its resource group IP address and the cluster-unique port numbers used by its MTA. 3 Click OK to save the Internet Agent domain description. 4 Select the Internet Agent Domain object to display its contents.

  • Page 422: Internet Agent Clustering Worksheet

    43.4 Internet Agent Clustering Worksheet Item Explanation 1) Resource Group for Internet Specify the information for the Internet Agent resource group. Agent: For more information, see “Planning the Internet Agent Resource Group” on page 414. Network name: IP address: Physical disk: File share: MTA service resource: Internet Agent service resource:...

  • Page 423: Implementing Webaccess In A Microsoft Cluster

    Implementing WebAccess in a Microsoft Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 41, “Planning GroupWise in a Microsoft Cluster,” on page 385 Chapter 42, “Setting Up a Domain and Post Office in a Microsoft Cluster,” on page 401.

  • Page 424: Setting Up Your Web Server In The Microsoft Cluster

    Because the WebAccess Application is installed to a subdirectory of the Web server installation directory (directory\com\novell\webaccess), the WebAccess Application cannot be installed on a shared disk. Instead, you will install it to each node in the cluster where the Web server has been installed.

  • Page 425: Planning The Webaccess Resource Group

    WEBACCESS CLUSTERING WORKSHEET Under Item 1: Resource Group for WebAccess Agent, transfer the shared disk from the Domain Worksheet to the WebAccess Clustering Worksheet. Under Item 2: WebAccess Agent Domain Name, transfer the domain name and directory from the Domain Worksheet to the WebAccess Clustering Worksheet. 44.2.3 Planning the WebAccess Resource Group The WebAccess resource group is similar to the domain and post office resource groups you have already set up, as described in...

  • Page 426: Deciding Where To Install The Webaccess Agent And Its Mta

    44.2.5 Deciding Where to Install the WebAccess Agent and Its As with the MTA and the POA, you can choose to install the WebAccess Agent and its MTA to each node in the cluster or to the shared disk of the WebAccess resource group. For a discussion of these alternatives, see “Deciding Where to Install the Agent Software”...

  • Page 427: Setting Up Webaccess In A Cluster

    Under Item 16: Novell Root Directory, specify a directory on the Web server where you want to install the WebAccess Agent configuration file. the default is c:\novell 44.3 Setting Up WebAccess in a Cluster You should already have reviewed “Planning GroupWise in a Microsoft Cluster” on page 385 filled out the Section 44.5, “WebAccess Clustering Worksheet,”...

  • Page 428: Creating A Domain For The Webaccess Agent

    44.3.2 Creating a Domain for the WebAccess Agent The WebAccess Agent domain will be a secondary domain. To create it, follow the instructions in Section 42.3, “Creating a New Secondary Domain in a Cluster,” on page 404, taking your information from the WebAccess Clustering Worksheet, rather than the System Clustering Worksheet, then return to this point.
  • Page 429 On the Gateway Directory page, be sure to browse to the domain directory through the drive you mapped in Step 1 above. On the Execution Options page, be sure that Run WebAccess Agent as a Windows Service is selected. On the Start Applications page, deselect Start the GroupWise WebAccess Agent. 6 Repeat Step 4 Step...

  • Page 430: Testing Your Clustered Webaccess Installation

    6 Make sure you have completed all the WebAccess Application tasks described in “NetWare and Windows: Setting Up GroupWise WebAccess” in “Installing GroupWise WebAccess” in GroupWise 7 Installation Guide. 7 Copy the directory\docs\com directory from the server where you just installed the WebAccess Application to the document root directory of the Web server.

  • Page 431: Updating Groupwise Objects With Cluster-Specific Descriptions

    44.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions After installing WebAccess in your clustered GroupWise system, while the cluster-specific information is fresh in your mind, you should record that cluster-specific information as part of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the information recorded in the GroupWise objects if the configuration of your system changes.

  • Page 432: Knowing What To Expect In Webaccess Failover Situations

    WebAccess Application is currently running. However, the other nodes in the Web server possible owners list are not currently available for update. Therefore, you must manually copy the updated commgr.cfg file to the drive:\novell\webaccess subdirectory on each node in the Web serve possible owners list.

  • Page 433: Webaccess Clustering Worksheet

    44.5 WebAccess Clustering Worksheet Item Explanation 1) Resource Group for Specify the information for the WebAccess resource group. WebAccess Agent: For more information, see “Planning the WebAccess Resource Group” on page 425. Group name: Network name: IP address: Shared disk: Share name: MTA service resource: WebAccess Agent service...
  • Page 434 Item Explanation 7) Physical Web Servers: List the servers in the cluster where you are installing the Web server for use with WebAccess. For more information, see “Setting Up Your Web Server in the Microsoft Cluster” on page 424. 8) Web Server Record the secondary IP address for the Web server in the cluster.

  • Page 435: Implementing Groupwise Gateways In A Microsoft Cluster

    Implementing GroupWise Gateways in a Microsoft Cluster ® A significant system configuration difference between a GroupWise system in a clustering environment and a GroupWise system in a regular environment is that you need to create a separate domain to house each GroupWise gateway. The gateway domain should be created in its own resource group.
  • Page 436 436 GroupWise 7 Interoperability Guide...

  • Page 437: Monitoring A Groupwise System In A Microsoft Cluster

    Monitoring a GroupWise System in a Microsoft Cluster ® GroupWise Monitor is similar to WebAccess in that it relies on a Web server for communication with administrators’ Web browsers. Consequently, the setup procedure for GroupWise Monitor in a Microsoft cluster is similar to the setup procedure for WebAccess. If you have set up WebAccess in your clustered GroupWise system, you should already have the skills necessary to set up GroupWise Monitor as well.
  • Page 438 438 GroupWise 7 Interoperability Guide...

  • Page 439: Backing Up A Groupwise System In A Microsoft Cluster

    This means that GroupWise users cannot be logged into their mailboxes while backups are running. To find backup software that is compatible with GroupWise, see the Novell Partner Product Guide (http://www.novell.com/partnerguide). Backing Up a GroupWise System in a Microsoft Cluster...
  • Page 440 440 GroupWise 7 Interoperability Guide...

  • Page 441: Moving An Existing Groupwise 7 System Into A Microsoft Cluster

    Moving an Existing GroupWise 7 System into a Microsoft Cluster ® If you are adding the high availability benefits of a Microsoft cluster to a GroupWise 7 system that is already up and running, the first step is to set up the cluster and review Chapter 40, “Introduction to GroupWise 7 and Microsoft Clusters,”...
  • Page 442 Move GroupWise administration into the cluster as needed. Add other components to your clustered GroupWise system as needed, following the instructions in: Chapter 43, “Implementing the Internet Agent in a Microsoft Cluster,” on page 413 Chapter 44, “Implementing WebAccess in a Microsoft Cluster,” on page 423.

  • Page 443: Implementing Messenger In A Microsoft Cluster

    Implementing Messenger in a Microsoft Cluster ® ® Novell Messenger does not require the existence of a GroupWise system in your Microsoft cluster, but presumably one has already been set up as described in Chapter 41, “Planning GroupWise in a Microsoft Cluster,” on page 385 Chapter 42, “Setting Up a Domain and Post...

  • Page 444: Deciding Where To Install The Messenger Agent Software

    Messenger Installation program. Shared disk If you create a drive:\novell\nm directory on a shared disk, the Messenger agent software and startup files fail over and fail back along with supporting files such as the Messenger archive. IMPORTANT: You must install to a shared disk if you do not want a separate Messenger archive to be created on each node where the Archive Agent runs.

  • Page 445: Planning The Messenger Agent Installation

    If you are installing the Messenger agents to each node in the cluster, use c:\novell\nm. If you are installing the Messenger agents to a shared disk, use drive:\novell\nm where drive is the shared disk from Item 4: Resource Group for Messenger Agents on the Messenger Clustering Worksheet.

  • Page 446: Setting Up Your Messenger System In A Cluster

    3), copy the Messenger agent startup files to the planned location on the shared disk, then delete them from the c:\novell\nm\ma and c:\novell\nm\aa directories on each node to avoid future confusion. 3 Make each node in the cluster active to make sure that the Messenger agents start successfully on each node.

  • Page 447: Messenger Clustering Worksheet

    Installation Guide. 5 Install the Windows Messenger agents, keeping in mind the following cluster-specific details: Use the Novell Messenger System Worksheet that you filled out in “Planning the Messenger Agent Installation” on page 122 to fill in the fields during the Messenger installation process.
  • Page 448 Item Explanation 3) Installation Location for Messenger Mark the location where you will install the Messenger agent Agents: software. For more information, see “Deciding Where to Install the Each node in the cluster Messenger Agent Software” on page 444. Consolidate startup files? Shared disk 4) Resource Group for Messenger If you plan to install the Messenger agent software to a shared...

  • Page 449: Part Vii Non-Groupwise Clients

    Non-GroupWise Clients V I I If your users already have a common POP, IMAP, or SOAP e-mail client that comes with Linux or ® Windows, they can continue to use it to access their GroupWise mailboxes. Users of non- ® GroupWise e-mail clients retain the feature sets of their familiar e-mail clients, but many GroupWise features are not available to such users because they are not offered in POP, IMAP, and...
  • Page 450 450 GroupWise 7 Interoperability Guide...

  • Page 451: Outlook Express

    Outlook Express ® The GroupWise Internet Agent is required in order for users to access their mailboxes using non- GroupWise clients. If you have not already installed the Internet Agent, follow the instructions in the GroupWise 7 Installation Guide. In order for users to access their GroupWise mailboxes from a third-party e-mail client, they must configure their e-mail clients to access their GroupWise accounts.
  • Page 452 8 Select My Server Requires Authentication, then click OK. The default setting for server authentication is Use Same Settings as My Incoming Mail Server, so you do not need to change any settings. 9 To access your GroupWise mailbox in Outlook Express, click Tools > Send and Receive. 10 Click the IP address or hostname of your mail server.

  • Page 453: Microsoft Outlook

    Guide, available on the GroupWise 7 Documentation Web site (http:// www.novell.com/documentation/gw7). If your users have been using the Microsoft Outlook e-mail client that comes with Microsoft Office, they can continue to use POP or IMAP in it to access their GroupWise mailboxes.
  • Page 454 For additional functionality, you can install the GroupWise Connector for Microsoft Outlook, available along with the GroupWise client from the Novell Product Downloads site (http:// download.novell.com). For more information, see the GroupWise Connector for Microsoft Outlook Quick Start on the GroupWise 7 Documentation Web site (http://www.novell.com/documentation/...

  • Page 455: Evolution

    ® ® If you have Evolution 2.4 installed, you can access accounts on Novell GroupWise Section 52.1, “GroupWise Features Available in Evolution,” on page 455 Section 52.2, “Configuring Evolution,” on page 456 52.1 GroupWise Features Available in Evolution...

  • Page 456: Configuring Evolution

    3 On the Identity page, type your e-mail address, then click Forward. 4 On the Receiving Mail page, select Novell GroupWise as your server type. 5 Type the name of your mail server, your user name, and select whether to use SSL.
  • Page 457 6 Click Forward. 7 On the Receive Options page, select if you want Evolution to automatically check for new mail. If you select this option, you need to specify how often Evolution should check for new messages. 8 Select if you want to check for new messages in all folders. 9 Select if you want to apply filters to new messages in the Inbox on the server.
  • Page 458 458 GroupWise 7 Interoperability Guide...

  • Page 459: Part Viii Mobile Devices

    VIII Mobile Devices V I I I ® If you own a mobile device, you can synchronize it with GroupWise . GroupWise has provided GroupWise Mobile Server for synchronizing several of the most common device. In addition, GroupWise has teamed up with BlackBerry* for synchronizing of BlackBerry devices. Chapter 53, “GroupWise Mobile Server, Powered by Intellisync,”...
  • Page 460 460 GroupWise 7 Interoperability Guide...

  • Page 461: Groupwise Mobile Server, Powered By Intellisync

    Using GroupWise Mobile Server, you can synchronize Personal Information Manager (PIM) and ® e-mail data from Novell GroupWise to Windows* CE, Windows Mobile*-based Smartphones, Symbian* OS, Palm OS* handheld devices, and SyncML* devices. The GroupWise Mobile Server includes the following modules from Intellisync*:...
  • Page 462 462 GroupWise 7 Interoperability Guide...

  • Page 463: Blackberry Enterprise Server

    Solution. It is designed to provide IT departments with simplified management and centralized control of wireless devices in a secure, scalable and flexible architecture. BlackBerry Enterprise Server v.4.1 for Novell GroupWise includes several new features to enhance end user productivity and back-end administration. These features include Novell GroupWise Messenger support, enhanced support for PowerPoint and Web Doc attachments, group- and role-based administration, localized data pass-through and SMS/PIN/call log auditing.
  • Page 464 464 GroupWise 7 Interoperability Guide...

  • Page 465: Groupwise Pda Connect

    7 Follow the on-screen instructions provided in the GroupWise PDA Connect Installation to install the software. 55.3 Third-Party Partners Novell partners with several third-party companies for synchronization of mobile devices. A complete list of the third-party partners can be found in the Novell Partner Product Guide (http:// www.novell.com/partnerguide).
  • Page 466 466 GroupWise 7 Interoperability Guide...

  • Page 467: Part Ix Documentation Updates

    This section lists updates to the Interoperability Guide that have been made since the initial release ® ® of Novell GroupWise 7. The information helps you to keep current on documentation updates and, in some cases, software updates (such as a Support Pack release).
  • Page 468 468 GroupWise 7 Interoperability Guide...
  • Page 469 June 25, 2008 Location Change Novell Teaming and Conferencing “Novell Teaming and Updated the section to correspond with Teaming and Conferencing 1.0 Conferencing” on page 243 Support Pack 3. Section 25.1.3, “Adding the Changed X-Authentication to X-Authorization. New Web Server...
  • Page 470 470 GroupWise 7 Interoperability Guide...
  • Page 471 March 14, 2008 (GroupWise 7 SP3) Location Change Novell Cluster Services on NetWare Section 5.1, “Understanding Emphasized that if you have not clustered your Web server, you can install the WebAccess the WebAccess Application on a Web server that is outside the cluster Components,”...
  • Page 472 472 GroupWise 7 Interoperability Guide...
  • Page 473 October 24, 2007 Location Change Novell Teaming and Conferencing ® “Novell Teaming and Added a new section about integrating eDirectory and GroupWise with ® Conferencing” on page 243 the Novell Teaming and Novell Teaming + Conferencing products. October 24, 2007...
  • Page 474 474 GroupWise 7 Interoperability Guide...
  • Page 475 April 16, 2007 (GroupWise 7 SP 2) Location Change Novell Cluster Services on NetWare “Copying LDAP and Improved the instructions for handling LDAP and QuickFinder files after QuickFinder Files to the installing the Messenger agents in a cluster. Messenger Volume” on...
  • Page 476 476 GroupWise 7 Interoperability Guide...

  • Page 477: E September 29, 2006

    September 29, 2006 Location Change Novell Cluster Services on NetWare Section 3.5.2, “Editing Mentioned use of the /user and /password startup switches for the MTA. Clustered Agent Startup Files,” on page 52 September 29, 2006...
  • Page 478 478 GroupWise 7 Interoperability Guide...

  • Page 479: F August 2, 2006

    August 2, 2006 Location Change Novell Cluster Services on Linux Section 14.4.3, “Configuring Added new examples of load and unload scripts for use with Linux GroupWise Cluster traditional file system disk partitions. Resources to Load and Unload the Agents,” on page 152 “Configuring the Internet...
  • Page 480 480 GroupWise 7 Interoperability Guide...
  • Page 481 June 15, 2006 (GroupWise 7 SP1) Location Change Novell Cluster Services on NetWare Section 2.8.4, “Deciding Strongly recommended running the agents in protected memory, with each Whether to Run the Agents agent in a separate memory space. in Protected Memory,” on page 36 Section 4.1.7, “Deciding...
  • Page 482 Location Change Section 14.1, “Setting Up a Explained that you should copy all agent software into the software New GroupWise System in distribution directory, and that you should exit the GroupWise Installation a Linux Cluster,” on program without installing the agent software from the CD. page 143 “Running the GroupWise Explained that you install the agent software from the software distribution...
  • Page 483 Location Change Section 22.1.4, Explained the mount point for shared storage. “Determining Cluster Resource Information for the Messenger Agents,” on page 230 “Running the Messenger Explained the new mount point prompt when installing the Messenger Installation Program on the agents in a cluster. Preferred Node”...
  • Page 484 484 GroupWise 7 Interoperability Guide...

  • Page 485: H November 30, 2005

    ® on page 277 GroupWise WebAccess and provided a link to the exteNd documentation that explains how to configure exteNd for use with GroupWise. Entire Guide Page design reformatted to comply with revised Novell documentation standards. November 30, 2005...

This manual is also suitable for:

Groupwise 7

Table of Contents