- Architecture
- A GroupWise system consists of one or more domains.
A domain consists of one or more post offices.
A post office contains user mailboxes and objects.
When creating an account, you must specify a domain and post office that the account will reside in.
NDS assigns a FID (File ID) to each user account.
- File ID - randomly generated three-character alphanumeric number that is associated with the user's account.
Types of user accounts:- NDS user with GroupWise account.
- External entity - GroupWise user that does not have an NDS account. Typically used with users who only need email, and not network access.
- Nickname - Identifies the roll or job of a user. My account is RYANS. My nickname is WEBMASTER. All email going to the WEBMASTER nickname will automatically be forwarded to the RYANS account.
- Distribution list - Mail account containing a number of users that can be addressed together.
- Public - created in NDS and stored in the public GW address book.
- Personal - created by a user and stored in the user's personal GW address book.
- Resource - Physical object requiring scheduling. A meeting room can be setup with an account. Other users can schedule times through GW to use this room.
- An owner must be assigned to the resource. The owner must be in the same post office as the resource. The owner approves/denies scheduling requests.
- Library - Compilation of documents stored in GW databases.
- File ID - randomly generated three-character alphanumeric number that is associated with the user's account.
- Domain
- A domain manages routing information to other domains and locations.
A GW system must contain at least one domain.
Domains are administered via NWAdmin.
GW directory store:
- WPDOMAIN.DB - Domain database that contains addressing information for objects within the domain, configurations and routing information for the domain's MTA. Serves as a replication point for updates.
GroupWise has a separate directory store from NDS. NDS synchronizes with the directory store.
- POA - Post Office Agent
- The POA performs the following:
- Delivers messages to other accounts within the same PO.
- Checks the MTA output folder for incoming messages.
- Delivers status messages within the same PO.
- Indexes library objects.
- Manages message store databases.
The POA agent can be run on:
- NetWare
- Windows NT
- OS/2
- UNIX
- MTA - Message Transfer Agent
- The MTA performs the following:
- Transfers all messages that are addressed to other accounts outside of the sending user's PO.
- Transfers administrative messages to ADAs.
- Sends and receives messages through gateways.
The MTA agent can be run on:
- NetWare
- Windows NT
- UNIX
- ADA - Administrative Agent
- The ADA works with NWAdmin to process and replicate administrative messages, update PO and domain databases, and synchronize NDS information with WPDOMAIN.DB and WPHOST.DB databases.
NWAdmin sends administrative messages to the ADA. The ADA then replicates these messages and updates the directory store.
The ADA updates the GW address book..
The ADA agent can be run on:
- NetWare
- Windows NT
- UNIX
- Stores
- The message store contains all messages for a GroupWise system.
The directory store is a distributed database containing contact information for all users, commonly accessed through the GW address book. The ADA processes all updates for this information, known as directory synchronization.
The document store contains all documents for GroupWise libraries.
- Installation and Configuration
- GroupWise 5 requires NetWare 4.1 and at least one workstation to administer the system.
By running the install program, NDS will be checked to verify if the schema has been extended to include GW information, and will automatically extend it if it has not been performed already.
You must install the GW plug-in to NWAdmin. This is located on the CD or domain directory - X:/GWSOFT/ADMIN/GWSETUP.EXE. Installing this plug-in will add enhancements to the version of NWAdmin used by the workstation to allow it to administer GW.
The administrative workstation must be running NetWare Client 32.
X:/GWSOFT/CLIENT/ will contain the Client16 and Client32 installation files. You will just need to run SETUP.EXE out of either directory to install the GW client.
X:/GWSOFT/AGENTS/ contains agent files for programs such as the GW Monitor that works in conjunction with ManageWise.
The PO name can contain up to 32 characters and can contain one or more words. Once a PO has been named, it cannot be changed.
The GRPWISE.NCF file contains load statements to load the ADA, MTA, and POA.
- ADA - LOAD GWADA.NLM @ domainname.ADA
- MTA - LOAD GWMTA.NLM @ domainname.MTA
- POA - LOAD GWPOA.NLM @ postofficename.POA
The ADA and MTA files have a required parameter that must be configured:
- /home-\\servername\domaindirectoryname
The POA file has a required parameter that must be configured:
- /home-\\servername\postofficedirectoryname
Parameters entered in the startup file or entered at the command line will override settings for the object in NDS.
Parameter changes made from the agent screen will be good only for that session, and will be reset once the agent restarts.
- Access Methods
- Access methods:
- Client-Server - Uses POA only for delivering messages. Communicates with POA via TCP/IP.
- Direct - Directly accesses PO directories for delivering messages. Requires that the user have proper access rights to the proper PO directories.
For direct access, users must have [RWCE_F] rights to all PO directories except X:\WPCSOUT\ADS\. Users also must have a mapped connection to the PO directory.
When using client-server access, the workstation must be configured with a TCP/IP address, and must be able to communicate properly with the server. Once the client has been installed, check to make sure you can ping the IP address of the server to ensure proper communications.
Direct access options:
- Agent Always - This allows the client to write to the WPCSOUT\OFS directory instead of directly to the databases. The POA will then deliver the message to the proper destination. This allows an added level of security, so that you will not have to give users certain rights to the database directories. You will need to grant users the following rights when using Agent Always with direct access:
- OFUSER - [R]
- OFMSG - [R]
- OFUSER - [R]
- Use App Threshold - Tells the client to deliver the message when the POA is busy. Sets a number that tells the client to deliver when the database updates are less then or equal to the number specified, and the POA to deliver when the number is more than the number specified. This option is set by default.
- Client Delivers Locally - The client always delivers all messages. The POA never handles the messages.
With client-server, you can proxy with users in another PO. With direct access, you can only proxy with users in the same PO.
- Client-Server - Uses POA only for delivering messages. Communicates with POA via TCP/IP.
- Message Store
- The message store is a logical point for storage of messages within the system.
Messages are broken into three sections:
- Header - Contains addressing information, priority, status and pointer to body.
- Body - Contains message text. Also contains attachments that are under 2KB.
- Attachments - Files attached to message that are larger than 2KB. Also contains body message text if it is larger than 2KB.
Message store directories:
Where each section is contained:
- Header - contained in OFUSER directory.
- Body - contained in OFMSG directory.
- Attachments - contained in OFFILES directory.
OFMSG directory holds message databases that contain the text of each message. This directory can hold up to 25 databases.
- A pointer to the message is placed in the sender and receivers' databases.
- Only one copy of each message will be stored in each PO.
- A message is deleted only after all of the pointers in the sender's and receivers' mailboxes have been deleted.
OFUSER directory holds user databases that contain the header information of each message.
Two types of databases are stored here:
- User - Database for the specific user. Named USERxxx.DB (xxx = the user's FID).
- Prime User - Database for PO. Stores shared folders created by users from another PO. Only stores header information; message text is stored normally in the OFMSG directory.
OFFILES directory holds file attachments larger than 2KB.
- Pointers to these attachments are stored with the body.
- Messages can include up to 99 attachments.
- Attachment files are randomly placed in subdirectories.
With client-server access, the POA handles moving all message sections to the different directories.
With direct access, the POA and client work together to move message sections to their proper directories.
- MTA Input and Output directories
-
The WPCSIN directory contains messages coming into the MTA to be delivered elsewhere. The PO places outgoing files into the WPCSIN directory.
The WPCSOUT directory contains messages that have been moved by the MTA. The PO scans this directory for new files and delivers them accordingly.
These directories are relative to the MTA, not the PO.
Each WPCSIN and WPCSOUT directory contains priority subdirectories.
- Guardian Database
- NGWGUARD.DB is the guardian database for each PO.
This database functions as a single reference point for all PO databases. For example, this database will reference where other databases store certain headers or messages.
NGWGUARD.DC is the guardian dictionary file, which is used as a template to build the any of the following databases:
- MSG<00-24>.DB
- USERxxx.DB
- PUxxxxx.DB
- NGWGUARD.DB
- DM*.DB
This file contains various schema information, such as user and message database information.
- Files
-
- WPDOMAIN.DB - Domain database containing routing and addressing information that serves as a replication point.
- WPHOST.DB - Post Office database that serves as a replication point.
- NGWGUARD.DB - Guardian database file. Reference for all other PO databases.
- NGWGUARD.DC - Template for building NGWGUARD.DB.
- MSG<00-24>.DB - Message database files.
- USERxxx.DB - User database files.
- Puxxxxx.DB - Prime user database files.
- DM*.DB - Document Management files.
- Security
- Mailbox security:
- User password - Password defined in the user's NDS account.
- Administrator security level setting - Level set in the PO, as defined in the PO settings in NWAdmin.
- Low - Can access any mailbox.
- High - User and Network login IDs have to match to gain access.
When deleting a NetWare user that has a GW account, you will be prompted with the following options:
- Expire GW Account - Deletes the user's NDS account, and expires the GW account.
- Delete GW Account - Deletes both the user's NDS account and GW account.
- Only Delete NDS Account - Deletes the user's NDS account, but the user's GW account remains active.
- Proxy
- The proxy feature allows a user to manage another user's mailbox and calendar. The user can read, accept and decline messages for the other user.
You can proxy in the same PO using either access method. Proxying with two accounts in different PO's requires client-server access.
- Administrative Tasks
- When you rename a user's mailbox, nothing will happen to the user account. This will affect other accounts that may have items mapped to this account, such as proxy access, distribution lists, personal groups, etc.
When moving a user's mailbox within the same domain:
- 1. User information is changed in the WPDOMAIN.DB and WPHOST.DB files.
2. User database information is transferred to the user's new PO.
3. User messages are transferred to the user's new PO directories.
- Database Maintenance
- Mailbox/Library maintenance options are used to maintain message store databases. Message database problems result in user problems with sending and receiving messages.
Mailbox/Library maintenance options:
- Structure - Checks database integrity.
- Index - Checks index
- Contents - Checks for existence of messages.
- Acquires statistics from user databases.
- Fix problems - Fix problems that are found.
- Reduce Only - Reclaims disk space.
- Expire and Reduce - Expires messages older than age specified.
- Summary Statistics - Display basic user statistics
- Complete Statistics - Displays thorough user statistics.
Analyze/Fix Databases Expire/Reduce Messages Mailbox Statistics Reset Client Options Resets options set by user within the client. Recreate User Database Recreates a deleted database. Structural Rebuild Reconstructs a user database. System maintenance options are used to maintain directory store databases.
System maintenance options:
Validate Database Verifies database integrity. Recover Database Corrects inconsitencies, but not information. Can be run while database is in use. Rebuild Database Corrects inconsitencies and information. Must have exclusive access to database. Rebuilds database using information from parent domain. Recliam Unused Space Reclaims unused space in database. Rebuild Indexes for Listing Rebuilds indexes for address book. You must ensure that the NWGUARD.DB, WPDOMAIN.DB, WPHOST.DB and message and user databases are backed up regularly.
- Scheduled Events
- Events can be scheduled for POA and ADA agents, but not the MTA.
POA:
- Check for PO database corruption, and repair if found.
- Index documents.
- Check disk space usage.
ADA:
- Suspend ADA for periods of time. Used when performing backups.
- Automatically synchronize information from NDS with WPDOMAIN.DB.
- Document Management
- A library must be created before a user can use document management services.
- BLOB (Binary Large Object files) - files where documents are stored.
Document properties are kept in library database files in the PO directory (DMDDxxxx.DB).
Document properties:
- Maximum revisions - Number of times the document can be revised.
- Retention time - Amount of time the document will stay in the document store.
- Disposition - Determines what happens to the document when it expires. Can be archived or deleted.
- DMSH.DB - Shared document services database that holds a list of all libraries and lookup tables for those libraries.
- DMDLxxxx.DB - Contains document logging information.
- DMSDxxxx.DB - Contains library system data.
- DMDDxxxx.DB - Contains library document data.
Library public rights:
Add User can add documents to the library. Change User can modify documents in the library. Delete User can delete documents in the library; must have view right to perform this. View Can view or copy documents, but not modify. Designate Official Version User can make a document the official version. The official version is the version of the document located in searches. Reset In-Use Flag Keeps two users from opening the same document at the same time. When deleting a library document, you can choose the following:
- 1. Delete the document reference from the folder.
2. Delete that version of the document.
3. Delete all versions of the document. - BLOB (Binary Large Object files) - files where documents are stored.
- GroupWise Client
- Users must be given [RF] permissions to the software distribution directory for client installations.
Minimum requirements:
- 386 or higher CPU
- 20MB free disk space (standard install)
- 1 MB free disk space (workstation install)
- 8MB RAM
- 486 or higher CPU
- 24MB free disk space (standard install)
- 5MB free disk space (workstation install)
- 8MB RAM
- 68040 or higher CPU
- 12.5MB free disk space
- 12MB RAM
- MAC OS 7
Windows 3.1 Windows 95 Macintosh - Standard installation - Installs all Client files to the user's local drive.
- Workstation installation - Installs only necessary files to the user's local drive, and all other files or accessed via a network directory.
The GroupWise client is available for:
- Windows 95
- Windows NT
- Windows 3.1
- Macintosh
- UNIX
The clients for Windows 95, Windows NT and Macintosh are fully functional.
The client for Windows 3.1 lacks functionality for document management, sharing, proxy access, and filtering.
The REG.DAT file is checked during installation to ensure the Windows Messaging system has been installed. It checks to verify that the MAPI32.DLL and MAPI32SP.DLL files are installed. If they are, it proceeds with the client installation, and if not, it first installs the Windows Messaging system, then proceeds with the installation.
Auto-Update is used to automatically upgrade detect and upgrade the workstations current version of the GW client to the newest version. Version identifiers are placed in the user's database and in the REG.DAT file.
Client startup options:
/ph-pathname Path to user's post office directory. /@u-UserID Tells GW which user account to use when logging in. /c Only opens GW if new mail is found. /d-pahtname Tells GW where to store temporary files. /l-xx Specifies language to use, where xx is the two letter language specifier. /la-UserID Used when logging into your GW account when another person is logged in to the workstation. The address book can be run as a separate program outside of GroupWise using the ADDRBOOK.EXE command.