Summary of Contents for Novell GROUPWISE 8 - TROUBLESHOOTING 3
Page 1
AUTHORIZED DOCUMENTATION Troubleshooting 3: Message Flow and Directory Structure Novell ® GroupWise ® August 31, 2009 www.novell.com GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure...
Page 2
Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Page 3
Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
Other sources of troubleshooting assistance include: Novell Support and Knowledgebase (http://www.novell.com/support) To search the GroupWise documentation from the Novell Support Web site, click Advanced Search, select Documentation in the Search In drop-down list, select GroupWise in the Products drop-down list, type the search string, then click Search.
Page 10
Troubleshooting 2: Solutions to Common Problems GroupWise Client User Guides GroupWise Client Frequently Asked Questions (FAQ) Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.
Message Flow Diagrams This part of Troubleshooting 3: Message Flow and Directory Structure helps you understand how ® messages travel between GroupWise users and how administrative updates to GroupWise databases occur. Chapter 1, “Message Delivery in the Local Post Office,” on page 13 Chapter 2, “Message Delivery to a Different Post Office,”...
Message Delivery in the Local Post Office ® The GroupWise 8 client always uses client/server access to the post office but it can interact with the POA for the post office in different ways. For a review, see “Changing GroupWise Modes”...
Stage Icon Description POA for Local The POA receives the message from the GroupWise client and performs Post Office the following actions for the sender: Adds the message to the message database ( msgnnn.db assigned to the sender. Creates a pointer in the sender’s user database ( userxxx.db ) so the message appears in the sender’s mailbox as a sent item.
Page 15
Caching mode. Sender’s The GroupWise client updates the sender’s Caching mailbox GroupWise Client ) by performing the \novell\groupwise\gwxxxxxxx\rofdata following actions: Adds the message to the message database ( rofdata\msg.db in the Caching mailbox. This database is local equivalent of the msgnnn.db...
Page 16
Stage Icon Description POA for Local The POA receives the message from the GroupWise client and performs Post Office the following actions for the sender to update the sender’s Online mailbox: Adds the message to the message database ( msgnnn.db assigned to the sender in the post office.
Stage Icon Description Recipient’s When each recipient sends a message or the time specified by the Send/ GroupWise Client Receive All Marked Accounts Every nn Minutes option has elapsed, each recipient’s GroupWise client connects with the POA and communicates the Opened status to the POA, along with any other data that needs to be uploaded to the recipient’s Online mailbox.
Message Delivery to a Different Post Office The MTA handles message transfer between post offices. Section 2.1, “TCP/IP Link Open: Transfer between Post Offices Successful,” on page 19 Section 2.2, “TCP/IP Link Closed: Transfer between Post Offices Delayed,” on page 22 The message flow diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure focus on TCP/IP links because they are the most common and convenient (unless you have a post office and a domain on the same server).
Page 20
Message Flow When the TCP/IP Link is Open Stages Table 2-1 Stage Icon Description Sender The user sends a message to recipients in a different post office in the same domain. In this diagram, the access mode setting in the local post office is Client/Server Only.
Page 21
Stage Icon Description POA for When the POA receives the new message from the MTA, it places it into the Recipient’s MTA output queue in the post office ( ) on behalf of the wpcsout\ofs\0-7 Post Office MTA. Then, the POA for the recipient’s post office performs the following actions: Adds the message to the message database ( msgnnn.db...
2.2 TCP/IP Link Closed: Transfer between Post Offices Delayed This message flow diagram illustrates how a GroupWise message travels from one user to another between post offices in the same domain when the TCP/IP link between the post office and the domain is closed.
Page 23
Stage Icon Description POA for The POA receives the message from the GroupWise client and performs the Sender’s Post following actions for the sender: Office Adds the message to the message database ( msgnnn.db ) assigned to the sender. Creates a pointer in the sender’s user database ( userxxx.db ) so the message appears in the sender’s mailbox as a sent item.
Page 24
Stage Icon Description POA for The POA communicates to the GroupWise client by way of TCP/IP that a new Local Post message has arrived. Office Recipient’s The Notify component of the recipient’s GroupWise client notifies the recipient GroupWise that a new message has arrived. Client Recipient Each recipient opens the message in the GroupWise client.
Message Delivery to a Different Domain The MTA handles message transfer between domains. Section 3.1, “TCP/IP Link Open: Transfer between Domains Successful,” on page 25 Section 3.2, “TCP/IP Link Closed: Transfer between Domains Delayed,” on page 28 The message flow diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure focus on TCP/IP links because they are the most common and convenient (unless you have two domains on the same server).
Page 26
Message Flow When the TCP/IP Link is Open Stages Table 3-1 Stage Icon Description Sender The user sends a message to recipients in a post office in a different domain. In this diagram, the access mode setting for the local post office is Client/Server Only.
Page 27
Stage Icon Description POA for When it receives the new message, the POA for the recipient’s post office Recipient’s performs the following actions: Post Office Adds the message to the message database ( msgnnn.db ) corresponding to the one assigned to the sender. Creates a pointer in the recipient’s user database ( userxxx.db ) so the...
Stage Icon Description POA for The POA for the sender’s post office updates the sender’s message database Sender’s ) with the Delivered status information (and possibly Opened as well msgnnn.db Post Office if the recipient has opened the message). POA for The POA for the sender’s post office communicates the status to the sender’s Sender’s GroupWise client by way of TCP/IP.
Page 29
Stage Icon Description POA for The POA receives the message from the GroupWise client and performs the Sender’s following actions for the sender: Post Office Adds the message to the message database ( msgnnn.db ) assigned to the sender. Creates a pointer in the sender’s user database ( userxxx.db ) so the message appears in the sender’s mailbox as a sent item.
Page 30
Stage Icon Description POA for When it receives the new message, the POA for the recipient’s post office Recipient’s performs the following actions: Post Office Adds the message to the message database ( msgnnn.db ) corresponding to the one assigned to the sender. Creates a pointer in the recipient’s user database ( userxxx.db ) so the...
Page 31
Stage Icon Description POA for The POA for the sender’s post office updates the sender’s message database Sender’s ) with the Delivered status information (and possibly Opened as well msgnnn.db Post Office if the recipient has opened the message). POA for The POA for the sender’s post office communicates the status to the sender’s Sender’s GroupWise client by way of TCP/IP.
Message Delivery to and from the Internet Section 4.1, “TCP/IP Link: Outbound Transfer to the Internet Successful,” on page 33 Section 4.2, “TCP/IP Link: Outbound Transfer to the Internet Delayed or Unsuccessful,” on page 35 Section 4.3, “Mapped/UNC Link: Outbound Transfer to the Internet Successful,” on page 38 Section 4.4, “Mapped/UNC Link: Outbound Transfer to the Internet Delayed or Unsuccessful,”...
Page 34
Message Flow When the TCP/IP Link is Open Stages Table 4-1 Stage Icon Description Sender The user sends a message to recipients across the Internet by providing their Internet addresses. In this diagram, the access mode setting for the local post office is Client/Server Only.
Stage Icon Description Internet The Internet Agent scans its input queues according to the Idle Sleep Duration Agent for setting on the Gateway Time Settings page of the Internet Agent object in ® Sender’s ConsoleOne . The Internet Agent picks up the file in binary-encrypted format Domain from the directory and converts it.
Page 36
Message Flow When the TCP/IP Link is Closed Figure 4-2 GWIA mslocal gwinprog Destination Host mshold domainms wpcsin wpcsin posta wpcsout ofmsg postb msgnnn.db ofuser gatewayx Internet userxxx.db wpgate offiles gwia domains wpcsout fdo-7f wpcsout gwid send result defer wpcsin Message Flow When the TCP/IP Link is Closed Stages Table 4-2 Stage...
Page 37
Stage Icon Description MTA for The MTA for the sender’s domain receives the message and places it into the Sender’s MTA “in progress” ( ) queue. gwinprog Domain MTA for The MTA determines that the message must be sent out across the Internet. Sender’s Because there is a TCP/IP link between the MTA and the Internet Agent, the Domain...
Stage Icon Description Internet After an message receives 400-level SMTP reply codes until the S*.* Agent for Maximum Number of Hours to Retry a Deferred Message setting is reached, or Sender’s if a message receives 500-level SMTP reply codes, the Internet Agent deletes Domain all related schedule files from the defer directory because the message is undeliverable.
Page 39
Message Flow When the Mapped Link is Open Figure 4-3 GWIA mslocal gwinprog Destination Host mshold domainms wpcsin wpcsin posta wpcsout ofmsg postb msgnnn.db ofuser gatewayx Internet userxxx.db wpgate offiles gwia domains wpcsout fdo-7f wpcsout gwid send result defer wpcsin Message Flow When the Mapped Link is Open Stages Table 4-3 Stage...
Page 40
Stage Icon Description MTA for The MTA for the sender’s domain receives the message and places it into the Sender’s MTA “in progress” ( ) queue. gwinprog Domain MTA for The MTA determines that the message must be sent out across the Internet. Sender’s Because there is a mapped/UNC link between the MTA and the Internet Agent, Domain...
4.4 Mapped/UNC Link: Outbound Transfer to the Internet Delayed or Unsuccessful This message flow diagram shows how outbound messages travel through the GroupWise directory structure to the Internet when there is a mapped/UNC link between the MTA and the Internet Agent and when the Internet Agent cannot communicate successfully with the Internet host to which the message is addressed.
Page 42
Stage Icon Description POA for The POA receives the message from the GroupWise client and performs the Sender’s Post following actions for the sender: Office Adds the message to the message database ( msgnnn.db ) assigned to the sender. Creates a pointer in the sender’s user database ( userxxx.db ) so the message appears in the sender’s mailbox as a sent item.
Stage Icon Description Internet The Internet Agent analyzes the files in the result directory, comparing the Agent for SMTP reply codes in the file. R*.* Sender’s If the R*.* file has a temporary transmission error (meaning it has a 400-level Domain SMTP reply code such as 450 Host Down), the Internet Agent moves the S*.*...
Page 44
Message Flow in From the Internet Figure 4-5 GWIA Destination Host mslocal gwinprog mshold domainms Internet wpgate wpcsin posta gwia receive ofmsg postb msgnnn.db wpcsin ofuser gatewayx userxxx.db offiles domains fdo-7f wpcsout Message Flow in From the Internet Stages Table 4-5 Stage Actor Action...
Stage Actor Action POA for When it receives the new message, the POA for the recipient’s post office Recipient’s performs the following actions: Post Office Adds the message to the message database ( msgnnn.db file) corresponding to the one assigned to the sender. Creates a pointer in the recipient’s user database ( userxxx.db file), so...
Page 46
Message Flow in From the Internet Stages Table 4-6 Stage Actor Action Internet An Internet user sends a message to a GroupWise user. The Internet Agent Agent for receives the message from the external Internet host and places the message Recipient’s file in the wpgate\gwia\receive...
Message Delivery through a Modem Connection ® GroupWise client users can still access information in their mailboxes even when not connected to the network by running the GroupWise client in Remote mode. Section 5.1, ““Hit the Road” Process in Online Mode,” on page 47 Section 5.2, “Modem Link through the Async Gateway in Remote Mode,”...
Stage Icon Description POA for The POA receives the request from the GroupWise client and performs the Remote following actions: User’s Post Gathers all folders from the GroupWise user’s master mailbox ( msgnnn.db Office userxxx.db ) so that it has somewhere to put the items requested by the user.
Page 49
Message Flow Through a Modem Figure 5-2 rofdata wpcsin msg.db user.db wpcsout wprof.db wpcsin wpgate wpcsout async asyxxx mslocal gwin wpgwsend gwinprog connection-id wpgwrecv mshold gwout domainms connection-id wpcsin posta ofmsg postb wpcsin msgnnn.db ofuser gatewayx wpcsout userxxx.db offiles domains fdo-7f wpcsout Message Flow Through a Modem Stages...
Page 50
Stage Icon Description When the remote GroupWise user initiates the modem connection, the GroupWise GroupWise client polls its input queue ( ) and compresses the outgoing wpcsin\1 Client in messages and/or requests into a file. If the compressed file totals over 50 KB, Remote additional compressed files are created.
Page 51
Stage Icon Description POA for When the POA receives a message from the remote user, the POA performs the Remote following actions to update the remote user’s master mailbox: User’s Post Adds the message to the remote user’s message database ( msgnnn.db ) in Office...
Page 52
Stage Icon Description Async If the modem connection to the remote user is still active, the Async Gateway Gateway compresses the status/response files and moves them to the cmp directory. If the modem connection is no longer available, the status/response files wait in connection_id\1 subdirectory until a new connection is established by the remote user.
Administrative Database Update ® ® ConsoleOne and the agents handle database updates throughout the GroupWise system. This message flow diagram illustrates how an administrative message, such as a database update request, passes from ConsoleOne to the agents so that databases are updated throughout the GroupWise system.
Page 54
Stage Actor Action ConsoleOne performs the following actions: ConsoleOne Updates the domain database ( wpdomain.db ) to reflect the addition, modification, or deletion performed in ConsoleOne. Creates an administrative message in the priority subdirectory of the domain’s MTA input queue ( wpcsin ) to replicate the update.
Directory Structure Diagrams This part of Troubleshooting 3: Message Flow and Directory Structure helps you understand the ® structure of GroupWise message transfer/storage directories (such as domains and post offices) and software installation directories. Chapter 7, “Message Transfer/Storage Directories,” on page 57 Chapter 8, “Agent Installation Directories,”...
Message Transfer/Storage Directories Message transfer and storage directories are the locations through which messages pass as they ® travel from user to user through your GroupWise system. Section 7.1, “Domain Directory,” on page 57 Section 7.2, “Post Office Directory,” on page 64 Section 7.3, “MTA Local Queue Directory,”...
MTA input queue directory for administrative messages MTA restart requests Statistics requests Other non-priority administrative requests Reserved; not currently used Reserved; not currently used Reserved; not currently used Reserved; not currently used Reserved; not currently used Directory for undeliverable messages problem Domain name identifier mtaname...
Page 59
Historical Note: WP Office*, the predecessor of GroupWise, was originally designed by WordPerfect Corporation* (WPCorp*). The Message Transfer Agent (MTA) was originally named the Connection Server (CS). Hence, the directory name for the MTA input queue. Some wpcsin naming conventions were originally preserved for backward compatibility. 0 directory The priority subdirectory of the MTA input queue (...
Page 60
3 directory The priority subdirectory of the MTA input queue ( ) in the domain is for high priority wpcsin status messages routed back to senders in local post offices. For example, MTAs for other domains place status responses to high priority user messages here. The local MTA then routes the status messages to senders’...
GroupWise gateway you wpgate have installed in your GroupWise system. For a list of gateways, see the GroupWise Gateways Documentation Web site (http://www.novell.com/documentation/gwateways). GroupWise 5.5 gateways can be used with GroupWise 6.x, 7, and 8. 7.1.5 wpcsout directory subdirectory in the domain is the MTA output queue in each domain.
Page 62
2 directory The priority subdirectory of the MTA admin thread input queue ( ) in the domain wpcsout\ads for high priority administrative messages. For example: The MTA places administrative messages from other domains here. The administrative messages might instruct the MTA admin thread to add, modify, or delete users, post offices, or other objects in the domain.
7.1.6 mtaname file file in the domain provides the domain name associated with the domain directory mtaname structure. This can help you locate the domain information for the directory structure in ConsoleOne. It can also help you check links between MTAs. 7.1.7 wpdomain.db file file in the domain...
Historical Note: WP Office, the predecessor of GroupWise, was originally designed by WordPerfect Corporation (WPCorp). Post offices were originally called hosts. Hence, the name wphost.dc Some naming conventions were originally preserved for backward compatibility. 7.1.10 gwdom.dc file file in the domain is the data dictionary for creating and rebuilding GroupWise 8, 7, gwdom.dc...
Page 65
Library directories lib0001-FF dmxxnn01-FF.db Document databases QuickFinder index for library index archive Archive directory for library docs Large document directory for library Subdirectories for documents fd00-FF Message database directory ofmsg msgnnn.db As many as 255 message databases ngwdfr.db Deferred message database Backup guardian database guardbak User database directory...
POA admin thread input queue directory Restart requests Directory synchronization requests Database updates Reserved; not currently used Reserved; not currently used Reserved; not currently used Reserved; not currently used Reserved; not currently used GWCheck working directory GWCheck priority subdirectories GWCheck subdirectory for deferred database maintenance defer requests problem...
Page 67
For mapped and UNC links, the MTA scans its input queue for messages to process. You can control the rate at which the MTA scans its input queues. See “Adjusting MTA Polling of Input Queues in the Domain, Post Offices, and Gateways”...
Page 68
For mapped and UNC links, you can increase throughput for the priority subdirectories. See “Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices” in “Optimizing MTA” in the GroupWise 8 Administration Guide. For TCP/IP links, the subdirectory is used only if the POA is unable to immediately transfer the high priority user messages to the MTA by way of the TCP/IP link.
For example, the GroupWise client places low priority user messages here. The MTA then routes the messages to the appropriate destinations. For TCP/IP links, the subdirectory is used only if the POA is unable to immediately transfer the low priority user messages to the MTA by way of the TCP/IP link. 7 directory The priority subdirectory of the MTA input queue (...
index directory subdirectories in the library subdirectories ( ) in the post office contain the index lib0001-ff QuickFinder index for the documents contained in the library. archive directory subdirectories in the library subdirectories ( ) in the post office contain an archive lib0001-FF array of subdirectories for holding archived documents.
ngwdfr.db file file in the subdirectory in the post office holds deferred messages that users ngwdfr.db ofmsg have specified for delivery at a later time. When users delay delivery on messages, the messages are transferred to the receiving post office and held in the file until the delay expires.
7.2.6 offiles directory subdirectory in the post office contains subdirectories for messages, attachments, and offiles recipient lists that are equal to or greater than 2 KB in size. These larger messages, attachments, and recipient lists are stored outside the actual message databases in the directory to increase ofmsg database efficiency.
7.2.10 oftemp directory subdirectory in the post office holds various temporary files such as the MIME files oftemp created during access by IMAP e-mail clients. gwdca directory subdirectory in the post office holds subdirectories used by the Document Conversion gwdca Agent as it converts documents to HTML for indexing by the QuickFinder thread.
Page 74
Incoming status messages are queued by priority for delivery to senders’ mailboxes in the local post office. Incoming Busy Search requests are queued for the POA to check users’ schedules in the local post office. The POA scans these priority subdirectories regularly. When a new message arrives, the POA processes the messages and performs the required actions.
Page 75
6 directory The priority subdirectory of the POA input queue ( ) in the post office is for low wpcsout\ofs priority user messages being delivered to recipients in the local post office. For example, the MTA places low priority messages here. The POA then updates the message databases and recipients’...
0 directory The priority 0 subdirectory of the POA admin thread input queue ( ) in the post office wpcsout\ads is for service requests that demand an immediate response from the POA admin thread. 1 directory The priority subdirectory of the POA admin thread input queue ( ) in the post office wpcsout\ads...
7.2.13 gwpo.dc file file in the post office is the data dictionary for creating and rebuilding GroupWise 8, 7, gwpo.dc 6.x, and 5.x post office databases ( files). wphost.db If the file is missing from a post office and its domain, you cannot create or rebuild gwpo.dc GroupWise 8, 7/6.x/5.x post offices in that domain.
7.3 MTA Local Queue Directory mslocal MTA local working directory MTA log files on NetWare and Windows mmddxxx.nn Message logging directory msglog mmddmsg.nn Message logging files MTA "in progress" queue directory gwinprog Priority subdirectories mshold MTA holding directory Processing directory for MTA domainms Priority subdirectories Location identifier...
0518mta.002 second MTA log file created on May 18. On Linux, the MTA log files are stored in the /var/log/novell/groupwise/domain.mta directory Historical Note: In earlier versions of GroupWise, the Message Transfer Agent (MTA) was called the Message Server (MS). Hence, the indicator representing the MTA.
7.3.4 mshold directory subdirectory is a holding queue for messages addressed to domains, post offices, or mshold gateways that are currently closed. A location might be closed because its server is down or because the MTA is unable to communicate with it for any other reason.
The name of the holding queue for each domain consists of the first three characters of the domain name, followed by four hashed characters to ensure uniqueness. 7.3.9 0-7 directories The priority subdirectories in each holding queue in the subdirectory correspond to the mshold priority subdirectories located in each domain, post office, or gateway.
MTA output queue wpcsout gwixxxx System-defined directory Message priority subdirectories problem Hold directory for damaged outbound messages Message hold directory gwhold qfiles Delayed delivery hold directory gwprob Hold directory for damaged inbound messages Directory for character conversion tables gwchars Directory for old configuration files from reinstalls or upgrades save gwia.cfg Internet Agent configuration file for startup switches...
Page 83
gwwork directory directory stores temporary files created by the Internet Agent as it converts and builds gwwork messages for transfer across the Internet. mmddlog.nnn file files hold error and status messages about the functioning of the Internet Agent. mmddlog.nnn The Internet Agent creates a log file each day with a unique name, where mm is the month, dd is the day, and nnn is a sequential number indicating the sequence of log files in a single day.
Page 84
wpcsout directory For a mapped/UNC link, the directory is the MTA output queue as well as being the wpcsout Internet Agent input queue. For a TCP/IP link, the Internet Agent and the MTA communicate by way of TCP/IP rather than by transferring message files.
Page 85
ConsoleOne to locate the file. This enables ConsoleOne exepath.cfg gwia.cfg ® to write any configuration setting changes to the file or update Novell eDirectory with gwia.cfg any changes from the file. The file must contain the path to the file in the gwia.cfg...
xspam.cfg file file lists “X” header fields that your anti-spam service writes to the MIME header, xspam.cfg along with the values that flag the message as spam. The Internet Agent examines the MIME header for any field listed in the file.
send directory The Internet Agent SMTP service places outbound messages in the directory after they have send been converted out of GroupWise format into SMTP format. The SMTP service polls the send directory and sends any messages to the destination SMTP host. receive directory The Internet Agent SMTP service places inbound messages in the directory, converts them...
MTA output queue wpcsout webxxxx System-defined directory for the WebAccess Agent Message priority subdirectories problem Hold directory for damaged outbound messages Hold directory for delayed delivery messages gwhold gwprob Hold directory for damaged inbound messages template Directory for templates for viewing documents Communications Manager configuration file commgr.cfg comint.cfg...
Guide. As part of the installation process, the file is automatically copied to the Web server commgr.cfg installation ( on NetWare, sys:\Novell\GroupWise\WebAccess /opt/novell/groupwise/ on Linux, and on Windows). The copies are webaccess c:\Novell\GroupWise\WebAccess synchronized automatically by the WebAccess Application. The file is also copied to commgr.cfg...
7.6 Caching Mailbox Directory c:\Documents and GroupWise Caching mailbox on Windows XP Settings\username\Local Settings\Application Data\Novell\GroupWise\gwxxx GroupWise Caching mailbox on Windows Vista c:\User\username\AppData\Lo cal\Novell\GroupWise\gwxxxx GroupWise Caching mailbox on Linux /home/username/gwcache/ gwxxxxxx GroupWise Caching mailbox on Mac /Users/username/gwcache/ gwxxxxxx rofdata Caching mailbox database directory msg.db...
7.6.1 gwxxxxxx directory Your GroupWise Caching mailbox is a directory structure that functions similarly to a post office. Like a post office, it contains databases and input/output queues. The default location varies by platform. For the Windows client, the same directory structure is used for a Caching mailbox as for a Remote mailbox.
Page 92
ngwguard.dc file file is the data dictionary for building the databases in the GroupWise Caching ngwguard.dc mailbox. It is parallel in function to the file in the post office. ngwguard.dc ngwguard.rfl file file is a roll-forward transaction log of every database transaction that has taken ngwguard.rfl place since the last copy of the file was created.
index directory directory under the directory contains the QuickFinder index for the documents in index gwdms your Caching mailbox. index directory directory under the directory contains the QuickFinder index for the messages index rofdata in your Caching mailbox. 7.6.3 wpcsin directory subdirectory is the input queue for the connection that transfers messages to your wpcsin GroupWise system for delivery.
7.6.5 wpgwsend directory directory holds compressed files that contain outgoing messages, requests, or both. wpgwsend When a connection to your GroupWise system is established, the GroupWise client uploads the files to your Online mailbox. Historical Note: WP Office Remote, the predecessor of the GroupWise client Remote mode, was originally designed by WordPerfect Corporation (WPCorp).
QuickFinder index for messages in the Remote mailbox index wpcsin Input queue for the GroupWise client in Remote mode Priority subdirectories Output queue for the GroupWise client in Remote mode wpcsout\ofs Priority subdirectories Output queue to master mailbox wpgwsend wpgwrecv Input queue from master mailbox remoten.log Remote connection log...
Page 96
wprof.dc file file in the remote data directory ( ) in the Remote mailbox directory is the wprof.dc rofdata data dictionary for the remote Address Book ( wprof.db Historical Note: An earlier version of the GroupWise client Remote mode, designed by WordPerfect Corporation (WPCorp), was named WP Office Remote.
gwdms directory subdirectory in the remote data directory ( ) in the remote mailbox directory gwdms rofdata the Document Management Services directory. It contains the document libraries you have downloaded from your master GroupWise system. It has the same structure as the gwdms subdirectory in the post office.
7.7.4 wpcsout\ofs directory subdirectory in the remote mailbox directory is the output queue for the wpcsout\ofs connection that transfers messages from your master GroupWise system. Messages from the GroupWise client in Remote mode are processed through the priority subdirectory of wpcsout\ofs. In Remote mode, the GroupWise client scans the subdirectory and updates the wpcsout\ofs\1...
Agent Installation Directories Section 8.1, “GroupWise Agent Installation (POA and MTA),” on page 99 Section 8.2, “Internet Agent Installation,” on page 110 Section 8.3, “WebAccess Agent Installation,” on page 117 Section 8.4, “Monitor Agent Installation,” on page 129 Section 8.5, “Web Server Installation,” on page 133 8.1 GroupWise Agent Installation (POA and MTA) The Post Office Agent (POA) and the Message Transfer Agent (MTA) are always installed together.
Page 100
GroupWise Time Stamp program gwtmstmp.nlm dbcopy.nlm GroupWise Database Copy program help Subdirectory for GroupWise agent Web console help files NetWare agent installation directory When you first install GroupWise Administration, the GroupWise agents are installed in platform- specific subdirectories in the directory in the software distribution directory.
Page 101
strtupxx.mta file The MTA startup file contains startup switches for the MTA. Switch settings placed in the MTA startup file override comparable options set for the MTA in ConsoleOne. The xx in the startup filename represents a two-letter language code. During installation, a customized version of the MTA startup file, named , is created.
“Using the MTA Web Console” in “Message Transfer Agent” in the GroupWise 8 Administration Guide. 8.1.2 Linux Installation Directory /opt/novell/groupwise/agents Linux agent installation directory Subdirectory for GroupWise agent executables gwpoa Post Office Agent (POA) executable Message Transfer Agent (MTA) executable gwmta...
Page 103
Snngrpwise Symbolic link to the startup script for the POA and MTA /etc/opt Standard Linux location for application configuration files Subdirectory for GroupWise configuration files novell/groupwise gwha.conf GroupWise High Availability service configuration file Subdirectory for GroupWise agents agents uid.conf...
Page 104
MTA log files agents directory On a Linux server, the agents are always installed in subdirectories of /opt/novell/groupwise/ agents bin directory directory holds GroupWise executable files. gwpoa file file is the Post Office Agent executable. You run this executable file to start the Post gwpoa Office Agent.
Page 105
gwcsrgen file file is the GroupWise Generate CSR utility. If you enable SSL for the agents, they gwcsrgen need access to a server certificate and private key. You can use the GroupWise Generate CSR utility (GWCSRGEN) to generate a Certificate Signing Request (CSR) file and a Private Key file. For more information, see “Server Certificates and SSL Encryption”...
Page 106
During installation, a customized version of the file, named , is created strtupxx.mta domain.mta in the directory. This customized version has the --home startup switch automatically set to share the domain directory the MTA will service. See “Using MTA Startup Switches”...
Page 107
/etc/opt/novell/groupwise directory directory is the standard location of application configuration files on Linux. Files /etc/opt that configure how the GroupWise agents interact with Linux are stored in the novell/groupwise subdirectory. gwha.conf file file is the GroupWise High Availability service configuration file. It is created gwha.conf...
8.1.3 Windows Installation Directory Windows agent installation directory c:\Program Files\Novell\GroupWise Server\Agents GroupWise Agent Engine gwenv1a.dll gwpoa.exe Post Office Agent (POA) program Message Transfer Agent (MTA) program gwmta.exe strtupxx.poa Boilerplate POA startup file Boilerplate MTA startup file strtupxx.mta post_office.poa Customized POA startup file Customized MTA startup file domain.mta...
Page 109
Message handling Thread management Semaphores (file/record locking) Date/time services The first agent started on a server automatically starts the GroupWise Agent Engine DLL. gwpoa.exe file file is the Post Office Agent program. You run this executable file to start the Post gwpoa.exe Office Agent.
agentnxx.chm files files contain the online documentation for the agents. Online Help is available by clicking .chm Help in the agent consoles on the server where the agents are running. In addition, dialog boxes have a Help button for context-sensitive Help. The first five characters of the filename are the agent name.
Page 111
GroupWise 8 Agent Engine gwenn5.nlm gwia.nlm Internet Agent NLM program Internet Agent configuration file gwia.cfg Internet Agent language information file gwianxx.fil Internet Agent load file gwia.ncf x*5.nlm XIS NLM programs GroupWise XIS NLM programs gwxis12.nlm XIS Internet Agent configuration file gwia.xml help Subdirectory for GroupWise agent console help files...
XML documents to monitor and change the agents as needed. gwia.xml file file is a specialized Internet Agent configuration file for use in the XIS environment. gwia.xml 8.2.2 Linux Installation Directory /opt/novell/groupwise/agents Linux agent installation directory Subdirectory for GroupWise agent executables gwia Internet Agent executable Internet Agent XIS configuration file gwia.xml...
Page 113
Standard Linux location for run-level-5 symbolic links rc5.d Snngrpwise Symbolic link to the startup script for the Internet Agent /etc/opt Standard Linux location for application configuration files novell/groupwise Subdirectory for GroupWise configuration files GroupWise High Availability service configuration file gwha.conf Subdirectory for GroupWise agents agents uid.conf...
Page 114
gwiaxxx.fil files This file contains all language-specific information for the Internet Agent. The last two characters xx are a language code. *.so files These files are Linux shared library files that provide information to the Internet Agent executable. image directory directory has subdirectories for agent icons for both color and monochrome displays.
Page 115
. It is created if you choose during installation to have the grpwise Snngrpwise Internet Agent start automatically when the server boots. /etc/opt/novell/groupwise directory directory is the standard location of application configuration files on Linux. Files /etc/opt that configure how the GroupWise Internet Agent interacts with Linux are stored in the novell/ subdirectory.
XIS agent configuration file See also Section 7.4, “Internet Agent Queue Directory,” on page c:\Program Files\Novell\GroupWise Server\GWIA On a Windows server, the Internet Agent can be installed in any directory you choose. The default location is . The Internet Agent icon is set c:\Program Files\Novell\GroupWise Server\GWIA up to include the full path to whatever directory you choose.
gwianxx.chm file files contain the online documentation for the Internet Agent. Online help is available by .chm clicking Help in the Internet Agent console on the server where the agent is running. In addition, dialog boxes have a Help button for context-sensitive Help. The digit n is a version number.
Page 118
Subdirectory for WebAccess template file storage cache template\xx Subdirectory for HTML template files WebAccess template files webacc.tpt publish.tpt WebPublisher template files Document Viewer Agent working directory gwdva.dir Subdirectory for GroupWise agent console help files help Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console.
Page 119
stopweb.ncf file is the NetWare configuration file that unloads the WebAccess Agent. A stopweb.ncf typical file would look similar to the following: stopweb.ncf unload gwinter webac80a.waa file The WebAccess Agent startup file contains startup switches for the WebAccess Agent. Switch settings placed in the WebAccess Agent startup file override comparable options set for the WebAccess Agent in ConsoleOne.
8.3.2 Linux Installation Directory Novell GroupWise installation directory /opt/novell/groupwise Linux agent installation directory agents Subdirectory for GroupWise agent executables gwinter WebAccess Agent executable gwinter.xml WebAccess Agent XIS configuration file Boilerplate WebAccess startup file webac80axx.waa template Subdirectory for HTML template files...
Page 121
Standard Linux location for application log files /var/log/ novell/groupwise Subdirectory for GroupWise agent log files domain.webac80a Domain-specific subdirectory for WebAccess Agent log files Processing directory for log files 000.prc mmddgwia.nnn WebAccess Agent log files Subdirectory for Viewer Agent log files gwdva mmdddva.nnn...
Page 122
lib directory directory holds GroupWise shared library files. *.so files files are Linux shared library files that provide information to the WebAccess Agent *.so executable. image directory directory has subdirectories for agent icons for both color and monochrome displays. image share directory directory holds agent startup files and files that are used by the agent consoles and Web share...
Page 123
commgr.cfg file file holds the same configuration information that is stored on the GroupWise commgr.cfg Provider object (named GroupWiseProvider) in eDirectory, including the IP address and encryption key for the WebAccess Agent. This information enables the WebAccess Application to communicate with the WebAccess Agent. For more information, see “Configuring the GroupWise Service Provider”...
Page 124
. It is created if you choose during installation to have the grpwise Snngrpwise WebAccess Agent start automatically when the server boots. /var/log/novell/groupwise directory directory is the standard location for log files on Linux. All GroupWise agent log /var/log files are created in the subdirectory.
Section 8.5, “Web Server Installation,” on page 133. See also Section 7.5, “WebAccess Agent Queue Directory,” on page c:\Program Files\Novell\GroupWise Server\WebAccess On a Windows server, the WebAccess Agent can be installed in any directory you choose. The default location is . The WebAccess c:\Program Files\Novell\GroupWise Server\WebAccess Agent desktop icon is set up to include the full path to whatever directory you choose.
Page 126
WebAccess Agent. The batch file specifies the strtweb.bat WebAccess startup file. A typical file includes the following: strtweb.bat title Novell GroupWise WebAccess @echo off cls gwinter.exe @webac80a.waa You run this batch file to start the WebAccess Agent. See “Starting GroupWise WebAccess” in “Installing GroupWise WebAccess”...
The Document Viewer Agent creates its working directory as a subdirectory of its installation directory. The default location varies by platform: NetWare: sys:\system\gwdva.dir Linux: /opt/novell/groupwise/agents/bin/gwdva.dir Windows: c:\Program Files\Novell\GroupWise Server\WebAccess\gwdva.dir gwdva.dir Document Viewer Agent working directory gwdavnnn.ste State files for Document Viewer Agent worker threads Subdirectory for caching converted documents for repeated display cache...
Page 128
Subdirectory for quarantined documents that failed HTML conversion hold Subdirectory for Document Viewer Agent log files Subdirectory for the temporary files using during HTML conversion temp template (not currently used) gwdva.dir directory directory is the working directory for the Document Viewer Agent. gwdva.dir gwdvannn.ste files files hold state information about each Document Viewer Agent worker thread.
NOTE: On Linux, Viewer Agent log files are stored in the typical location for log files on Linux ( ), rather than under the directory. var/log/novell/groupwise/gwdva gwdva.dir temp directory directory is used for the temporary files created during HTML conversion. See temp “Document...
Page 130
Subdirectory for Monitor Agent accounting files agents directory On a Linux server, the Monitor Agent is always installed in subdirectories of /opt/novell/ groupwise/agents bin directory directory holds GroupWise executable files. gwmon file file is the Monitor Agent executable. You run this executable file to start the Monitor gwmon Agent.
Page 131
. It is created if you choose during installation to grpwise-ma Snngrpwise-ma have the Monitor Agent start automatically when the server boots. /var/log/novell/groupwise directory directory is the standard location for log files on Linux. All GroupWise agent log /var/log files are created in the subdirectory.
Additional Monitor files are integrated into your Web server to support the Monitor Web console. For an example, see Section 8.5, “Web Server Installation,” on page 133. c:\Program Files\Novell\GroupWise Server\Monitor directory On a Windows server, the Monitor Agent can be installed in any directory you choose. The default location is . The Monitor Agent c:\Program Files\Novell\GroupWise Server\Monitor desktop icon is set up to include the full path to whatever directory you choose.
gwmon.exe file file is the Monitor Agent program. You run this executable file to start the Monitor gwmon.exe Agent. See “Windows: Setting Up GroupWise Monitor” in “Installing GroupWise Monitor” in the GroupWise 8 Installation Guide. monitor.xml file stores the Monitor Agent configuration information that you establish in the monitor.xml Monitor Agent console, as described in “Configuring the Monitor...
Directory for GroupWise WebPublisher Application files webpublisher WEB-INF GroupWise Web service information directory GroupWise Web service configuration file web.xml Directory for Novell product files classes/com/novell webaccess Directory for GroupWise WebAccess files Subdirectory for service provider files providers Directory for GroupWise WebPublisher files...
Page 135
GroupWise Monitor Web service template files classes/templates sys:\Novell\GroupWise Directory for GroupWise Web services files calhost Subdirectory for the Calendar Publishing Host Calendar Publishing Host configuration file calhost.cfg logs Directory for Calendar Publishing Host log files Subdirectory for GroupWise Monitor gwmonitor gwmonitor.cfg...
Page 136
Web server where the various GroupWise service providers and their web.xml configuration files are located. By default, they are located in subdirectories under sys:\Novell\GroupWise gw/WEB-INF/classes/com/novell/webaccess/providers directory directory holds the Java class and properties files for the WebAccess providers. For providers more information, see “Adding or Removing Service...
Page 137
For more information, see “Modifying Monitor Application Template Settings” in “Monitor” in the GroupWise 8 Administration Guide. sys:\Novell\GroupWise directory directory holds subdirectories for each GroupWise application. sys:\Novell\GroupWise calhost directory directory is created when you install the Calendar Publishing Host. calhost calhost.cfg file...
Page 138
webacc.cfg file file holds the same configuration information that is stored on the WebAccess webacc.cfg Application object (named GroupWiseWebAccess) in eDirectory. For more information, see “Configuring the WebAccess Application” in “WebAccess” in the GroupWise 8 Administration Guide. commgr.cfg file file holds the same configuration information that is stored on the GroupWise commgr.cfg Provider object (named GroupWiseProvider) in eDirectory, including the IP address, port number, number of threads, and encryption key for the WebAccess Agent.
Directory for GroupWise WebPublisher Application files WEB-INF GroupWise Web service information directory GroupWise Web service configuration file web.xml classes/com/novell Directory for Novell product files webaccess Directory for GroupWise WebAccess files Subdirectory for service provider files providers webpublisher Directory for GroupWise WebPublisher files...
Page 140
WebPublisher Application configuration file commgr.cfg Communications Manager configuration file Subdirectory for WebPublisher Application log files logs /etc/opt/novell/httpd/conf.d directory directory is the Apache Web server configuration /etc/opt/novell/httpd/conf.d directory. gw.conf file file includes the command that enables Apache to access the GroupWise gw.conf...
Page 141
/var/opt/novell/tomcat5/webapps directory directory is where applications are installed into the /var/opt/novell/tomcat5/webapps Web server. gw/index.html file file in the directory is the default HTML file for the GroupWise client Web index.html services (WebAccess and WebPublisher) and displays when you go to the following URL:...
Page 142
For more information, see “Modifying Monitor Application Template Settings” in “Monitor” in the GroupWise 8 Administration Guide. /var/opt/novell/groupwise directory directory holds subdirectories for each GroupWise application. /var/opt/novell/groupwise calhost directory directory is created when you install the Calendar Publishing Host. calhost calhost.cfg file...
Page 143
webacc.cfg file file holds the same configuration information that is stored on the WebAccess webacc.cfg Application object (named GroupWiseWebAccess) in eDirectory. For more information, see “Configuring the WebAccess Application” in “WebAccess” in the GroupWise 8 Administration Guide. commgr.cfg file file holds the same configuration information that is stored on the GroupWise commgr.cfg Provider object (named GroupWiseProvider) in eDirectory, including the IP address, port number, number of threads, and encryption key for the WebAccess Agent.
Directory for GroupWise WebPublisher Application files WEB-INF GroupWise Web service information directory web.xml GroupWise Web service configuration file classes/com/novell Directory for Novell product files webaccess Directory for GroupWise WebAccess files providers Subdirectory for service provider files webpublisher Directory for GroupWise WebPublisher files...
Page 145
WEB-INF web.xml GroupWise Monitor Web service configuration file classes/templates GroupWise Monitor Web service template files Directory for GroupWise Web services files /var/opt/novell/groupwise Subdirectory for the Calendar Publishing Host calhost calhost.cfg Calendar Publishing Host configuration file logs Directory for Calendar Publishing Host log files...
Page 146
Web server where the various GroupWise service providers and their web.xml configuration files are located. By default, they are located in subdirectories under sys:\Novell\GroupWise gw/WEB-INF/classes/com/novell/webaccess/providers directory directory holds the Java class and properties files for the WebAccess providers. For providers more information, see “Adding or Removing Service...
Page 147
For more information, see “Modifying Monitor Application Template Settings” in “Monitor” in the GroupWise 8 Administration Guide. /var/opt/novell/groupwise directory directory holds subdirectories for each GroupWise application. /var/opt/novell/groupwise calhost directory directory is created when you install the Calendar Publishing Host. calhost calhost.cfg file...
Page 148
webacc.cfg file file holds the same configuration information that is stored on the WebAccess webacc.cfg Application object (named GroupWiseWebAccess) in eDirectory. For more information, see “Configuring the WebAccess Application” in “WebAccess” in the GroupWise 8 Administration Guide. commgr.cfg file file holds the same configuration information that is stored on the GroupWise commgr.cfg Provider object (named GroupWiseProvider) in eDirectory, including the IP address, port number, number of threads, and encryption key for the WebAccess Agent.
Directory for GroupWise WebPublisher Application files WEB-INF GroupWise Web service information directory GroupWise Web service configuration file web.xml classes/com/novell Directory for Novell product files webaccess Directory for GroupWise WebAccess files Subdirectory for service provider files providers webpublisher Directory for GroupWise WebPublisher files...
Page 150
Subdirectory for WebPublisher Application log files c:/inetpub/wwwroot directory directory is the standard Internet Information Services directory for /inetpub/wwwroot publishing content to the Web. c:/Novell/GroupWise/Tomcat5.5/webapps directory directory is where applications are installed into /Novell/GroupWise/Tomcat5.5/webapps the Web server. gw/index.html file file in the directory is the default HTML file for the GroupWise client Web index.html...
Page 151
Java class and properties files for the WebAccess providers. For providers more information, see “Adding or Removing Service Providers” in “WebAccess” in the GroupWise 8 Administration Guide. gw/WEB-INF/classes/com/novell/webpublisher/providers directory directory holds the Java class and properties files for the WebPublisher providers.
Page 152
calhost.cfg file The calhost.cfg file holds Calendar Publishing Host configuration information. For more information, see “Configuring the Calendar Publishing Host” in “Calendar Publishing Host” in the GroupWise 8 Administration Guide. logs directory subdirectory holds Calendar Publishing Host Application log files. For more information, logs “Using Calendar Publishing Host Log Files”...
Page 153
logs directory subdirectory holds WebAccess Application log files. For more information, see logs “Controlling WebAccess Application Logging” in “WebAccess” in the GroupWise 8 Administration Guide. users directory subdirectory holds session files for WebAccess users. If WebAccess times out after a users period of user inactivity, the user’s session information is saved.
startups directory subdirectory contains the default startup files for the GroupWise agents. During startups installation, a customized startup file is created for each agent that includes the location of the domain or post office serviced by that agent. The customized startup files are named after the domain or post office for which they are created.
wphost.dc file file is the distribution copy of the data dictionary for rebuilding GroupWise 4.x post wphost.dc office databases ( files). wphost.db If the file is missing from a domain, you cannot rebuild GroupWise 4.x post offices in wphost.dc that domain. The original file is located in the subdirectory of the GroupWise wphost.dc...
win32 directory subdirectory contains all GroupWise client files installed for use with Windows. See win32 Section 10.1, “Windows Client,” on page 171. setup.exe file file is the program GroupWise client users run to install and set up the GroupWise setup.exe client on their Windows workstations.
monitor directory subdirectory contains the GroupWise 8/7/6.x Monitor program, an SNMP admin\monitor monitoring program for use with the GroupWise agents. See “Monitor” in the GroupWise 8 Administration Guide. utility directory subdirectory contains helpful GroupWise utilities. admin\utility gwcheck directory subdirectory contains the GroupWise Check utility. See admin\utility\gwcheck “GroupWise Check”...
Installation Guide in PDF docs format. You can find the most up-to-date version of the GroupWise 8 Installation Guide on the GroupWise 8 Documentation Web site (http://www.novell.com/documentation/gw8). 9.2 Linux Software Distribution Directory /opt/novell/groupwise/software Master copy of GroupWise software...
Page 162
GroupWise client software client linux Subdirectory for Linux software Linux client installation script install novell-groupwise-gwclient- Linux client package ver.date.i386.rpm GroupWise Check Utility package novell-groupwise-gwcheck- GroupWise client view files ver.date.i386.rpm ofviews GroupWise administrator software admin novell-groupwise-admin- GroupWise snap-ins to ConsoleOne package ver.date.i386.rpm...
Cluster configuration file 9.2.1 /opt/novell/groupwise/software directory The GroupWise software distribution directory resides initially on the GroupWise 8 DVD or GroupWise 8 downloaded image. GroupWise Administration is installed directly from the original media. In addition, during installation, you can create a software distribution directory on your network from which you subsequently install the GroupWise agents and GroupWise client software.
102. novell-sms-version.i586.rpm file is the Novell Storage Management Services package novell-sms-version.i586.rpm that is used in conjunction with the Service Agent for File Systems (TSAFS) and TSAFS for GroupWise (TSAFSGW) for the purpose of backing up GroupWise databases in a live GroupWise system.
Historical Note: WordPerfect Office (WP Office), the predecessor of GroupWise, was originally designed by WordPerfect Corporation (WPCorp). Hence, the . Some naming wpdomain.dc conventions were originally preserved for backward compatibility. gwdom.dc file file is the distribution copy of the data dictionary for creating and rebuilding gwdom.dc GroupWise 8, 7, 6.x, and 5.x domain databases ( files) in secondary domains.
To see what files are installed by the package, see Section 10.2, “Linux Client,” on page 174. novell-groupwise-gwcheck-version.date.i386.rpm file file is the GroupWise Check utility novell-groupwise-gwcheck.version.date.i386.rpm package. It is not installed by the Installation script but must be installed manually, as described in “Using GWCheck on...
Page 167
GroupWise administrator novell-groupwise-admin.version.date.i386.rpm package that is installed by the Installation script. It contains the GroupWise Administrator snap-ins to ConsoleOne. You can install the admin package manually if necessary. novell-groupwise-dbcopy-version.date.i386.rpm file file is the GroupWise Database Copy novell-groupwise-dbcopy.version.date.i386.rpm...
“Internet Agent” in the GroupWise 8 Administration Guide. novell-groupwise-gwia-version.date.i386.rpm file file is the Internet Agent package that is novell-groupwise-gwia.version.date.i386.rpm installed by the Installation script. You can install the package manually if necessary. To see what files are installed by the package, see Section 8.2, “Internet Agent Installation,”...
WebAccess Agent novell-groupwise-gwinter.version.date.i386.rpm package that is installed by the Installation script. You can install the package manually if necessary. To see what files are installed by the package, see Section 8.3, “WebAccess Agent Installation,” on page 117.
9.2.11 gwinst directory subdirectory contains supporting files and subdirectories used by the Installation script. gwinst clusterimport.conf file file is created by the GroupWise Installation program when you select clusterimport.conf Configure GroupWise for Clustering. It stores your responses from when you installed a GroupWise agent on the preferred cluster node, so that on subsequent nodes, the Import Clustering Data option is available.
Section 10.2, “Linux Client,” on page 174 Section 10.3, “Mac Client,” on page 176 10.1 Windows Client ® c:\Program Installation directory for GroupWise 8.x Windows client software Files\Novell\GroupWise GroupWise client program grpwise.exe gwdca.exe GroupWise Notify program notify.exe addrbook.exe GroupWise Address Book program Hit the Road setup program htrsetup.exe...
10.1.5 addrbook.exe file file is the program that accesses the GroupWise Address Book. The Address addrbook.exe ® Book contains information for all Novell eDirectory users, GroupWise external users, GroupWise external entities, GroupWise e-mail distribution lists, and so on. 10.1.6 htrsetup.exe file file is the setup program for Hit the Road, which creates your Remote mailbox.
10.1.8 gwmailto.exe file file is the program that integrates the GroupWise client with your Web browser. gwmailto.exe If you select Internet Browser Mail Integration during installation, the GroupWise client becomes the default e-mail program on your workstation. See “Installing the GroupWise Clients”...
*.prs example, day planners used by English-speaking people in the United States have different forms from day planners used for various languages in Europe. 10.2 Linux Client /opt/novell/groupwise/client GroupWise Linux client installation directory Desktop shortcut for the Linux client gwclient.desktop gwclient.png...
Java Runtime Environment (JRE) used by the Linux client Log files generated by the Linux client logs 10.2.1 /opt/novell/groupwise/client directory directory is the default location for the GroupWise Linux /opt/novell/groupwise/client client software. The Installation program does not provide the opportunity to specify a different location and typically there is no need to move the software.
wprof.dc file file is the data dictionary used to create the local copy of the Address Book that wprof.dc resides on the user’s workstation ( wprof.db *.jar files files efficiently store information referenced by the Linux client. The file *.jar gwclient.jar contains the Linux online help information.
10.3.3 MacOS directory directory contains the file that enables the Mac client to invoke MacOS JavaApplicationStub the Java Virtual Machine (JVM). 10.3.4 Resources directory directory is the standard location on Macintosh for files that support an application. Resources GroupWise.icns file file contains all the images that display in the Mac client.
Documentation Updates I I I This section lists updates to Troubleshooting 3: Message Flow and Directory Structure that have ® been made since the initial release of GroupWise 8. The information helps you to keep current on documentation updates and, in some cases, software updates (such as a Support Pack release). The information is grouped according to the date when Troubleshooting 3: Message Flow and Directory Structure was republished.
August 31, 2009 (GroupWise 8 SP1) Location Change Directory Structure Diagrams Section 7.2, “Post Office Clarified the difference in functionality in the priority wpcsin Directory,” on page 64 subdirectories when using mapped/UNC links vs. TCP/IP links, added the subdirectory. gwdca Section 7.3, “MTA Local Noted that the location for MTA log files is different on Linux.
Need help?
Do you have a question about the GROUPWISE 8 - TROUBLESHOOTING 3 and is the answer not in the manual?
Questions and answers