1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - TROUBLESHOOTING 3
  6. Troubleshooting manual

Novell GROUPWISE 7 - TROUBLESHOOTING 3 Troubleshooting Manual

Message flow and directory structure
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Novell
GroupWise
7
S e t e m b e r 2 9 , 2 0 0 6
®
T R O U B L E S H O O T I N G 3 : M E S S A G E
F L O W A N D D I R E C T O R Y S T R U C T U R E
w w w . n o v e l l . c o m

Advertisement

Table of Contents
loading

Related Manuals for Novell GROUPWISE 7 - TROUBLESHOOTING 3

Summary of Contents for Novell GROUPWISE 7 - TROUBLESHOOTING 3

  • Page 1 Novell GroupWise ® w w w . n o v e l l . c o m T R O U B L E S H O O T I N G 3 : M E S S A G E...
  • Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.

  • Page 5: Table Of Contents

    Contents About This Guide Part I Message Flow Diagrams 1 Message Delivery in the Local Post Office Online Mode ............. . 13 Caching Mode .
  • Page 6 7.6.1 \novell\groupwise\gwxxxxxx directory ........97 7.6.2...
  • Page 7 Linux Software Distribution Directory......... . . 162 9.2.1 /opt/novell/groupwise/software directory ....... . . 165 9.2.2 agents directory.
  • Page 8 10.2.1 /opt/novell/groupwise/client directory ........177 10.2.2...

  • Page 9: About This Guide

    We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.
  • 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.

  • Page 11: Part I Message Flow Diagrams

    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,”...
  • Page 12 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 13: Message Delivery In The Local Post Office

    Message Delivery in the Local Post Office ® The GroupWise 7 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 “Using Different GroupWise Modes (Online, Caching, and Remote)”...
  • Page 14 Stage Icon Description The GroupWise client communicates with the POA by way of TCP/IP. Sender’s GroupWise Client The POA receives the message from the GroupWise client and POA for Local performs the following actions for the sender: Post Office Adds the message to the message database (msgnnn.db) assigned to the sender.

  • Page 15: Caching Mode

    1.2 Caching Mode This message flow diagram illustrates how a GroupWise message travels from one user to another in the local post office when the users are accessing their Caching mailboxes. Message Flow in Caching Mode Figure 1-2 10 7 rofdata rofdata msg.db...
  • Page 16 Stage Icon Description The GroupWise client updates the sender’s Caching mailbox Sender’s (\novell\groupwise\gwxxxxxxx\rofdata) by performing the GroupWise following actions: Client Adds the message to the message database (rofdata\msg.db) in the Caching mailbox. This database is local equivalent of the database in the post office.
  • Page 17 Stage Icon Description Because the recipients are also in Caching mode, they do not receive POA for Local immediate notification that a new message has arrived in their Online Post Office mailboxes. Based on the Send/Retrieve All Marked Accounts Every nn Minutes option under Accounts >...

  • Page 18: Remote Mode

    Stage Icon Description The sender’s GroupWise client updates the sender’s Caching mailbox Recipient’s by performing the following action: GroupWise Client Updates the message in the message database (rofdata\msg.db) with a Delivered and Opened status for each recipient. When the sender checks the sent items in his or her mailbox in the Sender GroupWise client, the message displays a status of Delivered and Opened for each recipient.

  • Page 19: Message Delivery To A Different Post Office

    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 7 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 The user sends a message to recipients in a different post office in the same Sender domain. In this diagram, the access mode setting in the local post office is Client/ Server Only.
  • Page 21 Stage Icon Description When the POA receives the new message from the MTA, it places it into the POA for MTA output queue in the post office (wpcsout\ofs\0-7) on behalf of the Recipient’s MTA. Then, the POA for the recipient’s post office performs the following Post Office actions: Adds the message to the message database (msgnnn.db)

  • Page 22: Tcp/Ip Link Closed: Transfer Between Post Offices Delayed

    Stage Icon Description The POA communicates the status to the sender’s GroupWise client by way POA for Local of TCP/IP. Post Office When the sender checks the sent items in his or her mailbox in the Sender GroupWise client, the message displays a status of Delivered for each recipient (and possibly Opened as well if the recipient has opened the message).
  • Page 23 Message Flow When the TCP/IP Link is Closed Stages Table 2-2 Stage Icon Description The user sends a message to recipients in a different post office in the same Sender domain. In this diagram, the access mode setting in the local post office is Client/ Server Only.
  • Page 24 Stage Icon Description When it receives the new message, the POA for the recipient’s post office POA for performs the following actions: Recipient’s Adds the message to the message database (msgnnn.db) Post Office corresponding to the one assigned to the sender. Creates a pointer in the recipient’s user database (userxxx.db) so the new message appears in the recipient’s mailbox and updates the notification information in the user database so the recipient can be...
  • Page 25 Stage Icon Description The POA communicates the Opened status to the sender’s GroupWise POA for Local client by way of TCP/IP. Post Office When the sender checks the sent items in his or her mailbox in the Sender GroupWise client, the message displays a status of Delivered for each recipient (and possibly Opened as well if the recipient has opened the message).
  • Page 26 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 27: Message Delivery To A Different Domain

    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 27 Section 3.2, “TCP/IP Link Closed: Transfer between Domains Delayed,” on page 31 The message flow diagrams in GroupWise 7 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 28 Message Flow When the TCP/IP Link is Open Stages Table 3-1 Stage Icon Description The user sends a message to recipients in a post office in a different domain. Sender In this diagram, the access mode setting for the local post office is Client/Server Only.
  • Page 29 Stage Icon Description When it receives the new message, the POA for the recipient’s post office POA for performs the following actions: Recipient’s Adds the message to the message database (msgnnn.db) corresponding Post Office to the one assigned to the sender. Creates a pointer in the recipient’s user database (userxxx.db) so the new message appears in the recipient’s mailbox and updates the notification information in the user database so the recipient can be...

  • Page 30: Tcp/Ip Link Closed: Transfer Between Domains Delayed

    Stage Icon Description The MTA for the sender’s domain communicates the status message to the MTA for POA for the sender’s post office by way of TCP/IP. Sender’s Domain The POA for the sender’s post office updates the sender’s message database POA for (msgnnn.db) with the Delivered status information (and possibly Opened as Sender’s...
  • Page 31 Message Flow When the TCP/IP Link is Closed Stages Table 3-2 Stage Icon Description The user sends a message to recipients in a post office in a different domain. Sender In this diagram, the access mode setting for the local post office is Client/ Server Only.
  • Page 32 Stage Icon Description The MTA for the recipient’s domain then communicates the message to the MTA for POA in the recipient’s post office by way of TCP/IP. Recipient’s Domain When it receives the new message, the POA for the recipient’s post office POA for performs the following actions: Recipient’s...
  • Page 33 Stage Icon Description The MTA for the sender’s domain places the status message into the MTA “in MTA for progress” (gwinprog) queue. Sender’s Domain The MTA for the sender’s domain communicates the status message to the MTA for POA for the sender’s post office by way of TCP/IP. Sender’s Domain The POA for the sender’s post office updates the sender’s message database...
  • Page 34 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 35: Message Delivery To And From The Internet

    Message Delivery to and from the Internet Section 4.1, “TCP/IP Link: Outbound Transfer to the Internet Successful,” on page 35 Section 4.2, “TCP/IP Link: Outbound Transfer to the Internet Delayed or Unsuccessful,” on page 38 Section 4.3, “Mapped/UNC Link: Outbound Transfer to the Internet Successful,” on page 41 Section 4.4, “Mapped/UNC Link: Outbound Transfer to the Internet Delayed or Unsuccessful,”...
  • Page 36 Message Flow When the TCP/IP Link is Open Stages Table 4-1 Stage Icon Description The user sends a message to recipients across the Internet by providing their Sender Internet addresses. In this diagram, the access mode setting for the local post office is Client/ Server Only.
  • Page 37 Stage Icon Description The Internet Agent scans its input queues according to the Idle Sleep Duration Internet setting on the Gateway Time Settings page of the Internet Agent object in ® Agent for ConsoleOne . The Internet Agent picks up the file in binary-encrypted format Sender’s from the wpcsout\gwid\0-7 directory and converts it.

  • Page 38: Tcp/Ip Link: Outbound Transfer To The Internet Delayed Or Unsuccessful

    4.2 TCP/IP 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 TCP/IP 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 39 Stage Icon Description The POA receives the message from the GroupWise client and performs the POA for following actions for the sender: Sender’s Adds the message to the message database (msgnnn.db) assigned to Post Office 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 40 Stage Icon Description While the Internet Agent is processing the message file in the send directory, it Internet changes the first character of the filename to P. When processing is Agent for completed, the Internet Agent sends the message to the destination host Sender’s across the Internet.

  • Page 41: Mapped/Unc Link: Outbound Transfer To The Internet Successful

    Stage Icon Description The POA for the sender’s post office updates the sender’s message database POA for (msgnnn.db) with the Transferred status information. Sender’s Post Office The POA for the sender’s post office communicates the Transferred status to POA for the sender’s GroupWise client by way of TCP/IP.
  • Page 42 Message Flow When the Mapped Link is Open Stages Table 4-3 Stage Icon Description The user sends a message to recipients across the Internet by providing their Sender Internet addresses. In this diagram, the access mode setting for the local post office is Client/ Server Only.

  • Page 43: Mapped/Unc Link: Outbound Transfer To The Internet Delayed Or Unsuccessful

    Stage Icon Description While the Internet Agent is processing the message file in the send directory, it Internet changes the first character of the filename to P. When processing is Agent for completed, the Internet Agent sends the message to the destination host Sender’s across the Internet.

  • Page 44: Poa

    and when the Internet Agent cannot communicate successfully with the Internet host to which the message is addressed. Message Flow When the Mapped Link is Closed Figure 4-4 GWIA mslocal gwinprog Destination Host mshold domainms wpcsin wpcsin posta wpcsout ofmsg postb msgnnn.db ofuser...
  • Page 45 Stage Icon Description The POA receives the message from the GroupWise client and performs the POA for following actions for the sender: Sender’s Adds the message to the message database (msgnnn.db) assigned to Post Office 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 46 Stage Icon Description The Internet Agent analyzes the files in the result directory, comparing the Internet SMTP reply codes in the R*.* file. Agent for If the R*.* file has a temporary transmission error (meaning it has a 400-level Sender’s SMTP reply code such as 450 Host Down), the Internet Agent moves the Domain S*.* message file to the...

  • Page 47: Tcp/Ip Link: Inbound Transfer From The Internet Successful

    4.5 TCP/IP Link: Inbound Transfer from the Internet Successful This message flow diagram illustrates how inbound message flow from the Internet through the GroupWise directory structure to the GroupWise recipient. The link between the Internet Agent and the MTA for the recipient’s domain is a TCP/IP link. Message Flow in From the Internet Figure 4-5 GWIA...
  • Page 48 Stage Actor Action The Internet Agent then communicates the message to the MTA for the Internet recipient’s domain by way of TCP/IP. When the transmission is successful, Agent for it deletes the copy in the in the wpgate\gwia\wpcsin\0-7 directory. Recipient’s Domain The MTA for the recipient’s domain receives the message and places it into MTA for...

  • Page 49: Mapped/Unc Link: Inbound Transfer From The Internet Successful

    4.6 Mapped/UNC Link: Inbound Transfer from the Internet Successful This message flow diagram illustrates how inbound message flow from the Internet through the GroupWise directory structure to the GroupWise recipient. The link between the Internet Agent and the MTA for the recipient’s domain is a mapped/UNC link. Message Flow in From the Internet Figure 4-6 Destination...
  • Page 50 Stage Actor Action The MTA determines which post office in the domain the recipient is located MTA for in, then moves the message to that post office’s hold queue Recipient’s (mslocal\mshold\postx\0-7). Domain The MTA for the recipient’s domain then communicates the message to the MTA for POA in the recipient’s post office by way of TCP/IP.

  • Page 51: Message Delivery Through A Modem Connection

    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 51 Section 5.2, “Modem Link through the Async Gateway in Remote Mode,”...
  • Page 52 Stage Icon Description The GroupWise client prompts the user for the location to create the Remote GroupWise mailbox and the types of items to download, then it transfers the request to the Client in POA. Online Mode The POA receives the request from the GroupWise client and performs the POA for following actions: Remote...

  • Page 53: Modem Link Through The Async Gateway In Remote Mode

    5.2 Modem Link through the Async Gateway in Remote Mode This message flow diagram illustrates how a GroupWise user in Remote mode can access the master GroupWise system through the GroupWise Async Gateway. Message Flow Through a Modem Figure 5-2 rofdata wpcsin msg.db...
  • Page 54 Stage Icon Description When the remote GroupWise user sends a message to another GroupWise GroupWise user, the GroupWise client performs the following actions in the user’s Client in Remote mailbox: Remote Adds the message to the message database (msg.db) on the user’s Mode remote computer.
  • Page 55 Stage Icon Description The MTA for the remote user’s domain then communicates the message/ MTA for request files to the POA for the post office where the remote user’s master Remote mailbox is located. User’s Domain NOTE: This message flow diagram illustrates only the simplest case where the recipient is in the same post office as the remote user’s master mailbox.
  • Page 56 Stage Icon Description With a TCP/IP link, the MTA for the remote user’s domain communicates the MTA in status/response files to the Async Gateway in the remote user’s domain. Remote With a UNC/mapped link, the MTA for the remote user’s domain places the User’s status/response files into the Async Gateway’s input queue Domain...
  • Page 57 Stage Icon Description The GroupWise user can now review current GroupWise mail when the Remote modem connection to the master GroupWise system is no longer available. User Message Delivery through a Modem Connection...
  • Page 58 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 59: Administrative Database Update

    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 60 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. The MTA for the domain transfers the administrative message to the MTA “in MTA for progress”...

  • Page 61: Part Ii Directory Structure Diagrams

    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 63 Chapter 8, “Agent Installation Directories,”...
  • Page 62 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 63: Message Transfer/Storage 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 63 Section 7.2, “Post Office Directory,” on page 70 Section 7.3, “MTA Local Queue Directory,”...

  • Page 64: Domain 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 65 the Connection Server (CS). Hence, the directory name wpcsin for the MTA input queue. Some naming conventions were originally preserved for backward compatibility. 0 directory The priority 0 subdirectory of the MTA input queue (wpcsin) in the domain is for service requests that demand an immediate response from the MTA.

  • Page 66: Wptools Directory

    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’ post offices, so senders’ mailboxes can be updated with current message status. You can increase throughput for the priority 2 and 3 subdirectories. See “Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices”...

  • Page 67: Wpgate Directory

    GroupWise gateway you 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 and 7.x. 7.1.5 wpcsout directory The wpcsout subdirectory in the domain is the MTA output queue in each domain.

  • Page 68: Mtaname File

    When you use the Synchronize utility in ConsoleOne, a synchronization request is placed here. The MTA admin thread then resends the specified administrative messages to produce the required database updates. css directory The css subdirectory of the MTA output queue (wpcsout) in the domain is processed by a specialized MTA thread that responds to requests regarding its own configuration.

  • Page 69: Wpdomain.dc File

    In the primary domain, the wpdomain.db file contains all administrative information for your entire GroupWise system (all its domains, post offices, users, and so on). Because the wpdomain.db file in the primary domain is so crucial, you should back it up regularly and keep it secure.

  • Page 70: Gwpo.dc File

    7.1.11 gwpo.dc file The gwpo.dc file in the domain is the data dictionary for creating and rebuilding GroupWise 7.x, 6.x, and 5.x post office databases (wphost.db files). If the gwpo.dc file is missing from a domain, you cannot create or rebuild GroupWise 7.x/6/x/5.x post offices in that domain.

  • Page 71: Post_Office Directory

    Attachment store directory offiles Subdirectories for attachments fd0-f6 GroupWise client view files ofviews GroupWise working directory ofwork Remote direct connection directory ofdirect GroupWise temporary files oftemp MTA output queue directory wpcsout POA input queue directory Live interactive requests Other interactive requests High priority messages High priority status responses Normal priority messages...

  • Page 72: Wpcsin Directory

    Physically, a post office is a directory structure on a network file server. The directory structure contains subdirectories and databases that store messages and the information used to distribute the messages. 7.2.2 wpcsin directory The wpcsin subdirectory in the post office is the MTA input queue in each post office.
  • Page 73 You can increase throughput for the priority 1 subdirectory. See “Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices” in “Optimizing the MTA” in the GroupWise 7 Administration Guide. 2 directory The priority 2 subdirectory of the MTA input queue (wpcsin) in the post office is for high priority user messages routed to recipients in other post offices, domains, or systems.

  • Page 74: Gwdms Directory

    For example, the GroupWise client places low priority user messages here. The MTA then routes the messages to the appropriate destinations. 7 directory The priority 7 subdirectory of the MTA input queue (wpcsin) in the post office is for low priority status messages routed back to senders in other post offices, domains, or systems.

  • Page 75: Ofmsg Directory

    index directory The index subdirectories in the library subdirectories (lib0001-ff) in the post office contain the QuickFinder index for the documents contained in the library. archive directory The archive subdirectories in the library subdirectories (lib0001-ff) in the post office contain an array of subdirectories for holding archived documents.

  • Page 76: Ofuser Directory

    messages are transferred to the receiving post office and held in the ngwdfr.db file until the delay expires. Historical Note: Earlier versions of GroupWise handled deferred messages through the ofpend directory in the post office. guardbak directory The guardbak subdirectory in the subdirectory in the post office holds a backup copy of...

  • Page 77: Offiles Directory

    7.2.6 offiles directory The offiles subdirectory in the post office contains subdirectories for messages, attachments, and 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.

  • Page 78: Oftemp Directory

    7.2.10 oftemp directory The oftemp subdirectory in the post office holds various temporary files such as the MIME files created during access by IMAP e-mail clients. 7.2.11 wpcsout directory The wpcsout subdirectory in the post office is the MTA output queue in each post office. It contains subdirectories which function as input queues for the other agents to which the MTA delivers messages.
  • Page 79 For example, the MTA places high priority user messages here. The POA then updates the message databases and recipients’ mailboxes. 3 directory The priority 3 subdirectory of the POA input queue (wpcsout\ofs) in the post office is for high priority status messages coming back to senders in the local post office. For example, the MTA places status responses to high priority user messages here.
  • Page 80 directory. You can change the location if needed. See “Using POA Log Files” in wpcsout\ofs “Post Office Agent” in the GroupWise 7 Administration Guide guide. The first two digits of the filename represent the month, the next two digits represent the day of the month, and the next three characters indicate what program created the log.

  • Page 81: Wphost.db File

    problem directory The problem subdirectory of the MTA output queue (wpcsout) in the post office is a holding area for damaged message files. Problem files are marked with an extension indicating which GroupWise agent placed each file in the problem directory. You should check this directory periodically for problem files, resolve the problem, then place the files back into the appropriate queue for continued processing.

  • Page 82: Ngwguard.fbk File

    7.2.16 ngwguard.fbk file The ngwguard.fbk file in the post office is a “fall back” copy of the file. If the ngwguard.db ngwguard.db file becomes damaged, the ngwguard.fbk file, along with the ngsguard.rfl file, can be used to rebuild a valid, current ngwguard.db file. The ngwguard.fbk file is so important that an additional copy of it is kept in the ofmsg\guardbak subdirectory in case the copy in the post office directory is inadvertently deleted.

  • Page 83: Mslocal Directory

    7.3.1 mslocal directory directory is the MTA local working directory. The /work startup switch of the MTA mslocal specifies the location of the mslocal directory. It must be located on the hard disk of the server where the MTA runs so it is always accessible. Adequate disk space must be available to hold messages going to destinations that are temporarily closed.

  • Page 84: Gwinprog Directory

    The first two digits of the filename represent the month; the next two digits represent the day of the month. The three-digit extension is a sequence number for multiple files created on the same day. For example, 0518msg.002 is the second message logging file created on May 18. 7.3.3 gwinprog directory The gwinprog subdirectory is the MTA “in progress”...

  • Page 85: Domainx Directories

    mshold. When the gateway is open, the MTA moves the messages from the holding queue back into the regular message flow through the gateway. The name of the holding queue for each gateway consists of the first three characters of the gateway name, followed by four hashed characters to ensure uniqueness.
  • Page 86 GroupWise Internet Agent home directory domain\wpgate\gwia Internet Agent message processing directory 000.prc Not currently used Hold directory for temporary files used during processing gwwork Log files mmddlog.nnn Accounting file acct Settings file for screen colors, log levels, and so on Statistics file for Internet Agent operation stat Process lock file indicating that the Internet Agent is running...

  • Page 87: Domain\Wpgate\Gwia Directory

    Delivery Status Notification (DSN) hold directory dsnhold 7.4.1 domain\wpgate\gwia directory The domain\wpgate\gwia directory is the GroupWise Internet Agent home directory where Internet Agent configuration files and queue directories are located. The name is established when you install the Internet Agent. The default is wpgate\gwia in the domain directory. You can change the location using the /home startup switch in the Internet Agent configuration file...
  • Page 88 pulse.tmp file The pulse.tmp file is re-created by the Internet Agent every time it completes a cycle (after an idle loop). If you are not at the Internet Agent console but need to know if the Internet Agent is running, you can delete the pulse.tmp file. If the Internet Agent is running, it re-creates the file. wpcsin directory For a mapped/UNC link, the Internet Agent places inbound messages in one of the wpcsin priority subdirectories (0-7).
  • Page 89 Linux: The Linux Internet Agent uses the file created in gwia.cfg /opt/novell/ during installation. The gwia.cfg file under the domain groupwise/agents/share is just a boilerplate file with no switches set during installation. Windows: Only the Windows Internet Agent actually uses the gwia.cfg file under the domain.
  • Page 90 This enables gwia.cfg ® ConsoleOne to write any configuration setting changes to the gwia.cfg file or update Novell eDirectory with any changes from the file. The file must contain the path to the gwia.cfg file in directory on NetWare, the...

  • Page 91: Gwia Directory

    statusxx.xml file The statusxx.xml file enables you to customize the messages that users receive regarding message delivery status. For more information, see “Customizing Delivery Status Notifications” in “Internet Agent” in the GroupWise 7 Administration Guide. 7.4.2 gwia directory The gwia directory is the SMTP service (daemon) home directory where messages are converted between GroupWise format and Internet format.

  • Page 92: Webaccess Agent Queue Directory

    7.5 WebAccess Agent Queue Directory The following directories and files are found under the \domain\wpgate\ structure for the WebAccess Agent after the software has been installed and the WebAccess Agent has processed messages. GroupWise WebAccess Agent home directory domain\wpgate\webac70a WebAccess Agent log file processing directory 000.prc Hold directory for temporary files used during processing gwwork...

  • Page 93: Wpcsin Directory

    As part of the installation process, the commgr.cfg file is automatically copied to the Web server installation (sys:\novell\webaccess on NetWare, /opt/novell/groupwise/ on Linux, and c:\novell\webaccess on Windows). The copies are webaccess synchronized automatically by the WebAccess Application. The commgr.cfg file is also copied to the webpublisher subdirectory on the Web server. 7.5.9 comint.cfg file The comint.cfg file in the WebAccess Agent queue directory is read by the WebAccess Agent...

  • Page 94: Gwac.db File

    GroupWise 7 Administration Guide. 7.5.12 gwac.dc file The gwac.dc file is the data dictionary file from which the gwac.db is created. 7.6 Caching Mailbox Directory GroupWise Caching mailbox \novell\groupwise\gwxxxxxx Caching mailbox database directory rofdata Cached message database msg.db Cached user database user.db...

  • Page 95: Novell\Groupwise\Gwxxxxxx Directory

    Like a post office, it contains databases and input/output queues. It is created in the directory where the GroupWise client is installed, which is typically \novell\groupwise. The same directory structure is used for a Caching mailbox as for a Remote mailbox. However, a Caching mailbox is a complete copy of your Online mailbox, but you can restrict what gets downloaded into your Remote mailbox.
  • Page 96 ngwguard.dc file The ngwguard.dc file is the data dictionary for building the databases in the GroupWise Caching mailbox. It is parallel in function to the file in the post office. ngwguard.dc ngwguard.rfl file The ngwguard.rfl file is a roll-forward transaction log of every database transaction that has taken place since the last copy of the file was created.

  • Page 97: Wpcsin Directory

    index directory The index directory under the gwdms directory contains the QuickFinder index for the documents in your Caching mailbox. index directory The index directory under the rofdata directory contains the QuickFinder index for the messages in your Caching mailbox. 7.6.3 wpcsin directory The wpcsin subdirectory is the input queue for the connection that transfers messages to your GroupWise system for delivery.

  • Page 98: Wpgwsend Directory

    7.6.5 wpgwsend directory The wpgwsend directory holds compressed files that contain outgoing messages, requests, or both. 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).

  • Page 99: Remote_Mailbox Directory

    QuickFinder index for messages in the Remote mailbox index Input queue for the GroupWise client in Remote mode wpcsin Priority subdirectories Output queue for the GroupWise client in Remote mode wpcsout\ofs Priority subdirectories Output queue to master mailbox wpgwsend Input queue from master mailbox wpgwrecv Remote connection log remoten.log...
  • Page 100 wprof.dc file The wprof.dc file in the remote data directory (rofdata) in the Remote mailbox directory is the 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.

  • Page 101: Wpcsin Directory

    gwdms directory The gwdms subdirectory in the remote data directory (rofdata) in the remote mailbox directory 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.

  • Page 102: Wpcsout\Ofs Directory

    7.7.4 wpcsout\ofs directory The wpcsout\ofs subdirectory in the remote mailbox directory is the output queue for the connection that transfers messages from your master GroupWise system. Messages from the GroupWise client in Remote mode are processed through the priority 1 subdirectory of wpcsout\ofs. In Remote mode, the GroupWise client scans the wpcsout\ofs\1 subdirectory and updates the files with the information received from the master mailbox.

  • Page 103: Agent Installation Directories

    Agent Installation Directories Section 8.1, “GroupWise Agent Installation (POA and MTA),” on page 103 Section 8.2, “Internet Agent Installation,” on page 114 Section 8.3, “WebAccess Agent Installation,” on page 121 Section 8.4, “Monitor Agent Installation,” on page 133 Section 8.5, “Apache/Tomcat Installation,” on page 137 8.1 GroupWise Agent Installation (POA and MTA) The Post Office Agent (POA) and the Message Transfer Agent (MTA) are always installed together.
  • Page 104 GroupWise Time Stamp program gwtmstmp.nlm GroupWise Database Copy program dbcopy.nlm Subdirectory for GroupWise agent Web console help files help 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 105 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 domain.mta, is created.

  • Page 106: Linux Installation Directory

    “Message Transfer Agent” in the GroupWise 7 Administration Guide. 8.1.2 Linux Installation Directory Linux agent installation directory /opt/novell/groupwise/agents Subdirectory for GroupWise agent executables Post Office Agent (POA) executable gwpoa Message Transfer Agent (MTA) executable gwmta GroupWise High Availability service executable...
  • Page 107 Symbolic link to the startup script for the POA and MTA S99grpwise Standard Linux location for application configuration files /etc/opt Subdirectory for GroupWise configuration files novell/groupwise GroupWise High Availability service configuration file gwha.conf Subdirectory for GroupWise agents agents Agent configuration file for running as a non-root user uid.conf...
  • Page 108 Domain-specific subdirectory for MTA log files domain.mta MTA log files mmddmta.nnn agents directory On a Linux server, the agents are always installed in subdirectories of /opt/novell/ groupwise/agents. bin directory The bin directory holds GroupWise executable files. gwpoa file The gwpoa file is the Post Office Agent executable. You run this executable file to start the Post Office Agent.
  • Page 109 more information, see “Server Certificates and SSL Encryption” in “Security Administration” in the GroupWise 7 Administration Guide. gwtmstmp file The gwtmstmp file is the GroupWise Time Stamp utility. If you deselect Allow Purge of Items Not Backed Up in ConsoleOne, user databases (userxxx.db) must be time-stamped every time a backup is performed so that items can be purged only after being backed up.
  • Page 110 /etc/opt/novell/groupwise directory The /etc/opt directory is the standard location of application configuration files on Linux. Files that configure how the GroupWise agents interact with Linux are stored in the novell/ groupwise subdirectory. 110 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 111: Windows Installation Directory

    Guide. /var/log/novell/groupwise directory The /var/log directory is the standard location for log files on Linux. All GroupWise agent log files are created in the novell/groupwise subdirectory. post_office.poa directory The post_office.poa directory is a post office-specific location for POA log files.
  • Page 112 Boilerplate POA startup file strtupxx.poa Boilerplate MTA startup file strtupxx.mta Customized POA startup file post_office.poa Customized MTA startup file domain.mta POA startup file for a specific post office post_office.poa MTA startup file for a specific domain domain.mta POA online help file gwpoanxx.chm MTA online help file gwmtanxx.chm...
  • Page 113 gwpoa.exe file The gwpoa.exe file is the Post Office Agent program. You run this executable file to start the Post Office Agent. See “Starting the Windows GroupWise Agents” in “Installing GroupWise Agents” in GroupWise 7 Installation Guide. gwmta.exe file The gwmta.exe file is the Message Transfer Agent program. You run this executable file to start the Message Transfer Agent.

  • Page 114: Internet Agent Installation

    agentnxx.dll files The agentnxx.dll files contain all language-specific information for the agents. The digit n is a version number. The last two characters xx are a language code. x*10a.dll and gwxis10.dll files The x*10a.dll and gwxis10.dll programs provide XIS capability for the GroupWise agents, so that you can create XML documents to monitor and change the agents as needed.
  • Page 115 XIS Internet Agent configuration file gwia.xml Subdirectory for GroupWise agent console help files help See also Section 7.4, “Internet Agent Queue Directory,” on page NetWare Internet Agent installation directory On a NetWare server, the GroupWise Internet Agent is typically installed in the sys:\system directory.

  • Page 116: Linux Installation Directory

    The gwia.xml file is a specialized Internet Agent configuration file for use in the XIS environment. 8.2.2 Linux Installation Directory Linux agent installation directory /opt/novell/groupwise/agents Subdirectory for GroupWise agent executables Internet Agent executable gwia Internet Agent XIS configuration file gwia.xml...
  • Page 117 Internet Agent log files mmddgwia.nnn See also Section 7.4, “Internet Agent Queue Directory,” on page agents directory On a Linux server, the Internet Agent is always installed in subdirectories of /opt/novell/ groupwise/agents. bin directory The bin directory holds GroupWise executable files. gwia file The gwia file is the Internet Agent executable.
  • Page 118 *.so files These files are Linux shared library files that provide information to the Internet Agent executable. image directory The image directory has subdirectories for agent icons for both color and monochrome displays. share directory The share directory holds agent startup files and files that are used by the agent consoles and Web consoles.

  • Page 119: Windows Installation Directory

    Internet Agent start automatically when the server boots. /etc/opt/novell/groupwise directory The /etc/opt directory is the standard location of application configuration files on Linux. Files that configure how the GroupWise Internet Agent interacts with Linux are stored in the novell/ groupwise subdirectory. gwha.conf file The gwha.conf file is the GroupWise High Availability service configuration file.
  • Page 120 GroupWise Agent Engine gwenv1a.dll Internet Agent program gwia.exe Internet Agent configuration file gwia.cfg Internet Agent online help file gwianxx.chm Internet Agent language information file gwianxx.dll Customized DLL program for MIME gwwww1.dll XIS DLL programs x*10a.dll GroupWise XIS DLL program gwxis10.dll XIS agent configuration file gwia.xml See also...

  • Page 121: Webaccess Agent Installation

    gwianxx.dll files The gwianxx.dll files contain all language-specific information for the Internet Agent. The digit n is a version number. The last two characters xx are a language code. gwwww1.dll file The gwwww1.dll file provides parsing of MIME messages received from the Internet. x*10a.dll and gwxis10.dll files The x*10a.dll and gwxis10.dll programs provide XIS capability for the GroupWise agents, so that you can create XML documents to monitor and change the agents as needed.
  • Page 122 Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console. See Section 8.5, “Apache/Tomcat Installation,” on page 137. See also Section 7.5, “WebAccess Agent Queue Directory,” on page NetWare WebAccess Agent installation directory On a NetWare server, the GroupWise WebAccess Agent is typically installed in the sys:\system directory.

  • Page 123: Linux Installation Directory

    The help directory holds help files and images used by the WebAccess Agent Web console. See “Using the WebAccess Agent Web Console” in “WebAccess” in the GroupWise 7 Administration Guide. 8.3.2 Linux Installation Directory Novell GroupWise installation directory /opt/novell/groupwise Linux agent installation directory agents Subdirectory for GroupWise agent executables WebAccess Agent executable...
  • Page 124 Subdirectory for WebAccess Application files webaccess WebAccess Application configuration file webacc.cfg Communications Manager configuration file commgr.cfg Novell Speller Application configuration file spellchk.cfg LDAP service provider configuration file ldap.cfg Subdirectory for boilerplate configuration files default Subdirectory for WebAccess Application log files logs Subdirectory for users’...
  • Page 125 137. See also Section 7.5, “WebAccess Agent Queue Directory,” on page agents directory On a Linux server, the WebAccess Agent is always installed in subdirectories of /opt/novell/ groupwise/agents. bin directory The bin directory holds GroupWise executable files. gwinter file The gwinter file is the WebAccess Agent executable.
  • Page 126 image directory The image directory has subdirectories for agent icons for both color and monochrome displays. share directory The share directory holds agent startup files and files that are used by the agent consoles and Web consoles. webac70a.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.
  • Page 127 The spellchk.cfg file holds the same configuration information that is stored on the Novell Speller Application object (named NovellSpeller) in eDirectory. For more information, see “Configuring the Novell Speller Application” in “WebAccess” in the GroupWise 7 Administration Guide.
  • Page 128 WebAccess Agent start automatically when the server boots. /var/log/novell/groupwise directory The /var/log directory is the standard location for log files on Linux. All GroupWise agent log files are created in the novell/groupwise subdirectory. domain.webac70a directory The domain.webac70a directory is a domain-specific location for WebAccess Agent log files.

  • Page 129: Windows Installation Directory

    gwdva directory The gwdva directory stores Viewer Agent log files. The first two digits of the filename represent the month; the next two digits represent the day of the month. The three-digit extension is a sequence number for multiple log files created on the same day. For example, 0518web.002 is the second Viewer Agent log file created on May 18.
  • Page 130 The strtweb.bat file is used to start the WebAccess Agent. The batch file specifies the WebAccess startup file. A typical strtweb.bat file includes the following: title Novell GroupWise WebAccess @echo off gwinter.exe @webac70a.waa You run this batch file to start the WebAccess Agent. See “Starting GroupWise...

  • Page 131: Document Viewer Agent Working Directory

    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:\webacc\gwdva.dir Document Viewer Agent working directory gwdva.dir Subdirectory for caching converted documents for repeated display...
  • Page 132 Guide. NOTE: On Linux, Viewer Agent log files are stored in the typical location for log files on Linux var/log/novell/groupwise/gwdva), rather than under the gwdva.dir directory. temp directory The temp directory is used for the temporary files created during HTML conversion. See “Document...

  • Page 133: Monitor Agent Installation

    Monitor Agent event log files mmddmon.nnn Monitor Agent history log files mmddhist.nnn acct 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. Agent Installation Directories 133...
  • Page 134 bin directory The bin directory holds GroupWise executable files. gwmon file The gwmon file is the Monitor Agent executable. You run this executable file to start the Monitor Agent. See “Starting the Linux Monitor Agent as a Daemon” in “Installing GroupWise Monitor”...

  • Page 135: Windows Installation Directory

    /var/log/novell/groupwise directory The /var/log directory is the standard location for log files on Linux. All GroupWise agent log files are created in the novell/groupwise subdirectory. gwmon directory Within the gwmon directory, the Monitor Agent creates two different types of log files. The mmddmon.nnn log files inform you of its processing and any problems it encounters.
  • Page 136 Monitor Agent language information file gwmonxx.dll Customized DLL program for SNMP gwsnmp.dll XIS DLL programs x*10a.dll GroupWise XIS DLL program gwxis10.dll Monitor Agent XIS configuration file gwmon.xml Monitor Agent working directory monwork Monitor Agent directory for accounting files acct Additional Monitor files are integrated into your Web server to support the Monitor Web console. For an example, see Section 8.5, “Apache/Tomcat Installation,”...

  • Page 137: Apache/Tomcat Installation

    gwsnmp.dll file The gwsnmp.dll file provides interaction with the Windows SNMP Service, so that the Monitor Agent can throw SNMP traps. See “Configuring SNMP Trap Notification for Agent Problems” in “Monitor” in the GroupWise 7 Administration Guide. x*10a.dll and gwxis10.dll files The x*10a.dll and gwxis10.dll programs provide XIS capability for the GroupWise agents, so that you can create XML documents to monitor and change the agents as needed.
  • Page 138 GroupWise-specific document root directory webapps/gw GroupWise default Web services page index.html Directory for Novell product files com/novell Directory for Novell class files and properties files collexion Directory for GroupWise Monitor files GWMonitor Subdirectory for Monitor Web console help files help...
  • Page 139 Subdirectory for service provider files providers Subdirectory for template files templates Standard Tomcat directory work Directory for Novell product configuration files sys:\novell Subdirectory for GroupWise Monitor gwmonitor Monitor Application configuration file gwmonitor.cfg Directory for Monitor Application log files logs...
  • Page 140 WEB-INF/web.xml file The web.xml file tells the Web server where the various GroupWise service providers and their configuration files are located. By default, they are located in subdirectories under sys:\novell. GWMonitor/providers directory The providers directory holds the Java* class and properties files for the Monitor provider. For more information, see “Adding or Removing Service...
  • Page 141 A copy of the commgr.cfg file is automatically maintained in the WebAccess Agent queue directory (domain\wpgate\webac70a). spellchk.cfg file The spellchk.cfg file holds the same configuration information that is stored on the Novell Speller Application object (named NovellSpeller) in eDirectory. For more information, see “Configuring the Novell Speller Application”...

  • Page 142: Linux Installation Directory

    The logs subdirectory holds WebAccess Application log files. For more information, see “Controlling WebAccess Application Logging” in “WebAccess” in the GroupWise 7 Administration Guide. 8.5.2 Linux Installation Directory Novell Apache installation directory /opt/novell/httpd Standard Apache directory modules 142 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...
  • Page 143 Apache document root directory for WebAccess and WebPublisher Web server default Web page index.html Directory for Novell product files com/novell Directory for Novell class files and properties files collexion Directory for Novell product image files images Directory for Inso viewer files for viewing attachments inso...
  • Page 144 Subdirectory for template files templates Apache document root directory for Monitor gwmon Web server default page index.html Directory for Novell product files com/novell Directory for GroupWise WebPublisher files gwmonitor Subdirectory for WebPublisher help files help Subdirectory for WebPublisher image files...
  • Page 145 The web.xml file in the gw/WEB-INF directory tells the Web server where the various WebAccess service providers and their configuration files are located. By default, they are located in /opt/novell/groupwise/webaccess. webaccess/providers directory The providers directory holds the Java class and properties files for the WebAccess providers.
  • Page 146 gwmonitor/templates directory The templates directory holds subdirectories for the various file formats used in various browser environments. For more information, see “Modifying Monitor Application Template Settings” in “Monitor” in the GroupWise 7 Administration Guide. 146 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 147: Software Distribution Directory

    Software Distribution Directory Section 9.1, “NetWare/Windows Software Distribution Directory,” on page 147 Section 9.2, “Linux Software Distribution Directory,” on page 153 9.1 NetWare/Windows Software Distribution Directory ® Master copy of GroupWise software software_distribution directory GroupWise agent software agents GroupWise Agent Installation program install.exe ®...

  • Page 148: Grpwise\Software Directory

    GroupWise administrator software admin ® GroupWise snap-ins to ConsoleOne c1admin GroupWise Monitor software monitor GroupWise administrative utilities utility GroupWise Check utility gwcheck GroupWise Generate CSR utility gwcsrgen GroupWise TCP/IP Setup utility setupip Internet connectivity software internet GroupWise Internet Agent software gwia GroupWise WebAccess software webaccess...

  • Page 149: Domain Directory

    startups directory The startups subdirectory contains the default startup files for the GroupWise agents. During 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.

  • Page 150: Po Directory

    wphost.dc file The wphost.dc file is the distribution copy of the data dictionary for rebuilding GroupWise 4.x post office databases (wphost.db files). If the wphost.dc file is missing from a domain, you cannot rebuild GroupWise 4.x post offices in that domain. The original wphost.dc file is located in the domain subdirectory of the GroupWise distribution media.

  • Page 151: Gwcheck Directory

    The pdaconnect directory contains a program to synchronize data between GroupWise and a PDA device. For more information, see the PDA Connect Readme (http://www.novell.com/ documentation/gw7/readmeen_pda_connect/readmeen_pda_connect.html). 9.1.6 gwcheck directory The gwcheck subdirectory contains the GroupWise Check utility that can be made available in the GroupWise client by clicking Tools >...

  • Page 152: Ppforms Directory

    9.1.8 ppforms directory The ppforms subdirectory contains day planner forms for printing GroupWise calendars and tasks. 9.1.9 uwl directory The uwl directory stores the wt61xx.uwl files that are used when users add words to the word list during spell checking. 9.1.10 admin directory The admin subdirectory contains subdirectories for administrative tools that can be used with GroupWise.

  • Page 153: License Directory

    The docs subdirectory contains language-specific subdirectories for the Installation Guide in PDF format. You can find the most up-to-date version of the GroupWise 7 Installation Guide on the GroupWise 7 Documentation Web site (http://www.novell.com/documentation/gw7). 9.2 Linux Software Distribution Directory Master copy of GroupWise software...
  • Page 154 GroupWise client software client Subdirectory for Linux software linux Cross-Platform client installation script install Cross-Platform client package novell-groupwise-gwclient- ver.date.i386.rpm GroupWise Check Utility package novell-groupwise-gwcheck- ver.date.i386.rpm GroupWise client view files ofviews GroupWise administrator software admin GroupWise snap-ins to ConsoleOne package novell-groupwise-admin- ver.date.i386.rpm...

  • Page 155: Opt/Novell/Groupwise/Software Directory

    Directories and files used by the Installation gwinst program 9.2.1 /opt/novell/groupwise/software directory The GroupWise software distribution directory resides initially on the GroupWise Administrator CD. GroupWise Administration is installed directly from the CD. 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.

  • Page 156: Agents Directory

    106. novell-sms-version.i586.rpm The novell-sms-version.i586.rpm file is the Novell Storage Management Services package 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.

  • Page 157: Domain Directory

    init.d. For more information, see “Installing and Starting the Linux GroupWise Agents” in “Installing a Basic GroupWise System” in the GroupWise 7 Installation Guide. 9.2.3 domain directory The domain subdirectory contains the files from which domains are created. wpdomain.dc file The wpdomain.dc file is the distribution copy of the data dictionary for rebuilding GroupWise 4.x domain databases (wpdomain.db...

  • Page 158: Po Directory

    GroupWise 7 Installation Guide. novell-groupwise-gwclient-version.date.i386.rpm The novell-groupwise-client.version.date.i386.rpm file is the GroupWise client package that is installed by the Installation script. You can install the client package manually if necessary. To see what files are installed by the package, see Section 10.2, “Cross-Platform Client on Linux,”...

  • Page 159: Ofviews Directory

    The admin subdirectory contains subdirectories for administrative tools that can be used with GroupWise. novell-groupwise-admin-version.date.i386.rpm file The novell-groupwise-admin.version.date.i386.rpm file is the GroupWise administrator 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.

  • Page 160: Internet Directory

    GroupWise 7 Administration Guide. novell-groupwise-gwia-version.date.i386.rpm file The novell-groupwise-gwia.version.date.i386.rpm file is the Internet Agent 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.2, “Internet Agent Installation,” on page 114.
  • Page 161 GroupWise 7 Administration Guide. novell-groupwise-gwinter-version.date.i386.rpm file The novell-groupwise-gwinter.version.date.i386.rpm file is the WebAccess Agent 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,”...

  • Page 162: License Directory

    Guide and Quick Start in PDF format, along with the Readme in HTML format. You can find the most up-to-date version of the GroupWise documentation on the GroupWise 7 Documentation Web site (http://www.novell.com/documentation/gw7). 9.2.11 gwinst directory The gwinst subdirectory contains supporting files and subdirectories used by the Installation script.

  • Page 163: Groupwise Client Installation Directories

    Section 10.2, “Cross-Platform Client on Linux,” on page 166 Section 10.3, “Cross-Platform Client on Macintosh,” on page 168 10.1 Windows Client ® Installation directory for GroupWise 7.x Windows client software c:\novell\groupwise GroupWise client program grpwise.exe GroupWise Tip of the Day program gwtip.exe GroupWise Notify program notify.exe...

  • Page 164: C:\Novell\Groupwise

    10.1.1 c:\novell\groupwise The GroupWise Windows client installation directory contains all files necessary to run the GroupWise client. The default location is c:\novell\groupwise. For a standard installation, the GroupWise client directory resides on the user’s workstation. For a workstation installation, the GroupWise client directory resides on the network and is run by users on many workstations.

  • Page 165: Gwreload.exe File

    The pdaconnect.exe file is the PDA Connect Installation program for synchronizing data between GroupWise and a PDA device. For more information, see the PDA Connect Readme (http:/ /www.novell.com/documentation/gw7/readmeen_pda_connect/readmeen_pda_connect.html). 10.1.12 ngwguard.dc file The ngwguard.dc file is the data dictionary for building databases in the post office. In Remote mode, the GroupWise client also uses the ngwguard.dc file as the data dictionary for its local...

  • Page 166: Flt Files

    English-speaking people in the United States have different forms from day planners used for various languages in Europe. 10.2 Cross-Platform Client on Linux GroupWise Cross-Platform client installation directory /opt/novell/groupwise/client Desktop shortcut for the Cross-Platform client gwclient.desktop Desktop icon for the Cross-Platform client shortcut gwclient.png...

  • Page 167: Opt/Novell/Groupwise/Client Directory

    Log files generated by the Cross-Platform client logs 10.2.1 /opt/novell/groupwise/client directory The /opt/novell/groupwise/client directory is the default location for the GroupWise Cross-Platform software. The Installation program does not provide the opportunity to specify a different location and typically there is no need to move the software.

  • Page 168: Jre Directory

    wprof.dc file The wprof.dc file is the data dictionary used to create the local copy of the Address Book that resides on the user’s workstation (wprof.db). *.jar files The *.jar files efficiently store information referenced by the Cross-Platform client. The gwclient.jar file contains the Cross-Platform online help information.

  • Page 169: Contents Directory

    10.3.2 Contents directory The Contents directory is the standard location on Macintosh for all files that make up an application. 10.3.3 MacOS directory The MacOS directory contains the JavaApplicationStub file that enables the Cross-Platform client to invoke the Java Virtual Machine (JVM) on Macintosh. 10.3.4 Resources directory The Resources directory is the standard location on Macintosh for files that support an application.
  • Page 170 *.dylib files The *.dylib files are dynamic library files the provide information to the Cross-Platform client program. 170 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...

  • Page 171: Part Iii Documentation Updates

    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 7. 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.
  • Page 172 182 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...
  • Page 173 September 29, 2006 Location Change Directory Structure Diagrams Section 7.1, “Domain Added the mslocal directory in its default location under the domain Directory,” on page 63 directory. ® Section 8.1, “GroupWise Indicated that the DBCopy utility is now installed on NetWare Agent Installation (POA and Windows along with the agents.
  • Page 174 184 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure...
  • Page 175 Section 9.1, “NetWare/ Added the new uwl subdirectory for Windows client user word lists. Windows Software Distribution Directory,” on page 147 Entire Guide Page design reformatted to comply with revised Novell documentation standards. June 15, 2006 (GroupWise 7 SP1) 185...

This manual is also suitable for:

Groupwise 7

Table of Contents