Installation
May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
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.
This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada.
Copyright © 1993-2001 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.
U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 5,963,938; 6,081,804; 6,138,170; 6,167,393; D393,457 and Patents Pending.
Novell, Inc. 1800 South Novell Place Provo, UT 84606 U.S.A. www.novell.com
Installation April 2001 104-001381-001
Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation.
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Novell Trademarks ConsoleOne is a trademark of Novell, Inc. GroupWise is a registered trademark of Novell, Inc., in the United States and other countries. IPX is a trademark of Novell, Inc. ManageWise is a registered trademark of Novell, Inc., in the United States and other countries. NDS is a registered trademark of Novell, Inc., in the United States and other countries. NetWare is a registered trademark of Novell, Inc., in the United States and other countries. NetWare Cluster Services is a trademark of Novell, Inc. NLM is a trademark of Novell, Inc. Novell is a registered trademark of Novell, Inc., in the United States and other countries. Novell Certificate Server is a trademark of Novell, Inc. Novell Client is a trademark of Novell, Inc. Novell Directory Services is a trademark of Novell, Inc. Novell Support Connection is a registered trademark of Novell, Inc., in the United States and other countries. Novell Technical Services is a service mark of Novell, Inc.
Third-Party Trademarks All third-party trademarks are the property of their respective owners.
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Contents
About this Guide 11 Trademark Conventions ...... 11 Additional Documentation ...... 11
Part I Installation 1 Installing a Basic GroupWise System 15 Planning Your Basic GroupWise System ...... 16 Determining Installation Locations ...... 16 Planning Your Domain ...... 21 Planning Your Post Office ...... 27 Planning Your GroupWise Agents ...... 31 Sample GroupWise Configurations...... 36 Summary of Requirements for a Basic GroupWise System ...... 38 Setting Up Your Basic GroupWise System ...... 41 Starting the GroupWise Installation Advisor ...... 42 Installing the GroupWise Software ...... 44 Providing System Information ...... 46 Creating the System ...... 48 Installing and Starting the GroupWise Agents ...... 50 Setting Up and Running the Client on Your Workstation ...... 62 Assigning GroupWise Accounts to Additional Users ...... 63 Setting Up Users' Workstations to Run the Client ...... 65 Other Things You Can Do ...... 65 Basic GroupWise System Worksheet ...... 67
2 Installing GroupWise Internet Agent 75 Overview ...... 75 GroupWise Internet Agent Features ...... 76 Ways to Use the GroupWise Internet Agent ...... 80 Preparing to Install the Internet Agent ...... 80 GroupWise System Prerequisites ...... 81 Information for the Internet Service Provider ...... 81 Performance Considerations ...... 82 Setting Up the Internet Agent for Windows NT/2000...... 83 Meeting System Requirements ...... 84 Installing the NT/2000 Internet Agent Software ...... 84 Setting Up Internet Services ...... 87 Assigning a Postmaster ...... 87 Setting Up DNS Integration...... 87 Starting the NT/2000 Internet Agent ...... 89
Contents 5
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Setting Up the Internet Agent NLM ...... 89 Meeting System Requirements ...... 89 Testing TCP/IP Functionality ...... 90 Installing the Internet Agent NLM Software ...... 91 Setting Up Internet Services ...... 93 Assigning a Postmaster ...... 93 Setting Up DNS Integration ...... 94 Verifying the HOSTS File ...... 95 Starting the Internet Agent NLM ...... 96
3 Installing GroupWise WebAccess 97 Planning GroupWise WebAccess ...... 98 GroupWise WebAccess Component Overview ...... 98 Deciding Where to Install the GroupWise WebAccess Components ...... 99 Determining the WebAccess Agent’s Configuration ...... 105 Determining the WebAccess and WebPublisher Applications’ Configuration ...... 110 Setting Up GroupWise WebAccess ...... 113 Establishing File System Rights and NDS Access Rights ...... 113 Shutting Down the Web Server and GroupWise Components ...... 114 Installing GroupWise WebAccess ...... 115 Starting GroupWise WebAccess...... 117 Testing GroupWise WebAccess ...... 118 Testing GroupWise WebPublisher...... 119 Other Things You Can Do ...... 119 GroupWise WebAccess Installation Worksheet ...... 120 WebAccess Agent and WebAccess/WebPublisher Applications ...... 120 WebAccess Agent ...... 121 WebAccess/WebPublisher Applications ...... 123
4 Installing GroupWise Monitor 125 Planning GroupWise Monitor ...... 125 GroupWise Monitor Overview ...... 126 Deciding Where to Install GroupWise Monitor ...... 127 Specifying Network Addresses ...... 128 Configuring GroupWise Monitor ...... 129 Locating Agents to Monitor ...... 129 Selecting the Web Server’s Default Web Page ...... 130 Selecting the Default Language ...... 130 Setting Up GroupWise Monitor ...... 130 Preparing to Install GroupWise Monitor ...... 131 Installing GroupWise Monitor ...... 131 Using GroupWise Monitor ...... 132 GroupWise Monitor Worksheet ...... 134
6 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
5 Installing GroupWise Agents 137 Selecting New Agent Locations and Platforms...... 137 Agent Location ...... 137 Agent Platform ...... 139 Configuring New Agent Objects in NDS ...... 139 Installing the NLM Agents ...... 140 Planning the NLM Agents ...... 140 Setting Up the NLM Agents...... 147 Installing the NT/2000 Agents ...... 150 Planning the NT/2000 Agents ...... 151 Setting Up the NT/2000 Agents ...... 156 Uninstalling the Agents...... 158 Agent Planning Worksheets ...... 159 NLM Agent Worksheet ...... 159 NT/2000 Agent Worksheet ...... 161
6 Installing the GroupWise Client 165 Determining Requirements...... 165 Installing the Client Software ...... 166 Starting the Client ...... 167
Part II Update 7 Understanding the Update Process 171 Extending the NDS Schema ...... 172 Installing the GroupWise Software ...... 172 Software Distribution Directory ...... 172 ConsoleOne ...... 173 Administration Agent ...... 173 Updating GroupWise Domain and Post Office Databases ...... 173 Updating the GroupWise Client ...... 174 Updating the GroupWise Internet Agent ...... 175 Updating GroupWise WebAccess ...... 175 WebAccess Agent ...... 175 WebAccess Components on the Web Server ...... 176 Using GroupWise Gateways ...... 176
8 Preparing Your GroupWise System 177 9 Updating Your GroupWise System 179 Installing the GroupWise 6 Software ...... 179 Updating the Primary Domain ...... 183 Updating Post Offices ...... 193 Installing and Starting the POA ...... 193 Copying the GroupWise Views to the Post Office Directory ...... 194
Contents 7
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Updating Users' GroupWise Clients ...... 195 Users’ Software Distribution Directory Already Updated...... 195 Users’ Software Distribution Directory Requires Updating...... 196 Updating Secondary Domains...... 198 Updating the GroupWise Internet Agent ...... 198 Updating GroupWise WebAccess ...... 198
Part III Appendixes A Manually Creating the NDS Object for the Internet Agent 201 Creating the Object ...... 201 Defining Properties for the Object ...... 204
B What’s New in GroupWise 6 207 GroupWise Administration...... 207 Full ConsoleOne Administration ...... 208 Smarter Backup and Restore ...... 208 Disk Space Management for Mailboxes ...... 208 Faster Mailbox/Library Maintenance...... 208 More Accessible GroupWise Check ...... 209 More Efficient Move User ...... 209 GroupWise Agents ...... 209 Optimization for NetWare Cluster Services ...... 210 More Powerful Agent Web Consoles ...... 210 Faster Message Transfer Protocol...... 210 Mailbox Size Monitoring and Enforcement ...... 210 Message Size Restriction ...... 210 Disk Space Management for Post Offices ...... 210 GroupWise Client ...... 211 NNTP Newsgroup Accounts ...... 211 POP3/IMAP4 Account Import ...... 212 Multiple Account Signatures ...... 212 Client Caching Mode...... 212 Mailbox Mode Switching ...... 212 Disk Space Management for Client Users’ Mailboxes ...... 212 Backup and Restore to Retrieve Deleted Items ...... 213 More Secure Messaging ...... 213 Calendar Printing Enhancements ...... 214 Remote Mode Enhancements ...... 215 Address Book Enhancements ...... 215 Improved Notification ...... 216 Improved Rules ...... 216 Improved Forwarding ...... 217 New Send, Accept, Decline, Forward, and Reply Buttons...... 217 Windows Time Zone Setting ...... 217 More Flexible Browser Functionality ...... 217
8 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Internet Agent ...... 217 ESMTP Support ...... 218 Secure POP and IMAP ...... 218 Improved Access Control ...... 218 Improved IMAP Compliance ...... 218 Consistent Agent Engine ...... 218 Consistent Windows Interface ...... 218 NT/2000 Service Functionality ...... 218 GroupWise WebAccess ...... 219 Wireless Device Support ...... 219 SNMP Support ...... 219 Windows Service Support ...... 219 NetWare Cluster Support ...... 219 Improved Installation and More NDS Administration ...... 220 WebAccess Client Features Added ...... 220 GroupWise Monitor...... 220 Link Trace ...... 221 Link Check ...... 221 System Performance Testing...... 221 Environment Report ...... 222 User Traffic Report ...... 222 Link Traffic Report ...... 222 Message Tracking Report ...... 222
C GroupWise 5.x and 6 Compatibility Matrix 223
Contents 9
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
10 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
About this Guide
This GroupWise® 6 Installation guide helps you install a new GroupWise system or update an existing GroupWise 5.x system. It is divided into three parts: ! “Installation” on page 13 ! “Update” on page 169 ! “Appendixes” on page 199
Trademark Conventions
In this documentation, a trademark symbol (TM, ®, etc.) denotes a Novell® trademark. An asterisk denotes a third-party trademark.
Additional Documentation
Novell® provides additional documentation to help you use, administer, and troubleshoot your GroupWise 6 system. This documentation, including any updates to the Installation guide, is located at the Novell Documentation Web site (http://www.novell.com/documentation).
About this Guide 11
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
12 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
I Installation
Chapter 1, “Installing a Basic GroupWise System,” on page 15 Chapter 2, “Installing GroupWise Internet Agent,” on page 75 Chapter 3, “Installing GroupWise WebAccess,” on page 97 Chapter 4, “Installing GroupWise Monitor,” on page 125 Chapter 5, “Installing GroupWise Agents,” on page 137 Chapter 6, “Installing the GroupWise Client,” on page 165
Installation 13
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
14 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
1 Installing a Basic GroupWise System
Every GroupWise® system, whether it services five users or 50,000 users, starts as a basic GroupWise system. A basic system consists of a single domain with one post office, a document library, and one or more users, as shown below.
Domain
Message Transfer Agent Post Office Agent Post Office with Library
GroupWise Client
Each GroupWise user has a mailbox in the post office; users run the GroupWise client to access their mailboxes and to send and receive mail. The GroupWise Post Office Agent (POA) delivers messages between users' mailboxes in a post office, and the GroupWise Message Transfer Agent (MTA) routes messages between post offices (if there is more than one post office in the domain) and between domains (if there is more than one domain in the system).
Installing a Basic GroupWise System 15
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The following sections present the background information and installation instructions you need to successfully implement your basic GroupWise system. ! “Planning Your Basic GroupWise System” on page 16 ! “Setting Up Your Basic GroupWise System” on page 41 ! “Basic GroupWise System Worksheet” on page 67 When you finish setting up your basic system, you will want to review “Other Things You Can Do” on page 65 to learn how you can expand your system.
Planning Your Basic GroupWise System
GroupWise includes an Installation Advisor to help you install the GroupWise files to the appropriate locations and a Setup Advisor to help you create and configure your GroupWise system. Both Advisors provide information to guide you through the process. If you are comfortable with your knowledge of GroupWise, you can skip this planning section and continue with “Setting Up Your Basic GroupWise System” on page 41. Otherwise, you should review the following sections while filling out the “Basic GroupWise System Worksheet” on page 67. The worksheet lists all the information you will be prompted for as you run the Advisors. ! “Determining Installation Locations” on page 16 ! “Planning Your Domain” on page 21 ! “Planning Your Post Office” on page 27 ! “Planning Your GroupWise Agents” on page 31 Once you've completed the above tasks, you should review the sample configurations and the summary of GroupWise requirements. ! “Sample GroupWise Configurations” on page 36 ! “Summary of Requirements for a Basic GroupWise System” on page 38
Determining Installation Locations
The Installation Advisor will prompt you for information about the NDS® tree and file server locations where you want to install GroupWise objects and files. The following sections prepare you to supply the required information.
16 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! “NDS” on page 17 ! “ConsoleOne” on page 17 ! “GroupWise Software Distribution Directory” on page 18 ! “GroupWise Languages” on page 20
NDS GroupWise is administered through NDS, Novell’s directory service. All components, such as domains, post offices, libraries, and agents, as well as all users’ GroupWise accounts, are configured through objects in NDS. You need to make sure that you have NDS installed in your environment. GroupWise supports all versions of NDS.
Extending the NDS Tree’s Schema The Installation Advisor must extend the schema of the NDS tree where you are going to create your GroupWise system. Because all objects for a single GroupWise domain must reside in the same NDS tree, installing a basic system (one domain) requires you to extend one tree only.
WORKSHEET
Under Item 1: NDS Tree, enter the NDS tree where you will create the GroupWise objects.
Making Sure Users Exist in NDS You must make sure all users who will use GroupWise exist in NDS. GroupWise accounts can only be assigned to NDS User objects and GroupWise External Entity objects. GroupWise external entities represent non-NDS users and are added to NDS for the sole purpose of assigning GroupWise accounts to these users. GroupWise external entities require GroupWise licenses but not NDS licenses. You can add GroupWise external entities only after you have installed GroupWise. Instructions for adding GroupWise external entities are provided in “Assigning GroupWise Accounts to Additional Users” on page 63.
ConsoleOne
GroupWise administration is performed through ConsoleOneTM, version 1.2d.1 or higher. When you install GroupWise, the GroupWise Administrator snap-in files are copied to a ConsoleOne location that you specify. The
Installing a Basic GroupWise System 17
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Administrator snap-in files extend the functionality of ConsoleOne to let you administer GroupWise. You need to decide which ConsoleOne location you will use to administer GroupWise. This can be a ConsoleOne location on a network server, or it could be on a local workstation. If you plan to use ConsoleOne on a local workstation, you will need to perform the GroupWise installation from that workstation.
IMPORTANT: ConsoleOne, version 1.2d.1, is included on the GroupWise 6 CD. The Installation Advisor lets you install ConsoleOne if necessary. You can also use the Installation Advisor at a later time to install ConsoleOne and the GroupWise Administrator snap-in to additional locations.
WORKSHEET
Under Item 3: ConsoleOne Path, enter the path for the ConsoleOne location you want to use to administer GroupWise.
GroupWise Software Distribution Directory During installation, you are prompted to create a GroupWise software distribution directory on a network server and then copy selected GroupWise software to the directory. You should consider the following when deciding where to create the software distribution directory. ! “User Access to the Directory” on page 18 ! “Disk Space Required for the Software” on page 19
User Access to the Directory Users can install the GroupWise client through a TCP/IP or mapped connection to the software distribution directory. If you want users to install via a mapped connection, you should create the software distribution directory on a server where you can provide appropriate user access. When users install the GroupWise client, they can choose to copy it to a local drive or they can run it from the software distribution directory. If you want users to be able to run the GroupWise client from the software distribution directory, they must have a permanent drive mapping to the directory.
18 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Disk Space Required for the Software The disk space required for the directory depends on the amount of software you copy to the directory. The maximum disk space required to store all the GroupWise software for one language is approximately 350 MB. We recommend that you copy at least the GroupWise client files to the directory. This enables users to install the GroupWise client from the distribution directory. Otherwise, you will need to mount the GroupWise 6 CD as a network volume or distribute the CD to individual users. All GroupWise software other than the client is used for administrative purposes only; if disk space is an issue and you don’t mind accessing the GroupWise 6 CD when you need to install one of the software components, you may want to leave the administrative software on the CD. The following sections describe the purpose of each software component and provide the approximate disk space required by each. GroupWise Administrator Snap-In: Enables GroupWise administration through ConsoleOne. The software requires approximately 30 MB. NLM Agents (MTA and POA): Route user and administration messages through the GroupWise system. The software requires approximately 21 MB. If the NT/2000 agent software is also copied to the distribution directory, the combined agent software requires only 27 MB.
NT/2000 Agents (MTA and POA): Like the NLMTM agents, the NT/2000 agents route user and administration messages through the GroupWise system. The software requires approximately 24 MB. If the NLM agent software is also copied to the distribution directory, the combined agent software requires only 27 MB total. Windows GroupWise Client: Sends and receives messages.The software requires approximately 75 MB. GroupWise Monitor: Monitors the status of the GroupWise agents and lets you configure agent settings. The software requires approximately 105 MB. Common files (JVM and servlet gateway) shared with GroupWise WebAccess make up 85 MB of this 105 MB total. GroupWise WebAccess: Lets users access their GroupWise mailboxes through a Web browser on a workstation or on a wireless device (such as a telephone). The software requires approximately 175 MB. Common files (JVM and servlet gateway) shared with GroupWise WebAccess make up 85 MB of this 175 MB total.
Installing a Basic GroupWise System 19
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Internet Agent: Lets users send and receive e-mail through the Internet. The software requires approximately 37 MB.
WORKSHEET
Under Item 4: Software Distribution Directory, specify the path for the software distribution directory.
Under Item 5: Software Selection, select the software you want copied to the software distribution directory.
NOTE: The Installation Advisor lets you create one software distribution directory. Once you've set up your basic GroupWise system, you can create additional software distribution directories if needed.
For example, if not all users can access a single software distribution directory to run the GroupWise client Setup program, you can create an additional software distribution directory on a server they can access. For information about creating additional software distribution directories, see the GroupWise 6 Administration guide on the Novell Documentation Web site (http://www.novell.com/ documentation).
GroupWise Languages The GroupWise 6 CD may contain multiple languages. If it does, you need to decide which languages you want to install. Your choice affects the following programs: ! GroupWise Administrator snap-in for ConsoleOne ! GroupWise agents ! GroupWise client For example, if you install English-US and German, you will be able to run GroupWise Administrator and the agents in either language. By default, GroupWise Administrator runs in the language in which you are running ConsoleOne. Your users will have the choice of using either the English-US client or the German client.
WORKSHEET
Under Item 2: Languages to Install, enter the languages you want to install. The GroupWise Administrator languages will be copied to the ConsoleOne location. The GroupWise agent and client languages will be copied to the software distribution directory.
20 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Planning Your Domain
The domain functions as the main administration unit for the GroupWise system. When you configure GroupWise information in NDS, it is also stored in the GroupWise domain database. From the domain database, the GroupWise agents distribute the information to each post office database. Users then get the information, such as user addresses, from the post office database. In a multiple-post office system, the domain also organizes post offices into a logical grouping for addressing and routing purposes, and enables you to scale your GroupWise system to meet your current and future needs. As you create your basic GroupWise system, the Setup Advisor will prompt you for information about the domain. The following sections prepare you to supply the required information. ! “System and Domain Names” on page 21 ! “Domain Directory” on page 22 ! “Domain Context” on page 23 ! “Domain Language” on page 26 ! “Domain Time Zone” on page 27
System and Domain Names The domain requires a unique name. The name is used as the Domain object’s name in NDS. It is also used for addressing and routing purposes within GroupWise, and may appear in the GroupWise Address Book. The domain name can reflect a location, company name or branch name, or some other element that makes sense for your organization. For example, you may want the domain name to be the location (for example, Provo) while the post office name is one of the company’s departments (for example, Research). Name your domain carefully. After it is created, the name cannot be changed. You must also provide a name for your GroupWise system. The system name is used when connecting to other GroupWise systems; for this reason, it must be different than any other GroupWise system with which you may want to connect. 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 ConsoleOne. You cannot change the name after your system is created.
Installing a Basic GroupWise System 21
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
System and domain names must be one word. Do not use any of the characters listed below.
ASCII characters 0-13 Double quote " At sign @ Extended characters Braces { } Parentheses ( ) Colon : Period . Comma , Space (use an underscore _ instead)
WORKSHEET
Under Item 6: System Name, enter the system name.
Under Item 7: Domain Name, enter the domain name.
Domain Directory The domain requires a directory structure in which to store database files and temporary files that are created during message routing. As you choose a location for the domain directory, consider the following: Security: GroupWise users never need access to the domain directory, so you should create it on a server volume that you can easily secure. Server Platform and Version: The domain directory can be located on any NetWare server (3.12, 4.1x, or 5.x) or Windows* NT**/2000 server or workstation. The only requirement is that the GroupWise Message Transfer Agent (MTA), running on a NetWare 5.x or Windows NT/2000 machine, be able to access the directory. MTA Access: Because the MTA requires access to the domain directory, you may also want to consider the type (NLM or NT/2000) and location of the MTA before deciding on a domain directory. For information about the MTA, see “Planning Your GroupWise Agents” on page 31. For examples of possible domain directory locations and MTA configurations, see “Sample GroupWise Configurations” on page 36. Disk Space Requirements: The domain directory requires approximately 10 MB of free disk space. This requirement could increase to around 30 MB as your GroupWise system grows.
22 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Directory Name: You should specify an empty directory for the domain. If you want, the directory can reflect the domain name you chose. However, use a maximum of 8 characters for the directory name. Choose the name and path carefully. After the directory is created, it is difficult to rename. If the directory you specify does not exist, it will be created during installation.
WORKSHEET
Under Item 8: Domain Directory, enter the full path for the domain directory.
Domain Context You can create the Domain object in any context in your NDS tree. The only requirement is that it be in the same tree as the other objects associated with the domain (Post Office object, User objects, and so forth). The following sections provide examples of where you might place your Domain object. Because it is helpful to discuss the Domain object’s context in relationship to the Post Office object’s context, the examples also include context information for the Post Office object. ! “Objects in Same Container as Users' Organizational Units” on page 23 ! “Objects Mirror NDS Organization” on page 24 ! “Objects in Dedicated Container” on page 24 ! “Objects Mirror Network Server Organization” on page 25
Objects in Same Container as Users' Organizational Units In the following example, the Domain object (Provo) and Post Office object (Research) reside in the same container (Provo) as the organizational units (Accounting, Manufacturing, R&D, and Sales) that contain the users. This allows you to associate the domain with a single organization and associate one post office with all users within the organization.
Installing a Basic GroupWise System 23
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Objects Mirror NDS Organization The following example is similar to the previous example, except that a separate post office is created for each organizational unit that contains users. The Domain object (Provo) resides in the organization (Provo) and the Post Office objects reside in the same organizational units (Accounting, Manufacturing, R&D, and Sales) as the users.
As in the previous example, this organizational structure allows you to quickly associate users with their post offices. In addition, if you have thousands of users split between the different organizational units, this method allows you to create multiple post offices with a smaller number of users on each post office.
Objects in Dedicated Container If, rather than mirroring your NDS organization, you would prefer to keep all your GroupWise objects together, you could create a container, such as GroupWise, and place all GroupWise objects in that container, as shown below. Administratively, this type of organizational structure makes it easier to restrict a GroupWise administrator's object and property rights to GroupWise objects only. For information about GroupWise administrator rights, see the GroupWise 6 Administration guide on the Novell Documentation Web site (http://www.novell.com/documentation).
24 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Objects Mirror Network Server Organization Because the domain and post office have directory structures on network servers, you could also choose to place the Domain and Post Office objects in the same context as the servers where the directories will reside, as shown in the following example.
WORKSHEET
Under Item 9: Domain Context, enter the domain context.
Installing a Basic GroupWise System 25
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
A Look at GroupWise from the GroupWise View ConsoleOne includes a GroupWise View, shown below.
The GroupWise View filters out all non-GroupWise objects and shows how GroupWise objects relate to each other. For example, in the left pane, notice the Post Office object (Research) is subordinate to the Domain object (Provo). You can select an object in the left pane and display its associated objects (User, Resource, and so forth) in the right pane. The GroupWise View is particularly useful if your GroupWise objects are placed in different contexts in the NDS tree. Rather than searching for GroupWise objects throughout the tree, you could administer the objects from the GroupWise View. Some GroupWise administrative functions can only be done while in the GroupWise View. This includes such tasks as defining users from other GroupWise systems so that they appear in your system's Address Book.
Domain Language The domain language determines how times, dates, and numbers are displayed in the GroupWise client and affects the sorting order for items in the GroupWise Address Book.
26 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 10: Domain Language, enter the language for the domain. The domain language becomes the default language for the domain’s post offices.
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 will be scheduled in the Los Angeles user's calendar at 1:00 p.m. Pacific Time.
WORKSHEET
Under Item 11: Domain Time Zone, enter the time zone for the domain. The domain time zone becomes the default time zone for the domain’s post offices.
Planning Your Post Office
The post office contains users’ mailboxes. Like a domain, a post office requires a name, has a directory structure and an NDS object, and can be configured to support different languages and time zones. The following sections prepare you to supply the Setup Advisor with the required information. ! “Post Office Name” on page 27 ! “Post Office Directory” on page 28 ! “Post Office Context” on page 29 ! “Post Office Language” on page 30 ! “Post Office Time Zone” on page 30 ! “Post Office Users” on page 30
Post Office Name The post office, like the domain, requires a unique name. The name is used as the Post Office object’s name in NDS. It is also used for addressing and routing purposes within GroupWise, and may appear in the GroupWise
Installing a Basic GroupWise System 27
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Address Book. The post office name can reflect any element that makes sense for your organization. For example, you may want the domain name to be the location (for example, Provo) while the post office name is one of the company’s departments (for example, Research). Name your post office carefully. After it is created, the name cannot be changed. Post office names must be one word. The same characters that are invalid in system and domain names are also invalid in post office names (see “System and Domain Names” on page 21).
WORKSHEET
Under Item 12: Post Office Name, enter the name you’ve selected.
Post Office Directory The post office requires a directory structure in which to store database files and temporary files that are created during message routing. As you choose a location for the post office directory, consider the following: Security: The GroupWise client accesses the post office through a client/ server (TCP/IP) connection to the GroupWise Post Office Agent (POA). GroupWise users never need access to the post office directory, so you should create the directory on a server volume that you can easily secure. Server Platform and Version: The post office directory can be located on any NetWare server (3.12, 4.1x, or 5.x) or Windows NT/2000 server or workstation. The only requirement is that the POA, running on a NetWare 5.x or Windows NT/2000 machine, be able to access the directory. POA Access: Because the POA requires access to the post office directory, you may also want to consider the type (NLM or NT/2000) and location of the POA before deciding on a post office directory. For information about the POA, see “Planning Your GroupWise Agents” on page 31. For examples of possible post office directory locations and POA configurations, see “Sample GroupWise Configurations” on page 36. Disk Space Requirements: The post office directory holds users’ messages and attachments, so you should plan a minimum of 2 MB per user. We recommend 10 MB per user. Although actual messages are relatively small, message attachments (documents, spreadsheets, graphic files, and so forth) can greatly increase the amount of disk space used.
28 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Using ConsoleOne, you can restrict the amount of disk space users are allowed for their mailboxes. When you know the number of users and the amount of disk space allocated to each user, you can more accurately determine the amount of disk space required. You can reduce the amount of disk space required for the post office by forcing users to run the GroupWise client in Caching mode rather than Online mode. In Online mode, messages are stored in the post office. In Caching mode, messages are stored on users’ local drives. In addition to users’ messages and attachments, the post office directory also contains a document library. You should take into account the disk space you will want to provide for storing documents. Directory Names: You should specify an empty directory for the post office. If you want, the directory can reflect the post office name you chose. However, use a maximum of 8 characters for the directory name. Choose the name and path carefully. After the directory is created, it is difficult to rename it. If the directory you specify does not exist, it will be created during installation.
WORKSHEET
Under Item 13: Post Office Directory, enter the full path for the post office directory.
Post Office Context Like the Domain object, you can create the Post Office object in any context in your NDS tree. The only requirement is that it be in the same tree as the Domain object and other objects associated with the domain (User objects and so forth). For configuration examples, see “Domain Context” on page 23.
WORKSHEET
Under Item 14: Post Office Context, enter the context where you want to create the Post Office object.
Installing a Basic GroupWise System 29
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Post Office Language The post office language determines how times, dates, and numbers are displayed in the GroupWise client and affects the sorting 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-US, all time, date, and numbers will be formatted according to English-US standards, and the Address Book items will be sorted according to English-US sort order rules. This will be true even if some users on the post office are running non-English GroupWise clients such as German or Japanese. Their client interface and Help files will be in German or Japanese, but the time, date, and number formats and sort order will be according to English-US standards.
WORKSHEET
Under Item 15: Post Office Language, enter the language for the post office.
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 will be scheduled in the Los Angeles user's calendar at 1:00 p.m. Pacific Time. The post office assumes the same time zone as its domain unless you specify otherwise.
WORKSHEET
Under Item 16: Post Office Time Zone, enter the time zone where the post office is located.
Post Office Users You will need to assign GroupWise accounts to each NDS user who should have a mailbox in the post office. You can do this while creating your system, or you can do it afterwards. However, we recommend that you at least add yourself so you can test the system.
30 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If you are adding non-NDS users as GroupWise external entities, you must wait to add them to the post office until after you have finished the installation.
WORKSHEET
If desired, enter the context for each user under Item 20: Post Office Users.
The Setup Advisor lets you select users from the NDS tree to add to the post office. You may choose not to list all of the users at this time.
Planning Your GroupWise Agents
The Message Transfer Agent (MTA) and Post Office Agent (POA) route messages through the GroupWise system. The MTA handles all message traffic between the domain and post office, while the POA handles all message traffic within the post office. MTA: GroupWise requires one MTA per domain, which means that you will need to install and run one MTA for your basic GroupWise system. In addition to routing user messages between post offices and between domains, the MTA routes administration messages from the domain to the post office. For example, when a user is given a GroupWise account in NDS, the user is added to the GroupWise domain database. At the same time, the MTA routes an administration message from the domain to the post office so that the POA can add the user to the post office database. After the user is added to the post office database, he or she appears in the GroupWise Address Book. POA: GroupWise requires one POA per post office, which means that you will need to install and run one POA for your basic GroupWise system. The POA routes messages within the post office, updates the post office database when it receives administration messages from the MTA, and performs other maintenance tasks on the post office. The following sections prepare you to supply the information required when installing the MTA and POA: ! “Agent Platform” on page 32 ! “Agent Location” on page 32 ! “MTA Link to the Post Office” on page 34
Installing a Basic GroupWise System 31
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! “Windows Application vs. Windows Service (NT/2000 Agents Only)” on page 34 ! “Web Console” on page 35 ! “Agent Language” on page 35
Agent Platform The MTA and POA are available as NetWare® NLM programs and Windows NT/Windows 2000 executables. In general, GroupWise is most efficient if you match the agent platform with the network operating system where the post office and domain have been created. For example, if a domain and post office are located on a NetWare server, then you would install the NLM agents for them. However, this is not required. For configuration examples, see “Sample GroupWise Configurations” on page 36. The following table outlines the disk space and memory requirements for the agents.
Platform Requirement
NetWare NLM Disk Space: 6.5 MB Memory: 7.5 MB
Windows NT/2000 Disk Space: 5.5 MB Memory: 7.5 MB
IMPORTANT: The memory requirements listed above are for a basic GroupWise system (one domain with a single post office). Memory requirements for the MTA increase as you add post offices and other domains to your system. For detailed information, see the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
WORKSHEET
Under Item 21: Agent Platform, enter the type of agents (NLM or NT/2000) you will use.
Agent Location The MTA requires direct access to the domain directory. The POA requires direct access to the post office directory.
32 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
You can install an agent on the same machine as its directory, or you can install it on another machine. If the agent is not installed on the same machine as its directory, the agent requires either a mapped drive or a UNC path to its directory in order to function, as shown in the following diagram.
Domain
Mapped Drive or UNC Path
Message Transfer Agent
Mapped Drive or UNC Path
Post Office Mapped Drive Agent or UNC Path
Post Office
For the purpose of simplifying the setup of your basic system, you will be required to install both the MTA and the POA to the same machine. If, at a later time, you decide that you want to run one of the agents on a different machine, see “Installing GroupWise Agents” on page 137.
NetWare NLM When installing the NLM agents, we recommend you use the SYS:\SYSTEM directory on the NetWare server. This simplifies the use of startup files and ensures that the NLM programs are in the server’s search path. If you use a different directory, you will need to add that directory to the server’s search path.
Installing a Basic GroupWise System 33
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Windows NT/2000 The default installation directory is C:\GRPWISE. However, you can install the agents to any directory you want.
WORKSHEET
Under Item 22: Agent Installation Path, enter the installation path for the agents.
MTA Link to the Post Office To route user and administration messages to the post office, the MTA requires direct access to the post office directory or TCP/IP access to the post office’s POA. In general, we recommend you use a TCP/IP link unless the MTA and post office directory are on the same machine.
WORKSHEET
Under Item 17: Post Office Link, select whether the MTA will link to the post office through a TCP/IP connection to the POA or a direct connection to the post office directory.
Under Item 18: POA Network Address, enter the IP address or DNS hostname of the POA’s machine. The GroupWise client, which accesses the POA through TCP/IP, needs to know the address. If the MTA will have a TCP/IP connection to the POA, it will also use this address.
If you plan to have the MTA use a TCP/IP connection to the POA, under Item 19: MTA Network Address, enter the IP address or DNS host name of the MTA’s machine.
Windows Application vs. Windows Service (NT/2000 Agents Only) You can run the MTA and POA as normal Windows applications or as Windows NT/2000 services. When you run the agents as Windows services, they must run under a specific NT/2000 user account. The user account you use depends on where the domain and post office directories are located: ! When the domain and post office directories are located on the same machine where you are installing the agents, the agents can run under the local system account. You can also display the agent console when the agent software, directories, and databases are local. ! When the domain and post office directories are located on a remote machine, you must specify a user with rights to access the domain and
34 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
post office directories. If the agents need to log in to an NT/2000 machine, provide a Windows user name and password. If the agents need to log in to a NetWare server, provide an existing NDS user name and password. As with all Windows services, you can start the agents manually or have them start automatically each time the NT/2000 machine restarts.
WORKSHEET
Under Item 23: NT/2000 Agent Installation Options, select Install as NT/2000 Services if you want to run the agents as Windows services.
If you will run the agents as Windows services, under Item 26: NT/2000 Services Information, record the account the agents will run under, and if necessary, the password for the account. Also select whether you want the service to start automatically or manually.
Web Console The MTA and POA provide consoles to let you monitor and configure the agents while at the agents’ machine. The Web console lets you use a Web browser to access the agents’ statistics and diagnostic information from another workstation.
WORKSHEET
Under Item 24: Enable Web Console, select Yes to enable monitoring of the agents through a Web browser, then select a username and password to use when logging in to the agents.
Agent Language If you have users with various language preferences, you can install the GroupWise agents in multiple languages, provided you have a multi-lingual version of the GroupWise software. The language determines the agents’ interface language only. It does not affect messages processed by the agents. By default, the agents will start in the language selected for the domain. If that language has not been installed, the agents will start in the language used by the operating system. If that language has not been installed, the agents will start in English.
Installing a Basic GroupWise System 35
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 25: Agent Language, list the languages you want to install for the agents.
Sample GroupWise Configurations
Many different configurations are possible for your GroupWise system. The following diagrams illustrate some of the ways a basic GroupWise system (one domain and one post office) can be set up.
A NetWare 5.1 Server The following diagram shows a basic GroupWise system set up on a single NetWare 5.1 server.
NW51
Z:\PUBLIC User running ConsoleOne GroupWise client J:\PROVO from software Domain (Provo) Administrator distribution directory. J:\RESEARCH Post Office (Research) J:\SOFTWARE X:\SOFTWARE Software Distribution Directory J:=NW51\MAIL: Z:\SYSTEM MTA NLM Z:=NW51\SYS: TCP/IP POA NLM
TCP/IP
User running GroupWise client from local drive.
A Windows NT 4.0 Server The following diagram shows all GroupWise components on a Windows NT 4.0 server.
36 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
NT40
User running GroupWise client K:\PROVO from software Domain (Provo) Administrator distribution directory. J:\RESEARCH Post Office (Research) J:\SOFTWARE X:\SOFTWARE Software Distribution Directory J:=NT40\MAIL: K:\GRPWISE MTA NT K:=NT40\C: TCP/IP POA NT
TCP/IP
User running GroupWise client from local drive.
A NetWare 5.1 Server and a Windows NT 4.0 Server The following diagram shows the domain, post office, and software distribution directory on a NetWare 5.1 server. The MTA and POA, located on a Windows NT 4.0 server, use a UNC path to access the domain directory and post office directory on the NetWare 5.1 server.
NW51
User running Z:\PUBLIC GroupWise client ConsoleOne Administrator from software J:\SOFTWARE X:\SOFTWARE distribution Software Distribution Directory directory. J:\RESEARCH Post Office (Research) J:\PROVO J:=NW51\MAIL: Domain (Provo) Z:=NW51\SYS:
NT40 User running \\NW51\MAIL GroupWise client from local drive. TCP/IP MTA NT TCP/IP POA NT
Installing a Basic GroupWise System 37
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The following diagram shows the domain and MTA on a NetWare 5.1 server. The post office, software distribution directory, and POA are on a Windows NT 4.0 server. The MTA communicates with the POA through TCP/IP.
NW51
Z:\PUBLIC ConsoleOne J:\PROVO Domain (Provo) Z:\SYSTEM MTA NLM User running Administrator GroupWise client NW40 from local drive. TCP/IP User running J:=NW51\MAIL: GroupWise client from software Z:=NW51\SYS: K:\GRPWISE TCP/IP POA NT TCP/IP distribution directory. K:\RESEARCH Post Office (Research) K:\SOFTWARE X:\SOFTWARE Software Distribution Directory
NOTE: The above configuration has the MTA on one machine and the POA on another. Because the basic GroupWise system setup requires you to install the MTA and POA on the same machine, you would have to do additional setup to create a similar configuration.
Summary of Requirements for a Basic GroupWise System
The following table summarizes the requirements for a single domain with one post office.
Item Requirement
NDS ! GroupWise information is stored in NDS. GroupWise supports all versions of NDS.
38 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
ConsoleOne and the GroupWise ! ConsoleOne 1.2d.1 or higher. Administrator Snap-In Files You can install version 1.2d.1 from the GroupWise 6 CD at the same time as the GroupWise Administrator snap-in. ! Windows 95/98 workstation with the Novell ClientTM for Windows 95/98 or a Windows NT 4.0/ 2000 workstation with the Novell Client for Windows NT/2000.
Software Distribution Directory ! 350 MB maximum of disk space on a network server. This will be less if you choose not to copy some software to the directory.
Domain Directory ! 10 MB (minimum) of disk space on a network server ! Can be located on a NetWare server (3.12, 4.1x, or 5.x) or Windows NT/2000 server or workstation. The MTA, running on a NetWare 5.x or Windows NT/2000 machine, must be able to access the directory.
Installing a Basic GroupWise System 39
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
Post Office Directory ! 2 MB disk space per user (minimum); 10 MB per user (recommended). To control disk space usage, you can restrict the amount of disk space allowed per person or force the GroupWise client to store messages on users’ local drives rather than at the post office (Caching mode instead of the standard Online mode). ! Disk space as needed for library documents ! Can be located on a NetWare server (3.12, 4.1x, or 5.x) or Windows NT/2000 server or workstation. The POA, running on a NetWare 5.x or Windows NT/2000 machine, must be able to access the directory.
NLM Agents ! NetWare 5.1 (or higher) server with the latest support pack ! 6.5 MB free disk space (minimum) ! 7.5 MB free memory (minimum)
NT/2000 Agents ! Windows NT 4.0/2000 server or workstation with the latest service pack ! 5.5 MB free disk space (minimum) ! 7.5 MB free memory (minimum)
40 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
Windows GroupWise Client ! OS: Windows 95 or higher ! Processor: Pentium 133 or higher recommended for Windows 95/98/NT Pentium 200 or higher recommended for Windows 2000 ! Memory: 48 MB RAM recommended for Windows 95/ 98 64 MB RAM recommended for Windows NT 128 MB RAM recommended for Windows 2000 ! Disk Space: 51 MB free disk space to run from the workstation’s local drive 5 MB free disk space to run from a network drive
Setting Up Your Basic GroupWise System
You should have already reviewed “Planning Your Basic GroupWise System” on page 16 and filled out the worksheet. The following sections step you through the GroupWise Installation Advisor and GroupWise Setup Advisor. The Installation Advisor installs the GroupWise software. It then launches the Setup Advisor to create your domain and post office, set up the GroupWise agents, and set up the GroupWise Windows client (if desired) on your workstation. ! “Starting the GroupWise Installation Advisor” on page 42 ! “Installing the GroupWise Software” on page 44 ! “Providing System Information” on page 46 ! “Creating the System” on page 48 ! “Installing and Starting the GroupWise Agents” on page 50 ! “Setting Up and Running the Client on Your Workstation” on page 62 ! “Setting Up Users' Workstations to Run the Client” on page 65
Installing a Basic GroupWise System 41
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Starting the GroupWise Installation Advisor
To start the GroupWise Installation Advisor: 1 From a Windows 95/98/NT/2000 workstation, log in as an Admin equivalent to the NDS tree in which you are installing GroupWise.
NOTE: If you will be installing the GroupWise agents on a Windows NT/2000 machine, you should run the Installation Advisor from that machine. 2 Click Start > Run > type d:setup.exe (where d is your CD drive).
3 Click Create or Update a GroupWise System > click Yes to accept the license agreement and display the Welcome to GroupWise Install dialog box.
42 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Click Next until you reach the Administration Options dialog box.
5 Make sure that Create a New System or Update an Existing System is selected > click Next to display the Select Tree dialog box.
Installing a Basic GroupWise System 43
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
6 Continue with the next section, “Installing the GroupWise Software” on page 44.
Installing the GroupWise Software The Installation Advisor extends the NDS schema for the selected tree and then installs GroupWise software to the ConsoleOne location and software distribution directory. To extend the schema and install the software: 1 In the Select Tree dialog box, select the tree whose schema you want to extend (worksheet item 1) > click Next > enter the information from your worksheet (item 2 through item 5) until you reach the Ready to Install dialog box.
44 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Click Install > follow the prompts until you reach the Determine Next Step dialog box.
3 Click Creating a New GroupWise System > click Next to display the Run ConsoleOne dialog box.
Installing a Basic GroupWise System 45
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Continue with the next section, “Providing System Information” on page 46.
Providing System Information The Installation Advisor launches ConsoleOne with the GroupWise Setup Advisor active. Use your worksheet to provide the Setup Advisor with the information it needs to create your GroupWise system. 1 In the Run ConsoleOne dialog box, click Run to start ConsoleOne and the GroupWise Setup Advisor. The GroupWise Setup Progress: Collect System Information dialog box is displayed.
46 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Click Next > enter the information from your worksheet (item 6 through item 20) until you reach the GroupWise Setup Progress: Create System dialog box.
3 Click Next to display a summary of the information you entered.
Installing a Basic GroupWise System 47
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Continue with the next section, “Creating the System” on page 48.
Creating the System After you've verified that the information you entered is correct, you are ready for the Setup Advisor to create your system. 1 In the Summary dialog box, click Next. The Setup Advisor creates the GroupWise system using the information you provided, then displays the following dialog box:
48 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Click Next to display the GroupWise Setup Progress: Install Agent Software dialog box.
3 Continue with the next section, “Installing and Starting the GroupWise Agents” on page 50.
Installing a Basic GroupWise System 49
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Installing and Starting the GroupWise Agents
At this point, the Setup Advisor has created NDS objects and file server directories associated with your GroupWise system. You now need to install and start the MTA and POA. 1 In the GroupWise Setup Progress: Install Agent Software dialog box, click Next to have the Setup Advisor launch the Agent Installation program and display the Select Platform dialog box.
2 If you are installing the NLM agents (worksheet item 21), see “Installing and Starting the NLM Agents” on page 50. or If you are installing the NT/2000 agents (worksheet item 21), see “Installing and Starting the NT/2000 Agents” on page 55.
Installing and Starting the NLM Agents 1 In the Select Platform dialog box, select NetWare as the platform > click Next to display the Installation Path dialog box.
50 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Select the directory where you want to install the agents (worksheet item 22) > click Next to display the Web Console Information dialog box.
3 Enter the Web console information (worksheet item 24) > click Next to display the Language dialog box. or
Installing a Basic GroupWise System 51
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If you don’t want to use the Web console, deselect the check box to turn off the option > click Next to display the Language dialog box.
4 Select the languages you want to install (worksheet item 25) > click Next to display the Summary dialog box.
5 Click Install to install the agents.
52 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The Installation Complete dialog box appears when the files have been installed.
6 Select from the following options: Update AUTOEXEC File: Select this option to reference the GRPWISE.NCF file from the server's AUTOEXEC.NCF file so that the GroupWise agents are automatically loaded whenever the server is started. Delete Obsolete GWADA Files and References to GWADA: This option does not apply when creating a new GroupWise system. Launch GroupWise Agents Now: Select this option to start the GroupWise agents. You should only do this if the MTA and POA are on the same server as the domain and post office directories. If you want the agents to run in protected mode, turn on the Launch in Protected Mode option. 7 Click Finish to return to the Setup Advisor. The GroupWise Setup Progress: Set Up Client Software dialog box is displayed.
Installing a Basic GroupWise System 53
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 If you've already started the GroupWise agents (because they are on the same server as the domain and post office directories), skip to “Setting Up Users' Workstations to Run the Client” on page 65. Otherwise, continue with Step 9. 9 Use a text editor to modify the agents' startup files. The load command in the GRPWISE.NCF file includes a startup switch that forces the agents to read their startup files. The startup files include configuration information the agents need to function properly. When the MTA is not on the same server as the domain directory and post office directory, you need to edit the MTA startup file to include the MTA’s NDS distinguished name. When the POA is not on the same server as the post office, you need to edit the POA startup file to include the POA’s NDS distinguished name. The startup files are located in the agent installation directory you specified in Step 2. The MTA startup file is named domain.MTA, where domain is the first 7 letters of the domain name (for example, PROVO.MTA). The POA startup file is named postoffice.POA, where postoffice is the first 7 letters of the post office name (for example, RESEARC.POA). The /dn-object_distinguished_name startup switch is located in Section 1 of the startup file. Delete the semicolon (;) at the beginning of the line and replace the object_distinguished_name variable with the distinguished name of the MTA or POA. For example, if the MTA is for a domain
54 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
named Provo that is located in a container named Novell, you would enter:
/dn-mta.provo.novell 10 At the server's console, enter GRPWISE.NCF to load the agents. 11 Skip to “Setting Up and Running the Client on Your Workstation” on page 62.
Installing and Starting the NT/2000 Agents To install the NT/2000 agents, you must run the Agent Installation program from the Windows NT/2000 machine where you are installing the agents. 1 If you are already running the Agent Installation program from the Windows NT/2000 machine where you are installing the agents, skip to Step 6. or Click Exit to close the Agent Installation program > go to the Windows NT/2000 machine where you want to install the agents > continue with Step 2. 2 Make sure you are logged in as an Admin equivalent and have network access to the software distribution directory (or GroupWise 6 CD), domain directory, and post office directory. 3 Start the Agent Installation program (INSTALL.EXE) > click Yes to accept the license agreement and display the Overview dialog box. INSTALL.EXE is located in the AGENTS directory on the GroupWise 6 CD or in the software distribution directory.
Installing a Basic GroupWise System 55
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Click Next to display the Install/Uninstall dialog box
5 Click Install > click Next to display the Select Platform dialog box.
56 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
6 Click Windows NT > click Next to display the Installation Path dialog box.
7 Enter the path to the directory where you want the agents installed (worksheet item 22) > select the installation options you want (worksheet item 23) > click Next to display the Web Console Information dialog box.
Installing a Basic GroupWise System 57
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 Enter the Web console information (worksheet item 24) > click Next to display the Language dialog box. or If you don’t want to use the Web console, deselect the check box to turn off the option > click Next to display the Language dialog box.
58 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
9 Select the languages you want to install (worksheet item 25) > click Next. If you are not running the Agent Installation program on the same machine as the GroupWise Setup Advisor, the Domains/Post Offices dialog box is displayed. Continue with Step 10. If you are running the Agent Installation program on the same machine as the GroupWise Setup Advisor, the Setup Advisor passes the domain and post office information to the Agent Installation program so you are not prompted for it again. Skip to Step 13.
The MTA and POA must know the location of the domain and post office directories. 10 To specify the location of your domain, click Add > enter the domain name > enter the path to the domain directory > click OK. The location you enter for the domain directory is stored in the MTA startup file. When you start the MTA, it reads the startup file to find the location of the domain directory. The MTA then reads the domain database (WPDOMAIN.DB) in the domain directory for all configuration information it needs to run. The MTA startup file is located in the agent installation directory you specified in Step 7. The startup file is named domain.MTA, where domain is the first 7 letters of the domain name (for example, PROVO.MTA).
Installing a Basic GroupWise System 59
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
11 To specify the location of your post office, click Add > enter the post office name > enter the path to the post office directory > click OK. The location you enter for the post office directory is stored in the POA startup file. When you start the POA, it reads the startup file to find the location of the post office directory. The POA then reads the post office database (WPHOST.DB) in the post office directory for all configuration information it needs to run. The POA startup file is located in the agent installation directory you specified in Step 7. The startup file is named postoffice.POA, where postoffice is the first 7 letters of the post office name (for example, RESEARC.POA). 12 Click Next to display the Summary dialog box.
13 Click Install to install the agents. The Installation Complete dialog box appears when the files have been installed.
60 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
14 Select from the following options: Update the AUTOEXEC File: This option does not apply to the NT/ 2000 agents. Delete Obsolete GWADA Files and References to GWADA: This option does not apply when creating a new GroupWise system. Launch GroupWise Agents Now: This option applies only if you did not install the agents as Windows services. Select this option to start the GroupWise agents. 15 Click Finish > return to the workstation where the Setup Advisor is running (if necessary). The GroupWise Setup Progress: Set Up Client Software dialog box is displayed.
Installing a Basic GroupWise System 61
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
16 Continue with the next section, “Setting Up and Running the Client on Your Workstation” on page 62.
Setting Up and Running the Client on Your Workstation To set up the Windows GroupWise client on the current workstation: 1 Click Next to launch the GroupWise client setup program > follow the prompts. 2 When setup is finished, double-click the GroupWise shortcut on your desktop to start the GroupWise client. Because the GroupWise client can get the location of your post office from NDS, and because you don't yet have a password on your mailbox, the GroupWise client starts without prompting you for post office and password information. If the GroupWise client can't get the location of your post office from NDS or can't access the post office, the GroupWise Startup dialog box appears. You should make sure you are logged in through your own NDS user account and not through an Admin account, and your current NDS tree is the tree in which the post office is located. By default, the GroupWise client logs in to GroupWise as the user who is logged in at the workstation. If you are not logged in as yourself, you may receive a "user not found" error; enter your GroupWise user ID in the User ID field and click OK to log in.
62 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Setting A Mailbox Password Once you are logged in and using GroupWise, one of the first things you should do is set a password on your mailbox so that other users can't access it. For information about setting a password, see Help in the GroupWise client.
Sending Messages and Scheduling Appointments You can send messages to or schedule appointments with any users you've added to the post office. To test your system, you may want to send a message to yourself. As soon as users set up the GroupWise clients on their workstations (see “Setting Up Users' Workstations to Run the Client” on page 65), they will also be able to do send messages and schedule appointments.
Using Document Management Services GroupWise Document Management Services (DMS) lets you store documents in GroupWise libraries. Library documents can be shared with other users, versioned, and searched for within the library. The Setup Advisor created a library under the post office directory. For information about using Document Management Services, see Help in the GroupWise client.
Assigning GroupWise Accounts to Additional Users
Once you’ve finished your basic system setup, you may want to add additional users to the post office. To do so, follow the instructions in one of the following sections: ! “Assigning GroupWise Accounts to NDS Users” on page 63 ! “Assigning GroupWise Accounts to Non-NDS Users” on page 64
Assigning GroupWise Accounts to NDS Users To give an NDS user a GroupWise account on the post office: 1 In ConsoleOne, right-click the user you want to give an account to > click Properties. 2 Click the GroupWise tab to display the GroupWise Account page. 3 In the Post Office field, click the Browse button to select the post office. 4 In the Mailbox ID field, enter the name the user will use when logging in to his or her mailbox. The field defaults to the NDS username. 5 Click OK.
Installing a Basic GroupWise System 63
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Assigning GroupWise Accounts to Non-NDS Users You give a non-NDS user a GroupWise account on a post office by adding the user to NDS as a GroupWise external entity. To add a user as a GroupWise external entity: 1 In ConsoleOne, right-click the container where you want to create the GroupWise external entity > click New > click Object to display the New Object dialog box. 2 In the list, select GroupWise External Entity > click OK to display the Create GroupWise External Entity dialog box. 3 Define the following properties: GroupWise Object ID: Enter the user's GroupWise ID. The user's ID, along with the user's post office and domain, provide the user with a unique name within the GroupWise system. Last Name: Enter the user's last name. GroupWise Post Office: Select the post office where you want the user's mailbox. External Network ID: Enter the user's network ID for the network that he or she logs in to. Define Additional Properties: Select this option so that you can define additional information such as the user's first name. The user's first name appears in the GroupWise Address Book. Create Another External Entity: As soon as you select Define Additional Properties, this option becomes unavailable. Repeat the above steps if you need to create additional GroupWise external entities. 4 Click Create. 5 Enter the user's first name in the Given Name field. 6 Fill in any other fields you want > click OK. The user is given a GroupWise account on the post office you selected and can access his or her mailbox through the GroupWise client.
Logging in to GroupWise as a Non-NDS User Because non-NDS users do not log in to NDS, the GroupWise client cannot use the GroupWise information in NDS to automatically log in to the users' post office. When a non-NDS user starts the GroupWise client for the first
64 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
time, he or she will be prompted for a GroupWise user ID and post office location (IP address and port number). You will need to provide non-NDS users with this information. If you don’t want to provide non-NDS users with the post office information, you can automate the login process by creating a GroupWise name server. A GroupWise name server is a DNS host name entry that defines the TCP/IP address of the POA. During startup, the GroupWise client automatically looks for the GroupWise name server in DNS. For information about creating a GroupWise name server, see "Post Office Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation).
Setting Up Users' Workstations to Run the Client Each user who has an account in the post office needs to run the GroupWise client setup program. The setup program (SETUP.EXE) is located in the CLIENT\WIN32 directory on the GroupWise 6 CD or in the GroupWise software distribution directory. GroupWise Notify is installed with the GroupWise client. Notify runs in the background to alert users of messages they have received. The setup program gives users the option of placing Notify in the Startup folder so that it automatically starts whenever a user logs in. If a user does not place Notify in the Startup folder, he or she can manually start Notify from the Windows Start menu. For additional information about setting up the GroupWise client, see Chapter 6, “Installing the GroupWise Client,” on page 165.
Other Things You Can Do
Once you have set up your basic GroupWise system, you can expand the system by: ! Defining resources that users can schedule. See "Resources" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation). ! Defining groups of users that GroupWise users can select when addressing messages. See "Distribution Lists" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation).
Installing a Basic GroupWise System 65
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! Configuring your current post office's library or setting up additional libraries. See "Libraries and Documents" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation). ! Setting up GroupWise Remote so that users can access their mailboxes from a computer that is not directly connected to your network. See "Client" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation). ! Changing the GroupWise client from standard Online mode to Caching mode so that users’ messages are stored on a local drive rather than at the post office. See "Client" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/ documentation). ! Adding additional post offices to the domain. See "Post Offices" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation). ! Adding additional domains to the system. See "Domains" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation). ! Installing the MTA or POA on a different machine than the one you installed to during the basic system setup. See Chapter 5, “Installing GroupWise Agents,” on page 137. ! Setting up GroupWise Monitor to monitor your GroupWise agents. See Chapter 4, “Installing GroupWise Monitor,” on page 125. ! Setting up messaging access to the Internet through the GroupWise Internet Agent. See Chapter 2, “Installing GroupWise Internet Agent,” on page 75. ! Setting up GroupWise WebAccess so that users can access their mailboxes through a Web browser on a computer or wireless device such as a telephone. See Chapter 3, “Installing GroupWise WebAccess,” on page 97. ! Connecting to other GroupWise 5.x or 6 systems. See "System" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
66 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Basic GroupWise System Worksheet
The GroupWise Installation Advisor helps you install the GroupWise software. It then launches the GroupWise Setup Advisor, which helps you set up your first domain and post office. The Advisors will prompt you for the information in the worksheet in the order listed. You should print the worksheet and carefully fill in the information for your system.
Item Example Explanation
1) Tree Name: NOVELL_TREE Specify the name of the NDS tree where your domain and post office will be installed. Because GroupWise introduces new objects into the tree, the NDS schema must be extended.
See “NDS” on page 17.
2) Languages to Install: English Specify the languages to install for GroupWise Administrator, the German GroupWise agents, and the GroupWise clients.
See “GroupWise Languages” on page 20.
3) ConsoleOne Path: C:\NOVELL\CONSOLEONE\1.2 Specify the path to a ConsoleOne location, either on the local workstation or on a network server. The GroupWise Installation Advisor installs the GroupWise Administrator snap-in files in the specified location.
ConsoleOne 1.2d.1 (or higher) is required. If necessary, you can install ConsoleOne 1.2d.1 at the same time you install the GroupWise Administrator snap- in.
See “ConsoleOne” on page 17.
Installing a Basic GroupWise System 67
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
4) Software Distribution Z:\GRPWISE\SOFTWARE Specify the directory path for the Directory: software distribution directory. If the directory does not exist, it will be created.
The path should be from the perspective of the network station you will use to install GroupWise.
See “GroupWise Software Distribution Directory” on page 18.
5) Software Selection: GroupWise Administrator snap-in Select the software you want copied to the software distribution ! GroupWise Administrator NLM agents directory. snap-in Windows client ! Monitor See “GroupWise Software Distribution Directory” on page ! NLM agents 18. ! NT/2000 agents ! WebAccess ! Internet Agent ! Windows client
6) System Name: Novell Specify a one-word name. Names can reflect companies, locations, and so forth.
See “System and Domain Names” on page 21.
7) Domain Name: Provo Specify a one-word name. Names can reflect locations, organizations, and so forth.
See “System and Domain Names” on page 21.
68 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
8) Domain Directory: J:\PROVO Specify the path for the domain directory. If the directory does not exist, it will be created.
The path should be from the perspective of the workstation you will use to install GroupWise.
See “Domain Directory” on page 22.
9) Domain Context: groupwise.novell Specify the NDS context where you want to create the Domain object. Make sure the context exists before you start installing GroupWise.
See “Domain Context” on page 23.
10) Domain Language: English Specify a language for the domain. The language determines how times, dates, and numbers are displayed in the GroupWise client and affects the sorting order for items in the GroupWise Address Book.
See “Domain Language” on page 26.
11) Domain Time Zone: Mid-Atlantic Specify the time zone where the domain is located. The time zone information is used to ensure that times for messages sent between time zones are adjusted properly.
See “Domain Time Zone” on page 27.
12) Post Office Name: Research Specify a one-word name. Names can reflect locations, organizations, and so forth.
See “Post Office Name” on page 27.
Installing a Basic GroupWise System 69
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
13) Post Office Directory: J:\RESEARCH Specify the path for the post office directory. If the directory does not exist, it will be created.
The path should be from the perspective of the workstation you will use to install GroupWise.
See “Post Office Directory” on page 28.
14) Post Office Context: groupwise.novell Specify the NDS context where you want to create the Post Office object. Make sure the context exists before you start installing GroupWise.
See “Post Office Context” on page 29.
15) Post Office Language: English The post office language defaults to the domain language. Specify a different language if you do not want the post office to use the default domain language.
See “Post Office Language” on page 30.
16) Post Office Time Zone: Mid-Atlantic The post office time zone defaults to the domain time zone. Specify a different time zone if the post office is not in the same time zone as the domain.
See “Post Office Time Zone” on page 30.
70 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
17) Post Office Link: TCP/IP link Select whether you want the Message Transfer Agent (MTA) ! TCP/IP link to link to the post office through a ! Direct link TCP/IP connection to the Post Office Agent (POA) or a direct connection to the post office directory.
See “MTA Link to the Post Office” on page 34.
18) POA Network Address: IP address: 123.456.78.90 Specify the IP address or DNS host name of the POA’s machine. ! IP address or DNS host name: C/S port: 1677 ! Client/Server port: By default, the POA listens for the MT port: 7101 GroupWise client on Client/ ! Message transfer port: Server port 1677. If this port is HTTP port:7181 already being used, specify a ! HTTP port: different C/S port number (for example, 1678).
By default, the POA listens for the MTA on Message Transfer port 7101 (if the MTA and POA are communicating using TCP/IP). If this port is already being used, specify a different MT port number (for example, 7102).
By default, the POA uses HTTP port 7181 for the Web console. The Web console enables you to view POA information through a Web browser. If this port is already being used, specify a different HTTP port number (for example, 7183).
See “MTA Link to the Post Office” on page 34.
Installing a Basic GroupWise System 71
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
19) MTA Network Address: IP Address: 123.456.78.91 This item applies only if you selected TCP/IP as the post ! IP address or DNS host name: MT port: 7100 office link method (item 17). ! Message transfer port: HTTP port:7180 Specify the IP address or DNS ! HTTP port host name of the machine running the Message Transfer Agent.
By default, the MTA listens for the POA on Message Transfer port 7100. If this port is already being used, specify a different MT port number (for example, 7103).
By default, the MTA uses HTTP port 7180 for the Web console. The Web console enables you to view MTA information through a Web browser. If this port is already being used, specify a different HTTP port number (for example, 7182).
See “MTA Link to the Post Office” on page 34.
20) Post Office Users: jsmith.r&d.novell Specify the users who will have mailboxes on the post office. The Setup Advisor lets you browse the NDS tree to select the users you want.
Adding users at this point is optional. After the Setup Advisor has finished, you can add users to the post office at any time.
See “Post Office Users” on page 30.
21) Agent Platform: NetWare Specify the platform (NetWare or Windows NT/2000) where you will run the GroupWise agents.
See “Agent Platform” on page 32.
72 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
22) Agent Installation Path: Z:\SYSTEM Specify the path to the directory where you want to install the agents.
We recommend that you install the NetWare NLM agents to the SYS:\SYSTEM directory to simplify the use of startup files and ensure that dependent NLM programs will load properly.
You can install the Windows NT/ 2000 agents to any directory on the Windows NT/2000 machine. Because the installation is done from the NT/2000 machine, the default is C:\GRPWISE.
See “Agent Location” on page 32.
23) NT/2000 Agent Installation Install GroupWise agent software This item applies only if you are Options: installing the NT/2000 agents. Install as NT/2000 services ! Install GroupWise agent Specify the installation options software you want to use.
! Install and configure SNMP for The Install GroupWise Agent GroupWise Agents Software option needs to be ! Install as NT/2000 services selected to install the files. The Install and Configure SNMP for GroupWise Agents option requires the SNMP service to already be enabled on the NT/ 2000 machine.
The Install as NT/2000 Services option configures the agents as Windows services.
See “Windows Application vs. Windows Service (NT/2000 Agents Only)” on page 34.
Installing a Basic GroupWise System 73
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Example Explanation
24) Enable Web Console: Yes Specify whether or not to enable agent statistics and diagnostic ! Yes/No Username: gwagents information to be displayed through a Web browser. ! Username: Password: web ! Password: If you select Yes, specify the username and password you want to use to access the agents.
See “Web Console” on page 35.
25) Agent Language: English Specify the language in which you want to be able to run the agents.
See “Agent Language” on page 35.
26) NT/2000 Service Information: Use a user account: username is This item applies only if you are gwagents, password is admin installing the NT/2000 agents as ! Use local system account Windows services. ! Use a user account Startup: automatic Select whether you want the ! Startup: automatic or manual services to use the local system account or another user account. If the domain and post office directories are on the same NT/ 2000 machine as the agents, you can use the local system account. If the domain and post office directories are on a different server, specify a different user account that exists in NDS and has rights to the domain and post office directories.
Select whether you want to manually start the services or have them start automatically when the machine starts.
See “Windows Application vs. Windows Service (NT/2000 Agents Only)” on page 34.
74 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Installing GroupWise Internet Agent
This section explains how the GroupWise® Internet Agent adds Internet messaging services to your existing GroupWise system. It also explains how to install and configure the GroupWise Internet Agent software. ! “Overview” on page 75 ! “Preparing to Install the Internet Agent” on page 80 ! “Setting Up the Internet Agent for Windows NT/2000” on page 83 ! “Setting Up the Internet Agent NLM” on page 89
Overview
The GroupWise Internet Agent allows communication between GroupWise users and users of other messaging systems who use the Internet to send e- mail. The Internet Agent picks up inbound e-mail messages from the Internet, converts them from RFC-822, SMTP, or MIME format to the GroupWise message format, and then passes the converted messages to the GroupWise Message Transfer Agent (MTA). For outgoing messages transported by the Internet, the GroupWise MTA passes the message to the Internet Agent, which then converts the message to Internet messaging format, and then sends it to the designated Internet address.
Installing GroupWise Internet Agent 75
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
PO Internet
PO Domain
PO
GWIA Domain Domain
PO
PO
Domain
PO
PO
Choose from the following list of topics to learn more about the capabilities of the GroupWise Internet Agent. ! “GroupWise Internet Agent Features” on page 76 ! “Ways to Use the GroupWise Internet Agent” on page 80
GroupWise Internet Agent Features
The GroupWise Internet Agent includes the following features: ! “SMTP/MIME Service” on page 77 ! “POP3 Service” on page 77 ! “LDAP and IMAP4 Services” on page 77 ! “SMTP Dial-Up Service” on page 78 ! “Multiple Threading” on page 78 ! “Multiple Foreign Names” on page 78
76 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! “Flexible Addressing” on page 78 ! “Internet Users in the Address Book” on page 79 ! “Connect to Other GroupWise Systems Through the Internet” on page 79 ! “Merge With Other GroupWise Systems Through the Internet” on page 79 ! “Access Control” on page 79 ! “Accounting” on page 79 ! “Mail Hub / Smart Host Server” on page 79 ! “SNMP-Compliant (NLM Version)” on page 79 ! “SMP Support (NLM Version)” on page 80 ! “DNS Name Resolution” on page 80
SMTP/MIME Service The SMTP/MIME service in the Internet Agent allows you to send and receive e-mail with standard encoding on attachments, international character sets, and multipart messages. Multimedia e-mail with graphics, sound, and video can also be exchanged.
POP3 Service The POP3 service in the Internet Agent allows you to download messages from your GroupWise post office to a POP3 client application such as a Web browser's e-mail program or a Telnet application. The Internet Agent acts as the POP3 server, providing a TCP connection between the user's GroupWise post office and a POP3 client. Accessing the GroupWise post office via the Internet Agent's POP3 server capability, users can retrieve their e-mail messages and manage them through user ID login options.
LDAP and IMAP4 Services The Internet Agent supports the Lightweight Directory Access Protocol (LDAP) directory standard with LDAP server capability that allows access for directory searches of GroupWise post offices. Using LDAP Public Access, Internet mail clients can do lookups on GroupWise users and address information. The GroupWise Internet Agent also supports the Internet Messaging Access Protocol 4 (IMAP4). As an IMAP4 server, the Internet
Installing GroupWise Internet Agent 77
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Agent allows IMAP4-compliant e-mail clients to read and manipulate GroupWise messages.
SMTP Dial-Up Service The Internet Agent includes the functionality of an SMTP dial-up feature. This can be useful when your system does not meet the requirements of a dedicated Internet connection, or when you prefer not to have a permanent Internet connection. With the SMTP dial-up feature, you can periodically check the message store without having to maintain a permanent link.
Multiple Threading Multiple threading allows more than one send or receive process to be running concurrently. You can configure the number of threads to enhance the speed and performance of the Internet Agent. The number of thread switches are set separately for the SMTP/MIME service, POP3 service, IMAP4 service, and LDAP service.
Multiple Foreign Names The Internet Agent can be seen as one or more Internet host addresses if user aliases, Internet Agent aliases, or post office aliases are used. Multiple foreign names can also be used to help implement a firewall or central mail hub.
Flexible Addressing The Internet Agent offers full GroupWise addressing support, including system groups, nicknames, and individual users. The Internet Agent also takes advantage of GroupWise Internet addressing, which allows inbound messages addressed in a variety of formats to be delivered to GW users. These formats include: ! Userid@Idomain ! First.Last@Idomain ! Last.First@Idomain ! user.po.domain@Idomain ! user.po@Idomain
78 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Internet Users in the Address Book Internet users can be added to the GroupWise Address Book so users won't have to remember long Internet addresses.
Connect to Other GroupWise Systems Through the Internet Using passthrough addressing, you can connect to other GroupWise systems anywhere on the Internet and have access to all of the GroupWise features. The Internet simply becomes a mail transport medium for GroupWise.
Merge With Other GroupWise Systems Through the Internet Using passthrough addressing, you can merge and administer other GroupWise systems anywhere on the Internet.
Access Control The Internet Agent program includes security capabilities called Access Control that allow administrators to control inbound and outbound messages. Access Control can help you reduce costs and provide added security.
Accounting The accounting feature provides inbound and outbound tracking of messages passing through Internet Agent. This lets administrators track how the Internet Agent is being used.
Mail Hub / Smart Host Server The Internet Agent can function as an SMTP mail hub, or smart host, to resend messages it receives that should go to another host.
SNMP-Compliant (NLM Version)
The NLMTM version of the Internet Agent can be managed by any SNMP- compliant network manager, such as the Novell® ManageWise® network management suite or the alarm management features of Novell ZENworksTM for Servers. The NT version of the Internet Agent includes SNMP support for Windows* NT* 4.0 and Windows 2000.
Installing GroupWise Internet Agent 79
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
SMP Support (NLM Version) The Internet agent supports Symmetric Multi-Processing (SMP), letting it take advantage of a server with multiple processors.
DNS Name Resolution The Internet Agent does not require an external smart host to resolve Internet domain names.The Internet Agent can perform IP address resolution directly with its DNS server, and is also MX record-aware.
Ways to Use the GroupWise Internet Agent You can use the GroupWise Internet Agent in the following ways. ! Exchanging e-mail messages, appointments, notes, tasks, while including text files, graphics, sound or video clips, programs, and nearly any other file type as an attachment. ! Downloading and managing e-mail messages from any GroupWise post office to a remote POP3 or IMAP4 client application such as your Web browser's e-mail program. ! Subscribing to Internet list servers to share information with other people on any topic of interest. ! Connecting GroupWise systems seamlessly through the Internet by using the passthrough addressing feature. For example, a GroupWise system in Los Angeles could send mail to a GroupWise system in Denmark with full GroupWise functionality and features. ! Administering other GroupWise systems through the Internet by using the passthrough feature. The Internet can be a cost-effective way to connect your company's GroupWise systems throughout the world.
Preparing to Install the Internet Agent
The information in this section can help you prepare to install the GroupWise Internet Agent. ! “GroupWise System Prerequisites” on page 81 ! “Information for the Internet Service Provider” on page 81 ! “Performance Considerations” on page 82
80 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
When you have met the prerequisites covered in this section, and you have access to the Internet, you can install and configure the Internet Agent. For more information, see "Internet Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/ documentation).
GroupWise System Prerequisites
The first requirement for installing the GroupWise Internet Agent is to have an existing GroupWise system set up. GroupWise system prerequisites include: ! A GroupWise domain and a GroupWise post office already installed. ! GroupWise Message Transfer Agent already installed. ! GroupWise client already installed on user workstations. ! Access to Novell ConsoleOneTM for use in configuring the Internet Agent. If you have a heterogeneous system with GroupWise 5.x and GroupWise 6.x post offices, the GroupWise 6 Internet Agent will not be able to access a GroupWise 5.x post office with POP or IMAP clients.
Information for the Internet Service Provider
To use the Internet Agent, you must have access to an Internet host computer by subscribing to an Internet Service Provider.You need to ask your Internet service provider (ISP) about the following GroupWise Internet Agent requirements: ! “Internet Connection” on page 81 ! “Access to DNS” on page 82 ! “IP Addresses” on page 82
Internet Connection You can connect to the Internet using a standard switched telephone line or a direct connection over a leased line. Consult with your ISP about the connection type that best suits your needs.
Installing GroupWise Internet Agent 81
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Access to DNS The Domain Name System is used by the Internet to resolve address information. The Internet Agent can access DNS via a smart host provided by the ISP or by making direct queries. Depending upon the platform and the kind of TCP/IP address resolution you use, you may need to obtain the IP address and DNS name from your Internet service provider.
IP Addresses The computer running the Internet Agent is the only computer in your LAN that requires an IP address. Contact your Internet service provider to obtain an IP address and fully qualified host name. Depending upon the IP address you receive, you may also need to get an IP subnet address. This subnet address may be required by your TCP/IP connectivity software.
Performance Considerations
To get the best performance from the GroupWise Internet Agent, consider the following factors that can affect Internet Agent and GroupWise system performance.
Distribution of Internet Agent Users Carefully examine the anticipated distribution patterns of your users to design your Internet Agent placement for maximum effectiveness. If you have a large, multiple-domain, multiple-post office system, consider how many users will use the Internet Agent, in what domains they are located, and how much traffic will be generated. For example, if there are many users in the Sales domain who will send many messages to sales contacts over the Internet, and much less traffic is anticipated from other domains in your system, it might be best to place the Internet Agent in the Sales domain. By doing this, Message Transfer Agents not located in the Sales domain will process fewer messages.
Internet Agent and Message Transfer Agent Platform Issues If you have a mixture of platforms for your Message Transfer Agent and other gateways, platform may be a consideration. Ensure that your Message Transfer Agent is fast enough to handle the volume of mail the Internet Agent can process. If the Internet Agent will be processing a large number of
82 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
messages, you should place it in a domain serviced by a fast Message Transfer Agent or in a domain that contains only the Internet Agent.
Network Computing Capacity If many of your users have unrestricted Internet access from GroupWise, your system may overload with message traffic. If you anticipate a significant increase in message flow and storage, you may want to upgrade certain computer components associated with your GroupWise system. Components that may need to be upgraded include memory, processor, and hard disk space. For example, the domain containing the Internet Agent may need: ! A faster processor in the file server running the Message Transfer Agent and the Internet Agent to process the increased number of messages faster. ! More memory in the file server running the Message Transfer Agent and the Internet Agent to increase file access performance. ! More hard disk space on post offices to store the additional messages that users may receive from the Internet.
Internet Connection Speed The Internet connection you have affects message delivery performance. If you have a fast connection to the Internet, you will probably want to optimize your Internet Agent and Message Transfer Agent. If you have a slow transmission speed you may not need to be concerned with the speed of your GroupWise system components relative to the Internet Agent.
Setting Up the Internet Agent for Windows NT/2000
The information in this section will help you set up the GroupWise Internet Agent for Windows NT/2000. The following list summarizes the tasks required to set up the Internet Agent. ! “Meeting System Requirements” on page 84 ! “Installing the NT/2000 Internet Agent Software” on page 84 ! “Setting Up Internet Services” on page 87 ! “Assigning a Postmaster” on page 87 ! “Setting Up DNS Integration” on page 87 ! “Starting the NT/2000 Internet Agent” on page 89
Installing GroupWise Internet Agent 83
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Meeting System Requirements
In order to install the GroupWise Internet Agent for NT/2000 you need: ! A workstation where the Internet Agent can be installed ! TCP/IP connectivity ! Access rights to the domain directory where you want to install the Internet Agent. The Install program copies the Internet Agent files to the subdirectories listed under the domain. Without access rights to the domain directory, the Install program cannot run. ! Access rights to NDS® where the Groupwise domain resides.
Internet Agent Station Requirements The Internet Agent station is the workstation used to run the GroupWise Internet Agent. The following specifications refer only to the Internet Agent requirements and do not include additional operating system requirements: ! 15 MB of disk space. This is the amount of disk space needed for the Internet Agent program files. It does not take into account the message files, which may or may not be located on the same machine. ! 10-12 MB of RAM. This is the amount of memory the Internet Agent needs to operate. It does not include memory for the Windows NT/2000 operating system or for TCP/IP connectivity. This amount can increase depending on message size and complexity. ! Windows NT (version 4.0 or higher with Service Packs applied) or Windows 2000. ! If the Internet Agent is installed on Windows 2000 and if the GroupWise domain directory that is accessed by the Internet Agent is on a NetWare® server (or any non-Windows server), you will need to apply Microsoft* HotFix Q266066 to the Windows 2000 operating system. To obtain the HotFix, contact Microsoft Support at the Microsoft Support Web site (http://support.microsoft.com/directory).
Installing the NT/2000 Internet Agent Software
The GroupWise Internet Agent Installation program is a Windows application that can be run from a Windows workstation. The NT/2000 Internet Agent software is located on the GroupWise 6 CD. You can run the installation program from a CD drive or from the software distribution directory, which is created during the GroupWise installation.
84 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The Internet Agent files are located in the \INTERNET\GWIA directory on the GroupWise 6 CD. This is the directory name you type when you are asked for the path to the Internet Agent files during the installation process. If you are installing from the software distribution directory, you need to specify the location where the files were copied by the GroupWise installation. By default, this directory location is \GRPWISE\SOFTWARE\INTERNET\GWIA. The GroupWise 6 installation program will do the following: ! Install GroupWise Internet Agent software. ! Create the Internet Agent object in NDS. ! Configure startup files for the Internet Agent. ! Test the server you are installing to for correct Internet configuration. To install the Internet Agent: 1 Insert the GroupWise 6 CD into the CD drive on a Windows workstation. or If you have already copied GroupWise Internet Agent files to the software distribution directory, you can also run the installation program from that network directory (GRPWISE\SOFTWARE\INTERNET\GWIA). 2 Select Start > Run. 3 Type the drive and path to INSTALL.EXE on the CD or in the software distribution directory > click OK. 4 At the License Agreement dialog box, click Accept. 5 At the Welcome dialog box, click Next. 6 At the Software Platform dialog box, select Windows NT > click Next to display the GroupWise Installation Path dialog box. 7 At the Installation Path dialog box, specify a local path where the Internet Agent files will be copied > select the options you want to install with the NT version of the Internet Agent > click Next.
NOTE: The "Install and configure SNMP for GroupWise agents" option is available only if SNMP was previously installed for Windows NT/2000.
Installing GroupWise Internet Agent 85
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 At the Web Console Information dialog box, you can choose whether to enable a Web browser view of the information provided by the Internet Agent. If you click the Enable Web Console check box, you must type an arbitrary user name and password > enter the HTTP port parameter where the Web browser can find the Internet Agent > click Next. 9 At the Relay Host screen, choose whether the Internet Agent will deliver outbound mail or forward mail to another relay host machine for delivery > click Next. 10 If you chose to install the Internet Agent as an NT service (see Step 7), the NT Service Information dialog box is displayed. Choosing either of the first two options disables the other: ! Use local system account ! Use this NT user account If you choose the NT user account option, you must type the NT user account name and the account password. Choose a startup method for the NT Service > click Next. 11 At the GroupWise Domain screen, select the domain directory where the Internet Agent object will reside > specify a name for the Internet Agent subdirectory that will be created under the \WPGATE directory > click Next. 12 At the Ready to Install screen, click Install to begin copying files to the server. 13 There may be configuration tasks that need to be completed in order to use the Internet Agent. If so, you will see a Post Installation Task List. You can double-click any task in the list for specific configuration instructions and troubleshooting tips. 14 Click Finish to close the Install program. The installation program will automatically create and configure an NDS object for the newly installed GroupWise Internet Agent. You can also manually create and configure an NDS object for administering the Internet Agent. For more information about creating and configuring the Internet Agent object, see Appendix A, “Manually Creating the NDS Object for the Internet Agent,” on page 201.
86 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Setting Up Internet Services
The GroupWise Internet Agent supports Internet messaging standards such as the Post Office Protocol 3 (POP3), Internet Messaging Access Protocol 4 (IMAP4), and Lightweight Directory Access Protocol (LDAP). The Internet Agent also offers dial-on-demand capability with the SMTP dial-up feature. To learn how to enable and configure these services, see "Internet Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Assigning a Postmaster
The Internet requires each site to assign at least one user to be the Postmaster. The Postmaster is assigned to be the recipient of messages addressed to postmaster@host. If the /badmsg startup switch is set with either the Send option or the Both option, the Postmaster will also receive any error messages processed by the Internet Agent. To assign a postmaster: 1 In ConsoleOne, right-click the Internet Agent object > click Properties > select the Administrators page. 2 Click Add > select a user from the list as the administrator > click OK. 3 With the selected user highlighted, select the Postmaster Administrator Role > click OK.
Setting Up DNS Integration
In order to resolve IP addresses when sending e-mail over the Internet, the GroupWise Internet Agent can use either MX records and the Domain Name System (DNS), or a HOSTS file.
DNS Address Resolution Using DNS is the preferred method of resolving IP addresses. DNS translates Internet names like novell.com to IP addresses like 151.155.111.11, which the TCP/IP protocol interprets to route and deliver messages to the correct destination.
Installing GroupWise Internet Agent 87
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
HOSTS File Address Resolution A HOSTS file is another way the Internet Agent can resolve IP addresses. The HOSTS file is a text file containing IP addresses associated with long host names. The Internet Agent looks up the name of the destination computer, identifies the corresponding IP address in the HOSTS file, and delivers the e- mail message. The HOSTS file can be very large and can contain many IP addresses.
Setting Up DNS with the RESOLV File Before starting the GroupWise Internet Agent and sending messages, make sure the DNS integration is set up correctly. DNS integration is set up in the RESOLV.CFG file, which contains the numeric IP address of the DNS server. The Internet Agent uses the RESOLV.CFG file to find the DNS server. It then uses the DNS server to find IP addresses on the Internet. The RESOLV.CFG file is automatically configured when you enter the correct information for DNS into the TCP/IP configuration screens. If you can use TCP/IP on your NT/2000 workstation for Web browsing, use FTP, or do some other TCP/IP function, then your TCP/IP connectivity is probably configured correctly. In Windows NT or Windows 2000, the RESOLV.CFG file is accessed through the Config > NetWork > Protocols > TCPIP menu path. The RESOLV.CFG file requires at least the first two lines, as shown in the following sample file. The Internet domain name provided by the Internet service provider is on the first line. Foo.com is used in this example for the domain name. The nameserver value is the numeric IP address for the DNS server.
Example RESOLV.CFG File
domain.foo.com nameserver 151.155.111.11 nameserver 151.155.111.12 nameserver 151.155.111.13 If you use a HOSTS name file instead of the DNS server, you must include the name and IP address for each host computer you intend to communicate with. If the RESOLV.CFG file does not exist or if the values are incorrect, you will receive "Host Unknown - 550" errors.
88 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Starting the NT/2000 Internet Agent
The GroupWise Internet Agent automatically uses a startup file named GWIA.CFG when it starts. You can specify a different startup file. To start the GroupWise Internet Agent: 1 Log the Internet Agent station on to the network. 2 Double-click the GroupWise Gateways folder icon > double-click the GroupWise Internet Agent icon to start the program and to display the Internet Agent operation screen. If the Internet Agent was installed as a Windows NT/2000 service, it will start automatically when the NT/2000 machine starts up. You can manually stop and start the Internet Agent by accessing the Control Panel > click Services > click Start or click Stop.
Setting Up the Internet Agent NLM
The information in this section will help you set up the GroupWise Internet Agent NLM. The following list summarizes the tasks required to set up the Internet Agent. ! “Meeting System Requirements” on page 89 ! “Testing TCP/IP Functionality” on page 90 ! “Installing the Internet Agent NLM Software” on page 91 ! “Setting Up Internet Services” on page 93 ! “Assigning a Postmaster” on page 93 ! “Setting Up DNS Integration” on page 94 ! “Verifying the HOSTS File” on page 95 ! “Starting the Internet Agent NLM” on page 96
Meeting System Requirements
In order to install the GroupWise Internet Agent NLM, you need: ! A file server where the Internet Agent can be installed ! TCP/IP connectivity
Installing GroupWise Internet Agent 89
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! Access rights to the domain directory where you want to install the Internet Agent. The Install program copies the Internet Agent files to the subdirectories listed under the domain. Without access rights to the domain directory, the Install program cannot run. ! Access rights to NDS where the Groupwise domain resides.
Internet Agent Server Requirements The Internet Agent station is the file server used to run the GroupWise Internet Agent. The following specifications refer only to the Internet Agent requirements and do not include additional operating system requirements: ! 15 MB of disk space. This disk space amount is what is needed for the Internet Agent program files only. It does not take into account the message files, which may or may not be located on the same machine. ! 10-12 MB of RAM. This is the amount of memory the Internet Agent needs to operate. It does not include memory for the NetWare operating system or for the TCP/IP NLM. This amount can increase, depending on message size and complexity. ! NetWare 5.0 or higher with all available NetWare Support Packs applied for the NetWare release you are using.
TCP/IP You need to ensure that the TCP/IP NLM is functioning correctly in your system and you have the correct version before installing the Internet Agent NLM. If TCP/IP is not functioning correctly within your system, the Internet Agent will not work. If you are uncertain whether TCP/IP is already configured on your file server, see "Internet Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation) to verify that it is working. If TCP/IP is not currently running, you can configure the TCP/IP NLM by using the INETCFG program that provides an automated menu for configuration, or you can use the AUTOEXEC.NCF file to manually configure TCP/IP. See your TCP/IP manual for more details.
Testing TCP/IP Functionality
Unless you are certain that TCP/IP is functioning correctly on your file server, use the following procedures to help you check correct TCP/IP functionality.
90 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! From the file server prompt, enter config. This command lists the network boards in your file server and the protocols they are bound to. Verify that one of the LAN protocols listed is IP. ! From the file server prompt, enter modules. This command lists all the NLM software loaded on your file server. Verify that one of them is TCPIP.NLM. ! If your version of NetWare comes with the PING utility, ping the file server IP address from the file server console. The syntax for ping is load ping file_server_address. (For example, load ping 151.155.111.11.) The ping program should record responses received from the file server. If it does not, there may be a problem. With NetWare 5.x, the PING NLM can perform DNS lookups, so you can use the syntax load ping hostname to see if DNS is working properly. (For example, load ping mail.acme.com).
Installing the Internet Agent NLM Software
The GroupWise Internet Agent Install program is a Windows application that can be run from a Windows workstation. The Internet Agent NLM software is located on the GroupWise 6 CD. You can either run the installation program from a CD drive or from the software distribution directory which is created during the GroupWise installation. The Internet Agent files are located in the \INTERNET\GWIA directory on the GroupWise 6 CD. This is the directory name you type when you are asked for the path to the Internet Agent files during the installation process. If you are installing from the software distribution directory, then you need to specify the location where the files were copied by the GroupWise installation. By default, this directory location is server\volume:GRPWISE\SOFTWARE\INTERNET\GWIA. The installation program will do the following: ! Install the GroupWise Internet Agent software. ! Create the Internet Agent object in NDS. ! Configure startup files for the Internet Agent. ! Test the server you are installing to for correct Internet configuration. To install the Internet Agent: 1 Insert the GroupWise 6 CD into the CD drive on a Windows workstation. or
Installing GroupWise Internet Agent 91
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If you have already copied the GroupWise Internet Agent files to the software distribution directory, you can also run the install program from that network directory (GRPWISE\SOFTWARE\INTERNET\GWIA). 2 Select Start > Run. 3 Type the drive and path to INSTALL.EXE on the GroupWise 6 CD or in the software distribution directory > click OK. 4 At the License Agreement dialog box, click Accept. 5 At the Welcome dialog box, click Next. 6 At the Software Platform dialog box, select NetWare > click Next. 7 At the NLM Installation Paths dialog box, specify the paths where the Internet Agent executables and script files will be copied. If you want the Internet Agent to start automatically when the server restarts, select Update AUTOEXEC File. If you are using NetWare Cluster ServicesTM and the location where you are installing the Internet Agent is part of an existing cluster, select Configure GroupWise Agents for Clustering. Click Next. 8 At the Web Console Information dialog box, you can choose whether to enable a Web browser view of the information provided by the Internet Agent. If you click the Enable Web Console check box, you must type an arbitrary user name and password > enter the HTTP port parameter where the Web browser can find the Internet Agent > click Next. 9 At the Relay Host screen, choose whether the Internet Agent will deliver outbound mail or forward mail to another relay host machine for delivery > click Next. 10 At the GroupWise Domain screen, select the domain directory where the Internet Agent object will reside > specify a name for the Internet Agent subdirectory that will be created under the domain\WPGATE directory > click Next. 11 At the Ready to Install screen, click Install to begin copying files to the server.
92 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
12 There may be configuration tasks that need to be completed in order to use the Internet Agent. If so, you will see a Post Installation Task List. You can double-click any task in the list for specific configuration instructions and troubleshooting tips. 13 Click Finish to close the Install program. The installation program will automatically create and configure an NDS object for the newly installed GroupWise Internet Agent. You can also manually create and configure an NDS object for administering the Internet Agent. For more information about creating and configuring the Internet Agent object, see Appendix A, “Manually Creating the NDS Object for the Internet Agent,” on page 201.
Setting Up Internet Services
The GroupWise Internet Agent supports Internet messaging standards such as the Post Office Protocol 3 (POP3), Internet Messaging Access Protocol 4 (IMAP4), and Lightweight Directory Access Protocol (LDAP). The Internet Agent also offers Internet dial-on-demand capability with the SMTP dial-up feature. By default, support for these services is enabled during installation; support for SMTP dial-up is not enabled. To learn how configure these services, see "Internet Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Assigning a Postmaster
The Internet requires that each site assign at least one user to be the Postmaster. The Postmaster is assigned to be the recipient of messages addressed to postmaster@host. If the /badmsg startup switch is set with either the Send option or the Both option, the Postmaster will also receive any error messages processed by the Internet Agent. To assign a postmaster: 1 In ConsoleOne, right-click the Internet Agent object > click Details > select the Administrators page. 2 Click Add > select a user from the list as the administrator > click OK. 3 With the selected user highlighted, select the Postmaster Administrator Role > click OK.
Installing GroupWise Internet Agent 93
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Setting Up DNS Integration
In order to resolve IP addresses when sending e-mail over the Internet, the GroupWise Internet Agent can use either MX records and the Domain Name System (DNS), or a HOSTS file.
DNS Name System The program can use either MX records and DNS or a HOSTS file to resolve IP addresses and send mail to the Internet. The DNS is the preferred way of resolving IP addresses. The DNS translates Internet host names like novell.com to IP addresses like 151.155.111.11, which the TCP/IP protocol uses to get messages to the correct destination.
HOSTS File Address Resolution A HOSTS file is the another way the program can resolve IP addresses. The HOSTS file is a text file containing IP addresses associated with names. The program performs a lookup in the HOSTS file of the IP address of the computer where mail is being sent, and then sends the message. This file can be very large and contain many IP addresses. If you are using the HOSTS file to resolve IP addresses and if the Internet address you are sending to is not in your HOSTS file, you will be unable to send to that address.
Setting Up DNS with the RESOLV File Before starting the Internet Agent and sending messages, make sure the DNS integration is set up correctly. DNS integration is set up in the RESOLV.CFG file, which contains the numeric IP address of the DNS server. You can get the IP address of your DNS server from your Internet service provider. The Internet Agent uses the RESOLV.CFG file, which contains the IP address of the DNS server, to find the DNS server. Then the DNS server locates IP addresses on the Internet. RESOLV.CFG is a text file that must be located in the server SYS:\ETC directory. If you do not have a RESOLV.CFG file and you want the Internet Agent to resolve IP addresses without a HOSTS file, you should create the RESOLV.CFG file manually. Follow the pattern given in the sample shown later in this topic. Make sure that you replace the sample values with the correct values for your system. If you already have a RESOLV.CFG file, you should check the file to ensure it contains the correct information for your system.You can include up to three nameserver IP addresses. The first IP address is for the primary DNS server. If you have a DNS server at your site, it should be the DNS server listed first in the file. Other DNS servers are used only if the program is unable to get a response from the first server.
94 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The RESOLV.CFG file requires at least the first two lines, as shown in the following sample file. The Internet domain name provided by the Internet service provider is on the first line. Foo.com is used in this example for the domain name. The nameserver value is the decimal IP address for the DNS server.
Example RESOLV.CFG File
domain.foo.com nameserver 151.155.111.11 nameserver 151.155.111.12 nameserver 151.155.111.13
If you use a HOSTS name file instead of the DNS server, you must include the name and IP address for each host computer you intend to communicate with. If the RESOLV.CFG file does not exist in SYS:\ETC or if the values are incorrect, you will receive "HostUnknown - 550" error messages.
Verifying the HOSTS File
Before starting the Internet Agent, either verify the IP address and the server name where the program is running in your HOSTS file, if you use one, or set the /hn switch in the GWIA.CFG file. The HOSTS file is automatically installed in the SYS:\ETC directory when you install TCP/IP. There is also a HOSTS file in the SYS:\ETC\SAMPLES directory that can be copied to the SYS:\ETC directory if needed. However, the IP address and name of the gateway server is not automatically inserted. You must manually add these values to the file. Listed below is a sample HOSTS file. Check the line showing the server name and IP address. In the sample file the IP address is 151.155.111.11 and the server name is yourservername.topeka.company.com.
Sample HOSTS file
# SYS:ETC\HOSTS # Mappings of host names and host aliases to IP address. 127.0.0.1 loopback lb localhost # normal loopback address 151.155.111.11 yourservername.topeka.company.com # Your IP address and server
Installing GroupWise Internet Agent 95
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
When the Internet Agent starts, it instructs TCP/IP to get the host name or the foreign name. If the instruction fails, the program will not start. The instruction to get the host name will fail if there is no HOSTS file, if the HOSTS file does not have the correct IP address and name of the Internet Agent machine, or if the /hn switch is not set.
Starting the Internet Agent NLM
When the Internet Agent was installed, the GWIA.NCF startup file was copied into the SYS:\SYSTEM directory. This file is used to load the Internet Agent. If you reference this file in your AUTOEXEC.NCF file, the Internet Agent will load when you start the file server. The GroupWise Internet Agent automatically uses a startup file named GWIA.CFG when it starts. You can specify a different startup file. This file is used to properly configure the Internet Agent and the program with the startup switches. The values of the two required switches, /home and /dhome, are automatically inserted during installation. The remaining switches are disabled until you are ready to use them to customize the Internet Agent. This file resides in the Internet Agent directory \WPGATE\GWIA. To start the Internet Agent NLM: 1 At the system console, type gwia to run the GWIA.NCF file. This file loads the Internet Agent. After you have started the Internet Agent, verify that the program is running. You can monitor the program from the operation screen. Select F10-Options followed by F9-Stats. If you see an error message in the Statistics window, the program has not loaded properly.
96 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
3 Installing GroupWise WebAccess
GroupWise® WebAccess enables access to GroupWise mailboxes through Web browsers on computers or WAP-enabled wireless devices (telephones, PDAs, and so forth). GroupWise WebAccess provides most of the functionality available in the GroupWise client for Windows*. For information about tasks that can be completed using GroupWise WebAccess, see the GroupWise WebAccess Help after installation. GroupWise WebAccess also includes GroupWise WebPublisher, an optional extension to GroupWise WebAccess. GroupWise WebPublisher lets GroupWise users publish documents from a GroupWise library to the Web. Web users can then view the published documents in their Web browsers.
Login GroupWise Mailbox WebAccess
Browser GroupWise Library No Login WebPublisher Documents Internet Intranet
As shown above, GroupWise WebAccess requires users to have a mailbox in a GroupWise post office. GroupWise WebPublisher, on the other hand, is designed to provide public access to GroupWise library documents; users do not require a mailbox. To plan and set up GroupWise WebAccess (including GroupWise WebPublisher if desired), complete the tasks in the following sections: ! “Planning GroupWise WebAccess” on page 98 ! “Setting Up GroupWise WebAccess” on page 113
Installing GroupWise WebAccess 97
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Once you’ve finished setting up GroupWise WebAccess, you should look at “Other Things You Can Do” on page 119 for additional information you may want to be aware of as you configure, maintain, and expand GroupWise WebAccess.
Planning GroupWise WebAccess
The “GroupWise WebAccess Installation Worksheet” on page 120 includes all information you will be prompted to supply during installation. Use the background and planning information in the following sections to fill out the worksheet. ! “GroupWise WebAccess Component Overview” on page 98 ! “Deciding Where to Install the GroupWise WebAccess Components” on page 99 ! “Determining the WebAccess Agent’s Configuration” on page 105 ! “Determining the WebAccess and WebPublisher Applications’ Configuration” on page 110
GroupWise WebAccess Component Overview
GroupWise WebAccess consists of three components: the WebAccess Application, the WebPublisher Application, and the WebAccess Agent.
WebAccess Application Post Office Web Web WebAccess Browser Server Agent WebPublisher Library Application
WebAccess Application: The WebAccess Application, which resides on the Web server, provides the WebAccess user interface. As users perform actions in WebAccess, the WebAccess Application passes information between the Web browser and the WebAccess Agent. WebPublisher Application: The WebPublisher Application, which resides on the Web server, provides the WebPublisher user interface. As users perform actions in WebPublisher, the WebPublisher Application passes information between the Web browser and the WebAccess Agent.
98 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WebAccess Agent: The WebAccess Agent receives user requests from the WebAccess Application and WebPublisher Application, accesses post offices and libraries to process the requests, and then passes information back to the applications. The WebAccess Agent is required for both WebAccess and WebPublisher. The WebAccess Application must be installed to use WebAccess. Likewise, the WebPublisher Application must be installed to use WebPublisher.
WORKSHEET
Under Item 1: Components to Install, select which components you want to install.
Deciding Where to Install the GroupWise WebAccess Components
As you decide where to install the WebAccess Agent, WebAccess Application, and WebPublisher Application, you should consider the following: ! “One Machine vs. Two Machines” on page 99 ! “Security Requirements” on page 100 ! “NetWare Cluster Services” on page 101 ! “System Requirements” on page 102
One Machine vs. Two Machines The WebAccess Application and WebPublisher Application must be installed to a Web server. If desired, you can install the WebAccess Agent on the same machine as the Web server.
Web Web Browser Server WebAccess Application WebAccess Post Office Agent WebPublisher Library Workstation NetWare or Application GroupWise Windows System NT/2000
You can also install the WebAccess Agent on a different machine, as shown below. If you plan to use a UNIX* Solaris* Web server, you will have to install
Installing GroupWise WebAccess 99
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
the WebAccess Agent on a different machine that the Web server. The WebAccess Agent supports NetWare® and Windows NT*/2000 only.
Web Web Browser Server WebAccess Application WebAccess Post Office Agent WebPublisher Library Workstation NetWare, Application NetWare or GroupWise Windows Windows System NT/2000, or NT/2000 UNIX Solaris
Security, discussed in the next section, may also determine whether you run the WebAccess Agent on the same machine as the Web server.
Security Requirements GroupWise WebAccess 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 WebAccess on a secured intranet), you can install the WebAccess components to any machines that provide access for your users and meet the requirements (see “System Requirements” on page 102). If you plan to use WebAccess to provide users with access to their mailboxes 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 WebAccess: ! Install all WebAccess components inside your firewall and use a proxy service. See “Configuration Using a Proxy Service” on page 100. This is the recommended configuration. ! Install the WebAccess and WebPublisher Applications on a Web server outside your firewall and the WebAccess Agent on a machine inside your firewall. See “Configuration Without a Proxy Service” on page 101.
Configuration Using a Proxy Service If your firewall includes a proxy service, you can install the WebAccess Application and WebPublisher Application to a Web server inside your firewall, and the WebAccess Agent to another machine inside the firewall, as shown in the following illustration.
100 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Firewall Server Web Server Network Server System with Proxy with WebAccess with WebAccess Internet Service and WebPublisher Agent Applications
If desired, the WebAccess Agent can also be installed to the Web server rather than a separate machine, as discussed in “One Machine vs. Two Machines” on page 99.
Configuration Without a Proxy Service If your firewall does not provide a proxy service, you need to install the WebAccess Application and WebPublisher Application to a Web server that is outside the firewall. Because the WebAccess Agent requires direct access (mapped path or UNC path) to a GroupWise domain directory, it needs to be installed to a machine that is located within the firewall.
GroupWise Web Server Firewall Network Server System with WebAccess Server with WebAccess Internet and WebPublisher Agent Applications
The firewall must allow inbound IP packets to be sent from the Web server to the IP address and port number of the WebAccess Agent (for example, 151.155.123.45:7205). In addition, the firewall must allow outbound IP packets to be sent from the WebAccess Agent to the Web server. This requires all high ports (above 1023) to be open to outbound IP packets.
NetWare Cluster Services
NetWare Cluster ServicesTM is a server clustering system that ensures high availability and manageability of critical network resources including volumes (where GroupWise domains and post offices reside) and applications (such as the GroupWise WebAccess Agent). NetWare Cluster Services supports failover, failback, and migration of individually managed cluster resources.
Installing GroupWise WebAccess 101
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The NLMTM WebAccess Agent can be configured to take advantage of the fault tolerant environment provided by NetWare Cluster Services if the following requirements are met: ! The domains and post offices to be serviced by the NLM WebAccess Agent have already been created on shared NSS volumes in the cluster. ! The NLM WebAccess Agent is being installed to a server that is part of the same cluster. When the WebAccess Agent is configured for clustering, its startup file is configured with shared volume names rather than specific server names.
System Requirements Once you’ve selected the machines where you will install the WebAccess components, you need to make sure they meet the requirements listed in the following table.
Item Requirement
WebAccess Agent ! GroupWise 6 system: The WebAccess Agent can only access GroupWise 6 post offices and libraries ! Server: NetWare 5.x, Windows NT 4, or Windows 2000
102 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
WebAccess and One of the following Web servers: WebPublisher Applications ! NetWare Enterprise Web Server running on a NetWare 5.x server with the latest NetWare (Web Server) Support Pack ! Netscape Enterprise Server* 3.6 or higher for Windows NT ! Microsoft* Internet Information Server 4.0 or higher for Windows NT (Windows NT 4.0 must have Service Pack 3 or higher installed) or Microsoft Internet Information Server 5 or higher for Windows 2000 ! Apache Web Server 1.3.3 or higher for UNIX Solaris
Although WebAccess may run on other Web servers, the Installation program does not facilitate installation to Web servers other than those listed. In addition, Novell® Technical ServicesSM will not support installations on other Web servers. If you want to use a different Web server, see the WebAccess Readme file for some general installation instructions and tips.
Installing GroupWise WebAccess 103
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
WebAccess and JVM, version 1.1.7B or higher. Please be aware of WebPublisher Applications the following: ! NetWare servers can run only one JVM. On (Java* Virtual Machine) NetWare, WebAccess requires JVM 1.1.7B dated 01/29/2001 or later. This version is included with WebAccess. During installation, you will be prompted to replace your current version with the WebAccess version; you should do so unless the server’s current version is newer. ! Windows NT/2000 machines can run multiple JVMs at the same time. To ensure compatibility with WebAccess, you should install JVM 1.1.8 or higher. JVM 1.3.0 (Java 2 Runtime Environment, Standard Edition Version 1.3.0) is included with WebAccess. ! A JVM is not included for UNIX Solaris. You will need to separately install JVM 1.1.7B or higher to your UNIX Web server.
WebAccess and JSDK 2.0 and JDK* 1.1.6 compatible. Please be WebPublisher Applications aware of the following: ! Novell’s Java servlet engine, the Novell Servlet (Java Servlet Engine) Gateway, is included with GroupWise WebAccess. We strongly recommend you use this servlet engine when installing on a NetWare or Windows NT/2000 Web server. ! For UNIX Solaris, you will need to separately install a Java servlet engine that meets the requirements. We recommend that you use Apache’s JSERV.
Computer Web Browser ! Windows: Microsoft Internet Explorer 4.0 or higher; Netscape Navigator* 4.0 or higher ! Macintosh*: Microsoft Internet Explorer 4.5 or higher; Netscape Navigator 4.51 or higher ! UNIX: Netscape 4.0 or higher; Microsoft Internet Explorer 4.0 or higher
104 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Requirement
Wireless Device ! Must support the Wireless Access Protocol (WAP) ! Must have a microbrowser that uses Handheld Device Markup Language (HDML) 3.0 or Wireless Markup Language (WML) 1.1
WORKSHEET
Under Item 2: Server Platform and Installation Directory, specify the platform (NetWare or Windows NT/2000) where you will install the WebAccess Agent, then specify the directory where you want to install the WebAccess Agent files. The default NetWare directory is SYS:\SYSTEM. The default Windows NT/2000 directory is C:\WEBACC.
If you are installing the WebAccess Agent on a NetWare server that is using NetWare Cluster Services, under Item 4: Clustering Support, select Yes.
Under Item 13: Web Server Type and Root Directory, select the type of Web server where you will install the WebAccess Application and WebPublisher Application, then specify the Web server’s root directory.
Under Item 16: Novell Root Directory, specify a directory on the Web server where you want to install the configuration files for the WebAccess Application and WebPublisher Application. The default is the NOVELL directory on the root of the volume (either SYS:\NOVELL or C:\NOVELL).
Under Item 17: Java Servlet Engine, select whether you want to use the Novell Servlet Gateway or another Java servlet engine. If you use another Java servlet engine, it must already be installed and you must specify the path to its root directory.
Determining the WebAccess Agent’s Configuration
As you install the WebAccess Agent, you will be prompted to supply the configuration information described in the following sections: ! “Network Address” on page 106 ! “Gateway Directory Location and Name” on page 106 ! “Gateway Object Name” on page 106 ! “Domain and Post Office Access” on page 107
Installing GroupWise WebAccess 105
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! “NT/2000 WebAccess Agent Options” on page 108 ! “Web Console” on page 109 ! “WebPublisher” on page 109
Network Address The WebAccess Agent communicates with the WebAccess Application and WebPublisher Application (on the Web server) through TCP/IP.
WORKSHEET
Under Item 3: Server Address, specify the IP address or DNS host name of the machine where you will install the WebAccess Agent, then specify the port number for the agent to use. The default is 7205.
Gateway Directory Location and Name The WebAccess Agent requires a GroupWise gateway directory in which to store configuration information and work files. The gateway directory must be located under a GroupWise domain directory. The default directory name is WEBAC60A. If you change the name, use a maximum of 8 characters in the new name. Once you specify the domain directory location and a gateway directory name, the Installation program creates the gateway directory under the domain\WPGATE directory (for example, PROVO\WPGATE\WEBAC60A).
WORKSHEET
Under Item 5: Gateway Directory, specify the GroupWise domain directory where you want to create the gateway directory, then give the gateway directory a name.
Gateway Object Name The WebAccess Agent also requires a GroupWise Gateway object in NDS®. This object stores the WebAccess Agent’s information and enables configuration of the agent through ConsoleOneTM. The WebAccess Agent’s object will be created below the Domain object. If you have multiple domains, the Installation program uses the Domain object
106 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
associated with the domain directory where you are creating the WebAccess Agent’s gateway directory.
WORKSHEET
Under Item 6: Gateway Object, specify the name you want to give the WebAccess Agent’s object. The default name is the same as the gateway directory name you chose for Item 5.
Domain and Post Office Access The WebAccess Agent requires access to the domain. It also requires access to each post office where mailboxes or libraries are located that WebAccess or WebPublisher users will access. Domain: The WebAccess Agent needs direct access (UNC path or mapped drive) to the domain directory. Post Offices: The WebAccess Agent needs direct access (UNC path or mapped drive) to the post office directory or client/server access (TCP/IP) to the post office’s POA. By default, the WebAccess Agent will use whatever access mode has been established for the post office (ConsoleOne > Post Office object > GroupWise tab > Post Office Settings page). If you are using the NLM version of the WebAccess Agent, you need to ensure that an NDS user account exists that provides the required access to the domain and post office directories. For direct access to the domain directory or a post office directory, the WebAccess Agent needs Read, Write, Create, Erase, Modify, and File Scan rights. If you are using the Windows NT/2000 version of the WebAccess Agent, you need to ensure that: ! A Windows user account exists on the NT/2000 machine for the agent to log in and that the user account provides the Full Control access to domain and post office directories. ! If the domain or any post office directories (directly accessed by the WebAccess Agent) are on Windows NT/2000 servers, the Windows user account provides Full Control access to those directories. ! If the domain directory or any post office directories (directly accessed by the WebAccess Agent) are on NetWare servers, an NDS user account exists for the WebAccess Agent that has an identical username and password as the agent’s Windows user account. The NDS account must provide Read, Write, Create, Erase, Modify, and File Scan rights to the directories.
Installing GroupWise WebAccess 107
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! If the WebAccess Agent does require an NDS user account, the context of the account is defined in the bindery context of all NetWare servers that will be accessed.
WORKSHEET
Under Item 7: NDS Authentication, specify the NDS username and password you want the WebAccess Agent to use to access the domain directory and post office directories. This applies to the NLM WebAccess Agent only.
If you are using the NT/2000 WebAccess Agent, ensure that the appropriate Windows and NDS user accounts exist.
NT/2000 WebAccess Agent Options This section applies to the Windows NT/2000 version of the WebAccess Agent only. The WebAccess Agent can be configured to support SNMP. This enables the WebAccess Agent to be monitored and managed through an SNMP management program.
WORKSHEET
If you want the WebAccess Agent to support SNMP, under Item 8: Execution Options, select the Install and Configure SNMP for WebAccess Agent option.
The WebAccess Agent can also run as a Windows service rather than a normal Windows application. To do so, the WebAccess Agent service requires a user account. The requirements for the Windows service user account are the same as those listed for the NT/2000 WebAccess Agent in “Domain and Post Office Access” on page 107.
WORKSHEET
Under Item 8: Execution Options, select Run WebAccess Agent as a Windows Service.
Under Item 9: Windows Service User, enter the username and password for the service’s user account.
108 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Web Console The WebAccess Agent console enables you to monitor the WebAccess Agent on the machine where it is running. If you want, you can enable the WebAccess Agent’s Web console. The Web console lets you view the WebAccess Agent’s statistical and diagnostic information through a Web browser, which is useful if want to see the WebAccess Agent’s activity without physically visiting the agent’s machine. If you want to restrict access to the Web console, you can assign a username and password. This can be any username and password you want. However, because the username and password are passed through an unsecure connection between the Web browser and WebAccess Agent, we recommend that you do not use an existing NDS or Windows username and password. You access the Web console by entering the WebAccess Agent’s network address and port number in a Web browser (for example, http:// 111.222.11.22:7205).
WORKSHEET
Under Item 10: Web Console, select Yes if you want to enable the Web console. If you want to restrict access to the Web console, enter a username and password.
WebPublisher You can choose whether or not you want the WebAccess Agent to support GroupWise WebPublisher. If you enable WebPublisher support, you need to specify a GroupWise account (mailbox ID and password). The GroupWise account serves two purposes: ! GroupWise users publish documents to WebPublisher users by sharing the documents with the GroupWise account. ! When Web users access WebPublisher, the WebAccess Agent logs in to this GroupWise account. This lets the WebAccess Agent know which documents have been shared with WebPublisher users. It can then retrieve these documents (and only these documents) for the WebPublisher users. We recommend that you create a new GroupWise account specifically for GroupWise WebPublisher. If you’ve already created an NDS account for the WebAccess Agent to use when accessing domain or post office directories (see “Domain and Post Office Access” on page 107), you might want to create the GroupWise account under that NDS user account.
Installing GroupWise WebAccess 109
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 11: WebPublisher Support, select Yes if you want to enable the WebAccess Agent to support WebPublisher, then enter the Mailbox ID and password for the GroupWise account you want the WebAccess Agent to use.
If you enable GroupWise WebPublisher support, you need to select the libraries that you want to make public. The WebAccess Agent, acting on behalf of WebPublisher users, will only access documents in public libraries. Making a library public does not automatically give WebPublisher users access to all documents in the library. For WebPublisher users to have access to a document in a public library, the document’s owner must have shared the document with the WebPublisher user account.
WORKSHEET
Under Item 12: Libraries, list the libraries from which documents can be shared. The Installation program will list all libraries in your GroupWise system. If you want, you can wait until then to select libraries.
NOTE: When a WebPublisher user requests a library document, the WebAccess Agent renders the document from its native format to HTML format. It also caches the HTML document to a directory on the agent’s local drive. This enables the WebAccess Agent to use the cached document for future requests. For NetWare, the cache directory is the SYS:\SYSTEM\CACHE directory. For Windows NT/2000, the cache directory is the C:\GROUPWISE\CACHE directory. For information about changing the cache directory’s location, size, and refresh interval, see "WebAccess" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Determining the WebAccess and WebPublisher Applications’ Configuration
As you install the WebAccess Application and/or the WebPublisher Application to a Web server, you will be prompted to supply the configuration information described in the following sections: ! “Network Address” on page 111 ! “Web Server Default Page” on page 111 ! “Default Language” on page 112 ! “NDS Objects and Configuration Files” on page 112
110 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
NOTE: You should have already selected the Web server where you will install the WebAccess Application and WebPublisher Application. If you have not, see “Deciding Where to Install the GroupWise WebAccess Components” on page 99.
Network Address Web browsers communicate with the WebAccess Application and WebPublisher Application (on the Web server) through TCP/IP.
WORKSHEET
Under Item 14: Web Server Address, specify the IP address or DNS host name of the Web server where you will install the WebAccess Application and/or WebPublisher Application, then select whether or not the Web server uses SSL (Secure Socket Layer).
Web Server Default Page The Installation program copies the Novell Web Services page to the Web Server's root directory. This page includes links for GroupWise WebAccess and GroupWise WebPublisher (provided you are installing both). You can have this page replace the Web Server's current default page, or you can retain your current page and create a link to the Novell Web Services page. If you use the Novell Web Services page as the default, the Installation program renames the current default page to filename.001 (for example, DEFAULT.001, INDEX.001, or index.001). You should change the default Web server page only if the Web server is used solely for Novell products. As you install additional Novell products, such as GroupWise Monitor, the Novell Web Services page is updated to allow access to each product. If you retain your current default page, the Install program copies the Novell Web Services page (NOVELL.HTM) to the Web Server's root directory. You will need to add a link from your default page to the Novell Web Services page.
WORKSHEET
Under Item 15: Web Server Default Page, select whether or not you want to use the Novell Web Services page as the Web server’s default page.
Installing GroupWise WebAccess 111
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Default Language If your GroupWise 6 CD includes more than one language, the Installation program installs all languages. In this case, you need to specify which language should be used when displaying the Novell Web Services page. Once users access the Novell Web Services page, they can use the default language for WebAccess or WebPublisher, or they can select another available language.
WORKSHEET
Under Item 18: Default Language, specify the language for the Novell Web Services page.
NDS Objects and Configuration Files WebAccess Application and WebPublisher Application configuration information is stored in two places: 1) NDS objects and 2) configuration files (WEBACC.CFG and WEBPUB.CFG) located in the Novell root directory (worksheet item 16) on the Web server. The WebAccess Application object and WebPublisher Application object allow you to easily modify configuration information in ConsoleOne. The NDS information is the master information; any changes made to the objects in NDS are also written to the configuration files. In some installation scenarios, such as installing to a Web server outside a firewall or installing to a UNIX Web server, you may not have access to NDS, which means the Installation program will not be able to create the objects. It will, however, still create the configuration files on the Web server. In this case, to change the application’s configuration, you will need to manually modify the WEBACC.CFG and WEBPUB.CFG files. You need to select the NDS container where you want the objects created. They will all be created in the same container. The default container is the Domain object.
NOTE: Each application also has several providers associated with it. For example, the WebAccess Application has a GroupWise Provider and an LDAP Provider. The GroupWise Provider is the component that actually communicates with the WebAccess Agent to request information for users. The LDAP Provider communicates with LDAP servers to enable users to search LDAP address books. Provider objects are created in the same location as the application objects.
112 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 19: NDS Object Configuration, specify the tree where you want the objects created, then specify the context. If you will be installing from a location where you don’t have access to NDS, you can skip this item.
Setting Up GroupWise WebAccess
Complete the following tasks to set up GroupWise WebAccess and WebPublisher: ! “Establishing File System Rights and NDS Access Rights” on page 113 ! “Shutting Down the Web Server and GroupWise Components” on page 114 ! “Installing GroupWise WebAccess” on page 115 ! “Starting GroupWise WebAccess” on page 117 ! “Testing GroupWise WebAccess” on page 118 ! “Testing GroupWise WebPublisher” on page 119
Establishing File System Rights and NDS Access Rights
For the Installation program to be able to install files to the appropriate locations and create NDS objects, you need to make sure you are logged in through a user account that has the appropriate file system rights and NDS access rights.
File System Rights You need Read, Write, Create, Erase, Modify, and File Scan rights (or equivalent rights) to the following locations: ! The GroupWise domain directory where the WebAccess Agent’s gateway directory will be created. See Item 5: Gateway Directory in the “GroupWise WebAccess Installation Worksheet” on page 120. ! The NetWare server or Windows NT/2000 server (or workstation) where you will install the WebAccess Agent. If you are installing the WebAccess Agent to a Windows NT/2000 machine, you must run the Installation program on that machine. See Item 2: Server Platform and Installation Directory in the “GroupWise WebAccess Installation Worksheet” on page 120.
Installing GroupWise WebAccess 113
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! The NetWare server or Windows NT/2000 server where your Web server is running. If your Web server is on a UNIX machine, the installation program copies tar files to a location you specify; this can be the UNIX machine if you have access to it from the Windows workstation where you are performing the installation, or another location from which you can then copy the tar files to the UNIX machine. See Item 13: Web Server Type and Root Directory in the “GroupWise WebAccess Installation Worksheet” on page 120.
NDS Access Rights When installing the WebAccess Agent, the Installation program creates the WebAccess Agent object below the GroupWise Domain object in NDS. For it to do so, you must have Admin rights (or Admin equivalent rights) to the NDS container where the GroupWise Domain object resides. When installing the WebAccess Application and WebPublisher Application, the Installation program creates the WebAccess Application and WebPublisher Application objects (and their associated provider objects) in a container you specify (worksheet item 19). Make sure you have Admin rights (or Admin equivalent rights) to the container.
Shutting Down the Web Server and GroupWise Components When installing the WebAccess Agent to a machine where the GroupWise MTA or POA is running, you need to shut down those agents before installing the WebAccess Agent’s files. This allows the Installation program to properly install the agents’ common files (also referred to as the agent engine files). The Installation program will attempt to shut down the MTA or POA on a NetWare server. We recommend, however, that you shut down these agents yourself before starting the installation. When installing the WebAccess Application and WebPublisher Application to a NetWare or Windows NT/2000 Web server, the Installation program will attempt to shut down the Web server and JVM. We recommend, however, that you shut down the Web server and JVM yourself before starting the installation.
114 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Installing GroupWise WebAccess
As you select the workstation from where you will install GroupWise WebAccess, consider the following situations: ! Situation 1: If you will install the WebAccess Agent, WebAccess Application, and WebPublisher Application to NetWare servers, you can run the Installation program on any Windows 95/98/NT/2000 workstation. ! Situation 2: If you will install the WebAccess Agent to a Windows NT/ 2000 machine, you need to run the Installation program on that machine. ! Situation 3: If, while installing the WebAccess Application and WebPublisher Application to a Windows NT/2000 Web server, you will also install the Novell Servlet Gateway, you must run the Installation program on that Web server. ! Situation 4: In the case where both situations 2 and 3 exist, you will need to run the Installation program twice, once to install the WebAccess Agent on its NT/2000 machine and once to install the WebAccess and WebPublisher Applications (along with the Novell Servlet Gateway) on its NT/2000 Web server. To install GroupWise WebAccess: 1 Insert the GroupWise 6 CD into the CD drive to start the Installation program > click Install Products > GroupWise WebAccess > Install GroupWise WebAccess. If the installation program does not start automatically, run SETUP.EXE from the root of the CD. or If you’ve already copied the GroupWise WebAccess software to a software distribution directory, run SETUP.EXE from the INTERNET\WEBACCES directory. 2 Follow the installation prompts, using the information you recorded on the “GroupWise WebAccess Installation Worksheet” on page 120. 3 After installation is complete, you may need to do the following: ! If you kept your Web server’s default home page file, create a link from your home page to the Novell Web Services page (NOVELL.HTM file) in the document root directory. ! If you chose to use an existing Java servlet engine rather than installing the Novell Servlet Gateway, modify the Java servlet engine’s servlet properties files to include the settings shown in the
Installing GroupWise WebAccess 115
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
sample WebAccess SERVLET.PROPERTIES file. This sample file is located in the INTERNET\WEBACCES\OTHER directory on the CD. ! If you chose to use an existing JVM on Windows NT/2000 rather than update to the one included with GroupWise WebAccess, edit the SERVLETGATEWAY.PROPERTIES file and change the java.base setting to point to the existing JVM (for example, C:\JDK1.1.8). The SERVLETGATEWAY.PROPERTIES file is located the NOVELL\JAVA\SERVLETS directory. ! If you are installing to the Apache Web Server for UNIX Solaris, continue with “Completing the Installation on a UNIX Apache Web Server” on page 116.
Completing the Installation on a UNIX Apache Web Server The Installation program copies the following files to the location you specified: webaccess.tar, webaccessdocs.tar, webaccessjars.tar, webaccessservlets.tar, index.html, servlets.properties, and commgr.cfg. To complete the installation and configuration process: 1 Using the tar -xvf command), extract the webaccess.tar file to the UNIX server’s root directory/ 2 Using the tar -xvf command, extract the webaccessdocs.tar file to the Web server’s document root directory. 3 Using the tar -xvf command, extract the webaccessservlets.tar file to the servlet root directory. 4 Using the tar -xvf command, extract the webaccessjars.tar file to the Web server's jar file directory. 5 Configure a new servlet zone. For information, see the Apache Software Foundation’s JServ Project site (http://java.apache.org/jserv). 6 Modify your Java servlet engine’s servlets properties file to include the following: ! The settings described in the WebAccess servlets.properties file. ! A wrapper.classpath entry for the new servlet zone. 7 Modify the webacc.cfg and webpub.cfg files, located in the Novell/ WebAccess and Novell/WebPublisher directories at the root of the UNIX server, to change the Templates.path setting to point to the templates path for the new servlet zone.
116 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 In the webacc.cfg and webpub.cfg files, verify that the paths for the following settings are correct from the perspective of the Web server: ! File.Upload.path ! Log.path ! Security.Timeout.path ! Provider.GWAP.Config.file ! Provider.LDAP.Config.file 9 Copy the index.html file to the Web server’s document root directory. You can replace your Web server’s current default home page with this file, or you can rename the file and link to it from your current default home page. 10 Copy the commgr.cfg file to the UNIX server’s Novell/WebAccess directory. If you installed GroupWise WebPublisher, you also need to copy the file to the Novell/WebPublisher directory.
Starting GroupWise WebAccess If you did not have the Installation program start the WebAccess components, complete the following steps: 1 Start the Web server and make sure the JVM and Java servlet engine are running. 2 To start the WebAccess Agent on a NetWare server, enter STRTWEB.NCF at the system console. or To start the WebAccess Agent as an application on a Windows NT/2000 machine, click the Start menu > Programs > GroupWise WebAccess Startup > STRTWEB.BAT. or To start the WebAccess Agent as a service on a Windows NT/2000 machine, open the Services dialog box (from the Control Panel) > open the WebAccess service > click Start. 3 If you shut down the MTA or POA to install the WebAccess Agent, make sure you start the agent again.
Installing GroupWise WebAccess 117
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Testing GroupWise WebAccess
To test GroupWise WebAccess, complete the steps in the following sections: ! “Testing WebAccess on a Computer” on page 118 ! “Testing WebAccess on a Wireless Device” on page 118
Testing WebAccess on a Computer 1 In a Web browser, enter the IP address or host name of the Web server. 2 If the Novell Web Services page is not the Web server’s default page, click the link you created to the page. 3 Select a GroupWise WebAccess language > click Go to display the Login page. 4 Type your GroupWise user ID or GroupWise full name in the Name box and your GroupWise mailbox password in the Password box. 5 Click Login to display the GroupWise WebAccess main window. 6 Click Help for more information about using GroupWise WebAccess.
Testing WebAccess on a Wireless Device 1 Enter the following URL: http://web_server_address/servlet/webacc where web_server_address is the IP address or DNS hostname of your Web server. If the Web server uses SSL, you’ll need to use https rather than http.
HINT: Follow the instructions in your wireless device’s documentation to add this URL to your Favorites or Bookmarks so you don’t have to type the URL every time you log in. 2 Enter your GroupWise user ID and GroupWise mailbox ID. 3 For more information about using GroupWise WebAccess on a wireless telephone, see the GroupWise 6 Wireless User’s Guide at the Novell Documentation Web site (http://www.novell.com/documentation).
118 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Testing GroupWise WebPublisher
GroupWise WebPublisher only supports access through a Web browser on a computer. Wireless devices are not supported. 1 In a Web browser, enter the IP address or host name of the Web server. 2 If the Novell Web Services page is not the Web server’s default page, click the link you created to the page. 3 Select a GroupWise WebPublisher language > click Go to display GroupWise WebPublisher. 4 To search for a specific document, enter the search words > click Search. or To browse the documents in a library, click Document Browse > click the library you want to browse. When you browse a library, the first 10 documents are listed. You can list additional documents if desired. 5 Click Help for more information about using GroupWise WebPublisher.
Other Things You Can Do
The GroupWise 6 Administration guide, located at the Novell Documentation Web site (http://www.novell.com/documentation), provides information to help you further configure and maintain GroupWise WebAccess, including how to: ! Scale GroupWise WebAccess to meet the needs of your users and environment. ! Control users’ access to GroupWise WebAccess. ! Modify the WebAccess Agent’s configuration information, including the number of threads allocated for request processing. ! Control logging for the WebAccess Agent, WebAccess Application, and WebPublisher Application. ! Change the WebAccess Agent’s links to post offices. ! Modify configuration information for the WebAccess Application and WebPublisher Application.
Installing GroupWise WebAccess 119
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise WebAccess Installation Worksheet
The following table lists the information you will be prompted to provide as you complete the WebAccess installation. The table is divided into three sections: ! “WebAccess Agent and WebAccess/WebPublisher Applications” on page 120 lists information you need to provide when you are installing the WebAccess Agent or the WebAccess/WebPublisher Applications. ! “WebAccess Agent” on page 121 lists information you need to provide when installing the WebAccess Agent. ! “WebAccess/WebPublisher Applications” on page 123 lists information you need to provide when installing the WebAccess Application and/or the WebPublisher Application.
WebAccess Agent and WebAccess/WebPublisher Applications
Item Explanation
1) Components to Install Select the components you want to install.
! WebAccess Agent For details, see “GroupWise WebAccess Component Overview” on page 98. ! WebAccess Application ! WebPublisher Application
120 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WebAccess Agent
Item Explanation
2) Server Platform and Specify the type of network server (NetWare or Windows NT/2000) where you Installation Directory will install the WebAccess Agent.
Platform: Specify the directory where you will install the WebAccess Agent. The default NetWare directory is SYS:SYSTEM. The default Windows NT/2000 directory ! NetWare is C:\WEBACC. The directory path you specify must be from the perspective ! Windows NT/2000 of the installation workstation.
Installation directory: For details, see “Deciding Where to Install the GroupWise WebAccess Components” on page 99.
3) Server Address Specify the IP address or DNS hostname of the network server where you will install the WebAccess Agent. The WebAccess Installation program will ! IP address: attempt to discover this information from the server, but you should be ! DNS hostname: prepared to supply it in case the attempt fails.
! Port number: 7205 If port 7205 is already in use, specify a different port. (default) For details, see “Network Address” on page 106.
4) Clustering Support This item applies to the NLM WebAccess Agent only.
Enable? Select Yes if you want to configure the WebAccess Agent for clustering.
! Yes For details, see “NetWare Cluster Services” on page 101. ! No
5) Gateway Directory Specify the path to the domain directory you want to associate with the WebAccess Agent. The WebAccess Agent stores configuration information ! Domain directory and work files in the directory. path: ! Gateway directory Specify the name of the gateway directory you want created for the name: WEBAC60A WebAccess Agent. This directory is created in the domain\WPGATE (default) directory. For details, see “Gateway Directory Location and Name” on page 106.
6) Gateway Object Specify a name for the GroupWise Gateway object that will be created in NDS to represent the WebAccess Agent. The default name is the same as the Name: WEBAC60A gateway directory. (default) For details, see “Gateway Object Name” on page 106.
Installing GroupWise WebAccess 121
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
7) NDS Authentication This item applies only if you are installing the NLM version of the WebAccess Agent. NDS username: Specify an NDS username and password that will provide the WebAccess Agent with file system access to the servers where the domain and post office directories reside. Password: For details, see “Domain and Post Office Access” on page 107.
8) Execution Options This item applies only if you are installing the NT/2000 version of the WebAccess Agent. ! Install and Configure SNMP for WebAccess If you want to enable the WebAccess Agent to be managed through an SNMP Agent management program, select the Install and Configure SNMP for WebAccess ! Run WebAccess option. Agent as a Windows If you want to run the WebAccess Agent as a Windows service, select the Run Service WebAccess Agent as a Windows Service option, then choose whether you Service Startup: want to manually start the service each time or have it start automatically Automatic/Manual when the machine starts. For details, see “NT/2000 WebAccess Agent Options” on page 108.
9) Windows Service User This item applies only if you are installing the NT/2000 version of the WebAccess Agent and will be running it as a Windows service rather than a ! Username: normal Windows application. ! Password: Enter the username and password for a user account that provides the service with access to the domain and post office directories.
For details, see “NT/2000 WebAccess Agent Options” on page 108.
10) Web Console Specify whether or not you want to enable the WebAccess Agent’s Web console. The Web console allows you to monitor the operation of the agent Enable? through a Web browser. ! Yes If you choose to enable the Web console, specify a WebAccess Agent Username: username and password to use when logging in to the agent. Password: For details, see “Web Console” on page 109. ! No
122 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
11) WebPublisher Specify whether or not you want to enable the WebAccess Agent to support Support WebPublisher. If you enable WebPublisher support, you need to specify a GroupWise account (mailbox ID and password). Enable: Yes/No For details, see “WebPublisher” on page 109. Mailbox ID:
Password:
12) Libraries List the libraries from which you want to enable GroupWise users to share documents with WebPublisher users.
For details, see “WebPublisher” on page 109.
WebAccess/WebPublisher Applications
Item Explanation
13) Web Server Type and Select the type of Web server where you will install the WebAccess Root Directory Application and/or the WebPublisher Application.
Web server type: Specify the path to the Web server’s root directory. The path must be from the perspective of the installation workstation. ! Netscape Enterprise Server for NetWare For details, see “Deciding Where to Install the GroupWise WebAccess ! Netscape Components” on page 99. FastTrack\Enterprise Server for Windows NT ! Microsoft Internet Information Server for Windows NT ! Apache Web Server for UNIX Solaris
Web server root directory:
Installing GroupWise WebAccess 123
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
14) Web Server Address Specify the IP address or DNS hostname of the Web server where you will install the WebAccess Application and/or the WebPublisher Application. The ! IP address: WebAccess Installation program will attempt to discover this information from ! DNS hostname: the server, but you should be prepared to supply it in case the attempt fails. ! Port number: 443 Select Yes if the Web server uses the Secure Socket Layer protocol, or select (SSL default) or 80 No if it does not. The default port number is determined by whether or not SSL (non-SSL default) is running on the Web server.
! SSL: Yes/No For details, see “Network Address” on page 111.
15) Web Server Default Select whether you want to retain your Web server’s current default page or Page replace it with the Novell Web Services page.
! Current default page For details, see “Web Server Default Page” on page 111. ! Novell Web Services page
16) Novell Root Directory Specify a directory on the Web server where you want to install the configuration files for the WebAccess Application and/or WebPublisher Application. The default is the NOVELL directory on the root of the server volume.
For details, see “Deciding Where to Install the GroupWise WebAccess Components” on page 99.
17) Java Servlet Engine Specify whether you want to use the Novell Servlet Gateway or another Java servlet engine that is already installed on your Web server. If you use a Java ! Use Novell Servlet servlet engine other than the Novell Servlet Gateway, you need to specify the Gateway path to the Java servlet engine’s root directory. ! Use other Java servlet engine For details, see “Deciding Where to Install the GroupWise WebAccess Components” on page 99. Path:
18) Default Language: Specify the language for the initial Novell Web Services page.
For details, see “Default Language” on page 112.
19) NDS Object Specify the tree where you are installing WebAccess. Configuration Specify the context where the Installation program should create the ! Tree: WebAccess Application and/or WebPublisher Application objects. The default ! Context: context is below the Domain object. For details, see “NDS Objects and Configuration Files” on page 112.
124 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Installing GroupWise Monitor
GroupWise® Monitor is a monitoring and management tool that allows you to monitor GroupWise agents and gateways 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. The topics below help you plan and set up GroupWise Monitor: ! “Planning GroupWise Monitor” on page 125 ! “Setting Up GroupWise Monitor” on page 130 ! “GroupWise Monitor Worksheet” on page 134
Planning GroupWise Monitor
Before installing GroupWise Monitor, you should complete the planning tasks listed below. The planning tasks provide concepts and information you will need as you install and set up GroupWise Monitor. You can use the “GroupWise Monitor Worksheet” on page 134 to record your installation and setup information. ! “GroupWise Monitor Overview” on page 126 ! “Deciding Where to Install GroupWise Monitor” on page 127 ! “Specifying Network Addresses” on page 128 ! “Configuring GroupWise Monitor” on page 129 ! “Locating Agents to Monitor” on page 129 ! “Selecting the Web Server’s Default Web Page” on page 130 ! “Selecting the Default Language” on page 130
Installing GroupWise Monitor 125
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Monitor Overview
GroupWise Monitor consists of two modules: Monitor Agent: The Monitor Agent continuously polls other GroupWise agents (POA, MTA, Internet Agent, WebAccess Agent, and gateways), gathers status information from them, and displays the status information at the Monitor Agent console. The Monitor Agent also services requests for agent status information from the Monitor Application. Monitor Application: The Monitor Application extends the capability of your Web server so that agent status information can be displayed in the Monitor Web console in your Web browser. The Monitor Agent and Monitor Application can both run on Windows* NT* or Windows 2000, as illustrated below:
Monitor POA App. Web Web Monitor MTA Browser Server Agent Other
Workstation Windows GroupWise NT/2000 System
The Monitor Agent and the Monitor Application can also run on different machines. The Monitor Agent can run on Windows NT/2000 with full functionality or on Windows 95/98 with slightly limited functionality. In addition to running on Windows NT/2000, the Monitor Application can also run on NetWare® or UNIX* Solaris* in conjunction with a Web server running on one of those platforms, as illustrated below:
Monitor POA App. Web Web Monitor MTA Browser Server Agent Other
Workstation NetWare Windows GroupWise or UNIX NT/2000 System 95/98
126 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Deciding Where to Install GroupWise Monitor
Install GroupWise Monitor in an environment where the following requirements are met:
Requirement Description
Platform The GroupWise Monitor Agent, which provides the Monitor Agent console, runs on Windows NT 4 and Windows 2000 with full functionality.
The GroupWise Monitor Agent also runs on Windows 95/98 but cannot monitor agents by way of SNMP. This means that, on Windows 95/98, the Monitor Agent cannot monitor GroupWise agents that are not enabled for HTTP, such as agents dated earlier than the GroupWise 5.5 Enhancement Pack or older gateways such as Async and Pager.
Web Server The GroupWise Monitor Application, which enables the Monitor Web console, requires one of the following Web servers: ! Netscape* Enterprise Server for NetWare ! Netscape FastTrack/Enterprise Server for Windows NT ! Microsoft* Internet Information Server (IIS) 4.0 or higher for Windows NT Server ! Apache Web server for Sun* Solaris
Java Your Web server must have a Java* servlet engine installed and running to support the Monitor Application. Preferably, you should use the Novell® Servlet Gateway provided with GroupWise Monitor.
If you choose to use another Java servlet engine, it must meet the following requirements: ! Compatible with Java Servlet Development Kit (JSDK) 2.0 ! Compatible with Java Development Kit (JDK*) 1.1.6 or above
Installing GroupWise Monitor 127
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 1: Modules to Install, select whether you want to install the Monitor Agent, the Monitor Application, or both. Both modules are required if you want to use the Monitor Web console, but you can install one module at a time if necessary. For example, you may want to install the Monitor Application on NetWare for use with a NetWare Web server, or on UNIX for use with a UNIX Web server, but you must always install the Monitor Agent on Windows.
Under Item 2: Monitor Agent Installation Path, specify the directory on the Windows machine where you want to install the Monitor Agent software. The default is C:\GWMON.
Under Item 6: Web Server, select the Web server you want to use with Monitor.
Under Item 7: Web Server Path, specify the directory path to the Web server root directory. The images used to produce the Monitor Web console interface and the Monitor Web console help files will be installed in the DOCS\COM\NOVELL\GWMONITOR subdirectory beneath the directory you specify.
Under Item 11: Java Servlet Engine, mark whether or not you want to use the Novell Servlet Gateway. If you do, it will be installed in SYS:\JAVA on NetWare or in C:\NOVELL\JAVA on Windows NT/2000. If you choose not to use the Novell Servlet Gateway, specify the directory path to your preferred Java servlet engine.
Under Item 12: Novell Servlet Gateway Authentication, if you are using the Novell Servlet Gateway, specify a unique user name and password to restrict access to the Novell Servlet Gateway. Do not use an NDS user name or password.
Specifying Network Addresses
The Monitor Agent and your Web server communicate by way of TCP/IP.
WORKSHEET
Under Item 3: Monitor Agent Network Address, record the IP address or the host name of the Windows machine where you will install the Monitor Agent software. Use the default port number of 8200 unless that number is already in use on that machine.
Under Item 8: Web Server Network Address, record the IP address or the host name of the machine where your Web server runs. Also record the port number the Web server listens on. If the Web server uses SSL, the default port number is 443. If it does not use SSL, the default port number is 80.
128 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Configuring GroupWise Monitor
Monitor configuration information is stored in two places: in a configuration file (GWMONITOR.CFG) and in NDS®. You can easily modify the configuration information in ConsoleOneTM by editing the properties of the GroupWiseMonitor object. On the other hand, the configuration file is required if you need to install the Monitor Application to a Web server that is outside your firewall, where access to NDS is not available.
WORKSHEET
Under Item 10: Monitor Configuration File Path, specify the directory on the Web server where you want to create the Monitor configuration file. The default is C:\NOVELL. The Monitor configuration file will be installed to the GWMONITOR subdirectory of the directory you specify.
Under Item 14: Monitor Object Configuration, specify the tree and context where you want the Installation program to create the GroupWiseMonitor object and the accompanying GroupWiseMonitorProvider object.
NDS is considered the master location for the configuration information. Any changes made directly to the configuration file will be overwritten the next time the information in NDS is modified and saved. The default configuration information is sufficient for an initial Monitor installation. For more information about configuring Monitor, see "Monitor" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Locating Agents to Monitor
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.
WORKSHEET
Under Item 4: Domain Directory Path, specify the directory path to a domain where a GroupWise 6 MTA is running.
Installing GroupWise Monitor 129
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Selecting the Web Server’s Default Web Page
The main Novell Web Services page (NOVELL.HTM) will be installed to the Web server's root directory. You can have this file replace the Web server's current default Web page, or you can retain the current default Web page. If you use the Novell Web Services page as the default Web server page, the Web server’s current default page remains in its original location but is renamed to filename.001 (for example, DEFAULT.001 or INDEX.001). You should change the default Web server page only if the machine and its Web server are used solely for Novell products. As you install additional Novell products, the Novell page is updated to allow access to each one.
WORKSHEET
Under Item 9: Default Web Page, specify whether you want to use the Novell Web Services page or retain the Web server’s current default page.
Selecting the Default Language GroupWise Monitor is automatically installed in all available languages. You can select a default language for the Monitor Agent console interface; if necessary, you can select a different default language for the Monitor Web console interface and default Web server page.
WORKSHEET
Under Item 5: Default Monitor Agent Console Language, specify a default language.
Under Item 13: Default Monitor Web Console Language, specify a default language.
Setting Up GroupWise Monitor
Complete the following tasks to set up GroupWise Monitor. These tasks are designed to help you get Monitor up and running as quickly as possible. ! “Preparing to Install GroupWise Monitor” on page 131 ! “Installing GroupWise Monitor” on page 131 ! “Using GroupWise Monitor” on page 132
130 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Preparing to Install GroupWise Monitor
The following prerequisites must be met before you start installing Monitor: ! You must be logged in as an Admin equivalent to a machine where a GroupWise 6 domain resides. ! Make sure no GroupWise agents are currently running on the machine where you install the Monitor Agent. ! If you want to monitor gateways or non-HTTP-enabled agents (such as earlier versions of any GroupWise agent), you must install the SNMP service for Windows NT/2000 before you install Monitor. This enables the Monitor Agent to use SNMP.
Installing GroupWise Monitor
To install GroupWise Monitor: 1 On a Windows machine, run SETUP.EXE at the root of the GroupWise 6 CD > click Install Products > GroupWise Monitor > Install GroupWise Monitor. or Run SETUP.EXE from the ADMIN\MONITOR subdirectory on the CD or in your software distribution directory if you have updated it with GroupWise 6 software. 2 Follow the on-screen instructions to install GroupWise Monitor, supplying the information you gathered on the “GroupWise Monitor Worksheet” on page 134. The Monitor Agent console displays on the Windows machine.
Installing GroupWise Monitor 131
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Using GroupWise Monitor
You can use GroupWise Monitor at the Windows machine where it is installed or from anywhere you have access to a Web browser. ! “Monitor Agent Console” on page 132 ! “Monitor Web Console” on page 133
Monitor Agent Console To start the Monitor Agent and display the Monitor Agent console at the Windows machine where it is installed, click Start > Programs > GroupWise Monitor > GroupWise Monitor. The Monitor Agent console displays.
At the Monitor Agent console, you can perform many activities, for example:
132 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! To monitor an additional agent, click Options > Add Agent > specify the IP address and port number of a new agent to monitor > click OK. On the Options menu, use Discover Machine or Discover Network to locate multiple agents quickly. ! To display agent status information, select an agent > click Console. ! Use items on the File menu to configure the Monitor Agent as needed. ! Use items on the Options menu to check the status of links throughout your GroupWise system. ! Use items on the Reports menu to organize status information into a format that can be e-mailed or printed. For more information about using the Monitor Agent console, see "Monitor" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Monitor Web Console To display similar information in your Web browser, enter the Monitor URL in your Web browser: https://network_address/servlet/gwmonitor where network_address represents an IP address or a host name. The Monitor Web console displays.
You can use this same URL to view the same agent status information in various wireless browsers and devices. Refer to the online help in the Monitor Web console for additional information about each Monitor page. For more information about using the Monitor Web console, see "Monitor" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Installing GroupWise Monitor 133
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Monitor Worksheet
Item Explanation
1) Modules to Install: Mark the modules you want to install. You don't need to install both modules at the same time or on the ! GroupWise Monitor same platform. Agent ! GroupWise Monitor For more information, see “Deciding Where to Install Application GroupWise Monitor” on page 127.
2) Monitor Agent Specify the directory path where you want the Installation Path: Monitor Agent software installed.
! C:\GWMON (default) For more information, see “Deciding Where to Install ! Other: GroupWise Monitor” on page 127.
3) Monitor Agent Specify the IP address or DNS host name of the Network Address: Windows machine where the Monitor Agent will run.
! IP address: Specify the port number the Monitor Agent will listen ! DNS host name: on. The Monitor Agent must use a unique port number. ! Port number: 8200 (default) For more information, see “Specifying Network Addresses” on page 128.
4) Domain Directory Specify a domain directory where a GroupWise 6 Path: MTA is running.
For more information, see “Locating Agents to Monitor” on page 129.
5) Default Monitor Agent Select the default language for the Monitor Agent Console Language: console Interface.
For more information, see “Selecting the Default Language” on page 130.
134 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
6) Web Server: Mark the Web server you want to use with GroupWise Monitor. ! Netscape Enterprise Server for NetWare For more information, see “Deciding Where to Install ! Netscape FastTrack/ GroupWise Monitor” on page 127 Enterprise Server for Windows NT ! Microsoft Internet Information Server (IIS) Windows NT ! Apache Web Server for UNIX Solaris
7) Web Server Path: Specify the directory path to the Web server’s root directory.
For more information, see “Deciding Where to Install GroupWise Monitor” on page 127.
8) Web Server Network Specify the IP address or DNS host name of the Address: machine where your Web server runs.
! IP address: Specify the port number the Web server listens on.
! DNS host name: Mark whether or not the Web server uses SSL. ! Port number: For more information, see “Specifying Network 443 (SSL default) Addresses” on page 128. 80 (non-SSL default) ! Uses SSL ! Does not use SSL
9) Default Web Page: Select whether or not you want the Novell Web Services page to replace the Web server's default ! Novell page page. ! Current page For more information, see “Selecting the Web Server’s Default Web Page” on page 130.
10) Monitor Specify the directory path where you want Monitor Configuration File Path: configuration files installed.
! C:\NOVELL (default) For more information, see “Configuring GroupWise ! Other: Monitor” on page 129.
Installing GroupWise Monitor 135
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
11) Java Servlet Engine: Select the Java servlet engine you want to use with Monitor. ! Use Novell Servlet Gateway If you do not want to use the Novell Servlet Gateway, ! Use Other Java specify the directory path to your preferred Java Servlet Engine servlet engine.
Java Servlet Root For more information, see “Deciding Where to Install Directory: GroupWise Monitor” on page 127.
12) Novell Servlet To restrict access to the Novell Servlet Gateway, Gateway Authentication: specify a unique user name and password.
! User name: For more information, see “Deciding Where to Install ! Password: GroupWise Monitor” on page 127.
13) Default Monitor Web Select the default language for the Monitor Web Console Language: console Interface.
For more information, see “Selecting the Default Language” on page 130.
14) Monitor Object Specify the tree where you are installing Monitor. Configuration: Specify the context in which the Installation program ! Tree: should create the GroupWiseMonitor and ! Context: GroupWiseMonitorProvider objects, where configuration information will be stored.
For more information, see “Configuring GroupWise Monitor” on page 129.
136 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
5 Installing GroupWise Agents
GroupWise® agents are first installed and started as part of installing a new GroupWise system, as described in Chapter 1, “Installing a Basic GroupWise System,” on page 15. These sections help you install additional agents as you create new domains and post offices in your growing GroupWise system. ! “Selecting New Agent Locations and Platforms” on page 137 ! “Configuring New Agent Objects in NDS” on page 139 ! “Installing the NLM Agents” on page 140 ! “Installing the NT/2000 Agents” on page 150 ! “Uninstalling the Agents” on page 158 ! “Agent Planning Worksheets” on page 159
Selecting New Agent Locations and Platforms
Each time you create a new post office, you must set up at least one Post Office Agent (POA) for it. Each time you create a new domain, you must set up a Message Transfer Agent (MTA) for it. Before installing the agents for new post offices and domains, you should start by considering the following: ! “Agent Location” on page 137 ! “Agent Platform” on page 139
Agent Location The POA requires direct access to the post office directory, where the post office database (WPHOST.DB) is located. The MTA requires direct access to the domain directory, where the domain database (WPDOMAIN.DB) is
Installing GroupWise Agents 137
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
located. If an agent is not installed on the same machine with its directory and database, it requires either a mapped drive or a UNC path to its directory in order to function. Running an agent on the same machine where its directory and database are located simplifies network connections, because no login is required. In addition, it reduces network traffic and protects database integrity.
NW 5.1
NW 4.1 POA MTA
POA Domain X PO1X PO2X NW 4.1
POA PO3X
Running an agent on a different machine from where its directory and database are located distributes the processing load on your network.
NW 5.1
Domain X PO1X
NT/2000
NT/2000 PO1Y
POA MTA PO1Z
138 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Agent Platform
In general, GroupWise is most efficient if you match the agent platform with the network operating system in use where the post office and domain have been created. For example, if a domain and post office are located on a NetWare® server, then you would install the NLMTM agents for them. Those with mixed networks may wonder what platform combinations are possible. For more information, see the following sections in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation): ! "Cross-Platform Issues in the Post Office" in "Post Office Agent" ! "Cross-Platform Issues between Domains and Post Offices" in "Message Transfer Agent" Print the worksheet for the type of agents (NLM or NT/2000) that you will be installing. Make multiple copies if you are installing on multiple machines. ! “NLM Agent Worksheet” on page 159 ! “NT/2000 Agent Worksheet” on page 161
Configuring New Agent Objects in NDS
When you create new post offices and domains, Agent objects are automatically created for them. Most agent configuration can be done after installation, but a few settings should be established before you install the agent software.
In ConsoleOneTM: 1 Click the NDS® container where the new post office or domain is located to display its contents. 2 Click the Post Office object or Domain object > click the Agent object to display its properties. 3 In the Description field, type a brief description of the agent for display at the agent console. 4 In the Platform field, select NetWare Loadable Module or Windows NT/ 2000. 5 In the Network Address field, specify the IP address of the machine where you will install the GroupWise agents.
Installing GroupWise Agents 139
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
6 Click OK to save the new Agent object properties. 7 Repeat these steps for each new post office and domain for which you are installing agents. 8 Continue with “Installing the NLM Agents” on page 140. or Continue with “Installing the NT/2000 Agents” on page 150.
Installing the NLM Agents
The topics below help you plan and set up the GroupWise NLM agents: ! “Planning the NLM Agents” on page 140 ! “Setting Up the NLM Agents” on page 147
Planning the NLM Agents
Before installing the GroupWise NLM agents, you should complete the planning tasks listed below: ! “Deciding Where to Install the NLM Agents” on page 140 ! “Considering Alternatives for Monitoring the NLM Agents” on page 144 ! “Deciding Which Languages to Install” on page 145 ! “Deciding How to Start the NLM Agents” on page 145 These planning tasks provide concepts and information you will need as you install and set up the NLM agents. Be sure to print the “NLM Agent Worksheet” on page 159 to record your installation and setup information.
Deciding Where to Install the NLM Agents Use the “NLM Agent Worksheet” on page 159 to record your decisions about where to install the GroupWise NLM agents as you review the following considerations: ! “Meeting NetWare Server Requirements” on page 141 ! “Gathering Domain and Post Office Information” on page 141 ! “Selecting NLM Agent Location Relative to Post Offices and Domains” on page 142
140 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! “Selecting the NLM Agent Software Installation Directory” on page 143 ! “Configuring the NLM Agents for Clustering” on page 143
Meeting NetWare Server Requirements Each NetWare server where you run the GroupWise NLM agents must meet the following system requirements:
Operating System: Novell® NetWare 5.x or above plus the latest Support Pack for your version of NetWare
Available Disk Space: 6.5 MB
Available Memory: 1 MB for the NLM POA and main threads 1 MB for the NLM MTA and main threads 5.5 MB for the Agent Engine 1 MB for caching
The required disk space accommodates both GroupWise agents because both are automatically installed together. The required memory would be adequate for the most basic configuration of a single NLM agent on the server. Additional free memory can significantly increase agent performance. Multiple agents on the same server require additional memory. For assistance in figuring the required memory for more complex agent configurations, see the following sections in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/ documentation): ! "Estimating NLM POA Memory Requirements" in "Post Office Agent" ! "Estimating NLM MTA Memory Requirements" in "Message Transfer Agent"
Gathering Domain and Post Office Information Record the following information about the domains and post offices you are installing and setting up the GroupWise NLM agents for:
Installing GroupWise Agents 141
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 6: Domains, record the domain name and path to the domain directory for the new domain.
Under Item 7: Post Offices, record the post office name and path to the post office directory for the new post office.
Selecting NLM Agent Location Relative to Post Offices and Domains Record which GroupWise NLM agents you are installing on the NetWare server (POA, MTA, or both) and whether you want to install the agents locally or remotely in relation to their directories and databases, as described in “Agent Location” on page 137.
WORKSHEET
Under Item 1: Agents and Locations, mark the agents to install and their locations relative to the directories and databases they need to access.
If the NLM agents need to access their directories and databases on remote NetWare servers, you must add configuration information to the agent startup files to provide the needed access. You can choose from two access methods: ! Use the /dn switch to specify the distinguished name of the agent object that was created along with the Domain or Post Office object. ! Use the /user and /password switches to specify a network user ID and password for the agent to use when it accesses the remote NetWare server.
WORKSHEET
Under Item 1: Agents and Locations, record the startup switches and settings you’ll need to add to the agent startup files after installation if you are installing the NLM agents on a different NetWare server from where their directories and databases are located.
How to edit the startup files after installation is described in “Editing the NLM Agent Startup Files” on page 150.
142 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Selecting the NLM Agent Software Installation Directory For the easiest installation and setup, install the NLM agents in the SYS:\SYSTEM directory. This simplifies the use of startup files and ensures that the agent NLM programs are on the server search path. If you use a different directory, you will need to add that directory to the server search path.
WORKSHEET
Under Item 2: Installation Path, record the directory where you want to install the NLM agent software.
Both the MTA and the POA will be installed to the specified directory.
Configuring the NLM Agents for Clustering
NetWare Cluster ServicesTM is a server clustering system that ensures high availability and manageability of critical network resources including volumes (where GroupWise domains and post offices reside) and applications (such as the GroupWise agents). NetWare Cluster Services supports failover, failback, and migration of individually managed cluster resources. The GroupWise NLM agents can be configured to take advantage of the fault tolerant environment provided by NetWare Cluster Services if the following requirements are met: ! The domains and post offices to be serviced by the NLM agents have already been created on shared NSS volumes in the cluster. ! The NLM agents are being installed to a server that is part of the same cluster. When the agents are configured for clustering, their startup files are configured with shared volume names rather than specific server names. In addition, the POA is configured to more effectively re-establish logins with GroupWise clients when a failover or migration situation arises.
Installing GroupWise Agents 143
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 3: Configuring GroupWise Agents for Clustering, mark whether or not you want to configure the NLM agents for clustering.
If you are using clustering, under Item 11: Launch in Protected Mode, mark that you want the Agent Installation program to start the agents in Protected Mode. This is required in a clustering environment. For more information, see “Launching the NLM Agents in Protected Mode” on page 146.
Additional configuration of the Agent objects in ConsoleOne is required to complete the agent setup in a clustering environment. See "Post Office Agent" and "Message Transfer Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation) for additional instructions.
Considering Alternatives for Monitoring the NLM Agents You can monitor agent functioning in a variety of ways, as described in the following sections of the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation): ! "Monitoring the POA" in "Post Office Agent" ! "Monitoring the MTA" in "Message Transfer Agent" The agent Web consoles enable you to conveniently monitor the agents from your Web browser. If you want to use agent Web consoles, record the information required to set them up.
WORKSHEET
Under Item 6: Domains and Item 7: Post Offices, specify a unique HTTP port for each agent to use when communicating with your Web browser.
To limit access to the agent Web consoles, you can provide a unique user name and password. Do not use an NDS user name and password because the information passes over the insecure connection between your Web browser and the agents.
WORKSHEET
Under Item 4: Enable Web Console, specify a unique user name and password if you want to restrict access to the agent Web consoles.
144 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Deciding Which Languages to Install If you have users with various language preferences, you can install the GroupWise NLM agents in multiple languages, provided you have a multi- lingual version of the GroupWise software.
WORKSHEET
Under Item 5: Languages, list the languages you want to install the agents for.
By default, the agents will start in the language selected for the domain. If that language has not been installed, the agents will start in the language used by the operating system. If that language has not been installed, the agents will start in English.
Deciding How to Start the NLM Agents The Agent Installation program can help you start the GroupWise NLM agents by creating and modifying system files and by launching the agents for you at the end of the installation process. ! “Creating a GRPWISE.NCF File” on page 145 ! “Modifying the AUTOEXEC.NCF File” on page 146 ! “Launching the NLM Agents Immediately after Installation” on page 146 ! “Launching the NLM Agents in Protected Mode” on page 146
Creating a GRPWISE.NCF File The Agent Installation program will automatically create a GRPWISE.NCF file that contains the commands to start the GroupWise NLM agents on the NetWare server. If you are installing the agents for the first time on the server, skip to “Modifying the AUTOEXEC.NCF File” on page 146. If the agents have been previously installed on the server, the GRPWISE.NCF file already exists. You can have the Agent Installation program overwrite the existing file, append new lines to it, or create a new file named GRPWISn.NCF.
WORKSHEET
Under Item 8: If GRPWISE.NCF Exists, mark what you want the Agent Installation program to do about the existing file.
Installing GroupWise Agents 145
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Modifying the AUTOEXEC.NCF File The Agent Installation program can add a GRPWISE.NCF line to the AUTOEXEC.NCF file so the GroupWise NLM agents start automatically each time the server restarts.
WORKSHEET
Under Item 9: Update AUTOEXEC.NCF File, mark whether or not you want the Agent Installation program to update the AUTOEXEC.NCF file.
Be aware that if you choose to create a GRPWISn.NCF file during an update, a GRPWISn.NCF line will be added, resulting in multiple GRPWISn.NCF lines. Make sure you are not starting redundant agents.
Launching the NLM Agents Immediately after Installation If you are installing the GroupWise NLM agents on the same NetWare server where their directories and databases are located, the Agent Installation program can launch the agents at the end of the installation process. If you are installing the agents remotely in relation to their directories and databases, you must manually edit the agent startup files to configure them to access the remote servers. This configuration procedure is explained in “Editing the NLM Agent Startup Files” on page 150.
WORKSHEET
Under Item 10: Launch GroupWise Agents Now, mark whether or not the Agent Installation program can start the agents for you at the end of the installation process.
Launching the NLM Agents in Protected Mode If you want the Agent Installation program to launch the agents for you, you can indicate that you want them launched in Protected Mode on NetWare 5.
WORKSHEET
Under Item 11: Launch in Protected Mode, mark whether or not you want the Agent Installation program to start the agents in Protected Mode.
146 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If you choose to have the Agent Installation program start the agents in Protected Mode at the end of the installation process, this also adds the following command to the AUTOEXEC.NCF file:
protect grpwise.ncf
This line will automatically start the agents in Protected Mode in the future.
Setting Up the NLM Agents
Complete the following tasks to set up the GroupWise NLM agents. These tasks are designed to help you get the agents up and running as quickly as possible. ! “Preparing the NetWare Server for the NLM Agents” on page 147 ! “Installing the NLM Agent Software” on page 149 ! “Editing the NLM Agent Startup Files” on page 150
Preparing the NetWare Server for the NLM Agents Make sure the NetWare server where you will be installing the GroupWise NLM agents has been properly prepared to run the agents: ! “Meeting NLM Requirements” on page 147 ! “Obtaining a Static IP Address” on page 148 ! “Creating a NetWare Account for NLM Agent Access (Optional)” on page 148 ! “Adding the NLM Agent Installation Directory to the Server Search Path (Optional)” on page 149
Meeting NLM Requirements The GroupWise NLM agents rely on the following NLM programs:
NLM Description
CLIB The C libraries are general routines and functions used by many NLM programs. Make sure you have the latest version.
STREAMS Network Protocol Streams is a common interface for the operating system to access different network protocols.
Installing GroupWise Agents 147
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
NLM Description
TLI Transport Level Interface is an API used by NLM programmers. It provides communications between NLM programs and the STREAMS NLM.
NWSNUT NLM User Interface Utility gives the GroupWise agents the standard NetWare user interface with windows and lists.
SNMP Simple Network Management Protocol is a standard management protocol that provides control and monitoring of network software and hardware (required only if using SNMP).
DSAPI (MTA only) The Directory Services API accesses the NDS database, which provides global access to all resources on NetWare 4.x and 5.x networks (required for the MTA to perform NDS user synchronization).
TCPIP The TCP/IP Network Protocol allows the NetWare server to transmit and receive TCP/IP network packets (required only if connecting by way of TCP/IP).
The NLM agents cannot start and run properly if any of the required NLM programs are not available. Make sure the required NLM programs are loaded automatically each time you start the NetWare server. If you encounter a problem starting the NLM agents, verify NLM version compatibility. For technical services and file updates, see the Novell Support Connection® Worldwide Sites (http://www.support.novell.com/misc/worldwide.htm).
Obtaining a Static IP Address The NetWare server where the GroupWise NLM agents run must have a static IP address. DHCP cannot be used to dynamically assign an IP address for it. Make sure the server where you plan to install the agents has a static IP address.
Creating a NetWare Account for NLM Agent Access (Optional) When the GroupWise NLM agents run on a different NetWare server from where their directories and databases are located, and they are not set up to authenticate through NDS (using the /dn startup switch), the agents must use a specific NDS user name and password to log in to that server. To create a user for the agents to log in as: 1 In ConsoleOne, create a new user (such as GWAgents).
148 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Provide a password for that user (such as GWise). 3 Grant that user the following rights to all domain, post office, and document storage directories: ! Read or execute files ! Write to files ! Create files or directories ! Erase files or directories ! Modify files (rename or change attributes) ! File scan
Adding the NLM Agent Installation Directory to the Server Search Path (Optional) If you have selected a directory other than SYS:\SYSTEM to install the agents to, add the agent installation directory to the server search path by adding a SEARCH command to the AUTOEXEC.NCF file.
Installing the NLM Agent Software Once you have prepared the NetWare server to run the GroupWise NLM agents, you are ready to install them. At a Windows* machine: 1 Map a drive to the NetWare server where you want to install the agents. 2 Make sure you have sufficient rights to install software in the desired directory. 3 Run SETUP.EXE at the root of the GroupWise 6 CD > click Install Products > GroupWise Agents > Install GroupWise Agents. or Run INSTALL.EXE from the AGENTS subdirectory on the CD or in your software distribution directory if you have updated it with GroupWise 6 software. 4 Follow the on-screen instructions to install the GroupWise NLM agents on the NetWare server, supplying the information you gathered on the “NLM Agent Worksheet” on page 159.
Installing GroupWise Agents 149
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
5 If necessary, modify the agent startup files as described in “Editing the NLM Agent Startup Files” on page 150. 6 If you encounter any problems starting the agents, refer to "Post Office Agent" and "Message Transfer Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation) for additional instructions. 7 To monitor an agent from your Web browser, view the URL where the agent is located by supplying the IP address and port number. For example: http://123.456.78.90:1677 http://123.456.78.90:7100 http://123.456.78.90:7180 When viewing the agent Web console, you can specify either the standard TCP port or the HTTP port you specified during installation.
Editing the NLM Agent Startup Files The Agent Installation program creates a customized agent startup file for each domain and post office location. The first eight characters of the post office and domain names became the names of the agent startup files, along with an agent-specific extension. For example, if the post office name is acctpo, then the POA startup file is named ACCTPO.POA. The Agent Installation program also customizes each startup file with the correct /home switch setting, pointing to the domain or post office directory. Each startup file also provides a comprehensive list of startup switches, with all but the /home switch commented out. You can use any ASCII text editor to set the startup switches required by the access method you recorded under Worksheet Item 1: Agents and Locations. The agent startup files are located in the agent installation directory. After modifying the startup files, use the GRPWISE.NCF file to start the NLM agents.
Installing the NT/2000 Agents
The topics below help you plan and set up the GroupWise agents for Windows NT* and Windows 2000: ! “Planning the NT/2000 Agents” on page 151 ! “Setting Up the NT/2000 Agents” on page 156
150 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Planning the NT/2000 Agents
Before installing the GroupWise NT/2000 agents, you should complete the planning tasks listed below: ! “Deciding Where to Install the NT/2000 Agents” on page 151 ! “Considering Alternatives for Monitoring the NT/2000 Agents” on page 153 ! “Configuring the NT/2000 Agents as Services” on page 154 ! “Deciding Which Languages to Install” on page 155 ! “Starting the NT/2000 Agents for the First Time” on page 155 The planning tasks provide concepts and information you will need as you install and set up the NT/2000 agents. Be sure to print the “NT/2000 Agent Worksheet” on page 161 to record your installation and setup information.
Deciding Where to Install the NT/2000 Agents Use the “NT/2000 Agent Worksheet” on page 161 to record your decisions about where to install the GroupWise NT/2000 agents as you review the following considerations: ! “Meeting NT/2000 Machine Requirements” on page 151 ! “Gathering Domain and Post Office Information” on page 152 ! “Selecting NT/2000 Agent Location Relative to Post Offices and Domains” on page 152 ! “Selecting the NT/2000 Agent Software Installation Directory” on page 153
Meeting NT/2000 Machine Requirements Each Windows NT or Windows 2000 machine where you run the GroupWise NT/2000 agents must meet the following requirements:
Operating System: Windows NT 4 or Windows 2000 plus the latest Service Pack for your version of Windows
Available Disk Space: 5.5 MB
Installing GroupWise Agents 151
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Available Memory: 1 MB for the NT/2000 POA and main threads 1 MB for the NT/2000 MTA and main threads 4.5 MB for the Agent Engine 1 MB for caching
The required disk space accommodates both GroupWise agents because both are automatically installed together. The required memory would be adequate for the most basic configuration of a single agent. Additional free memory can significantly increase agent performance. Multiple agents on the same machine require additional memory. Although the NT/2000 agent memory requirements differ slightly from the NLM agents, you can use the figures provided for the NLM agents to see what agent processes are most memory intensive. This can help you figure memory requirements for more complex configurations. See the following sections in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation): ! "Estimating NLM POA Memory Requirements" in "Post Office Agent" ! "Estimating NLM MTA Memory Requirements" in "Message Transfer Agent"
Gathering Domain and Post Office Information Record the required information about the domains and post offices you are installing and setting up the GroupWise NT/2000 agents for:
WORKSHEET
Under Item 6: Domains, record the domain name and the path to the domain directory for the new domain.
Under Item 7: Post Offices, record the post office name and the path to the post office directory for the new post office.
Selecting NT/2000 Agent Location Relative to Post Offices and Domains Record which GroupWise NT/2000 agents you are installing on the machine (POA, MTA, or both) and whether you want to install the agents locally or remotely in relation to their directories and databases, as described in “Agent Location” on page 137.
152 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 1: Agents and Locations, mark the agents to install and their locations relative to the directories and databases they need to access.
Selecting the NT/2000 Agent Software Installation Directory Record the directory where you want to install the GroupWise NT/2000 agents. Both the MTA and the POA will be installed to the specified directory.
WORKSHEET
Under Item 2: Installation Path, record the directory where you want to install the NT/2000 agent software.
Under Item 3: Installation Options, mark Install GroupWise Agent Software.
Considering Alternatives for Monitoring the NT/2000 Agents You can monitor agent functioning in a variety of ways, as described in the following sections of the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation): ! "Monitoring the POA" in ''Post Office Agent' ! "Monitoring the MTA" in "Message Transfer Agent" The agent Web consoles enable you to monitor the agents from your Web browser. If you want to use agent Web consoles, record the information required to set them up.
WORKSHEET
Under Item 6: Domains and Item 7: Post Offices, specify a unique HTTP port for each agent to use when communicating with your Web browser.
To limit access to the agent Web consoles, you can provide a unique user name and password. Do not use an NDS user name and password because the information passes over the insecure connection between your Web browser and the agents.
Installing GroupWise Agents 153
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 4: Enable Web Console, specify a unique user name and password if you want to restrict access to the agent Web consoles.
If you want to use an SNMP manager program such as Novell ManageWise® to monitor the agents, you must install some SNMP components along with the NT/2000 agent software.
WORKSHEET
Under Item 3: Installation Options, mark Install and Configure SNMP for GroupWise Agents if you want to use an SNMP manager program.
If this option is dimmed during installation, the SNMP service has not been enabled on the Windows NT/2000 machine where you are installing the agents. If you want to monitor the agents from an SNMP management program, the SNMP service must be enabled so you can select this option.
Configuring the NT/2000 Agents as Services When you run the GroupWise NT/2000 agents as services, they can start automatically and run without a user interface.
WORKSHEET
Under Item 3: Installation Options, mark Install as NT/2000 Services if you want to run the agents as services.
When you run the NT/2000 agents as services, they must run under a specific NT/2000 user account. When domains and post offices are located on the same machine where you are installing the agents, the agents can run under the local system account. You can also display the agent consoles when the agent software, directories, and databases are local. When domains and post offices are located on a remote machine, you must specify a user with rights to access the domain and post office directories. If the NT/2000 agents need to log in to an NT/2000 machine, provide a Windows user name and password. If the NT/2000 agents need to log in to a NetWare server, provide an existing NDS user name and password.
154 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WORKSHEET
Under Item 8: NT/2000 Service Information, record the account the agents will run under, and if necessary, the password for the account.
As with all NT/2000 services, the NT/2000 agents can be started automatically or manually as services each time the NT/2000 machine restarts.
WORKSHEET
Under Item 8: NT/2000 Service Information, mark how you want the NT/2000 agents to start each time the machine is restarted.
Deciding Which Languages to Install If you have users with various language preferences, you can install the GroupWise NT/2000 agents in multiple languages, provided you have a multi- lingual version of the GroupWise software.
WORKSHEET
Under Item 5: Languages, list the languages you want to install the agents for.
By default, the agents will start in the language selected for the domain. If that language has not been installed, the agents will start in the language used by the operating system. If that language has not been installed, the agents will start in English.
Starting the NT/2000 Agents for the First Time Unless you want to modify the agent startup files, you can have the Agent Installation program start the GroupWise NT/2000 agents for you at the end of the installation process.
WORKSHEET
Under Item 9: Launch GroupWise Agent Now, mark whether or not you want the Agent Installation program to start the agents for you after installation.
Installing GroupWise Agents 155
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Modifying the startup files is usually not necessary for an initial installation of the NT/2000 agents.
Setting Up the NT/2000 Agents
Complete the following tasks to set up the NT/2000 agents. These tasks are designed to help you get the NT/2000 agents up and running as quickly as possible: ! “Preparing the NT/2000 Machine for the NT/2000 Agents” on page 156 ! “Installing the NT/2000 Agent Software” on page 157
Preparing the NT/2000 Machine for the NT/2000 Agents Make sure the NT/2000 machine where you will be installing the GroupWise NT/2000 agents has been properly prepared to run the agents: ! “Obtaining a Static IP Address” on page 156 ! “Mapping Drives to Post Offices and Domains” on page 156 ! “Creating an NT/2000 User Account for Remote Access (Optional)” on page 157 ! “Enabling SNMP (Optional)” on page 157
Obtaining a Static IP Address The NT/2000 machine where the GroupWise NT/2000 agents run must have a static IP address. DHCP cannot be used to dynamically assign an IP address for it. Make sure the machine where you plan to install the NT/2000 agents has a static IP address.
Mapping Drives to Post Offices and Domains The POA requires direct access to the post office directory and the MTA requires direct access to the domain directory. If the agents are not installed on the same machine where their directories are located, make sure the machine has drives mapped to all locations where the agents will need access. After installation, the agents can access their directories using either mapped drives or UNC paths. However, mapped drives are required during installation so that the agent startup files can be set up properly.
156 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Creating an NT/2000 User Account for Remote Access (Optional) If you specified a new NT/2000 user name and password under Worksheet Item 8: NT/2000 Services Information, create the new NT/2000 user account so it will be ready when you start the agents for the first time. In Windows NT, click Start > Programs > Administrative Tools > User Manager to create a new user. In the Control Panel of Windows 2000, double-click Users and Passwords to add a new user. Grant the user Full Control rights in the domain and post office directories.
Enabling SNMP (Optional) If you want to monitor the GroupWise NT/2000 agents from an SNMP manager program such as Novell ManageWise, SNMP must be enabled on the Windows NT/2000 machine where the agents are installed. If it is not already enabled, you should enable it before you run the Agent Installation program. In the Control Panel in Windows NT, double-click Network > click Services > Add > double-click SNMP. In the Control Panel in Windows 2000, double-click Add/Remove Programs > click Add/Remove Windows Components > double-click Management and Monitoring Tools > select Simple Network Management Protocol.
Installing the NT/2000 Agent Software Once you have prepared the NT/2000 machine to run the GroupWise NT/2000 agents, you are ready to install them. At the Windows NT/2000 machine where you want to install the NT/2000 agents: 1 Make sure you have mapped drives to all domain and post office directories for which you are installing agents. 2 If you are planning to install the SNMP components of the NT/2000 agents, stop the SNMP service. 3 Run SETUP.EXE at the root of the GroupWise 6 CD > click Install Products > GroupWise Agents > Install GroupWise Agents. or
Installing GroupWise Agents 157
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Run INSTALL.EXE from the AGENTS subdirectory on the CD or in your software distribution directory if you have updated it with GroupWise 6 software. 4 Follow the on-screen instructions to install the GroupWise NT/2000 agents on the NT/2000 machine, supplying the information you gathered on the “NT/2000 Agent Worksheet” on page 161. 5 If you encounter any problems starting the agents, see "Post Office Agent" and "Message Transfer Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation) for additional instructions. 6 To monitor an agent from your Web browser, view the URL where the agent is located by supplying the IP address and port number. For example: http://123.456.78.90:1677 http://123.456.78.90:7100 http://123.456.78.90:7180 When viewing the agent Web console, you can specify either the standard TCP port or the HTTP port you specified during installation.
Uninstalling the Agents
If you move the GroupWise agents to a different machine, you can uninstall them from the old location to regain disk space if no other GroupWise agents are running there. 1 Stop the agents. 2 Run INSTALL.EXE in the AGENTS subdirectory of the GroupWise software distribution directory or GroupWise 6 CD. 3 In the Install/Uninstall dialog box, click Uninstall to remove the agent software from the machine. NT/2000 Note: If the NT/2000 agents were running as services, the Agent Installation program removes the services, registry entries, and start menu icons from Windows NT/2000.
158 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Agent Planning Worksheets
NLM Agent Worksheet
Item Explanation
1) Agents and Locations: Mark the NLM agents you want to install and where you want to install them. ! POA local to post office If you want to install the agents on a server different ! MTA local to domain from where their directories and databases are located, specify the startup switches the agents can ! POA remote from post use to access the remote servers. office For more information, see “Deciding Where to Install Access method: the NLM Agents” on page 140. ! MTA remote from domain
Access method:
2) Installation Path: Specify the directory where you want to install the NLM agent software.
For more information, see “Selecting the NLM Agent Software Installation Directory” on page 143.
3) Configure GroupWise Mark whether or not you want to enable the NLM Agents for Clustering: agents for clustering.
! Yes For more information, see “Configuring the NLM ! No Agents for Clustering” on page 143.
4) Enable Web Console: Mark whether or not you want to enable the agent Web consoles so you can monitor the agents from ! No your Web browser. If you do, provide a unique user ! Yes name and password if you want to restrict access.
User name: For more information, see “Considering Alternatives Password: for Monitoring the NLM Agents” on page 144.
5) Languages: List the languages you want to install.
For more information, see “Deciding Which Languages to Install” on page 145.
Installing GroupWise Agents 159
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
6) Domains: List the domains you are installing the NLM MTA for.
! Domain name: For more information, see “Deciding Where to Install ! Path to database: the NLM Agents” on page 140. ! HTTP port: 7180 (default)
7) Post Offices: List the post offices you are installing the NLM POA for. ! Post office name: ! Path to database: For more information, see “Deciding Where to Install the NLM Agents” on page 140. ! HTTP port: 7181 (default)
8) If GRPWISE.NCF If this is an update, decide what you want the Agent Exists: Installation program to do about the existing GRPWISE.NCF file. ! Overwrite the existing file For more information, see “Creating a ! Append the existing GRPWISE.NCF File” on page 145. file ! Create a new file named GRPWISn.NCF
9) Update Decide whether or not you want the Agent AUTOEXEC.NCF File: Installation program to update the AUTOEXEC.NCF file so the NLM agents will start each time the ! Yes NetWare server restarts. ! No For more information, see “Modifying the AUTOEXEC.NCF File” on page 146.
10) Launch GroupWise Mark whether or not the Agent Installation program Agents Now: can start the NLM agents for you at the end of the installation process. ! Yes ! No For more information, see “Launching the NLM Agents Immediately after Installation” on page 146.
160 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Explanation
11) Launch in Protected Mark whether or not you want the Agent Installation Mode: program to start the NLM agents in Protected Mode on NetWare 5. ! Yes ! No For more information, see “Launching the NLM Agents in Protected Mode” on page 146.
NT/2000 Agent Worksheet
Item Description
1) Agents and Locations: Mark the NT/2000 agents you want to install and where you want to install them. ! POA local to post office For more information, see “Deciding Where to Install ! MTA local to domain the NT/2000 Agents” on page 151. ! POA remote from post office ! MTA remote from domain
2) Installation Path: Specify the directory where you want to install the NT/2000 agent software.
For more information, see “Selecting the NT/2000 Agent Software Installation Directory” on page 153.
3) Installation Options: Mark the installation options you want when you install the NT/2000 agents. ! Install GroupWise agent software For more information, see “Deciding Where to Install ! Install and configure the NT/2000 Agents” on page 151, “Considering SNMP for GroupWise Alternatives for Monitoring the NT/2000 Agents” on agents page 153, and “Configuring the NT/2000 Agents as Services” on page 154. ! Install as NT/2000 services
Installing GroupWise Agents 161
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Description
4) Enable Web Console: Mark whether or not you want to enable the agent Web consoles so you can monitor the agents from ! No your Web browser. If you do, provide a unique user ! Yes name and password if you want to restrict access.
User name: For more information, see “Considering Alternatives Password: for Monitoring the NT/2000 Agents” on page 153.
5) Languages: List the languages you want to install.
For more information, see “Deciding Which Languages to Install” on page 155.
6) Domains: List the domains you are installing the NT/2000 MTA for. ! Domain name: ! Path to database: For more information, see “Deciding Where to Install the NT/2000 Agents” on page 151. ! HTTP port: 7180 (default)
7) Post Offices: List the post offices you are installing the NT/2000 POA for. ! Post office name: ! Path to database: For more information, see “Deciding Where to Install the NT/2000 Agents” on page 151. ! HTTP port: 7181 (default)
162 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Item Description
8) NT/2000 Service If you are installing the NT/2000 agents as services, Information: mark the type of account they can use to log in.
Account type: If needed, specify the NT/2000 user account they can run under. ! Use local system account Also mark whether you want them to be started automatically or manually each time the NT/2000 Allow service to machine restarts. interact with desktop: For more information, see “Configuring the NT/2000 - Yes Agents as Services” on page 154. - No ! Use this NT/2000 user account:
User name: Password:
Startup type: ! Automatic ! Manual ! Disabled
9) Launch GroupWise Mark whether or not the Agent Installation program Agents Now: should start the NT/2000 agents for you at the end of the installation process. ! Yes ! No For more information, see “Starting the NT/2000 Agents for the First Time” on page 155.
Installing GroupWise Agents 163
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
164 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
6 Installing the GroupWise Client
The following sections will assist you with installing the GroupWise® 6 client for Windows*. ! “Determining Requirements” on page 165 ! “Installing the Client Software” on page 166 ! “Starting the Client” on page 167
Determining Requirements
The workstation where you install the GroupWise client for Windows must meet the following minimum requirements:
Hardware/Software Requirements
Operating System Windows 95 or higher
CPU Pentium* 133 or higher (recommended) for Windows 95/98 and Windows NT*
Pentium 200 or higher (recommended) for Windows 2000
RAM 48 MB or higher (recommended) for Windows 95/98
64 MB or higher (recommended) for Windows NT
128 MB or higher (recommended) for Windows 2000
Disk Space 5 MB (workstation installation) 51 MB (standard installation)
Installing the GroupWise Client 165
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Installing the Client Software
The GroupWise client for Windows can be installed to users’ workstations by the user or by the system administrator. The system administrator can restrict which selections the user can make during installation by use of a configuration file. The system administrator can also prompt for or force updates of client software (using AutoUpdate) through a mapped drive or IP connection to the software distribution directory, so users cannot make any selections. If the system administrator wants to add predefined LDAP service accounts to the Address Book in the client during installation, this information must be added to the configuration file before the client is installed for the first time. To find out about these and other client installation options that are available to the system administrator, see "Client" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/ documentation) before installing the client. During the installation of your GroupWise system, the client files were copied to the software distribution directory on your server. For example, if you accepted the default Z:\GRPWISE\SOFTWARE as your target, the client software was copied to Z:\GRPWISE\SOFTWARE\CLIENT\WIN32. SETUP.EXE is run from the software distribution directory. In order to run this setup program, users require rights to CLIENT\WIN32 in the software distribution directory. The minimum rights required are Read and File Scan. (This does not apply if you are running AutoUpdate over an IP connection.) 1 Map a drive to the client files in the software distribution directory. A good place for this mapping would be the users' system or personal login scripts. The following is an example of a NetWare® login script command:
MAP Q:=SERVER/VOLUME:GRPWISE\SOFTWARE\CLIENT\WIN32 2 From the Windows taskbar, click Start > Run. 3 Browse to the software distribution directory and select SETUP.EXE. 4 Click OK > follow the prompts until you reach the Setup Options screen > click one of the following options: Workstation Install: Allows the user to run GroupWise from the network, which saves disk space on the user's hard drive.
166 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Standard Install: Installs all of the client files on the user's hard drive. This option is required when the computer will run GroupWise in Caching or Remote mode. See "Client" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation) for more information about setting up GroupWise Remote and Caching modes. 5 Click the Browse button to select a different Destination Folder path or click Next to select the default. 6 Make sure each component you want to install is selected > click Next. GroupWise: This component is required. Internet Browser Mail Integration: Sets GroupWise to be the default e- mail program on the workstation, so that whenever the user clicks an e- mail link on a web page or chooses the Mail command in the browser (Internet Explorer 3.x and higher, Netscape Navigator* 4.03-4.08), GroupWise starts. GroupWise Tip of the Day: The Tip of the Day displays different hints about using GroupWise. A new tip is displayed each time GroupWise is started. 7 Continue to follow the prompts and select the options you want.When the setup program has completed, a shortcut to run GroupWise will appear on the user's desktop.
Starting the Client
If you did not grant object and property rights or set up a GroupWise name server, the user may need to add the following startup options to the GroupWise shortcut properties: Syntax: /ph-path to post office /@u-GroupWise user ID Example: Q:\GrpWise.exe /ph-J:\advert /@u-mjohnson For more information on startup switches, see "Client" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation). To launch GroupWise for the first time: 1 Double-click the GroupWise icon on the user's desktop. 2 Type the user's password. If an error message appears stating that no archive path has been set for storing archived items, click OK. You can specify the path later.
Installing the GroupWise Client 167
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
168 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
II Update
Chapter 7, “Understanding the Update Process,” on page 171 Chapter 8, “Preparing Your GroupWise System,” on page 177 Chapter 9, “Updating Your GroupWise System,” on page 179
Update 169
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
170 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
7 Understanding the Update Process
You can update a GroupWise® 5, 5.1, 5.2, 5.5, or 5.5 Enhancement Pack system to GroupWise 6. To update a GroupWise 4.x system to GroupWise 6, you need to first update the system to GroupWise 5.x. Before you begin updating your GroupWise 5.x system to GroupWise 6, you should review the following sections. These sections, which describe the process to follow when updating, will help you plan and implement a successful update strategy: ! “Extending the NDS Schema” on page 172 ! “Installing the GroupWise Software” on page 172 ! “Updating GroupWise Domain and Post Office Databases” on page 173 ! “Updating the GroupWise Client” on page 174 ! “Updating the GroupWise Internet Agent” on page 175 ! “Updating GroupWise WebAccess” on page 175 ! “Using GroupWise Gateways” on page 176 For a list of enhancements and new features in GroupWise 6, see Appendix B, “What’s New in GroupWise 6,” on page 207. In some cases, you may need to maintain a mixed-version environment as you roll out GroupWise 6. For a table showing which GroupWise 5.x and 6 components can be used together, see Appendix C, “GroupWise 5.x and 6 Compatibility Matrix,” on page 223.
Understanding the Update Process 171
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Extending the NDS Schema
GroupWise 6 includes new functionality that requires you to extend the schema of any NDS® trees where you have GroupWise objects. The GroupWise Installation Advisor automatically extends the schema for any trees you select.
Installing the GroupWise Software
The GroupWise 6 software requirements are different than the GroupWise 5.x software requirements. To review the requirements, see “Summary of Requirements for a Basic GroupWise System” on page 38.
Software Distribution Directory
The GroupWise Installation Advisor helps you copy the GroupWise 6 software (administration, agents, client, and so forth) to a GroupWise software distribution directory. This can be an existing software distribution directory or a new software distribution directory. How users run the GroupWise client is the main issue to consider when deciding whether to update an existing software distribution directory or create a new one. The GroupWise 6 client will not run against a GroupWise 5.x post office. When you update an existing software distribution directory, users running from the software distribution directory (a workstation installation) are automatically forced to update. If their post office is not yet updated, they will be locked out until you update it. Users running the GroupWise client from their local drives (a standard installation) will continue to run the local GroupWise client until you prompt them to update. In general, you should update an existing software distribution directory only if 1) all users can run the GroupWise client from their local drives, or 2) you can update all users' post offices within a reasonable time of updating the software distribution directory. If this approach will not work for you, you should create a new GroupWise 6 software distribution directory. You can then use the new software distribution directory to update your domains and post offices to version 6 while users continue to run the GroupWise 5.x client from the existing software distribution directory. Once the users' post offices have been updated, you can update their existing software distribution directory to version 6 to get them up and running on the GroupWise client.
172 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
ConsoleOne
GroupWise 6 is administered through ConsoleOneTM, version 1.2d.1 or higher. ConsoleOne 1.2d.1 is included on the GroupWise 6 CD. If necessary, you can install it at the same time as the other GroupWise software. Once you’ve installed GroupWise 6, we strongly recommend that you no longer use NetWare® Administrator to administer your GroupWise system. Doing so can cause problems such as overwriting of the GroupWise 6 database dictionary files by the 5.x dictionary files. In addition, some GroupWise 6 administration functionality, such as post office disk space management, is available only when using ConsoleOne. You can also use ConsoleOne to administer the GroupWise 5.x components in your GroupWise system.
Administration Agent
Beginning with GroupWise 5.5, the Administration Agent’s functionality was moved into the Message Transfer Agent (MTA) and the Post Office Agent (POA). If you are updating a GroupWise 5, 5.1, or 5.2 system, you need to make sure that you don't run the Administration Agent against the domain after you’ve started the GroupWise 6 MTA. Doing so may result in the loss of GroupWise 6 information. The Agent Installation program has been modified to help you remove the ADA.
Updating GroupWise Domain and Post Office Databases
Functionality enhancements in GroupWise 6 require the GroupWise domain and post office databases to be updated with new records and fields, similar to the schema extensions that are required for NDS. You must update the primary domain first so that correct replication of GroupWise 6 information can take place as you update post offices and secondary domains. After you update the primary domain, you can update the primary domain's post offices or you can update a secondary domain and its post offices. The following diagram illustrates this update sequence.
Understanding the Update Process 173
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
1 Primary Domain2 Secondary Domain
Post Post Post Post Post 2 Office Office Office 3 Office Office
To update a domain database, you run the GroupWise 6 Message Transfer Agent (MTA) against it. The first time the GroupWise 6 MTA runs against a domain, it rebuilds the domain database (WPDOMAIN.DB) so the database includes the records required for new GroupWise 6 information. The MTA uses a new domain dictionary file (GWDOM.DC) to rebuild the database. Likewise, to update a post office database, you run the GroupWise 6 Post Office Agent (POA) against it. The first time the GroupWise 6 POA runs against the post office, it rebuilds the post office database (WPHOST.DB) so the database includes the new records required for GroupWise 6 information. The POA uses a new post office dictionary file (GWPO.DC), which it requests from the MTA, to rebuild the database. A user cannot run the GroupWise 6 client until his or her post office has been updated.
Updating the GroupWise Client
After a post office is updated to version 6, users can run the GroupWise 6 client on a Windows* 95/98 or Windows NT*/2000 workstation. If necessary, they can also continue to run their GroupWise 5.x client for Windows, but they will not have GroupWise 6 functionality such as disk space management and Caching mode.
IMPORTANT: Users who need to proxy users on a GroupWise 5.x post office should not update to the GroupWise 6 client. If they do, they will not be able to access the 5.x post office until it is updated to version 6. For a list of new features in the GroupWise 6 client, see Appendix B, “What’s New in GroupWise 6,” on page 207.
174 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Updating the GroupWise Internet Agent
The GroupWise 6 Internet Agent will be fully functional only when running against GroupWise 6 domains and post offices. If you run it against a GroupWise 5.x domain or post office, users on GroupWise 5.x post offices will be able to send and receive Internet messages (SMTP support), but will not be able to use POP3 and IMAP4 clients to access their mailboxes. The GroupWise 5.x Internet Agent will run against a GroupWise 6 domain and post office, which means that you can continue to use it until all domains and post offices are updated to version 6. For a list of new features in GroupWise 6 Internet Agent, see Appendix B, “What’s New in GroupWise 6,” on page 207.
Updating GroupWise WebAccess
As you plan how to update GroupWise WebAccess, you need to consider both the WebAccess Agent and the WebAccess components on the Web server. ! “WebAccess Agent” on page 175 ! “WebAccess Components on the Web Server” on page 176
WebAccess Agent The GroupWise 6 WebAccess Agent can access only GroupWise 6 domains and post offices. The GroupWise 5.x WebAccess Agent, with the exception of the GroupWise 5.5 Enhancement Pack SP3 WebAccess Agent, can access only GroupWise 5.x domains and post offices. To continue to provide the WebAccess Agent with access to post offices, you will need to: ! Update the GroupWise 5.x WebAccess Agent at the same time you update its domain and post offices. This keeps the WebAccess Agent version synchronized with the domain and post office version. ! If you have multiple domains or post offices that will be updated over a long period of time, keep a GroupWise 5.x WebAccess Agent, installed in a GroupWise 5.x domain, to service users on GroupWise 5.x post offices. Install the GroupWise 6 WebAccess Agent in a GroupWise 6 domain to service users on GroupWise 6 post offices.
Understanding the Update Process 175
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
WebAccess Components on the Web Server
The GroupWise 6 WebAccess Agent can communicate with the GroupWise 5.5 and 5.5 Enhancement Pack WebAccess servlets (on the Web server). If you have GroupWise 5.5 or 5.5EP, you can update your WebAccess Agent independent of the WebAccess components on the Web server. The GroupWise 6 WebAccess Agent cannot communicate with pre-5.5 Web server components. In this case, you will need to update the WebAccess components on your Web server at the same time you update the WebAccess Agent. For a list of changes and new features in GroupWise 6 WebAccess, see Appendix B, “What’s New in GroupWise 6,” on page 207.
Using GroupWise Gateways
There are no known issues with using GroupWise gateways with GroupWise 6.
176 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 Preparing Your GroupWise System
To prepare your GroupWise® 5.x system to be updated to version 6, you should complete the following tasks: ! Validate your domain and post office databases to make sure 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 GroupWise 5.x Maintenance guide at the Novell® Documentation Web site (http://www.novell.com/ documentation). ! Back up the domain or post office immediately before updating it. GroupWise provides a backup utility, GWBACKUP.EXE, that you can use to back up (and restore) your databases. For information about using the backup utility, see the GroupWise 5.x Maintenance guide at the Novell Documentation Web site (http://www.novell.com/ documentation).
Preparing Your GroupWise System 177
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
178 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
9 Updating Your GroupWise System
The following sections provides step-by-step instructions for updating your GroupWise® system. Before beginning, make sure you've reviewed Chapter 7, “Understanding the Update Process,” on page 171 and Chapter 8, “Preparing Your GroupWise System,” on page 177. ! “Installing the GroupWise 6 Software” on page 179 ! “Updating the Primary Domain” on page 183 ! “Updating Post Offices” on page 193 ! “Updating Users' GroupWise Clients” on page 195 ! “Updating Secondary Domains” on page 198 ! “Updating the GroupWise Internet Agent” on page 198 ! “Updating GroupWise WebAccess” on page 198
Installing the GroupWise 6 Software
To start the GroupWise Installation Advisor: 1 From a Windows* 95/98/NT/2000 workstation, log in as an Admin equivalent to the NDS® tree where you are installing GroupWise. 2 Click Start > Run > type d:setup.exe (where d is your CD drive).
Updating Your GroupWise System 179
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
3 Click Create or Update a GroupWise System > click Yes to accept the license agreement and display the Welcome to GroupWise Install dialog box.
180 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Click Next until you reach the Administration Options dialog box.
5 Make sure that Create a New System or Update an Existing System is selected > click Next to display the Select Tree dialog box.
6 In the Select Tree dialog box, select the trees whose schema you want to extend (you should extend the schema of all trees where GroupWise
Updating Your GroupWise System 181
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
objects reside) > click Next > follow the prompts until you reach the Ready to Install dialog box.
7 Click Install > follow the prompts until you reach the Determine Next Step dialog box.
182 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
8 Click Updating an Existing GroupWise 5.x System > click Next to display the Update GroupWise system dialog box.
9 Continue with “Updating the Primary Domain” on page 183.
Updating the Primary Domain
To update the primary domain, you need to install and start the GroupWise 6 MTA. The MTA uses the new domain dictionary file (GWDOM.DC) to update the domain database to version 6.
IMPORTANT: The MTA and ADA cannot be running while you update the MTA files. In addition, once you've updated to the GroupWise 6 MTA, do not run the ADA again. The ADA became obsolete with GroupWise 5.5. Running the ADA in combination with a GroupWise 6 MTA will result in the loss of GroupWise 6 information. To install and start the GroupWise 6 MTA: 1 To install the MTA to a NetWare® server, make sure the workstation has access to both the primary domain directory and the NetWare server where you want to install the MTA > enter the path to the primary domain directory > click Update to launch the Agent Installation program. or
Updating Your GroupWise System 183
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
To install the MTA to a Windows NT*/2000 machine, click Finish > go to the NT/2000 machine > ensure that you have access to the primary domain directory > start the Agent Installation program (INSTALL.EXE). The Agent Installation program is located in the AGENTS directory in the GroupWise 6 software distribution directory or on the GroupWise 6 CD. 2 Click Yes to accept the license agreement and display the Overview dialog box.
3 Click Next to display the Install/Uninstall dialog box.
184 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
4 Make sure Install is selected > click Next to display the Select Platform dialog box.
5 In the Select Platform dialog box, select NetWare or Windows NT > click Next to display the Installation Path dialog box.
Updating Your GroupWise System 185
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The default NetWare installation directory is SYS:\SYSTEM and the default Windows NT/2000 directory is C:\GRPWISE. You can, however, install the agent files to any directory. On NetWare, if you don’t install to the SYS:\SYSTEM directory, you must define the agent directory in the server’s search path. For example, you could add SEARCH ADD SYS:\SYSTEM\agent_directory to the AUTOEXEC.NCF file, where agent_directory is the actual name of the installation directory. If you are installing to Windows NT/2000, the dialog box displays the following options: Install GroupWise Agent Software: This option must be selected to install the agent files. Install and Configure SNMP for GroupWise Agents: Select this option to enable the MTA to be monitored through an SNMP management program. This option is available only if the SNMP service is enabled on the NT/2000 machine. Install as NT Services: Select this option to install the MTA as a Windows service. 6 Select the directory where you want to install the agent files > click Next to display the Web Console Information dialog box.
186 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The Web console enables you to view the MTA’s statistics and diagnostics information through a Web browser. If you enable the Web console, you can define a username and password to restrict access. For security reasons, this should not be an existing NDS username or password. 7 If you want to use the Web console, enter a username and password (if desired) > click Next to display the Language dialog box. or If you don’t want to use the Web console, deselect the check box to turn off the option > click Next to display the Language dialog box.
Updating Your GroupWise System 187
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If multiple languages are displayed, you can install one or more of the languages. By default, the MTA will start in the language selected for the domain. If that language has not been installed, the MTA will start in the language used by the operating system. If that language has not been installed, the MTA will start in English. 8 Select the languages you want to install > click Next to display the Domains / Post Offices dialog box.
188 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
To simplify the process of loading the MTA, the Agent Installation program uses the domain information you enter in the Domains / Post Offices dialog box to create an MTA startup file. The startup file includes a required switch (/home-path) that points to the domain directory. The Agent Installation program also creates a GRPWISE.NCF file on NetWare or a Startup menu shortcut on Windows NT/2000. The NCF file or shortcut includes the command to load the MTA using the MTA startup file. 9 To specify the location of your domain, click Add > enter the domain name > enter the path to the domain directory > make sure the HTTP port is unique (if you’ve enabled the Web console) > click OK to add the domain to the list. In addition to the MTA, the POA is automatically installed to the installation directory. If you plan to run the POA on the same machine as the MTA, specify the location of the post office (or post offices) the POA will service. The Agent Installation program creates a POA startup file with a /home switch that points to the post office directory. It then includes the command to load the POA in the GRPWISE.NCF file on NetWare or in a Startup menu shortcut on Windows NT/2000. 10 Click Next. If you are installing the NLMTM MTA or the Windows NT/ 2000 MTA as a regular Windows application (not as a Windows service), the Summary dialog box is displayed. Skip to Step 12. or If you are installing the Windows NT/2000 MTA as a Windows service, the NT Service Information dialog box is displayed.
Updating Your GroupWise System 189
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
The MTA requires a user account that provides access to the domain directory. ! If the domain directory is on the Windows NT/2000 machine, you can use the local system user account to provide the access; the Use Local System Account option is available only if the domain directory is on the current machine. ! If the domain directory is on another Windows NT/2000 machine, you need to specify a Windows user account that provides access to that machine. ! If the domain directory is on a NetWare server, you need to specify a username and password that is valid as both a Windows user account and an NDS user account. If you are also planning to run the POA on this machine, the user account you specify must also provide access to the post office directory. 11 Provide the appropriate user account information > click Next to display the Summary dialog box.
190 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
12 Click Install to install the agent files. After the files are installed, the Agent Installation program creates the MTA startup file and the GRPWISE.NCF file (NetWare) or Startup menu shortcut (Windows NT/2000). MTA startup file: If an MTA startup file already exists, the Agent Installation program renames the file with a .MT1 extension. For example, an existing PROVO.MTA file would be renamed to PROVO.MT1 before the new PROVO.MTA file is created. If you’ve made modifications to the existing MTA file, you may want to use it instead of the new MTA file. The same is true for the POA (if you defined a post office in the Domains / Post Office dialog box). GRPWISE.NCF file (NetWare only): If a GRPWISE.NCF file already exists, the Agent Installation program gives you the option of 1) overwriting the existing GRPWISE.NCF file, 2) appending the new MTA load commands to the existing GRPWISE.NCF file, or 3) creating a new file named GRPWIS1.NCF. If you have modified the existing GRPWISE.NCF file and want to save the modifications, you should append to the existing file or create a new GRPWIS1.NCF file. If you append to the file, make sure you review it later to ensure that it includes only the commands you want. Shortcut: If a shortcut already exists on the Start menu (Start > Programs > GroupWise Agents), the Agent Installation program replaces the shortcut with the new shortcut.
Updating Your GroupWise System 191
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
After the startup file and GRPWISE.NCF file or Windows shortcut have been created, the Installation Complete dialog box is displayed.
13 Select from the following options: Update AUTOEXEC File: Select this option to reference the GRPWISE.NCF file from the server's AUTOEXEC.NCF file so that the MTA loads automatically whenever the server starts. If you specified a post office in the Domains / Post Offices dialog box (Step 9), the POA is also loaded. This option does not apply to Windows NT/2000. Delete Obsolete GWADA Files and References to GWADA: The ADA is no longer necessary and should not be used with the GroupWise 6 MTA. Select this option to delete the ADA program and startup files. Launch GroupWise Agents Now: Select this option to start the MTA. Once you start the MTA, it updates the domain database to version 6. You can verify that the database version has been updated by viewing the Domain object’s Identification page in ConsoleOneTM. If you specified a post office in the Domains / Post Offices dialog box (Step 9), the POA is also started. After the domain database is updated, the POA will update the post office database. You can view the Post Office object’s Identification page in ConsoleOne to verify that the database version has been updated. If for some reason it has not been updated, restart the POA. 14 Click Finish to perform the selected options.
192 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
15 To update post offices in the domain, continue with “Updating Post Offices” on page 193. or To update other domains, skip to “Updating Secondary Domains” on page 198.
Updating Post Offices
To update a post office, you need to install the GroupWise 6 POA and run it against the post office. The POA uses the new post office dictionary file (GWPO.DC) to update the post office database to version 6. Once you’ve installed the POA, you may also need to copy the new GroupWise client views from the software distribution directory to the post office directory. ! “Installing and Starting the POA” on page 193 ! “Copying the GroupWise Views to the Post Office Directory” on page 194
Installing and Starting the POA The POA cannot be running while you update it. Users who connect to the post office via client/server (TCP/IP) will not be able to access the post office while the POA is shut down. However, users who connect to the post office via direct access (mapped drive or UNC path) can continue to access the post office. To install and start the POA: 1 To install the POA to a NetWare server, start the GroupWise Agent Installation program (INSTALL.EXE) from a Windows 95/98/NT/2000 workstation that has access to the server. or To install the POA to a Windows NT/2000 machine, start the GroupWise Agent Installation program (INSTALL.EXE) from that machine. The INSTALL.EXE program is located in the AGENTS directory in the GroupWise 6 software distribution directory or on the GroupWise 6 CD.
Updating Your GroupWise System 193
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
2 Click Yes to accept the license agreement and display the Overview dialog box.
3 Follow the prompts to complete the installation and start the POA. The process for installing the POA is identical to installing the MTA. If you need information about any of the Installation Agent dialog boxes, refer to “Updating the Primary Domain” on page 183. 4 Continue with the next section, “Copying the GroupWise Views to the Post Office Directory” on page 194.
Copying the GroupWise Views to the Post Office Directory
GroupWise 6 includes new views for the GroupWise client. When the POA starts, it updates the post office database and also attempts to update the client views in the post office directory. To do so, it requires access to the software distribution directory. If it doesn’t have access, you will need to manually copy the views. You can check whether or not the POA was able to update the views by verifying the existence of the USML_PP.VEW and USML_PR.VEW files in the x:\po\OFVIEWS\WIN directory, where x:\po is the path to the post office directory.
194 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
If the USML_PP.VEW and USML_PR.VEW files do not exist, copy all files from z:\software\CLIENT\OFVIEWS\WIN to x:\po\OFVIEWS\WIN where z:\software is the path to the software distribution directory and x:\po is the path to the post office directory.
Updating Users' GroupWise Clients
After a post office is updated to version 6, users who have accounts on that post office can start using the GroupWise 6 client. The tasks you need to complete to update users depend on whether or not the users’ software distribution directory has been updated to GroupWise 6. ! “Users’ Software Distribution Directory Already Updated” on page 195 ! “Users’ Software Distribution Directory Requires Updating” on page 196
Users’ Software Distribution Directory Already Updated
If you updated the users' software distribution directory to version 6 during installation, the following will occur the next time users start the GroupWise client: ! Users who run the GroupWise client from the software distribution directory (a workstation installation) will be updated to version 6. ! Users who run the GroupWise client from their local drives (a standard installation) will not be updated automatically. You need to use the Software Directory Management feature in ConsoleOne to force Standard Install users to update. Follow the instructions under “Users’ Software Distribution Directory Requires Updating” on page 196, choosing the Force Auto-Update Check by GroupWise Component option when instructed.
Updating Your GroupWise System 195
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Users’ Software Distribution Directory Requires Updating
If the users’ software distribution directory has not been updated, you will need to use the new software distribution directory (or the GroupWise 6 CD) to update the users' old software distribution directory. Users will then be updated.
IMPORTANT: Before you update a software distribution directory, make sure all post offices that use the software distribution directory have been updated. The GroupWise 6 client cannot access a GroupWise 5.x post office. Users who update to the GroupWise 6 client before their post office has been updated will be locked out of the post office. Users cannot be running the GroupWise client from the software distribution directory while you are updating the software in it. Open files will not be updated. To update a GroupWise 5.x software distribution directory to GroupWise 6: 1 Make sure you have Read, Write, Create, Erase, Modify, and File Scan rights (or equivalent rights) in the GroupWise 6 software distribution directory and in the GroupWise 5.x software distribution directory you will be updating. If you still have access to the GroupWise 6 CD, you can use it instead of a GroupWise 6 software distribution directory. 2 In ConsoleOne, click Tools > GroupWise System Operations > Software Directory Management.
196 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
3 Select the GroupWise 5.x directory you want to update > click Update to display the Update Software Distribution Directory dialog box.
4 Click Update by Copying From. 5 Click Software Distribution Directory > select the GroupWise 6 software distribution directory. or If the GroupWise 6 software distribution directory is not listed, click Path > enter the path to the directory. You can also use this option to update the software directly from the GroupWise 6 CD.
The Force Auto-Update Check by GroupWise Components option is automatically selected. This causes the GroupWise client to check for a new version; if a new version is found, the client then prompts users to update the next time they start the client.
IMPORTANT: If the software distribution directory is already updated to version 6 and you are now trying to force Standard Install users to update to the GroupWise 6 client, you should select only the Force Auto-Update Check by GroupWise Components option. 6 Click OK to copy the files.
Updating Your GroupWise System 197
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
IMPORTANT: When you turn on auto-update (the Force Auto-Update Check by GroupWise Components option), a flag is set in each post office database. This flag instructs the GroupWise client to check for updated software. GroupWise clients using direct access mode (mapped or UNC path) read this new setting in the post office database and automatically check for updated software. However, GroupWise clients running in client/server mode do not access the post office database directly; instead, the Post Office Agent accesses the post office database for them. For the Post Office Agent to read the new auto-update setting, you need to restart the Post Office Agent. Only after the POA restarts will GroupWise clients running in client/server mode check for updated software.
Updating Secondary Domains
Once you've updated the primary domain, you can update any secondary domains in your system. To do so, follow the same process you used to update the primary domain, its post offices, and users.
Updating the GroupWise Internet Agent
Once you’ve updated your domains and post offices, you can update the Internet Agent. For information about update issues you should consider, see “Updating the GroupWise Internet Agent” on page 175. For information about installing GroupWise 6 Internet Agent, see Chapter 2, “Installing GroupWise Internet Agent,” on page 75.
Updating GroupWise WebAccess
Once you’ve updated your domains and post offices, you can update GroupWise WebAccess. For information about update issues you should consider, see “Updating GroupWise WebAccess” on page 175. For information about installing GroupWise 6 Internet Agent, see Chapter 3, “Installing GroupWise WebAccess,” on page 97.
198 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
III Appendixes
Appendix A, “Manually Creating the NDS Object for the Internet Agent,” on page 201 Appendix B, “What’s New in GroupWise 6,” on page 207 Appendix C, “GroupWise 5.x and 6 Compatibility Matrix,” on page 223
Appendixes 199
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
200 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Manually Creating the NDS Object for A the Internet Agent
If you need to, you can manually create an NDS® object for the GroupWise® Internet Agent in ConsoleOneTM. The object will be contained in the NDS directory tree structure under a GroupWise domain. To manually create the object, complete the tasks in the following sections: ! “Creating the Object” on page 201 ! “Defining Properties for the Object” on page 204
Creating the Object
To create an NDS object for the Internet Agent: 1 In ConsoleOne, right-click the GroupWise domain object where you installed the Internet Agent. 2 Click Object > Create > double-click GroupWise Gateway/Internet Agent.
Manually Creating the NDS Object for the Internet Agent 201
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
3 Select the Internet Agent radio button at the top of the page. 4 Fill in the fields: Internet Agent Name: Specify a name that identifies the Internet Agent and is unique within the domain. GWIA is commonly used, but you can use any name. This name and an accompanying GroupWise icon will appear together as an object in ConsoleOne or in the GroupWise View. Internet Agent Home Directory: Specify the name of the directory in the domain directory structure where the Internet Agent files have been installed. If you have already installed the Internet Agent software, select the directory name from the drop-down list box. Language: This field defaults to the language selected for the domain. If necessary, select the language from the drop-down list. The language will determine the sorting rules that will be used for the lists displayed in GroupWise, such as the Address Book list. Time Zone: The Internet Agent assumes the time zone of its domain as the default. If necessary, you can select a different time zone. Internet Mail Domain Name (stored as Foreign ID): In order to receive Internet e-mail, you should enter a mail domain name in the GroupWise Internet Agent configuration (normally done during installation). The mail domain name you enter in this field will be used as
202 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
the host portion of the sender's address on the From: line for outbound GroupWise e-mail messages (such as [email protected]). The mail domain name may or may not be the same as your Internet host name (the host name for the machine where you are installing the GroupWise Internet Agent that corresponds with that machine's IP address in its DNS "A record" entry). If your mail domain name is different than the Internet Agent machine's host name, it is listed as an MX record in the DNS table. Your Internet host name is what identifies you to other hosts on the Internet (such as mail.novell.com). The host name is associated with an IP address in a DNS "A record.” You obtain an IP address and a fully qualified host name from your Internet service provider (ISP). If you want to be known by more than one name (such as novell.com) you need to register the additional name with the ISP, and have the name listed as an MX record in the DNS table, where it points to the fully qualified host name. You can also enter a mail domain name at a later time through ConsoleOne in the Foreign ID field of the Internet Agent's Properties page. You can enter multiple names in the Foreign ID field of the Internet Agent's Properties page in ConsoleOne. The first name in the field will be the name you are known by on the Internet. After the first host name, any additional names will be used for inbound address resolution. Multiple domain names must be separated by a space. Version: Select version 6. Platform: Select NLM (NetWare Loadable Module) or Windows NT/ 2000 as appropriate. 5 Select Define Additional Properties to configure the Internet Agent properties after the NDS object is created. 6 Click Create.
Manually Creating the NDS Object for the Internet Agent 203
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Defining Properties for the Object
You define the Internet Agent object’s basic information by verifying and filling in the fields on the ConsoleOneTM Properties page shown below.
To define the properties on the Internet Agent Properties page: 1 If the Properties page is not already open, right-click the Internet Agent object > click Properties. 2 Click GroupWise > Identification to display the Identification page. 3 Check the Domain.Gateway field for the correct domain and gateway names. 4 Enter a brief description in the Description field (optional). For example, you could include the installation date, the machine name, or any other information. 5 Check the Database Version field. The version number should be 6. 6 As appropriate, select NLM or Windows NT/2000 in the Platform field (required).
204 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
7 Select Internet Agent as the Gateway Type. 8 Fill in the Gateway Alias Type field. You will need this name when you configure the aliases later. The acronym GWIA is commonly used. Aliases let you define addresses for users on third-party mail systems in your GroupWise Address Book. With aliases defined, your GroupWise users can select foreign mail system recipients from the GroupWise Address Book. 9 Fill in the Foreign ID field (required). The Foreign ID is also known as the Internet mail domain name in the GroupWise Internet Agent configuration (normally specified during installation). The mail domain name you enter in this field will be used as the host portion of the sender's address on the From: line for outbound GroupWise e-mail messages (such as [email protected]). The mail domain name may or may not be the same as your Internet host name (the host name for the machine where you are installing the GroupWise Internet Agent that corresponds with that machine's IP address in its DNS "A record" entry). If your mail domain name is different than the Internet Agent machine's host name, it is listed as an MX record in the DNS table. Your Internet host name is what identifies you to other hosts on the Internet (such as mail.novell.com). The host name is associated with an IP address in a DNS "A record." You obtain an IP address and a fully qualified host name from your Internet service provider (ISP). If you want to be known by more than one name, (such as novell.com) you need to register the name with the ISP, and have the name listed as an MX record in the DNS table, where it points to the fully qualified host name. You can also enter a mail domain name at a later time through ConsoleOne in the Foreign ID field of the Internet Agent's Information page. You can enter multiple names in the Foreign ID field of the Internet Agent's Properties page in ConsoleOne. The first name in the field will be the name by which you are known on the Internet. After the first host name, any additional names will be used for inbound address resolution. Multiple domain names must be separated by a space. 10 Provide the "get" community string for the machine where the Internet Agent will run. Community strings are case-sensitive. If access to Internet Agent information is unrestricted, the "get" community string would typically be PUBLIC.
Manually Creating the NDS Object for the Internet Agent 205
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
By providing the "get" community string, you enable the Internet Agent to receive SNMP requests. The community string information is stored in the domain database and can be discovered by network management and monitoring programs such as GroupWise Monitor. 11 If you are using an SNMP monitor (such as ManageWise®) that requires an IPXTM/SPX address to communicate SNMP information from the Internet Agent, click the edit icon next to the IPX/SPX Address field and manually enter this address > click OK. 12 Click OK to save the information.
206 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
B What’s New in GroupWise 6
This section lists enhancements and new features in the following components of GroupWise® 6: ! “GroupWise Administration” on page 207 ! “GroupWise Agents” on page 209 ! “GroupWise Client” on page 211 ! “GroupWise Internet Agent” on page 217 ! “GroupWise WebAccess” on page 219 ! “GroupWise Monitor” on page 220
GroupWise Administration
GroupWise 6 administration includes the following enhancements and new features. ! “Full ConsoleOne Administration” on page 208 ! “Smarter Backup and Restore” on page 208 ! “Disk Space Management for Mailboxes” on page 208 ! “Faster Mailbox/Library Maintenance” on page 208 ! “More Accessible GroupWise Check” on page 209 ! “More Efficient Move User” on page 209 For information about using new features, see the GroupWise 6 Administration guide at the Novell® Documentation Web site (http:// www.novell.com/documentation).
What’s New in GroupWise 6 207
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Full ConsoleOne Administration
All GroupWise administration is performed in ConsoleOneTM. After installing GroupWise 6 and using ConsoleOne to administer domains and post offices, do not perform subsequent GroupWise administration tasks on those domains and post offices with NetWare® Administrator.
Smarter Backup and Restore
Smart Purge is a new feature that integrates the use of the GroupWise Backup utility with related GroupWise features such as Purge, Archive, and Disk Space Management. Smart Purge ensures that GroupWise items will not be purged from the system prior to a backup process. Smart Purge relies on the GroupWise Target Service Agent (GWTSA) for executing a specialized backup process. After you have properly backed up your GroupWise data, you can set up a restore area so that users can restore items that have already been emptied from the Trash.
Disk Space Management for Mailboxes
As a GroupWise administrator, you can set new client options to control how much disk space users occupy for mailboxes. The new client Caching mode stores users' messages on their hard drives, thus conserving disk space on the server. In addition, the GroupWise 6 client displays for users how much disk space their mailboxes are using, and you can set maximum mailbox and message size limits for users.
Faster Mailbox/Library Maintenance
In GroupWise 6, the Mailbox/Library Maintenance utility in ConsoleOne has been optimized to improve performance. Previously, Mailbox/Library Maintenance was a single-threaded application limited to processing multiple tasks serially (one after the other). With the conversion to a multi-threaded application, Mailbox/Library Maintenance can now execute multiple tasks concurrently. You will see significant performance gains, especially when running Mailbox/Library Maintenance against a post office with large databases.
208 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
More Accessible GroupWise Check
GroupWise Check (GWCheck) is the standalone version of Mailbox/Library Maintenance that can be run for databases that are not located in the post office directory. By default, GWCheck is now installed along with the client software so users can check GroupWise databases located on their hard drives. Users will have local databases if they are using the new Caching mode, if they have a Remote mailbox, or if their archive databases are stored locally. You can configure the client installation to add a Repair Mailbox item to the GroupWise client Tools menu to make mailbox repair very easy for client users.
More Efficient Move User
Moving users from one post office to another has been enhanced to increase performance and reliability. In the new method, called a live move, message files are no longer transferred. Instead, a client/server thread is used to communicate information between the post offices. A live move makes use of a unique identifier called a GUID, which is associated with each user. Because of this additional identifier, rules, remote settings, and replies to moved users function properly after the move is completed.
GroupWise Agents
The GroupWise 6 NLMTM and Windows* NT*/2000 agents include the enhancements and new features listed below: ! “Optimization for NetWare Cluster Services” on page 210 ! “More Powerful Agent Web Consoles” on page 210 ! “Faster Message Transfer Protocol” on page 210 ! “Mailbox Size Monitoring and Enforcement” on page 210 ! “Message Size Restriction” on page 210 ! “Disk Space Management for Post Offices” on page 210 For information about using new features, see "Post Office Agent" and "Message Transfer Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
What’s New in GroupWise 6 209
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Optimization for NetWare Cluster Services
The GroupWise 6 POA and the MTA have been optimized for use with NetWare® Cluster ServicesTM to provide enhanced failover and failback capabilities.
More Powerful Agent Web Consoles The GroupWise 6 agent Web consoles provide detailed thread status and message queue information. In addition, you can modify some agent settings from the agent Web consoles.
Faster Message Transfer Protocol
GroupWise 6 Message Transfer Protocol (MTP) provides substantially faster throughput when post offices are located across slow links from domains.
Mailbox Size Monitoring and Enforcement
The GroupWise 6 POA monitors each user's mailbox size on a regular basis. The mailbox size information is then displayed in the GroupWise 6 client so users are aware of how much disk space their mailboxes occupy. In addition, the POA can enforce maximum mailbox size.
Message Size Restriction
The GroupWise 6 POA can prevent messages larger than a specified size from being sent outside the post office.
Disk Space Management for Post Offices
The GroupWise 6 POA can stop receiving and processing messages if disk space in the post office becomes too limited.
210 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise Client
The GroupWise 6 client for Windows includes the enhancements and new features listed below: ! “NNTP Newsgroup Accounts” on page 211 ! “POP3/IMAP4 Account Import” on page 212 ! “Multiple Account Signatures” on page 212 ! “Client Caching Mode” on page 212 ! “Mailbox Mode Switching” on page 212 ! “Disk Space Management for Client Users’ Mailboxes” on page 212 ! “Backup and Restore to Retrieve Deleted Items” on page 213 ! “More Secure Messaging” on page 213 ! “Calendar Printing Enhancements” on page 214 ! “Remote Mode Enhancements” on page 215 ! “Address Book Enhancements” on page 215 ! “Improved Notification” on page 216 ! “Improved Rules” on page 216 ! “Improved Forwarding” on page 217 ! “New Send, Accept, Decline, Forward, and Reply Buttons” on page 217 ! “Windows Time Zone Setting” on page 217 ! “More Flexible Browser Functionality” on page 217 For information about using new features, from the GroupWise client for Windows, click Help > Help Topics > Contents.
NNTP Newsgroup Accounts
Users can set up newsgroup accounts by selecting Account Options on the Accounts menu. An NNTP folder is added to the folder list for each account.
What’s New in GroupWise 6 211
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
POP3/IMAP4 Account Import
Users can import addresses and account information from the following supported POP3/IMAP4 accounts: Outlook Express 4.x and 5.x and Netscape Communicator* 4.0x, 4.6x, and 4.7x.
Multiple Account Signatures Users can specify a different signature for each account they use. For example, a user could have one signature for a newsgroup account and a different signature for a POP3 or IMAP4 account.
Client Caching Mode
A new mode of running the client, called Caching mode, is provided to enable users to work from their hard drives without being continuously connected to the network. Users do not need to set up connections or be prompted when they want to connect; this happens automatically. In Caching mode, overall client performance is greatly increased. However, everything is stored on the user's hard drive, so each user's available disk space needs to be considered before selecting this mode.
Mailbox Mode Switching
Users can select from a drop-down list on the toolbar to switch to a different mode of running GroupWise. The mailbox modes are: Online, Caching, and Remote. Depending on the mode the user is switching from, the user may be prompted to restart GroupWise before the mode will take effect. The system administrator can force users to use Caching mode only, and can also disable Remote mode.
Disk Space Management for Client Users’ Mailboxes The system administrator can set a send size limit on items. If a user sends an item that exceeds this size, a message displays saying that the item is too large and cannot be sent.
212 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
In addition, system administrators can set a mailbox size limit. At the bottom of the main GroupWise client window, in Online mode, a Mailbox Size status indicates how much disk space the user is using. As users approach the limit, messages warn them that their disk space is running out. When the limit is met, users cannot send messages until they delete or archive items. Messages in shared folders are only counted as disk space for the owner of the shared folder. A new menu item called Delete and Empty has been added to the Edit menu. This option deletes and purges selected items without sending them to the Trash, which allows users to quickly clean up their disk space.
Backup and Restore to Retrieve Deleted Items If the system administrator has created a restore area and has backed up the entire GroupWise system, the user can open a backup copy of his or her mailbox in the restore area to find missing items by selecting Open Backup on the File menu. The user needs to have Read and Write access to the restore area. In the backup copy of his or her mailbox, the user has partial functionality to access items, including Read, Search, and Undelete. Users can selectively restore any items from the backed-up mailbox, with the exception of documents. For more information, in the GroupWise 6 client, click File > Open Backup > press F1.
More Secure Messaging The following enhancements have been made for S/MIME secure messages: ! Security warning messages contain more detailed information; warnings display in color so that the user will immediately see them. ! The certificate view uses terminology and categories that are similar to the Novell Certificate ServerTM. ! The certification path view gives the entire certificate chain, displayed in its correct hierarchy. ! When a user opens a signed item, the user certificate associated with the item is checked against the Certificate Revocation List repository of the issuer. If the item was signed after a certificate was revoked, the user receives a security warning message.
What’s New in GroupWise 6 213
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
! The certificate list browser displays root Certificate Authorities and sub- Certificate Authorities. Users can select separate certificates for signing and encrypting an item. ! Users can select different trust options for individual Certificate Authorities. ! Additional options on the Advanced Option dialog box give the user more control over what a signed or encrypted item will contain. ! A user's S/MIME capabilities and preferences are stored locally. ! Features have been added for greater S/MIME Version 2 and S/MIME Version 3 compliance. ! Any Cryptographic Service Provider (CSP) compatible with the Microsoft* Base or Enhanced Cryptographic Provider is now supported. ! Ability to import and export public certificates in DER or Base64 format has been included. ! Administrative locking of signature, encryption, encryption algorithm, and key size settings is now available.
Calendar Printing Enhancements
Users can now perform the following: ! Print calendars to a file in an HTML table format ! Print calendars from the Archive ! Preview and print colored RTF text in calendars ! Use Print Preview to show different form and paper sizes ! Print calendars with Show Appointment As information (shading that shows availability) ! Change the order in the Multi-User Setup checklist ! Turn shading on and off in the print forms that support shading ! Turn separator lines on and off between data items
214 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Remote Mode Enhancements
The following features are new in GroupWise Remote: ! Archive ! Ability to change the main GroupWise password ! Notify can notify users of newly downloaded messages ! Backup functionality is available The following enhancements have been added: ! Improved address resolution ! Warning of unsent items when you exit GroupWise ! Increased performance
Address Book Enhancements
Information About Users Users can find detailed information about other users without needing to look them up in the Address Book. This is called Quick Info. Position the mouse pointer over any name in the To, CC, BC, or From boxes of a message and all the information for that person displays. You can turn Quick Info on or off.
NDS Roles and Groups Users can select NDS® roles and groups from the Address Book and send items to them.
Shared Address Book Columns Users can arrange their address book columns differently from the way the columns are arranged by the owner of the shared address book.
Company Information Company Name displays in both the Name and Organization fields. Company Phone Number displays in the Office Phone Number field.
What’s New in GroupWise 6 215
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
LDAP Address Book Enhancements ! The last query results list is maintained between sessions and between switching to different address books. ! Users can stop a query before it has finished. ! LDAP version 3 and SSL are supported.
Printing Enhancements From the Address Book, you can print address labels, lists of users, and selected fields from individual users' personal information.
New Filter A Begins With filter has been added.
New Buttons Previous/Next buttons have been added in the Address Book information dialog box.
Improved Notification
The following enhancements have been made: ! Notify can be automatically started when GroupWise starts. ! Alarms can be sent to a pager. ! Users can select the amount of snooze time when an alarm goes off. ! A Close All button is available when a user has several notifications. ! Notify is available in Remote and Caching modes.
Improved Rules ! When users create a vacation rule to reply to incoming items, Reply to All is disabled to avoid mass messages being sent when the rule is activated. ! Reply rules can now handle different Accept levels.
216 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Improved Forwarding
You can now forward an item without embedding it as an attachment. You can also select several items and forward them all at once.
New Send, Accept, Decline, Forward, and Reply Buttons
Menus have been added to these buttons with additional options.
Windows Time Zone Setting
When creating and displaying appointments, messages, and so forth, GroupWise now uses the Windows time zone setting of the local machine, rather than the time zone of the POA. This allows users located in different time zones to be on the same post office and still have their appointments displayed correctly for their local time zone. When users use Proxy to manage someone else's Mailbox or Calendar, appointments will display in the Calendar according to the proxy's time zone. (This is the opposite of how appointments were displayed when using Proxy in previous versions of GroupWise.)
More Flexible Browser Functionality
Users have the option to launch a new browser instead of having the page display in a browser window that is already open.
GroupWise Internet Agent
The GroupWise 6 Internet Agent includes the enhancements and new features listed below: ! “ESMTP Support” on page 218 ! “Secure POP and IMAP” on page 218 ! “Improved Access Control” on page 218 ! “Improved IMAP Compliance” on page 218 ! “Consistent Agent Engine” on page 218 ! “Consistent Windows Interface” on page 218 ! “NT/2000 Service Functionality” on page 218
What’s New in GroupWise 6 217
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
For information about using new features, see "Internet Agent" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
ESMTP Support
The GroupWise 6 Internet Agent supports ESMTP, including message size restrictions (SIZE), delivery status notifications (DSN), and SSL/TLS support in SMTP (STARTTLS).
Secure POP and IMAP
The GroupWise 6 Internet Agent includes SSL support in both POP3 and IMAP4 to allow secure connections.
Improved Access Control
The GroupWise 6 Internet Agent offers access control, which provides improved control of spamming and relaying problems. To reduce the risk of being used as a relay host, the Internet Agent reads the Mail From address and verifies that it actually corresponds to the sending host or e-mail client.
Improved IMAP Compliance
The GroupWise 6 Internet Agent conforms more fully to the IMAP specification.
Consistent Agent Engine
The GroupWise 6 Internet Agent uses the same agent engine as the POA and MTA.
Consistent Windows Interface The GroupWise 6 NT/2000 Internet Agent has a Windows interface similar to the NT/2000 POA and MTA.
NT/2000 Service Functionality The GroupWise 6 NT/2000 Internet Agent can run as an NT/2000 service.
218 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise WebAccess
GroupWise 6 WebAccess includes the enhancements and new features listed below: ! “Wireless Device Support” on page 219 ! “SNMP Support” on page 219 ! “Windows Service Support” on page 219 ! “NetWare Cluster Support” on page 219 ! “Improved Installation and More NDS Administration” on page 220 ! “WebAccess Client Features Added” on page 220 For information about using new features, see "WebAccess" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http://www.novell.com/documentation).
Wireless Device Support
GroupWise 6 WebAccess supports access to GroupWise Mailboxes through WAP-enabled wireless devices with microbrowsers that support HDML or WML. This includes wireless telephones and wireless PDA devices such as Windows CE, PocketPC, and AvantGo.
SNMP Support
The WebAccess Agent now includes support for SNMP so that you can monitor it through an SNMP management program.
Windows Service Support
The Windows NT/2000 WebAccess Agent can be run as a normal Windows application or as a Windows service. .
NetWare Cluster Support
The WebAccess Agent has been optimized for use with NetWare Cluster Services to provide enhanced failover and failback capabilities.
What’s New in GroupWise 6 219
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Improved Installation and More NDS Administration
The improved Installation program makes it easier to install or update the GroupWise WebAccess components.
Administration is now performed through ConsoleOneTM. In addition, new NDS objects have been added to represent the WebAccess Application (previously called the WebAccess Servlet), the WebPublisher Application (previously called the WebPublisher Servlet), and the Novell Speller Application (previously called the Novell Spell Check Server). NDS objects have also been added to represent the GroupWise WebAccess providers so that they can now be configured through NDS rather than through the WebAccess and WebPublisher configuration files.
WebAccess Client Features Added
The GroupWise WebAccess user interface (Web pages) has been refreshed and improved. With WebAccess, users can now do the following (in addition to what they could previously do): ! Mark items to be read later ! Add a signature to items ! Set WebAccess to the time zone they are in so that information that relies on dates and times will be based on their location rather than their post office’s location ! Share folders with other users, add items to shared folders, and post messages to shared folders ! Enable or disable existing rules; create new rules to delete, forward, move to a folder, reply to, or indicate vacation; delete rules. ! Create, delete, and modify personal address books ! Search on all available Address Book fields
GroupWise Monitor
The GroupWise 6 Monitor is fast and easy to use. The Monitor Agent watches other GroupWise agents (POA, MTA, Internet Agent, and WebAccess Agent), gathers information about their status, and displays the information at the Monitor Agent console of the machine where it is installed. The Monitor Application passes the gathered information to your Web browser for display in the Monitor Web console at any location where an Internet connection and a Web browser are available.
220 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise 6 Monitor includes the following capabilities not available in earlier versions of GroupWise Monitor: ! “Link Trace” on page 221 ! “Link Check” on page 221 ! “System Performance Testing” on page 221 ! “Environment Report” on page 222 ! “User Traffic Report” on page 222 ! “Link Traffic Report” on page 222 ! “Message Tracking Report” on page 222 For information about using new features, see "Monitor" in the GroupWise 6 Administration guide at the Novell Documentation Web site (http:// www.novell.com/documentation).
Link Trace
The Link Trace feature lets you follow the path a message would take between two GroupWise domains. If a message fails to arrive at its destination, this feature helps you pinpoint its current location, so you can resolve the problem and get messages flowing smoothly again.
Link Check
The Link Check feature lists the links from one or more GroupWise domains to all other domains in your GroupWise system. This helps you identify inefficient link paths, loops, and unreachable domains.
System Performance Testing
The System Performance Testing feature lets you send performance test messages from a specially configured Monitor domain to target domains anywhere in your GroupWise system. The Monitor Agent measures the amount of time it takes for replies to return from the target domains, which lets you ascertain the speed at which messages flow through your GroupWise system.
What’s New in GroupWise 6 221
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
Environment Report
An environment report lists all monitored agents, along with each agent's version, IP address, port number, and operating system information. You can send the environment report to any e-mail user, which can be helpful when getting assistance from Novell Technical ServicesSM.
User Traffic Report
A user traffic report enables you to determine how many messages a user has sent. The user traffic report lists all messages sent by a specified user during a specified date/time range, along with date, time, and size information for each message.
Link Traffic Report
A link traffic report enables you to determine how many messages are passing from a selected GroupWise domain across a specified link. The link traffic report lists the total number and total size of all messages passing through the link during each hour or half hour of operation.
Message Tracking Report
A message tracking report enables you to track an individual message through your GroupWise system. The message tracking report provides information about when a message was sent, what queues the message has passed through, and how long it spent in each message queue. If the message has not been delivered, the message tracking report shows where it is.
222 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GroupWise 5.x and 6 Compatibility C Matrix
Use the chart below to determine the compatibilty of GroupWise® 5.x (5, 5.1, 5.2, 5.5, and 5.5 Enhancement Pack) and 6 components. The left-hand column lists the GroupWise 5.x components, while the GroupWise 6 components are listed across the top row. To read the chart, locate the GroupWise 5.x component you want and read across the row until it intersects the column that contains the GroupWise 6 component you want. Example 1: To see if you can use the GroupWise 5.1 client in client/server mode against a GroupWise 6 POA, locate Client - C/S in the first column, then read across the row to the POA column. The cell contains an S, which means the configuration is supported. Example 2: To see if you can use GroupWise 5.5 Administrator to administer a GroupWise 6 domain, locate NWAdmin in the first column, then read across the row to the DPO column. The cell contains an NS, which means the configuration is not supported. Example 3: To see if you can use the GroupWise 6 POA in the same domain as the GroupWise 5.2 MTA, locate MTA in the first column, then read across the row to the POA column. The cell contains an NS, which means the configuration is not supported. On the other hand, GroupWise does support the use of a GroupWise 5.2 POA in the same domain as the GroupWise 6 MTA.
GroupWise 5.x and 6 Compatibility Matrix 223
Installation 104-001381-001 May 11, 2001 Novell Confidential Manual Rev 99a30 4 December 00
GROUPWISE 6
DPO CO MTA POA IA WA Client - D Client - C/S Client - R
DPO NA S S S NS NS NS NA NA
NWAdmin NS NA NS NS NS NS NA NA NA G R MTA NS S S NS NS NS NA NA NA O U ADA NS S NS NS NA NA NA NA NA P W POA NS S S NA NS NS NS NS NS I IA S S S S S NA NA NA NA S E WA NS* S NS* NS* NA S** NA NA NA 5 x Client - D S NA NA NA NA NA NA NA NA Client - C/S NA NA NA S NA NA NA NA NA
Client - R NA NA NA S NA NA NA NA NA
* The GroupWise 5.5 Enhancement Pack SP3 (and higher) WebAccess Agent can access GroupWise 6 domains and post offices; all other GroupWise 5.x WebAccess Agents cannot. ** Some 5.x and 6 WebAccess components can function together. For information, see “Updating GroupWise WebAccess” on page 175. KEY
DPO = Domains and Post Offices CO = ConsoleOne NWAdmin = NetWare Administrator IA = Internet Agent MTA = Message Transfer Agent WA = WebAccess Agent POA = Post Office Agent Client - D = GroupWise client using direct access to post office directory ADA = Administration Agent Client - C/S = GroupWise client using client/server (TCP/IP) access to POA NA = Not Applicable Client - Remote = GroupWise client in Remote mode S = Supported NS = Not Supported
224 Installation
Installation 104-001381-001 May 11, 2001 Novell Confidential