Installation Guide GroupWise 2014 November 2014 www.novell.com/documentation

Transcription

www.novell.com/documentation
Installation Guide
GroupWise 2014
November 2014
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically
disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any
person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right
to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of
such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade
laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or
classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S.
export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use
deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade
Services web page (http://www.novell.com/company/legal/exports/) for more information on exporting Novell software.
Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 1993-2013 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on
a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc.
1800 South Novell Place
Provo, UT 84606
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see the
Novell Documentation website (http://www.novell.com/documentation/).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Contents
About This Guide
11
Part I GroupWise Product Overview
13
1 GroupWise Features and Benefits
15
1.1
1.2
1.3
1.4
1.5
1.6
Essential Communication and Collaboration Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Available Anytime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Accessible Anywhere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Always Secure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Competitive Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Evaluation Version Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 GroupWise Components
19
3 GroupWise System Architecture
21
3.1
3.2
3.3
3.4
3.5
Agent Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Administration Service Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
WebAccess Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Calendar Publishing Host Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Monitor Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Part II GroupWise System Requirements
25
4 GroupWise Administration Requirements
27
4.1
4.2
4.3
4.4
4.5
4.6
Hardware and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Directory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Web Browser Requirements Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Internet Agent Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.1
GroupWise Version Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5.2
Internet Connectivity Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Sample Agent Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.6.1
Sample POA Memory Requirements Based on Post Office Size . . . . . . . . . . . . . . . . . . . . 30
4.6.2
Sample Memory Requirements for Other GroupWise Agents and Applications . . . . . . . . . 31
5 GroupWise User Requirements
5.1
5.2
5.3
33
GroupWise Client User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
GroupWise WebAccess User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
GroupWise WebAccess Mobile User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6 Supported Environments
6.1
35
IPv6 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Contents
3
6.2
6.3
6.4
6.5
6.6
6.7
6.8
Clustering Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Xen Virtualization Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
VMware Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Hyper-V / Cloud Server Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Citrix Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Domain Services for Windows Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
File System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Part III GroupWise System Creation
39
7 GroupWise System Overview
41
7.1
7.2
7.3
7.4
Simple GroupWise System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Typical GroupWise System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
GroupWise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
8 Planning Your GroupWise System
8.1
8.2
8.3
8.4
8.5
Planning GroupWise System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1.1
GroupWise System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.1.2
GroupWise Internet Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Planning a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.2.1
Domain Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.2.2
Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.2.3
Domain Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.2.4
Domain Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.2.5
Domain Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.2.6
Domain Link (Secondary Domain Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.2.7
Agents for the Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.2.8
Administrator Access for Domain Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Planning a Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.3.1
Post Office Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.3.2
Post Office Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.3.3
Post Office Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.3.4
Post Office Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.3.5
Post Office Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.3.6
Agents in the Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.3.7
Administrator Access for Post Office Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Planning Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.4.1
Manually Created Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.4.2
Imported Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
GroupWise System Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.5.1
Simple GroupWise System Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.5.2
Primary Domain Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.5.3
Secondary Domain Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.5.4
Post Office Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9 Installing the GroupWise Server Software
9.1
9.2
4
45
63
Linux: Installing the GroupWise Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
9.1.1
Preparing the Linux Server for Your GroupWise System . . . . . . . . . . . . . . . . . . . . . . . . . . 63
9.1.2
Running the Linux GroupWise Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Windows: Installing the GroupWise Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.2.1
Preparing the Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.2.2
Running the Windows GroupWise Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
GroupWise 2014 Installation Guide
10 Creating a Simple GroupWise System
69
11 Creating a Typical GroupWise System
73
11.1
11.2
11.3
11.4
11.5
Creating the Primary Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Adding a Secondary Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Adding a Post Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Handling an Installation Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Changing the Authentication Mode for the Installation Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
12 Adding Users to Your GroupWise System
12.1
12.2
12.3
81
Manually Adding Users to the Internal GroupWise Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Importing Users from an LDAP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
12.2.1 Providing LDAP Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
12.2.2 Importing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Testing the Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
13 Working with the GroupWise Administration Console
13.1
13.2
13.3
13.4
13.5
13.6
85
Accessing the Admin Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Making the Most of the System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Finding Objects in Object Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Finding Frequently Used Objects Quickly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Working with Objects and Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Using System Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
14 Working with the GroupWise Agents
14.1
14.2
14.3
91
Linux: Managing the GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
14.1.1 Manually Starting and Stopping the Linux GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . 92
14.1.2 Running the Linux GroupWise Agents as a Non-root User . . . . . . . . . . . . . . . . . . . . . . . . . 94
14.1.3 Automatically Restarting the Linux GroupWise Agents with the GroupWise High
Availability Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
14.1.4 Using the Linux GroupWise Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
14.1.5 Uninstalling the Linux GroupWise Agents and Applications . . . . . . . . . . . . . . . . . . . . . . . 103
Windows: Managing the GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
14.2.1 Manually Starting and Stopping the Windows GroupWise Agents . . . . . . . . . . . . . . . . . . 104
14.2.2 Using the Windows GroupWise Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
14.2.3 Uninstalling the Windows GroupWise Agents and Applications . . . . . . . . . . . . . . . . . . . . 106
Monitoring the Agents from Your Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
15 What’s Next
109
Part IV GroupWise Component Installation and Setup
111
16 Setting Up GroupWise WebAccess
113
16.1
16.2
GroupWise WebAccess Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
16.1.1 GroupWise WebAccess Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
16.1.2 GroupWise WebAccess Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
16.1.3 WebAccess Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
GroupWise WebAccess System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
16.2.1 Hardware and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
16.2.2 Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Contents
5
16.3
16.4
16.5
16.6
16.7
16.2.3 GroupWise Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
16.2.4 User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Planning GroupWise WebAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
16.3.1 Selecting the WebAccess Application Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
16.3.2 Gathering Web Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
16.3.3 Determining the WebAccess Application’s Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 119
16.3.4 Connecting the WebAccess Application with Supporting Agents . . . . . . . . . . . . . . . . . . . 119
Installing the GroupWise WebAccess Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
16.4.1 Linux: Installing the GroupWise WebAccess Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
16.4.2 Windows: Installing the GroupWise WebAccess Software . . . . . . . . . . . . . . . . . . . . . . . . 122
Testing GroupWise WebAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
16.5.1 Testing WebAccess on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
16.5.2 Testing WebAccess on a Tablet Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
16.5.3 Testing the WebAccess Basic Interface on a Mobile Device. . . . . . . . . . . . . . . . . . . . . . . 127
16.5.4 Assisting Users with Login Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
16.5.5 Monitoring the WebAccess Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
GroupWise WebAccess Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
17 Setting Up the GroupWise Calendar Publishing Host
17.1
17.2
17.3
17.4
17.5
17.6
17.7
17.8
6
131
GroupWise Calendar Publishing Host Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.1.1 GroupWise Calendar Publishing Host Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.1.2 GroupWise Calendar Publishing Host Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
17.1.3 GroupWise Calendar Publishing Host Security Requirements . . . . . . . . . . . . . . . . . . . . . 132
GroupWise Calendar Publishing Host System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
17.2.3 Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Planning a GroupWise Calendar Publishing Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
17.3.1 Selecting the Calendar Publishing Host Application Platform . . . . . . . . . . . . . . . . . . . . . . 136
17.3.2 Gathering Web Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
17.3.3 Choosing the Calendar Publishing Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
17.3.4 Determining the URL of the Calendar Publishing Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
17.3.5 Selecting a Calendar Publishing Host Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
17.3.6 Connecting the Calendar Publishing Host to a POA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
17.3.7 Designing Your Calendar Browse List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
17.3.8 Selecting Calendar Publishing Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Installing the GroupWise Calendar Publishing Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
17.4.1 Linux: Installing the Calendar Publishing Host Software . . . . . . . . . . . . . . . . . . . . . . . . . . 140
17.4.2 Windows: Installing the Calendar Publishing Host Software . . . . . . . . . . . . . . . . . . . . . . . 142
Configuring GroupWise to Support the Calendar Publishing Host. . . . . . . . . . . . . . . . . . . . . . . . . . 145
17.5.1 Configuring the Calendar Publishing Host in the GroupWise Admin Console. . . . . . . . . . 146
17.5.2 Enabling Calendar Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
17.5.3 Configuring a POA for Calendar Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.5.4 Setting Up Calendar Publishing Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
17.5.5 Using the Published Calendar Browse List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Testing GroupWise Calendar Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
17.6.1 Publishing a Personal Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
17.6.2 Displaying the Browse List of Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
17.6.3 Publishing Free/Busy Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
GroupWise Calendar Publishing Host Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
17.8.1 Calendar Publishing Host Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
17.8.2 Calendar Publishing Host Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
18 Setting Up GroupWise Monitor
18.1
18.2
18.3
18.4
18.5
18.6
157
GroupWise Monitor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
18.1.1 GroupWise Monitor Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
18.1.2 GroupWise Monitor Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
18.1.3 One Monitor Server versus Two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
18.1.4 Monitor Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
18.1.5 Monitor and the GroupWise High Availability Service on Linux . . . . . . . . . . . . . . . . . . . . . 160
GroupWise Monitor System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
18.2.3 Web Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Planning GroupWise Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
18.3.1 Deciding Where to Install the GroupWise Monitor Components . . . . . . . . . . . . . . . . . . . . 162
18.3.2 Determining the Monitor Agent’s Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
18.3.3 Determining the Monitor Application’s Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Installing the GroupWise Monitor Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
18.4.1 Linux: Installing the GroupWise Monitor Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
18.4.2 Windows: Installing the GroupWise Monitor Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Testing GroupWise Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
18.5.1 Using the Monitor Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
18.5.2 Using the Monitor Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
18.5.3 Using the Windows Monitor Agent Server Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
GroupWise Monitor Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
18.6.1 GroupWise Monitor Agent Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
18.6.2 GroupWise Monitor Application Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
19 Installing the GroupWise Client
19.1
19.2
19.3
19.4
19.5
177
GroupWise Client Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
GroupWise Client Workstation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Installing the GroupWise Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
19.3.1 Installing the GroupWise Client from the Windows GroupWise 2014 Software Image . . . 178
19.3.2 Installing the GroupWise Client from the Linux GroupWise 2014 Software Image . . . . . . 180
19.3.3 Implementing System-Wide GroupWise Client Rollouts . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Starting the Groupwise Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
20 Using Other Novell Products with GroupWise
20.1
20.2
20.3
183
Using the GroupWise Mobility Service to Synchronize GroupWise Data to Mobile Devices . . . . . . 183
Using Novell Messenger to Provide Secure Instant Messaging for GroupWise Users . . . . . . . . . . 183
Using Novell Vibe to Provide Team Workspaces for GroupWise Users . . . . . . . . . . . . . . . . . . . . . 184
Part V GroupWise System Upgrade
185
21 What’s New in GroupWise 2014
187
21.1
21.2
21.3
GroupWise Administration Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
GroupWise Agent Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
21.2.1 Post Office Agent Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
21.2.2 Message Transfer Agent Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
21.2.3 Internet Agent Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
21.2.4 Document Viewer Agent Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
21.2.5 Monitor Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
GroupWise User Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
21.3.1 GroupWise Client Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Contents
7
21.4
21.3.2 GroupWise WebAccess Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
21.3.3 GroupWise WebAccess Mobile Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
21.3.4 Calendar Publishing Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
GroupWise What’s New and Tutorial Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
22 Understanding the Upgrade Process
22.1
22.2
22.3
22.4
22.5
22.6
22.7
22.8
22.9
22.10
Domain and Post Office Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Agent Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Monitor Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
WebAccess Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Calendar Publishing Host Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
GroupWise Client Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Obsolete eDirectory Schema Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Obsolete Software Distribution Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Obsolete GroupWise Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
NetWare Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
23 Preparing Your Existing GroupWise System for the Upgrade
199
24 Installing the GroupWise 2014 Software
201
24.1
24.2
Linux: Installing the GroupWise 2014 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Windows: Installing the GroupWise 2014 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
25 Upgrading the Primary Domain Server
205
26 Upgrading a Secondary Domain Server
211
27 Upgrading a Post Office Server
219
28 Upgrading GroupWise Agents and Applications
225
28.1
28.2
28.3
28.4
28.5
8
193
Upgrading the Document Viewer Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Upgrading GroupWise WebAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
28.2.1 Preparing to Upgrade the WebAccess Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
28.2.2 Installing the GroupWise 2014 WebAccess Application . . . . . . . . . . . . . . . . . . . . . . . . . . 226
28.2.3 Clearing User Browser Caches to Display GroupWise 2014 WebAccess Correctly . . . . . 227
Upgrading the Calendar Publishing Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
28.3.1 Installing the GroupWise 2014 Calendar Publishing Host Application . . . . . . . . . . . . . . . 227
28.3.2 Clearing User Browser Caches to Display Published Calendars Correctly . . . . . . . . . . . . 228
Upgrading GroupWise Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
28.4.1 Preparing to Upgrade GroupWise Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
28.4.2 Installing the Monitor Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
28.4.3 Clearing Browser Caches to Display GroupWise 2014 Monitor Correctly . . . . . . . . . . . . . 229
28.4.4 Reconfiguring the GroupWise High Availability Service . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Implementing SSL Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
29 Upgrading Users’ GroupWise Client Software
231
30 Transitioning from ConsoleOne
233
31 Upgrading the GroupWise/Exchange Coexistence Solution
235
Part VI Appendixes
237
A GroupWise Version Compatibility
239
A.1
A.2
GroupWise 2014 with Earlier GroupWise Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
A.1.1
Compatibility with GroupWise 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
A.1.2
Compatibility with GroupWise 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
GroupWise 2014 in a Cross-Platform Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
A.2.1
GroupWise 2014 Administrative Components and Databases . . . . . . . . . . . . . . . . . . . . . 242
A.2.2
GroupWise 2014 Agents on Linux and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
B Attributes, Operators, and Values for Object Filters
B.1
B.2
B.3
B.4
B.5
B.6
245
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Logical Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Grouping Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Wildcard Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Literal Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Date Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
C Invalid Characters in GroupWise Object Names and Email Addresses
C.1
C.2
249
Invalid Characters in GroupWise Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Invalid Characters in Internet Email Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
D Cross-Platform Connections
D.1
D.2
D.3
D.4
251
Setting up Samba on OES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
D.1.1
Configuring NetWare Core Protocol (NCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
D.1.2
Installing Samba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
D.1.3
Logging In to iManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
D.1.4
Creating a User to Manage the Samba Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
D.1.5
Configuring the eDirectory Universal Password for Samba. . . . . . . . . . . . . . . . . . . . . . . . 253
D.1.6
Setting the eDirectory Universal Password for the Samba Administrator User . . . . . . . . . 253
D.1.7
Creating a Samba Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
D.1.8
Setting the eDirectory Rights for the Samba Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
D.1.9
Testing Samba on the OES Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Mapping a Drive to a Samba Share on an OES Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Setting Up Samba on SLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
D.3.1
Preparing Your Firewall to Allow Samba Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
D.3.2
Configuring the Samba Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
D.3.3
Configuring the Samba Web Administration Tool (SWAT) . . . . . . . . . . . . . . . . . . . . . . . . 255
D.3.4
Accessing SWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
D.3.5
Setting the Samba User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
D.3.6
Creating a Samba Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Mapping a Drive to a Samba Share on a SLES Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Contents
9
E Third-Party Materials
E.1
E.2
E.3
E.4
E.5
E.6
E.7
E.8
E.9
E.10
E.11
E.12
E.13
E.14
Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
BLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
GD Graphics Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
getopt.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
iCal4j - License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
ICU License - ICU 1.8.1 and Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
NET-SNMP Open Source Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
E.8.1
---- Part 1: CMU/UCD copyright notice: (BSD like) ----- . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
E.8.2
---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) ----- . . . . . . . . . 264
E.8.3
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) ----- . . . . . . . . . . . . . . . . . 264
E.8.4
---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) ----- . . . . . . . . . . . . . . . . . . . . 265
ODMA 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
OpenLDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Oracle Outside In Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Python 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Yahoo! UI Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
F Documentation Updates
F.1
10
259
271
July 28, 2014 (GroupWise 2014 SP1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
About This Guide
This Novell GroupWise 2014 Installation Guide helps you install a new GroupWise system or upgrade
an existing GroupWise 8 or 2012 system to GroupWise 2014.
 Part I, “GroupWise Product Overview,” on page 13
 Chapter 1, “GroupWise Features and Benefits,” on page 15
 Chapter 2, “GroupWise Components,” on page 19
 Chapter 3, “GroupWise System Architecture,” on page 21
 Part II, “GroupWise System Requirements,” on page 25
 Chapter 4, “GroupWise Administration Requirements,” on page 27
 Chapter 5, “GroupWise User Requirements,” on page 33
 Chapter 6, “Supported Environments,” on page 35
 Part III, “GroupWise System Creation,” on page 39
 Chapter 7, “GroupWise System Overview,” on page 41
 Chapter 8, “Planning Your GroupWise System,” on page 45
 Chapter 9, “Installing the GroupWise Server Software,” on page 63
 Chapter 10, “Creating a Simple GroupWise System,” on page 69
 Chapter 11, “Creating a Typical GroupWise System,” on page 73
 Chapter 12, “Adding Users to Your GroupWise System,” on page 81
 Chapter 13, “Working with the GroupWise Administration Console,” on page 85
 Chapter 14, “Working with the GroupWise Agents,” on page 91
 Chapter 15, “What’s Next,” on page 109
 Part IV, “GroupWise Component Installation and Setup,” on page 111
 Chapter 16, “Setting Up GroupWise WebAccess,” on page 113
 Chapter 17, “Setting Up the GroupWise Calendar Publishing Host,” on page 131
 Chapter 18, “Setting Up GroupWise Monitor,” on page 157
 Chapter 19, “Installing the GroupWise Client,” on page 177
 Chapter 20, “Using Other Novell Products with GroupWise,” on page 183
 Part V, “GroupWise System Upgrade,” on page 185
 Chapter 21, “What’s New in GroupWise 2014,” on page 187
 Chapter 22, “Understanding the Upgrade Process,” on page 193
 Chapter 23, “Preparing Your Existing GroupWise System for the Upgrade,” on page 199
 Chapter 24, “Installing the GroupWise 2014 Software,” on page 201
 Chapter 25, “Upgrading the Primary Domain Server,” on page 205
 Chapter 26, “Upgrading a Secondary Domain Server,” on page 211
 Chapter 27, “Upgrading a Post Office Server,” on page 219
About This Guide
11
 Chapter 28, “Upgrading GroupWise Agents and Applications,” on page 225
 Chapter 29, “Upgrading Users’ GroupWise Client Software,” on page 231
 Part VI, “Appendixes,” on page 237
 Appendix A, “GroupWise Version Compatibility,” on page 239
 Appendix B, “Attributes, Operators, and Values for Object Filters,” on page 245
 Appendix C, “Invalid Characters in GroupWise Object Names and Email Addresses,” on
page 249
 Appendix D, “Cross-Platform Connections,” on page 251
 Appendix E, “Third-Party Materials,” on page 259
The following resources provide additional information about using GroupWise 2014:
 Novell Support and Knowledgebase (http://www.novell.com/support/)
To search the GroupWise documentation from the Novell Support website, click Advanced
Search, select Documentation in the Search In drop-down list, select GroupWise in the Products
drop-down list, type the search string, then click Search.
 GroupWise Support Forums (https://forums.novell.com/forumdisplay.php/356-GroupWise)
 GroupWise Support Community (http://www.novell.com/support/kb/
product.php?id=SG_XGROUPWISE_1_2)
 GroupWise Cool Solutions (https://www.novell.com/communities/coolsolutions/category/
groupwise/)
Audience
This guide is intended for network administrators who install and administer GroupWise.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comment feature at the bottom of each page of the
online documentation.
Additional Documentation
For additional GroupWise documentation, see the Novell GroupWise 2014 Documentation website
(http://www.novell.com/documentation/groupwise2014/).
12
I
GroupWise Product Overview
I
Novell GroupWise is an enterprise collaboration system that provides the following secure services:
 Email
 Calendaring
 Scheduling
 Task management
 Contact management
 Document management
 Additional productivity tools
Companion products provide additional capabilities:
 GroupWise Mobility Service: Synchronization of GroupWise data to mobile devices
 Novell Messenger: Secure instant messaging
 Novell Vibe: Team workspaces, document management, and other collaboration tools
GroupWise 2014 can be used in a variety of environments:
 Your Windows Desktop: Windows XP, 7, and 8
 Web Browsers: Mozilla Firefox, Google Chrome, and Microsoft Internet Explorer
 Tablets: Apple, Android, Kindle, and RIM
 Mobile Devices: Apple, Android, BlackBerry, and Windows
The following sections include more details about the benefits that GroupWise provides and the
steps you need to perform to set up your GroupWise system to best meet your users’ needs.
 Chapter 1, “GroupWise Features and Benefits,” on page 15
 Chapter 2, “GroupWise Components,” on page 19
 Chapter 3, “GroupWise System Architecture,” on page 21
GroupWise Product Overview
13
14
1
GroupWise Features and Benefits
1
GroupWise provides communication and collaboration services that are secure, highly available, and
easily accessible:
 Section 1.1, “Essential Communication and Collaboration Services,” on page 15
 Section 1.2, “Available Anytime,” on page 16
 Section 1.3, “Accessible Anywhere,” on page 16
 Section 1.4, “Always Secure,” on page 17
 Section 1.5, “Competitive Performance,” on page 17
 Section 1.6, “Evaluation Version Available,” on page 17
1.1
Essential Communication and Collaboration Services
GroupWise provides a variety of tools to enable users to work together and to work smarter:
 Messaging: Send and receive mail messages, phone messages, and reminder notes. A mail
message is for general correspondence. A phone message is for those who take phone messages
for others. A reminder note includes a start date and, when accepted by the recipient, is posted
to the recipient’s Calendar.
 Scheduling: Schedule both appointments and tasks. When you schedule an appointment, you
can search other users’ Calendars to find free times for the appointment. When you schedule a
task, you can assign a priority and due date to the task. If the recipient accepts an appointment
or task, it is automatically added to his or her Calendar.
 Calendaring: View and manage your appointments, tasks, and reminder notes in a Calendar
view. You can create multiple calendars. You can create multi-user calendars. You can also
publish calendars and free/busy status to the web so that non-GroupWise users can
conveniently schedule meetings with you.
 Task Management: Create and schedule tasks for others. Accept or decline the tasks you
receive, and track accepted tasks through to completion. You can turn any message into a task.
You can also organize, schedule, and monitor tasks in your Tasklist folder.
 Contact Management: Manage information for your contacts, groups, resources, and
organizations, including being able to view, update, delete, and add information to the contacts
in your personal address books and Contacts folders. In addition, you can view a history of
messages sent to and received from individual contacts, and compile notes on interactions with
contacts.
 Document Management: Store documents in GroupWise libraries. In a library, documents, are
compressed to save disk space and encrypted to maintain security. With document
management, you can check in, check out, share, and create multiple versions of documents.
 Mobile Device Synchronization: Receive and respond to GroupWise messages, appointments,
tasks, and notes on your mobile device. You can also send new items of all types and manage
contacts on your mobile device.
15
 Instant Messaging: Communicate in real time with other GroupWise users through Novell
Messenger. Messenger lets you know when other users are online, busy, or away from their
desks and displays this status in the GroupWise client. Messenger also allows you to save
conversations.
 Teaming: Collaborate on a Novell Vibe website where personal, team, and global workspaces
can include discussion folders, shared calendars, shared documents, blogs, wikis, surveys, and
more. Powerful search capabilities make finding information quick and easy. GroupWise
includes integration with Vibe, so that you can access a Vibe site from the GroupWise client.
1.2
Available Anytime
GroupWise ensures that your essential communication tools are always available:
 Caching: The GroupWise client includes a Caching mode that allows you to cache GroupWise
information to your local drive and continue to work even when you are not logged in to your
Online mailbox.
 LDAP Pooling: If you are using LDAP authentication for GroupWise mailbox authentication,
LDAP pooling ensures that there is always an LDAP server through which authentication can be
performed.
 Clustering: To ensure that GroupWise data is always available and GroupWise components are
always running, you can install GroupWise in a cluster on Linux or Windows.
1.3
Accessible Anywhere
GroupWise lets you communicate and collaborate with other people by using the device that is most
convenient:
 Personal Computers: To access your GroupWise mailbox with the most robust functionality,
you can run the GroupWise client on any workstation that uses Windows XP, 7, or 8.
 Web Browsers: When you are away from your office, or when you prefer a platform other than
Windows, you can access your GroupWise mailbox from a variety of desktop web browsers by
using GroupWise WebAccess.
 Tablet Computers: For those who prefer a more mobile computer, you can access your
GroupWise mailbox from a tablet computer by using GroupWise WebAccess Mobile.
 Mobile Devices: If you want to access email messages, calendar items, tasks, and so on from a
handheld mobile device such as your cell phone, you have several options:
 GroupWise Mobility Service: The GroupWise Mobility Service, available free of charge to
GroupWise customers with maintenance contracts, synchronizes GroupWise data to most
popular mobile devices.
 BlackBerry Enterprise Server for GroupWise: This solution from Research in Motion
provides synchronization of GroupWise data for BlackBerry users with devices that are
older than the BlackBerry Z10. Newer BlackBerry devices are fully supported by the
GroupWise Mobility Service.
 GroupWise WebAccess Basic Template: GroupWise WebAccess includes a basic template
customized for use on the small display available on a typical mobile device.
NOTE: GroupWise WebAccess Mobile is intended for use on tablets, not on smaller mobile
devices such as cell phones.
16
 Other Email Clients: GroupWise enables you to access your mailbox with any POP3, IMAP4, or
SOAP email client.
1.4
Always Secure
GroupWise provides extensive security measures to protect your information:
 Native GroupWise Encryption: To protect your information as it is stored in the various
GroupWise databases and moved across the network, GroupWise automatically encrypts the
information. Each piece of information is encrypted differently through the use of randomly
generated encryption keys.
 Open Security Standards: To further ensure that your information is secure while moving
across your internal network and across the Internet, GroupWise supports open security
standards such as Secure Sockets Layer (SSL), Secure Multipurpose Internet Mail Extension (S/
MIME), Public Key Infrastructure (PKI), and Transport Layer Security (TLS).
 Spam Protection: To protect you from seeing unwanted messages, the GroupWise client
includes a Junk Mail Handling feature that lets you control unwanted Internet email messages.
In addition, you can configure the GroupWise Internet Agent (GWIA) to reject messages from
known open relay hosts and spam hosts. GroupWise also works with partner products that
provide additional anti-spam solutions.
 Virus Protection: GroupWise works with partner products to provide solutions that detect and
eliminate viruses.
For information about additional security solutions available for GroupWise through GroupWise
partners, see the Novell Partner Product Guide (http://www.novell.com/partnerguide/).
1.5
Competitive Performance
GroupWise functionality compares very favorably with popular email solutions:
 Novell GroupWise and Microsoft Exchange/Outlook (http://www.novell.com/products/
groupwise/features/groupwise-vs-outlook.html)
 Novell GroupWise and Google Gmail (http://www.novell.com/products/groupwise/features/
groupwise-vs-gmail.html)
1.6
Evaluation Version Available
An evaluation version of GroupWise is available on the Novell Downloads website (http://
download.novell.com). With the evaluation version of GroupWise, you can create a test GroupWise
system that includes any number of domains, post offices, and users. The evaluation version does not
expire. However, the evaluation software cannot legally be installed and run in a production
environment.
17
18
2
GroupWise Components
2
GroupWise includes multiple components that you need to install to realize the full benefits of
GroupWise. However, some components might not be necessary, depending on your needs. The
following table outlines the components, what they provide, and where to find instructions for
installing them.
Component
What it does
Go to
GroupWise Server:
Required for any GroupWise system.
These components must be installed
before any other components.
Chapter 10, “Creating a Simple
GroupWise System,” on page 69
 Administration Service
 Message Transfer Agent
Chapter 11, “Creating a Typical
GroupWise System,” on page 73
 Post Office Agent
 Internet Agent
 Document Viewer Agent
WebAccess
WebAccess Mobile
Provides access to mailboxes through Chapter 16, “Setting Up GroupWise
desktop web browsers, tablet
WebAccess,” on page 113
computers, and mobile devices.
Calendar Publishing Host
Provides web-based public access to
GroupWise calendars and free/busy
availability to Internet users.
Chapter 17, “Setting Up the
GroupWise Calendar Publishing
Host,” on page 131
Monitor
Provides administrative monitoring of
the GroupWise agents.
Chapter 18, “Setting Up GroupWise
Monitor,” on page 157
GroupWise Client
Provides access to mailboxes from
Chapter 19, “Installing the GroupWise
the Windows desktop; can be easily
Client,” on page 177
rolled out to all GroupWise users on a
convenient schedule.
In addition to the sections referenced in the above table, this Installation Guide includes the following
supplemental sections:
 Section 20.1, “Using the GroupWise Mobility Service to Synchronize GroupWise Data to Mobile
Devices,” on page 183
 Section 20.2, “Using Novell Messenger to Provide Secure Instant Messaging for GroupWise
Users,” on page 183
 Section 20.3, “Using Novell Vibe to Provide Team Workspaces for GroupWise Users,” on
page 184
The information in these sections is provided as a reference for installing additional products after
you have created your GroupWise system.
GroupWise Components
19
20
3
GroupWise System Architecture
3
Your GroupWise system consists of multiple components. The better you understand each
component, the more effectively you can manage your GroupWise system.
 Section 3.1, “Agent Architecture,” on page 21
 Section 3.2, “Administration Service Architecture,” on page 22
 Section 3.3, “WebAccess Architecture,” on page 23
 Section 3.4, “Calendar Publishing Host Architecture,” on page 23
 Section 3.5, “Monitor Architecture,” on page 24
3.1
Agent Architecture
The GroupWise agents move email throughout your GroupWise system, as well as to and from the
Internet.
GroupWise
System
Primary
Domain
Post
Office
Message
Transfer
Agent
Post
Office
Agents
Post
Office
Agents
Post
Office
GroupWise Clients
GroupWise Clients
Secondary
Domain
Message
Transfer
Agent
Post
Office
GroupWise Clients
Post
Office
GroupWise Clients
The Post Office Agent (POA) runs for each post office. The POA delivers email to users’ mailboxes.
The Message Transfer Agent (MTA) runs for each domain. The MTA transfers email between post
offices and other domains.
21
The Internet Agent (GWIA) runs for at least one domain in your GroupWise system. The GWIA
communicates with SMTP hosts across the Internet, sending and receiving email for users who are
not part of your GroupWise system.
Internet
Agent
Internet
Message
Transfer
Agent
Domain
Document
Viewer
Agent
Post
Office
Agents
Post
Office
GroupWise Clients
Post
Office
GroupWise Clients
The Document Viewer Agent (DVA) runs for at least one post office. The DVA converts attached
document files from a wide variety of formats into HTML format for indexing by the POA and for
viewing in GroupWise WebAccess.
3.2
Administration Service Architecture
The GroupWise Administration Service provides the GroupWise Administration console in your
web browser. The Admin console provides the global view of your GroupWise system. It enables you
to configure and customize all GroupWise objects (Domain, Post Office, User, MTA, POA, GWIA,
DVA, and so on). It also provide a number of administrative tools for managing your GrouPWise
system.
Primary
Domain
Server
Admin
Console
Secondary
Domain
Server
Domain
Domain
Admin Service
Admin Service
Admin Service
Post
Office
Admin Service
Post
Office
Server
Admin
Console
Post
Office
Server
Post
Office
Admin Service
Post
Office
Admin Service
Post
Office
Server
Post
Office
Server
Post
Office
The Admin Service runs on each domain server and post office server. The Admin Service
communicates with Admin Services on other GroupWise servers and with the agents that run on its
local server. You can access the Admin console on any domain server. For post office access, you
access the Admin console for the domain that owns the post office.
22
3.3
WebAccess Architecture
WebAccess enables GroupWise users to access their mailboxes from their web browser.
WebAccess
Secure
Login
Web Browser
Internet
WebAccess
Application
Web Server
Post
Office
Agent
Document
Viewer
Agent
Externally, the WebAccess Application, which integrates with your web server, communicates with
the user’s web browser across the Internet. Internally, the WebAccess Application communicates with
the Post Office Agent (POA) to request mailbox data and with the Document Viewer Agent (DVA) for
conversion of attached documents into HTML for viewing.
3.4
Calendar Publishing Host Architecture
The Calendar Publishing (CalPub) Host enables GroupWise users and non-GroupWise users to view
GroupWise users’ calendars from their web browser.
Published
Calendar
No
Login
Web Browser
Internet
Calendar
Publishing
Host
Application
Web Server
Post
Office
Agent
GroupWise
Admin Service
Externally, the CalPub Host Application, which integrates with your web server, communicates with
the user’s web browser across the Internet. Internally, the CalPub Host Application communicates
with the Post Office Agent (POA) to request calendar data from the user’s mailbox. The CalPub Host
requires access to an LDAP server such as NetIQ eDirectory or Microsoft Active Directory for
administrator authentication to the CalPub Admin console.
23
3.5
Monitor Architecture
Monitor enables you to monitor the GroupWise agents from your web browser when you are not
working behind your firewall.
Internal
Monitor
Console
Web
Browser
External
Monitor
Console
Post Office
Agents
Monitor
Application
Message Transfer
Agents
Web Browser
Internet
Web Server
Monitor
Agent
Internet
Agents
Internally, the Monitor Agent gathers status information from GroupWise agents. Externally, the
Monitor Application, which integrates with your web server, communicates with your web browser
across the Internet to provide a Monitor console that is available outside your firewall. The Monitor
Agent also provides its own internal Monitor console independent of your web server, which is
available inside your firewall.
24
II
GroupWise System Requirements
I
You, as a GroupWise administrator, must ensure that your system meets GroupWise system
requirements, so that your GroupWise system can be set up successfully. After your GroupWise
system is set up, you must ensure that users’ workstations meet GroupWise client requirements, so
that users can run the GroupWise clients successfully.
 Chapter 4, “GroupWise Administration Requirements,” on page 27
 Chapter 5, “GroupWise User Requirements,” on page 33
 Chapter 6, “Supported Environments,” on page 35
GroupWise System Requirements
25
26
4
GroupWise Administration
Requirements
4
 Section 4.1, “Hardware and Operating System Requirements,” on page 27
 Section 4.2, “Directory Requirements,” on page 28
 Section 4.3, “Web Server Requirements,” on page 28
 Section 4.4, “Web Browser Requirements Administrators,” on page 29
 Section 4.5, “Internet Agent Functional Requirements,” on page 29
 Section 4.6, “Sample Agent Memory Requirements,” on page 30
4.1
Hardware and Operating System Requirements
 x86-64 processor
 Any of the following server operating systems for the GroupWise agents (Post Office Agent,
Message Transfer Agent, Document Viewer Agent, Internet Agent, Monitor Agent):
 Novell Open Enterprise Server (OES) 11, plus the latest Support Pack
 SUSE Linux Enterprise Server (SLES) 11, plus the latest Service Pack
NOTE: On Linux, the X Window System and Open Motif are required by the GUI
GroupWise agent server consoles for the Post Office Agent, the Message Transfer Agent,
and the Internet Agent.
By default, the GroupWise Linux agents run as services without user interfaces. Starting
and stopping the agents when they are running with a user interface is not supported in the
GroupWise Administration console.
 Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, plus the latest
Service Pack
 Adequate server memory as required by the operating system
Depending on the anticipated load on the GroupWise agents, additional memory might be
required. For details, see Section 4.6, “Sample Agent Memory Requirements,” on page 30.
 Adequate server disk space as required by each GroupWise component:
 Domain Folder: 100-200 MB for the domain database, plus 1 GB or more for message
queues when links are down
 Post Office Folder: 5 MB per user (minimum); 100 MB or more per user (recommended);
plus 100-300 MB for the post office database; plus 500 MB or more for message queues
when links are down
 GroupWise Server Installation: Approximately 885 MB (GroupWise Administration
Service, Message Transfer Agent, Post Office Agent, Internet Agent, and Document Viewer
Agent combined; varies by platform)
GroupWise Administration Requirements
27
For additional Internet Agent requirements, including Internet connectivity requirements,
see Section 4.5, “Internet Agent Functional Requirements,” on page 29.
 WebAccess Installation: Approximately 525 MB (shared with the Calendar Publishing
Host Application and the Monitor Application when they are installed on the same web
server; varies by platform)
 Calendar Publishing Host Installation: Approximately 525 MB (shared with the
WebAccess Application and the Monitor Application when they are installed on the same
web server; varies by platform), plus 50 KB per published calendar and 50 KB per user for
free/busy searching
 Monitor Installation: Approximately 40 MB for the Monitor Agent (varies by platform);
approximately 525 MB for the Monitor Application (shared with the WebAccess
Application and the Calendar Publishing Host Application when they are installed on the
same web server; varies by platform)
For additional disk space guidance, see the GroupWise Best Practices Wiki (http://
wiki.novell.com/index.php/GroupWise).
4.2
Directory Requirements
One or more of the following directories:
 NetIQ eDirectory 8.8.7 or later, plus the latest Support Pack, with LDAP enabled (optional)
You can download eDirectory from the Novell Downloads site (http://download.novell.com).
 Microsoft Active Directory (optional)
 Native GroupWise directory (internal; required)
4.3
Web Server Requirements
The web server that is supported for your operating system, for use with the GroupWise
Administration console, the agent consoles, WebAccess, Monitor, and the Calendar Publishing Host:
 x86-64 or x86-32 processor
 OES 11 / SLES 11
Apache 2.2 plus:
 Tomcat 6
 IBM Java 6 Runtime Environment (JRE)
 ModProxy Module
A Linux repository should be available when you run the GroupWise Installation Wizard.
Apache, Tomcat, the JRE, and the ModProxy Module are automatically installed from the Linux
repository if they are not already present on the Linux server.
If no Linux repository is available during the GroupWise installation, you are prompted to
manually install these required components from the Linux media, and then restart the
GroupWise installation.
 Windows Server 2008 R2 / Windows Server 2012 / Windows Server 2012 R2
Microsoft Internet Information Server (IIS) 7 or later plus:
 Tomcat 6
28
 Jakarta Connector 1.2
Tomcat 6.0.24, IBM JRE 6 Update 26, and Jakarta Connector 1.2 are automatically installed
along with the GroupWise software if they are not already present on the Windows server.
 ISAPI support
On Windows, WebAccess requires ISAPI support. ISAPI support is no longer installed by default
when you install Windows Server 2008 R2 or later and Internet Information Services (IIS). Ideally,
you should select ISAPI support during the installation of IIS. However, if you are installing
WebAccess on Windows Server 2008 R2 or later, and ISAPI support is not yet installed, you can add it
after the fact.
1 In Windows Server Manager, expand Roles, then right-click Web Server (IIS).
2 In the Role Services section, click Add Role Services.
3 Select Application Development, select ISAPI Extensions and ISAPI Filters, then click Install.
4 (Conditional) If you installed the GroupWise WebAccess Application before you installed ISAPI
support, reinstall the GroupWise WebAccess Application.
The WebAccess Installation Wizard restarts Tomcat and IIS to put the ISAPI changes into effect.
4.4
Web Browser Requirements Administrators
Any of the following web browsers for the GroupWise Administration console and agent consoles:
 Linux: Mozilla Firefox
 Windows: Microsoft Internet Explorer 10 or later; Mozilla Firefox
 Macintosh: Mozilla Firefox
NOTE: The web browser requirements for GroupWise WebAccess are different from the web
browser requirements for the Admin and agent consoles. For those user requirements, see
Section 5.2, “GroupWise WebAccess User Requirements,” on page 33.
The Admin and agent consoles are not supported on tables devices. For those user requirements, see
Section 5.3, “GroupWise WebAccess Mobile User Requirements,” on page 34.
4.5
Internet Agent Functional Requirements
The following additional requirements apply when you install the Internet Agent:
 Section 4.5.1, “GroupWise Version Requirements,” on page 30
 Section 4.5.2, “Internet Connectivity Requirements,” on page 30
29
4.5.1
GroupWise Version Requirements
The GroupWise system in which you install the Internet Agent (GWIA) must meet the following
requirements:
 The domain’s version must be equal to or later than the GWIA’s version. The domain’s version is
determined by the Message Transfer Agent (MTA) version running for it.
 The versions of any post offices that the GWIA accesses on behalf of POP3 or IMAP4 clients
must be equal to or later than the GWIA’s version. A post office’s version is determined by the
Post Office Agent (POA) version running for it.
4.5.2
Internet Connectivity Requirements
Before you install the Internet Agent (GWIA), ensure that your network is configured for Internet
connectivity.
 Internet Connection: You can connect to the Internet by using a direct connection over a leased
line or a standard switched telephone line.
 Internet Domain Name: You must have an Internet domain name. The domain name must be
defined by an MX RR (mail exchanger resource record) in DNS.
 DNS Server Access or Relay Host Access: If you want the GWIA to send messages directly to
other SMTP hosts, it requires access to a DNS server for address resolution. Otherwise, it
requires access to a relay host that can perform the address resolution and message routing.
Ensure the server where you plan to install the GWIA is configured to access a DNS server or
can access your relay host. For specific details, refer to your server documentation.
 IP Address: The GWIA’s server requires a static IP address and a fully qualified DNS hostname.
4.6
Sample Agent Memory Requirements
 Section 4.6.1, “Sample POA Memory Requirements Based on Post Office Size,” on page 30
 Section 4.6.2, “Sample Memory Requirements for Other GroupWise Agents and Applications,”
on page 31
4.6.1
Sample POA Memory Requirements Based on Post Office Size
The amount of memory used by the POA depends on the number of active users, as illustrated by the
table below. The POA typically performs best with abundant cache memory available.
30
Concurrent Users
Minimum
Memory
Required
Recommended Memory for
Best Performance
100 active users (100-250 users in post office)
400 MB
2 GB
600 MB
4 GB
800 MB
4 GB
1000 active users (1000 - 1500 users in post office)
1 GB
8 GB - 12 GB
1500 active users (1500 - 3000 users in post office)
2 GB
12 GB
4.6.2
Sample Memory Requirements for Other GroupWise Agents and
Applications
Agent/Application
Minimum
Memory
Required
Recommended Memory for
Best Performance
Routing MTA
200 MB
2 GB
DVA
100 MB
1 GB
GWIA and its MTA
400 MB
4 GB
Monitor
100 MB
1 GB
WebAccess Application
400 MB
4 GB
Calendar Publishing Host Application
200 MB
1 GB
WebAccess and Calendar Publishing Host Applications
together
600 MB
4 GB
31
32
5
GroupWise User Requirements
5
 Section 5.1, “GroupWise Client User Requirements,” on page 33
 Section 5.2, “GroupWise WebAccess User Requirements,” on page 33
 Section 5.3, “GroupWise WebAccess Mobile User Requirements,” on page 34
5.1
GroupWise Client User Requirements
 x86-32 processor or x86-64 processor
On a 64-bit processor, GroupWise still runs as a 32-bit application.
 Any of the following desktop operating systems for the GroupWise client:
 Windows XP on a 300 MHz or higher workstation with at least 128 MB of RAM
 Windows 7 on a 1 GHz or higher workstation with at least 1 GB of RAM
 Windows 8 or Windows 8.1 on a 1 GHz or higher workstation with at least 1 GB of RAM
NOTE: Windows 8 or later on a Microsoft Surface Pro tablet is not supported for use with
the GroupWise client. Use GroupWise WebAccess instead.
 Microsoft Internet Explorer 9 or later
NOTE: On Windows XP, Microsoft Internet Explorer 8.0 is also supported.
 Any of the following word processors for use as the GroupWise editor:
 OpenOffice 3.4 or later
 LibreOffice 3.6 or later
 Microsoft Word 2007 or later
 Approximately 200 MB of free disk space on each user’s workstation to install the GroupWise
client.
5.2
GroupWise WebAccess User Requirements
 Any of the following web browsers:
 Linux: Mozilla Firefox; Google Chrome
 Windows: Microsoft Internet Explorer 9 or later; Mozilla Firefox; Google Chrome
 Macintosh: The latest version of Safari for your version of Mac OS; Mozilla Firefox; Google
Chrome
GroupWise User Requirements
33
 Microsoft Surface Pro tablet, with Windows 8 or later
 Any mobile device that supports Wireless Access Protocol (WAP) and has a microbrowser that
supports Hypertext Markup Language (HTML) 4.0 or later
5.3
GroupWise WebAccess Mobile User Requirements
Any of the following tablet operating systems and tablets:
 Android 4.1, 5.0, or later, with Google Chrome, on any Android device
 Apple iOS 7.x, 8.x, or later, with Apple Safari
 Kindle Fire, with Amazon Silk
 RIM Tablet OS 2.1 or later, with Google Chrome, on the Blackberry Playbook
 Windows Mobile 8.0 or later Pro, with Microsoft Internet Explorer, on any Windows device (full
WebAccess, no template)
NOTE: On a Microsoft Surface Pro tablet, you can use WebAccess in any supported browser,
instead of using WebAccess Mobile.
34
6
Supported Environments
6
 Section 6.1, “IPv6 Support,” on page 35
 Section 6.2, “Clustering Support,” on page 35
 Section 6.3, “Xen Virtualization Support,” on page 36
 Section 6.4, “VMware Support,” on page 36
 Section 6.5, “Hyper-V / Cloud Server Support,” on page 36
 Section 6.6, “Citrix Support,” on page 36
 Section 6.7, “Domain Services for Windows Support,” on page 36
 Section 6.8, “File System Support,” on page 37
6.1
IPv6 Support
The Post Office Agent, the Message Transfer Agent, the Internet Agent, and the Monitor Agent
support the IPv6 protocol when it is available on the server. If IPv6 is available, the agent detects it
and supports it by default, along with IPv4. The Document Viewer Agent does not support IPv6.
As you configure your GroupWise system and specify the network address of an IPv6 server in the
GroupWise Administration console, you must specify its DNS hostname. IP Address fields in the
Admin console do not accommodate IPv6 address format.
6.2
Clustering Support
You can set up your GroupWise system in the following clustering environments:
 Novell Cluster Services on Linux
 Microsoft Clustering on Windows
If you are using one of these clustering environments, see “Clustering” in the GroupWise 2014
Interoperability Guide before using the installation instructions in this guide.
35
6.3
Xen Virtualization Support
You can install components of your GroupWise system in virtual environments where a software
program enables one physical server to function as if it were two or more physical servers. Xen
virtualization technology in Open Enterprise Server (OES) 11 and SUSE Linux Enterprise Server
(SLES) 11 is supported. For more information, see:
 Open Enterprise Server 11 Virtualization documentation (http://www.novell.com/
documentation/oes11/#cat_virtualization)
 SLES Virtualization Technology documentation (https://www.suse.com/documentation/sles11/
#additional)
Large post offices with busy Post Office Agents are not good candidates for Xen virtualization.
Specialized Post Office Agents, such as an indexing Post Office Agent with no mailboxes and users,
could be virtualized using Xen. Other GroupWise components such as the Message Transfer Agent
and the Internet Agent do well when virtualized using Xen.
6.4
VMware Support
GroupWise is supported on VMWare ESX and ESXi. For more information, see the VMware website
(http://www.vmware.com).
All GroupWise components are good candidates for VMware virtualization.
6.5
Hyper-V / Cloud Server Support
GroupWise is supported on Hyper-V Server 2008 and Windows Cloud Server 2012. For more
information, see the Microsoft Hyper-V Server website (http://www.microsoft.com/en-us/servercloud/products/windows-server-2012-r2/default.aspx).
All GroupWise components are good candidates for Hyper-V / Cloud Server virtualization.
6.6
Citrix Support
Any version of the GroupWise client runs successfully on any 32-bit version of Citrix terminal
services.
The GroupWise agents run successfully on Citrix XenServer.
For more information, see the Citrix website (http://www.citrix.com).
6.7
Domain Services for Windows Support
GroupWise can be used with Domain Services for Windows (DSfW) in your NetIQ eDirectory tree.
GroupWise accounts can be added to User objects in the DSfW partition, but all other GroupWise
objects (Domain, Post Office, Agent, and so on) must be created in the eDirectory partition.
IMPORTANT: Do not install GroupWise on the same server with DSfW.
36
6.8
File System Support
GroupWise is supported on any file system supported by the server OS.
NOTE: If you choose to use the NSS file system, turn off Salvage for best performance. For more
information, see the Novell Open Enterprise Server Documentation (https://www.novell.com/
documentation/oes11/).
37
38
III
GroupWise System Creation
I
 Chapter 7, “GroupWise System Overview,” on page 41
 Chapter 8, “Planning Your GroupWise System,” on page 45
 Chapter 9, “Installing the GroupWise Server Software,” on page 63
 Chapter 12, “Adding Users to Your GroupWise System,” on page 81
GroupWise System Creation
39
40
7
GroupWise System Overview
7
Your GroupWise system can be structured in a variety of ways. Some decisions must be made in the
beginning. Other decisions can be made as your GroupWise system grows.
 Section 7.1, “Simple GroupWise System,” on page 41
 Section 7.2, “Typical GroupWise System,” on page 42
 Section 7.3, “GroupWise Users,” on page 42
 Section 7.4, “GroupWise Agents,” on page 43
7.1
Simple GroupWise System
A simple GroupWise system is installed on a single server. A simple GroupWise system would be
appropriate only for a very small number of users working in a single geographic location or for
temporary use in a lab environment.
A simple GroupWise system consists of a single domain (the primary domain) with one post office,
and several users, as shown below:
Simple
GroupWise
System
GroupWise
Server
Message
Transfer
Agent
Primary
Domain
Internet
Agent
Post Office
Internet
Post
Office
Agent
GroupWise Users
Document
Viewer
Agent
A domain organizes post offices into a logical grouping for administration and routing purposes in
your GroupWise system. Messages are transferred between post offices and domains by the Message
Transfer Agent (MTA). Messages are transferred to and from your GroupWise system by the Internet
Agent (GWIA).
A post office serves as an administrative unit for a group of users and mailboxes. Messages are
delivered to mailboxes by the Post Office Agent (POA).
41
7.2
Typical GroupWise System
In contrast to a simple GroupWise system, a typical GroupWise system is installed on multiple
servers, perhaps across multiple geographic locations.
 Primary Domain: The primary domain would be created on its own server and would not own
post offices.
 Secondary Domains: Secondary domains would each be created on their own servers and
would own multiple post offices.
 Post Offices: Depending on server capacity, post offices could be created on domain servers or
could be created on their own servers.
 Internet Agents: One or more Internet Agents would be set up for the GroupWise system. An
Internet Agent could be set up in a domain that owns post offices, or a separate domain could be
created specifically to house one or more Internet Agents.
Typical
GroupWise
System
Primary
Domain
Server
Message
Transfer
Agent
Primary
Domain
Internet
Agent
Secondary
Domain
Server(s)
Message
Transfer
Agent
Post
Office
Agent
Secondary
Domain
Post
Office
Post
Office
Server(s)
Post
Office
Post
Office
Agent
GroupWise Users
Internet
7.3
GroupWise Users
Document
Viewer
Agent
GroupWise Users
You can add users to your GroupWise system in two different ways:
 Manually create users in the internal GroupWise directory
 Import users from an LDAP directory such as NetIQ eDirectory or Microsoft Active Directory
Each GroupWise user has a mailbox in the post office. Users can access their mailboxes in several
ways:
 GroupWise client on a Windows desktop
 GroupWise WebAccess in a supported web browser
 GroupWise WebAccess Mobile on a supported tablet
Users can also synchronize mailbox data with mobile devices using the GroupWise Mobility Service.
42
7.4
GroupWise Agents
Domains, post offices, and mailboxes are supported by four GroupWise agents:
 The Post Office Agent (POA) responds to GroupWise client requests for mailbox data and
delivers messages between users’ mailboxes in a post office. The POA also communicates with
the MTA to route messages to and from the post office. In addition, the POA performs a variety
of maintenance tasks in the post office.
 The Message Transfer Agent (MTA) transfers messages between post offices and domains, and
performs a variety of other functions in the domain.
 The Internet Agent (GWIA) converts GroupWise messages into SMTP format and transfers them
to the Internet SMTP hosts where recipients are located. In reverse, it receives SMTP messages
from Internet SMTP hosts and converts them into GroupWise format. The GWIA can also
provide access for POP3 and IMAP4 clients to access GroupWise mailboxes.
 The Document Viewer Agent (DVA) converts attached document files from a wide variety of
formats into HTML format for indexing by the POA and for viewing in GroupWise WebAccess.
You can run up to three DVAs to service conversion requests for a single instance of the POA.
Each DVA must be installed on a different server.
43
44
8
Planning Your GroupWise System
8
The GroupWise Installation Wizard helps you install the GroupWise software on GroupWise servers.
The GroupWise Installation console helps you create domains and post offices and configure the
GroupWise agents.
Print the following worksheets and fill them out as you plan your GroupWise system:
 Simple, single-server GroupWise system
Simple GroupWise System Worksheet
 Typical, multiple-server GroupWise system
Primary Domain Worksheet
Secondary Domain Worksheet (one for each secondary domain)
Post Office Worksheet (one for each post office)
The topics in this section present the required information in a convenient planning sequence. The
worksheets organize the information in the order in which you need it during installation and setup.
As you review the planning information, record the specific details for your GroupWise system on
the appropriate worksheet.
 Section 8.1, “Planning GroupWise System Information,” on page 45
 Section 8.2, “Planning a Domain,” on page 46
 Section 8.3, “Planning a Post Office,” on page 51
 Section 8.4, “Planning Users,” on page 55
 Section 8.5, “GroupWise System Worksheets,” on page 56
8.1
Planning GroupWise System Information
To identify your GroupWise system as a whole, the Installation console prompts you for the
following information:
 GroupWise System Name
 GroupWise Internet Domain Name
45
8.1.1
GroupWise System Name
You must provide a name for your GroupWise system. The system name can be your company name
(for example, Novell), GroupWise, or anything else that fits the naming scheme you want to use. The
system name is displayed only in the Admin console, so any characters can be used. You cannot
change the name after your GroupWise system is created.
WORKSHEET
Under System Settings, specify the name for your GroupWise system.
8.1.2
GroupWise Internet Domain Name
Your GroupWise system also needs an Internet domain name. The Internet domain name is used
after the @ sign in GroupWise users’ email addresses. You should already have obtained an Internet
domain name from your Internet service provider (ISP).
WORKSHEET
Under GroupWise System Settings, specify the Internet domain name.
Under Create Internet Agent, specify the host name of the GWIA server as it appears in its DNS record.
8.2
Planning a Domain
The primary domain functions as the main administration unit for your GroupWise system.
In a simple, single-server GroupWise system, the primary domain owns one or more post offices and
a GWIA. In a typical, multiple-server GroupWise system, the primary domain can function as a hub
for the secondary domains where post offices and GWIAs are located, or it can own post offices that
are located on other servers.
As you create a domain, the Installation console prompts you for the following information about the
domain:
 Domain Server
 Domain Name
 Domain Folder
 Domain Language
 Domain Time Zone
 Domain Link (Secondary Domain Only)
 Agents for the Domain
 Administrator Access for Domain Creation
46
8.2.1
Domain Server
You can create a domain on Linux or Windows. Your GroupWise system can include both Linux
servers and Windows servers.
WORKSHEET
Under Platform, mark the operating system (Linux or Windows) that you plan to use for the domain.
Under Host, specify the IP address or DNS hostname of the server where you plan to create the domain.
8.2.2
Domain Name
The name of the primary domain might reflect a company name (such as Novell). The name of a
secondary domain might reflect a location (such as Provo), a department (such as Engineering), or
some other element that makes sense for your organization. The name is used as the Domain object’s
name in the Admin console.
The name should consist of a single string. Do not use any of the characters listed in Section C.1,
“Invalid Characters in GroupWise Object Names,” on page 249.
WORKSHEET
Under Domain Settings, specify the domain name.
8.2.3
Domain Folder
The domain requires a folder structure in which to store database files and temporary files that are
created during message routing. If you want, the folder name can reflect the domain name you chose.
You must specify an empty folder. If the folder does not already exist, it is automatically created. The
installation process can proceed more smoothly if you create the folder in advance.
Use the following platform-specific naming conventions for the folder name:
Linux:
Windows:
Use only lowercase characters.
No limitations.
WORKSHEET
Under Domain Settings, specify the full path for the domain folder.
47
8.2.4
Domain Language
The domain language determines the sort order for object lists in the Admin console. The primary
domain language becomes the default language for secondary domains. The owning domain
language becomes the default language for the domain’s post offices.
WORKSHEET
Under Primary Domain Settings, specify the language for the domain.
NOTE: The languages listed for selection in the Installation console includes more languages than
GroupWise supports. See “Multilingual GroupWise Systems” in the GroupWise 2014 Administration
Guide for a list of valid languages.
8.2.5
Domain Time Zone
When a message is sent from a user in one time zone to a user in another time zone, GroupWise
adjusts the message’s time so that it is correct for the recipient’s time zone. For example, if a user in
New York (GMT -05:00, Eastern Time) schedules a user in Los Angeles (GMT -08:00, Pacific Time) for
a conference call at 4:00 p.m. Eastern Time, the appointment is scheduled in the Los Angeles user’s
calendar at 1:00 p.m. Pacific Time.
The primary domain time zone becomes the default time zone for secondary domains. The owning
domain time zone becomes the default time zone for the domain’s post offices.
WORKSHEET
Under Domain Settings, specify the time zone for the domain.
8.2.6
Domain Link (Secondary Domain Only)
When you add a new domain to your GroupWise system, links define how messages are routed from
one domain to another. When you add the first secondary domain, the links between the primary and
secondary domains are very simple. As the number of domains grows, the links among them can
become quite complex. For more information, see “Managing the Links between Domains and Post
Offices” in the GroupWise 2014 Administration Guide.
SECONDARY DOMAIN WORKSHEET
Under Domain Settings, specify the domain that you want to link the new secondary domain to.
8.2.7
Agents for the Domain
Two agents run for a domain. As you configure the agents for the domain, the Installation console
prompts you for the following information:
 MTA Configuration
 GWIA Configuration
The agent consoles are automatically available in the GroupWise Admin console. The agents are
configured to start automatically when the server restarts.
48
MTA Configuration
The Message Transfer Agent (MTA) transfers messages between post offices and domains, and
performs a variety of other functions in the domain.
The MTA requires a TCP/IP connection with POAs in the domain and with MTAs in other domains.
In order to configure the MTA, you need to plan the following port numbers:
 Message Transfer Protocol Port: Used to communicate with the POA. The default MTP port for
the MTA is 7100.
 HTTP Port: Used to communicate with your web browser to provide the MTA console. The
default HTTP port for the MTA is 7180.
Use the default port number unless it is already in use on the server.
WORKSHEET
Under MTA Settings, specify the required port numbers.
For a complete list of default port numbers used by the GroupWise agents, see “GroupWise Port
Numbers” in the GroupWise 2014 Administration Guide.
GWIA Configuration
The Internet Agent (GWIA) converts GroupWise messages into SMTP format and transfers them to
the Internet SMTP hosts where recipients are located. In reverse, it receives SMTP messages from
Internet SMTP hosts and converts them into GroupWise format. The GWIA can also provide access
for POP3 and IMAP4 clients to access GroupWise mailboxes.
The GWIA requires that you provide the fully qualified Internet hostname of the server where the
GWIA runs, such as gwia.example.com, or the name of the "A record" in your DNS table that
associates the hostname with the server's IP address.
WORKSHEET
Under Create Internet Agent, specify the hostname of the GWIA server as it appears in its DNS record if you
want to run the GWIA for this domain.
As your GroupWise system grows, you might want to set up a standalone GWIA in a domain that
does not own post offices.
8.2.8
Administrator Access for Domain Creation
The GroupWise Administration Service provides the GroupWise Administration console for
managing your GroupWise system. For background information, see Section 3.2, “Administration
Service Architecture,” on page 22.
As you configure the domain, the Installation console prompts you for the following information:
 Domain Admin Port
 Primary Domain: Super Admin Creation
 Secondary Domain: Primary Domain Access
49
Domain Admin Port
An instance of the Admin Service runs on each GroupWise domain server so that you can access the
Admin console at the following URL:
https://domain_server_address:9710/gwadmin-console
Replace domain_server_address with the IP address or DNS hostname of the domain server. The
default Admin port for a domain is 9710.
The Admin Service also uses the Admin port to communicate with the MTA for the domain.
WORKSHEET
Under MTA Settings, specify the Admin port for the domain.
Primary Domain: Super Admin Creation
When you create the primary domain of a new GroupWise system, you create a GroupWise Super
Admin user. The Super Admin has all administrative rights throughout your GroupWise system. The
Super Admin can designate other Admin users with lesser rights, perhaps for specific domains or
post offices. For more information, see “GroupWise Administrators” in the GroupWise 2014
Administration Guide.
WORKSHEET
Under Credential Settings, specify the name for the GroupWise Super Admin user and the accompanying
password.
If you need to reset the Super Admin password at a later time, you can use the GroupWise
Administration utility (GWAdminUtil). For more information, see “Using the GroupWise
Administration Utility” in the GroupWise 2014 Administration Guide.
Secondary Domain: Primary Domain Access
When you create a secondary domain, you must be the GroupWise Super Admin or a GroupWise
system administrator, and know the associated password. For more information, see “GroupWise
Administrators” in the GroupWise 2014 Administration Guide.
WORKSHEET
Under System Settings, specify the administrator user name and password that provide access to the primary
domain in the Admin console.
You also need to know the network address of the primary domain server and the Admin port
number for the domain. You must be connected to the primary domain in order to create a secondary
domain.
50
WORKSHEET
Under System Settings, specify the IP address or DNS hostname of the primary domain server and the Admin
port.
8.3
Planning a Post Office
A post office contains users’ mailboxes. Like a domain, a post office requires a name and has a folder
structure.
As you create the post office, the Installation console prompts you for the following information:
 Post Office Server
 Post Office Name
 Post Office Folder
 Post Office Language
 Post Office Time Zone
 Agents in the Post Office
 Administrator Access for Post Office Creation
8.3.1
Post Office Server
You can create a post office on Linux or Windows. Your GroupWise system can include both Linux
servers and Windows servers.
WORKSHEET
Under Platform, mark the operating system (Linux or Windows) that you plan to use for the post office.
Under Host, specify the IP address or DNS hostname of the server where you plan to create the post office.
8.3.2
Post Office Name
A post office, like a domain, requires a unique name. The name can reflect any element that makes
sense for your organization. For example, you could use a location (such as Provo) or a department
(such as Engineering).
The name is used as the Post Office object’s name in the Admin console. It can appear in the
GroupWise Address Book.
The name should consist of a single string. Do not use any of the characters listed in Section C.1,
“Invalid Characters in GroupWise Object Names,” on page 249.
WORKSHEET
Under Post Office Settings, specify the post office name.
51
8.3.3
Post Office Folder
A post office requires a folder structure in which to store database files and temporary files that are
created during message routing and delivery. If you want, the folder name can reflect the post office
name you chose.
You must specify an empty folder. If the folder does not already exist, it is automatically created. The
installation process can proceed more smoothly if you create the folder in advance.
Use the following platform-specific naming conventions for the folder name:
Linux:
Windows:
Use only lowercase characters.
No limitations.
WORKSHEET
Under Post Office Settings, specify the full path for the post office folder.
8.3.4
Post Office Language
The post office language determines the sort order for items in the GroupWise Address Book.
The post office assumes the same language as its domain unless you specify otherwise. For example,
if you set the domain and post office language to English, the GroupWise Address Book items are
sorted according to English sort order rules. This is true even if some users in the post office are
running non-English GroupWise clients such as German or Japanese. Their client interface and help
files are in German or Japanese, but the sort order in the GroupWise Address Book is according to
English standards. Time, date, and number formats for the non-English clients default to the
workstation language.
WORKSHEET
Under Post Office Settings, specify the language for the post office.
NOTE: The languages listed for selection in the Installation console includes more languages than
GroupWise supports. See “Multilingual GroupWise Systems” in the GroupWise 2014 Administration
Guide for a list of valid languages.
52
8.3.5
Post Office Time Zone
When a message is sent from a user in one time zone to a user in another time zone, GroupWise
adjusts the message’s time so that it is correct for the recipient’s time zone. For example, if a user in
New York (GMT -05:00, Eastern Time) schedules a user in Los Angeles (GMT -08:00, Pacific Time) for
a conference call at 4:00 p.m. Eastern Time, the appointment is scheduled in the Los Angeles user’s
calendar at 1:00 p.m. Pacific Time.
In a simple, single-server GroupWise system, the post office is automatically created with the same
time zone as the primary domain. In a typical, multiple-server GroupWise system, the post office
time zone defaults to the domain time zone, but you can change it as you create the post office.
WORKSHEET
Under Post Office Settings, specify the time zone where the post office is located.
8.3.6
Agents in the Post Office
Two agents run for a post office. As you configure the agents for the post office, the Installation
console prompts you for the following information:
 POA Configuration
 DVA Configuration
The agent consoles are automatically available in the GroupWise Admin console. The agents are
configured to start automatically when the server restarts.
POA Configuration
The Post Office Agent (POA) responds to GroupWise client requests for mailbox data and delivers
messages between users’ mailboxes in a post office. The POA also communicates with the MTA to
route messages to and from the post office. In addition, the POA performs a variety of maintenance
tasks in the post office.
The POA requires a TCP/IP connection with the domain’s MTA. It also requires TCP/IP connections
with GroupWise clients. In order to configure the POA, you need to plan the following port numbers:
 Client/Server Port: Used to communicate with GroupWise clients. The default client/server port
is 1677.
 Message Transfer Port: Used to communicate with the MTA. The default MTP port for the POA
is 7101.
 HTTP Port: Used to communicate with your web browser to provide the POA console. The
default HTTP port for the POA is 7181.
 SOAP Port: Used to communicate with SOAP clients such as WebAccess and the GroupWise
Mobility Service. The default SOAP port for the POA is 7191.
WORKSHEET
Under POA Settings, specify the required port numbers.
53
DVA Configuration
The Document Viewer Agent (DVA) converts attached document files from a wide variety of formats
into HTML format for indexing by the POA and for viewing in GroupWise WebAccess. You can run
up to three DVAs to service conversion requests for a single instance of the POA. Each DVA must be
installed on a different server.
The DVA requires a TCP/IP connection with a POA. The default DVA port is 8301. Typically, the DVA
is set up along with a post office.
WORKSHEET
Under Create Document Viewer Agent, mark Yes or No.
If you need to create a DVA on a server that does not have a post office and POA on it, see “Scaling
Your DVA Installation” in the GroupWise 2014 Administration Guide.
8.3.7
Administrator Access for Post Office Creation
In order to create a new post office, you need access to the owning domain.
 Owning Domain Access
 Post Office Admin Port
Owning Domain Access
When you create a post office, you must be the GroupWise Super Admin, a GroupWise system
administrator, or a domain administrator for the owning domain, and you must know the associated
password. For more information, see “GroupWise Administrators” in the GroupWise 2014
WORKSHEET
Under System Settings, specify the administrator user name and password that provide access to the owning
domain in the Admin console.
You also need to know the network address of the primary domain server or the owning domain
server, and the Admin port number for the domain.
WORKSHEET
Under System Settings, specify the IP address or DNS hostname of the domain server and the Admin port for
the domain.
54
Post Office Admin Port
An instance of the Admin Service runs on each GroupWise post office server. You never use this port
when you connect to the Admin console, but the Admin Service uses it to communicate with the
POA for the post office. The default Admin port for a post office is 9711.
WORKSHEET
Under POA Settings, specify the Admin port for the post office.
8.4
Planning Users
When you create a new GroupWise system, you can manually add a few users in order to test your
new system. When you see that everything is working smoothly, you can add all of the users to your
GroupWise system.
For a simple, single-server GroupWise system, you might want to add the users to the internal
GroupWise directory. For a larger number of users, you can import them from an LDAP directory
such as NetIQ eDirectory or Microsoft Active Directory.
 Manually Created Users
 Imported Users
8.4.1
Manually Created Users
You manually create GroupWise users in the Admin console. You can manually create users
specifically for testing a new GroupWise system, or you can initially create users in the internal
GroupWise directory and then later associate them with users in an LDAP directory.
WORKSHEET
Under Users, list any users that you want to create for testing purposes in your new GroupWise system.
8.4.2
Imported Users
In order to import users from an LDAP directory into GroupWise, you need to gather the following
information about the LDAP directory so that GroupWise agents can access it:
 Type: NetIQ eDirectory or Microsoft Active Directory.
 Address: The IP address or DNS hostname of the LDAP server.
 Port: 636 if the LDAP server requires SSL; 389 if SSL is not required.
 SSL Certificate: The location of the LDAP root certificate file on the LDAP server.
 LDAP User: The user name for accessing the LDAP directory.
The user must have sufficient rights to read the LDAP User and Group objects that you plan to
import. Specify the information in the format used by the LDAP server. For example:
cn=user_name,ou=org_unit,o=organization|
cn=user_name,ou=users,dc=server_name,dc=company_name,dc=com
55
 Password: The password for the LDAP user.
 Base DN: (Optional) The LDAP context under which User and Group objects are located.
You must also establish a name for the LDAP directory to be known in your GroupWise system. The
name should be clear and easy to remember, especially if you plan to have multiple GroupWise
administrators.
WORKSHEET
Under LDAP Directory Information, specify the name for the LDAP directory and list the required information for
connecting to the LDAP server.
8.5
GroupWise System Worksheets
 Section 8.5.1, “Simple GroupWise System Worksheet,” on page 56
 Section 8.5.2, “Primary Domain Worksheet,” on page 58
 Section 8.5.3, “Secondary Domain Worksheet,” on page 59
 Section 8.5.4, “Post Office Worksheet,” on page 60
8.5.1
Simple GroupWise System Worksheet
Installation Console Field
Platform
Value for Your Simple GroupWise Explanation
System
“Domain Server” on page 47
 Linux
 Windows
Folders
 Domain folder
“Domain Folder” on page 47
“Post Office Folder” on page 52
 Post office folder
System Settings
 System Name
 Internet Domain Name
 Host
 IP address
“GroupWise System Name” on
page 46
“GroupWise Internet Domain
Name” on page 46
 DNS hostname
Primary Domain Settings
 GroupWise Domain Name
 Domain Folder
 Language
 Time zone
56
“Planning a Domain” on page 46
MTA Settings
 MTP Port
System
“MTA Configuration” on page 49
“Domain Admin Port” on page 50
(default 7100)
 HTTP Port
(default 7180)
 Admin Port
(default 9710)
Create Internet Agent
“GWIA Configuration” on page 49
 Hostname/DNS “A Record”
Name
Create Post Office
“Planning a Post Office” on page 51
Create Document Viewer Agent
“DVA Configuration” on page 54
 Yes
 No
POA Settings
 Client/Server Port
“POA Configuration” on page 53
“Post Office Admin Port” on
page 55
(default 1677)
 MTP Port
(default 7101)
 HTTP Port
(default 7181)
 SOAP Port
(default 7191)
 Admin Port
(default 9711)
Credential Settings
 Admin Name
“Primary Domain: Super Admin
Creation” on page 50
 Password
57
System
Users
“Planning Users” on page 55
 GroupWise Directory


 LDAP Directory
 eDirectory
 Active Directory
LDAP Directory Information
“Imported Users” on page 55
 Name
 Type
 eDirectory
 Address
 Port
 Use SSL
 No
 Yes
SSL Certificate
 LDAP User
 LDAP User Password
8.5.2
Primary Domain Worksheet
Primary Domain Platform
Value for the Primary Domain
Explanation
 Linux
 Windows
Primary Domain Folder

System Settings
 System Name
 Internet Domain Name
 Host
 IP address
 DNS hostname
58
“GroupWise System Name” on
page 46
“GroupWise Internet Domain
Name” on page 46
Value for the Primary Domain
Domain Settings
Explanation
 Domain Folder
 Language
 Time zone
MTA Settings
 MTP Port
(default 7100)
 HTTP Port
(default 7180)
 Admin Port
(default 9710)
Credential Settings
“Primary Domain: Super Admin
Creation” on page 50
 Admin Name
 Password
8.5.3
Secondary Domain Worksheet
Domain Platform
Value for the Secondary Domain
Explanation
 Linux
 Windows
Domain Folder

System Settings
 Primary Domain Host
Secondary Domain: Primary
Domain Access
 Primary Domain Admin Port
 Admin Name
 Password
59
Value for the Secondary Domain
Explanation
Domain Settings
 Domain Folder
 Host
 Link to Domain
 Language
 Time zone
MTA Settings
 MTP Port
(default 7100)
 HTTP Port
(default 7180)
 Admin Port
(default 9710)
“GWIA Configuration” on page 49
 Hostname/DNS “A Record”
Name
8.5.4
Post Office Worksheet
Post Office Platform
Value for the Post Office
Explanation
“Post Office Server” on page 51
 Linux
 Windows
Post Office Folder
“Post Office Folder” on page 52

System Settings
 Owning Domain Host
 Owning Domain Admin Port
 Admin Name
 Password
60
“Owning Domain Access” on
page 54
Post Office Settings
Explanation
“Planning a Post Office” on page 51
 Host
 Language
 Time zone
“DVA Configuration” on page 54
 Yes
 No
POA Settings
 Client/Server Port
“POA Configuration” on page 53
“Post Office Admin Port” on
page 55
(default 1677)
 MTP Port
(default 7101)
 HTTP Port
(default 7181)
 SOAP Port
(default 7191)
 Admin Port
(default 9711)
Users
“Planning Users” on page 55
 GroupWise Directory


 LDAP Directory
 eDirectory
61
LDAP Directory Information
 Name
 Type
 eDirectory
 Address
 Port
 Use SSL
 No
 Yes
SSL Certificate
 LDAP User
 LDAP User Password
62
Explanation
Section 8.4.2, “Imported Users,” on
page 55
9
Installing the GroupWise Server
Software
9
You should have already reviewed Chapter 8, “Planning Your GroupWise System,” on page 45 and
filled out the appropriate GroupWise System Worksheets. The following sections step you through
using the GroupWise Installation Wizard to install the GroupWise Server software.
Follow the installation instructions for the platform where you are creating your GroupWise system:
 Section 9.1, “Linux: Installing the GroupWise
Server Software,” on page 63
Preparing the Linux Server for Your GroupWise
System
Running the Linux GroupWise Installation Wizard
If you are new to Linux, you might want to review
“Linux Basics for GroupWise Administration” in the
GroupWise 2014 Administration Guide before
beginning to install your GroupWise system on Linux.
 Section 9.2, “Windows: Installing the GroupWise Preparing the Windows Server
Server Software,” on page 65
9.1
Running the Windows GroupWise Installation Wizard
Linux: Installing the GroupWise Server Software
 Section 9.1.1, “Preparing the Linux Server for Your GroupWise System,” on page 63
 Section 9.1.2, “Running the Linux GroupWise Installation Wizard,” on page 64
9.1.1
Preparing the Linux Server for Your GroupWise System
1 Ensure that the server for your GroupWise system meets the system requirements listed in
Chapter 4, “GroupWise Administration Requirements,” on page 27.
2 Ensure that the Linux operating system media is available, either physically or in a repository, in
case the Installation Wizard needs to install supporting packages on the Linux server.
3 Ensure that the server has a static IP address.
4 (Optional) Ensure that the folders exist where you want to create your domain and post office
folder structures, as described in “Domain Folder” on page 47 and “Post Office Folder” on
page 52.
5 Continue with Running the Linux GroupWise Installation Wizard.
Installing the GroupWise Server Software
63
9.1.2
Running the Linux GroupWise Installation Wizard
1 In a terminal window, become root by entering su - and the root password.
2 Start the GroupWise Installation Wizard at the root of the downloaded GroupWise 2014 software
image:
./install.sh
3 Type the number for the language in which you want to run the GroupWise Installation Wizard,
then press Enter to select OK.
4 (Optional) Type 1 for Documentation, then press Enter to review the Readme, Quick Start, and
Installation Guide to better prepare yourself for the installation.
5 Type 2 for Installation, then press Enter.
6 Type a to accept the License Agreement and display the Software list.
7 Type 1 for GroupWise Server, then press Enter to display the Actions list.
8 Type 1 for Install, then press Enter to install the GroupWise Server component.
The packages for the GroupWise Server component (Admin Service and agents) are installed on
the server. If any supporting packages are not available on the server, the Installation Wizard
automatically installs them from the operating system media.
9 When the installation is finished, press any key to return to the Installation Options list.
All of the GroupWise agents are installed on every GroupWise server. The MTA and, optionally,
the GWIA are configured to run on a domain server. The POA and the DVA are configured to
run on a post office server.
10 Type 2 for Configure, then press Enter to start the GroupWise Admin Service and display
instructions for accessing the Installation console to create a new GroupWise system.
11 Right-click the URL under To install or configure a new GroupWise server, then click Open Link to
open your web browser.
64
If your web browser does not offer this functionality, open your web browser, then copy the URL
into it.
12 Accept the self-signed certificate that the Installation Wizard has automatically provided for
accessing the Installation console.
13 Skip to the instructions for the type of GroupWise system that you want to create:
9.2
Windows: Installing the GroupWise Server Software
You should have already reviewed Chapter 8, “Planning Your GroupWise System,” on page 45 and
filled out the appropriate GroupWise System Worksheets. The following sections step you through
using the GroupWise Installation Wizard to install the GroupWise Server software.
 Section 9.2.1, “Preparing the Windows Server,” on page 65
 Section 9.2.2, “Running the Windows GroupWise Installation Wizard,” on page 65
9.2.1
Preparing the Windows Server
1 Ensure that the server for your GroupWise system meets the system requirements listed in
Chapter 4, “GroupWise Administration Requirements,” on page 27.
3 Ensure that the firewall on the server has the ports open that are used by the GroupWise agents.
For assistance, see “GroupWise Port Numbers” in the GroupWise 2014 Administration Guide.
4 (Optional) Ensure that the folders exist where you want to create your domain and post office
folder structures, as described in “Domain Folder” on page 47 and “Post Office Folder” on
page 52.
5 Continue with Running the Windows GroupWise Installation Wizard.
9.2.2
Running the Windows GroupWise Installation Wizard
1 Log in to Windows as an Administrator-equivalent user.
2 Run setup.exe at the root of the downloaded GroupWise 2014 software image to start the
GroupWise Installation Wizard.
65
3 (Optional) Review the Readme, Quick Start, and Installation Guide to better prepare yourself for
the installation.
4 Click GroupWise Server to install the GroupWise Server component.
5 Select the language in which you want to perform the installation, then click OK to start the
GroupWise Server Setup Wizard.
6 Click Next to continue.
7 Accept the License Agreement, then click Next to display the Custom Setup page.
The following components are available for installation:
 GroupWise Server: (Required) Consists of the Admin Service, the POA, the MTA, the
GWIA, and the DVA.
All of the GroupWise agents are installed on every GroupWise server. The MTA and,
optionally, the GWIA are configured to run on a domain server. The POA and the DVA are
configured to run on a post office server.
 Client Auto-Update Repository: (Optional) Helps you distribute the GroupWise client
software to users’ Windows workstations.
For usage instructions, see “Using Client Auto-Update to Distribute the GroupWise Client
Software” in the GroupWise 2014 Administration Guide.
8 Click Next to continue, then click Install to install the GroupWise software.
66
9 When the GroupWise software has been installed, click Finish to return to the main page of the
Installation Wizard, then close the Installation Wizard.
The Installation Wizard has created two new icons on your Windows desktop.
10 On your Windows desktop, double-click GroupWise Install
to open your web browser and
access the Installation console.
This starts the GroupWise Admin Service and launches the GroupWise Installation console in
your web browser.
After installation, use GroupWise Admin Console
GroupWise system administration.
to access the Admin console for ongoing
12 Skip to the instructions for the type of GroupWise system that you want to create:
67
68
10
Creating a Simple GroupWise System
10
Before you create your simple GroupWise system, you should have reviewed the following sections
and completed the associated tasks:
 “GroupWise System Overview” on page 41
 “Planning Your GroupWise System” on page 45
 “Simple GroupWise System Worksheet” on page 56
 “Installing the GroupWise Server Software” on page 63
You are ready to use the Installation console to create your simple GroupWise system.
IMPORTANT: As a security feature, the Installation console times out after one hour. For
instructions to renew the session, see Section 11.4, “Handling an Installation Timeout,” on page 79.
1 In the GroupWise Installation console, click
Create a New GroupWise System to display the
System Settings page.
69
2 Fill in the following fields from the Simple GroupWise System Worksheet:
System Name
Internet Domain Name
Host
GroupWise Domain Name
Domain Folder
Language
Time Zone
MTA Settings
MTA MTP Port
MTA HTTP Port
Admin Port
Internet Agent Settings
Hostname/DNS “A Record” Name
Post Office Settings
Create Post Office
Post Office Name
Post Office Folder
POA Client/Server Port
POA HTTP Port
POA MTP Port
Admin Port
You can click Help for more information about the fields.
3 Click Next to display the Credential Settings page:
4 Fill in the following fields from the Simple GroupWise System Worksheet:
Admin Name
Password
5 Click Next to display the Summary page.
6 Review the information that you have provided, then click Finish to create your simple
GroupWise system.
70
7 Click GroupWise Administration Console to log in to the GroupWise Admin console.
8 Specify the GroupWise Super Admin user name and password, then click Login.
9 Skip to Chapter 12, “Adding Users to Your GroupWise System,” on page 81.
71
72
11
Creating a Typical GroupWise System
1
Before you create your GroupWise system, you should have reviewed the following sections and
completed the associated tasks:
 “GroupWise System Overview” on page 41
 “Planning Your GroupWise System” on page 45
 “Primary Domain Worksheet” on page 58
 “Secondary Domain Worksheet” on page 59
 “Post Office Worksheet” on page 60
 “Installing the GroupWise Server Software” on page 63
You are now ready to create your GroupWise system.
 Section 11.1, “Creating the Primary Domain,” on page 73
 Section 11.2, “Adding a Secondary Domain,” on page 75
 Section 11.3, “Adding a Post Office,” on page 77
 Section 11.4, “Handling an Installation Timeout,” on page 79
 Section 11.5, “Changing the Authentication Mode for the Installation Console,” on page 80
IMPORTANT: If you plan to install GroupWise in a clustered server environment, see “Clustering”
the GroupWise 2014 Interoperability Guide before starting to set up your GroupWise system.
11.1
Creating the Primary Domain
When you are finished installing the GroupWise Server software, the Installation Wizard
automatically displays the GroupWise Installation console:
73
Create a New GroupWise System to display the
System Settings page.
NOTE: The following steps assume that you do not want to run the Internet Agent in the
primary domain and that you do not want to create a post office on the same server with the
primary domain.
2 Fill in the following fields from the Primary Domain Worksheet:
System Name
Internet Domain Name
Host
Domain Folder
Language
Time Zone
MTA Settings
MTA MTP Port
MTA HTTP Port
Admin Port
3 Click Next to display the Credential Settings page:
4 Fill in the following fields from the Primary Domain Worksheet:
Admin Name
Password
74
6 Review the information that you have provided, then click Finish to create the primary domain
for your GroupWise system.
7 (Optional) Click GroupWise Administration Console to display the GroupWise Admin console and
administer the domain.
For usage instructions, see Chapter 13, “Working with the GroupWise Administration Console,”
on page 85.
8 Continue with the task that you want to do next:
 Section 11.2, “Adding a Secondary Domain,” on page 75
 Section 11.3, “Adding a Post Office,” on page 77
11.2
Adding a Secondary Domain
1 Install the GroupWise Server software on the domain server that you listed on the Secondary
Domain Worksheet.
For instructions, see Chapter 9, “Installing the GroupWise Server Software,” on page 63.
instructions to renew the session, see Section 11.4, “Handling an Installation Timeout,” on
page 79.
Add a New Domain to display the System Settings
page.
75
3 Fill in the following fields from the Secondary Domain Worksheet:
Primary Domain Host
Primary Domain Admin Port
Admin Name
Password
4 Click Next.
Because no GroupWise software is yet installed on the new GroupWise server, the connection
between it and the owning domain server is not yet trusted. This is normal.
5 Click Trust Connection to display the Domain Settings page.
6 Fill in the following fields from the Secondary Domain Worksheet:
Domain Folder
Host
Link to Domain
Language
Time Zone
MTA Settings
MTA MTP Port
MTA HTTP Port
76
Admin Port
Internet Agent Settings
Hostname/DNS “A Record” Name (optional)
8 Review the information that you have provided, then click Finish to create a secondary domain
in your GroupWise system.
9 (Optional) Click GroupWise Administration Console to display the GroupWise Admin console and
administer the domain.
on page 85.
10 Continue with Adding a Post Office.
11.3
Adding a Post Office
1 Install the GroupWise Server software on the post office server that you listed on the Post Office
Worksheet.
For instructions, see Chapter 9, “Installing the GroupWise Server Software,” on page 63.
page 79.
Add a New Post Office to display the System
Settings page.
77
3 Fill in the following fields from the Post Office Worksheet:
Owning Domain Host
Owning Domain Admin Port
Admin Name
Password
4 Click Next.
Because no GroupWise software is yet installed on the new GroupWise server, the connection
between it and the owning domain server is not yet trusted. This is normal.
5 Click Trust Connection to display the Post Office Settings page.
6 Fill in the following fields from the Post Office Worksheet:
Post Office Name
Host
Post Office Folder
Language
Time Zone
POA Settings
POA Client/Server Port
POA MTP Port
POA HTTP Port
78
Admin Port
8 Review the information that you have provided, then click Finish to create a new post office in
your GroupWise system.
9 Click GroupWise Administration Console to display the GroupWise Admin console.
10 Skip to Chapter 12, “Adding Users to Your GroupWise System,” on page 81.
11.4
Handling an Installation Timeout
As a security feature, the Installation console times out after one hour. This helps prevent access by
unauthorized persons if the Installation console is left unattended. When an installation session times
out, you see the following page:
You then run the following command to obtain a new security token:
Linux:
/opt/novell/groupwise/admin/gwadmin-ipc authorize token_string
Windows:
c:\Program Files\Novell\GroupWise Server\admin\gwadmin-ipc.exe
authorize token_string
If the Timeout page does not provide a token string, use the following method to gain access to the
Installation console:
Linux:
Windows:
Reselect Configure in the Installation Wizard to authorize the Installation console session.
Close the existing browser window.
Double-click GroupWise Install
session.
on the desktop to start a new authorized Installation console
79
11.5
Changing the Authentication Mode for the Installation
Console
By default, the Installation console uses token-based authentication. After initial installation, you can
change the authentication method as needed.
To configure the Installation console to prompt for a user name and password to allow access, use the
following command:
gwadminutil installcfg -m user -u user_name -p
To configure the Installation console to not allow logins so that the configuration of your GroupWise
system cannot be changed by unauthorized users, use the following command:
gwadminutil installcfg -m disabled
To re-enable logins, specify an authentication method:
gwadminutil installcfg -m token
gwadminutil installcfg -m user -u user_name -p
80
12
Adding Users to Your GroupWise
System
12
You can add users to your new GroupWise system by manually typing the user information or by
importing the user information from an LDAP directory such as NetIQ eDirectory or Microsoft
Active Directory. You use the Admin console for either approach. You need to create at least two
users in order to test your new GroupWise system.
 Section 12.1, “Manually Adding Users to the Internal GroupWise Directory,” on page 81
 Section 12.2, “Importing Users from an LDAP Directory,” on page 82
 Section 12.3, “Testing the Users,” on page 84
12.1
Manually Adding Users to the Internal GroupWise Directory
1 In the GroupWise Admin console, click Users > New.
2 Specify the user’s GroupWise user name, along with the user’s first name and last name.
3 In the Post Office field, start typing the name of the post office to select it.
or
Select the post office from the drop-down list.
4 Select Create Another User to create at least one more user in your new GroupWise system.
For more detailed information about planning and adding users, see “Creating GroupWise
Accounts” in the GroupWise 2014 Administration Guide.
5 To provide additional information for each user, click Users, then click each user to display and
edit the properties of each User object.
6 After you have created at least two users, skip to Section 12.3, “Testing the Users,” on page 84.
Adding Users to Your GroupWise System
81
12.2
Importing Users from an LDAP Directory
In order to add users to your new GroupWise system from an LDAP directory such as NetIQ
eDirectory or Microsoft Active Directory, you must first provide configuration information about the
LDAP directory, and then import the users.
 Section 12.2.1, “Providing LDAP Directory Information,” on page 82
 Section 12.2.2, “Importing Users,” on page 83
12.2.1
Providing LDAP Directory Information
1 In the GroupWise Admin console, click System > LDAP Servers > New Directory.
2 Fill in the following fields from the Simple GroupWise System Worksheet or the Post Office
Worksheet:
Name
Type
Address
Port
SSL Certificate (if needed)
LDAP User
LDAP User Password
Base DN (optional)
You can click Help for more information about the fields. For more detailed instructions, see
“Setting Up an LDAP Directory” in the GroupWise 2014 Administration Guide.
3 Click Test Connection to verify that you have specified the required information correctly.
82
4 Click OK to save the LDAP directory information and add the LDAP directory to the list of
LDAP directories.
5 Click Close to close the list and return to the main Admin console window.
6 Continue with Importing Users.
12.2.2
Importing Users
1 In the GroupWise Admin console, click System > User Import.
2 Select the post office to import the users into.
3 Click Preview to list the users to import.
4 (Conditional) If there are individual users that you do not want to import, delete them from the
list.
5 (Conditional) If the list is too long, use the Context and LDAP Filter fields to restrict the list, then
click Update Preview.
Adding Users to Your GroupWise System
83
6 When the list contains the correct set of users, click Import Users to perform the import.
7 Click Close.
8 To see that the users have been imported, click Users.
9 Continue with Testing the Users.
12.3
Testing the Users
1 Install the GroupWise client in order to provide mailbox access on a Windows workstation.
See Chapter 19, “Installing the GroupWise Client,” on page 177 for workstation system
requirements and installation instructions.
2 Log in as each test user and exchange email messages in order to test the POA and the MTA.
3 Exchange email messages with colleagues whose email systems are across the Internet from
your GroupWise system in order to test the GWIA.
4 Continue with the next task that interests you:
84
13
Working with the GroupWise
Administration Console
13
The GroupWise Administration console enables you to perform GroupWise administration
anywhere you have a web browser and an Internet connection.
 Section 13.1, “Accessing the Admin Console,” on page 85
 Section 13.2, “Making the Most of the System Overview,” on page 86
 Section 13.3, “Finding Objects in Object Lists,” on page 87
 Section 13.4, “Finding Frequently Used Objects Quickly,” on page 88
 Section 13.5, “Working with Objects and Object Properties,” on page 88
 Section 13.6, “Using System Tools,” on page 89
13.1
Accessing the Admin Console
When you complete a session in the Installation console, you can go immediately into the Admin
console.
NOTE: If your installation session times out before you access the Admin console, see Section 11.4,
“Handling an Installation Timeout,” on page 79.
To access the Admin console directly:
1 Click the Admin console icon ( ) on your desktop.
or
Display the following URL in your web browser:
https://groupwise_server_address:admin_port/gwadmin-console
Replace groupwise_server_address with the IP address or DNS hostname of the GroupWise
server. If you are not using the default Admin port, replace admin_port with the Admin port
number. If you are using the default Admin port number, you do not need to specify it.
Working with the GroupWise Administration Console
85
The Admin console displays:
13.2
Making the Most of the System Overview
On the System Overview page, you can quickly view and configure all domains, post offices, and
agents in your GroupWise system. The System Overview page also provides status information for
all GroupWise agents, with easy access to their agent consoles and to the controls for starting and
stopping them.
Domains are automatically added to the System Overview page when you create them.
1 If you do not want a specific domain to be displayed, simply close it.
2 To display it again, click Options
> Add Domains.
3 Click a domain, post office, or agent to view its properties.
Agents display status indicators to show whether they are running.
To stop or start an agent:
1 Click Running
or Stopped
.
2 Click the name of the agent to display agent properties.
3 Click Stop Agent or Start Agent.
The agent consoles can also be displayed from the status icons and from the agent properties
pages when the agents are running.
86
13.3
Finding Objects in Object Lists
Click any object type in
the Administration
panel to list all objects
of that type in your
GroupWise system.
Click to collapse the
Administration panel so
that only the icons
display.
After you display
object properties for a
domain or post office,
you can list just the
objects that belong to
that domain or post
office.
To add more columns to an options list, click Options ( ), then select the columns to add.
You can use the Search field to shorten a long list by including only those objects that match the search
criteria. As a simple case in the list above, you could type the letter g and then press Enter to list only
the GroupWise user names that begin with “G.”
But the Search field is much more powerful than that. You can search on any GroupWise object
attribute and list only those objects that have the matching attribute. To see a complete list of
attributes to search on for the displayed object type, press Ctrl+Spacebar in the Search field. Here are
some common searches:
Object List
Search Criteria
Explanation
Domain
domainversion<2014
All domains that have not yet been upgraded
to GroupWise 2014.
Post Office
intruderdetection=false
All post offices where intruder detection has
not yet been enabled.
87
Object List
Search Criteria
Explanation
Post Office Agent
soapenabled=false
All POAs where SOAP is not enabled.
Message Transfer Agent loglevel=diagnostic
All MTAs where the Log Level is set to
Diagnostic.
Internet Agent
bindexclusive=false
All GWIAs that are not configured to find to a
specific IP address.
User
visibility!=system
All users who are not visible to all other users
in the GroupWise Address Book.
For complete usage details, see Appendix B, “Attributes, Operators, and Values for Object Filters,” on
page 245.
13.4
Finding Frequently Used Objects Quickly
When you are not quite sure what you are looking for, the object lists available from the
Administration panel can help you find it. After you have gone to the same object many times, there
are faster ways to display the object that you want.
Global Search
As you start typing in the Global Search field, the Admin console starts building a list of
objects that match. When you see what you want, click the object in order to go to its property
page.
Recent
Every object that you go to is added to your Recent list, with the most recent object at the top
of the list. This makes it very easy to return to any object that you have worked with recently.
Favorites
Any object you go to can be added to your Favorites list. Click
in the upper-right corner of
any object property page to add it to your Favorites list. Favorite objects are alphabetized in
the list so that your Favorites list has a predicable order.
A
on an object property page shows that it is on your Favorites list. Click
object from your Favorites list.
13.5
to remove that
Working with Objects and Object Properties
You can edit the properties of any GroupWise objects that you have rights to modify. If you are
logged in to the GroupWise Admin console as the GroupWise Super Admin, you can edit all objects.
If you are logged in as a subordinate administrator, objects that you do not have rights to modify are
dimmed. GroupWise tools on the System page are dimmed if you do not have rights to use them
Usually, when you work with objects, your changes are saved immediately. Sometimes, changes need
to replicate throughout your GroupWise system before the change is complete. When that happens,
the object is dimmed and you cannot make further changes to the object until replication is finished.
88
13.6
Using System Tools
You can find all of the GroupWise system operations and object-specific utilities on the System page.
The System tools are described in detail in the GroupWise 2014 Administration Guide:
Addressing Rules: Configures GroupWise to perform text
substitutions in email addresses when messages are sent.
See “Addressing Rules.”
Admin-Defined Fields: Maps LDAP directory user fields to GroupWise See “Admin-Defined Fields.”
fields so that they can be displayed in the GroupWise Address Book.
Administrators: Grants administrator rights to GroupWise users on a
system, domain, and post office basis.
See “Administrators.”
Calendar Publishing: Sets up and configures Calendar Publishing
See “Calendar Publishing
Hosts, so that users can publish their GroupWise personal calendars on Host.”
the Internet.
Directory Associations: Creates or redefines links between users in
an LDAP directory (such as NetIQ eDirectory or Microsoft Active
Directory) and GroupWise.
See “Directory Associations.”
Document Viewer Agent: Converts attached document files into
See “Document Viewer
HTML format for display in GroupWise WebAccess and for indexing by Agent.”
the POA, if the POA has been configured to use it.
Email Address Lookup: Searches for the GroupWise object (User,
Resource, or Group) that an email address is associated with.
See “Email Address Lookup.”
Expired Records: Displays the GroupWise user accounts that have an See “Expired Records.”
expiration date assigned to them.
External System Synchronization: Automatically synchronizes
information between your GroupWise system and an external
GroupWise system connected to your local system.
See “External System
Synchronization.”
Global Signatures: Establishes a list of globally available signatures
that can be automatically appended to messages sent by GroupWise
users.
See “Global Signatures.”
Information: Summarizes useful information about your GroupWise
system, including the numbers of all types of objects, along with
mailbox and license statistics.
See “Information.”
89
Internet Addressing: Establishes the allowed and preferred formats
for Internet email addresses in your GroupWise system.
See “Internet Addressing.”
LDAP Servers: Defines LDAP directories (such as NetIQ eDirectory
See “LDAP Directories and
and Microsoft Active Directory) and physical LDAP servers for use with Servers.”
Legacy: Provides for the removal of legacy software distribution
directories and gateways from your GroupWise 2014 system.
See “Legacy.”
Link Configuration: Manages the links between domains throughout
See “Link Configuration.”
Pending Operations: Monitors and resolves the pending
See “Pending Operations.”
administrative operations that have not yet been permanently written to
the appropriate GroupWise databases.
Record Enumerations: Displays by record type the data associated
with any record in a GroupWise database.
See “Record Enumerations.”
Recover Deleted Account: Re-creates recently deleted user and
resource accounts from a backup version of the GroupWise primary
domain database.
See “Recover Deleted
Account.”
Restore Area Management: Manages backup copies of post offices
so that you or GroupWise users can retrieve mailbox items that are
unavailable in your live GroupWise system.
See “Restore Area
Management.”
System Preferences: Configures the defaults for various GroupWise
system-wide settings.
See “System Preferences.”
Time Zones: Provides for modifying existing time zone definitions and
adding new definitions.
See “Time Zones.”
Trusted Applications: Creates and configures GroupWise trusted
applications, which log into POAs and GWIAs in order to access
GroupWise mailboxes without needing personal user passwords.
See “Trusted Applications.”
User Import: Imports user information from an LDAP directory (such as See “User Import.”
NetIQ eDirectory or Microsoft Active Directory) when creating
GroupWise user accounts.
User Move Status: Manages the process of moving mailboxes from
one post office to another.
90
See “User Move Status.”
14
Working with the GroupWise Agents
14
The GroupWise agent software is automatically installed when you create domains and post offices.
For a domain, you run the MTA and optionally the GWIA. For a post office, you run the POA and
optionally the DVA. All of the agents are configured to automatically restart whenever the server
restarts.
Basic agent monitoring and management is most easily performed on the System Overview page in
the Admin console. For instructions, see Section 13.2, “Making the Most of the System Overview,” on
page 86.
This section covers additional agent management tasks that apply to all of the GroupWise agents:
 Section 14.1, “Linux: Managing the Manually Starting and Stopping the Linux GroupWise Agents
GroupWise Agents,” on page 91
Running the Linux GroupWise Agents as a Non-root User
Automatically Restarting the Linux GroupWise Agents with the
GroupWise High Availability Service
Monitoring the Agents from Your Web Browser
Using the Linux GroupWise Agent Log Files
Uninstalling the Linux GroupWise Agents and Applications
If you are new to Linux, you might want to review “Linux Basics for
GroupWise Administration” in the GroupWise 2014 Administration
Guide before you work with the GroupWise agents on Linux.
 Section 14.2, “Windows: Managing Manually Starting and Stopping the Windows GroupWise Agents
the GroupWise Agents,” on
page 104
Using the Windows GroupWise Agent Log Files
Uninstalling the Windows GroupWise Agents and Applications
For detailed configuration information about each agent, see the following sections in the GroupWise
2014 Administration Guide:
 “Post Office Agent”
 “Message Transfer Agent”
 “Internet Agent”
 “Document Viewer Agent”
14.1
Linux: Managing the GroupWise Agents
page 86. Refer to the following additional tasks as you maintain all the GroupWise agents on Linux:
 Section 14.1.1, “Manually Starting and Stopping the Linux GroupWise Agents,” on page 92
 Section 14.1.2, “Running the Linux GroupWise Agents as a Non-root User,” on page 94
91
 Section 14.1.3, “Automatically Restarting the Linux GroupWise Agents with the GroupWise
High Availability Service,” on page 97
 Section 14.1.4, “Using the Linux GroupWise Agent Log Files,” on page 103
 Section 14.1.5, “Uninstalling the Linux GroupWise Agents and Applications,” on page 103
If you are new to Linux, you might want to review “Linux Basics for GroupWise Administration” in
the GroupWise 2014 Administration Guide before you work with the GroupWise agents on Linux.
14.1.1
Manually Starting and Stopping the Linux GroupWise Agents
 “Starting and Stopping the Linux Agents as Services” on page 92
 “Starting the Linux Agents with a User Interface for Troubleshooting” on page 93
Starting and Stopping the Linux Agents as Services
 “Using the grpwise Script” on page 92
 “Using the gwsc Command” on page 93
Using the grpwise Script
All of the Linux GroupWise agents except the Monitor Agent can be started as services by using the
grpwise script. The Monitor Agent uses its own customized grpwise-ma script that works essentially
the same way. When the agents run as services, they do not have a user interface.
In the grpwise script, each agent is designated in terms of the name of the domain and post office
associated with it, in the following format:
POA:
MTA:
GWIA:
DVA:
post_office.domain
domain
gwia.domain
gwdva
Use the following set of rcgrpwise commands to start and stop the agents as services and verify their
status:
rcgrpwise status
Displays the status of the GroupWise agents that are
configured to run on the server.
rcgrpwise status agent_location_name
Displays the status of the specified agent.
rcgrpwise start
rcgrpwise restart
Starts/restarts the GroupWise agents that are
rcgrpwise start agent_location_name
rcgrpwise restart agent_location_name
Starts/restarts the specified agent.
rcgrpwise stop
Stops the GroupWise agents that are configured to
run on the server.
rcgrpwise stop agent_location_name
Stops the specified agent.
If an agent does not respond to the rcgrpwise
stop command, you can use the Linux kill
pid_number command to stop it.
92
rcgrpwise print
Lists the contents of the gwha.conf file where the
agents are configured.
For information about the gwha.conf file, see
Section 14.1.3, “Automatically Restarting the Linux
GroupWise Agents with the GroupWise High
Availability Service,” on page 97.
When the agents run without a user interface, you can monitor them by using their agent consoles.
See Section 14.3, “Monitoring the Agents from Your Web Browser,” on page 107.
Using the gwsc Command
You can also manage the GroupWise agents by using the gwsc command, which is short for the
gwadminutil services command.
For the gwsc command, each agent is designated in terms of its object name or of the name of the
domain and post office associated with it:
POA:
MTA:
GWIA:
DVA:
poa_object_name or post_office_name
mta_object_name or domain_name
gwia_object_name
dva_object_name
Use the following set of gwsc commands to start and stop the agents as services and verify their
status:
gwsc -query
gwsc -query name
gwsc -start
Starts the GroupWise agents that are configured to
run on the server.
gwsc -start name
Starts the specified agent.
gwsc -stop
run on the server.
gwsc -stop name
gwsc -list
Lists the agent services that are configured on the
server.
Starting the Linux Agents with a User Interface for Troubleshooting
In general, you should run the Linux agents as services without a user interface, so that they can be
managed in the Admin console.
Occasionally, when troubleshooting a problem that occurs at agent startup, the problem can occur
before the agent console can be displayed and before error messages can be written to the agent log
file. Under such circumstances, you can start an agent with a user interface in order to view any
errors that the agent displays on the server console before the agent stops again.
93
IMPORTANT: When an agent is running with a user interface, it cannot be managed in the Admin
console.
2 Change to the GroupWise agent bin directory.
cd /opt/novell/groupwise/agents/bin
3 Enter one of the following commands to start an agent with a user interface:
Syntax:
./gwpoa --show --home /post_office_folder &
./gwmta --show --home /domain_folder &
./gwia --show --home /gwia_folder &
Example:
./gwpoa --show --home /mail/polnx &
./gwmta --show --home /mail/domlnx &
./gwia --show --home /mail/domlnx/gwia &
The --show startup switch starts the agent with a server console interface. This user interface
requires that the X Window System and Open Motif be running on the Linux server.
The --home startup switch specifies the directory that is required to start the agent.
The ampersand (&) causes the agent to run in the background, so that the terminal window you
started it in is again available for use.
NOTE: The DVA cannot be started with a user interface.
14.1.2
Running the Linux GroupWise Agents as a Non-root User
For security reasons, it is preferable that the GroupWise agents do not run with root user privileges.
For example, if an intruder manages to assume the identity of a GroupWise agent, the intruder gains
all the privileges of the commandeered process. If the process is running with root user privileges,
then the intruder has root access to your system. If the process is running as a user with minimal
privileges, then the intruder has only restricted access to your system. Therefore, your system is more
secure if the GroupWise agents do not run as root.
The root user still needs to start the agents, because the agents do need to access some root-only
resources on startup. However, you can configure the agents to switch to a different user after they
start. After the agents are running as the non-root user, they need adequate access to the locations
where each domain, post office, and library is located.
 “Setting Up Typical Non-root Access” on page 95
 “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server” on page 95
 “Changing the Non-root User” on page 97
NOTE: You can configure the POA, MTA, and GWIA to run as a non-root user. The DVA must still
run as root. Unlike the other agents, the Monitor Agent can be started as a non-root user by default,
so no setup is required for it to run as a non-root user.
94
Setting Up Typical Non-root Access
To configure the GroupWise agents to switch users after startup:
1 Ensure that you are logged in as root.
2 Select a Linux user for the agents to run as, and ensure that the user is listed in the /etc/passwd
file.
You might want to create a new user specifically for this purpose, perhaps named gwagents. The
user name must not match any local user names on the Linux server.
IMPORTANT: All agents running on the same server must run as the same user.
3 Change to the groupwise folder under /etc:
cd /etc/opt/novell/groupwise
4 Create a new agents folder, then change to that folder:
mkdir agents
cd agents
5 Create a file named uid.conf.
6 Type the selected user name in the file, for example:
gwagents
7 Stop and then start the agents.
While starting as root, the agents automatically change the ownership of the domain and post
office folder structures from root to the user you specified in the uid.conf file. Then they
switch users and run as the user you specified, rather than as root.
IMPORTANT: The first time you start an agent as a non-root user (or if you change from one
non-root user to another), the agent might take longer than usual to start, because of the change
in ownership of the directories and files accessed by that agent. This is especially true of a POA
that services a large post office and that requires access to a restore area, especially a restore area
on a remote server.
8 (Optional) List the agent processes to see that they are no longer running as root.
ps -eaf | grep gw
9 Repeat Step 1 through Step 8 on each domain and post office server.
Later on, if you want to change the user that the agents are running as, follow the instructions in
“Changing the Non-root User” on page 97.
Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server
When your domains, post offices, and libraries are located on a Novell Open Enterprise Server (OES)
NSS volume, you must set up an eDirectory user for the agents to run as and you must Linux-enable
that user. On OES, you can use NetIQ iManager to accomplish these tasks.
To configure the agents to switch users after startup and provide access to an NSS volume:
1 Select or create an eDirectory user for the agents to run as.
95
You might want to create a new user specifically for this purpose, perhaps named gwagents. The
user name must not match any local user names on the Linux server.
1a From the Open Enterprise Server Welcome page in your web browser, click the Management
Services tab, then click iManager.
1b To log in to iManager, specify a user name, a password, and a tree.
1c In the left pane, expand Users, then click Create User.
1d Provide the required information, then click OK.
The user does not need a password
IMPORTANT: All agents running on the same server must run as the same user.
2 Linux-enable the user you just created:
2a In the left pane, expand Linux User Management, then click Enable User for Linux.
2b Browse to and select the user you just created, then click OK.
2c Select the primary group for the user to belong to (for example, admingroup).
2d Change /bin/bash to /bin/false because the user does not need a shell.
2e Click OK to Linux-enable the user.
3 Ensure that you are logged in as root.
4 Change to the groupwise folder under /etc:
cd /etc/opt/novell/groupwise
5 Create a new agents folder, then change to that folder:
mkdir agents
cd agents
6 Create a file named uid.conf.
7 Type the selected user name in the file, for example:
gwagents
8 Use the following command to grant the user the required rights to the folders that the agents
need to access on the local server:
rights -f /folder_name -r rwcemf trustee user.context.tree
The POA needs access to the post office folder. The MTA and the GWIA need access to the
domain folder.
9 Stop and then start the agents.
While starting as root, the agents automatically change the ownership of the domain and post
office folder structures from root to the user you specified in the uid.conf file. Then they
switch users and run as the user you specified, rather than as root.
IMPORTANT: The first time you start an agent as a non-root user (or if you change from one
non-root user to another), the agent might take longer than usual to start, because of the change
in ownership of the directories and files accessed by that agent. This is especially true of a POA
that services a large post office and that requires access to a restore area, especially a restore area
on a remote server.
10 (Optional) List the agent processes to see that they are no longer running as root.
96
ps -eaf | grep gw
11 Repeat Step 3 through Step 10 on each domain and post office server.
Later on, if you want to change the user that the agents are running as, follow the instructions in
“Changing the Non-root User” on page 97.
Changing the Non-root User
To prevent an agent from running as a different user than the one for which it was originally
configured, the GroupWise agents create a uid.run file in the domain or post office folder that they
service. The GWIA creates the uid.run file in its gwia directory (typically domain/wpgate/gwia).
If, for any reason, the user specified in the uid.run file does not match the user specified in the
uid.conf file, the agent displays the following message:
Error: Running the agent with conflicting effective users
This could happen if the user specified in the uid.conf file is manually edited, or if the uid.conf file
is deleted, thus changing or removing the information about the user that the agent should run as. If
this message appears, verify that the uid.conf file specifies the desired user, then delete the uid.run
file.
After displaying the message, the agent does not start, because it no longer has appropriate
permissions in the domain or post office folder that it needs to service. By deleting the uid.run file,
you enable the agent to reset the permissions in the domain or post office folder to the appropriate
user and then start successfully.
After configuring an agent to run as a specific non-root user:
 If you want the agent to run as a different non-root user, modify the uid.conf file in the /etc/
opt/novell/groupwise/agents folder to specify the desired non-root user. Then delete the
uid.run file from the folder serviced by the agent.
 If you want the agent to run as root again, delete the uid.conf file from the /etc/opt/novell/
groupwise/agents folder, and delete the uid.run file from the folder serviced by the agent.
14.1.3
Automatically Restarting the Linux GroupWise Agents with the
GroupWise High Availability Service
You can use the GroupWise High Availability Service (gwha), in conjunction with GroupWise
Monitor, to detect when a Linux GroupWise agent has stopped unexpectedly and to restart it
automatically.
NOTE: On Windows, Microsoft Clustering Services can automatically restart a GroupWise agent
service that is not responding. However, on Linux, some clustering environments do not include this
capability, so it is provided by the GroupWise High Availability Service.
The GroupWise High Availability Service is installed automatically. After you enable it, it
automatically starts when your server starts.
The High Availability Service relies on the Monitor Agent to detect when a Linux GroupWise agent is
no longer running. The Monitor Agent notifies the GroupWise High Availability Service of any
problem. Then the GroupWise High Availability Service then issues the command by using the
grpwise script to start the problem agent. The GroupWise High Availability Service runs as root, as
configured in the /etc/xinetd.d/gwha file.
97
A single Monitor Agent can service multiple instances of the GroupWise High Availability Service on
multiple servers, as long as all instances use the same user name and password to communicate with
the Monitor Agent.
NOTE: You can use either the Linux Monitor Agent or the Windows Monitor Agent to monitor the
Linux GroupWise agents. However, you cannot use the GroupWise High Availability Service to
restart the Windows GroupWise agents.
 “Reconfiguring the GroupWise High Availability Service (Optional)” on page 98
 “Enabling the GroupWise High Availability Service” on page 100
 “Creating a GroupWise High Availability Service User” on page 101
 “Configuring the Monitor Agent to Communicate with the GroupWise High Availability
Service” on page 101
 “Testing the High Availability Service” on page 103
Reconfiguring the GroupWise High Availability Service (Optional)
The default configuration of the High Availability Service is often appropriate, but you can optionally
edit its configuration files to customize its functionality:
 “Editing the gwha File to Change the Port Number (Optional)” on page 98
 “Editing the gwha.conf File to Enable SSL and Customize Agent Management (Optional)” on
page 99
Editing the gwha File to Change the Port Number (Optional)
The basic configuration for the GroupWise High Availability Service is contained in the /etc/
xinetd.d/gwha file:
socket_type = stream
user = root
server = /opt/novell/groupwise/agents/bin/gwha
wait = no
instances = 1
protocol = tcp
type = UNLISTED
port = 8400
disable = yes
The only option you can change in this file is the port number. By default, the GroupWise High
Availability service listens on port 8400. If that port number is already in use on the server where you
are setting up the GroupWise High Availability service, you can change the port number in the gwha
file.
IMPORTANT: The GroupWise High Availability service must use the same port number on all
servers where you want it to restart the GroupWise agents.
2 Edit the gwha file in an ASCII text editor.
3 Change the port number as needed.
IMPORTANT: Do not change any other options in this file.
4 Save the file, then exit the text editor.
98
5 Continue with Editing the gwha.conf File to Enable SSL and Customize Agent Management
(Optional).
or
Skip to “Enabling the GroupWise High Availability Service” on page 100.
Editing the gwha.conf File to Enable SSL and Customize Agent Management (Optional)
The interaction between the GroupWise High Availability service and the GroupWise agents is
controlled by the following file:
/etc/opt/novell/groupwise/gwha.conf
You can reconfigure the following functionality:
 Enable SSL between the High Availability Service and the Monitor Agent.
 Change the length of time between when the grpwise script issues the command to start an
agent, and when the script displays a message indicating that the agent has started.
 If you changed the port number in the /etc/xinetd.d/gwha file, make the corresponding
change in the gwha.conf file.
At the top of the gwha.conf file, in the [gwha] section, is a section for configuring SSL for
communication between the GroupWise High Availability service and the Monitor Agent. After the
[gwha] section are sections for each agent that is configured to run on the server, as shown. The
headings for the agent sections match the agent designations listed in “Starting and Stopping the
Linux Agents as Services” on page 92.
[gwha]
ssl
key
cert
password
= no
=
=
=
[domain_name]
server
= /opt/novell/groupwise/agents/bin/gwmta
command
= /etc/init.d/grpwise
startup
= domain_name.mta
delay
= 2
wait
= 10
[post_office_name.domain_name]
server
= /opt/novell/groupwise/agents/bin/gwpoa
command
startup
= post_office_name.poa
delay
= 2
wait
= 10
[gwia.domain_name]
server
= /opt/novell/groupwise/agents/bin/gwia
command
startup
= gwia.cfg
delay
= 2
wait
= 10
[gwdva]
server
command
startup
delay
wait
=
=
=
=
=
/opt/novell/groupwise/agents/bin/gwdva
/etc/init.d/grpwise
gwdva.dva
2
10
99
To reconfigure the GroupWise High Availability service in the gwha.conf file:
2 Edit the gwha.conf file in an ASCII text editor.
3 (Conditional) If you use SSL, fill in the following fields in the [gwha] section:
[gwha]
ssl
key
cert
password
=
=
=
=
yes
file_name.key
file_name.crt
password
4 (Conditional) If you changed the port number for the GroupWise High Availability service, as
described in “Reconfiguring the GroupWise High Availability Service (Optional)” on page 98,
add the following line to the [gwha] section:
port = port_number
Replace port_number with the new port number you specified in the gwha file.
5 (Optional) If you want to control how the grpwise script manages starting and stopping the
agents, modify the delay = and wait = settings.
The delay = setting controls the length of time between when the script issues the command to
start an agent and when the script displays a message indicating that the agent has started. The
default delay time is 2 seconds. Under certain circumstances, an agent could encounter a
problem and fail to start after 2 seconds. In this case, you would receive the success message, but
the agent would not be running. You need to increase the delay = setting to accommodate the
length of time it typically takes for the agent to start successfully on your system.
The wait = setting controls the length of time between when the script issues the command to
stop an agent and when the script kills the agent if the agent has not yet stopped. The default
wait time is 10 seconds. Under certain circumstances, an agent could take longer than 10 seconds
to perform a normal shutdown, and killing the agent under those circumstances would not be
appropriate. You need to increase the wait = setting to accommodate the length of time it
usually takes for the agent to shut down. A message notifies you if the script kills an agent
because its shutdown exceeds the wait = setting.
The default settings are usually appropriate, so you do not need to change them unless you
frequently encounter problems with starting or stopping an agent with the script.
7 Continue with Enabling the GroupWise High Availability Service.
Enabling the GroupWise High Availability Service
1 In YaST, click Network Services > Network Services (inetd).
2 (Conditional) If necessary, select Enable to activate the list of services.
3 Scroll down to the gwha line, select it, then click Toggle Status (On or Off) to change the status to
On.
4 Click Finish.
5 Repeat Step 1 through Step 4 on all servers where you want the GroupWise High Availability
service to restart the GroupWise agents.
6 Continue with Creating a GroupWise High Availability Service User.
100
Creating a GroupWise High Availability Service User
The GroupWise High Availability service needs a login user on each server where GroupWise agents
need to be restarted.
1 Create a new user and associated password on the local Linux server to represent the
GroupWise High Availability service.
You might name it gwhauser.
IMPORTANT: Use a local user account for use only by the GroupWise High Availability service.
Do not use a Novell Linux-enabled user. Do not use root.
2 Create the same user on each Linux server where you want the GroupWise High Availability
service to restart the GroupWise agents.
3 On each Linux server, configure the gwha.allow file for the new user:
3a Change to the following folder:
/etc/opt/novell/groupwise
3b Edit the gwha.allow file in an ASCII text editor.
3c Specify the user that you created in Step 1.
3d Save the file, then exit the text editor.
4 Continue with Configuring the Monitor Agent to Communicate with the GroupWise High
Availability Service.
Configuring the Monitor Agent to Communicate with the GroupWise High
Availability Service
After you have the GroupWise High Availability service set up and working correctly on all Linux
servers where you want it to restart the GroupWise agents, you need to configure the Monitor Agent
to communicate with it, and then test it to ensure that you can rely on it in the future.
IMPORTANT: Although you need a GroupWise High Availability service running on each Linux
server where there are GroupWise agents, you need only one Monitor Agent to monitor all agents in
 “Configuring the Linux Monitor Agent” on page 101
 “Configuring the Windows Monitor Agent” on page 102
Configuring the Linux Monitor Agent
1 Install the Linux Monitor Agent.
For installation instructions, see Chapter 18, “Setting Up GroupWise Monitor,” on page 157.
2 Configure the Linux Monitor Agent with the --hauser, --hapassword, and --hapoll startup
switches.
The Monitor Agent uses the --hauser and --hapassword switches to communicate with the
GroupWise High Availability service on port 8400, as configured in the /etc/xinetd.d/gwha
file. When the Monitor Agent notices that a GroupWise agent has stopped, it notifies the
GroupWise High Availability Service. Then the GroupWise High Availability Service issues the
command to restart the problem agent.
101
For more information, see “Using Monitor Agent Startup Switches” in the GroupWise 2014
2a In YaST, click System > /etc/sysconfig Editor.
2b Expand Network > Mail > GroupWise.
2c Click GROUPWISE_MA_OPTIONS.
2d In the Setting field, set the --hauser and --hapassword switches for the user that you created
in “Creating a GroupWise High Availability Service User” on page 101.
TIP: An easy way to create the string is to copy the example at the bottom of the Description
paragraph and replace username and password as needed.
2e In the Setting field, set the --hapoll switch for the number of seconds in the poll cycle on
which the Monitor Agent contacts the GroupWise High Availability Service to provide
agent status information.
2f Click OK to save the settings.
2g Click OK again to save the change.
2h Exit YaST.
3 Start the Monitor Agent.
rcgrpwise-ma start
4 Skip to “Testing the High Availability Service” on page 103.
Configuring the Windows Monitor Agent
1 Install the Windows Monitor Agent as either an application with a server console UI on the
server or as a Windows service without UI on the server.
For installation instructions, see Chapter 18, “Setting Up GroupWise Monitor,” on page 157.
NOTE: The Windows Monitor Agent provides a server console that is not available on Linux.
For more information, see “Comparing the Monitor Consoles” in the GroupWise 2014
2 Configure the Windows Monitor Agent with the /hauser, /hapassword, and /hapoll startup
switches.
The Monitor Agent uses the --hauser and --hapassword switches to communicate with the
GroupWise High Availability service on port 8400, as configured in the /etc/xinetd.d/gwha
file. When the Monitor Agent notices that a GroupWise agent has stopped, it notifies the
GroupWise High Availability Service. Then the GroupWise High Availability Service issues the
command to restart the problem agent.
For more information, see “Using Monitor Agent Startup Switches” in the GroupWise 2014
3 (Conditional) If you installed the Windows Monitor Agent as an application:
3a Create a batch file similar to the following example:
c:\Program Files\Novell\GroupWise Server\Monitor\gwmon.exe
/hauser-gwha /hapassword-gwha /hapoll-60
3b Create a desktop icon for running the batch file.
3c To start the Monitor Agent, run the batch file.
102
4 (Conditional) If you installed the Windows Monitor Agent as a Windows service:
4a In the Control Panel, click Administrator Tools > Services.
4b Right-click GroupWise Monitor, then click Properties.
4c In the Start Parameters field, specify the required Monitor Agent startup switches, then click
OK. For example:
/hauser-gwha /hapassword-gwha /hapoll-60
4d To start the Monitor Agent, right-click GroupWise Monitor, then click Start.
Testing the High Availability Service
1 Stop one of the Linux agents, as described in “Starting and Stopping the Linux Agents as
Services” on page 92.
2 Check the status of the agent you stopped to make sure it is stopped.
3 Wait for the next Monitor Agent polling cycle.
You can check and, if necessary, change the Monitor Agent polling cycle in the Monitor Agent
console. Click Preferences, then scroll down to the HTTP Settings section.
4 After the polling cycle has passed, check the status of the agent again.
The agent that you stopped should now be running again.
14.1.4
Using the Linux GroupWise Agent Log Files
Agent status messages and error messages are written to the agent log files (mmddagent.nnn) in
agent-specific subfolders of the following folder:
/var/log/novell/groupwise
The log file name includes the month and day when it was created, the name of the agent, and an
incrementing extension to accommodate multiple log files on the same day.
The agents also maintain a symbolic link to a file named agent.currentlog, where agent is the
name of the agent object in the Admin console. This link points to the current agent log file,
regardless of the date and incrementing extension of the actual agent log file name. This facilitates
monitoring the current agent log file using the tail command.
NOTE: The agent.currentlog symbolic link is not available for the DVA log files.
14.1.5
Uninstalling the Linux GroupWise Agents and Applications
If you move the GroupWise agents to a different server, the GroupWise agent software can be
uninstalled just like any other software on Linux. To determine what GroupWise software is
currently installed on the Linux server, use the following command:
rpm -qa | grep groupwise
103
This lists all of the GroupWise RPM packages on the server. The POA, the MTA, the GWIA, and the
DVA are together in the same RPM. WebAccess has its own RPM. Monitor has two RPMs, one for the
agent software and one for the application software.
The following list shows all GroupWise RPMs that you might need to uninstall from a server:
POA, MTA, GWIA, and DVA:
WebAccess Application:
Monitor Agent:
Monitor Application:
Calendar Publishing Host Application:
GroupWise High Availability Service:
GroupWise Check:
GroupWise Database Copy:
novell-groupwise-server-version-date
novell-groupwise-webaccess-version-date
novell-groupwise-gwmon-version-date
novell-groupwise-monitor-version-date
novell-groupwise-calhost-version-date
novell-groupwise-gwha-version-date
novell-groupwise-gwcheck-version-date
novell-groupwise-dbcopy-version-date
Use the following command to uninstall a GroupWise RPM package:
rpm -e novell-groupwise-package
Uninstalling the RPMs does not uninstall files created after installation by the GroupWise programs.
To completely uninstall GroupWise, delete GroupWise files from the following locations:
/etc/init.d
/usr/sbin
/etc/xinitd.d
/etc/opt/novell/groupwise
/var/opt/novell/groupwise
/var/log/novell/groupwise
14.2
Windows: Managing the GroupWise Agents
page 86. Refer to the following additional tasks as you maintain all the GroupWise agents on
Windows:
 Section 14.2.1, “Manually Starting and Stopping the Windows GroupWise Agents,” on page 104
 Section 14.2.2, “Using the Windows GroupWise Agent Log Files,” on page 106
 Section 14.2.3, “Uninstalling the Windows GroupWise Agents and Applications,” on page 106
14.2.1
Manually Starting and Stopping the Windows GroupWise Agents
 “Manually Starting and Stopping the GroupWise Agents as Services” on page 104
 “Manually Starting the Windows Agents As Applications for Troubleshooting” on page 105
Manually Starting and Stopping the GroupWise Agents as Services
 “By Using the Windows Services Tool” on page 105
 “By Using the gwsc Command” on page 105
104
By Using the Windows Services Tool
You can manage the GroupWise agents just as you would any other Windows services.
For example, on Windows Server 2012:
1 From the Windows desktop, click Start > Administrative Tools > Services.
2 Select the agent service, then click Start.
or
Select the agent service, then click Stop.
When the agents run without a user interface, you can monitor them by using their agent consoles.
See Section 14.3, “Monitoring the Agents from Your Web Browser,” on page 107.
By Using the gwsc Command
You can also manage the GroupWise agents by using the gwsc command, which is short for the
gwadminutil services command.
For the gwsc command, each agent is designated in terms of its object name or of the name of the
domain and post office associated with it:
POA:
MTA:
GWIA:
DVA:
poa_object_name or post_office_name
mta_object_name or domain_name
gwia_object_name
dva_object_name
Use the following set of gwsc commands to start and stop the agents as services and verify their
status:
gwsc -query
gwsc -query name
gwsc -start
Starts the GroupWise agents that are configured to
run on the server.
gwsc -start name
Starts the specified agent.
gwsc -stop
run on the server.
gwsc -stop name
gwsc -list
Lists the agent services that are configured on the
server.
Manually Starting the Windows Agents As Applications for Troubleshooting
In general, you should run the Windows agents as services without a user interface, so that they can
be managed in the Admin console.
105
Occasionally, when troubleshooting a problem that occurs at agent startup, the problem can occur
before the agent console can be displayed and before error messages can be written to the agent log
file. Under such circumstances, you can start an agent with a user interface in order to view any
errors that the agent displays on the server console before the agent stops again.
IMPORTANT: When an agent is running with a user interface, it cannot be managed in the Admin
console.
To run the agents as applications, you can create desktop shortcuts for them. The desktop shortcuts
need to contain the following commands:
Syntax:
c:\Program Files\Novell\GroupWise Server\agents\gwpoa.exe
/home \post_office_folder
c:\Program Files\Novell\GroupWise Server\agents\gwmta.exe
/home \domain_folder
c:\Program Files\Novell\GroupWise Server\agents\gwia.exe
/home /gwia_folder
c:\Program Files\Novell\GroupWise Server\agents\Monitor\gwmon.exe
/home \domain_folder
Example:
c:\Program Files\Novell\GroupWise Server\agents\gwpoa.exe
/home \mail\powin
c:\Program Files\Novell\GroupWise Server\agents\gwmta.exe
/home \mail\domwin
c:\Program Files\Novell\GroupWise Server\agents\gwia.exe
/home \mail\domwin\gwia
c:\Program Files\Novell\GroupWise Server\agents\Monitor\gwmon.exe
/home \mail\domwin
14.2.2
Using the Windows GroupWise Agent Log Files
Agent status messages and error messages are written to the agent log files (mmddagent.nnn) in the
following directories:
POA:
MTA:
GWIA:
DVA:
Monitor:
post_office_folder\wpcs\ofs
domain_folder\mslocal
domain_folder\wpgate\gwia\000.prc
c:\ProgramData\Novell\GroupWise\gwdva
c:\ProgramData\Novell\GroupWise Monitor
NOTE: On some versions of Windows Server, the ProgramData folder is not visible by default. To
display it in File Explorer, click View, then select Hidden items.
14.2.3
Uninstalling the Windows GroupWise Agents and Applications
If you move the GroupWise agents to a different server, you can uninstall the agent software from the
old location to reclaim disk space.
Agents:
106
In the Control Panel, click Programs and Features. Right-click Novell GroupWise Server, then
click Uninstall.
Monitor:
Stop the Monitor Agent, then delete the c:\Program Files\Novell\GroupWise
Server\Monitor folder.
Applications: Stop Tomcat, then delete the following folder:
c:\Novell
14.3
To monitor any GroupWise agent from your web browser, view the agent console by supplying the
IP address or DNS hostname and the port number of the agent. The following table lists the default
port numbers:
POA:
MTA:
GWIA:
DVA:
Monitor:
http://server_network_address:7181
For more information about the agent consoles, including instructions on protecting the agent
consoles with passwords, see the following sections in the GroupWise 2014 Administration Guide:
 “Using the POA Console”
 “Using the MTA Console”
 “Using the GWIA Console”
 “Using the DVA Console”
 “Using the Monitor Web Console”
107
108
15
What’s Next
15
After you have created your GroupWise system, you can expand the system in the following ways:
Task
Section in This Guide
Setting up GroupWise WebAccess so that users
See Chapter 16, “Setting Up GroupWise WebAccess,” on
can access their mailboxes through a web browser page 113.
on a computer or mobile device
Setting up a GroupWise Calendar Publishing Host See Chapter 17, “Setting Up the GroupWise Calendar
so that GroupWise users can share their personal Publishing Host,” on page 131.
calendars and free/busy information with Internet
users
Setting up GroupWise Monitor to monitor your
GroupWise agents
See Chapter 18, “Setting Up GroupWise Monitor,” on
page 157.
Setting up users to run the GroupWise client on
their workstations
See Chapter 19, “Installing the GroupWise Client,” on
page 177.
Setting up synchronization between users’
GroupWise mailboxes and their mobile devices
See Section 20.1, “Using the GroupWise Mobility Service
to Synchronize GroupWise Data to Mobile Devices,” on
page 183.
Setting up instant messaging capabilities for users See Section 20.2, “Using Novell Messenger to Provide
Secure Instant Messaging for GroupWise Users,” on
page 183.
Setting up team collaboration capabilities
See Section 20.3, “Using Novell Vibe to Provide Team
Workspaces for GroupWise Users,” on page 184.
After your GroupWise system is fully installed, you can maintain your GroupWise system in the
following ways:
Task
Section in the GroupWise 2014 Administration Guide
Adding multiple domains to your GroupWise
system
See “Domains.”
Adding post offices to new domains
See “Post Offices.”
Adding more users to post offices
See “Users.”
Defining resources that users can schedule
See “Resources.”
Defining groups of users that GroupWise users can See “Groups.”
select when addressing messages
Changing the GroupWise client from Online mode
to Caching mode so that users’ messages are
stored on a local drive as well as in the post office
See “Client.”
What’s Next
109
110
Task
Setting up GroupWise Remote so that GroupWise
client users can access their mailboxes from a
computer that is not directly connected to your
network
See “Client.”
Controlling the functionality of users’ GroupWise
client software
See “Client.”
Setting up a library
See “Libraries and Documents.”
Configuring the agents to support secure
connections (SSL)
See “Post Office Agent,” “Message Transfer Agent,”
“Internet Agent,” and “Document Viewer Agent.”
Configuring GroupWise to run in a clustering
environment
See the “Clustering” in the GroupWise 2014
Interoperability Guide.
IV
GroupWise Component Installation
and Setup
IV
 Chapter 16, “Setting Up GroupWise WebAccess,” on page 113
 Chapter 17, “Setting Up the GroupWise Calendar Publishing Host,” on page 131
 Chapter 18, “Setting Up GroupWise Monitor,” on page 157
 Chapter 19, “Installing the GroupWise Client,” on page 177
 Chapter 20, “Using Other Novell Products with GroupWise,” on page 183
GroupWise Component Installation and Setup
111
112
16
Setting Up GroupWise WebAccess
16
GroupWise WebAccess enables users to access GroupWise mailboxes through desktop web
browsers, through tablet devices such as Apple iPads, and through mobile devices. The following
sections provide information to help you successfully install the GroupWise WebAccess Application
in your existing GroupWise system.
 Section 16.1, “GroupWise WebAccess Overview,” on page 113
 Section 16.2, “GroupWise WebAccess System Requirements,” on page 116
 Section 16.3, “Planning GroupWise WebAccess,” on page 118
 Section 16.4, “Installing the GroupWise WebAccess Software,” on page 120
 Section 16.5, “Testing GroupWise WebAccess,” on page 125
 Section 16.6, “What’s Next,” on page 128
 Section 16.7, “GroupWise WebAccess Installation Worksheet,” on page 129
16.1
GroupWise WebAccess Overview
 Section 16.1.1, “GroupWise WebAccess Functionality,” on page 113
 Section 16.1.2, “GroupWise WebAccess Components,” on page 114
 Section 16.1.3, “WebAccess Security Requirements,” on page 114
16.1.1
GroupWise WebAccess Functionality
When used in a desktop web browser, GroupWise WebAccess provides much of the functionality
available in the GroupWise client. On a tablet device, the most commonly used functionality is
available. WebAccess functionality on mobile devices is limited compared to WebAccess in a desktop
browser or on a tablet device.
See the following guides for WebAccess user functionality details:
 GroupWise 2014 WebAccess User Guide
 GroupWise 2014 WebAccess Mobile User Guide
 WebAccess Basic Interface Quick Start
After you set up GroupWise WebAccess, see Section 16.6, “What’s Next,” on page 128 for additional
information that you might want to be aware of as you configure, maintain, and expand GroupWise
WebAccess.
113
16.1.2
GroupWise WebAccess Components
GroupWise WebAccess consists of four components: the browser-based WebAccess user interface
(desktop computer, tablet device, or mobile device), the WebAccess Application, the Post Office
Agent (POA), and the Document Viewer Agent (DVA).
WebAccess
Secure
Login
Web Browser
Internet
WebAccess
Application
Web Server
Post
Office
Agent
Document
Viewer
Agent
 WebAccess User Interface: The WebAccess user interface in web browsers gives users access to
their GroupWise mailboxes anywhere an Internet connection is available.
 WebAccess Application: The WebAccess Application, which resides on the web server,
provides the GroupWise WebAccess user interface. As users perform actions in WebAccess, the
WebAccess Application passes information between the web browser and the Post Office Agent.
 Post Office Agent: The POA receives user requests from the WebAccess Application, accesses
post offices and libraries to process the requests, and then passes information back to the
WebAccess Application.
 Document Viewer Agent: The DVA isolates the conversion process for attached document files.
The DVA can simultaneously convert multiple document files into HTML format. If it
encounters a problem converting a document file, the problem does not affect conversion of
other document files, nor does it affect the functioning of the WebAccess Application. Therefore,
GroupWise WebAccess users do not experience interruptions because of document files that fail
to convert into HTML. Document files that fail in the conversion process simply cannot be
viewed in WebAccess. The DVA is typically installed along with the POA.
16.1.3
WebAccess Security Requirements
The WebAccess Application can be configured to support the level of security you have established
for your Internet/intranet communication.
If you are not concerned about security issues (for example, you only plan to use the WebAccess
Application on a secured intranet), you can install the WebAccess Application to any web server that
provides access for your users and meets the requirements listed in Section 16.2, “GroupWise
WebAccess System Requirements,” on page 116.
If you plan to use the WebAccess Application to provide users with access to their mailboxes from
anywhere on the Internet (rather than only within a secured intranet), and you already have a
firewall in place to provide security, you have the following options for configuring the WebAccess
Application:
 Install the WebAccess Application inside your firewall and use a proxy service. See “WebAccess
with a Proxy Service” on page 115. This is the recommended configuration.
 Install the WebAccess Application on a web server outside your firewall, and install the POA
and the DVA on a server inside your firewall. See “WebAccess without a Proxy Service” on
page 115.
114
WebAccess with a Proxy Service
If your firewall includes a proxy service, you can install the WebAccess Application to a web server
inside your firewall. The POA and the DVA are located on a post office server, which is also inside the
firewall.
In this configuration, only the firewall server with the proxy service is located outside the firewall, as
shown in the following illustration.
WebAccess
Web
Browser
Web
Browser
Firewall
Secure
Login
Internet
Firewall Server
with Proxy
Service
WebAccess
Application
Post
Office
Agent
Web
Server
Document
Viewer
Agent
Network
Server
WebAccess without a Proxy Service
If your firewall does not provide a proxy service, you need to install the WebAccess Application to a
web server that is outside the firewall. The POA and the DVA are located on a post office server,
which is inside the firewall.
In this configuration, both the web server and the firewall server are located outside the firewall, as
WebAccess
Web
Browser
Web
Browser
Web
Browser
Secure
Login
Internet
WebAccess
Application
Web
Server
Firewall
Firewall
Server
Post
Office
Agent
Document
Viewer
Agent
Network
Server
The firewall must allow inbound IP packets to be sent from the web server to the IP address and port
of the POA (for example, 172.16.5.18:1677).
In addition, the firewall must allow outbound IP packets to be sent from the POA to the web server.
This requires all high ports (above 1023) to be open to outbound IP packets.
115
16.2
GroupWise WebAccess System Requirements
 Section 16.2.1, “Hardware and Operating System Requirements,” on page 116
 Section 16.2.2, “Web Server Requirements,” on page 116
 Section 16.2.3, “GroupWise Requirements,” on page 117
 Section 16.2.4, “User Requirements,” on page 117
16.2.1
 Any of the following server operating systems for the WebAccess Application:
Service Pack
 Adequate server disk space:
 Approximately 525 MB (shared with the Calendar Publishing Host Application and the
Monitor Application when they are installed on the same web server; varies by platform)
16.2.2
The web server that is supported for your operating system:
 OES 11 / SLES 11
Apache 2.2 plus:
 Tomcat 6
 ModProxy Module
116
 Tomcat 6
 ISAPI support
16.2.3
GroupWise Requirements
 One or more Post Office Agents (POAs) configured for SOAP and secure SSL connections
 One or more Document Viewer Agents (DVAs) configured to communicate with the POAs
16.2.4
User Requirements
 “WebAccess User Requirements” on page 117
 “WebAccess Mobile User Requirements” on page 117
WebAccess User Requirements
 Any of the following web browsers:
 Linux: Mozilla Firefox; Google Chrome
 Windows: Microsoft Internet Explorer 9 or later; Mozilla Firefox; Google Chrome
 Macintosh: The latest version of Safari for your version of Mac OS; Mozilla Firefox; Google
Chrome
 Microsoft Surface Pro tablet, with Windows 8 or later
 Any mobile device that supports Wireless Access Protocol (WAP) and has a microbrowser that
supports Hypertext Markup Language (HTML) 4.0 or later
WebAccess Mobile User Requirements
Any of the following tablet operating systems and tablets:
 Android 4.1, 5.0, or later, with Google Chrome, on any Android device
 Apple iOS 7.x, 8.x, or later, with Apple Safari
 Kindle Fire, with Amazon Silk
 RIM Tablet OS 2.1 or later, with Google Chrome, on the Blackberry Playbook
117
 Windows Mobile 8.0 or later Pro, with Microsoft Internet Explorer, on any Windows device (full
WebAccess, no template)
NOTE: On a Microsoft Surface Pro tablet, you can use WebAccess in any supported browser,
instead of using WebAccess Mobile.
16.3
Planning GroupWise WebAccess
Use the “GroupWise WebAccess Installation Worksheet” on page 129 to record the information
required to install the WebAccess Application.
Installation Worksheet organizes the information in the order in which you need it during
installation.
 Section 16.3.1, “Selecting the WebAccess Application Platform,” on page 118
 Section 16.3.2, “Gathering Web Server Information,” on page 118
 Section 16.3.3, “Determining the WebAccess Application’s Configuration,” on page 119
 Section 16.3.4, “Connecting the WebAccess Application with Supporting Agents,” on page 119
16.3.1
Selecting the WebAccess Application Platform
The WebAccess Application can be installed to a web server on Linux or Windows. See Section 16.2,
“GroupWise WebAccess System Requirements,” on page 116 for supported web servers.
GROUPWISE WEBACCESS APPLICATION INSTALLATION WORKSHEET
Under Web Server Platform, mark whether you plan to install the WebAccess Application to a Linux or
Windows web server.
16.3.2
Gathering Web Server Information
The WebAccess Application integrates with your web server to pass mailbox information gathered
by the POA to your web browser for display in WebAccess. The location of the WebAccess
Application files that are installed depends on the web server that it is being integrated with.
The default web server paths vary by platform:
118
Apache Web Server on OES 11:
Tomcat on OES 11:
/etc/opt/novell/httpd/conf.d
/var/opt/novell/tomcat6/webapps
Apache Web Server on SLES 11:
Tomcat on SLES 11:
/etc/apache2/conf.d
/usr/share/tomcat6/webapps
Microsoft Internet Information Server (IIS) on Windows:
Tomcat on Windows:
c:\inetpub\wwwroot
c:\novell\tomcat6\webapps
Under Web Server Information, select the type of web server where you plan to install the WebAccess
Application. Also specify the web server’s root directory.
On Windows, if the Internet Information Server services more than one website, specify the website where you
want to install the WebAccess Application.
16.3.3
Determining the WebAccess Application’s Configuration
WebAccess Application configuration information is stored in a configuration file (webacc.cfg). The
webacc.cfg file is located in the following folders:
Linux:
Windows:
/var/opt/novell/groupwise/webaccess
c:\novell\groupwise\webaccess
To change the WebAccess Application’s configuration, you must manually modify the webacc.cfg
file.
Under Configuration File Location, note the location of the webacc.cfg file for the platform where you are
installing WebAccess.
16.3.4
Connecting the WebAccess Application with Supporting Agents
The WebAccess Agent needs to communicate with a POA and a DVA.
Under POA Network Address, specify the IP address or DNS hostname of a POA that the WebAccess
Application can communicate with, along with that POA’s SOAP port. The default SOAP port for the POA is
7191.
Under DVA Network Address, specify the IP address or DNS hostname of a DVA that the WebAccess
Application can communicate with, along with that DVA’s TCP port. The default DVA port is 8301.
IMPORTANT: The POA that the WebAccess Application communicates with must be configured for
SOAP. A secure SSL connection between the POA and the WebAccess Application is highly
recommended.
For instructions on preparing the POA to work successfully with the WebAccess Application, see the
following sections in the GroupWise 2014 Administration Guide:
 “Supporting SOAP Clients”
 “Securing the Post Office with SSL Connections to the POA”
119
For instructions on preparing the DVA to work successfully with the WebAccess Application, see the
following sections in the GroupWise 2014 Administration Guide:
 “Multiple DVAs for WebAccess”
 “Installing the DVA”
16.4
Installing the GroupWise WebAccess Software
As you install the WebAccess software, use the GroupWise WebAccess Installation Worksheet that
you filled out in Section 16.3, “Planning GroupWise WebAccess,” on page 118 to provide the
required information.
 Section 16.4.1, “Linux: Installing the GroupWise
WebAccess Software,” on page 120
Preparing the Linux Server for GroupWise WebAccess
Installing the Linux WebAccess Software
GroupWise 2014 Administration Guide
 Section 16.4.2, “Windows: Installing the
GroupWise WebAccess Software,” on page 122
16.4.1
Preparing the Windows Server for GroupWise
WebAccess
Installing the Windows WebAccess Software
Linux: Installing the GroupWise WebAccess Software
 “Preparing the Linux Server for GroupWise WebAccess” on page 120
 “Installing the Linux WebAccess Software” on page 120
Preparing the Linux Server for GroupWise WebAccess
1 Ensure that the web server where you are installing the WebAccess Application meets the
system requirements listed in Section 16.2, “GroupWise WebAccess System Requirements,” on
page 116.
4 Ensure that the POA that the WebAccess Application will communicate with has SOAP enabled
on a secure SSL connection, as described in Section 16.3.4, “Connecting the WebAccess
Application with Supporting Agents,” on page 119.
5 Continue with Installing the Linux WebAccess Software.
Installing the Linux WebAccess Software
image:
./install.sh
120
7 Type 2 for GroupWise WebAccess, then press Enter to display the Actions list.
8 Type 1 for Install, then press Enter to install GroupWise WebAccess.
The WebAccess package is installed on the server. If any supporting packages are not available
on the server, the Installation Wizard automatically installs them from the operating system
media.
10 Type 2 for Configure, then press Enter to configure the WebAccess Application.
11 Follow the prompts to configure the WebAccess Application, using the following information
from the GroupWise WebAccess Installation Worksheet:
POA Network Address
DVA Network Address
Web Server Information
12 Press any key to exit WebAccess Configuration.
13 Exit the GroupWise Installation Wizard.
14 Verify the status of the DVA that you configured the WebAccess Application to communicate
with.
121
For instructions, see Chapter 14, “Working with the GroupWise Agents,” on page 91. For more
information about the DVA, see “Document Viewer Agent” in the GroupWise 2014 Administration
Guide.
15 Skip to Section 16.5, “Testing GroupWise WebAccess,” on page 125.
16.4.2
Windows: Installing the GroupWise WebAccess Software
 “Preparing the Windows Server for GroupWise WebAccess” on page 122
 “Installing the Windows WebAccess Software” on page 122
Preparing the Windows Server for GroupWise WebAccess
1 Ensure that the web server where you are installing the WebAccess Application meets the
system requirements listed in Section 16.2, “GroupWise WebAccess System Requirements,” on
page 116.
3 Ensure that the POA that the WebAccess Application will communicate with has SOAP enabled
on a secure SSL connection, as described in Section 16.3.4, “Connecting the WebAccess
Application with Supporting Agents,” on page 119.
4 Continue with Installing the Windows WebAccess Software.
Installing the Windows WebAccess Software
the installation.
122
3 Click GroupWise WebAccess.
4 Click Next to display the Web Server Information page.
The Installation Wizard provides diagrams that help you understand how the various
components interact with each other. Review the diagrams as you provide the requested
information.
5 Follow the prompts to configure the WebAccess Application, using the following information
from the GroupWise WebAccess Installation Worksheet:
POA Network Address
DVA Network Address
123
6 Click Next to display the Installation Summary.
7 Review the Installation Summary page, then click Install to install the WebAccess Application.
8 (Conditional) If prompts appear because your web server is running, decide whether you want
the Installation Wizard to stop your web server.
9 When the installation is complete, click Finish to exit the WebAccess Installation Wizard.
You can choose to have the Installation Wizard restart the web server for you.
Along with the WebAccess Application, the WebAccess Installation Wizard also installs Tomcat
6 to c:\novell\tomcat6, integrates it with your web server, and automatically starts it to
support the WebAccess Application.
11 Verify the status of the DVA that you configured the WebAccess Application to communicate
with.
For instructions, see Chapter 14, “Working with the GroupWise Agents,” on page 91. For more
information about the DVA, see “Document Viewer Agent” in the GroupWise 2014 Administration
Guide.
12 Continue with Testing GroupWise WebAccess.
124
16.5
Testing GroupWise WebAccess
After you have installed WebAccess, you should test it in the environments where you think that
your GroupWise users will typically use it.
 Section 16.5.1, “Testing WebAccess on a Workstation,” on page 125
 Section 16.5.2, “Testing WebAccess on a Tablet Device,” on page 126
 Section 16.5.3, “Testing the WebAccess Basic Interface on a Mobile Device,” on page 127
 Section 16.5.4, “Assisting Users with Login Problems,” on page 128
 Section 16.5.5, “Monitoring the WebAccess Application,” on page 128
16.5.1
Testing WebAccess on a Workstation
1 To access GroupWise WebAccess, use the following URL:
http://web_server_address/gw/webacc
Replace web_server_address with the IP address or DNS hostname of your web server. If the web
server uses SSL, use https rather than http.
2 Type your GroupWise user name in the User Name field and your GroupWise mailbox password
in the Password field.
3 (Optional) Click Settings, then select the interface language you want from the Language drop-
down list.
125
4 Click Login to display the GroupWise WebAccess main window.
5 Click Options
16.5.2
> Help for more information about using GroupWise WebAccess.
Testing WebAccess on a Tablet Device
1 To access GroupWise WebAccess on a tablet device such as an iPad, use the following URL:
or
(Conditional) If you have a tablet device that is not yet supported, but you want to see how well
the mobile interface works on your device, use the following URL:
http://web_server_address/gw/webacc?User.interface=mobile
126
3 (Optional) Tap Settings, then select the interface language you want from the Language drop-
down list.
4 Tap Login to display the GroupWise WebAccess main window.
5 Tap Options
16.5.3
> Help for more information about using GroupWise WebAccess on your iPad.
Testing the WebAccess Basic Interface on a Mobile Device
1 To access GroupWise WebAccess in the web browser on your mobile device, use the following
URL:
2 Follow the instructions in your mobile device’s documentation to add this URL to your Favorites
or Bookmarks so you do not need to type the URL every time you log in on your mobile device.
127
4 Tap Login to display the GroupWise WebAccess main window.
The appearance of the WebAccess basic interface varies depending on the size of the screen
where it is displayed.
For more information about using WebAccess on your mobile device, see the WebAccess Basic Interface
Quick Start (https://www.novell.com/documentation/groupwise2014/gw2014_qs_webaccbasic/data/
gw2014_qs_webaccbasic.html).
As an alternative to this limited interface, you can synchronize GroupWise data to your mobile
device using the GroupWise Mobility Service. For more information, see the GroupWise Mobility
Service website (http://www.novell.com/documentation/groupwisemobility2).
16.5.4
Assisting Users with Login Problems
The WebAccess Login page includes a Can’t log in link, which provides the following information to
WebAccess users by default:
If you have forgotten your GroupWise password, contact your local GroupWise
administrator.
For your convenience and for the convenience of your WebAccess users, you can customize the
information that is provided by the Can’t log in link. For setup instructions, see “Helping Users Who
Forget Their GroupWise Passwords” in the GroupWise 2014 Administration Guide.
16.5.5
Monitoring the WebAccess Application
You can monitor the WebAccess Application from your web browser. For more information, see
“Using the WebAccess Application Console” in the GroupWise 2014 Administration Guide.
16.6
What’s Next
You can further configure and maintain GroupWise WebAccess in the following ways:
Task
Scale GroupWise WebAccess to meet the needs of See “Scaling Your GroupWise WebAccess Installation.”
your users and environment
128
Control users’ access to GroupWise WebAccess
See “Managing User Access” and “Helping Users Who
Forget Their GroupWise Passwords.”
Configure the WebAccess Application
See “Configuring the WebAccess Application.”
Monitor the WebAccess Application
See “Monitoring the WebAccess Application.”
Control logging for the WebAccess Application
See “Using WebAccess Application Log Files.”
16.7
GroupWise WebAccess Installation Worksheet
Installation Wizard Field
Web Server Platform
 Linux
Value for Your GroupWise
System
Explanation
Section 16.3.1, “Selecting the
WebAccess Application Platform,”
on page 118
 Windows
POA Network Address
 IP address
Section 16.3.4, “Connecting the
WebAccess Application with
Supporting Agents,” on page 119
 SOAP port
(default 7191)
DVA Network Address
 IP address
Section 16.3.4, “Connecting the
WebAccess Application with
Supporting Agents,” on page 119
 TCP port
(default 8301)
OES 11
Section 16.3.2, “Gathering Web
Server Information,” on page 118
 Apache path
/etc/opt/novell/httpd/
conf.d
 Tomcat path
/var/opt/novell/
tomcat6/webapps
SLES 11
 Apache path
/etc/apache2/conf.d
 Tomcat path
/usr/share/tomcat6/
webapps
Windows
 Microsoft Internet Information
Server (IIS) for Windows
 Path to the web server’s root
directory
 Website
129
Configuration File Location
Linux
/var/opt/novell/
groupwise/webaccess
Windows
c:\novell\groupwise\
webaccess
130
System
Explanation
17
Setting Up the GroupWise Calendar
Publishing Host
17
The GroupWise Calendar Publishing (CalPub) Host publishes GroupWise users’ calendars to the
Internet, so that the calendars are readily available to colleagues who are not part of the GroupWise
system. The CalPub Host also returns free/busy schedule status to Internet colleagues who want to
set up appointments with GroupWise users. The free/busy search checks the main GroupWise
Calendar and personal calendars.
 Section 17.1, “GroupWise Calendar Publishing Host Overview,” on page 131
 Section 17.2, “GroupWise Calendar Publishing Host System Requirements,” on page 134
 Section 17.3, “Planning a GroupWise Calendar Publishing Host,” on page 135
 Section 17.4, “Installing the GroupWise Calendar Publishing Host,” on page 139
 Section 17.5, “Configuring GroupWise to Support the Calendar Publishing Host,” on page 145
 Section 17.6, “Testing GroupWise Calendar Publishing,” on page 150
 Section 17.8, “GroupWise Calendar Publishing Host Worksheets,” on page 153
17.1
GroupWise Calendar Publishing Host Overview
 Section 17.1.1, “GroupWise Calendar Publishing Host Functionality,” on page 131
 Section 17.1.2, “GroupWise Calendar Publishing Host Components,” on page 132
 Section 17.1.3, “GroupWise Calendar Publishing Host Security Requirements,” on page 132
17.1.1
GroupWise Calendar Publishing Host Functionality
The CalPub Host enables Internet users to view GroupWise users’ published calendars and to
retrieve free/busy information from their calendars to assist with scheduling available appointment
times. Internet users do not need login access to the GroupWise system in order to view published
calendars and obtain free/busy status. Information provided by the CalPub Host is publicly available
to Internet users everywhere.
For calendar publishing user functionality details, see the Calendar Publishing User Quick Start (https:/
/www.novell.com/documentation/groupwise2014/gw2014_qs_calpubuser/data/
gw2014_qs_calpubuser.html).
Setting Up the GroupWise Calendar Publishing Host
131
17.1.2
GroupWise Calendar Publishing Host Components
The CalPub Host includes three components: the CalPub Host Application, which connects to the
Internet through a web server, the Post Office Agent (POA), which connects to your GroupWise
system, and the GroupWise Administration Service, which provides authentication to the CalPub
Host Administration console.
Published
Calendar
No
Login
Web Browser
Internet
Calendar
Publishing
Host
Application
Web Server
Post
Office
Agent
GroupWise
Admin Service
 Calendar Publishing Host Application: The CalPub Host Application, which resides on the
web server, provides the browser interface for users across the Internet. As users request
calendar and free/busy information from GroupWise users, the CalPub Host Application passes
the information between the web browser and the POA.
 Post Office Agent: The POA receives user requests from the CalPub Host Application, accesses
post offices and mailboxes to process the requests, and then passes information back to the
CalPub Host Application in the form of ICS (Internet Calendaring and Scheduling) files and IFB
(Internet Free Busy) files. These files can be imported into GroupWise, Outlook, and Macintosh
iCal calendaring applications.
 GroupWise Admin Service: The CalPub Host has an Administration console for configuration
and management tasks. You can authenticate to the CalPub Host Admin console by using the
user name and password of any GroupWise administrator user.
17.1.3
GroupWise Calendar Publishing Host Security Requirements
The CalPub Host Application can be configured to support the level of security you have established
for your Internet/intranet communication.
If you are not concerned about security issues (for example, you only plan to use the CalPub Host
Application on a secured intranet), you can install the CalPub Host Application to any web server
that provides access for your users and meets the requirements listed in Section 17.2, “GroupWise
Calendar Publishing Host System Requirements,” on page 134.
If you plan to use the CalPub Host Application to provide calendar and free/busy information to
users anywhere on the Internet (rather than simply within a secured intranet), and you already have
a firewall in place to provide security, you have the following options for configuring the CalPub
Host Application:
 Install the CalPub Host Application inside your firewall and use a proxy service, as described in
“Calendar Publishing Host with a Proxy Service” on page 133. This is the recommended
configuration.
 Install the CalPub Host Application on a web server outside your firewall and have it
communicate with a POA through your firewall, as described in “Calendar Publishing Host
without a Proxy Service” on page 133.
132
Calendar Publishing Host with a Proxy Service
If your firewall includes a proxy service, you can install the CalPub Host Application to a web server
inside your firewall. The POA is located on a post office server, which is also located inside the
firewall.
Published
Calendar
Web
Browser
Web
Browser
Web
Browser
Firewall
No
Login
Internet
Calendar
Publishing
Host
Application
GroupWise
Admin Service
Web
Server
Firewall Server
with Proxy
Service
Post
Office
Agent
Calendar Publishing Host without a Proxy Service
If your firewall does not provide a proxy service, you need to install the CalPub Host Application to a
web server that is outside the firewall. The POA is located on a post office server, which is located the
firewall.
Published
Calendar
Web
Browser
Web
Browser
Web
Browser
No
Login
Internet
Calendar
Publishing
Host
Application
Web
Server
Firewall
Firewall
Server
Post
Office
Agent
GroupWise
Admin Service
The firewall must allow inbound IP packets to be sent from the web server to the POA’s internal or
external IP address and the calendar publishing port for the POA (for example, 172.16.5.18:7171). If
you are using an external IP address, all POAs that support calendar publishing must be configured
to use the same external IP address. For more information about external POA IP addresses, see
“Securing Client Access through an External Proxy Server” in the GroupWise 2014 Administration
Guide.
133
In addition, the firewall must allow outbound IP packets to be sent from the POA to the web server.
This requires all high ports (above 1023) to be open to outbound IP packets.
17.2
GroupWise Calendar Publishing Host System
Requirements
 Section 17.2.3, “Web Browser Requirements,” on page 135
17.2.1
 Any of the following server operating systems for the Calendar Publishing Host Application:
Service Pack
 Approximately 525 MB (shared with the WebAccess Application and the Monitor
Application when they are installed on the same web server; varies by platform)
 50 KB per published calendar
 50 KB per user for free/busy searching
17.2.2
 OES 11 / SLES 11
Apache 2.2 plus:
 Tomcat 6
 ModProxy Module
134
 Tomcat 6
 ISAPI support
17.2.3
Web Browser Requirements
Any of the following web browsers for the GroupWise Calendar Publishing Host user web pages and
the Calendar Publishing Host Administration console:
 Linux: Mozilla Firefox; Google Chrome
 Windows: Microsoft Internet Explorer 9 or later; Mozilla Firefox; Google Chrome
 Macintosh: The latest version of Safari for your version of Mac OS; Mozilla Firefox; Google
Chrome
17.3
Planning a GroupWise Calendar Publishing Host
Use the “GroupWise Calendar Publishing Host Worksheets” on page 153 to record the information
required to install and configure the CalPub Host Application.
installation.
 Section 17.3.1, “Selecting the Calendar Publishing Host Application Platform,” on page 136
 Section 17.3.2, “Gathering Web Server Information,” on page 136
 Section 17.3.3, “Choosing the Calendar Publishing Host Name,” on page 137
 Section 17.3.4, “Determining the URL of the Calendar Publishing Host,” on page 137
 Section 17.3.5, “Selecting a Calendar Publishing Host Administrator,” on page 138
 Section 17.3.6, “Connecting the Calendar Publishing Host to a POA,” on page 138
 Section 17.3.7, “Designing Your Calendar Browse List,” on page 138
 Section 17.3.8, “Selecting Calendar Publishing Settings,” on page 139
135
17.3.1
Selecting the Calendar Publishing Host Application Platform
The CalPub Host can be installed to a web server on Linux or Windows. See Section 17.2,
“GroupWise Calendar Publishing Host System Requirements,” on page 134 for supported web
servers.
GROUPWISE CALENDAR PUBLISHING HOST INSTALLATION WORKSHEET
Under Web Server Platform, mark whether you plan to install the CalPub Host Application to a Linux or
Windows web server.
17.3.2
Gathering Web Server Information
The CalPub Host Application integrates with your web server to pass calendar information gathered
by the Post Office Agent to your web browser for display. The location of the CalPub Application files
that are installed depends on the web server that it is being integrated with.
The default web server paths vary by platform:
Tomcat on OES 11:
Tomcat on SLES 11:
/etc/apache2/conf.d
Tomcat on Windows:
c:\inetpub\wwwroot
Under Web Server Information, select the type of web server where you plan to install the CalPub Host
Application. Also specify the web server’s root directory.
want to install the CalPub Host Application.
The CalPub Host needs the IP address and TCP port number of the web server so that they can
communicate.
GROUPWISE CALENDAR PUBLISHING HOST CONFIGURATION WORKSHEET
Under Calendar Publishing Host Configuration, list the IP address of the web server and the web server port
number (by default, 80).
136
17.3.3
Choosing the Calendar Publishing Host Name
You must provide a unique and descriptive name for the CalPub Host. The name might include the
platform or location of the CalPub Host, or perhaps the users it serves. You specify this name when
you install the CalPub Host Application and again when you configure it in the GroupWise Admin
console. The name must be specified identically in both places, including spacing and capitalization.
The CalPub Host name is stored in the calhost.cfg file, located in the following folders:
Linux:
Windows:
/var/opt/novell/groupwise/calhost
c:\novell\groupwise\calhost
Under Calendar Publishing Host Name, specify a unique name for this CalPub Host.
Under Calendar Publishing Host Configuration, list the name for the CalPub Host name again. Ensure that the
names are specified identically on both worksheets.
If desired, provide a helpful description of the CalPub Host.
17.3.4
Determining the URL of the Calendar Publishing Host
The CalPub Host uses the DNS hostname of the web server as part of its base URL.
http://web_server_address:port/gwcal
Replace web_server_address with the DNS hostname of the web server. Replace port with the port
number on which the CalPub Host communicates with the web server. The default port number is 80;
it does not need to be specified if your web server uses that default.
IMPORTANT: Select the URL carefully. This URL is disseminated by GroupWise users to their
Internet colleagues when they publish their personal calendars and free/busy information. If you
change the URL later, GroupWise users need to send updated information to Internet colleagues.
You might want to create a generic URL, such as http://gwcal.example.com/gwcal, and then
configure your network to redirect incoming traffic to the CalPub Host server.
Under Calendar Publishing Host Configuration, list the CalPub Host base URL (http://
web_server_address/gwcal).
You typically need only one CalPub Host in your GroupWise system. However, depending on the
size of your GroupWise system and the locations of your GroupWise users, you might need multiple
CalPub Hosts in various locations if some users experience slowness when accessing the initial
location.
137
17.3.5
Selecting a Calendar Publishing Host Administrator
The web-based CalPub Admin console is provided for additional configuration of the CalPub Host.
You must select at least one GroupWise user to access the Calpub Admin console. You might want to
select a GroupWise user who is already a GroupWise system administrator, domain administrator, or
post office administrator, but this is not required. Any GroupWise user can be a CalPub Host
administrator.
The CalPub administrator logs into the CalPub Admin console using the same user name and
password that is used for mailbox access.
Under Authentication Information, list at least one GroupWise user to serve as a CalPub Host administrator.
17.3.6
Connecting the Calendar Publishing Host to a POA
The CalPub Host connects to your GroupWise system through the POA of a post office. For initial
installation, you enable one POA for calendar publishing. As you roll out calendar publishing to your
GroupWise users, you must enable calendar publishing for the POA of every post office where users
publish calendars and free/busy information.
The initially selected POA must be configured to communicate with the CalPub Host. The POA
server’s IP address or DNS hostname is required, along with a calendar publishing port. The default
calendar publishing port is 7171.
Under Post Office Agent Information, specify the IP address or DNS hostname of the POA that will
communicate with the CalPub Host, along with the calendar publishing port number. The default calendar
publishing port is 7171.
Under Calendar Publishing Post Office, transfer the IP address or DNS hostname of the POA, along with the
calendar publishing port from the Installation Worksheet to the Configuration Worksheet. You need this
information during installation and during configuration.
17.3.7
Designing Your Calendar Browse List
The CalPub Host collects a list of published calendars for Internet users to browse and select from at
the following URL:
http://web_server_address/gwcal/calendar
138
However, by default, no calendars are displayed in this calendar browse list. You can handle the
calendar browse list in three different ways:
 Do not provide a calendar browse list.
Users need to notify Internet colleagues by email of the URL to access their published calendars.
 Use the calendar browse list only for calendars of general corporate interest.
If you want to have such a corporate browse list, you restrict which users can list calendars on
the browse list, by allowing only a few specific users who manage the corporate calendars to
publish to the calendar browse list.
 Allow most, if not all, users to publish their personal calendars on the calendar browse list.
This open approach to the calendar browse list makes users’ published calendars easily
accessible to anyone who knows the URL of the calendar browse list for your GroupWise
system.
Under Calendar Browse List, mark whether you want to enable the calendar browse list, and if so, what
kind (corporate or open).
17.3.8
Selecting Calendar Publishing Settings
After you have set up the CalPub Host, you can configure how you want it to work for your
GroupWise users. The following settings are available in the CalPub Admin console:
 Enable Calendar Publishing: Lets users publish personal GroupWise calendars on the Internet.
When calendar publishing is enabled, users of the GroupWise client and GroupWise WebAccess
can right-click a personal calendar, and then click Publish to select options for publishing a
personal calendar.
 Enable Rules To Move Items to a Published Calendar: Allows users to create rules that move
specific items to a published GroupWise calendar. Rules are disabled by default.
 Enable Publish Free/Busy Search: Allows users to make their appointment information
available to external users, so that external users can perform Free/Busy Searches on users'
GroupWise calendars. Free/Busy searching is disabled by default. Free/busy publishing can be
enabled even if no Calendar Publishing Host has been selected.
 Enable Subscribe to Calendar: Allows users to subscribe to Internet calendars that are updated
on a regular basis, such as calendars for sporting events. Calendar subscription is disabled by
default. Calendar subscription can be enabled even if no Calendar Publishing Host has been
selected.
Under Calendar Publishing Options, mark the options you want to enable for the CalPub Host.
17.4
Installing the GroupWise Calendar Publishing Host
As you set up the CalPub Host, use the GroupWise Calendar Publishing Host Worksheets that you
filled out in Section 17.3, “Planning a GroupWise Calendar Publishing Host,” on page 135 to provide
the required information.
139
 Section 17.4.1, “Linux: Installing the Calendar
Publishing Host Software,” on page 140
Preparing the Linux Server for the Calendar Publishing
Host
Installing the Linux Calendar Publishing Host Software
GroupWise 2014 Administration Guide before you
work with the GroupWise agents on Linux.
 Section 17.4.2, “Windows: Installing the Calendar Preparing the Windows Server for the Calendar
Publishing Host Software,” on page 142
17.4.1
Publishing Host
“Installing the Windows Calendar Publishing Host
Software” on page 142
Linux: Installing the Calendar Publishing Host Software
 “Preparing the Linux Server for the Calendar Publishing Host” on page 140
 “Installing the Linux Calendar Publishing Host Software” on page 140
Preparing the Linux Server for the Calendar Publishing Host
1 Ensure that the web server where you are installing the CalPub Host Application meets the
system requirements listed in Section 17.2, “GroupWise Calendar Publishing Host System
Requirements,” on page 134.
4 Continue with Installing the Linux Calendar Publishing Host Software.
Installing the Linux Calendar Publishing Host Software
image:
./install.sh
140
7 Type 3 for Calendar Publishing Host, then press Enter to display the Actions list.
8 Type 1 for Install, then press Enter to install the GroupWise Calendar Publishing Host.
The CalPub Host package is installed on the server. If any supporting packages are not available
media.
10 Type 2 for Configure, then press Enter to configure the CalPub Host Application
11 Follow the prompts to configure the CalPub Host Application, using the following information
from the Calendar Publishing Host Installation Worksheet:
Calendar Publishing Host Name
Post Office Agent Information
12 When the installation is finished, review the instructions for configuring the Calendar
Publishing Host.
13 Press any key to exit CalPub Host Configuration.
141
15 Skip to “Configuring the Calendar Publishing Host in the GroupWise Admin Console” on
page 146.
17.4.2
Windows: Installing the Calendar Publishing Host Software
 “Preparing the Windows Server for the Calendar Publishing Host” on page 142
 “Installing the Windows Calendar Publishing Host Software” on page 142
Preparing the Windows Server for the Calendar Publishing Host
1 Ensure that the web server where you are installing the CalPub Host Application meets the
system requirements listed in Section 17.2, “GroupWise Calendar Publishing Host System
Requirements,” on page 134.
3 Continue with Installing the Windows Calendar Publishing Host Software.
Installing the Windows Calendar Publishing Host Software
the installation.
142
3 Click GroupWise Calendar Publishing Host.
4 Click Next to display the Calendar Publishing Host Name page.
information.
5 Follow the prompts to configure the CalPub Host Application, using the following information
from the Calendar Publishing Host Installation Worksheet:
143
6 Click Next to display the Installation Summary.
8 When the installation is finished, review the instructions for configuring the Calendar
Publishing Host.
144
10 When the installation is complete, click Finish to exit the Calendar Publishing Host Installation
Wizard.
You can choose to have the Installation Wizard restart the web server for you.
Along with the Calendar Publishing Host Application, the Calendar Publishing Host
Installation Wizard also installs Tomcat 6 to c:\novell\tomcat6, integrates it with your web
server, and automatically starts it to support the Calendar Publishing Host Application.
12 Continue with Configuring GroupWise to Support the Calendar Publishing Host.
17.5
Configuring GroupWise to Support the Calendar Publishing
Host
After your install the Calendar Publishing Host Application, additional configuration is still
required.
 Section 17.5.1, “Configuring the Calendar Publishing Host in the GroupWise Admin Console,”
on page 146
 Section 17.5.2, “Enabling Calendar Publishing,” on page 147
 Section 17.5.3, “Configuring a POA for Calendar Publishing,” on page 148
 Section 17.5.4, “Setting Up Calendar Publishing Administration,” on page 149
 Section 17.5.5, “Using the Published Calendar Browse List,” on page 150
145
17.5.1
Configuring the Calendar Publishing Host in the GroupWise Admin
Console
Use the information under Calendar Publishing Host Configuration and Calendar Browse List on your
Calendar Publishing Host Configuration Worksheet as you configure the CalPub Host.
1 In the GroupWise Admin console, click System > Calendar Publishing, then click New.
2 Fill in the fields to configure the CalPub Host, using the following information from the
Calendar Publishing Host Configuration Worksheet
Name:
URL:
Description:
Address:
Port:
IMPORTANT: The name that you specify in the GroupWise Admin console must be the
identical name that you specified during installation, including spacing and capitalization, as
described in Section 17.3.3, “Choosing the Calendar Publishing Host Name,” on page 137.
If you decide that you want to use a different name after you have already installed the CalPub
Host Application, you must reinstall the software, and then specify the identical name during
the reinstallation that you specify in the GroupWise Admin console.
146
3 Click OK to save the CalPub Host configuration information.
4 If you want to allow users to add their published calendars to the calendar browse list as the
default for your GroupWise system, select Enable Publishing of Calendars to the Browse List.
or
If you want to set up a corporate calendar browse list or provide no calendar browse list, leave
Enable Publishing of Calendars to the Browse List deselected.
5 Click OK when you are finished.
6 Continue with Enabling Calendar Publishing.
17.5.2
Enabling Calendar Publishing
Use the information under Calendar Publishing Options on your GroupWise Calendar Publishing Host
Worksheets as you enable calendar publishing.
1 In the GroupWise Admin console, click Post Offices, then click the name of the post office where
you want to enable calendar publishing.
For convenience in testing your Calendar Publishing Host setup, you might want to start with
your post office.
147
2 Click Client Options > Calendar > Web Calendar.
As you roll out calendar publishing, you can use Client Options to enable it at the domain, post
office, and user level.
3 Select a Calendar Publishing Host from the drop-down list.
4 Set the Web Calendar options as you planned on your Calendar Publishing Host Installation
Worksheet.
5 Click OK to save the Web Calendar settings, then click Close.
6 Restart Tomcat:
OES 11:
SLES 11:
Windows
rcnovell-tomcat6 restart
rctomcat6 restart
1. At the Windows server, click Start > Administrative Tools > Services.
2. Right-click Tomcat 6, then click Restart.
7 Continue with Configuring a POA for Calendar Publishing.
17.5.3
Configuring a POA for Calendar Publishing
After calendar publishing is enabled, the POA can look up calendar information and return it to the
CalPub Host in the form of ICS (Internet Calendaring and Scheduling) or IFB (Internet Free Busy)
files. Internet users can import these files into GroupWise, Outlook, and Macintosh iCal calendaring
applications.
1 In the GroupWise Admin console, click Post Office Agents, then click the name of the POA that
you want to configure for calendar publishing.
2 Click Agent Settings, then scroll down to the Calendar Publishing section.
148
3 Select Enabled.
4 (Optional) Decrease the number in the Max Calendar Publishing Threads field as needed.
The default maximum number of calendar publishing threads is 4. By default, the POA creates 2
calendar publishing threads and adds more as needed. However, you cannot set the maximum
higher than 4. The default setting is highly recommended.
5 Click OK to save the calendar publishing configuration settings.
6 As you roll out calendar publishing to your GroupWise users, enable calendar publishing on the
POA for each post office where users will publish calendars and free/busy information.
To determine which POAs have been enabled for calendar publishing, see “Viewing Calendar
Publishing Status in the POA Console” in the GroupWise 2014 Administration Guide.
7 Continue with Setting Up Calendar Publishing Administration.
17.5.4
Setting Up Calendar Publishing Administration
After calendar publishing has been enabled and the POA is communicating with the CalPub Host,
you use the CalPub Admin console to monitor the CalPub Host and to make configuration changes
as needed. Any GroupWise administrator user can access the CalPub Host Admin console. Use the
information under Authentication Information on your Calendar Publishing Host Configuration
Worksheet as you set up Calendar Publishing Host administration.
1 Edit the calhost.cfg file in the following folder:
Linux:
Windows:
/var/opt/novell/groupwise/calhost
c:\Novell\GroupWise\calhost
2 Search to find the following line:
#Admin.WebConsole.enable=false
3 Remove the pound sign (#) to activate the setting.
4 Change false to true.
6 Restart Tomcat:
OES 11:
SLES 11:
Windows
rcnovell-tomcat6 restart
rctomcat6 restart
1. At the Windows server, click Start > Administrative Tools > Services.
2. Right-click Tomcat 6, then click Restart.
7 Display the CalPub Host Admin console:
http://server_network_address/gwcal/admin
149
8 Log in to the CalPub Host Admin console using any GroupWise administrator user name and
password.
For more information about the CalPub Host Admin console, see “Using the CalPub Admin
Console” in the GroupWise 2014 Administration Guide.
9 (Conditional) If additional GroupWise administrators need to access the CalPub Admin console,
notify them of the URL to access.
10 Continue with Using the Published Calendar Browse List.
17.5.5
Using the Published Calendar Browse List
If you selected Enable Publishing of Calendars to the Browse List as your GroupWise system default, skip
to Section 17.6, “Testing GroupWise Calendar Publishing,” on page 150.
If you are planning to implement a corporate calendar browse list in the future, you can enable
publishing of calendars to the browse list for yourself for testing purposes.
1 Browse to and right-click your User object, then click Properties.
2 Click GroupWise > Calendar Publishing.
3 Select Override, then select Enable Publishing of Calendars to the Browse List.
This gives you the right to add your calendars to the calendar browse list so that you can test the
setup of the Calendar Publishing Host.
4 Continue with Testing GroupWise Calendar Publishing.
17.6
Testing GroupWise Calendar Publishing
Now that you have set up a Calendar Publishing Host, you can test it by doing the following:
 Section 17.6.1, “Publishing a Personal Calendar,” on page 151
 Section 17.6.2, “Displaying the Browse List of Calendars,” on page 151
 Section 17.6.3, “Publishing Free/Busy Information,” on page 152
150
17.6.1
Publishing a Personal Calendar
1 In the GroupWise client, create and populate a personal calendar, as described in “Creating a
Personal Calendar” in the GroupWise 2014 Client User Guide.
2 Right-click the personal calendar, then click Publish.
3 Select Publish This Calendar.
For more information, see “Publishing Personal Calendars on the Internet” in the GroupWise
2014 Client User Guide.
This feature is also available in GroupWise WebAccess, as described in “Publishing Personal
Calendars on the Internet” in the GroupWise 2014 WebAccess User Guide.
For more information, see the GroupWise 2014 Calendar Publishing Host User Quick Start.
4 Click Send Publish Location, then address and send the resulting message, which provides the
URL from which Internet colleagues can obtain your calendar information.
The URL has the following format:
http://calpubhost_server/gwcal/freebusy/user_name@internet_domain
5 Click OK to publish the selected personal calendar.
6 Check your mailbox for the notification sent by the Calendar Publishing Host.
7 Continue with Displaying the Browse List of Calendars.
17.6.2
Displaying the Browse List of Calendars
1 Display the following URL:
http://web_server_address/gwcal/calendar
151
Your newly published personal calendar should appear on the list.
2 Click your calendar to view it in its published format.
This assures you that your calendar is available for access by users across the Internet.
17.6.3
Publishing Free/Busy Information
1 In the GroupWise client, click Tools > Options.
2 Click Calendar > Free/Busy.
3 Click Send Free/Busy Publish Location, then address and send the resulting message, which
provides the URL from which Internet colleagues can obtain your free/busy information.
4 Click OK, then click Close.
5 Check your mailbox for the notification sent by the Calendar Publishing Host.
6 Continue with What’s Next.
17.7
What’s Next
You can further configure and maintain the Calendar Publishing Host in the following ways:
152
Task
Using the CalPub Host Admin console to change
the configuration of the CalPub Host
See “Configuring the Calendar Publishing Host.”
Changing the appearance of the calendar browse
list to represent your company
See “Customizing the Calendar Publishing Host Logo.”
Restricting the posted list of calendars to those of
corporate importance
See “Creating a Corporate Calendar Browse List.”
Monitoring the CalPub Host at the POA console
and through CalPub Host log files
See “Monitoring Calendar Publishing.”
17.8
GroupWise Calendar Publishing Host Worksheets
 Section 17.8.1, “Calendar Publishing Host Installation Worksheet,” on page 153
 Section 17.8.2, “Calendar Publishing Host Configuration Worksheet,” on page 154
17.8.1
Calendar Publishing Host Installation Worksheet
Web Server Platform
 Linux
 Windows
System
Explanation
Section 17.3.1, “Selecting the
Application Platform,” on
page 136
Section 17.3.4, “Determining
the URL of the Calendar
Publishing Host,” on page 137
Section 17.3.6, “Connecting
the Calendar Publishing Host
to a POA,” on page 138
 POA network address
 IP address
 DNS hostname
 Calendar publishing port
(default 7171)
OES 11
Server Information,” on
page 136
 Apache path
conf.d
 Tomcat path
/var/opt/novell/tomcat6/
webapps
SLES 11
page 136
 Apache path
/etc/apache2/conf.d
 Tomcat path
153
System
Explanation
page 136
Windows
directory
 Website
17.8.2
Calendar Publishing Host Configuration Worksheet
Configuration Field
Configuration
 Name
 URL
 Description
 IP address
 TCP port
Calendar Browse List
 Yes
System
Explanation
Section 17.3.3, “Choosing the
Name,” on page 137
Section 17.3.4, “Determining
the URL of the Calendar
Publishing Host,” on page 137
page 136
Section 17.3.7, “Designing
Your Calendar Browse List,” on
page 138
 Corporate (restricted)
 Open
 No
Calendar Publishing Options
 Enable calendar publishing
 Enable rules to move items to a
published calendar
 Enable subscribe to calendar
 Enable publish free/busy searches
154
Section 17.3.8, “Selecting
Calendar Publishing Settings,”
on page 139
Configuration Field
Calendar Publishing Post Office
 Name
System
Explanation
Section 17.3.6, “Connecting
the Calendar Publishing Host
to a POA,” on page 138
 POA network address
 IP address
 DNS hostname
 Calendar publishing port
(default 7171)
Authentication Information
 GroupWise user name
Section 17.3.5, “Selecting a
Administrator,” on page 138
155
156
18
Setting Up GroupWise Monitor
18
GroupWise Monitor is a monitoring and management tool that allows you to monitor GroupWise
agents from any location where you are connected to the Internet and have access to a web browser.
Some agent administration can also be performed from your web browser if the agent console is
password protected.
 Section 18.1, “GroupWise Monitor Overview,” on page 157
 Section 18.2, “GroupWise Monitor System Requirements,” on page 160
 Section 18.3, “Planning GroupWise Monitor,” on page 162
 Section 18.4, “Installing the GroupWise Monitor Software,” on page 165
 Section 18.5, “Testing GroupWise Monitor,” on page 172
 Section 18.6, “GroupWise Monitor Installation Worksheets,” on page 174
IMPORTANT: If you are installing GroupWise Monitor in a clustered server environment, see the
“Clustering” in the GroupWise 2014 Interoperability Guide before you install Monitor.
18.1
GroupWise Monitor Overview
 Section 18.1.1, “GroupWise Monitor Functionality,” on page 157
 Section 18.1.2, “GroupWise Monitor Components,” on page 158
 Section 18.1.3, “One Monitor Server versus Two,” on page 158
 Section 18.1.4, “Monitor Security Requirements,” on page 159
 Section 18.1.5, “Monitor and the GroupWise High Availability Service on Linux,” on page 160
18.1.1
GroupWise Monitor Functionality
GroupWise Monitor is a monitoring and management tool that allows you to monitor GroupWise
agents from any location where you are connected to the Internet and have access to a web browser.
Some agent administration can also be performed from your web browser. Monitor provides more
detail than is provided on the System page in the GroupWise Admin console.
You can install Monitor on either Linux or Windows. Either version can monitor agents on both
Linux and Windows. Depending on the installation platform, two or three different monitoring
environments are available:
 Monitor Web Console: The Monitor Web console, provided by the Monitor Application, takes
advantage of your web server’s capabilities to make agent status information available to you
when you are outside your firewall.
157
 Monitor Agent Console: The Monitor Agent console, provided by the Monitor Agent itself, can
be used only behind your firewall, but it provides capabilities that are not available in the main
Monitor Web console. This section focuses on using the full-featured Monitor Agent console.
NOTE: The Monitor Web console and the Monitor Agent console are available on both Linux
and Windows because they are browser based.
 Windows Monitor Agent Server Console: The Windows Monitor Agent server console is
available only on the Windows server where the Windows Monitor Agent runs and only if you
run the Monitor Agent as an application, rather than as a Windows service. All agent
configuration tasks can be performed at the Windows Monitor Agent server console, but some
reports are not available.
Specific differences in functionality between the three Monitor consoles are summarized in
“Comparing the Monitor Consoles” in the GroupWise 2014 Administration Guide.
18.1.2
GroupWise Monitor Components
GroupWise Monitor consists of two components: the Monitor Agent and the Monitor Application.
Internal
Monitor
Console
Web
Browser
External
Monitor
Console
Post Office
Agents
Monitor
Application
Message Transfer
Agents
Web Browser
Internet
Web Server
Monitor
Agent
Internet
Agents
 Monitor Agent: The Monitor Agent continuously polls the POA, MTA, and GWIA; gathers
status information from them; and displays the status information in the Monitor Agent console.
The Monitor Agent also services requests for agent status information from the Monitor
Application, which displays the Monitor Web console.
 Monitor Application: The Monitor Application extends the capability of your web server so that
agent status information can be displayed in your web browser in the Monitor Web console.
18.1.3
One Monitor Server versus Two
The Monitor Agent and the Monitor Application can run together on a Linux server or a Windows
server. The server where they run together must be a web server because the Monitor Application is
installed into the web server.
The Monitor Agent and the Monitor Application can also run on different servers. The security issues
discussed in Monitor Security Requirements might determine whether you run the Monitor Agent on
the same server with the web server and the Monitor Application.
158
18.1.4
Monitor Security Requirements
GroupWise Monitor can be configured to support the level of security you have established for your
Internet/intranet communication.
If you are not concerned about security issues (for example, you plan to use Monitor only on a
secured intranet), you can install the Monitor components to any servers that provide access for your
GroupWise administrators and that meet the requirements listed in Section 18.2, “GroupWise
Monitor System Requirements,” on page 160.
If you plan to use Monitor to provide GroupWise administrators with access to your GroupWise
system from anywhere on the Internet (rather than simply within a secured intranet), and you
already have a firewall in place to provide security, you have the following options for configuring
Monitor:
 Install both Monitor components inside your firewall and use a proxy service. See “Configuring
Monitor with a Proxy Service” on page 159. This is the recommended configuration.
 Install the Monitor Application to a web server outside your firewall and the Monitor Agent on a
server inside your firewall. See “Configuring Monitor without a Proxy Service” on page 160.
Configuring Monitor with a Proxy Service
If your firewall includes a proxy service, you can install the Monitor Application to a web server
inside your firewall, and the Monitor Agent to another server inside the firewall.
External
Monitor
Console
Web
Browser
Web
Browser
Internal
Monitor
Console
Web
Browser
Web
Browser
Firewall
Post Office
Agents
Monitor
Application
Message Transfer
Agents
Internet
Firewall Server
with Proxy
Service
Web
Server
Network
Server
with Monitor
Agent
Internet
Agents
If desired, the Monitor Agent can also be installed to the web server rather than to a separate server,
as described in Section 18.1.3, “One Monitor Server versus Two,” on page 158.
159
Configuring Monitor without a Proxy Service
If your firewall does not provide a proxy service, you need to install the Monitor Application to a
web server that is outside the firewall. However, the Monitor Agent requires direct access to a
GroupWise domain folder, so it needs to be installed to a server that is located within the firewall. It
should be installed to the same server where a domain folder is located.
External
Monitor
Console
Web
Browser
Web
Browser
Internal
Monitor
Console
Web
Browser
Web
Browser
Post Office
Agents
Firewall
Monitor
Application
Message Transfer
Agents
Internet
Web
Server
Firewall Server
Network
Server
with Monitor
Agent
Internet
Agents
The firewall must allow inbound IP packets to be sent from the web server to the IP address and port
number of the Monitor Agent (for example, 172.16.5.18:8200).
In addition, the firewall must allow outbound IP packets to be sent from the Monitor Agent to the
web server. This requires all high ports (above 1023) to be open to outbound IP packets.
18.1.5
Monitor and the GroupWise High Availability Service on Linux
The Monitor Agent can be used with the GroupWise High Availability service (gwha), which runs on
Linux, to automatically restart GroupWise agents when they stop unexpectedly. For setup
instructions, see “Automatically Restarting the Linux GroupWise Agents with the GroupWise High
Availability Service” on page 97.
There is no GroupWise High Availability service on Windows. Windows includes a mechanism for
restarting services automatically when they stop unexpectedly. For more information, see
“Clustering” in the GroupWise 2014 Interoperability Guide.
18.2
GroupWise Monitor System Requirements
 Section 18.2.3, “Web Browser Requirements,” on page 162
160
18.2.1
 x86-64 processor for the Monitor Agent
 x86-64 or x86-32 processor for the Monitor Application
 Any of the following server operating systems for the Monitor Agent and the Monitor
Application:
Service Pack
 Approximately 40 MB for the Monitor Agent (varies by platform)
 Approximately 525 MB for the Monitor Application (shared with the WebAccess
Application and the Calendar Publishing Host Application when they are installed on the
same web server; varies by platform)
18.2.2
 OES 11 / SLES 11
Apache 2.2 plus:
 Tomcat 6
 ModProxy Module
 Tomcat 6
161
 ISAPI support
18.2.3
Web Browser Requirements
Any of the following web browsers for the Monitor console:
 Linux: Mozilla Firefox
 Windows: Microsoft Internet Explorer 10 or later; Mozilla Firefox
 Macintosh: Mozilla Firefox
18.3
Planning GroupWise Monitor
Use the “GroupWise Monitor Installation Worksheets” on page 174 to record your decisions about
how to install GroupWise Monitor.
installation.
 Section 18.3.1, “Deciding Where to Install the GroupWise Monitor Components,” on page 162
 Section 18.3.2, “Determining the Monitor Agent’s Configuration,” on page 164
 Section 18.3.3, “Determining the Monitor Application’s Configuration,” on page 165
18.3.1
Deciding Where to Install the GroupWise Monitor Components
After reviewing Section 18.1, “GroupWise Monitor Overview,” on page 157 and the system
requirements listed in Section 18.2, “GroupWise Monitor System Requirements,” on page 160, plan
where you want to install the Monitor components in your system.
 “Monitor Agent Server” on page 162
 “Web Server” on page 163
Monitor Agent Server
The Monitor Agent runs on Linux and Windows. On Linux, the Monitor Agent runs as a daemon. On
Windows, the Monitor Agent runs as a Windows service or as an application. When the Monitor
Agent runs as an application, it has a user interface on the Windows server. When it runs as a
Windows service, it does not.
If you want to install the Monitor Agent and the Monitor Application to the same server, you can
install them at the same time. If you want to install them to different servers, you must run the
Monitor Installation program twice, once for each server. For example, you might want to install the
Monitor Application on Linux for use with a Linux web server, but you might want to install the
Monitor Agent on Windows so that you can use its server console, which is not available on Linux.
162
The Monitor Agent needs to communicate with an MTA. If possible, install the Monitor Agent on the
same server where a domain and MTA are already located. If you want to install the Monitor Agent
on its own server, consider creating a domain on that server specifically for helping the Monitor
Agent communicate with the rest of your GroupWise system.
The installation folder for the Monitor Agent depends on the platform:
Linux:
Windows:
The Linux Monitor Agent is automatically installed to /opt/novell/groupwise/agents.
The default installation directory is c:\Program Files\Novell\GroupWise Monitor.
On Windows, you can specify a different directory during installation. On Linux, you cannot.
GROUPWISE MONITOR AGENT INSTALLATION WORKSHEET
Under Agent Software Platform, mark the platform (Linux or Windows) where you plan to install the Monitor
Agent.
Under Server Information, specify the directory on the Linux or Windows server where you plan to install the
Monitor Agent software.
Web Server
The Monitor Application can be installed to a web server on Linux or Windows.
GROUPWISE MONITOR APPLICATION INSTALLATION WORKSHEET
Under Web Server Platform, mark whether you plan to install the Monitor Application to a Linux or Windows
web server.
The Monitor Application integrates with your web server to pass agent status information gathered
by the Monitor Agent to your web browser for display in the Monitor web console. The location of
the Monitor Application files that are installed depends on the web server that it is being integrated
with. The default web server paths vary by platform:
Tomcat on OES 11:
Tomcat on SLES 11:
/etc/apache2/conf.d
Tomcat on Windows:
c:\inetpub\wwwroot
GROUPWISE MONITOR APPLICATION INSTALLATION WORKSHEET
Under Web Server Information, select the type of web server you want to use with Monitor, and specify the
directory path to the web server root directory.
want to install the Monitor Application.
163
18.3.2
Determining the Monitor Agent’s Configuration
As you install the Monitor Agent, you are prompted to supply the configuration information:
 Monitor Agent Network Address
 Domain Folder
Monitor Agent Network Address
The Monitor Agent communicates with the Monitor Application and with monitored agents by way
of TCP/IP.
Under Server Information, record the IP address or DNS hostname of the Linux or Windows server where you
plan to install the Monitor Agent software. Use the default port number of 8200 unless that number is already in
use on that server.
If you are installing the Monitor Application on a different server from where you are installing the Monitor
Agent, record the same information under Monitor Agent Information on the GroupWise Monitor Agent
Installation Worksheet.
Domain Folder
The Monitor Agent can gather information about the locations of GroupWise agents to monitor by
reading from a domain database. Using the gathered information, the Monitor Agent can display a
list of monitored agents when you start it for the first time.
Under Domain Location, specify the path to a domain folder where an MTA is running.
If the domain is located on a different server from where you are installing the Monitor Agent, specify the IP
address or DNS hostname of the domain server.
Service vs. Application (Windows Only)
On Windows, you can choose to install the Monitor Agent as a Windows service or an application.
When you install the Monitor Agent as an application, it displays a Monitor Agent console on the
server where it runs. You can start the Windows Monitor Agent on the Windows Start menu, or you
can create a desktop icon for it.
When you install the Monitor Agent as a service, it does not display a server console. You manage it
by using the Windows Services administrative tool.
Under Windows Installation Option, mark Service or Application.
164
18.3.3
Determining the Monitor Application’s Configuration
Monitor Application configuration information is stored in a configuration file (gwmonitor.cfg),
located in the following directories:
Linux:
Windows:
/var/opt/novell/groupwise/monitor
c:\novell\groupwise\gwmonitor
The default configuration information is sufficient for an initial Monitor Application installation. For
more information about configuring the Monitor Application, see “Configuring the Monitor
Application” in the GroupWise 2014 Administration Guide after you have installed the Monitor
Application.
18.4
Installing the GroupWise Monitor Software
As you install the Monitor software, use the GroupWise Monitor Installation Worksheets that you
filled out in Section 18.3, “Planning GroupWise Monitor,” on page 162 to provide the required
information.
 Section 18.4.1, “Linux: Installing the GroupWise
Monitor Software,” on page 165
Preparing the Linux Server for GroupWise Monitor
Installing and Configuring the Linux Monitor Agent
Installing and Configuring the Linux Monitor
Application
Starting the Linux Monitor Agent
GroupWise 2014 Administration Guide.
 Section 18.4.2, “Windows: Installing the
GroupWise Monitor Software,” on page 169
Preparing the Windows Server for GroupWise Monitor
Installing the Windows GroupWise Monitor Software
Starting the Windows Monitor Agent
18.4.1
Linux: Installing the GroupWise Monitor Software
 “Preparing the Linux Server for GroupWise Monitor” on page 165
 “Installing and Configuring the Linux Monitor Agent” on page 166
 “Installing and Configuring the Linux Monitor Application” on page 167
 “Starting the Linux Monitor Agent” on page 168
Preparing the Linux Server for GroupWise Monitor
1 Ensure that the server where you are installing the Monitor Agent meets the system
requirements listed in Section 18.6, “GroupWise Monitor Installation Worksheets,” on page 174.
2 Ensure that the web server where you are installing the Monitor Application meets the system
requirements listed in Section 18.2.2, “Web Server Requirements,” on page 161.
165
4 Ensure that the firewall on the server has the ports open that are used by the Monitor Agent and/
or the Monitor Application and the web server.
5 Continue with Installing and Configuring the Linux Monitor Agent.
Installing and Configuring the Linux Monitor Agent
image:
./install.sh
7 Type 4 for GroupWise Monitor Agent, then press Enter to display the Actions list.
8 Type 1 for Install, then press Enter to install the Monitor Agent.
The Monitor Agent package is installed on the server. If any supporting packages are not
available on the server, the Installation Wizard automatically installs them from the operating
system media.
166
During the installation, any other GroupWise agents on the server are stopped and then started
again after the Monitor software has been installed.
9 Type 2 for Configure, then press Enter to configure the Monitor Agent.
10 Follow the prompts to configure the Monitor Agent, using the following information from the
GroupWise Monitor Agent Installation Worksheet:
Domain Directory Path
11 Type 1 for Yes, then press Enter, to configure the Monitor Agent to automatically start when the
server restarts.
IMPORTANT: The Monitor Agent must be running in order for the GroupWise High
Availability Service (gwha) to automatically restart the GroupWise agents if they stop
unexpectedly. For more information, see “Automatically Restarting the Linux GroupWise
Agents with the GroupWise High Availability Service” on page 97.
12 Press any key to exit the Monitor Agent Configuration.
13 Type b for Back to return to the Software list.
14 In a terminal window, start the Monitor Agent:
rcgrpwise-ma start
NOTE: Unlike the other GroupWise agents, you do not need to be logged in as root in order to
start the Monitor Agent.
15 Continue with Installing and Configuring the Linux Monitor Application.
Installing and Configuring the Linux Monitor Application
1 If you are installing the Monitor Application on the same server where you just installed the
Monitor Agent, skip to Step 2.
or
If you are installing the Monitor Application on a different server from where you installed the
Monitor Agent:
1a Access the web server where you want to install the Monitor Application.
1b In a terminal window, become root by entering su - and the root password.
1c Start the GroupWise Installation Wizard at the root of the downloaded GroupWise 2014
software image:
./install.sh
1d Type the number for the language in which you want to run the GroupWise Installation
Wizard, then press Enter to select OK.
1e Type 2 for Installation, then press Enter.
167
1f Type a to accept the License Agreement and display the Software list.
2 Type 5 for GroupWise Monitor Application, then press Enter to display the Actions list.
3 Type 1 for Install, then press Enter to install the Monitor Application.
The Monitor Application is installed on the server. If any supporting packages are not available
media.
5 Type 2 for Configure, then press Enter to configure the Monitor Application.
6 Follow the prompts to configure the Monitor Application, using the following information from
the GroupWise Monitor Application Installation Worksheet:
Server Information
7 Press any key to exit Monitor Application Configuration.
9 (Conditional) If you use a proxy service, follow the instructions in “Configuring Proxy Service
Support for the Monitor Console” in the GroupWise 2014 Administration Guide.
10 Continue with Starting the Linux Monitor Agent.
Starting the Linux Monitor Agent
1 Use the following commands to manage the Monitor Agent:
rcgrpwise-ma
rcgrpwise-ma
rcgrpwise-ma
rcgrpwise-ma
start
restart
stop
status
2 (Optional) If desired, you can run the Monitor Agent executable directly:
2a Change to the GroupWise agent bin folder.
cd /opt/novell/groupwise/agents/bin
168
2b Use one of the following commands to start the Monitor Agent:
./gwmon --home /domain_folder &
./gwmon --ipa domain_server_ip_address --ipp mta_port_number &
3 For instructions on using the Monitor consoles, skip to Section 18.5, “Testing GroupWise
Monitor,” on page 172.
18.4.2
Windows: Installing the GroupWise Monitor Software
 “Preparing the Windows Server for GroupWise Monitor” on page 169
 “Installing the Windows GroupWise Monitor Software” on page 169
 “Starting the Windows Monitor Agent” on page 172
Preparing the Windows Server for GroupWise Monitor
1 Ensure that the server where you are installing the Monitor Agent meets the system
requirements listed in Section 18.6, “GroupWise Monitor Installation Worksheets,” on page 174.
2 Ensure that the web server where you are installing the Monitor Application meets the system
requirements listed in Section 18.2.2, “Web Server Requirements,” on page 161.
4 Ensure that no GroupWise agents are currently running on the Windows server where you plan
to install the Monitor Agent.
5 Ensure that the firewall on the server has the ports open that are used by the Monitor Agent and/
or the Monitor Application and the web server.
6 Continue with Installing the Windows GroupWise Monitor Software.
Installing the Windows GroupWise Monitor Software
169
2 Click GroupWise Monitor, accept the License Agreement, then click Next.
3 Click Next to display the GroupWise Monitor Components page.
information.
4 (Conditional) If you are installing the Monitor Agent, follow the prompts to provide the
information from your GroupWise Monitor Agent Installation Worksheet:
Server Information
Domain Directory
Service vs. Application
5 (Conditional) If you are installing the Monitor Application, follow the prompts to provide the
information from your GroupWise Monitor Application Installation Worksheet:
Monitor Agent Information (This page does not appear when you install the Monitor Agent and
the Monitor Application together on the same server.)
170
6 Review the Installation Summary, then click Install.
8 When the installation is complete, click Finish to exit the Monitor Installation program.
You can choose to have the Monitor Installation program start the Monitor Agent and restart the
web server for you.
9 Click Finish to exit the GroupWise Installation program.
171
If you chose to start the Monitor Agent immediately, the Monitor Agent server console displays
on the Windows server.
If the Monitor Agent does not start successfully, see “Manually Starting the Windows Agents As
Applications for Troubleshooting” on page 105.
10 (Conditional) If you use a proxy service, follow the instructions in “Configuring Proxy Service
Support for the Monitor Console” in the GroupWise 2014 Administration Guide.
11 Continue with Testing GroupWise Monitor.
Starting the Windows Monitor Agent
1 If you installed the Monitor Agent as a Windows service, use the Services administrative tool to
start and stop it.
or
If you installed the Monitor Agent as an application, start it on the Windows Start menu, or
create a desktop icon to start it.
2 Continue with Testing GroupWise Monitor.
18.5
Testing GroupWise Monitor
Monitor has two different web-based consoles. The main Monitor web console uses the capabilities of
your web server to provide access from outside your firewall. The web-based Monitor Agent console
is provided by the Monitor Agent itself and provides additional functionality beyond that which is
available from outside your firewall.
On Windows, the Monitor Agent also has a server console that displays only on the Windows server
where the Monitor Agent runs.
 Section 18.5.1, “Using the Monitor Web Console,” on page 173
 Section 18.5.2, “Using the Monitor Agent Console,” on page 173
 Section 18.5.3, “Using the Windows Monitor Agent Server Console,” on page 174
172
18.5.1
Using the Monitor Web Console
To display agent status information in your web browser from outside your firewall, enter the
Monitor Web console URL in your web browser:
http://network_address/gwmon/gwmonitor
Replace network_address with the IP address or DNS hostname of the server where your web server
runs. The Monitor console appears.
You can use this same URL to view the same agent status information in various browsers and on
mobile devices.
You can perform many of the same monitoring activities at the Monitor Web console as you can at the
Windows Monitor Agent server console. Refer to the online help in the Monitor Web console for
additional information about each Monitor Web console page.
For more information about using the Monitor consoles, see “Monitor” in the GroupWise 2014
18.5.2
Using the Monitor Agent Console
To display agent status information in your web browser from inside your firewall, enter the Monitor
Agent console URL in your web browser:
http://network_address:8200
For instructions on protecting the Monitor Agent console with a password, see “Securing the Monitor
Web Console” in the GroupWise 2014 Administration Guide.
173
18.5.3
Using the Windows Monitor Agent Server Console
To start the Monitor Agent on a Windows server and display the Windows Monitor Agent server
console:
 On Windows Server 2012: Click Search > GroupWise Monitor.
You might find it convenient to pin GroupWise Monitor to the Windows Start menu for future
use.
 On Windows Server 2008: Click Start > All Programs > GroupWise Monitor > GroupWise Monitor.
The Windows Monitor Agent server console appears.
In the Monitor Agent server console, you can perform many activities, for example:
 Use items on the Configuration menu to configure the Windows Monitor Agent as needed.
 Use items on the View menu to choose how much and what kind of agent status information to
display.
 Create agent groups in order to monitor related agents together.
 Use items on the Reports menu to check the status of links throughout your GroupWise system
and to organize status information into a format that can be emailed or printed.
 Use items on the Actions menu to control agent polling.
For more information about using the Windows Monitor Agent server console, see “Monitor” in the
18.6
GroupWise Monitor Installation Worksheets
 Section 18.6.1, “GroupWise Monitor Agent Installation Worksheet,” on page 175
 Section 18.6.2, “GroupWise Monitor Application Installation Worksheet,” on page 175
174
18.6.1
GroupWise Monitor Agent Installation Worksheet
Installation Program Field
System
Explanation
Section 18.1, “GroupWise Monitor
Overview,” on page 157
Monitor Component
 GroupWise Monitor Agent
Agent Software Platform
Section 18.3.1, “Deciding Where to
Install the GroupWise Monitor
Components,” on page 162
 Linux
 Windows
Server Information
 Installation path
Linux:
“Monitor Agent Network Address”
on page 164
/opt/novell/groupwise/
agents/bin
Windows:
c:\Program
Files\Novell\GroupWise
Monitor
 Network address
 IP address
 DNS hostname
 TCP port
(default 8200)
Domain Location
 Server
 Path
“Service vs. Application (Windows
Only)” on page 164
Windows Installation Option
 Service
 Application
18.6.2
GroupWise Monitor Application Installation Worksheet
Monitor Component
 GroupWise Monitor Application
System
Explanation
175
Web Server Platform
 Linux
System
Explanation
 Windows
Monitor Agent Information
 IP address
“Monitor Agent Network Address”
on page 164
 DNS hostname
 TCP port
(default 8200)
Web Server Information: OES 11
 Apache path
conf.d
 Tomcat path
/var/opt/novell/
tomcat6/webapps
Web Server Information: SLES 11
 Apache path
/etc/apache2/conf.d
 Tomcat path
/usr/share/tomcat6/
webapps
Web Server Information:
Windows
directory
 Website
c:\inetpub\wwwroot
176
19
Installing the GroupWise Client
19
The following sections assist you with assigning GroupWise accounts to users and with installing the
GroupWise 2014 client.
 Section 19.1, “GroupWise Client Overview,” on page 177
 Section 19.2, “GroupWise Client Workstation Requirements,” on page 177
 Section 19.3, “Installing the GroupWise Client,” on page 178
 Section 19.4, “Starting the Groupwise Client,” on page 181
For information about client licensing requirements, see “Auditing Mailbox License Usage in the Post
Office” in the GroupWise 2014 Administration Guide.
19.1
GroupWise Client Overview
Each user with a GroupWise account has a mailbox in a post office. In a corporate workplace
environment, GroupWise users with Windows workstations can run the GroupWise client to access
their mailboxes and to send and receive mail.
When the users are not at their workstations, they can access their GroupWise mailboxes from a web
browser by using GroupWise WebAccess or on a tablet device by using GroupWise WebAccess
Mobile. See Chapter 16, “Setting Up GroupWise WebAccess,” on page 113.
Users can also synchronize GroupWise data to their mobile devices. See Section 20.1, “Using the
GroupWise Mobility Service to Synchronize GroupWise Data to Mobile Devices,” on page 183.
19.2
GroupWise Client Workstation Requirements
 x86-32 processor or x86-64 processor
On a 64-bit processor, GroupWise still runs as a 32-bit application.
 Any of the following desktop operating systems for the GroupWise client:
 Windows XP on a 300 MHz or higher workstation with at least 128 MB of RAM
 Windows 7 on a 1 GHz or higher workstation with at least 1 GB of RAM
 Windows 8 or Windows 8.1 on a 1 GHz or higher workstation with at least 1 GB of RAM
NOTE: Windows 8 or later on a Microsoft Surface Pro tablet is not supported for use with
the GroupWise client. Use GroupWise WebAccess instead.
 Microsoft Internet Explorer 9 or later
177
 Any of the following word processors for use as the GroupWise editor:
 OpenOffice 3.4 or later
 LibreOffice 3.6 or later
 Microsoft Word 2007 or later
 Approximately 200 MB of free disk space on each user’s workstation to install the GroupWise
client.
19.3
The GroupWise client software is available in both the Windows version and the Linux version of the
downloaded GroupWise 2014 software image. A simple installation of the GroupWise client helps you
test your GroupWise system as you are setting it up.
If you want, you can burn the GroupWise 2014 software image to DVDs for distribution to GroupWise
client users. Advanced, system-wide rollout methods for the GroupWise client are also available.
 Section 19.3.1, “Installing the GroupWise Client from the Windows GroupWise 2014 Software
Image,” on page 178
 Section 19.3.2, “Installing the GroupWise Client from the Linux GroupWise 2014 Software
Image,” on page 180
 Section 19.3.3, “Implementing System-Wide GroupWise Client Rollouts,” on page 181
19.3.1
Installing the GroupWise Client from the Windows GroupWise 2014
Software Image
1 Install the GroupWise client software on a Windows workstation that meets the system
requirements listed in Section 19.2, “GroupWise Client Workstation Requirements,” on
page 177.
2 Run the GroupWise Installation Wizard (setup.exe) from the root of the downloaded
GroupWise 2014 software image.
3 Click GroupWise Client to start the GroupWise Client Setup Wizard.
4 Select the language in which you want to run the GroupWise Client Installation Wizard, then
click OK.
178
All available languages are automatically installed on the workstation, but you select the specific
language that you want to use for the Installation Wizard.
The GroupWise Client Installation Wizard appears.
5 Click Next to display the Setup Type dialog box.
6 Select one of the following options:
 Typical: Installs the most commonly used components in the standard installation directory
of c:\Program Files\Novell\Groupwise without prompting for further information.
Review the Custom settings to see which ones are enabled by default.
 Custom: Allows you to customize the following GroupWise client functionality:
 Languages (select as needed)
 Internet Browser Mail Integration (enabled by default)
 Program Folder (Novell GroupWise by default)
 Add GroupWise to the Desktop (selected by default)
 Add GroupWise to Quick Launch (selected by default)
 Add Icons to the Start Menu (selected by default)
179
 Add Notify to the Startup folder (disabled by default)
If Notify is not added to the Startup folder, Notify does not automatically run when
Windows starts. Users can control how Notify starts in the GroupWise client. For
instructions, see “Starting Notify” in the GroupWise 2014 Client User Guide.
See “Using GroupWise Client Custom Installation Options” in the GroupWise 2014
Administration Guide for more information about installing the GroupWise client.
7 Click Next.
8 (Conditional) If you selected Typical or Upgrade:
8a Click Install to install the client files.
When the client Installation Wizard has completed, a shortcut to run GroupWise appears
on your desktop and in the Quick Launch area.
8b Click Finish to exit the GroupWise Installation program.
8c Skip to Section 19.4, “Starting the Groupwise Client,” on page 181.
9 (Conditional) If you selected Custom:
9a Ensure that each component you want to install is selected.
Languages: Select which languages to install.
Internet Browser Mail Integration: Sets GroupWise to be the default email program on the
workstation, so that whenever the user clicks an email link on a web page or chooses the
Mail command in the browser, GroupWise starts.
9b Click Next.
9c Select the Program folder where you want to add the GroupWise icons.
The default is Novell GroupWise.
9d Select whether you want the GroupWise icon added to your Desktop and Quick Launch.
9e Select whether you want GroupWise icons added to the Start menu.
9f Select whether you want Notify added to the Startup folder.
If Notify is not added to the Startup folder, Notify does not automatically run when
Windows starts. Users can control how Notify starts in the GroupWise client. For
instructions, see “Starting Notify” in theGroupWise 2014 Client User Guide.
9g Click Next.
9h Click Install to install the client software files.
When the Installation Wizard has completed, a shortcut to run GroupWise appears on your
desktop.
9i Click Finish to exit the GroupWise Client Installation Wizard.
9j Skip to Section 19.4, “Starting the Groupwise Client,” on page 181.
19.3.2
Installing the GroupWise Client from the Linux GroupWise 2014
Software Image
Install the GroupWise client on a Windows workstation that meets the system requirements listed in
Section 19.2, “GroupWise Client Workstation Requirements,” on page 177. The Linux GroupWise 2014
software image includes the GroupWise client software.
1 On the Linux server where the GroupWise client software is located, set up a Samba share to
provide access to the GroupWise client software.
180
If you need assistance with this task, follow the instructions for your version of Linux:
 Section D.1, “Setting up Samba on OES,” on page 251
 Section D.3, “Setting Up Samba on SLES,” on page 255
2 Install the GroupWise client software on a Windows workstation that meets the system
requirements listed in Section 19.2, “GroupWise Client Workstation Requirements,” on
page 177.
3 On the client workstation, map a drive to the Samba share that you created in Step 1.
If you need assistance with this task, follow the instructions for your version of Linux:
 Section D.2, “Mapping a Drive to a Samba Share on an OES Server,” on page 254
 Section D.4, “Mapping a Drive to a Samba Share on a SLES Server,” on page 256
4 Change to the win32 subdirectory through the Samba share on the Linux server, then run the
GroupWise Client Installation Wizard (setup.exe).
The installation then proceeds normally.
5 Skip to Step 4 in Section 19.3.1, “Installing the GroupWise Client from the Windows GroupWise
2014 Software Image,” on page 178 to continue with the standard GroupWise client installation
process.
19.3.3
Implementing System-Wide GroupWise Client Rollouts
For a system-wide rollout of the GroupWise client software, see “Distributing the GroupWise Client”
in the GroupWise 2014 Administration Guide.
19.4
Starting the Groupwise Client
At startup, the GroupWise client needs to know the location (IP address/hostname and port number)
for the user’s post office.
The GroupWise client can get the information for the initial login in two ways:
 The user can provide the post office location when prompted.
 The GroupWise client can access a GroupWise name server to get the user’s post office location.
A GroupWise name server is a DNS hostname entry that defines the IP address of a POA.
During startup, the GroupWise client automatically looks for the GroupWise name server in
DNS. The POA identified as the GroupWise name server then redirects the client login to the
POA for the user’s post office. For information about creating a GroupWise name server, see
“Post Office Agent” in the GroupWise 2014 Administration Guide.
181
After the first successful login, the GroupWise client stores the post office location as the default for
future logins. The user is subsequently presented with a simpler Startup dialog box:
To start the GroupWise client for the first time:
1 Double-click the GroupWise icon
on the Windows desktop.
2 Enter the password and post office address information, then click OK.
For more information about logging in, see “Getting Started” in the GroupWise 2014 Client User Guide.
For information about providing users’ GroupWise passwords automatically, see “Security Options:
Password” in the GroupWise 2014 Administration Guide.
19.5
What’s Next
For information about using the features in the GroupWise client, click Help > Help Topics, or Help >
User Guide. The User Guide is also available on the GroupWise 2014 Documentation website (http://
www.novell.com/documentation/groupwise2014/) in HTML and PDF formats.
182
20
Using Other Novell Products with
GroupWise
20
 Section 20.1, “Using the GroupWise Mobility Service to Synchronize GroupWise Data to Mobile
Devices,” on page 183
 Section 20.2, “Using Novell Messenger to Provide Secure Instant Messaging for GroupWise
Users,” on page 183
 Section 20.3, “Using Novell Vibe to Provide Team Workspaces for GroupWise Users,” on
page 184
20.1
Using the GroupWise Mobility Service to Synchronize
GroupWise Data to Mobile Devices
The GroupWise Mobility Service provides data synchronization between GroupWise mailboxes and
mobile devices for synchronizing email, appointments, contacts, tasks, notes, and phone messages.
The GroupWise Mobility Service is fast, reliable and scalable, and supports the latest device
operating systems. For more information, see the GroupWise Mobility 2.0 Documentation website.
To support BlackBerry devices with an operating system earlier than BlackBerry 10.x, use BlackBerry
Enterprise Server for GroupWise.
20.2
Using Novell Messenger to Provide Secure Instant
Messaging for GroupWise Users
Novell Messenger is a corporate-based, secure instant messaging solution that supports instant
messaging, presence, and archiving of conversations. The Messenger client integrates with the
GroupWise Groupwise client to provide access to instant messaging features from within the
GroupWise client.
Novell Messenger is installed separately from GroupWise and does not rely on your GroupWise
system. All Messenger information is stored in eDirectory, not in GroupWise databases. For more
information, see:
 Novell Messenger Documentation website (https://www.novell.com/documentation/
novell_messenger22/)
 GroupWise and Messenger Quick Start (https://www.novell.com/documentation/groupwise2014/
gw2014_qs_messenger/data/gw2014_qs_messenger.html)
Using Other Novell Products with GroupWise
183
20.3
Using Novell Vibe to Provide Team Workspaces for
GroupWise Users
Novell Vibe enhances GroupWise by providing easy document management and document sharing,
team calendars and task lists, workflows, discussion threads, wikis, blogs, RSS feeds, and more.
For more information, see:
 Novell Vibe 3 Documentation website (http://www.novell.com/documentation/vibe34/)
 “Novell Vibe” in the GroupWise 2012 Interoperability Guide
The integration procedure is the same in GroupWise 2014 as it was in GroupWise 2012.
 GroupWise and Vibe Quick Start (https://www.novell.com/documentation/groupwise2014/
gw2014_qs_vibe/data/gw2014_qs_vibe.html)
184
V
GroupWise System Upgrade
V
 Chapter 21, “What’s New in GroupWise 2014,” on page 187
 Chapter 22, “Understanding the Upgrade Process,” on page 193
 Chapter 23, “Preparing Your Existing GroupWise System for the Upgrade,” on page 199
 Chapter 24, “Installing the GroupWise 2014 Software,” on page 201
 Chapter 28, “Upgrading GroupWise Agents and Applications,” on page 225
 Chapter 29, “Upgrading Users’ GroupWise Client Software,” on page 231
 Chapter 30, “Transitioning from ConsoleOne,” on page 233
 Chapter 31, “Upgrading the GroupWise/Exchange Coexistence Solution,” on page 235
GroupWise System Upgrade
185
186
21
What’s New in GroupWise 2014
21
GroupWise 2014 provides substantial improvements over GroupWise 2012 in these areas:
 Section 21.1, “GroupWise Administration Enhancements,” on page 187
 Section 21.2, “GroupWise Agent Enhancements,” on page 188
 Section 21.3, “GroupWise User Enhancements,” on page 190
 Section 21.4, “GroupWise What’s New and Tutorial Videos,” on page 192
21.1
GroupWise Administration Enhancements
 Simplified Installation and Upgrade: GroupWise software files are quickly laid down by the
GroupWise Installation Wizard. You then perform installation and upgrade tasks in the new
web-based Installation console. You use the Installation console to create a new GroupWise
system, to create domains and post offices on new GroupWise servers, and to upgrade an
existing GroupWise system to GroupWise 2014.
For examples of the new functionality, see Chapter 11, “Creating a Typical GroupWise System,”
on page 73 and Chapter 25, “Upgrading the Primary Domain Server,” on page 205.
 New Web-Based Administration Tool: The GroupWise Administration console enables you to
perform all required GroupWise administration tasks for which ConsoleOne was used in the
past. Many new and enhanced administrative features are also available. Now you can perform
GroupWise administration anywhere you have a web browser and an Internet connection.
on page 85.
 Directory-Agnostic Administration: In addition to NetIQ eDirectory, Microsoft Active
Directory can serve as the source of user information for GroupWise accounts. As an additional
alternative, GroupWise users can be created without any directory association. The eDirectory
schema is no longer modified with GroupWise-specific user information and objects. Standard
LDAP access is used with both eDirectory and Active Directory. You can use different directories
for different users in the same post office. You can use different directories for user provisioning
and authentication.
For usage instructions, see “LDAP Directories and Servers” in the GroupWise 2014 Administration
Guide.
 Delegated Administration: When you upgrade your GroupWise system to GroupWise 2014, a
GroupWise Super Admin user is created. The Super Admin user can then delegate
administration responsibilities to other GroupWise users to act as administrators on the system,
domain, or post office level.
For usage instructions, see “GroupWise Administrators” in the GroupWise 2014 Administration
Guide.
187
 GroupWise Administration Service: GroupWise administration is now based on the
GroupWise Administration Service that runs on each GroupWise server, along with any
GroupWise agents that have been installed there. The Admin Service provides the
communication between GroupWise servers and the Admin console so that drive mappings and
mounted filesystems are no longer required.
For background information, see Chapter 3, “GroupWise System Architecture,” on page 21.
 Scriptable Administration: The GroupWise Administration Service is based on the GroupWise
Administration REST API, which allows you to create customized administrative actions
through scripting.
For more information, see the GroupWise for Software Developers website.
 Native GroupWise Certificate Authority: You no longer need to purchase commercially signed
certificates in order to secure your GroupWise system with SSL connections between agents.
For more information, see “Using a Self-Signed Certificate from the GroupWise Certificate
Authority” in the GroupWise 2014 Administration Guide.
 Streamlined Client Software Updates: The new Client Auto-Update feature replaces the
software distribution directory for automatically updating GroupWise client software on users’
workstations. The client software is automatically installed to each post office whenever the
POA is updated. The software can be automatically distributed by the POA or by a web server.
 New Administrative Command Line Utility: The GroupWise Administration Utility
(GWAdminUtil) performs the few administrative tasks that cannot be performed in the Admin
console, because they require direct file system access.
Such tasks include:
 Database maintenance where two databases must be open simultaneously
 Agent service management
 Password management
 Server certificate management
For details, see “Using the GroupWise Administration Utility” in the GroupWise 2014
 Improved Online Help: The online help in the GroupWise Administration console and the
agent consoles now link seamlessly into the GroupWise 2014 Administration Guide, where details
beyond the information in the online help is readily available.
21.2
GroupWise Agent Enhancements
All GroupWise agents now use 64-bit architecture. GroupWise web-based applications (WebAccess,
Calendar Publishing Host, and Monitor) can be installed on either 64-bit or 32-bit web servers.
The following sections provide details on specific enhancements for the GroupWise agents and
applications:
 Section 21.2.1, “Post Office Agent Enhancements,” on page 189
 Section 21.2.2, “Message Transfer Agent Enhancements,” on page 189
 Section 21.2.3, “Internet Agent Enhancements,” on page 189
 Section 21.2.4, “Document Viewer Agent Enhancements,” on page 189
 Section 21.2.5, “Monitor Enhancements,” on page 190
188
21.2.1
Post Office Agent Enhancements
 DVA by Default: The POA always uses the DVA for document conversion. The DVA is installed
along with the other agent software as part of the GroupWise Server component. You can run it
along with the POA on a post office server, or you can run it on a separate server. The Document
Converter Agent (DCA) is no longer used.
 Peak Value Data: The POA console includes a Peak Value column for client/server performance
data. The data is written to the [email protected] file whenever the values are refreshed. The file
is created in the post_office/oftemp folder.
 Snapshot Data: The POA provides more accurate performance data and writes the data to a
[email protected] file. The file is created in the post_office/oftemp folder.
 LDAP Server Pools: The POA console displays LDAP server pools based on the directory
(Novell eDirectory or Microsoft Active Directory) that the LDAP server is associated with. From
the list of LDAP servers in the pool, you can easily check the status of each one.
 Audit Trail: In Verbose mode, all POA console activities are written to the log file. Search in the
log file for “Web Console” to see the activities.
 Improved IMAP Functionality: IMAP has been optimized so that the most recent mailbox items
are delivered to IMAP clients first before older items, and so that the items are transferred much
more quickly.
21.2.2
Message Transfer Agent Enhancements
 User Synchronization with Active Directory: The MTA can perform user synchronization
between GroupWise and Exchange systems.
 On-Demand Synchronization: In the MTA console, you can start user synchronization
immediately, rather than waiting for a scheduled event.
21.2.3
Internet Agent Enhancements
 Increased Stability: Improper encoding of incoming messages is handled more gracefully.
 Load Balancing of Relay Hosts: The GWIA cycles through the list of available relay hosts
instead of using the first relay host in the list every time.
 Improved Spam Tracking: Sender and IP address information on relayed messages and hacked
account accounts is logged to help track spam.
 Improved IMAP Functionality: IMAP has been optimized so that the most recent mailbox items
are delivered to IMAP clients first before older items, and so that the items are transferred much
more quickly.
 Improved Experience for Non-English Speakers: Returned status messages now use translated
text. For example, the Subject line in an Undeliverable Message notification is in the language of
the sender’s GroupWise client.
21.2.4
Document Viewer Agent Enhancements
 Log Files for Worker Thread: With logging set to Verbose, the DVA creates a log file for each
worker thread. This helps identify the error when a worker process fails to convert a specific
document into HTML.
189
21.2.5
Monitor Enhancements
 Windows Service: You can now run the Monitor Agent as a Windows service, as an alternative
to running it as a Windows application.
 More Timely Status Reporting: The Monitor Agent now polls unresponsive agents every 12
seconds, so that it can report promptly when the agent is back up. After the agent is responsive
again, the default polling interval of 5 minutes resumes. This is especially useful when you
reboot a server where GroupWise agents run. You can see more quickly when agents are
running again. If a number of agents are unresponsive, the Monitor Agent continues the 12second polling until 80% of the agents are responsive. It then returns to the default polling cycle
to conserve resources.
21.3
GroupWise User Enhancements
 Section 21.3.1, “GroupWise Client Enhancements,” on page 190
 Section 21.3.2, “GroupWise WebAccess Enhancements,” on page 191
 Section 21.3.3, “GroupWise WebAccess Mobile Enhancements,” on page 191
 Section 21.3.4, “Calendar Publishing Enhancements,” on page 191
21.3.1
GroupWise Client Enhancements
TIP: For demonstrations, see “GroupWise 2014 What’s New Videos.”
 New Look and Feel: GroupWise 2014 includes significant improvements to the look and feel of
the GroupWise client.
 A new light-and-dark interface simplifies the user experience and highlights important
fields and information. The clean, flat layout highlights your data and causes the
surrounding GroupWise structure to blend in.
 A modern layout and large, easily identifiable icons make features, resources, and folders
more discoverable and intuitive.
 Many dialogs have been improved or removed to make managing your items easier.
 A new Options slide-out in the Compose and Received views makes the items you’re
composing or editing easier to customize, and allows you to change many important
settings on the fly.
 Relevancy is used to bring frequently selected features and commands into easy-to-access
locations in the client interface. For example, the new Favorites list, located in the dropdown menu on the To list, uses relevancy give you access to people you contact often.
For examples, see “New Look and Feel” in the GroupWise 2014 Client User Guide.
 More Convenient Signatures: Signature management features are now integrated directly into
the compose view to make adding and editing signatures more convenient. In addition, your
default signature now appears in the Compose view if signatures are turned on.
 Improved Name Completion: Name Completion enhancements in GroupWise 2014 make it
easier to find the contact that you’re looking for. For example, when you type characters into the
To, > CC, or BC fields in the Compose view, GroupWise Name Completion now returns results
on the first name, last name, display name, and email address of contacts in your address book
and then displays them in a list format.
190
 Personal/Group Items: To reduce confusion, Posted items are now referred to as Personal items
in GroupWise 2014. In addition, interface enhancements, such as the Options slide-out, make it
easier to manage Group and Personal (formerly Posted) items.
 Reply Options: Compose options are now more accessible in GroupWise 2014, allowing greater
control over how and who you reply to items in your mailbox.
 Clearer Month Calendar Display: A bolded date in the calendar view indicates that you have
an appointment with a status of Busy, Out of Office, or Tentative on that day. In previous versions
of GroupWise, a bolded date indicated that an appointment, task, or note was associated with
that day.
 Finding Folders: Just as it has in previous versions, Find allows you to locate items, contacts,
and more. New in GroupWise 2014, Find now searches and returns folders in the Find results. In
conjunction, you can now hover over the Folder column in the Find Results list, and immediately
see the file path of the folder, which is especially useful for users who have folders with similar
names.
 Help Improvements: In GroupWise 2014, you can quickly access Help topics with the new
Search Help feature. The Welcome tab, located in the Nav Bar, also provides Help resources for
new and experienced GroupWise users.
21.3.2
GroupWise WebAccess Enhancements
TIP: For demonstrations, see “WebAccess What’s New Videos.”
 New Look and Feel: The user interface in GroupWise 2014 WebAccess, which features large,
easily identifiable icons and streamlined access to features, has been updated to match the clean,
flat layout of the GroupWise 2014 client.
 Auto-Refresh: Your GroupWise Mailbox automatically refreshes as you receive new items in
GroupWise 2014 WebAccess. There is no need to manually refresh WebAccess to check for new
items as in earlier versions.
 Notification of New Messages: If your computer has audio capabilities, and a GroupWise
WebAccess window is open in your web browser, an audio cue plays when a new item is
received.
21.3.3
GroupWise WebAccess Mobile Enhancements
 Auto-Refresh: Your GroupWise Mailbox automatically refreshes as you receive new items in
GroupWise 2014 WebAccess Mobile. There is no need to manually refresh WebAccess to check
for new items as in earlier versions.
 Attachments on iOS Devices: You can attach files to items that you send from Android tablets
or iOS tablets running iOS version 6.0 or higher. You can also download and read attachments
that you receive on either Android or iOS tablets.
 Broader Device Support: New tablet devices are now supported (Apple iPad 3, Android 4.1x or
later devices, Kindle Fire HD7).
21.3.4
Calendar Publishing Enhancements
 Private Items: The content of private items is hidden, but the time period for private items is
blocked out.
 Calendar Display: When you publish your entire main GroupWise Calendar, 365 days in the
future are published. There is no restriction on publishing an entire personal calendar.
191
21.4
GroupWise What’s New and Tutorial Videos
GroupWise 2014 includes a set of What’s New videos to introduce your experienced GroupWise
users to new and improved features in the GroupWise client and in WebAccess:
 GroupWise 2014 Client What’s New Videos
 GroupWise 2014 WebAccess What’s New Videos
GroupWise 2014 also includes a set of tutorial videos to introduce new GroupWise users to the basics
of using GroupWise as their email client. See GroupWise 2014 Client How-To Videos.
192
22
Understanding the Upgrade Process
2
You can upgrade a GroupWise 8 or GroupWise 2012 system to GroupWise 2014.
IMPORTANT: If you need to upgrade from an older GroupWise version, you must upgrade at least
to GroupWise 8, and preferably to GroupWise 2012, in order to ensure that your GroupWise data is
compatible with the upgrade process that is provided in GroupWise 2014.
If your GroupWise system is still on NetWare, see “Migrating Away from NetWare” in the GroupWise
2012 Installation Guide.
Before you begin upgrading any aspect of your GroupWise system to GroupWise 2014, review the
following sections to help you plan a successful upgrade strategy:
 Section 22.1, “Domain and Post Office Upgrades,” on page 194
 Section 22.2, “Agent Upgrades,” on page 195
 Section 22.3, “Monitor Upgrades,” on page 196
 Section 22.4, “WebAccess Upgrades,” on page 196
 Section 22.5, “Calendar Publishing Host Upgrades,” on page 196
 Section 22.6, “GroupWise Client Upgrades,” on page 197
 Section 22.7, “Obsolete eDirectory Schema Extensions,” on page 197
 Section 22.8, “Obsolete Software Distribution Directories,” on page 197
 Section 22.9, “Obsolete GroupWise Gateways,” on page 197
 Section 22.10, “NetWare Compatibility,” on page 198
IMPORTANT: After you understand the upgrade process in general, you are ready to upgrade
specific components of your existing GroupWise system. Do not start upgrading your GroupWise
system until you have a solid understanding of the entire process.
For a large GroupWise system, you might need to maintain a mixed-version environment as you roll
out GroupWise 2014. For a table showing which GroupWise 8 and GroupWise 2012 components can
be used with GroupWise 2014, see Appendix A, “GroupWise Version Compatibility,” on page 239.
193
22.1
Domain and Post Office Upgrades
Functionality enhancements in GroupWise 2014 require the GroupWise domain and post office
databases to be upgraded. The following diagram illustrates the required upgrade sequence for
installing the GroupWise 2014 software.
Primary
Domain Server
1
Secondary
Domain Server
Primary
Domain
2
Secondary
Domain
Post Office
Server
3
3
2
Post Office
Post Office
Post Office
1. Upgrade the primary domain server first, so that correct replication of GroupWise 2014
information can take place as you upgrade secondary domains and post offices.
If there are secondary domains or post offices on the primary domain server, you can upgrade
them at the same time as the primary domain, but this is not required.
2. Upgrade secondary domain servers.
If there are multiple secondary domains or post offices on a secondary domain server, you can
upgrade them at the same time, but this is not required.
3. Upgrade post office servers after upgrading the secondary domains that they belong to.
When you install the GroupWise 2014 software on a server where an earlier version of GroupWise is
installed, the Installation Wizard stops the existing agents, installs the GroupWise 2014 software, and
then starts the GroupWise 2014 agents.
IMPORTANT: Upgrading the domain and post office servers does not upgrade the domain and post
office databases. Database upgrades are performed in a separate step.
When you upgrade multiple domains and post office on the same server at the same time, the
Installation console orchestrates the process of upgrading the databases in the proper order.
194
22.2
Agent Upgrades
POA
POAs are automatically upgraded along with the post offices that they belong to.
The upgrade process looks for POA startup files. If a POA startup file is found, the setting of the -home switch is verified. If the home folder is valid, the existing POA startup file is used with the
upgraded POA. If the POA startup file cannot be found, or if the home folder is not valid, a new POA
startup file is created in the post office folder. The GroupWise 2014 location for POA startup files is the
post office folder.
If you have been running multiple POAs on multiple servers, the upgrade process cannot upgrade
POAs on remote servers. In GroupWise 2014, the need for running multiple POAs for a post office
does not occur. You can configure the POA that runs on the server where the post office is located to
handle all the needs of the post office.
If your existing POAs have been using the internal Document Converter Agent (DCA) rather than the
independent Document Viewer Agent (DVA), you must run at least on DVA in your GroupWise 2014
system.
For a list of improvements in the GroupWise 2014 POA, see Section 21.2.1, “Post Office Agent
Enhancements,” on page 189.
MTA
MTAs are automatically upgraded along with the domains that they belong to.
The upgrade process looks for MTA startup files. If an MTA startup file is found, the setting of the -home switch is verified. If the home folder is valid, the existing MTA startup file is used with the
upgraded MTA. If the MTA startup file cannot be found, or if the home folder is not valid, a new MTA
startup file is created in the domain folder. The GroupWise 2014 location for MTA startup files is the
domain folder.
For a list of improvements in the GroupWise 2014 MTA, see Section 21.2.2, “Message Transfer Agent
GWIA
GWIAs are automatically upgraded along with the domains that they belong to.
For a list of improvements in the GroupWise 2014 GWIA, see Section 21.2.3, “Internet Agent
IMPORTANT: If you are upgrading to GroupWise 2014 from GroupWise 8, you need to understand
the important changes to where GWIA configuration information is stored. See “Using Internet Agent
Startup Switches” in the GroupWise 8 Administration Guide before you upgrade to GroupWise 2014.
DVA
Existing DVAs are automatically upgraded along with the POAs that they were installed with.
However, their startup files (gwdva.dva) are not modified. On Linux, the gwha.conf file already has
an entry for each DVA. On Windows, the DVA service is already set up.
If you were not running a DVA in your existing GroupWise system, you must install and configure at
least one DVA in your GroupWise 2014 system.
For a list of improvements in the GroupWise 2014 DVA, see Section 21.2.4, “Document Viewer Agent
195
22.3
Monitor Upgrades
GroupWise Monitor is not dependent on any other GroupWise agents, so you can upgrade the
Monitor Agent and the Monitor Application to GroupWise 2014 at any time.
IMPORTANT: If you are upgrading from GroupWise 8 directly to GroupWise 2014, you need to
understand that Monitor no longer relies on eDirectory objects for its configuration information. All
configuration information is located in the gwmonitor.cfg file instead. See “Understanding Monitor
Updates” and “Updating GroupWise Monitor”in the GroupWise 2012 Installation Guide before you
upgrade Monitor from GroupWise 8 directly to GroupWise 2014.
On Linux, the GroupWise High Availability Service (gwha), that works in conjunction with the
Monitor Agent to automatically restart the GroupWise agents, has been made more secure.
22.4
WebAccess Upgrades
If you are upgrading from GroupWise 2012 to GroupWise 2014, there are no WebAccess upgrade
issues. You can upgrade your WebAccess software whenever it is convenient as you upgrade your
GroupWise system. However, in order to use the WebAccess Application console, you must change
the way it is configured. For instructions, see “Using the WebAccess Application Console” in the
For a list of new features in GroupWise 2014 WebAccess, see Section 21.3.2, “GroupWise WebAccess
understand that the WebAccess Agent is no longer part of GroupWise. See “Understanding
WebAccess Updates” and “Updating GroupWise WebAccess” in the GroupWise 2012 Installation
Guide before you upgrade WebAccess from GroupWise 8 directly to GroupWise 2014.
22.5
Calendar Publishing Host Upgrades
There are no Calendar Publishing Host upgrade issues. You can upgrade the Calendar Publishing
Host to GroupWise 2014 at any time after the POA that it communicates with has been upgraded.
However, in order to use the CalPub Host Admin console, you must change the way it is configured.
For instructions, see Section 17.5.4, “Setting Up Calendar Publishing Administration,” on page 149.
For a list of improved functionality in the GroupWise 2014 Calendar Publishing Host, see
Section 21.3.4, “Calendar Publishing Enhancements,” on page 191.
196
22.6
GroupWise Client Upgrades
After a post office is upgraded to version 2014, users can run the GroupWise 2014 client on
workstations that meet the requirements listed in Chapter 5, “GroupWise User Requirements,” on
page 33. If necessary, they can also continue to run their older GroupWise clients. However, older
clients do not have GroupWise 2014 functionality just because they are accessing mailboxes in a
GroupWise 2014 post office.
IMPORTANT: A user who needs to proxy into another user’s mailbox should not upgrade to the
GroupWise 2014 client until the mailbox owner’s post office has been upgraded to version 2014. The
GroupWise 2014 client cannot proxy into a mailbox that has not been upgraded to GroupWise 2014.
For a list of new features in the GroupWise 2014 client, see Section 21.3.1, “GroupWise Client
22.7
Obsolete eDirectory Schema Extensions
GroupWise 2014 no longer extends the eDirectory schema to accommodate GroupWise-specific
objects. After upgrading domains and post offices to GroupWise 2014, the associated GroupWise
objects in eDirectory are not used by GroupWise 2014.
IMPORTANT: It is not necessary to remove obsolete GroupWise objects from eDirectory. If you want
to remove them, use iManager (recommended) or ConsoleOne (not recommended). If you use
ConsoleOne, remove (or move) the GroupWise snapins first. Otherwise, you run the risk of
inadvertently deleting a GroupWise account. Always back up your domain database before taking
any action.
22.8
Obsolete Software Distribution Directories
GroupWise 2014 no longer uses software distribution directories. After you have upgraded post
offices, you can delete the associated software distribution directories in the Admin console.
1 In the GroupWise Admin console, click System > Legacy.
2 Click Software Areas.
3 Select the obsolete software distribution directory, then click Delete.
GroupWise 2014 uses the Client Auto-Update feature instead of software distribution directories. For
usage instructions, see “Using Client Auto-Update to Distribute the GroupWise Client Software” in
the GroupWise 2014 Administration Guide.
22.9
Obsolete GroupWise Gateways
There are no known issues with using GroupWise gateways with GroupWise 2014. However,
GroupWise gateways are legacy products that are not supported with the current GroupWise
version. You can delete obsolete gateways in the GroupWise Admin console.
1 In the GroupWise Admin console, click System > Legacy.
2 On the Gateways tab, select the obsolete gateway, then click Delete.
197
22.10
NetWare Compatibility
As of GroupWise 2012, GroupWise does not include GroupWise agents that run on NetWare, because
NetWare has entered the Extended Support phase of the Novell Support Life cycle. For more
information, see TID 7003092, “NetWare Support,” in the Novell Support Knowledgebase (http://
www.novell.com/support/).
If you currently have NetWare servers in your GroupWise system, you must decide how to handle
them as you move forward with your GroupWise 2014 upgrade. You have several alternatives:
 Migrate NetWare servers to Open Enterprise Server (OES).
 Move domains and post offices from NetWare servers to supported Linux servers.
 Move domains and post offices from NetWare servers to supported Windows servers.
You might decide to use one or more of these alternatives as you upgrade your GroupWise system to
GroupWise 2014. Detailed instructions for each alternative are provided in “Migrating Away from
NetWare” in the GroupWise 2012 Installation Guide, because GroupWise 2012 is the first version where
NetWare is not supported.
198
23
Preparing Your Existing GroupWise
System for the Upgrade
23
To prepare your GroupWise system to be upgraded to version 2014, complete the following tasks:
 Validate your domain and post office databases to ensure that there are no physical
inconsistencies with the database. If problems exist, you should recover or rebuild the database.
For information about validating, recovering, or rebuilding a database, see the documentation
for your current GroupWise version at the Novell Documentation website (http://
www.novell.com/documentation/#d).
 Back up each domain or post office immediately before upgrading it. For information about
backing up your GroupWise databases, see the documentation for your current GroupWise
version at the Novell Documentation website (http://www.novell.com/documentation/#d).
 Collect the information about your existing GroupWise system that the GroupWise Installation
Wizard prompts you for as you upgrade to GroupWise 2014. You might find it helpful to review
Chapter 8, “Planning Your GroupWise System,” on page 45 and to record the information on the
worksheets provided for an initial installation:
 “Simple GroupWise System Worksheet” on page 56 (for a small GroupWise system that is
all on one server)
 “Primary Domain Worksheet” on page 58 (for a primary domain on its own server)
 “Secondary Domain Worksheet” on page 59 (for each secondary domain)
 “Post Office Worksheet” on page 60 (for each post office)
 “GroupWise WebAccess Installation Worksheet” on page 129 (for each WebAccess
Application)
 “GroupWise Calendar Publishing Host Worksheets” on page 153 (for each Calendar
Publishing Host Application)
 “GroupWise Monitor Installation Worksheets” on page 174 (for each Monitor Agent/
Application)
Preparing Your Existing GroupWise System for the Upgrade
199
 Prepare the existing agents for upgrade. The Installation console uses the same agent
configuration for GroupWise 2014 that is in use for your existing GroupWise system. Your
current agent configuration might not be the best option for GroupWise 2014. The GroupWise
2012 Installation Guide provides information for reconfiguring your existing agents in
preparation for the upgrade.
Linux:
The Installation console can locate agents that are listed in the gwha.conf file used by the
GroupWise High Availability Service (gwha). For background information, see “Enabling the
GroupWise High Availability Service for the Linux GroupWise Agents” in the GroupWise 2012
Installation Guide.
Also, the Admin console cannot manage agents that run with the user interface provided by
the --show switch. For background information, see “Starting the Linux Agents with a User
Interface” in the GroupWise 2012 Installation Guide.
Windows:
The Installation console can locate agents that have been running as Windows services. For
background information, see “Starting the Windows Agents Manually or Automatically as
Services” in the GroupWise 2012 Installation Guide.
Also, the Admin console cannot manage agents that run as applications with a user interface.
For background information, see “Starting the Windows Agents Manually As Applications” in
the GroupWise 2012 Installation Guide.
In preparation for GroupWise 2014, you can configure your existing agents to run without a user
interface, so that the Installation console can automatically locate them, or you can specify the
locations of domains and post offices during the upgrade process.
 Ensure that all GroupWise servers meet the system requirements listed in Chapter 4,
“GroupWise Administration Requirements,” on page 27.
 When you upgrade the primary domain to GroupWise 2014, you establish the user name and
password for the GroupWise Super Admin. For background information about this
administrative user, see “Primary Domain: Super Admin Creation” on page 50. Decide on the
Super Admin user name and password before you start the upgrade process.
 When you upgrade a domain or post office on a Linux server, ensure that the Linux operating
system media is available, either physically or in a repository, in case the Installation Wizard
needs to install supporting packages on the Linux server.
 Ensure that all GroupWise client user workstations meet the system requirements listed in
Chapter 5, “GroupWise User Requirements,” on page 33.
200
24
Installing the GroupWise 2014 Software
24
Before installing the GroupWise 2014 software, review the background information and complete the
tasks in the following sections:
 Chapter 22, “Understanding the Upgrade Process,” on page 193
 Chapter 23, “Preparing Your Existing GroupWise System for the Upgrade,” on page 199
Then follow the installation instructions for the platform where the domain or post office to upgrade
is located.
 Section 24.1, “Linux: Installing the GroupWise 2014 Software,” on page 201
 Section 24.2, “Windows: Installing the GroupWise 2014 Software,” on page 203
24.1
Linux: Installing the GroupWise 2014 Software
1 Stop the existing GroupWise agents that are running on the server to upgrade.
image:
./install.sh
201
8 Type 1 for GroupWise Server, then press Enter to display the Actions list.
9 Type 1 for Install, then press Enter to install the GroupWise Server component.
The packages for the GroupWise Server component (Admin Service and agents) are installed on
the server. If any supporting packages are not available on the server, the Installation Wizard
automatically installs them from the operating system media.
All of the GroupWise agents are installed on every GroupWise server. The MTA and, optionally,
the GWIA are configured to run on a domain server. The POA and the DVA are configured to
run on a post office server.
The Installation Wizard starts any agents that typically run on the server.
IMPORTANT: Running the GroupWise 2014 agents does not upgrade the GroupWise databases
on the server to GroupWise 2014. Updating the databases is performed in a subsequent step.
11 Type 2 for Configure, then press Enter to start the GroupWise Admin Service and display
instructions for accessing the Installation console to upgrade the GroupWise server to
GroupWise 2014.
12 Right-click the URL under To install or configure a new GroupWise server, then click Open Link to
open your web browser.
If your web browser does not offer this functionality, open your web browser, then copy the URL
into it.
14 Skip to the instructions for the upgrade task that you are performing:
202
24.2
Windows: Installing the GroupWise 2014 Software
3 Click GroupWise Server to install the GroupWise Server component.
4 Select the language in which you want to perform the installation, then click OK to start the
GroupWise Server Setup Wizard.
203
6 Accept the License Agreement, then click Next to display the Custom Setup page.
The following components are available for installation:
 GroupWise Server: (Required) Consists of the Admin Service, the POA, the MTA, the
GWIA, and the DVA.
All of the GroupWise agents are installed on every GroupWise server. The MTA and,
optionally, the GWIA are configured to run on a domain server. The POA and the DVA are
configured to run on a post office server.
 Client Auto-Update Repository: (Optional) Helps you distribute the GroupWise client
software to users’ Windows workstations.
7 Click Next to continue, then click Install to install the GroupWise software.
8 When the GroupWise software has been installed, click Finish to return to the main page of the
Installation Wizard, then close the Installation Wizard.
9 Reboot the Windows server to complete the installation and start the GroupWise Installation
console.
The Installation Wizard has created two new icons on your Windows desktop.
10 On your Windows desktop, double-click GroupWise Install
to open your web browser and
access the Installation console.
This starts the GroupWise Admin Service and launches the GroupWise Installation console in
your web browser.
After installation, use GroupWise Admin Console
GroupWise system administration.
to access the Admin console for ongoing
12 Skip to the instructions for the upgrade task that you are performing:
204
25
Upgrading the Primary Domain Server
25
Before you upgrade the primary domain server, you should have reviewed the following sections
and completed the accompanying tasks:
 Chapter 3, “GroupWise System Architecture,” on page 21
 Chapter 4, “GroupWise Administration Requirements,” on page 27
 Chapter 24, “Installing the GroupWise 2014 Software,” on page 201
After you install the GroupWise 2014 software on the primary domain server, the Installation Wizard
displays the Installation console in your web browser.
1 In the Installation console, click
Upgrade an Existing Domain or Post Office to GroupWise 2014.
What displays next depends on whether the Installation console can detect the existing domains
and post offices on the server. The conditions for automatic detection are described in
Chapter 23, “Preparing Your Existing GroupWise System for the Upgrade,” on page 199.
205
2 (Conditional) If the Installation console can locate existing domains and post offices:
2a (Conditional) If there are any domains and post offices on the primary domain server that
you do not want to upgrade along with the primary domain, select them, then click Remove
to remove them from the list.
2b (Conditional) If you want to change the IP address or Admin port for any domain or post
office, click its name to display the Network Information dialog box.
Specify the desired IP address or Admin port, then click OK.
2c Skip to Step 4 to perform the upgrade.
3 (Conditional) If the Installation console cannot locate existing domains and post offices:
3a Click Add.
3b Browse to and select the primary domain folder.
206
3c Click OK, then review the MTA IP address and domain Admin port that the Installation
console has provided.
3d (Optional) Change the information as needed.
3e Click OK to return to the Installation console.
3f Repeat Step 3a through Step 3e for each additional domain and post office that you want to
upgrade on the primary domain server.
3g Continue with Step 4 to perform the upgrade.
4 In the list of domains and post offices to upgrade, click Next to display the Credentials page.
5 Specify the user name for the GroupWise Super Admin, type the password twice for
confirmation, then click Next to display the Summary page.
207
6 Review the information to ensure that it is correct, then click Finish to perform the upgrade.
7 Click Go to the GroupWise Administration console now.
8 Accept the self-signed certificate that the Installation console has automatically provided for
accessing the Admin console.
The Login fields display.
9 Specify the GroupWise Super Admin user name and password that you established in Step 5,
then click Login to display the Overview page in the GroupWise Admin console.
To finish the upgrade process, you must restart the MTA for the primary domain. You must also
restart the agents for any other upgraded domains and post offices on the primary domain
server.
If the primary domain has a GWIA, it was also upgraded along with the primary domain and its
MTA. However, you do not need to restart the upgraded GWIA.
IMPORTANT: If you are upgrading from GroupWise 8, see Section 22.2, “Agent Upgrades,” on
page 195 for release-specific information.
208
10 To restart the MTA in the upgraded primary domain:
10a In the Domain box on the Overview page, click MTA or click Running
> MTA to display
the MTA properties page.
10b Click Stop Agent, then click Start Agent to restart the upgraded MTA.
10c (Optional) Click Launch MTA Console to open the MTA console in a new browser window.
TIP: You can conveniently open the MTA console on the Overview page by clicking
Running , and then clicking the IP address of the MTA.
If the primary domain has a GWIA, it was also upgraded along with the primary domain
and its MTA. However, you do not need to restart the upgraded GWIA.
IMPORTANT: If you are upgrading from GroupWise 8, see Section 22.2, “Agent
Upgrades,” on page 195 for release-specific information.
10d Click Overview to return to the Overview page.
11 (Conditional) If the primary domain server has additional upgraded domains, repeat Step 10 for
the MTA in each upgraded domain.
209
12 (Conditional) If the primary domain server has upgraded post offices:
12a In the Domain box on the Overview page, click Running
next to the Post Office icon
then click POA to display the POA properties page.
12b Click Stop Agent, then click Start Agent to restart the upgraded POA.
12c (Optional) Click Launch POA Console to open the POA console in a new browser window.
TIP: You can conveniently open the POA console on the Overview page by clicking
Running , and then clicking the IP address of the POA.
12d Click Overview to return to the Overview page.
If the post office has a DVA, it was also upgraded along with the post office and its POA.
However, you do not need to restart the upgraded DVA.
13 (Conditional) If the primary domain server has additional post offices, repeat Step 12 for the
POA in each upgraded post office.
14 Skip to the next upgrade task for your GroupWise system:
 Section 28.2, “Upgrading GroupWise WebAccess,” on page 225
 Section 28.3, “Upgrading the Calendar Publishing Host,” on page 227
 Section 28.4, “Upgrading GroupWise Monitor,” on page 228
210
,
26
Upgrading a Secondary Domain Server
26
After you have upgraded the primary domain server in your GroupWise system, you can upgrade
secondary domains in your GroupWise system in any order that is convenient for you.
Before you upgrade a secondary domain server, review the following sections and complete the
accompanying tasks if you have not done so recently:
To upgrade a secondary domain server:
2 Install the GroupWise 2014 software on the secondary domain server.
See Chapter 24, “Installing the GroupWise 2014 Software,” on page 201 for instructions.
When the software installation is complete, the Installation Wizard displays the Installation
console in your web browser.
page 79.
211
4 (Conditional) If the Installation console can locate existing domains and post offices:
4a (Conditional) If there are any domains and post offices on the secondary domain server that
you do not want to upgrade, select them, then click Remove.
4b (Conditional) If you want to change the IP address or Admin port for any domain or post
office, click its name to display the Network Information dialog box.
Specify the desired IP address or Admin port, then click OK.
212
5 (Conditional) If the Installation console cannot locate existing domains and post offices:
5a Click Add.
5b Browse to and select the secondary domain folder.
5c Click OK, then review the MTA IP address and domain Admin port that the Installation
5f If you want o upgrade additional domains and post offices on the domain server, repeat
Step 5a through Step 5e.
213
6 In the list of secondary domains, and optionally, post offices to upgrade, click Next to display the
Credentials page.
7 Specify the IP address of the primary domain server and the password for the GroupWise Super
Admin, then click Next to display the Summary page.
9 (Optional) Click the Existing Configuration slide-out to list all upgraded domains and post
offices.
214
12 Specify the GroupWise Super Admin user name and password that you established when you
upgraded the primary domain, then click Login to display the Overview page in the Admin
console.
To finish the upgrade process, you must restart the agents for all upgraded secondary domains
and post offices on the secondary domain server.
If any secondary domains have GWIAs, they were also upgraded along with the secondary
domains. However, you do not need to restart the upgraded GWIAs.
IMPORTANT: If you are upgrading from GroupWise 8, see Section 22.2, “Agent Upgrades,” on
page 195 for release-specific information.
215
13 To restart the MTA in the upgraded secondary domain:
13a In the Domain box on the Overview page, click MTA or click Running
> MTA to display
the MTA properties page.
13b Click Stop Agent, then click Start Agent to restart the upgraded MTA.
13c (Optional) Click Launch MTA Console to open the MTA console in a new browser window.
TIP: You can conveniently open the MTA console on the Overview page by clicking
Running , and then clicking the IP address of the MTA.
If any secondary domains have GWIAs, they were also upgraded along with the secondary
domains. However, you do not need to restart the upgraded GWIAs.
IMPORTANT: If you are upgrading from GroupWise 8, see Section 22.2, “Agent
Upgrades,” on page 195 for release-specific information.
14 (Conditional) If the secondary domain server has additional upgraded domains, repeat Step 13
for the MTA in each upgraded domain.
216
15 (Conditional) If the secondary domain server has upgraded post offices:
,
NOTE: You can conveniently open the POA console on the Overview page by clicking
If the post office has a DVA, it was also upgraded along with the post office and its POA.
However, you do not need to restart the upgraded DVA.
16 (Conditional) If the secondary domain server has additional post offices, repeat Step 15 for the
217
218
27
Upgrading a Post Office Server
27
You can upgrade a post office after you have upgraded the domain that owns it.
When the post office is located on the same server with the owning domain, you can upgrade it along
with its domain. See these associated tasks:
 Chapter 25, “Upgrading the Primary Domain Server,” on page 205
 Chapter 26, “Upgrading a Secondary Domain Server,” on page 211
When the post office is on a separate post office server, review the following sections and complete
the accompanying tasks if you have not done so recently:
To upgrade a post office server:
2 Install the GroupWise 2014 software on the post office server.
See Chapter 24, “Installing the GroupWise 2014 Software,” on page 201 for instructions.
When the software installation is complete, the Installation Wizard displays the Installation
console in your web browser.
219
4 (Conditional) If the Installation console can locate existing post offices:
4a (Conditional) If there are any post offices on the post office server that you do not want to
upgrade, select them, then click Remove.
4b (Conditional) If you want to change the IP address or Admin port for any post office, click
its name to display the NetWork Information dialog box.
5 (Conditional) If the Installation console cannot locate existing post offices:
5a Click Add.
5b Browse to and select the post office folder.
220
5c Click OK, then review the POA IP address and post office Admin port that the Installation
5f (Conditional) If you want to upgrade additional post offices on the post office server, repeat
Step 5a through Step 5e.
6 In the list of post offices to upgrade, click Next to display the Credentials page.
221
9 (Optional) Click the Existing Configuration slide-out to list all upgraded domains and post
offices.
To finish the upgrade process, you must restart the POAs for all upgraded post offices on the
post office server.
222
13 To restart the POA in the upgraded post office:
,
NOTE: You can conveniently open the POA console on the Overview page by clicking
14 (Conditional) If the post office server has additional upgraded post offices, repeat Step 13 for the
223
224
28
Upgrading GroupWise Agents and
Applications
28
 Section 28.1, “Upgrading the Document Viewer Agent,” on page 225
 Section 28.5, “Implementing SSL Encryption,” on page 229
28.1
Upgrading the Document Viewer Agent
DVAs on the same servers with POA are automatically upgraded along with the POAs. The
following situations require additional upgrade actions:
 If you installed additional DVAs on other servers, you must manually upgrade them. Stop the
existing DVA, then install and set up the GroupWise 2014 DVA. For instructions, see “Scaling
Your DVA Installation” in the GroupWise 2014 Administration Guide.
 If you were not using the DVA in your existing GroupWise system, you must run at least one
DVA in your GroupWise 2014 system. For instructions, see “Installing the DVA” in the
In all cases, in order to make the DVA appear in the Admin console, you must manually add a DVA
object. For instructions, see “Setting Up the DVA” in the GroupWise 2014 Administration Guide.
28.2
Upgrading GroupWise WebAccess
After you have upgraded a domain and a post office to GroupWise 2014, you can upgrade
WebAccess for that domain and post office. For information about upgrade issues that you should
consider, see Section 22.4, “WebAccess Upgrades,” on page 196.
IMPORTANT: The POA that the GroupWise 2014 WebAccess Application communicates with must
be configured for SOAP. A secure SSL connection between the POA and the WebAccess Application
is highly recommended.
 Section 28.2.1, “Preparing to Upgrade the WebAccess Application,” on page 226
 Section 28.2.2, “Installing the GroupWise 2014 WebAccess Application,” on page 226
 Section 28.2.3, “Clearing User Browser Caches to Display GroupWise 2014 WebAccess
Correctly,” on page 227
Upgrading GroupWise Agents and Applications
225
28.2.1
Preparing to Upgrade the WebAccess Application
If you are upgrading from GroupWise 2012 to GroupWise 2014, there are no WebAccess upgrade
issues. You can upgrade your WebAccess software whenever it is convenient as you upgrade your
GroupWise system. However, in order to use the WebAccess Application console, you must change
the way it is configured. For instructions, see “Using the WebAccess Application Console” in the
For a list of new features in GroupWise 2014 WebAccess, see Section 21.3.2, “GroupWise WebAccess
understand that the WebAccess Agent is no longer part of GroupWise. See “Understanding
WebAccess Updates” and “Updating GroupWise WebAccess” in the GroupWise 2012 Installation
Guide before you upgrade WebAccess from GroupWise 8 directly to GroupWise 2014.
28.2.2
Installing the GroupWise 2014 WebAccess Application
1 (Conditional) If you are upgrading from GroupWise 8:
1a Prepare the POA to work successfully with the WebAccess Application, as described in the
following sections in “Post Office Agent” in the GroupWise 2014 Administration Guide:
 “Supporting SOAP Clients”
 “Securing the Post Office with SSL Connections to the POA”
1b Stop the existing WebAccess Agent.
2 (Conditional) On Linux, stop Tomcat.
OES 11:
SLES 11:
rcnovell-tomcat6 stop
rctomcat6 stop
On Windows, the Installation Wizard does this for you.
3 To upgrade WebAccess to GroupWise 2014, follow the standard installation instructions in
Chapter 16, “Setting Up GroupWise WebAccess,” on page 113.
IMPORTANT: If more than one web-based GroupWise component (WebAccess, Calendar
Publishing Host, and/or Monitor) is installed on the same server, you must upgrade all webbased GroupWise components at the same time. After one existing web-based component has
been upgraded to GroupWise 2014, other web-based components on the server do not work
until they also are upgraded to GroupWise 2014.
4 Reconfigure the WebAccess Application console.
For instructions, see “Enabling the WebAccess Application Console” in the GroupWise 2014
5 (Conditional) If you are upgrading from GroupWise 8, complete the steps in “Cleaning Up the
WebAccess Server after Updating to GroupWise 2012” and “Updating Access Control for
WebAccess Users” in the GroupWise 2012 Installation Guide.
6 Continue with Clearing User Browser Caches to Display GroupWise 2014 WebAccess Correctly.
226
28.2.3
Clearing User Browser Caches to Display GroupWise 2014 WebAccess
Correctly
After you have upgraded the WebAccess Application to GroupWise 2014, notify your GroupWise
WebAccess users that they should clear their browser caches before logging into their mailboxes with
the upgraded version of GroupWise WebAccess. If old GroupWise WebAccess files are used from
users’ browser caches, they might not be compatible with the upgraded files from the web server. The
results can be unpredictable and undesirable.
28.3
Upgrading the Calendar Publishing Host
There are no Calendar Publishing Host upgrade issues. You can upgrade the Calendar Publishing
Host to GroupWise 2014 at any time after the POA that it communicates with has been upgraded.
However, in order to use the CalPub Host Admin console, you must change the way it is configured.
For instructions, see Section 17.5.4, “Setting Up Calendar Publishing Administration,” on page 149.
For a list of improved functionality in the GroupWise 2014 Calendar Publishing Host, see
Section 21.3.4, “Calendar Publishing Enhancements,” on page 191.
 Section 28.3.1, “Installing the GroupWise 2014 Calendar Publishing Host Application,” on
page 227
 Section 28.3.2, “Clearing User Browser Caches to Display Published Calendars Correctly,” on
page 228
28.3.1
Installing the GroupWise 2014 Calendar Publishing Host Application
OES 11:
SLES 11:
rctomcat6 stop
2 To upgrade the Calendar Publishing Host to GroupWise 2014, follow the standard installation
instructions in Chapter 17, “Setting Up the GroupWise Calendar Publishing Host,” on page 131.
3 Reconfigure the CalPub Host Admin console.
For instructions, see Section 17.5.4, “Setting Up Calendar Publishing Administration,” on
page 149.
Calendar Publishing Host Server after Updating to GroupWise 2012” in the GroupWise 2012
Installation Guide.
5 Continue with Clearing User Browser Caches to Display Published Calendars Correctly.
227
28.3.2
Clearing User Browser Caches to Display Published Calendars
Correctly
After you have upgraded the Calendar Publishing Host Application to GroupWise 2014, notify your
GroupWise users that they should clear their browser caches before accessing published calendars. If
old Calendar Publishing files are used from users’ browser caches, they might not be compatible with
the upgraded files from the web server. The results can be unpredictable and undesirable.
External users of published calendars might not see some aspects of the GroupWise 2014 Calendar
Publishing interface until after they clear their browser caches.
28.4
Upgrading GroupWise Monitor
After you have upgraded at least one domain to GroupWise 2014, you can upgrade GroupWise
Monitor. For information about upgrade issues that you should consider, see Section 22.2, “Agent
Upgrades,” on page 195.
 Section 28.4.1, “Preparing to Upgrade GroupWise Monitor,” on page 228
 Section 28.4.2, “Installing the Monitor Software,” on page 228
 Section 28.4.3, “Clearing Browser Caches to Display GroupWise 2014 Monitor Correctly,” on
page 229
 Section 28.4.4, “Reconfiguring the GroupWise High Availability Service,” on page 229
28.4.1
Preparing to Upgrade GroupWise Monitor
GroupWise Monitor is not dependent on any other GroupWise agents, so you can upgrade the
Monitor Agent and the Monitor Application to GroupWise 2014 at any time.
understand that Monitor no longer relies on eDirectory objects for its configuration information. All
configuration information is located in the gwmonitor.cfg file instead. See “Understanding Monitor
Updates” and “Updating GroupWise Monitor”in the GroupWise 2012 Installation Guide before you
upgrade Monitor from GroupWise 8 directly to GroupWise 2014.
28.4.2
Installing the Monitor Software
1 Stop the existing Monitor Agent.
OES 11:
SLES 11:
rctomcat6 stop
3 To upgrade Monitor to GroupWise 2014, follow the standard installation instructions in
Chapter 18, “Setting Up GroupWise Monitor,” on page 157.
228
4 Restart all GroupWise services on the server.
Monitor Server after Updating to GroupWise 2012” in the GroupWise 2012 Installation Guide.
6 Continue with Clearing Browser Caches to Display GroupWise 2014 Monitor Correctly.
28.4.3
Clearing Browser Caches to Display GroupWise 2014 Monitor
Correctly
After you have upgraded the Monitor Application to GroupWise 2014, clear your browser cache
before accessing the upgraded version of GroupWise Monitor. If old GroupWise Monitor files are
used from users’ browser caches, they might not be compatible with the upgraded files from the web
server. The results can be unpredictable and undesirable.
28.4.4
Reconfiguring the GroupWise High Availability Service
On Linux, the GroupWise High Availably Service (gwha), that works in conjunction with GroupWise
Monitor to automatically restart the Linux GroupWise agents, now requires an additional file. The
gwha.allow file lists the user that the High Availability Service uses to log in to the Monitor Agent.
This file increases the security of the interaction between the High Available Service and the Monitor
Agent. For setup instructions, see Step 3 in “Creating a GroupWise High Availability Service User”
on page 101.
28.5
Implementing SSL Encryption
If you have not yet implemented SSL in your GroupWise system, you can now easily generate selfsigned certificates by using the native GroupWise certificate authority (CA). For instructions, see
“Using a Self-Signed Certificate from the GroupWise Certificate Authority” in the GroupWise 2014
229
230
29
Upgrading Users’ GroupWise Client
Software
29
After a post office is upgraded to GroupWise 2014, users who have accounts in that post office can
start using the GroupWise 2014 clients. You can give users access to a GroupWise 2014 software image,
so that they can install the GroupWise client themselves, or you can use the other methods of client
software distribution described in “Distributing the GroupWise Client” in the GroupWise 2014
The GroupWise 2014 client is available as part of the Linux GroupWise 2014 software image. For more
information about installing the GroupWise 2014 client from a Linux server, see Section 19.3.2,
“Installing the GroupWise Client from the Linux GroupWise 2014 Software Image,” on page 180.
Upgrading Users’ GroupWise Client Software
231
232
30
Transitioning from ConsoleOne
30
Use the table below to learn how to perform familiar ConsoleOne tasks in the GroupWise Admin
console.
Task
ConsoleOne Functionality
Admin Console Functionality
Locate a domain or post
office to edit its properties.
Use the eDirectory View to browse the Click Domains or Post Offices in the
eDirectory tree structure to find the
Administration panel to list the Domain
Domain or Post Office object.
or Post Office objects in your
GroupWise system.
or
or
Use the GroupWise View to list the
Domain or Post Office objects in your Click the domain or post office on the
GroupWise system.
System Overview page.
or
Type the name of the domain or post
office in the Global Search field.
Locate a user to edit its
properties.
Locate an agent to edit its
properties.
Use the eDirectory View to browse the Click Users in the Administration panel
to list the User objects in your
User object.
GroupWise system.
or
or
User objects in your GroupWise
system.
Type the user’s first name, last name,
GroupWise user name, email address,
or file ID (FID) in the Global Search
field.
Use the eDirectory View to browse the Click the agent type in the
Administration panel to list the agent
agent object.
objects of that type in your GroupWise
system.
or
or
agent objects in your GroupWise
Click the agent on the System Overview
system.
page.
or
Type the agent’s IP address in the
Global Search field.
Transitioning from ConsoleOne
233
Task
ConsoleOne Functionality
Perform GroupWise system Click Tools > GroupWise System
operations.
Operations.
Admin Console Functionality
Click System in the Administration
panel.
or
Type the name of the GroupWise
system tool in the Global Search field.
Run GroupWise utilities.
Click Tools > GroupWise Utilities.
Click System in the Administration
panel.
or
Type the name of the GroupWise
system tool in the Global Search field.
Perform database
maintenance.
Browse to and select a Domain or Post Display the properties of a domain or
Office object, then click Tools >
post office, then click Maintenance >
GroupWise Utilities > System
System Maintenance.
Maintenance.
Perform Mailbox/Library
Maintenance.
Browse to and select a Post Office or
User object, then click Tools >
GroupWise Utilities > System
Maintenance.
Set Client Options.
Browse to and select a Domain, Post
Display the properties of a domain, post
Office, or User object, then click Tools office, or user, then click Client Options.
> GroupWise Utilities > Client Options.
Display the properties of a post office or
user, then click Maintenance > Mailbox/
Library Maintenance.
If parts of your GroupWise system are still running legacy GroupWise agents, you should continue to
use the legacy ConsoleOne and its snap-ins to administer the legacy parts of your GroupWise system.
For convenience, you can safely run the GroupWise 2012 ConsoleOne and snap-ins on most of the
legacy parts of your GroupWise system. However, the GroupWise 2012 snap-ins do not support
specific legacy GroupWise functionality, such as the WebAccess Agent and its eDirectory objects,
which no longer exist in GroupWise 2012.
When you are in the GroupWise 2014 Admin console, you can easily see which agents have not yet
been upgraded. Legacy agents that have not yet been upgraded to GroupWise 2014 are marked with
their GroupWise version.
234
31
Upgrading the GroupWise/Exchange
Coexistence Solution
31
If you installed the GroupWise/Exchange Coexistence solution in your GroupWise 2012 system, you
must follow the instructions in “Configuring the MTA for Address Book Synchronization” in the
GroupWise/Exchange Coexistence Guide after you upgrade the MTA that synchronizes users between
GroupWise and Exchange. This enables you to see the external GroupWise objects in the GroupWise
Admin console.
No other changes to GroupWise or Exchange are required to continue using the GroupWise/
Exchange Coexistence solution with your GroupWise 2014 system.
Upgrading the GroupWise/Exchange Coexistence Solution
235
236
VI
Appendixes
VI
 Appendix A, “GroupWise Version Compatibility,” on page 239
 Appendix B, “Attributes, Operators, and Values for Object Filters,” on page 245
 Appendix C, “Invalid Characters in GroupWise Object Names and Email Addresses,” on
page 249
 Appendix D, “Cross-Platform Connections,” on page 251
 Appendix E, “Third-Party Materials,” on page 259
 Appendix F, “Documentation Updates,” on page 271
Appendixes
237
238
A
GroupWise Version Compatibility
A
Use the tables in this section to determine compatibility among the following GroupWise versions:
 Section A.1, “GroupWise 2014 with Earlier GroupWise Versions,” on page 239
 Section A.2, “GroupWise 2014 in a Cross-Platform Environment,” on page 242
For each GroupWise version, the tables indicate compatibility for:
 Administrative components: Domain and post office database platforms and versions,
eDirectory platforms, and GroupWise snap-ins to ConsoleOne platforms and versions.
 Agents: Domain and post office database platforms and versions, agent platforms and versions.
 Clients: Post office directory platforms and access, POA platforms and versions, client modes.
In the compatibility tables, cells with combinations that are not applicable are marked N/A. For
example, the POA never communicates with the Internet Agent, so that table cell is N/A.
For information about what operating system versions are supported for GroupWise 2014 on Linux
and Windows, refer to “GroupWise System Requirements” on page 25. For information about earlier
versions of GroupWise, refer to:
 GroupWise 2012 Installation Guide
 GroupWise 8 Installation Guide
A.1
GroupWise 2014 with Earlier GroupWise Versions
Select the GroupWise version that you want to determine GroupWise 2014 compatibility with:
 Section A.1.1, “Compatibility with GroupWise 2012,” on page 239
 Section A.1.2, “Compatibility with GroupWise 8,” on page 241
A.1.1
Compatibility with GroupWise 2012
 “GroupWise 2014 Administrative Components with GroupWise 2012” on page 240
 “GroupWise 2014 Agents with GroupWise 2012” on page 240
 “GroupWise 2014 Clients and POAs with GroupWise 2012” on page 240
239
GroupWise 2014 Administrative Components with GroupWise 2012
GroupWise 2014
Components
GW 2012 Objects in
GroupWise 2012
Domain and Post Office eDirectory
Databases
ConsoleOne + GW 2012
Snap-Ins
GW 2014 Domain and Post
Office Databases
N/A
N/A
Not Supported
GW 2014 Admin Console
Supported
Not Supported
Not Supported
Table Summary: The GroupWise Admin console can be used to access GroupWise 2012 databases
for domains and post offices, but GroupWise 2012 ConsoleOne with the GroupWise snap-ins should
not be used to access GroupWise 2014 databases. The Admin console does not access GroupWise
eDirectory objects. You must continue to use ConsoleOne with the GroupWise snap-ins to access
GroupWise objects in eDirectory.
GroupWise 2014 Agents with GroupWise 2012
GroupWise
2012 Domain
GroupWise 2014 and Post
Agents
Office
Databases
GW 2012
POA
GW 2012
MTA
GW 2012
GWIA
GW 2012
DVA
GW 2012
Monitor
Agent
GW 2014 Domain N/A
and Post Office
Databases
Not
Supported
Not
Supported
Not
Supported
N/A
N/A
GW 2014 POA
Supported
N/A
Supported
N/A
Supported
Supported
GW 2014 MTA
Supported
Supported
Supported
N/A
N/A
Supported
GW 2014 GWIA
Supported
N/A
Supported
N/A
N/A
Supported
GW 2014 DVA
N/A
Supported
N/A
N/A
N/A
N/A
GW 2014 Monitor N/A
Agent
Supported
Supported
Supported
N/A
N/A
Table Summary: GroupWise 2012 agents cannot access domain and post office databases that have
been upgraded to GroupWise 2014. When a GroupWise 2014 MTA or POA accesses an earlier
GroupWise database, it has no effect on the database. You must use the Installation console to
upgrade domain and post office databases to GroupWise 2014.
GroupWise 2014 Clients and POAs with GroupWise 2012
240
GroupWise 2012 Client
GroupWise 2012 POA
N/A
Not Supported
GroupWise 2014 POA
Supported
N/A
Table Summary: The GroupWise 2012 client can communicate with the GroupWise 2014 POA, but
the GroupWise 2014 client cannot communicate with the GroupWise 2012 POA. The general rule is
that earlier GroupWise clients can always communicate with later POAs, but later GroupWise clients
cannot communicate with earlier POAs.
A.1.2
Compatibility with GroupWise 8
 “GroupWise 2014 Administrative Components with GroupWise 8” on page 241
 “GroupWise 2014 Agents with GroupWise 8” on page 241
 “GroupWise 2014 Client with GroupWise 8” on page 242
GroupWise 2014 Administrative Components with GroupWise 8
GroupWise 2014
Components
GroupWise 8 Domain
and Post Office
Databases
GW 8 Objects in
eDirectory
ConsoleOne + GW 8
Snap-Ins
GW 2014 Domain and Post
Office Databases
N/A
N/A
Not Supported
GW 2014 Admin Console
Supported
Not Supported
Not Supported
Table Summary: The GroupWise Admin console can be used to access GroupWise 8 databases for
domains and post offices, but GroupWise 8 ConsoleOne with the GroupWise snap-ins should not be
used to access GroupWise 2014 databases. The Admin console does not access GroupWise eDirectory
objects. You must continue to use ConsoleOne with the GroupWise snap-ins to access GroupWise
objects in eDirectory.
GroupWise 2014 Agents with GroupWise 8
GroupWise 8
Domain and
GroupWise 2014 Post Office
Agents
Databases
GW 8 POA
GW 8 MTA
GW 8 GWIA
GW 8
GW 8
WebAccess Monitor
Agent
Agent
GW 2014 Domain N/A
and Post Office
Databases
Not
Supported
Not
Supported
Not Supported
N/A
N/A
GW 2014 POA
Supported
N/A
Supported
N/A
N/A
Supported
GW 2014 MTA
Supported
Supported
Supported
Supported
N/A
Supported
GW 2014 GWIA
Supported
N/A
Supported
N/A
N/A
Supported
GW 2014 DVA
N/A
N/A
N/A
N/A
N/A
N/A
Supported
Supported
Supported
N/A
N/A
GW 2014 Monitor N/A
Agent
Table Summary: GroupWise 8 agents cannot access domain and post office databases that have been
upgraded to GroupWise 2014. When a GroupWise 2014 MTA or POA accesses an earlier GroupWise
database, it has no effect on the database. You must use the Installation console to upgrade domain
and post office databases to GroupWise 2014.
241
The Document Viewer Agent (DVA) was introduced in GroupWise 2012 and so does not interact
with any GroupWise 8 agents. The WebAccess Agent that was part of GroupWise 8 was eliminated in
GroupWise 2012.
GroupWise 2014 Client with GroupWise 8
GroupWise 8 Client
GroupWise 8 POA
N/A
Not Supported
GroupWise 2014 POA
Supported
N/A
Table Summary: The GroupWise 8 Windows client can communicate with the GroupWise 2014
POA, but the GroupWise 2014 client cannot communicate with the GroupWise8 POA. The general
rule is that earlier GroupWise clients can always communicate with later POAs, but later GroupWise
clients cannot communicate with earlier POAs.
A.2
GroupWise 2014 in a Cross-Platform Environment
 Section A.2.1, “GroupWise 2014 Administrative Components and Databases,” on page 242
 Section A.2.2, “GroupWise 2014 Agents on Linux and Windows,” on page 242
A.2.1
GroupWise 2014 Administrative Components and Databases
Thanks to the web-based nature of the GroupWise Admin console, it does not matter what platform
GroupWise databases and agents are on, or where your browser is running, they successfully
communicate.
A.2.2
242
GroupWise 2014 Agents on Linux and Windows
GroupWise 2014
on Linux Agents
GroupWise
2014 Domain
or Post Office
Databases on
Windows
GW 2014
POA on
Windows
GW 2014
MTA on
Windows
GW 2014
GWIA on
Windows
GW 2014
DVA on
Windows
GW 2014
Monitor
Agent on
Windows
GW 2014 Domain
and Post Office
Databases on
Linux
N/A
Not
Supported
Not
Supported
N/A
N/A
N/A
GW 2014 POA on
Linux
Not Supported
N/A
Supported
N/A
Supported
Supported
GW 2014 MTA on
Linux
Not Supported
Supported
Supported
Supported
N/A
Supported
GW 2014 GWIA on N/A
Linux
N/A
Supported
N/A
N/A
Supported
GW 2014 DVA on
Linux
Supported
N/A
N/A
N/A
N/A
N/A
GroupWise 2014
on Linux Agents
GroupWise
2014 Domain
or Post Office
Databases on
Windows
GW 2014
POA on
Windows
GW 2014
MTA on
Windows
GW 2014
GWIA on
Windows
GW 2014
DVA on
Windows
GW 2014
Monitor
Agent on
Windows
GW 2014 Monitor
Agent on Linux
N/A
Supported
Supported
Supported
N/A
N/A
Table Summary: Domains and post offices can be located on Linux or Windows. Run the version of
the GroupWise agents that matches the platform where the domains and post offices are located.
Agents on either platform can communicate with other agents regardless of platform.
243
244
B
Attributes, Operators, and Values
for Object Filters
B
In general terms, a filter selects data. In any list of objects, you can use a filter in the Search field to
select and list GroupWise object data based on object attributes and operators.
 Section B.1, “Attributes,” on page 245
 Section B.2, “Logical Operators,” on page 246
 Section B.3, “Grouping Operators,” on page 247
 Section B.4, “Wildcard Characters,” on page 247
 Section B.5, “Literal Values,” on page 247
 Section B.6, “Date Specifications,” on page 248
B.1
Attributes
To list the attributes that you can filter on for any object type, press Ctrl-Spacebar in the Search field of
the object list. Common attributes that you might want to filter on include the following:
Object
Common Attributes
Domain
domainversion
lockoutoldadmin
minimumadminreleasedate
minimumadminreleaseversion
Post Office
clientlockout
clientlockoutdate
clientlockoutversion
disabledlogins
intruderdetection
postofficeversion
User
allowedaddressformats
lastclientlogintime
logindisabled
mailboxicensetype
mailboxsizemb
preferredemailid
visibility
Attributes, Operators, and Values for Object Filters
245
Object
Common Attributes
POA
clientserverthreads
imapenabled
maintenancehandlerthreads
messagehandlerthreads
soapenabled
MTA
defaultroutingdomain
loglevel
platform
syncldapservername
trackadminmessages
For an exhaustive list of attributes and their possible values, display the following URL on the Admin
Service server:
https://admin_service_address:9710/gwadmin-service/list/object_type/schema
Replace admin_service_address with the IP address or DNS hostname of a server where the
Admin Service is installed.
Replace object_type with any of the following object types, depending on what you want to list:
 domain
 post_office
 user
 group
 resource
 nickname
 poa
 mta
 gwia
 library
 ldap_server
B.2
Logical Operators
Spaces around the operators are optional.
246
Operator
Meaning
Example
=
Equal
lastname = smith
!=
Not equal
visibility != system
>
Greater than
mailboxsizemb > 500
<
Less than
mtpport < 2000
>=
Greater than or equal to soapthreads >= 10
B.3
Operator
Meaning
Example
<=
Less than or equal to
physicalconnections <= 1000
Grouping Operators
B.4
Operator
Meaning
Example
&, and
Conjunction
firstname = john & lastname = smith
firstname = john and lastname = smith
|, or
Disjunction
lastname = smith | lastname = jones
lastname = smith or lastname = jones
!, not
Inversion
! (lastname = smith | lastname = jones)
not (lastname = smith or lastname = jones)
()
Parentheses
lastname = smith & (firstname = john | firstname = jill)
lastname = smith and (firstname = john or firstname = jill)
Wildcard Characters
The match operator must be used with wildcard characters. The string to match must be surrounded
by single quote marks.
B.5
Characters
Meaning
Example
*
Zero or more characters lastname match ‘sm*’
?
One character
lastname match ‘sm?th’
Literal Values
Value
Explanation
Example
null
Empty
internetdomainname != null
minimumadminreleasedate != null
preferredaddressformat != null
true, 1
Enabled or set
logindisabled = true
logindisabled = 1
false, 0
Disabled or not set
soapenabled = false
soapenabled = 0
Attributes, Operators, and Values for Object Filters
247
B.6
Date Specifications
You can filter on one specific date or on a range of dates that are relative to today.
248
Format
Explanation
Example
yyyy-mm-ddTmm:ss
Literal date
2014-01-01T00:00
timelastmod > now(time_unit)
Modified now (current time stamp on server)
Modified in the last day
Modified in the last 2 weeks
Modified in the last three months
Modified in the last year
timelastmod > now()
timelastmod > now(-1)
timelastmod > now(-2, weeks)
timelastmod > now(-3, months)
timelastmod > now(-1, year)
C
Invalid Characters in GroupWise
Object Names and Email Addresses
C
Although most characters in the languages supported by GroupWise can be used in GroupWise
object names and Internet email addresses, some cannot.
 Section C.1, “Invalid Characters in GroupWise Object Names,” on page 249
 Section C.2, “Invalid Characters in Internet Email Addresses,” on page 250
C.1
Invalid Characters in GroupWise Object Names
Do not use any of the following invalid characters in GroupWise object names:
 Space (use underscore instead)
 ASCII characters 0-31
 Extended ASCII characters that are graphical or typographical symbols
Accented characters in the extended range can be used in GroupWise object names.
 Asterisk *
 At sign @
 Backslash \
 Braces { }
 Colon :
 Comma ,
 Double quote "
 Parentheses ( )
 Period .
In addition to the characters listed above, do not use any of the following invalid characters in Agent
objects names:
 Exclamation mark !
 Semicolon ;
 Single quote '
Invalid Characters in GroupWise Object Names and Email Addresses
249
C.2
Invalid Characters in Internet Email Addresses
Characters that are valid and even desirable in the name of a user, group, or resource might not be
valid in an email address. Such invalid characters include spaces and certain accented and special
characters. (Providing a definitive list of such invalid characters is beyond the scope of the
GroupWise product documentation.)
In the names of users, groups, and resources, use underscores (_) rather than spaces as separators
between words in order to facilitate addressing across the Internet.
When an object name includes any character that is not valid in an email address, that object cannot
receive messages. For such an object, you must set up a preferred email ID in order to ensure that it
has a valid email address.
250
D
Cross-Platform Connections
D
If you want users to be able to install the GroupWise client software to Windows workstations from a
location on a Linux server, you must make the Linux server look like a Windows server from the
point of view of the workstations. There are a variety of ways to accomplish this. Samba is one of
them.
This section provides examples of how to use Samba to install the GroupWise client software from a
Linux server.
 Section D.1, “Setting up Samba on OES,” on page 251
 Section D.2, “Mapping a Drive to a Samba Share on an OES Server,” on page 254
 Section D.3, “Setting Up Samba on SLES,” on page 255
 Section D.4, “Mapping a Drive to a Samba Share on a SLES Server,” on page 256
D.1
Setting up Samba on OES
In order to access the GroupWise client software on a Linux server, you can set up a Samba share to
the client folder, either in the downloaded GroupWise 2014 software image or in the software
distribution folder, if you have created one on the Linux server.
 Section D.1.1, “Configuring NetWare Core Protocol (NCP),” on page 251
 Section D.1.2, “Installing Samba,” on page 252
 Section D.1.3, “Logging In to iManager,” on page 252
 Section D.1.4, “Creating a User to Manage the Samba Share,” on page 252
 Section D.1.5, “Configuring the eDirectory Universal Password for Samba,” on page 253
 Section D.1.6, “Setting the eDirectory Universal Password for the Samba Administrator User,”
on page 253
 Section D.1.7, “Creating a Samba Share,” on page 253
 Section D.1.8, “Setting the eDirectory Rights for the Samba Share,” on page 254
 Section D.1.9, “Testing Samba on the OES Server,” on page 254
D.1.1
Configuring NetWare Core Protocol (NCP)
1 In a terminal window on the OES server, become root by entering su - and the root password.
2 Enter the following command to create the NCP volume:
251
ncpcon create volume volume_name /folder
2a Replace volume_name with a unique name for the location of the GroupWise client
software.
2b Replace folder with the full path to the GroupWise client software, for example:
/opt/novell/groupwise/software/client
3 Verify that the volume has been created:
more /etc/opt/novell/ncpserv.conf
The new volume should be listed at the end of the NCP server configuration file.
4 Restart the Novell eDirectory daemon:
rcndsd restart
5 Continue with Installing Samba.
D.1.2
Installing Samba
If you installed Samba when you installed OES, skip to “Logging In to iManager” on page 252.
If you did not install Samba when you installed OES, install it now:
1 Start YaST.
2 Under Groups, click Open Enterprise Server, then click OES Install and Configuration.
3 Under OES Services, select Novell Samba, then click Accept.
4 Follow the prompts to install Novell Samba.
5 Continue with Logging In to iManager.
D.1.3
Logging In to iManager
1 Access the following URL:
https://ip_address/nps/servlet/webacc?taskid=fw Startup
Replace ip_address with the IP address of the OES server.
2 Specify the eDirectory administrator user name, such as admin.users.novell, the password for
the user name, and the IP address of the eDirectory tree, then click Login.
3 Continue with Creating a User to Manage the Samba Share.
D.1.4
Creating a User to Manage the Samba Share
1 In iManager, click Users > Create User.
2 In the Username field, specify a unique user name for accessing the Samba share from Windows,
such as gwclient.
3 In the Last name field, provide a last name (this is a required field).
4 In the Context field, browse to and click the eDirectory context where you want to create the new
User object.
5 Type and confirm the password for the new user.
252
IMPORTANT: Any users who map a drive to the Samba share need to know this user name and
password in order to map the drive.
6 Click OK to create the Samba user for the GroupWise client Samba share.
7 Click Users to close the Users menu.
8 Continue with Configuring the eDirectory Universal Password for Samba.
D.1.5
Configuring the eDirectory Universal Password for Samba
1 Click Passwords > Password Policies.
2 Click Samba Default Password Policy.
3 On the Policy Assignment tab, browse to and click the name of the Samba User object that you
created in “Creating a User to Manage the Samba Share” on page 252, then click OK to add the
user to the list.
4 Click OK to complete the process.
5 Continue with Setting the eDirectory Universal Password for the Samba Administrator User.
D.1.6
Setting the eDirectory Universal Password for the Samba
Administrator User
1 Under Passwords, click Set Universal Password.
2 Browse to and click the name of the Samba User object, then click OK.
3 Specify the password for the Samba user, retype the password for confirmation, then click OK.
4 Click Passwords to close the Passwords menu.
5 Continue with Creating a Samba Share.
D.1.7
Creating a Samba Share
1 Click File Protocols, then click Samba.
2 Browse to and click the name of the Server object where you are setting up the Samba share.
3 On the Shares tab, create a new Samba share for the client folder on the Linux server:
3a Click New.
3b Specify a unique name for the Samba share, such as gwclient.
3c Specify the full path name to the client folder on the Linux server, for example:
/opt/novell/groupwise/software/client
3d Select Read-Only.
Write access is not required in order to install the GroupWise client software from the Linux
server.
3e Click OK to add the location to the list of Samba shares, then click Close.
3f Click File Protocols to close the File Protocols menu.
4 Continue with Setting the eDirectory Universal Password for the Samba Administrator User.
253
D.1.8
Setting the eDirectory Rights for the Samba Share
1 Click Files and Folders, then click Properties.
2 Browse to and click the name of the Linux partition or folder where you created the new share,
then click OK.
3 Click Rights.
4 In the Add Trustee field, browse to and click the name of the Samba User object, then click OK.
5 Under Inherited Rights Filter, select Read, then click OK.
6 Continue with Testing Samba on the OES Server.
D.1.9
Testing Samba on the OES Server
1 Double-click the Home Directory icon on the Linux desktop.
2 Click
3 In the Location field, type smb://user_name@ip_address
3a Replace user_name with the user name of the Samba administrator user.
3b Replace ip_address with the IP address of the Linux server.
The File Browser should display all Samba shares, including the new one that you created
for the GroupWise client software.
4 Return to Step 3 in Section 19.3.2, “Installing the GroupWise Client from the Linux GroupWise
2014 Software Image,” on page 180.
D.2
Mapping a Drive to a Samba Share on an OES Server
1 On the Windows server, right-click
on the Windows taskbar, then click Novell Map Network
Drive.
2 Select the drive letter to map to the NCP volume on the OES server.
3 Specify the network path to the NCP volume in the following format:
\\linux_hostname\ncp_volume
3a Replace linux_hostname with the hostname of the OES server.
3b Replace ncp_volume with the name of the NCP volume that you just created.
4 For the network user name, specify the fully qualified Samba user name for eDirectory, such as
gwclient.users.novell.
5 Click Map.
6 Click OK.
The mapped drive to the OES server opens in Windows Explorer and can now be accessed from
Windows.
254
D.3
Setting Up Samba on SLES
In order to access the GroupWise client software on a Linux server, you can set up a Samba share on
the Linux server to the client folder, either in the downloaded GroupWise 2014 software image or in
the software distribution folder, if you have created one on the Linux server.
 Section D.3.1, “Preparing Your Firewall to Allow Samba Connections,” on page 255
 Section D.3.2, “Configuring the Samba Server,” on page 255
 Section D.3.3, “Configuring the Samba Web Administration Tool (SWAT),” on page 255
 Section D.3.4, “Accessing SWAT,” on page 256
 Section D.3.5, “Setting the Samba User Name and Password,” on page 256
 Section D.3.6, “Creating a Samba Share,” on page 256
D.3.1
Preparing Your Firewall to Allow Samba Connections
1 In YaST, click Firewall, then click Interfaces.
2 Click Change, select Internal Zone, then click OK.
3 Click Next to view the summary, then click Finish.
4 Continue with Configuring the Samba Server.
D.3.2
Configuring the Samba Server
1 In YaST, click Network Services > Samba Server.
2 Specify a workgroup or domain name, then click Next.
For use in your GroupWise system, the Samba server does not need to be part of a workgroup or
domain, so it does not matter what you put in this field. For example, you could use
GWCLIENT.
3 Select Not a Domain Controller, then click Next.
For use in your GroupWise system, the Samba server does not need to be a domain controller.
4 Under Service Start, select During Boot.
Because you prepared the firewall in “Preparing Your Firewall to Allow Samba Connections” on
page 255, the Firewall Settings section shows that the firewall port for Samba is already open.
5 Click OK to finish the basic configuration of the Samba server.
6 Continue with Configuring the Samba Web Administration Tool (SWAT).
D.3.3
Configuring the Samba Web Administration Tool (SWAT)
1 In YaST, click Network Services > Network Services (xinetd).
2 Select Enable.
3 In the Currently Available Services list, select swat, then click Toggle Status (On or Off).
SWAT is off by default; this turns it on.
4 Click Finish.
5 Continue with “Accessing SWAT” on page 256.
255
D.3.4
Accessing SWAT
1 Display SWAT in your web browser with the following URL:
http://localhost:901
2 Specify the root user name and password, then click OK.
3 On the SWAT toolbar, click Status to verify that smbd and nmbd are running.
It is not necessary for winbindd to be running.
4 Continue with Setting the Samba User Name and Password.
D.3.5
Setting the Samba User Name and Password
1 On the SWAT toolbar, click Password.
2 In the User Name field, specify a unique user name for use when mapping a drive to the Samba
share, such as gwclient.
3 Type and confirm the password for the new user, then click Add User.
IMPORTANT: Any users who map a drive to the Samba share need to know this user name and
password in order to map the drive.
4 Continue with Creating a Samba Share.
D.3.6
Creating a Samba Share
1 On the SWAT toolbar, click Shares.
2 In the Create Share field, type a unique name for the share, such as gwclient, then click Create
Share.
3 In the Path field, specify the full path name to the client folder on the Linux server.
4 Leave the Read Only field set to the default of Yes.
Write access is not required in order to install the GroupWise client software from the Linux
server.
5 In the Available field, select Yes.
6 Click Commit Changes.
The Samba share on the Linux server is now ready for access from a Windows workstation.
D.4
Mapping a Drive to a Samba Share on a SLES Server
1 In Windows Explorer, right-click the Computer object, then click Map network drive.
2 In the Drive field, select the drive letter for the new Samba share.
3 In the Folder field, specify the location of the Samba share in the following format:
256
\\ip_address\share_name
3a Replace ip_address with the IP address of the Linux server.
3b Replace share_name with the name of the new Samba share where the GroupWise client
software is available.
4 Deselect Reconnect to logon.
5 Select Connect using different credentials.
6 Specify the Samba share user name and password, then click OK.
The Samba share for the OES file system opens in Windows Explorer and can now be accessed
from Windows.
257
258
E
E
The following third-party software is included in Novell GroupWise 2014:
 Section E.1, “Apache,” on page 259
 Section E.2, “BLT,” on page 260
 Section E.3, “GD Graphics Library,” on page 260
 Section E.4, “getopt.h,” on page 261
 Section E.5, “iCal4j - License,” on page 262
 Section E.6, “ICU License - ICU 1.8.1 and Later,” on page 262
 Section E.7, “JRE,” on page 263
 Section E.8, “NET-SNMP Open Source Package,” on page 263
 Section E.9, “ODMA 2.0,” on page 265
 Section E.10, “OpenLDAP,” on page 266
 Section E.11, “OpenSSL,” on page 267
 Section E.12, “Oracle Outside In Technology,” on page 268
 Section E.13, “Python 2.2,” on page 269
 Section E.14, “Yahoo! UI Library,” on page 269
E.1
Apache
The Apache Software License, Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All
rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The end-user documentation included with the redistribution, if any, must include the following
acknowledgment:
“This product includes software developed by the Apache Software Foundation (http://
www.apache.org/).”
Alternately, this acknowledgment may appear in the software itself, if and wherever such thirdparty acknowledgments normally appear.
259
4. The names “Apache” and “Apache Software Foundation” must not be used to endorse or
promote products derived from this software without prior written permission. For written
permission, please contact [email protected].
5. Products derived from this software may not be called “Apache”, nor may “Apache” appear in
their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED `ÀS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache
Software Foundation. For more information on the Apache Software Foundation, please see <http://
www.apache.org/>.
Portions of this software are based upon public domain software originally written at the National
Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
E.2
BLT
Copyright 1993-1998 Lucent Technologies, Inc.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appear in all copies and
that both that the copyright notice and warranty disclaimer appear in supporting documentation,
and that the names of Lucent Technologies any of their entities not be used in advertising or publicity
pertaining to distribution of the software without specific, written prior permission.
Lucent Technologies disclaims all warranties with regard to this software, including all implied
warranties of merchantability and fitness. In no event shall Lucent Technologies be liable for any
special, indirect or consequential damages or any damages whatsoever resulting from loss of use,
data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or
in connection with the use or performance of this software.
E.3
GD Graphics Library
Portions copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 by Cold Spring
Harbor Laboratory. Funded under Grant P41-RR02188 by the National Institutes of Health.
Portions copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 by Boutell.Com, Inc.
Portions relating to GD2 format copyright 1999, 2000, 2001, 2002, 2003, 2004 Philip Warner.
Portions relating to PNG copyright 1999, 2000, 2001, 2002, 2003, 2004 Greg Roelofs.
Portions relating to gdttf.c copyright 1999, 2000, 2001, 2002, 2003, 2004 John Ellson
([email protected]).
Portions relating to gdft.c copyright 2001, 2002, 2003, 2004 John Ellson ([email protected]).
260
Portions relating to JPEG and to color quantization copyright 2000, 2001, 2002, 2003, 2004, Doug
Becker and copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Thomas G.
Lane. This software is based in part on the work of the Independent JPEG Group. See the file
README-JPEG.TXT for more information.
Portions relating to GIF compression copyright 1989 by Jef Poskanzer and David Rowley, with
modifications for thread safety by Thomas Boutell.
Portions relating to GIF decompression copyright 1990, 1991, 1993 by David Koblas, with
modifications for thread safety by Thomas Boutell.
Portions relating to WBMP copyright 2000, 2001, 2002, 2003, 2004 Maurice Szmurlo and Johan Van
den Brande.
Permission has been granted to copy, distribute and modify gd in any context without fee, including
a commercial application, provided that this notice is present in user-accessible supporting
documentation.
This does not affect your ownership of the derived work itself, and the intent is to assure proper
credit for the authors of gd, not to interfere with your productive use of gd. If you have questions,
ask. “Derived works” includes all programs that utilize the library. Credit must be given in useraccessible documentation.
This software is provided “AS IS.” The copyright holders disclaim all warranties, either express or
implied, including but not limited to implied warranties of merchantability and fitness for a
particular purpose, with respect to this code and accompanying documentation.
Although their code does not appear in the current release, the authors also wish to thank Hutchison
Avenue Software Corporation for their prior contributions.
E.4
getopt.h
Copyright (c) 2000 The NetBSD Foundation, Inc. All rights reserved.
This code is derived from software contributed to The NetBSD Foundation by Dieter Baron and
Thomas Klausner.
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement:
This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
4. Neither the name of The NetBSD Foundation nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
261
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
E.5
iCal4j - License
Copyright (c) 2012, Ben Fortuna
All rights reserved.
 Redistributions of source code must retain the above copyright notice, this list of conditions and
 Redistributions in binary form must reproduce the above copyright notice, this list of conditions
distribution.
 Neither the name of Ben Fortuna nor the names of any other contributors may be used to
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
E.6
ICU License - ICU 1.8.1 and Later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2006 International Business Machines Corporation and others
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the Software and that both the
above copyright notice(s) and this permission notice appear in supporting documentation.
262
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY
RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or
otherwise to promote the sale, use or other dealings in this Software without prior written
authorization of the copyright holder.
E.7
JRE
JRE Note
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are
available at http://oss.software.ibm.com/icu4j/.
E.8
NET-SNMP Open Source Package
 Section E.8.1, “---- Part 1: CMU/UCD copyright notice: (BSD like) -----,” on page 263
 Section E.8.2, “---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----,” on
page 264
 Section E.8.3, “---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----,” on page 264
 Section E.8.4, “---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----,” on page 265
E.8.1
---- Part 1: CMU/UCD copyright notice: (BSD like) ----Copyright 1989, 1991, 1992 by Carnegie Mellon University Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appears in all copies and
that both that copyright notice and this permission notice appear in supporting documentation, and
that the name of CMU and The Regents of the University of California not be used in advertising or
publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE
UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
263
E.8.2
---- Part 2: Networks Associates Technology, Inc copyright notice
(BSD) ----Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved.
distribution.
 Neither the name of the Networks Associates Technology, Inc nor the names of its contributors
may be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS”
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
E.8.3
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) ----Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved.
distribution.
 The name of Cambridge Broadband Ltd. may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
264
E.8.4
---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) ----Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.
Use is subject to license terms below.
This distribution may include materials developed by third parties.
Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
distribution.
 Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to
permission.
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
E.9
ODMA 2.0
OPEN DOCUMENT MANAGEMENT API LICENSE 1.0 ODMA 2.0 SPECIFICATIONS AND
SOFTWARE Copyright © 1994-1998 AIIM International
LICENSE:
Redistribution and use in source and binary forms, with or without modifications, are permitted
distribution.
 Neither the name of AIIM International nor the names of its contributors may be used to
permission.
265
DISCLAIMER:
CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO, PROCUREMENT OF
ADDITIONAL INFORMATION:
 ODMA reference materials, software, and status: <http://ODMA.info>
 Information about this ODMA License and its application: <http://DMare.info/license/>
 Open Source Definition 1.9 and the BSD License (the model for this ODMA license): <http://
opensource.org>
 HTML (ISO 8859-1) version of this license: <http://Dmware.info/license/P040801F.htm>
E.10
OpenLDAP
The OpenLDAP Public License Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation (“Software”), with or without
modification, are permitted provided that the following conditions are met:
1 Redistributions in source form must retain copyright statements and notices,
2 Redistributions in binary form must reproduce applicable copyright statements and notices, this
list of conditions, and the following disclaimer in the documentation and/or other materials
provided with the distribution, and
3 Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished
by a version number. You may use this Software under terms of this license revision or under the
terms of any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS
`ÀS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS
CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
The names of the authors and copyright holders must not be used in advertising or otherwise to
promote the sale, use or other dealing in this Software without specific, written prior permission.
Title to copyright in this Software shall at all times remain with copyright holders.
266
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
E.11
OpenSSL
OpenSSL License Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved.
1 Redistributions of source code must retain the above copyright notice, this list of conditions and
2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions
distribution.
3 All advertising materials mentioning features or use of this software must display the following
acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/)”
4 The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote
products derived from this software without prior written permission. For written permission,
please contact [email protected].
5 Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear
in their names without prior written permission of the OpenSSL Project.
6 Redistributions of any form whatsoever must retain the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT `ÀS IS’’ AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
This product includes cryptographic software written by Eric Young ([email protected]). This
product includes software written by Tim Hudson ([email protected]).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.
This package is an SSL implementation written by Eric Young ([email protected]). The
implementation was written so as to conform with Netscape's SSL.
This library is free for commercial and non-commercial use as long as the following conditions are
adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is
covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).
267
Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be
removed. If this package is used in a product, Eric Young should be given attribution as the author of
the parts of the library used. This can be in the form of a textual message at program startup or in
documentation (online or textual) provided with the package.
1 Redistributions of source code must retain the copyright notice, this list of conditions and the
following disclaimer.
2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions
distribution.
3 All advertising materials mentioning features or use of this software must display the following
acknowledgement:
“This product includes cryptographic software written by Eric Young ([email protected])”
The word “cryptographic” can be left out if the routines from the library being used are not
cryptographic related :-).
4 If you include any Windows specific code (or a derivative thereof) from the apps directory
(application code) you must include an acknowledgement:
“This product includes software written by Tim Hudson ([email protected])”
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG `ÀS IS’’ AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publicly available version or derivative of this code cannot
be changed; i.e. this code cannot simply be copied and put under another distribution licence
[including the GNU Public Licence.]
E.12
Oracle Outside In Technology
Oracle shall inform you of any notices and other instructions that are related to third party
components (including open source software) that are included in a program and/or hardware and
that Oracle is required to distribute with such programs and/or hardware. These notices and other
instructions shall be provided to you in at least one of the following ways, at Oracle’s sole discretion:
(a) automatically installed with the programs or in the installation details; (b) in the program
documentation; (c) in the readme files or notice files; or (d) via a supplemental list.
You shall comply with all instructions related to third party software components (including open
source software). If you reproduce the programs, operating system and/or integrated software, you
shall reproduce all third party notices in an appropriate location in the reproduction and/or in its
related documentation and include any associated source code (to the extent such source code is
provided by Oracle), as required by the applicable notices or as otherwise directed by Oracle.
268
E.13
Python 2.2
Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights
reserved.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear in supporting documentation, and
that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity
pertaining to distribution of the software without specific, written prior permission.
STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY
SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
E.14
Yahoo! UI Library
Yahoo! UI Library uses the BSD License which states:
Software License Agreement (BSD License)
Copyright (c) 2006, Yahoo! Inc.
Redistribution and use of this software in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
distribution.
 Neither the name of Yahoo! Inc. nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission of
Yahoo! Inc.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
269
270
F
Documentation Updates
F
This section lists updates to the GroupWise 2014 Installation Guide that have been made since the initial
release of GroupWise 2014. The information helps you to keep current on documentation updates
and, in some cases, software updates (such as a Support Pack release).
The information is grouped according to the date when the GroupWise 2014 Installation Guide was
republished. Within each dated section, the updates are listed by the names of the main table of
contents sections.
The GroupWise 2014 Installation Guide has been updated on the following dates:
 Section F.1, “July 28, 2014 (GroupWise 2014 SP1),” on page 271
F.1
July 28, 2014 (GroupWise 2014 SP1)
Location
Change
System
Chapter 25, “Upgrading the
Primary Domain Server,” on
page 205
Corrected the order of steps in the upgrade procedure.
Documentation Updates
271
272

Installation Guide GroupWise 2014 November 2014 www.novell.com/documentation

Transcription

Similar documents

How to use the Address Book

Kelly Order Form

How to Activate Your Smartphone to Sync with GroupWise

HOW TO ACCESS GROUPWISE “REMOTELY”

Note: To view a listing of the document... Bookmarks

Quick Setup Guide

Attention All GSU Faculty and Staff Attention All GSU Faculty and Staff

Novell® GroupWise® 8