Home

GroupWise 7 Troubleshooting 3: Message Flow

1. Each recipient opens the message in the GroupWise client Each recipient s GroupWise client creates an Opened status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office Message Delivery to a Different Domain 37 Stage Icon Description For mapped and UNC links the MTA scans its input queue in each post office MTA for p for messages to process You can control the rate at which the MTA scans its Recipient s MTA input queues See Adjusting MTA Polling of Input Queues in the Domain and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Domain Guide When it detects the status message the MTA picks it up from the recipient s post office and transfers it to the MTA in progress gwinprog queue From there the MTA in the recipient s domain transfers the status message to the output queue in the sender s domain aa nig The MTA in the sender s domain also polls its domain input queues When it MTA for detects the status message the MTA in the sender s domain picks it up and Senders HTA transfers it to its output queue inthe sender S post office The MTA output queue Domain is the input queue for the POA in the sender s post office A The POA in the sender s post office updates the sender s message database POA for msgnnn db with the Delivered status information and possibly Opened as well Sender s P if the recipient has opened the message Pos
2. 1 blocked txt LJ gwia mib LJ statusxx xml Access control database Database dictionary file used to create the access control database Message for recipients who lack a MIME compliant mail reader Preamble message in various languages List of blocked Internet sites Internet Agent Management Information Base MIB NetWare only File for customizing status messages ee gwia SMTP service daemon home directory de send Outbound hold directory for converting messages into Internet format 3 receive Incoming hold directory for converting messages into GroupWise format E result Send and result files to confirm transmission defer Hold directory for re queued and deferred messages Es work Schedule files for SMTP service operations on deferred messages E dsnhold Delivery Status Notification DSN hold directory 3 help Internet Agent Web console help file directory domain wpgate gwia directory 000 prc 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 gwia cfg The Internet Agent uses the 000 prc directory to process messages gwwork directory The gwwork directory stores temporary files created by the I
3. MTA for Local Domain Description The POA receives the message from the GroupWise client and performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office in case the TCP IP link to the MTA is currently closed The POA then attempts to communicate the message to the MTA by way of TCP IP but the MTA does not respond The POA leaves the copy of the message in the MTA input queue and periodically attempts to contact the MTA When the MTA responds again the POA communicates the message and deletes the copy in the MTA input queue after the TCP IP transmission to the MTA is successful The MTA receives the message and places it into the MTA in progress gwinprog queue The MTA then communicates the message to the POA in the recipient s post office by way of TCP IP When the transmission is successful the MTA deletes the message from the MTA in pr
4. in the post office are databases for library and document information 70 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure The mn in the filenames represents the partition number which is generated by a hashing algorithm to guarantee uniqueness The 0 ffin the filenames represents the library number matching the number on the library directory in which the database is found dmsdnn01 ff db file The dmsdnn01 ff db file in each library holds system data for the library such as library configuration information dmddun01 ff db file The dmddnn0 1 ff db file in each library holds document data for the library Document data is the document property information for documents in the library dmdlnn01 ff db file The dmdlnn01 ff db file in each library holds document logging data for the library Document logging data records all activities performed on documents in the library index directory The index subdirectories in the library subdirectories 1ib000 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 1ib000 in the post office contain an array of subdirectories for holding archived documents The subdirectories are numbered sequentially When the first archive subdirectory reaches its maximum allowable size archived documents are stored in the next sequential directory and so on
5. 0 7 J mtaname Ta postx BN 0 7 J mtaname E gatewayx MN 0 7 J mtaname Ea domainx 0 7 J mtaname Z gwvsscan MTA local working directory MTA log files Message logging directory Message logging files MTA in progress queue directory Priority subdirectories MTA holding directory Processing directory for MTA Priority subdirectories Location identifier Holding directories for post offices Priority subdirectories Location identifier Holding directories for gateways Priority subdirectories Location identifier Holding directories for other domains Priority subdirectories Location identifier Working directory for third party virus scanning programs 78 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure EA mtaconv Work area for 5 x to 4 x conversion mslocal directory mmddxxx nnn files The mslocal directory is the MTA local working directory The work startup switch of the MTA 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 Typical locations for the mslocal directory include sys system on a NetWare server c ona Windows server To move the mslocal directory stop the MTA the copy the mslocal directory along with all its subdirectories to the new location Then re
6. GroupWise System Requirements in Installing a Basic GroupWise System in the GroupWise 7 Installation Guide In this section the Apache Web server and the Tomcat Servlet Engine used to illustrate how GroupWise integrates with your Web server NetWare Installation Directory on page 129 Linux Installation Directory on page 134 NetWare Installation Directory y sys apache Apache installation directory 3 bin Standard Apache directory E cgi bin Standard Apache directory E conf Standard Apache directory httpd conf Main Apache configuration file GWApache2 conf Specialized Apache configuration file for use with GroupWise 3 error Standard Apache directory ee htdocs Apache document root directory L index html Web server default Web page 3 com novell Directory for Novell product files de collexion Directory for Novell class files and properties files Agent Installation Directories 129 Es GWMonitor de help Es images Es images Es inso E webaccess de applets ds help w images w webconsole Es webpublisher de help Es images Es icons Es logs E man E manual En modules el sys tomcat 4 E bin E common Es conf Ta examples EA logs server el shared temp E webapps ROOT T WEB INF LJ web xml an J classes com novell E collexion Directory for GroupWise Monitor files Subdirectory for Monitor Web console help files Subdirectory for Monitor Web console image files
7. docs directory The docs subdirectories in the library subdirectories lib000 in the post office contain an array of subdirectories for storing documents fd0 ff directories The fd0 ff subdirectories in the docs subdirectory in the post office store documents that are equal to or greater than 2 KB in size The 0 ff variable represents hexadecimal number 0 through ff so the subdirectories are named fd0 through fdff The document databases dmxxnn01 ff db files contain pointers to documents stored in the subdirectories of the docs directory ofmsg directory msgnn db file The ofmsg subdirectory in the post office contains as many as 25 databases where messages are stored It serves as centralized storage for all users in the post office A message must be stored only once to be delivered to any number of users in the same post office Historical Note An earlier version of GroupWise designed by WordPerfect Corporation WPCorp was named WP Office Hence the of in ofmsg Some naming conventions were originally preserved for backward compatibility The msgvn db files in the ofmsg subdirectory in the post office are the message databases where users messages smaller than 2 KB are stored To increase database efficiency messages attachments and recipient lists equal to or greater than 2 KB are stored outside the msgnn db files Message Transfer Storage Directories 71 ngwdfr db file guardbak directory in an array of subdir
8. remoten log 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 Group Wise Remote are processed through the priority 1 subdirectory of wpcsout ofs Group Wise Remote scans the wpcsout ofs 1 subdirectory and updates the user db and msg db files with the information received from the master mailbox Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp The Message Transfer Agent MTA was originally named the Connection Server CS Hence the directory names wpcsin and ofs for the input queue though the MTA is not involved in processing messages in your Remote mailbox Some naming conventions were originally preserved for backward compatibility The priority 0 7 subdirectories in the connection output queue wpcsout ofs in the remote mailbox directory parallel those found in the ofs subdirectory in the remote user s post office on the master GroupWise system The remoten log files in the connection output queue wpcsout ofs in the remote mailbox directory are saved versions of the connection logs you can view in Group Wise Remote These log files can be useful for troubleshooting problems with your modem or with your connection to your master GroupWise system 98 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Agent Installation D
9. MTAs for other domains place low priority user messages here The local MTA then routes the messages to recipients post offices The priority 7 subdirectory of the MTA input queue wpcsin in the domain is for low priority status messages routed back to senders in local post offices 62 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure For example MTAs for other domains place status responses to low 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 wptools directory The wptools subdirectory in the domain contains programs that support GroupWise administration Historical Note WP Office the predecessor of GroupWise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wptools Some naming conventions were originally preserved for backward compatibility wpgate directory The wpgate subdirectory in the domain contains a subdirectory for each GroupWise gateway you have installed in your GroupWise system For a list of gateways see Group Wise Gateways http www novell com documentation gwateways GroupWise 5 5 gateways can be used with GroupWise 6 x and 7 wpcsout directory ads directory The wpcsout subdirectory in the domain is the MTA output queue in each domain It contains subdirectories that function as input queues for the processes to which the MTA delivers
10. Run license exe gt select a language common directory The common subdirectory contains Java files used by various components of GroupWise docs 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 gw 7 Linux Software Distribution Directory 2 opt novell groupwise software _ install ds agents linux LJ novell groupwise agents ver date i386 rpm de startups E language J strtupxx poa J strtupxx mta L S99grpwise i domain LJ wpdomain dc LJ gwdom dc J wphost dc J gwpo dc Master copy of GroupWise software GroupWise Installation script GroupWise agent software Subdirectory for Linux software GroupWise agent package Subdirectory for startup files Language specific files POA startup file MTA startup file GroupWise agent startup script POA and MTA Domain data dictionary files Data dictionary for GroupWise 4 x domain databases Data dictionary for GroupWise 7 6 x and 5 x domain databases Data dictionary for GroupWise 4 x post office databases Data dictionary for GroupWise 7 6 x and 5 x post office databases Software Distribution Directory 145 E po LJ ngwguard dc LJ wphost dc LJ gwpo dc client E linux _ install LJ novell groupwise gwclient ver date i386 rpm E
11. Subdirectory for icon images Subdirectory for agent shared files POA startup file for a specific post office MTA startup file for a specific domain Subdirectory for agent console files Subdirectory agent console help files Subdirectory for agent Web console files Subdirectory for agent Web console help files Standard Linux location for application startup scripts Startup script for the POA and MTA Standard Linux location for run level 3 symbolic links Symbolic link to the startup script for the POA and MTA Standard Linux location for run level 5 symbolic links Symbolic link to the startup script for the POA and MTA Standard Linux location for application log files Subdirectory for GroupWise agent log files Post office specific subdirectory for POA log files POA log files Domain specific subdirectory for MTA log files MTA log files Agent Installation Directories 103 agents directory bin directory 3 var opt novell groupwise log Location for script log files LJ mmddlog nnn Log file for the agent startup script grpwise On a Linux server the agents are always installed in subdirectories of opt novell groupwise agents 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 See Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide gwmt
12. 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 The startup file is named the same as the WebAccess Agent object in ConsoleOne The default is webac70a 116 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwdva dva file x 10 nlm files gwinter xml file During installation a customized version ofthe WebAccess Agent startup file is created This customized version has the home startup switch automatically set to the domain directory where the WebAccess Agent s queue directories are located See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide The gwdva dva file is the Document Viewer A gent startup file The Viewer Agent is currently configured completely by startup switches For more information see Document Viewer Agent Startup Switches The x 10 nlm programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed The gwinter xml file is a specialized WebAccess Agent configuration file for use in the XIS environment cache template xx directory help directory The cache template xx directory holds language specific HTML template files for viewing documents in WebAccess and WebPublisher The xx is a two letter language c
13. gwinprog queue From there the MTA in the recipient s domain transfers the status message to the output queue in the sender s domain The MTA in the sender s domain also polls its domain input queues When it detects the status message the MTA in the sender s domain picks it up and transfers it to its output queue in the sender s post office The MTA output queue is the input queue for the POA in the sender s post office The POA in the sender s post office updates the sender s message database msgnnn db with the Delivered status information and possibly Opened as well if the recipient has opened the message When the sender checks the sent items in his or her mailbox in the GroupWise client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message 40 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Message Delivery to and from the Internet Outbound TCP IP Link Open Transfer to the Internet Successful on page 41 Outbound TCP IP Link Closed Transfer to the Internet Delayed on page 41 Outbound Mapped UNC Link Open Transfer to the Internet Successful on page 41 Outbound Mapped UNC Link Closed Transfer to the Internet Delayed on page 43 Inbound TCP IP Link Open Transfer from the Internet Successful on page 43 Inbound Mapped UNC Link Open Transfer from the Internet Successful on page 43 O
14. is used to separate actions within a step and items in a cross reference path A trademark symbol E etc denotes a Novell trademark An asterisk denotes a third party trademark When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms the pathname is presented with a backslash Users of platforms that require a forward slash such as Linux should use forward slashes as required by your software About This Guide 9 When a startup switch can be written with a forward slash for some platforms or a double hyphen for other platforms the startup switch is presented with a forward slash Users of platforms that require a double hyphen such as Linux should use double hyphens as required by your software User Comments We want to hear your comments and suggestions about this manual and the other documentation included with this product Please use the User Comment feature at the bottom of each page of the online documentation or go to www novell com documentation feedback html and enter your comments there 10 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 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 Message Delivery in the Local Post Office on page 13 Message Delivery
15. 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 in Optimizing the MTA in the GroupWise 7 Administration Guide The priority 4 subdirectory of the MTA input queue wpcsin in the post office is for normal priority user messages routed to recipients in other post offices domains or systems Message Transfer Storage Directories 69 5 directory 6 directory 7 directory For example the GroupWise client places normal priority user messages here The MTA then routes the messages to the appropriate destinations Most messages in your GroupWise system pass through the priority 4 subdirectory You can increase throughput for the priority 4 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 The priority 5 subdirectory of the MTA input queue wpcsin in the post office is for normal priority status messages routed back to senders in other post offices domains or systems For example the GroupWise client and local POA place status responses to normal priority user messages here The MTA then routes the status messages to the appropriate post offices so senders mailboxes can be updated with current message status The priority 6 subdirectory of the MTA input
16. wpcsout directory aore aer Se a have eb eee ba be bees ba ee ba ee ds 63 Mitaname filen sani le E eck eee i See we ee CAE a Sane Ae Os BOS eR eS BA Bane 65 wpdomain db file lt o ses s c m bo wart ee ee a be ee ade Se aes 65 Contents 5 wpdomain de file s i 4 oa BO bh dd A BE SR a be BRE LEE ED ORE hae ee BY 65 wphostideshile E u mo teiaa e a Yo Mok YA eR Bes BO Le Pe ek a Ba el oe 65 QWdOM dC file ye bok eile alee E ee RE te a eee be ee ee Se Se aa i 66 OWPo dc TIS We corse Stee im cece te Moose al ee HOR a dt Regge MOS HS GD Tae A A oh tn Raye i 66 agentinstallitkt s ias n AGS Ue aa Ee A ea AA Eo ee eh hag do 66 Post Office Directory nass os ets Doh eh hee oe Buen ae EAE e Pei ee ed BS 66 post office directory cs me fae te Be PR eA ee ee a ee RP es OE ee ee E g 68 WPCSINGIFECIOnY woos ae ei he Se a BE e E PE EG SEP eS a ae OE EE Oe ee 68 Gwdms directory ese dpa wee aan aged Ede AA eens Ee Atk a Ba Pe eco ea a 70 ONMNSG dIFECtOry 2 6h e eek 2 Re Be RU BOR E o e OE a A ets ok 71 ofuser directory x bee ee be ce ea re a oe A ee oe ee eS 72 offiles directory ado aus eee Ee eH al ek ey Rete ia ee i te ee eh ok he es BA ee 73 ofviews directory se ei as ee ae ee EEA A AA Ba EG A Aare oe x 73 OIWOFK CIFECIONY the ee ok SA Rabe plate eed Sack bee AE wea E Sk Reale bel be Robe ee Re BS 73 ofdirect directory oi aor ee E eae E ae PE a a Pe ee SP ee oe ai 74 WPCSOUL CIFECIOLY comicios sek Pee oie ed ak ae ee Se le ag ea a a
17. 07 GA TEWA YX Stage Icon Description TD The user sends a message to recipients in a post office in a different domain Sender pen In this diagram the access mode setting for the local post office is Client Server Only Message Delivery to a Different Domain 27 Stage Sender s GroupWise Client E POA for Sender s Post Office D POA for Sender s Post Office 5 MTA for Sender s Domain MTA for Sender s Domain MTA for Recipient s Domain MTA for Recipient s Domain Icon HTA MTA HTA HTA Description The GroupWise client communicates the message to the POA by way of TCP IP The POA receives the message from the GroupWise client and performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office in case the TCP IP link to the MTA is currently closed The POA then communicates t
18. Different Post Office 17 Stage Icon Description de The POA for the sender s post office updates the sender s message POA in database msgnnn db with the Delivered status information and possibly Sender s POA Opened as well if the recipient has opened the message Post Office A The POA communicates the status to the sender s GroupWise client by way we f TCP IP POA for Local S Post Office POA a When the sender checks the sent items in his or her mailbox in the Sender pen GroupWise client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message 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 Re a P0Aa a GATEWAY DOMAIN L 0 Stage Icon Description T The user sends a message to recipients in a different post office in the same Sender pen domain In this diagram the access mode setting in the local post office is Client Server Only D The GroupWise client communicates the message to the POA by way of Sender s TCP IP GroupWise Client 18 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage E POA for Sender s Post Office POA for Sender s Post Office MTA for Local Domain
19. ES docs grpwise software directory GroupWise client software GroupWise client installation configuration file GroupWise client for Windows GroupWise client installation program GroupWise client addon programs Program to make GroupWise your browser e mail program Program to display tips each time GroupWise starts GroupWise client view files ZENworks supporting files GroupWise administrator software GroupWise snap ins to ConsoleOne GroupWise Monitor software GroupWise administrative utilities GroupWise Check utility GroupWise Generate CSR utility GroupWise TCP IP Setup utility Internet connectivity software GroupWise Internet Agent software GroupWise WebAccess software GroupWise Software License Agreement in multiple languages Java files used by GroupWise programs GroupWise Installation Guide The Group Wise software distribution directory resides initially on the GroupWise distribution CD GroupWise Administration is installed directly from the CD In addition during installation you create a software distribution directory on your network from which you subsequently install the GroupWise agents and GroupWise client software The default software distribution directory is grpwise software agents directory The agents subdirectory contains all files associated with Group Wise agents Post Office Agent POA Message Transfer Agent MTA GroupWise Target Service Agent GWTSA 140 GroupWise 7 Troubl
20. GroupWise 7 6 x 5 x post office databases LJ ngwguard db G ngwguard de Guardian database G ngwguard fok Data dictionary for databases G ngwguard rfl Guardian database backup J ngwcheck db LJ agentInstall txt Guardian database roll forward log GWCheck control database List of information provided during agent installation post_office directory Conceptually a post office contains mailboxes for a set of network users The users on the post office send and receive messages through their mailboxes 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 wpcsin directory The wpcsin subdirectory in the post office is the MTA input queue in each post office It contains eight priority subdirectories to handle different types of message traffic Outgoing user messages are queued by priority for routing to recipients in other post offices Outgoing status messages are queued by priority for routing back to senders post offices Outgoing Busy Search requests are queued for routing to other post offices so users schedules can be checked GroupWise Remote requests are queued for routing to GroupWise Remote users master mailboxes When a new message arrives the MTA routes it to the appropriate destination For mapped and UNC links the MTA scans its input que
21. Host authentication configuration file MIME encoding configuration file Database dictionary for the access control database Message for non MIME recipients Preamble message in various languages File for customizing status messages Subdirectory for startup files Internet Agent startup script 146 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure de webacces GroupWise WebAccess software y linux Subdirectory for Linux software LJ novell groupwise gwinter ver date i386 rpm GroupWise WebAccess Agent package J novell groupwise webaccess ver date i386 rpm GroupWise WebAccess Application package a root Subdirectory for boilerplate supporting files J mimetype cfg MIME encoding configuration file LJ gwac dc Database dictionary for the access control database gwgs ini Gateway identifier file E startup Subdirectory for startup files LJ S99grpwise wa WebAccess Agent startup script 3 webserver Web server to support WebAccess and Monitor linux Subdirectory for Linux software LJ rpm Apache Tomcat and related packages ay license GroupWise Software License Agreement in multiple languages 3 docs GroupWise Readme Quick Start and Installation Guide Es gwinst Directories and files used by the Installation program opt novell groupwise software directory The Group Wise software distribution directory resides initially on the GroupWise distribution CD GroupWise Administration is installed directly from the CD In addition duri
22. The original gwdom dc file is located in the domain subdirectory of the GroupWise distribution media Historical Note WP Office the predecessor of GroupWise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain db Some naming conventions were originally preserved for backward compatibility The wphost dc file is the distribution copy of the data dictionary for rebuilding Group Wise 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 There is also a copy in the po subdirectory Historical Note WP Office the predecessor of Group Wise 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 The gwpo dc file is the distribution copy of the data dictionary for creating and rebuilding GroupWise 7 6 x and GroupWise 5 x post office databases wphost db files If the gwpo dc file is missing from a domain you cannot create or rebuild Group Wise 7 6 x 5 x post offices in that domain The original gwpo dc file is located in the domain directory of the GroupWise CD There is also a copy in the po directory Historical Note WP Office the predecessor of Group Wi
23. Transfer Pull 2 a aaa a 38 4 Message Delivery to and from the Internet 41 Outbound TCP IP Link Open Transfer to the Internet Successful oaa aaa a 41 Outbound TCP IP Link Closed Transfer to the Internet Delayed 0 000000 ee eee ee 41 Outbound Mapped UNC Link Open Transfer to the Internet Successful 0 0 o 41 Outbound Mapped UNC Link Closed Transfer to the Internet Delayed 0 0 43 Inbound TCP IP Link Open Transfer from the Internet Successful 0 e e 43 Inbound Mapped UNC Link Open Transfer from the Internet Successful o 43 5 Message Delivery to and from GroupWise Remote 47 Mapped UNC Link for Hit the Road a 47 Modem Link to the Remote User through the Async Gateway 0 o eo 49 6 Administrative Database Update 53 TCP IP Link between the Domain and the Post Office 2 2 0 ee eo 53 Mapped UNC Link between the Domain and the Post Office 0 200002002 2s 54 Part II Directory Structure Diagrams 7 Message Transfer Storage Directories 59 Domain Directory 64 La al ic e te A A AA E Sth ee 59 domain directory se cae bea ee a A A A A ae ae 60 WPESINOITEC ONYE sinensis AA Sole Seeds fe Be BB ee ete Oe Be 60 wptools directory o e cosc cr A ee eh ee be ee es 63 Wpgate directory 6 joo ee eee we alee eet ee BER ee eee eed oe est BES e 63
24. WebAccess Agent This information enables the WebAccess Application to communicate with the WebAccess Agent For more information see Configuring the GroupWise Service Provider in WebAccess in the GroupWise 7 Administration Guide A copy of the commer cfg file is automatically maintained in the WebAccess Agent queue directory domain wpgate webac 70a default directory The default directory holds boilerplate versions of the webpub cfg and commgr cfg files logs 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 Linux Installation Directory 3 opt novell http Novell Apache installation directory E bin Standard Apache directory E build Standard Apache directory Es doc Standard Apache directory E logs Standard Apache directory Es modules Standard Apache directory 134 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure E etc opt novell http a conf Es conf d E gconf d E init El logrotate d E ssiconf d Ea etc opt novell tomcat4 J catalina properties Li jk2 properties _ server xml _ tomcat users xml L tomcat4 conf _ web xml E init d dal logrotate d E var opt novell Mi ow LJ index html E com novell E collexion Es images E inso Es webaccess ds applets de help Es images Z webconsole E webpublis
25. WordPerfect Corporation WPCorp was named WP Office Hence the of in ofviews Some naming conventions were originally preserved for backward compatibility ofwork directory The ofwork subdirectory in the post office is a working directory for GroupWise Remote Historical Note An earlier version of GroupWise designed by WordPerfect Corporation WPCorp was named WP Office Hence the of in ofwork Some naming conventions were originally preserved for backward compatibility Message Transfer Storage Directories 73 ofdirect directory The ofdirect subdirectory in the working directory ofwork in the post office is used by GroupWise Remote for direct connections Historical Note An earlier version of GroupWise designed by WordPerfect Corporation WPCorp was named WP Office Hence the of in ofdirect Some naming conventions were originally preserved for backward compatibility wpcsout directory ofs 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 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 wpcsout for the MTA output queue Some naming conventions were originally preserved for backwar
26. a sent item Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office If client server mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects a new message the MTA picks up the message from the sender s post office and transfers it to the MTA in progress gwinprog queue From there the MTA in the sender s domain transfers the message to the output queue in the recipient s domain The MTA in the recipient s domain also polls its input queue When it detects a new message the MTA in the recipient s domain picks up the message from its domain input queue and transfers it to the MTA in progress gwinprog queue From there the MTA in the recipient s domain t
27. at the MTA agent console or in ConsoleOne a restart request is placed here The MTA processes the request and restarts 1 directory The priority 1 subdirectory of the CSS input queue wpcsout css in the domain is for service requests of the next highest priority For example each time the statistics are updated on the MTA agent console a statistics request is placed here The MTA then gathers the statistics and displays them on the MTA agent console 2 directory The priority 2 subdirectory of the css input queue wpcsout css in the domain is for non priority requests The problem subdirectory of the MTA output queue wpcsout in the domain is where the MTA places message files that cannot be delivered because they are damaged in some way Message files in the problem directory must be handled by the GroupWise administrator See Message Is Dropped in the problem Directory in the Domain in GroupWise 7 Troubleshooting 2 Solutions to Common Problems 64 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure mtaname file The mtaname file in the domain provides the domain name associated with the domain directory structure This can help you locate the domain information for the directory structure in ConsoleOne It can also help you check links between MTAs wpdomain db file The wpdomain db file in the domain is the domain database It contains all administrative information for the domain In the primary dom
28. being backed up You can use the GroupWise Time Stamp GWTMSTMP utility to ensure that Group Wise user databases include the dates when they were last backed up restored and retained For more information see Group Wise Time Stamp Utility in Databases in the GroupWise 7 Administration Guide 104 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure lib directory share directory letc init d directory The lib directory holds GroupWise library files fil files These files contain all language specific information for the POA and the MTA The first five characters of the filename are the agent name The last two characters xx are a language code so files These files are Linux library files that provide information to the GroupWise agent executables image directory The image directory has subdirectories for agent icons for both color and monochrome displays The share directory holds agent startup files and files that are used by the agent consoles and Web consoles post_office poa The POA startup file contains startup switches for the POA Switch settings placed in the POA startup file override comparable options set for the POA in ConsoleOne During installation a customized version of the strtupxx poa file named post_office poa is created in the share directory This customized version has the home startup switch automatically set to the post office directory the POA will service Se
29. db file The wprov50 db file in the wpcsout ofs directory is the downloadable system Address Book for Remote client users By default it is automatically re created once a day to keep it up to date See Performing Nightly User Upkeep in Post Office Agent in the GroupWise 7 Administration Guide guide The ads subdirectory of the MTA output queue wpcsout in the post office is the input queue for the POA admin thread in each post office It contains priority subdirectories where administrative messages are queued for processing Historical Note The POA admin thread was previously part of a separate agent the Administration Agent ADA which was originally named the Administration Server ADS Hence the directory name ads Some naming conventions were originally preserved for backward compatibility 0 directory The priority 0 subdirectory of the POA admin thread input queue wpcsout ads in the post office 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 wpcsout ads in the post office is for service requests of the next highest priority For example a directory synchronization request that could not be performed when the POA admin thread received it in its domain input queue would be placed here in the post office for later processing 2 directory The priority 2 subdirectory of the POA admin thread input q
30. directory holds files used by the Monitor Application gwmonitor cfg file The gwmonitor cfg file holds the same configuration information that is stored on the Monitor Application object named Group WiseMonitor in eDirectory For more information see Configuring the Monitor Application in Monitor in the GroupWise 7 Administration Guide default directory The default directory holds boilerplate versions of the gwmonitor cfg file and the monitor xml file logs directory The logs subdirectory holds Monitor Application log files For more information see Modifying Monitor Application Log Settings in Monitor in the GroupWise 7 Administration Guide 126 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure users directory The users subdirectory holds session files for Monitor users letc init d directory The etc init d directory is the standard location for Linux startup scripts grpwise ma file The grpwise ma script is created automatically during installation You can use the script to start restart stop and display status information about the Monitor Agent For more information about starting the Monitor Agent see Starting the Monitor Agent in Monitor in the GroupWise 7 Administration Guide rc3 d directory The rc3 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 3 multi user boots to a text mode login
31. ee WPCSIN 0 7 Lao ADS 0 7 es 7 OFS Lo 7 P wphost db GWINPROG L 9 7 gt MSHOLD DOMAINMS POSTX L_ 9 7 GATEWAYY L 9 7 DOMAINY L 9 7 Stage Actor Action T The administrator uses the GroupWise Administrator snap in in ConsoleOne to GroupWise da add modify or delete a GroupWise object in a single domain single post office GroupWise system An object could be a GroupWise user resource distribution list post office secondary domain and so on ConsoleOne performs the following actions Updates the domain database wpdomain db to reflect the addition modification or deletion performed in ConsoleOne Creates an administrative message in the priority 2 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 progress gwinprog queue From there the MTA transfers the administrative message to the output queue in the post office The MTA output queue is the input queue for the POA in the post office The administrative message notifies the POA a GroupWise object has been added modified or deleted Historical Note In earlier versions of GroupWise this function of the POA was handled by a separate agent the Administration Agent ADA The ADA no longer exists in GroupWise The POA picks up the message from its administrative input queue in the post office then updates the post office database wphost db to re
32. ee oe ee ee AA A eee Ss 157 gwrel0ad exe TG onire ane Bk eR a ee 2 hoe ee BAe ee ee ek i RY as a de de 157 Gwsyneexe file fe eo ane GPs ene Sa a Ee A a eee ae Ba eG Ar we 157 gwguard de fil ek a BR ee en Be ee ee eS bh BE U eo hoe bea tek a 157 Wprohdc Tle eee eo ee Ee a ek ee A a ee eS Ee 157 AUTOS af a vest Bee Load ita Gere Agee eee Ee Dea eas cre a BS aE ae as wa ee 157 A A eee RN ad eg ede i a ee 157 TAIETIOSy oe dea A aes Ri a eR a Rane Te a Y Ee ka ea E 158 CAME 3025 46 ag eee eke Glen wae wo ae ek Wave bo eles Be eas eee a Gee EE 158 ONVIEWS AITEC ONY lt teo FR i Ae eae A ae a Bee tt E a ithe aha Fae ee 158 ppformsidirectory iis puna tog ee Eee eve A AG og A A A tale a 158 Cross Platform Clienton LINUX e 408 2 e ee bok ee ea OE ke Re ed Pe ee ee Ee 158 opt novell groupwise client directory o oo aaa a a 159 BI AIrECtTO A pt Suite eee Bee EE AA oe AOE a a a ad Sis a PES 159 lib dire CtOryic lt one rata aa A a a a onde aa e Ghee sl 159 Je AIMTEC I N aens ik ke sie SEO RK RL Se A OE Ree E a e ln Pe a A e AAE eo 160 logs directory 3 2 nae ere en adda See bee RR a A ee E 160 Cross Platform Client on Macintosh 2 aaa 160 Applications GroupWise app directory 2 o 161 Contents directory ies maoe dtar se E Ae See A aS bok Rog eee bok Ave we ee a 161 MacOS directory 35 or a ee Ne A A ae ee PP oe ee OEE ee ES 161 Resources directory Zoo essen a ta eo ee es O A ARE be area ks 2 tl eee 161 lib director o aa aen
33. file created on May 18 106 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Ivar opt novell groupwise log directory The var directory is used for various types of files The log file for the agent startup script is created in the opt novell groupwise log subdirectory mmddlog nnn The mmddlog nnn file stores messages from the agent startup script grpwise as it tries to start the GroupWise agents Windows Installation Directory c grpwise E c grpwise Windows agent installation directory LJ gwenv1a dll LJ gwpoa exe LJ gwmta exe J strtupxx poa LJ strtupxx mta LJ post_office poa _ domain mta LJ gwpoanxx chm J gwmtanxx chm J gwpoanxx dll LJ gwmtanxx dll J gwsnmp dll L gwwww1 dll L x 10 dll Ll agent xml de help GroupWise Agent Engine Post Office Agent POA program Message Transfer Agent MTA program Boilerplate POA startup file need post poa Boilerplate MTA startup file need domain mta POA startup file for a specific post office MTA startup file for a specific domain POA online help file MTA online help file POA language information files MTA language information files Customized DLL program for SNMP Customized DLL program for MIME XIS DLL programs XIS agent configuration files Subdirectory for GroupWise agent Web console help files When you first install Group Wise Administration the GroupWise agents are initially installed in platform specific s
34. have been downloaded to your GroupWise Remote mailbox It contains a list of all available libraries and lookup tables for each library index directory The index directory in the remote document management subdirectory gwdms in the remote mailbox directory contains the QuickFinder index for the documents contained in the library wpgwsend directory The wpgwsend subdirectory in the remote mailbox directory holds compressed files that contain outgoing messages requests or both When a connection to your master GroupWise system is established GroupWise Remote uploads the files across the link Message Transfer Storage Directories 97 Historical Note WP Office Remote the predecessor of GroupWise Remote was originally designed by WordPerfect Corporation WPCorp Hence the name wpgwsend Some naming conventions were originally preserved for backward compatibility wpgwrecv directory The wpgwrecv subdirectory in the Remote mailbox directory holds compressed files that contain messages or other information that have been downloaded from your master mailbox Group Wise Remote decompresses the files and places the message files into the wpcsout ofs 1 directory Historical Note WP Office Remote the predecessor of GroupWise Remote was originally designed by WordPerfect Corporation WPCorp Hence the name wpgwrecv Some naming conventions were originally preserved for backward compatibility wpcsoutlofs directory 0 7 directories
35. libgwia so Internet Agent shared library file LJ libgwia_ui so Internet Agent user interface shared library file Ll so Supporting shared library files 2 image Subdirectory for icon images Es share Subdirectory for agent shared files J gwia cfg Internet Agent configuration file E agtcon Subdirectory for agent console files E help Subdirectory agent console help files Es webcon Subdirectory for agent Web console files Es help Subdirectory for agent Web console help files 2 letc init d Standard Linux location for application startup scripts J grpwise ia Startup script for the Internet Agent E rc3 d Standard Linux location for run level 3 symbolic links J S99grpwise ia Symbolic link to the startup script for the Internet Agent Agent Installation Directories 111 agents directory bin directory lib directory share directory E rc5 d Standard Linux location for run level 5 symbolic links LJ S99grpwise ia Symbolic link to the startup script for the Internet Agent 3 var log Standard Linux location for application log files E novell groupwise Subdirectory for GroupWise agent log files Es domain gwia Domain specific subdirectory for Internet Agent log files LJ mmddgwia nnn Internet Agent log files See also Internet Agent Queue Directory on page 82 On a Linux server the Internet Agent is always installed in subdirectories of opt novell groupwise agents The bin directory holds GroupWise executable files gwia file The g
36. log file created on May 18 Windows Installation Directory En c gwmon Windows Monitor Agent installation directory J gwenv1a dll GroupWise Agent Engine LJ gwmon exe Monitor Agent program L monitor xml Monitor Agent configuration file Agent Installation Directories 127 c gwmon gwenv1a dll file gwmon exe file monitor xml gwmonxx dll files LJ gwmonxx dll Monitor Agent language information file gwsnmp dll Customized DLL program for SNMP x 10 dll XIS DLL programs LJ gwmon xml XIS agent configuration file a monwork Monitor Agent working directory Additional Monitor files are integrated into your Web server to support the Monitor Web console For an example see Apache Tomcat Installation on page 129 On a Windows server the Monitor Agent can be installed in any directory you choose The default location is c gwmon The Monitor Agent desktop icon is set up to include the full path to whatever directory you choose The gwenvla dll file is the GroupWise Agent Engine a program that is shared by all GroupWise agents It provides the following services to the agents Database management File operations 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 The gwmon exe file is the Monitor Agent program You run this executable file to start the Monitor Agent See St
37. messages 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 wpcsout for the MTA output queue Some naming conventions were originally preserved for backward compatibility The ads subdirectory of the MTA output queue wpcsout in the domain is the input queue for the MTA admin thread in each domain It contains priority subdirectories where incoming administrative messages are queued for processing When a new administrative message arrives the MTA admin thread performs the requested action Historical Note The MTA admin thread was previously part of a separate agent the Administration Agent ADA which was originally named the Administration Server ADS Hence the directory name ads Some naming conventions were originally preserved for backward compatibility 0 directory The priority 0 subdirectory of the MTA admin thread input queue wpcsout ads in the domain is for service requests that demand an immediate response from the MTA admin thread For example when you create or delete a post office in ConsoleOne a restart request is placed here The domain MTA admin thread processes the request and then restarts 1 directory The priority 1 subdirectory of the MTA admin thread input queue wpcsout ads in the domain is for service requests of the next highest
38. new message has arrived The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client communicates the Opened status message to the POA by way of TCP IP The POA for the recipient s post office communicates the status message to the MTA for the recipient s domain by way of TCP IP The MTA for the recipient s domain places the status message into the in progress gwinprog queue The MTA for the recipient s domain communicates the status message to the MTA for the sender s domain by way of TCP IP 32 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon Description i nig The MTA for the sender s domain places the status message into the MTA in MTA for progress gwinprog queue Sender s HTA Domain KE 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 HTA Domain a9 nt 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 POA well if the recipient has opened the message Post Office wr The POA for the sender s post office communicates the status to the sender s POA for GroupWise client by way of TCP IP Sender s POA Post Office When the sender chec
39. post office communicates the status message to the MTA for the recipient s domain by way of TCP IP The MTA for the recipient s domain places the status message into the MTA in progress gwinprog queue The MTA for the recipient s domain communicates the status message to the MTA for the sender s domain by way of TCP IP Message Delivery to a Different Domain 29 Stage Icon Description a The MTA for the sender s domain places the status message into the MTA in MTA for progress gwinprog queue Sender s HTA Domain da 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 HTA Domain KE The POA for the sender s post office updates the sender s message database POA for p msgnnn db with the Delivered status information and possibly Opened as well Sender s POA if the recipient has opened the message Post Office en The POA for the sender s post office communicates the status to the sender s POA for GroupWise client by way of TCP IP Sender s POA Post Office 23 When the sender checks the sent items in his or her mailbox in the GroupWise Sender pen client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message TCP IP Link Closed Transfer between Domains Delayed This message flow diagram illustrates how a GroupWise message travels from one user to another
40. priority directories from 0 7 The Internet Agent puts messages only in the 4 directory The Message Transfer Agent polls the domain wpgate gwia wpcsin fd0 7f directory and moves the file to the post_office wpcsout ofs 0 7 directory The POA polls its input queue regularly When it detects a new message the POA in the recipient s post office performs the following actions 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 the message appears in the recipient s Mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 76 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and recipient lists larger than 2 KB are also handled as attachments GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Actor Action 5 The Notify component of the recipient s GroupWise client notifies the Recipient s recipient that a new message has arrived GroupWise Client E Each recipient opens the message in the GroupWise client Recipient pen Message Delivery to and from the Internet 45 46 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Mess
41. priority status responses Es 4 Normal priority messages E 5 Normal priority status responses ey 6 Low priority messages Es 7 Low priority status responses Es wptools Supporting program directory wpgate GroupWise gateway directory En wpcsout MTA output queue directory Message Transfer Storage Directories 59 E ads MTA admin thread input queue directory wo Restart requests Es 1 Directory synchronization requests de 2 Database updates E 3 Reserved not currently used E 4 Reserved not currently used E 5 Reserved not currently used E 6 Reserved not currently used E 7 Reserved not currently used E css MTA input queue directory for administrative messages E 0 MTA restart requests Es 1 Statistics requests Es 2 Other non priority administrative requests Es 3 Reserved not currently used a 4 Reserved not currently used E 5 Reserved not currently used Es 6 Reserved not currently used E 7 Reserved not currently used E problem Directory for undeliverable messages L mtaname Domain name identifier E wpdomain db Domain database LJ wpdomain dc Data dictionary for 4 x domain databases J wphost dc Data dictionary for 4 x post office databases Ll gwdom dc Data dictionary for 5 x 6 x and 7 domain databases J gwpo dc Data dictionary for 5 x 6 x and 7post office databases J Agentinstall txt List of information provided during agent installation domain directory Within the Group Wise system a domain is hierarchi
42. prompt without The X Window System The symbolic link to the grpwise ma script is S99grpwise ma It is created if you choose during installation to have the Monitor Agent start automatically when the server boots rc5 d directory The rc5 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 5 multi user boots to The X Window System login dialog box The symbolic link to the grpwise ma script is S99grpwise ma It is created if you choose during installation to have the Monitor Agent start automatically when the server boots Ivar 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 The mmddhist nnn log files record dumps of all MIB values gathered during each poll cycle For more information about log files see Configuring Monitor Agent Log Settings in Monitor in the GroupWise 7 Administration Guide 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 0518mon 002 is the second Monitor Agent
43. queue wpcsin in the post office is for low priority user messages routed to recipients in other post offices domains or systems For example the GroupWise client places low priority user messages here The MTA then routes the messages to the appropriate destinations 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 For example the GroupWise client and local POA place status responses to low priority user messages here The MTA then routes the status messages to the appropriate post offices so senders mailboxes can be updated with current message status gwdms directory dmsh db file The gwdms subdirectory in the post office is the Document Management Services DMS directory in each post office It contains the document libraries associated with the post office The dmsh db file in the document management subdirectory gwdms in the post office is a database shared by all libraries in the post office It contains a list of all available libraries and lookup tables for each library lib0001 ff directories The lib000 subdirectories in the gwdms subdirectory in the post office contain the libraries for the post office with one library per directory You can create a maximum of 256 libraries in a post office dmxxnn01 ff db files The dmxxnn01 ff db files in the library subdirectories lib000
44. queue wpcsin in the post office is for service requests of the next highest priority For example Remote with a direct connection places requests here for routing to GroupWise Remote users master mailboxes The POA places outgoing status messages to Group Wise Remote users here for routing to the async connection 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 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 For example the Group Wise client places high priority user messages here The MTA then routes the messages to the appropriate destinations 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 in Optimizing the MTA in the GroupWise 7 Administration Guide The priority 3 subdirectory of the MTA input queue wpcsin in the post office is for high priority status messages routed back to senders in other post offices domains or systems For example the GroupWise client and local POA place status responses to high priority user messages here The MTA then routes the status messages to the appropriate post offices so senders
45. rita ala Ele aap end o Bie ae ek wale Pon eng cea A us 161 EVEN LO RR ee a 161 8 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure About This Guide This Novell Group Wise Ti roubleshooting 3 Guide provides diagrams to help you understand the structure and functioning of your GroupWise system The guide is divided into the following sections Message Flow Diagrams on page 11 Directory Structure Diagrams on page 57 Other sources of troubleshooting assistance include Novell Support http support novell com Novell Support Knowledgebase http support novell com search kb_index jsp GroupWise 7 Support Forums http support novell com forums 2gw html Novell GroupWise Support Community http support novell com products groupwise GroupWise Cool Solutions http www novell com coolsolutions gwmag index html Additional Documentation For additional GroupWise documentation see the following guides at the GroupWise 7 Documentation Web site http www novell com documentation gw7 Installation Guide Administration Guide Multi System Administration Guide Interoperability Guide GroupWise Client User Guides Documentation Updates For the most recent version of the GroupWise 7 Troubleshooting 3 Guide visit the Group Wise 7 Documentation Web site http www novell com documentation gw7 Documentation Conventions In Novell documentation a greater than symbol gt
46. so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client creates an Opened status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the status message the MTA picks it up from the sender s post office and transfers it to the MTA in progress gwinprog queue Because the sender s post office is open the MTA can immediately transfer the message to the output queue in the sender s post office The MTA output queue is the input que
47. the GroupWise Service Provider in WebAccess in the GroupWise 7 Administration Guide A copy of the commgr cfg file is automatically maintained in the WebAccess Agent queue directory domain wpgate webac 70a default directory The default directory holds boilerplate versions of the webpub cfg and commgr cfg files logs directory The logs subdirectory holds WebPublisher Application log files For more information see Controlling WebAccess Application Logging in WebAccess in the GroupWise 7 Administration Guide cache template xx directory The cache template xx directory holds language specific HTML template files for viewing documents in WebAccess and WebPublisher The xx is a two letter language code You can change the location of the cache directory as described in Modifying WebPublisher Settings in WebAccess in the GroupWise 7 Administration Guide The etc init d directory is the standard location for Linux startup scripts Agent Installation Directories 121 grpwise wa file The grpwise wa script is created automatically during installation You can use the script to start restart stop and display status information about the WebAccess Agent For more information about starting the WebAccess Agent see Linux Setting Up GroupWise WebAccess in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide rc3 d directory The rc3 d directory holds symbolic links to sc
48. to a Different Post Office on page 15 Message Delivery to a Different Domain on page 27 Message Delivery to and from the Internet on page 41 Message Delivery to and from GroupWise Remote on page 47 Administrative Database Update on page 53 Message Flow Diagrams 11 12 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Message Delivery in the Local Post Office The GroupWise 7 client functions optimally using client server access to the post office For an explanation of client server access mode see Post Office Access Mode in Post Office Agent in the GroupWise 7 Administration Guide Access Mode Client Server on page 13 Access Mode Client Server This message flow diagram illustrates how a GroupWise message travels from one user to another in the local post office when the client and POA communicate by way of TCP IP OFUSER L userxxx db OFFILES L_ FDO 7F WPCSOUT ADS L 9 7 OFS L9 7 Stage Icon Description 0 The user sends a message to recipients in the same post office The Sender access mode setting for the post office is Client Server Only The GroupWise client communicates with the POA by way of TCP IP Sender s GroupWise Client Message Delivery in the Local Post Office 13 14 Stage E POA for Local Post Office D POA for Local Post Office D Recipient s GroupWise Client Recipient O Recipient s GroupWise
49. to your GroupWise system for delivery Messages from the GroupWise client in Caching mode are processed through the priority 1 subdirectory of wpcsin When you send a message in Caching mode the GroupWise client connects to your GroupWise system It polls the wpcsin 1 directory and compresses any outgoing messages requests or both into a file If the compressed file totals over 50 KB additional compressed files are created The Group Wise client then moves the compressed files into the wpgwsend directory Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp The Message Transfer Agent MTA was originally named the Connection Server CS Hence the directory name wpcsin for the input queue although the MTA is not involved in processing messages in your Caching mailbox Some naming conventions were originally preserved for backward compatibility 0 7 directories The priority 0 7 subdirectories in the connection input queue wpcsin parallel those found in the wpcsin directory in your post office wpcsoutlofs directory The wpcsout ofs directory is the output queue for the connection that transfers messages from your Online mailbox Messages from your Group Wise system are processed through the priority 1 subdirectory of wpcsout ofs The Group Wise client scans the wpcsout ofs 1 subdirectory and updates the user db and msg db files with the information received from your On
50. variety of file types from within Group Wise chm files chm files contain the online documentation for all components of GroupWise chm files are typically located in the same directory with the executable programs they support ofviews directory The ofviews directory contains platform specific subdirectories of view files for use by the Group Wise client Historical Note An earlier version of GroupWise designed by WordPerfect Corporation WPCorp was named WP Office Hence the of in ofviews Some naming conventions were originally preserved for backward compatibility win directory The win subdirectory contains view vew files for use by the Group Wise client It also contains initialization ini files to control display of views ppforms directory The ppforms directory contains day planner forms for printing GroupWise calendars and tasks bfp files bfp files are form description files that contain binder filler and page attributes for forms prs files prs files are print resource files that indicate which forms are available for which languages For example day planners used by English speaking people in the United States have different forms from day planners used for various languages in Europe Cross Platform Client on Linux Es opt novell groupwise client GroupWise Cross Platform client installation directory gwclient desktop Desktop shortcut for the Cross Platform client Ll gwclient png
51. 0 7 subdirectory of the sender s MTA input queue If client server mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 The MTA for the sender s domain polls its input queue as specified by Scan Cycle in Agent Settings in ConsoleOne When it detects a new message the MTA recognizes that it must be sent through a gateway and places the message in its output queue in the program s directory structure domain wpgate gwia wpcsout a 0 7 The Internet Agent picks up the file in binary encrypted format from the wpcsout ia 0 7 directory and converts it It UUencodes any attachments unless the Internet Agent is configured with the mime switch to use MIME specifications or unless the sender specified the MIME foreign domain If MIME is specified the Internet Agent encodes the message attachments with the appropriate encoding scheme as specified in the mimetype cfg file When the message file is built the Internet Agent saves it with S as the first character of the filename and places the file in the wpgate gwia send directory The Internet Agent processes the message in the domain wpgate gwia send directory and sends the message to the destination host across the Internet The Internet Agent creates a file R that records the SMTP reply codes error messages or transmission confirmation in the wpgatelgwialresult direct
52. 7 Administration Guide novell groupwise gwinter version date i386 rpm file The novell groupwise gwinter version date 1386 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 WebAccess Agent Installation on page 115 novell groupwise webaccess version date i386 rpm file The novell groupwise webaccess version date i386 rpm file is the WebAccess Application 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 WebAccess Agent Installation on page 115 and Apache Tomcat Installation on page 129 root directory The root directory contains boilerplate versions of the configuration files that are installed to the WebAccess Agent root directory under the domain directory For more information see WebAccess Agent Queue Directory on page 88 S99grpwise wa file The S99grpwise ia file is the WebAccess Agent startup script During installation it is named grpwise ma and placed in etc init d If you choose to have the Internet Agent start automatically when the server reboots the Installation script places symbolic links to it named S99grpwise ma in the rc3 d and rc5 d subdirectories of etc init d For more information see Linux Setting Up GroupWise WebAccess in Installing GroupWi
53. Agent message processing directory Es cmd Not currently used E gwwork Hold directory for temporary files using during processing J mmddlog nnn Log files L acct Accounting file J set Settings file for screen colors log levels and so on L stat Statistics file for Internet Agent operation J proc Process lock file indicating that the Internet Agent is running J pulse tmp Temporary file to verify Internet Agent operation 3 wpcsin MTA input queue directory E 0 7 Message priority subdirectories E wpcsout MTA output queue Es QW XXXX System defined directory E 0 7 Message priority subdirectories E problem Hold directory for damaged outbound messages Es gwhold Message hold directory Ta qfiles Delayed delivery hold directory Es gwprob Hold directory for damaged inbound messages E gwchars Directory for character conversion tables El save Directory for old configuration files from reinstalls or upgrades J gwia cfg Internet Agent configuration file for startup switches l route cfg Route configuration file to customize routing J gwauth cfg LJ mimetype cfg LJ exepath cfg LJ frgnames cfg J xspam cfg Host authentication configuration file MIME encoding configuration file for various file types Configuration file pointing ConsoleOne to the gwia cfg file Foreign domain name configuration file Anti spam configuration file GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure LJ gwac db J gwac dc J preamble txt L preamble all
54. Client 8 POA for Local Post Office O POA for Local Post Office Sender Description The POA receives the message from the GroupWise client and performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments The POA also performs the following actions for the recipient Creates a pointer in each recipient s user database userxxx db to the message in the message database msgnnn db so the new message appears in the recipient s mailbox Updates the message in the message database msgnnn db with a Delivered status for each recipient The POA communicates to the GroupWise client by way of TCP IP that a new message has arrived The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client communicates the Opened status to the POA by way of TCP IP The POA receives the Opened status from the GroupWise client
55. Desktop icon for the Cross Platform client shortcut 3 bin Subdirectory for the Cross Platform client executable J groupwise Cross Platform client executable 158 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure E ib Ll gwenlxxx fil LJ ngwguard dc LJ wprof dc LJ jar _ so E jre Es logs opt novell groupwise client directory Subdirectory for Cross Platform client library files Cross Platform client language resource files Data dictionary for local databases on the user s workstation Data dictionary for the local copy of the Address Book Java archive jar files used by the Cross Platform client Shared library files used by the Cross Platform client Java Runtime Environment JRE used by the Cross Platform client Log files generated by the Cross Platform client 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 gwclient desktop file The gwclient desktop file create the GroupWise Cross Platform client shortcut on your Linux desktop gwclient png file The gwelient png file is the GroupWise icon used for Cross Platform client shortcut bin directory The bin directory is the standard Linux location for executable files groupwise file The groupwise file is the GroupWise Cross Platform clien
56. Directory for Novell product image files Directory for Inso viewer files for viewing attachments Directory for GroupWise WebAccess files Subdirectory for WebAccess client properties files Subdirectory for WebAccess client help files Subdirectory for WebAccess client image files Subdirectory for WebAccess Application Web console help files Directory for GroupWise WebPublisher files Subdirectory for WebPublisher help files Subdirectory for WebPublisher image files Standard Apache directory Standard Apache directory Standard Apache directory Standard Apache directory Standard Apache directory Tomcat installation directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Web server information directory Web server configuration file Directory for Novell product files Directory for language specific morphology files 130 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure da GWMonitor En providers Es templates de webaccess de providers E templates e webpublisher Ta providers Es templates work w sys novell Es gwmonitor J gwmonitor cfg E logs Es webaccess Lj webacc cfg O commgr cfg O spellchk cfg O Idap cfg logs Ba temp E users w webpublisher J webpub cfg E commgr cfg Ee default E lo
57. KB in the post_office offiles fd0 76 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office If client server mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects a new message the MTA picks up the message from the sender s post office and transfers it to the MTA in progress gwinprog queue From there the MTA for the sender s domain would normally transfer the message to the output queue in the recipient s domain However in this transfer pull configuration the MTA for the sender s domain does not have access to the recipient s domain Therefore the MTA for the sender s domain transfers the message into the appropriate priority 0 7 subdirectory in the transfer directory in its own domain It is now the job of the MTA for the re
58. NLM program to start the Message Transfer Agent See Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide 100 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure strtupxx poa file strtupxx mta file The POA startup file contains startup switches for the POA Switch settings placed in the POA startup file override comparable options set for the POA in ConsoleOne The xx in the startup filename represents a two letter language code During installation a customized version of the POA startup file named post_office POA is created This customized version has the home startup switch automatically set to the post office directory the POA will service See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide 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 This customized version has the home startup switch automatically set to the domain directory the MTA will service See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide nlm_agentnxx hlp files Online help is available by pressing F1 at the agent c
59. NY deviene as ae Red E a BR ee A AT ee RS a ad e sk tice 94 Wwpcsoutlofs directory gt ir rar a a a A A A ata 94 Wpgwsenid dIreClORY i icce o a a e de Relea ds Ee ee ett Bb Els 94 WPOWrecv directory ees ete ee ee a Se SA Be Foe SOE Se Se A 95 Remote Mailbox Directory si iia EAS aS NE E E EA ee EES OS ES 95 remote mailbox directory 2 orar m eop ee ee Re Be ey pE ea ee ee em a 95 WPCSIN GIFECIONY e 0 24 40 seh bh le ee Be Veh Re AE Ba Boe EM Ge Patek Eat wit Pp ae oe ES 96 rofdata directo sch eek ee ee ee A ee ea ee a ee 96 Wpgwsend direCtOry s 2 puri te Sed Goethe SP tReet Ai oe Sek ESR AY as Edo Ose hee 97 WpgWrecv directory iio 4 4 5 gece Aap eee a oe pania a a ee Ge Ge ee BE OG I Ba as 98 Wwpcsoutlofs directory eist a rr BR I be OE BAS Re le ek Sa ee OEE E Ok ls 98 Agent Installation Directories 99 GroupWise Agent Installation POA and MTA ee 99 NetWare Installation Directory o sioi Senei aae e a E e e a a e a E a e a e E aO E OEE oe 99 Linux Installation Directory 2 a e aa a e an e e a a aS a e D a e a A p p a 102 Windows Installation Directory aaa 107 Internet Agent Installation 2 a 109 NetWare Installation Directory 2 1 a 109 Linux Installation Directory lt o 2 acici ma pa raosra tudta sed tad hadr eedit ia da aaa 111 Windows Installation Directory o ooa aa a 114 WebAccess Agent Installation o oo aa a 115 NetWare Installation Directory sos sois eaei ee ee 115 Linux Installation Dir
60. Novell GroupWise www novell com 7 TROUBLESHOOTING 3 MESSAGE FLOW August 15 2005 AND DIRECTORY STRUCTURE Novell Legal Notices Novell Inc makes no representations or warranties with respect to the contents or use of this documentation and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose Further Novell Inc reserves the right to revise this publication and to make changes to its content at any time without obligation to notify any person or entity of such revisions or changes Further Novell Inc makes no representations or warranties with respect to any software and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose Further Novell Inc reserves the right to make changes to any and all parts of Novell software at any time without any obligation to notify any person or entity of such changes Any products or technical information provided under this Agreement may be subject to U S export controls and the trade laws of other countries You agree to comply with all export control regulations and to obtain any required licenses or classification to export re export or import deliverables You agree not to export or re export to entities on the current U S export exclusion lists or to any embargoed or terrorist countries as specified in the U S export laws You agree to not use deliverables f
61. TA were closed see TCP IP Link Closed Transfer between Post Offices Delayed on page 18 The MTA receives the message and places it into the MTA in progress gwinprog queue The MTA then communicates the message to the POA in the recipient s post office by way of TCP IP When the transmission is successful the MTA deletes the message from the MTA in progress queue If the TCP IP link to the recipient s post office were closed the message would be placed in the closed post office s holding queue in the MTA s mslocal directory for later transfer The resulting message flow would be parallel to what occurs when a domain is closed See TCP IP Link Closed Transfer between Domains Delayed on page 30 for a similar message flow that illustrates how messages to closed locations are handled GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage POA for Recipient s Post Office O POA for Local Post Office O Recipient s GroupWise Client Recipient O Recipient s GroupWise Client a POA for Recipient s Post Office KE MTA for Local Domain a MTA for Local Domain Icon POA POA MTA MTA Description When it receives the new message the POA for the recipient s post office performs the following actions 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 databa
62. The symbolic link to the grpwise ia script is S99grpwise ia It is created if you choose during installation to have the Internet Agent start automatically when the server boots Ivar 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 gwia directory The domain gwia directory is a domain specific location for Internet Agent log files Agent Installation Directories 113 Within the domain gwia directory the Internet Agent creates log files mmddgwia nnn to inform you of its processing and any problems it encounters For more information about log files see Using Internet Agent Log Files in Internet Agent in the GroupWise 7 Administration Guide 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 0518gwia 002 is the second Internet Agent log file created on May 18 Windows Installation Directory c grpwise gwia gwenv1a dll file gwia exe file Es c grpwise gwia Windows Internet Agent installation directory LJ gwenv1a dll GroupWise Agent Engine J gwia exe Internet Agent program Ll gwia cfg Internet Agent configuration file J gwianxx chm Internet Agent online help file J gwianxx dll Internet Agent language information fil
63. WebAccess Agent handles this just as the Internet Agent does For more information see Customizing MIME Content Type Mappings in Internet Agent in the GroupWise 7 Administration Guide gwcache db file gwac db file gwac dc file The gwcache db file is like a catalog of documents in the files directory When a user requests a document WebAccess checks gwcache db and if the document is already in the files directory it can be quickly returned to the user If the document is not yet in gwcache db it is retrieved recorded in gwcache db converted for display in HTML format and then returned to the user The gwac db file is the access control database that stores information about the classes of service you have created For more information see Maintaining the Access Database in WebAccess in the GroupWise 7 Administration Guide The gwac dc file is the data dictionary file from which the gwac db is created 90 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Caching Mailbox Directory E WMovelAgroupwiselgwxxxxxx ds rofdata J msg db _ user db J wprof db J wprof dc LJ ngwguard db J ngwguard dc LJ ngwguard rfl O ngwguard fok LJ puxxxxx db LJ ngwcheck db LJ gwcheckn log Lj remoten log E gwdms L dmsh db L dmxxnno1 ff db E docs E index de index w wpcsin 0 7 Es wpesoutlofs MN 0 7 E wpgwsend E wpgwrecv novel groupwise gwxxxxxx directory GroupWise Caching mailb
64. a Some naming conventions were originally preserved for backward compatibility The msg db file in the remote data directory rofdata in the remote mailbox directory is the remote equivalent of the msgrn db files in the ofmsg directory in the post office where your master mailbox is located The msg db file contains messages you have downloaded from your master mailbox The user db file in the remote data directory rofdata in the remote mailbox directory is the remote equivalent of the userxxx db files in the ofuser directory in the post office where your master mailbox is located The user db file contains user information you have downloaded from your master mailbox The wprof db file in the remote data directory rofdata in the Remote mailbox directory contains the remote version of the GroupWise Address Book if you have downloaded it Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the wprof in wprof db Some naming conventions have been preserved for backward compatibility 96 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure wprof dc file ngwguard db file ngwguard dc file puxxxxx db files gwdms directory 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 GroupWise Remote des
65. a file The gwmta file is the Message Transfer Agent executable You run this executable file to start the Message Transfer Agent See Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide xml files The agent xml files are specialized agent configuration files for use in the XIS environment strtupxx poa file The strtupxx poa file is the boilerplate file from which a post office specific post_office poa file is created in the share directory The xx in the startup filename represents a two letter language code strtupxx mta file The strtupxx mta file is the boilerplate file from which a domain specific domain poa file is created in the share directory The xx in the startup filename represents a two letter language code gwesrgen file The gwesrgen file is the GroupWise Generate CSR utility If you enable SSL for the agents they 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 in Security 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
66. age Delivery to and from GroupWise Remote GroupWise client users can still access information in their mailboxes even when not connected to the network Mapped UNC Link for Hit the Road on page 47 Modem Link to the Remote User through the Async Gateway on page 49 Mapped UNC Link for Hit the Road This message flow diagram illustrates how a user who will be away from the network prepares to access GroupWise from a remote location WPCSIN s Lo WPCSOUT L_aps C WPCSIN L 07 OFMSG L msqd 24 db OFUSER wprof db Dn el WPGWSEND DOMAINIMS LFDO 7F WPGWRECY POSTA WPCSOUT WPCSOUT L 9 7 ADS POSTE PY 0 7 GATEWAYX 6 7 F L 9 7 OFIWORK POA DOMAINS L_OFDIRECT L 9 7 L CONNECTION ID Message Delivery to and from GroupWise Remote 47 48 Stage Remote User GroupWise Remote GroupWise Remote D MTA for Remote User s Domain POA for Remote User s Post Office MTA for Remote User s Domain Icon a 5 MTA POA MTA Description The GroupWise user requests items from the master mailbox to be downloaded to the Remote mailbox in preparation for disconnecting from the master GroupWise system For example the user could be preparing a laptop computer for use away from the network using the Hit the Road feature of the GroupWise client When the GroupWise Remote user sends a request for items from the master mailbox GroupWis
67. ain the wpdomain db file contains all administrative information for your entire Group Wise 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 You can re create your entire GroupWise system from the primary domain wpdomain db file however if the primary domain wpdomain db file becomes unusable you can no longer make administrative updates to your GroupWise system In a secondary domain the wpdomain db file contains administrative information about that secondary domain only In GroupWise 7 6 x and 5 x domains the data dictionary for the wpdomain db file is the gwdom dc file In groupwise 4 x domains the data dictionary is the wpdomain dc file As a result wpdomain db files have different structures schemas depending on whether they were created for 7 6 x 5 x or 4 x domains Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain db Some naming conventions were originally preserved for backward compatibility wpdomain dc file wphost dc file The wpdomain dc file in the domain is the data dictionary for rebuilding GroupWise 4 x domain databases wpdomain db files in secondary domains If the wpdomain dc file is missing from the primary domain you cannot rebuild Group Wise 4 x secondary domains The original wpdomain d
68. al entities GroupWise e mail distribution lists and so on gwcheck exe file The gwchek exe file is the program that checks and repairs GroupWise databases located on users workstations or other locations not accessible to the Mailbox Library Maintenance feature of Console See GroupWise Check in Databases in the GroupWise 7 Administration Guide htrsetup exe file The htrsetup exe file is the setup program for Hit the Road which creates your Remote mailbox See Remote Mode in Client in the GroupWise 7 Administration Guide 156 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwimpexe exe file The gwimpexe exe file is the GroupWise E Mail Importer Utility which enables you to import supported POP3 IMPA4 accounts into GroupWise See Importing POP3 and IMAP4 Accounts in Working with Items in Your Mailbox in the GroupWise 7 Windows Client User Guide gwmailto exe file The gwmailto exe file is the program that integrates the Group Wise client with your Web browser If you select Internet Browser Mail Integration during installation the GroupWise client becomes the default e mail program on your workstation See Setting Up the GroupWise Client in Installing the GroupWise Windows and Cross Platform Clients in the GroupWise 7 Installation Guide gwreload exe file The gwreload exe file is the program that restarts the Group Wise client when you switch between Online Ca
69. also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office in case the TCP IP link to the MTA is currently closed The POA then communicates the message to the MTA for the sender s domain by way of TCP IP and deletes the copy in the MTA input queue because the TCP IP transfer to the MTA was successful To see what would happen if the TCP IP link to the MTA were closed see TCP IP Link Closed Transfer between Post Offices Delayed on page 18 The MTA for the sender s domain receives the message and places it into the MTA in progress gwinprog queue The MTA for the sender s domain then attempts to communicate the message to the MTA for the recipient s domain by way of TCP IP but the recipient MTA does not respond Therefore the MTA stores the message in its holding queue for the recipient s domain in the mshold directory When the MTA in the recipient s domain responds again the MTA for the sender s domain transfers the delayed message from the domain holding queue to the MTA in the recipient s domain by way of TCP IP The MTA for the recipient s domain receives the message and places it into the MTA in progress gwinprog queue The MTA for the recipient s domain then communicates the message to the POA in the recipient s post office by way of TCP IP Message Delivery to a Different Domain 31 Stage O POA for Recipi
70. and updates the message in the message database with the Opened status for each recipient who opens the message The POA communicate the Opened status to the sender s GroupWise client by way of TCP IP When the sender checks the sent items in his or her mailbox in the GroupWise client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Message Delivery to a Different Post Office The MTA handles message transfer between post offices TCP IP Link Open Transfer between Post Offices Successful on page 15 TCP IP Link Closed Transfer between Post Offices Delayed on page 18 Mapped UNC Link Open Transfer between Post Offices Successful on page 21 Mapped UNC Link Closed Transfer between Post Offices Delayed on page 23 For an explanation of link types and link protocols see Understanding Link Configuration in Domains in the GroupWise 7 Administration Guide TCP IP Link Open Transfer between Post Offices Successful 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 open DOMANX 0 7 Stage Icon Description T The user sends a message to recipients in a different post office in the sa
71. andard Tomcat file E examples Standard Tomcat directory 3 gw gt var opt novell gw al gwmon gt var opt novell gwmon Es tomcat docs Standard Tomcat directory E webdav Standard Tomcat directory gw index html file The index html file in the gw directory is the initial page for accessing the WebAccess client See Starting GroupWise WebAccess in the GroupWise 7 WebAccess Client User Guide gw WEB INF web xml file 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 For more information see Adding or Removing Service Providers in WebAccess in the GroupWise 7 Administration Guide webaccess templates directory The templates directory holds subdirectories for the various file formats used in various browser environments For more information see Modifying WebAccess Application Template Settings in WebAccess in the GroupWise 7 Administration Guide webpublisher providers directory The providers directory holds the Java class and properties files for the WebPublisher providers For more information see Adding or Removing Service Providers in WebAccess in the GroupWise 7 Administration Guide webpu
72. arting the Monitor Agent in Monitor inthe GroupWise 7 Administration Guide The monitor xml file stores the Monitor Agent configuration information that you establish in the Monitor Agent console as described in Configuring the Monitor Agent in Monitor in the GroupWise 7 Administration Guide The gwmonxx dll files contain all language specific information for the WebAccess Agent The last two characters xx are a language code 128 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwsnmp dll file x 10 dil files gwmon xml file monwork directory 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 The x 10 dll programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed The gwmon xml file is a specialized agent configuration file for use in the XIS environment The monwork directory is used for temporary files used in calculating system performance as described in Measuring Agent Performance in Monitor in the GroupWise 7 Administration Guide Apache Tomcat Installation WebAccess WebPublisher and Monitor rely on the presence of a Web server in order to fulfil their functions A number of Web servers are supported See
73. bility The ngwguard db file is the guardian database for your Caching mailbox It is parallel in function to the ngwguard db file in the post office The ngwguard dc file is the data dictionary for building the databases in the GroupWise Caching mailbox It is parallel in function to the ngwguard dc file in the post office The ngwguard rfl file is a roll forward transaction log of every database transaction that has taken place since the last copy of the ngwguard fbk file was created It is parallel in function to the ngwguard rfl file in the post office 92 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure ngwguard fbk puxxxxx db files ngwcheck db file gwcheckn log remoten log gwdms directory The ngwguard fbk file fall back copy of the ngwguard db file It is parallel in function to the ngwguard fbk file in the post office The puxxxxx db files are databases for replicated items such as shared folders These databases prevent conflicts between user names of shared items from users in other post offices and user names in your own post office They are parallel to the puxxxxx db files in the post office The ngwcheck db file tracks GroupWise Check threads and the databases being checked In the Group Wise client GroupWise Check is run using Tools gt Repair Mailbox The gwcheckn log file records any errors that occurred during mailbox repair For assistance with GroupWise Check errors see GroupW
74. blisher templates directory The templates directory holds subdirectories for the various file formats used in various browser environments For more information see Modifying WebPublisher Application Template Settings in WebAccess in the GroupWise 7 Administration Guide gwmon index html file The index html file in the gwmon directory is the login Web page for GroupWise Monitor if you have provided a password as described in Configuring Authentication and Intruder Lockout for the Monitor Web Console in Monitor in the GroupWise 7 Administration Guide See also Using the Monitor Agent Consoles Agent Installation Directories 137 gwmon WEB INF web xml file The web xml file in the gwmon WEB INF directory tells the Web server where the Monitor service provider and its configuration file are located By default they are located in opt novell groupwise gwmonitor 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 Providers in Monitor in the GroupWise 7 Administration Guide 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 138 GroupWise 7 Troubles
75. by the Installation script You can install the package manually if necessary To see what files are installed by the package see Monitor Agent Installation on page 125 and Apache Tomcat Installation on page 129 novell groupwise monitor version date i386 rpm file The novell groupwise monitor version date 1386 rpm file is the GroupWise Monitor Application 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 Monitor Agent Installation on page 125 and Apache Tomcat Installation on page 129 S99grpwise ma file The S99grpwise ma file is the Monitor Agent startup script During installation it is named grpwise ma and placed in etc init d If you choose to have the Monitor Agent start automatically when the server reboots the Installation script places symbolic links to it named S99grpwise ma in the rc3 d and rc5 d subdirectories of etc init d For more information see Installing the Linux Monitor Agent in Installing GroupWise Monitor in the GroupWise 7 Installation Guide internet directory gwia directory The internet subdirectory contains subdirectories for GroupWise components that provide and support Internet connectivity The gwia subdirectory contains the Internet Agent software used to connect GroupWise systems across the Internet and to allow GroupWise users to exchange e mail with users of vari
76. c file is located in the domain subdirectory of the software distribution directory or on the GroupWise CD Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain dc Some naming conventions were originally preserved for backward compatibility The wphost dc file in the domain is 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 directory of the software distribution directory or on the GroupWise CD 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 Message Transfer Storage Directories 65 gwdom dc file The gwdom dc file in the domain is the data dictionary for creating and rebuilding GroupWise 7 6 x and 5 x domain databases wpdomain db files in secondary domains If the gwdom dc file is missing from the primary domain you cannot create or rebuild Group Wise 7 6 x 5 x secondary domains The original gwdom dc file is located in the domain directory of the software distribution directory or on the GroupWise distribution media gwpo dc
77. cally the highest level object It organizes post offices into a logical grouping for addressing and routing purposes Each user in the domain has an address that consists of the user s GroupWise user ID the user s post office name and the domain name user post_office domain The explicit name is not displayed in the Address Book but is stored in the domain database wpdomain db wpcsin directory The wpcsin subdirectory in the domain is the MTA input queue in each domain It contains eight priority subdirectories to handle different types of message traffic Incoming user messages are queued by priority for routing to recipients post offices in the local domain 60 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 0 directory 1 directory 2 directory Incoming status messages are queued by priority for routing to senders post offices in the local domain Outgoing administrative messages are queued for replication to other domains In a routing domain messages pass through this directory on their way to the next domain When a new message arrives the MTA routes it to the appropriate destination For TCP IP links the MTA is notified immediately when a message arrives for processing 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 and Pos
78. cation webacc cfg file The webacc cfg file holds the same configuration information that is stored on the WebAccess Application object named GroupWiseWebAccess in eDirectory For more information see Configuring the WebAccess Application in WebAccess in the GroupWise 7 Administration Guide commgr cfg file The commgr cfg file holds the same configuration information that is stored on the GroupWise Provider object named Group WiseProvider in eDirectory including the IP address port number number of threads 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 in WebAccess in the GroupWise 7 Administration Guide A copy of the commgr cfg file is automatically maintained in the WebAccess Agent queue directory domain wpgate webac 70a 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 in WebAccess in the GroupWise 7 Administration Guide Idap cfg file The Idap cfg file holds the same configuration information that is stored on the LDAP Provider object named LDAPProvider in eDirectory For more information see Configuring the LDAP Service Provider i
79. ces the data dictionary for the wphost db file is the gwpo dc file In GroupWise 4 x post offices the data dictionary is the wphost dc file As a result wphost db files have different structures schemas depending on whether they were created for GroupWise 7 6 x 5 x or 4 x post offices Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp Post offices were originally called hosts Hence the name wphost db Some naming conventions were originally preserved for backward compatibility The gwpo dc file in the post office is the data dictionary for creating and rebuilding GroupWise 7 6 x and 5 x post office databases wphost db files If the gwpo dc file is missing from a post office and its domain you cannot create or rebuild Group Wise 7 6 x 5 x post offices in that domain The original gwpo dc file is located in the domain directory of the software distribution directory or on the GroupWise CD ngwguard db file The ngwguard db file in the post office is the guardian database See Information Stored in the Post Office in Post Office Agent in the GroupWise 7 Administration Guide ngwguard dc file The ngwguard dc file in the post office is the data dictionary for building the following databases in the post office ngweguard db guardian database dmxxnn01 ff db document management databases msgnn db message databases userxxx db user database
80. ching and Remote modes See Using Caching Mode and Using Remote Mode in the GroupWise 7 Windows Client User Guide gwsync exe file The gwsync exe file is the program that synchronizes your Online and Caching mailboxes See Using Caching Mode in the GroupWise 7 Windows Client User Guide ngwguard dc file The ngwguard dc file is the data dictionary for building databases in the post office GroupWise Remote also uses the ngwguard dc file as the data dictionary for its local databases wprof dc file The wprof dc file is the data dictionary for the GroupWise Remote Address Book wprof db Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the wprof in wprof dc Some naming conventions were originally preserved for backward compatibility dil files dll files are dynamically linked libraries of program code used by executable programs Language independent dll files are typically located in the same directory with the executable programs they support Language specific dll files are grouped into subdirectories by language ocx files ocx files are OLE custom controls For example ocx files control the Address Book and name completion GroupWise Client Installation Directories 157 fit files flt files are graphics filters used by the Inso viewers incorporated into the GroupWise client The viewers enable you to view a wide
81. cipient s domain to pick up or pull the message from the sender s domain to the recipient s domain See Using a Transfer Pull Configuration in Message Transfer Agent in the GroupWise 7 Administration Guide The MTA for the recipient s domain polls its input queue in the local domain and any transfer directories in other domains The transfer pull configuration is the only situation where an MTA scans directories outside its own directory structure When it detects a new message in a transfer directory of another domain the MTA picks up or pulls the message from the other domain and transfers it to the MTA in progress gwinprog queue From there the MTA for the recipient s domain transfers the message to the output queue in the recipient s post office The MTA output queue is the input queue for the POA in the recipient s post office Message Delivery to a Different Domain 39 Stage POA for Recipient s Post Office o Recipient s GroupWise Client Recipient Recipient s GroupWise Client MTA for Recipient s Domain MTA for Sender s Domain KE POA for Sender s Post Office Sender Icon MTA HTA POA na Description The POA polls its input queue regularly When it detects a new message the POA in the recipient s post office performs the following actions Adds the message to the message database msgnnn db corresponding to the one assigned to the se
82. contains supporting programs for the client AutoUpdate feature See Enabling AutoUpdate in Client in the GroupWise 7 Administration Guide internet directory gwia directory The internet subdirectory contains subdirectories for GroupWise components that provide Internet connectivity The internet gwia subdirectory contains the GroupWise Internet Agent software used to connect GroupWise systems across the Internet and to allow GroupWise users to exchange e mail with users of various Internet e mail programs For information about Internet Agent files and directories see Internet Agent Queue Directory on page 82 and Internet Agent Installation on page 109 For information about the Internet Agent see Internet Agent in the GroupWise 7 Administration Guide 144 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure webaccess directory The internet webaccess subdirectory contains the GroupWise WebAccess software which allows users to access their GroupWise mailboxes from a Web browser For information about WebAccess files and directories see WebAccess Agent Queue Directory on page 88 WebAccess Agent Installation on page 115 and Apache Tomcat Installation on page 129 For information about WebAccess see WebAccess in the GroupWise 7 Administration Guide license directory The license subdirectory contains the GroupWise Software License Agreement in multiple languages
83. 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 Within the post_office poa directory the POA creates log files mmddpoa nnn to inform you of its processing and any problems it encounters For more information about log files see Using POA Log Files in 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 The three digit extension is a sequence number for multiple log files created on the same day For example 0518poa 002 is the second POA log file created on May 18 domain mta directory The domain mta directory is a domain specific location for MTA log files Within the domain mta directory MTA creates log files mmddxxx nnn to inform you of its processing and any problems it encounters For more information about log files see Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide The first two digits of the filename represent the month the next two digits represent the day of the month the next three characters indicate what program created the log The three digit extension is a sequence number for multiple log files created on the same day For example 0518mta 002 is the second MTA log
84. d messages E domain wpgate webac70a GroupWise WebAccess Agent home directory 000 prc LJ mmddweb nnn WebAccess Agent log file processing directory WebAccess Agent log files 3 wpcsin MTA input queue directory 3 0 7 Message priority subdirectories Es wpcsout MTA output queue 3 webxxxx System defined directory for the WebAccess Agent 3 0 7 Message priority subdirectories 3 problem Hold directory for damaged outbound messages E gwhold Hold directory for delayed delivery messages E gwprob Hold directory for damaged inbound messages En files Directory for documents attached to messages E template Directory for templates for viewing documents LJ commgr cfg J comint cfg LJ mimetype cfg LJ gwcache db LJ gwac db LJ gwac dc Communications Manager configuration file Communications initialization configuration file MIME encoding configuration file for various file types Database catalog of documents in the files directory Access control database Database dictionary file used to create the gwac db file 88 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure domain wpgate webac70a directory The domain wpgate webac70a directory is the WebAccess Agent home directory where WebAccess Agent configuration files and queue directories are located The name is established when you install the WebAccess Agent The default is wpgate webac70a in the domain directory You can change the location using the home startup sw
85. d 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 ofmsg directory to increase database efficiency Historical Note An earlier version of GroupWise designed by WordPerfect Corporation WPCorp was named WP Office Hence the of in offiles Some naming conventions were originally preserved for backward compatibility The fd0 6 subdirectories in the offiles subdirectory in the post office store messages attachments and recipient lists that are equal to or greater than 2 KB in size The nn variable represents hexadecimal number 0 through f6 so the subdirectories are named fd0 through fdf6 The message databases msgin db files contain pointers to messages attachments and recipient lists stored in the subdirectories of offiles ofviews directory The ofviews subdirectory in the post office contains subdirectories for Group Wise client platforms Within the platform specific subdirectories for example win are view vew files that create the various views displayed in the Group Wise client The gwviewxx ini and ofviewxx ini files configure the standard views on the menus where users select views The gwviewxx ini file configures GroupWise 7 6 x and 5 5 standard views The ofviewxx inI file configures standard views from earlier versions of GroupWise Historical Note An earlier version of GroupWise designed by
86. d compatibility The ofs subdirectory of the mta output queue wpcsout in the post office is the POA input queue in each post office It contains eight priority subdirectories to handle different types of message traffic Incoming user messages are queued by priority for delivery to recipients mailboxes in the local post office 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 0 directory The priority 0 subdirectory of the POA input queue wpcsout ofs in the post office is for service requests that demand an immediate response from the POA For example the MTA places Busy Search requests here so the POA can check recipients schedules and quickly return the schedule information to the sender 1 directory The priority 1 subdirectory of the POA input queue wpcsout ofs in the post office is for service requests of the next highest priority For example the MTA places requests from GroupWise Remote users for items in their master mailboxes here The POA then processes the messages and returns the requested items 74 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 2 directory The p
87. d file Agent Installation Directories 109 L x 10 nlm XIS NLM programs LJ gwia xml XIS Internet Agent configuration file E help Subdirectory for GroupWise agent console help files See also Internet Agent Queue Directory on page 82 NetWare Internet Agent installation directory gwenn65 nIm file gwia nIm file gwia cfg file gwianxx fil files On a NetWare server the GroupWise Internet Agent is typically installed in the sys system directory You can choose a different location during installation The gwenn5 nlm file is the GroupWise 7 Agent Engine a program that is shared by all GroupWise agents It provides the following services to the agents Database management File operations Message handling Thread management Semaphores file record locking Date time services The first agent loaded on a server automatically loads the GroupWise Agent Engine The gwia nlm file is the Internet Agent program You load this NLM program to start the Internet Agent See Starting the Internet Agent in Installing the GroupWise Internet Agent in the GroupWise 7 Installation Guide The Internet Agent configuration file contains startup switches for the Internet Agent Switch settings placed in the Internet Agent startup file override comparable options set for the Internet Agent in ConsoleOne The startup file is named the same as the Internet Agent object in ConsoleOne The default is gwia During i
88. directory where the Internet Agent queue directory is located See Using Internet Agent Startup Switches in Internet Agent in the GroupWise 7 Administration Guide agtcon directory The agtcon directory holds subdirectories and files used by the agent consoles such as help files webcon directory The webcon directory holds subdirectories and files used by the agent Web consoles such as help files The etc init d directory is the standard location for Linux startup scripts grpwise ia file The grpwise script is created automatically during installation You can use the script to start restart stop and display status information about the Internet Agent For more information about starting the Internet Agent see Starting the Internet Agent in Installing the GroupWise Internet Agent in the GroupWise 7 Installation Guide rc3 d directory The rc3 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 3 multi user boots to a text mode login prompt without The X Window System The symbolic link to the grpwise ia script is S99grpwise ia It is created if you choose during installation to have the Internet Agent start automatically when the server boots rc5 d directory The rc5 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 5 multi user boots to The X Window System login dialog box
89. e Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide domain mta 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 During installation a customized version of the strtupxx mta file named domain mta is created in the share directory This customized version has the home startup switch automatically set to the domain directory the MTA will service See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide agtcon directory The agtcon directory holds subdirectories and files used by the agent consoles such as help files See Using the POA Server Console in Post Office Agent and Using the MTA Server Console in Message Transfer Agent in the GroupWise 7 Administration Guide webcon directory The webcon directory holds subdirectories and files used by the agent Web consoles such as help files See Using the POA Web Console in Post Office Agent and Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide The etc init d directory is the standard location for Linux startup scripts Agent Installation Directories 105 grpwise file The grpwise script is created automatically during installation You can use the script to start restart stop a
90. e J gwwww1 dll Customized DLL program for MIME x 10 dll XIS DLL programs J gwia xml XIS agent configuration file See also Internet Agent Queue Directory on page 82 On a Windows server the Internet Agent can be installed in any directory you choose The default location is c grpwise gwia The Internet Agent icon is set up to include the full path to whatever directory you choose The gwenvla dll file is the GroupWise Agent Engine a program that is shared by both GroupWise agents It provides the following services to the agents Database management File operations 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 The gwia exe file is the Internet Agent program You run this executable file to start the Internet Agent See Starting the Internet Agent in Installing the GroupWise Internet Agent in the GroupWise 7 Installation Guide 114 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwia cfg file gwianxx chm files gwianxx dll files gwwww1 dll file x 10 dil files gwia xml file On Windows the gwia cfg file in the installation directory is simply a pointer to the gwia cfg file under the domain directory where the actual Internet Agent configuration file is located Online help is available by clicking Help in the Internet Agent console on
91. e 15 The name of the holding queue for each post office consists of the first three characters of the post office name followed by four hashed characters to ensure uniqueness Troubleshooting 3 Message Flow and Directory Structure gatewayx directories The gatewayx subdirectories in the holding directory mshold represent gateways in the domain If a gateway is closed the MTA routes messages for that gateway into its holding queue in 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 domainx directories 0 7 directories mtaname files The domainx subdirectories in the holding directory mshold represent domains to which the current domain has a direct link If a domain is closed the MTA routes messages for that domain into its holding queue in MSHOLD When the domain is open the MTA moves the messages from the holding queue back into the regular message flow For more information see Message Delivery to a Different Domain on page 27 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 The priority 0 7 subdirectories in each holding queue in the mshold subdirectory c
92. e MTA input queues to look for work The resources used for message logging are configurable See Optimizing the Routing Queue in Optimizing the MTA in the GroupWise 7 Administration Guide More detailed message logging by the MTA is also available but is turned off by default See Enabling MTA Message Logging in Configuring the MTA in the GroupWise 7 Administration Guide Message Transfer Storage Directories 79 mmddmsg nnn files The mmddmsg nnn files in the message logging subdirectory msglog in the MTA local directory are used by the MTA to track messages in its in progress queue 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 gwinprog directory The gwinprog subdirectory is the MTA in progress queue It contains eight priority subdirectories parallel to those found in wpcsin All messages for recipients in the domain pass through gwinprog no matter whether they arrived by way of TCP IP or by way of message files deposited into the MTA input queue by a POA or another MTA The resources used to process the in progress queue are configurable See Optimizing the Routing Queue in Optimizing the MTA in the GroupWise 7 Administration Guide mshold director
93. e Remote places the request in the wpcsin 1 subdirectory of the remote input queue on the user s remote computer When the GroupWise Remote user establishes a direct network connection between the remote computer and the master GroupWise system the GroupWise client places the request into the priority 1 subdirectory of the MTA input queue WPCSIN in the post office to which the GroupWise Remote user has connected The MTA then transfers the request to the post office where the GroupWise Remote user s master mailbox is located If the GroupWise Remote user has connected directly to the post office where the master mailbox is located GroupWise Remote places the request directly into the priority 1 subdirectory of the POA input queue wpcsoutlofs in the post office so processing by the MTA is not needed For mapped and UNC links the MTA for the GroupWise Remote user s domain scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the new request from the GroupWise Remote user the MTA picks it up from its domain input queue and transfers it to the post office where the GroupWise Remote user s master mailbox is located The MTA output queue is the input queue for the POA in the post office where the GroupW
94. e Remote user The Async Gateway transmits the response files through the modem connection to GroupWise Remote on the remote computer The GroupWise client on the remote computer decompresses the response files and places them in its input queue on the GroupWise Remote user s computer Taking the items from its input queue the GroupWise client performs the following actions for the GroupWise Remote user Updates the GroupWise Remote message database msg db with any items requested from the GroupWise Remote user s master mailbox Creates pointers in the GroupWise Remote user database user db so the messages gathered from the master mailbox appear in the GroupWise Remote user s mailbox Places any requested attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments The user s Remote mailbox now contains current copies of requested items from the user s master mailbox plus any messages received in the user s master mailbox from other GroupWise users The GroupWise user can now review current GroupWise mail when the connection to the master GroupWise system is no longer available 52 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Administrative Database Update ConsoleOne and the agents handle database updates throughout the GroupWise s
95. e file must contain the path to the gwia cfg file in the sys system directory on NetWare the opt novell groupwise agents share directory on Linux or the domain wpgate gwia directory on Windows The frgnames cfg file lets you list more Internet domain names than can fit in the Foreign ID field on the Identification page of the Internet Agent object in ConsoleOne For more information see Configuring How the Internet Agent Handles E Mail Addresses in Internet Agent in the GroupWise 7 Administration Guide The xspam cfg file lists X header fields that your anti spam service writes to the MIME header along with the values that flag the message as spam The Internet Agent examines the MIME header for any field listed in the xspam cfg file When a match occurs the message is marked for handling by the GroupWise client Junk Mail Handling feature For more information see Customized Spam Identification in Internet Agent in the GroupWise 7 Administration Guide The gwac db file is the access control database that stores information about the classes of service you have created For more information see Maintaining the Access Control Database in Internet Agent in the GroupWise 7 Administration Guide The gwac dc file is the data dictionary file from which the gwac db is created The preamble txt file is an ASCH text file that is automatically included with any MIME multipart message and is displayed when the
96. e new message the POA for the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office It also communicates the Delivered status message directly to the MTA by way of TCP IP and when that transmission is successful the copy in the MTA input queue is deleted The POA for the recipient s post office communicates to the GroupWise client by way of TCP IP that a new message has arrived The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client communicates the Opened status message to the POA by way of TCP IP The POA for the recipient s
97. ectories in the offiles directory After the 2 KB limit is reached only pointers are stored in the message databases The nn variable in the database names is a two digit number from zero to 24 A hashing algorithm takes each user s GroupWise file ID FID to derive which database the user s outgoing mail is assigned to The contents of the messages databases are encrypted so the text of message can only be read through Group Wise Multiple users are assigned to the same message database You can use GWCheck to determine which database a specific user has been assigned to See GroupWise Check in Standalone Database Maintenance Programs in the GroupWise 7 Administration Guide The ngwdfr db file in the ofmsg subdirectory in the post office holds deferred messages that users 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 ngwdfr db file until the delay expires Historical Note Earlier versions of GroupWise handled deferred messages through the ofpend directory in the post office The guardbak subdirectory in the ofmsg subdirectory in the post office holds a backup copy of the ngwguard fbk file ofuser directory userxxx db file The ofuser subdirectory in the post office contains a separate database mailbox for each GroupWise user Historical Note An earlier version of GroupWise designed by WordPerfect Corporatio
98. ectory saru esi ans a A ee 117 Windows Installation Directory 2 aaa a 122 Monitor Agent Installation 2 ee 125 Linux Installation Directory s ab wk e we ae ae ee Se Poe SB e da eR 125 Windows Installation Directory 2 aaa a 127 Apache Tomcat Installation sos e e 42 06 AR ao o ER Re Oe Eee ee eR ee Be de 129 NetWare Installation Directory 2 2 a 129 Linux Installation Directory sz tio ee ee bow oa ee Bee ee Ree a ee OR a Pe ee 134 Software Distribution Directory 139 NetWare Windows Software Distribution Directory o oo e 139 grpwise software directory ea a a 140 agents directory 4 4 ai eee ra ta sd da a A eek oda M ot d a dd Mat tis E rh 140 domain directory se innar a perir ee i AA a ee ee A a 141 PO CIFECIONY ss 0 eed ATA A ee DA A ee Se BAO he BS Se eS SA BS 142 clientdir ctory o 302 240 ee eb ar Bee a a ae be ee Be ec ab ee a a 143 Olviews directory Le a Baek BO la Le La ee ave ene ee A eee ek ESS eared 143 ZEN directory sate orden a AAA A ewe ba Se AAA ae hae Swe Ee ee 144 AAUMINGIRCClONY cde eae Ss te Ee Bede E A A Ee Ee oe ee ee AB de 144 internet directory a 144 license directory ians eae ee ELA e it E ee ee Be QRS ee BSS 145 COMMON directory eva a Ee a ee eb See eae alee ea ee ee ab ee eae we ba 145 AOS ALEC Y tess Sas A Bok a Sh eS E A he a ee SRE E EA Berk 145 Linux Software Distribution Directory oaoa oaa a a 145 opt novell groupwise software directo
99. ectory Structure gwprob directory gwchars directory save directory gwia cfg file route cfg file gwauth cfg file mimetype cfg file qfiles directory The qfiles directory holds messages that cannot be sent during the current Send Receive cycle The messages are queued to this directory until the next cycle The delayed delivery messages waiting in the qfiles directory remain in encrypted format until the Internet A gent transfers them to the send directory for processing by the SMTP service The Internet Agent uses the gwprob directory for messages it cannot process These are usually messages that have been damaged during transmission or that have the wrong Internet address This directory contains conversion tables that the Internet Agent uses to convert message attachments between character sets If you reinstall or upgrade the Internet Agent your old configuration files are copied to the save directory as a backup If you reinstall or upgrade repeatedly the files are overwritten each time The gwia cfg file is the Internet Agent configuration file that contains startup switches Some switches are set during installation You can set others as needed For more information see Using Internet Agent Startup Switches in Internet Agent in the GroupWise 7 Administration Guide NetWare The NetWare Internet Agent uses the gwia cfg file created in sys system during installation The gwia cfg file under the domain i
100. eee ae ee ds Be Bee 74 WPhOSECB Mee ca mear ep Ate bug Be Se Eee ea A ee te Ae de a Behe ee aie ty a 77 QWPO dC TIC visi n a Boe OR Se Re BR e Jee Beate th ew BA ele kk ee ae e ok 77 ngwouard db Tile 3 swede ia eee Aine bh kee eee ne Ee he ls ee da da 77 ngwguardide file sae ee E eee Ete ae il kh ew Geb tenho alas Ete ce eA 77 ngwg ard TDK file sss ad ee eae eee oR eee a A eh eee eek Bt oa te bad Dy 77 ngwguard ME ee Pee ek Rae eee dee Av Oe we SRE e Raa eed Wh ee ee E a 78 ngweheckdb m avs Sy do BRS See OS PR ee eS ee ee Pee Re ee oi 78 agentinstall Xt x 32 ek ee A E A A a a ee de EOE SB OS EY 78 MTA Local Queue Directory ise sio ea eae eke eR Re a Be ee e E 78 mslocal directOny 9 2 208 28 et he ek SB Sk A Gon Be Sh ace Bh Soe AO ath aoa Bab 79 MSglOg direCtOry e i sas ee Ee Bere ag ee Re oe a Re A ee e 79 OWINProg dIrECtO lit n a e eh 2 Ge Ro tia Se eh de de E o ti a 80 MmShold directory ipod A A 80 domains directory a eek Sk hn tee Ban dr ee ce et la o be Bee RR a a 80 postx directores oia a ee es Se ie wt ee OR eee ee oP So fe ee 80 galewayX directores ici o a a eee he Ga Ee ta Bee Pee aA oe ede BE nds wep See Led 81 domain directories Sr reese e Ate ae A eRe ee oe eh ea ee ee Ge 81 O CIFECIONIES non eS ho E a i eRe ok eo SR A OM nk eee eo E 81 mtaname MleS yi xica aoe Seve ack Bar Pals Bo Re ew Ee Beals Bek ee ee eo e 81 QWwvsscCani directory 4 Se is eA ee A eee ali a oe Rae cate Ba eh Oe ae ia a N 81 mtaconv direc
101. ened and locked when the Internet Agent starts This prevents multiple Internet Agents from being started for the same domain 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 The Internet Agent places inbound messages in one of the wpcsin priority subdirectories 0 7 Most messages go in the 4 directory although some administrative and status messages might go in other directories The Message Transfer Agent retrieves the messages and delivers them to the proper destinations The wpcsout directory is the MTA output queue as well as being the Internet Agent input queue gwixxxx directory The gwixxxx directory is a system defined directory where gwi represents the first three letters of the Internet Agent object name as defined during installation and displayed in ConsoleOne and xxxx is a randomly generated string Here the Message Transfer Agent places outbound messages in the appropriate 0 7 priority subdirectory for the Internet Agent to retrieve and process problem directory The problem directory holds messages that the MTA cannot process The gwhold directory holds messages that are scheduled for delayed delivery 84 GroupWise 7 Troubleshooting 3 Message Flow and Dir
102. ent Items folder The Internet Agent deletes the R file and moves the S file to the gwprob directory Only the msgnnn db not the userxxx db is updated when the Internet Agent sends a status message for the user s Sent Items folder Outbound Mapped UNC Link Closed Transfer to the Internet Delayed Under construction for GroupWise 7 Inbound TCP IP Link Open Transfer from the Internet Successful Under construction for GroupWise 7 Inbound Mapped UNC Link Open Transfer from the Internet Successful The diagram below shows the flow of inbound messages from the Internet through the Group Wise directory structure to the Group Wise recipient Message Delivery to and from the Internet 43 44 L gwila Internet User lena 9 RECIEVE gt e Los ye e Stage Internet Agent for Recipient s Domain Internet Agent for Recipient s Domain MTA for Recipien s Domain POA for Recipien s Post Office Actor OFFILES mL FDK0 7 Fo e OFMSG sL msg lt 0 24 gt db OFUSER mL usercrao db WPCSIN wl 0 7 gt WPCSOUT GWIA MTA POA Action GWIA A message is sent from an Internet user to a GroupWise user and the Internet Agent places the message in the wpgatelgwialreceive directory GWIA The Internet Agent polls the receive directory converts the message to 5 MTA 5 POA GroupWise format and places it in the wpgate gwia wpcsin 0 7 directory where 0 7 is one of the
103. ent 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 The digit n is a version number The last two characters xx are a language code 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 The x 10 dll programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed The agent xml files are specialized agent configuration files for use in the XIS environment The help directory contains language specific subdirectories for the help files available from the POA and MTA Web consoles See Using the POA Web Console in Post Office Agent and Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide Internet Agent Installation NetWare Installation Directory on page 109 Linux Installation Directory on page 111 Windows Installation Directory on page 114 NetWare Installation Directory 2 sys system NetWare Internet Agent installation directory LJ gwenn5 nlm GroupWise 7 Agent Engine LJ gwia nlm Internet Agent NLM program J gwia cfg Internet Agent configuration file Ll gwianxx fil Internet Agent language information file LJ gwia ncf Internet Agent loa
104. ent item Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office If client server mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 For mapped and UNC links the MTA scans its input queue in each post office MTA for for messages to process You can control the rate at which the MTA scans its Local HTA input queues See Adjusting MTA Polling of Input Queues in the Domain and Domain Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects a new message the MTA picks up the message from the sender s post office and transfers it to the MTA in progress gwinprog queue From there the MTA transfers the message to the output queue in the recipient s post office The MTA output queue is the input queue for the POA in the recipient s post office a The POA polls its input queue regularly When it detects a new message the POA for POA for the recipient s post office performs the following actions Recipient s PQA Adds the message to t
105. ent s Post Office do POA for Recipient s Post Office a Recipient s GroupWise Client Recipient Recipient s GroupWise Client A POA for Recipient s Post Office MTA for Recipient s Domain de MTA for Recipient s Domain Icon POA x POA MTA Description When it receives the new message the POA for the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office It also communicates the Delivered status message directly to the MTA by way of TCP IP and when that transmission is successful the copy the MTA input queue is deleted The POA for the recipient s post office communicates to the GroupWise client by way of TCP IP that a
106. erver mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 36 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon MTA for Sender s HTA Domain a in Recipient s WTA Domain an in Recipient s POA Post Office 0 Recipient s GroupWise Client Recipient O Recipient s GroupWise Client Description For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects a new message the MTA picks up the message from the sender s post office and transfers it to the MTA in progress gwinprog queue However because the recipient s domain is closed the MTA in the sender s domain cannot complete the delivery Therefore the MTA in the sender s domain stores the message in its holding queue for the recipient s domain in the mslocal directory From there the MTA in the sender s domain transfers the message to the output queue in the recipient s domain When the recipient s domain is open again the MTA in the sender s domain transfers the delayed message from the domain holding queue to the MTA output queue in
107. es and other countries GroupWise is a registered trademark of Novell Inc in the United States and other countries NDS is a registered trademark of Novell Inc in the United States and other countries NLM is a trademark of Novell Inc QuickFinder is a trademark of Novell Inc Third Party Materials All third party trademarks are the property of their respective owners Contents About This Guide 9 Part I Message Flow Diagrams 1 Message Delivery in the Local Post Office 13 Access Mode Client Server i s ica rr ti a eR en E ee he ee we 13 2 Message Delivery to a Different Post Office 15 TCP IP Link Open Transfer between Post Offices Successful 0 0 e eo 15 TCP IP Link Closed Transfer between Post Offices Delayed 0 o 2 18 Mapped UNC Link Open Transfer between Post Offices Successful 0 ee ee 21 Mapped UNC Link Closed Transfer between Post Offices Delayed 0 a 23 3 Message Delivery to a Different Domain 27 TCP IP Link Open Transfer between Domains Successful e o e 27 TCP IP Link Closed Transfer between Domains Delayed 0 e e 30 Mapped UNC Link Open Transfer between Domains Successful 2 2 2 e e 33 Mapped UNC Link Closed Transfer between Domains Delayed 0 e e ee 36 Alternate Link Configuration
108. eshooting 3 Message Flow and Directory Structure install exe file nim directory nt directory startups directory snmp directory help directory The install exe file in the agent subdirectory is the installation program you run to install the Group Wise agents on the servers where you will run the POA and or MTA For instructions see Installing and Starting the POA in Post Office Agent and Installing and Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide The nlm subdirectory in the agent subdirectory contains the GroupWise agent NLM files installed on NetWare servers See NetWare Installation Directory on page 99 The nt subdirectory contains the GroupWise agent files installed on Windows servers See Windows Installation Directory on page 107 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 See NetWare Installation Directory on page 99 or Windows Installation Directory on page 107 The snmp subdirectory contains GroupWise MIB files For more information see Using an SNMP Management Console in Post Office Agent and Message Transfer Agent in the Gr
109. ffices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects a new message the MTA picks up the message from the sender s post office and transfers it to the MTA in progress gwinprog queue However because the recipient s post office is closed the MTA cannot complete the delivery Therefore the MTA stores the message in the holding queue for the recipient s post office in the mslocal directory When the recipient s post office is open again the MTA transfers the delayed message from the post office holding queue to the MTA output queue in the recipient s post office The MTA output queue is the input queue for the POA in the recipient s post office GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon POA for Recipient s POA Post Office Recipient s GroupWise Client Recipient Recipient s GroupWise Client 5 x MTA for Local Domain WTA x POA for Sender s POA Post Office E Sender Description The POA polls its input queue regularly When it detects a new message the POA for the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database
110. file The commgr cfg file holds the same configuration information that is stored on the GroupWise 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 in WebAccess in the GroupWise 7 Administration Guide A copy of the commgr cfg file is automatically maintained in the WebAccess Agent queue directory domain wpgate webac 70a 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 in WebAccess in the GroupWise 7 Administration Guide Idap cfg file The Idap cfg file holds the same configuration information that is stored on the LDAP Provider object named LDAPProvider in eDirectory For more information see Configuring the LDAP Service Provider in WebAccess in the GroupWise 7 Administration Guide default directory The default directory holds boilerplate versions of the various cfg files logs directory The logs subdirectory holds WebAccess Application log files For more information see Controlling WebAccess Application Logging in WebAccess in the GroupWise 7 Administrat
111. file The gwpo dc file in the domain is the data dictionary for creating and rebuilding GroupWise 7 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 Group Wise 7 6 x 5 x post offices in that domain The original gwpo dc file is located in the domain directory of the software distribution directory or on the GroupWise distribution media agentinstall txt The agentinstall txt file in the domain records all the information that you provide when you install the MTA for the domain Post Office Directory w post_office a wpcsin Mo E E Ma 5 M6 mi E gwdms L dmsh db 1ib0001 ff E dmxxnn01 ff db de index E archive docs T 400 ff Post office directory MTA input queue directory Live interactive requests Other interactive requests High priority messages High priority status responses Normal priority messages Normal priority status responses Low priority messages Low priority status responses Document Management Services directory Shared Document Management Services database Library directories Document databases QuickFinder index for library Archive directory for library Large document directory for library Subdirectories for documents 66 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure ie ofmsg LJ msgnn db J ngwdfr db E guardbak B ofuser J userxxx db J puxxxxx db En index E of
112. files T ta0 6 EN ofviews Ea ofwork E ofdirect E wpcsout En ofs o gt 3 MN a 5 MN 6 7 l mmddpoa nnn L wprof50 db a ads o y E 3 E a 5 e 7 Message database directory As many as 25 message databases Deferred message database Backup guardian database User database directory User databases one per user Databases for shared folders QuickFinder index for messages Attachment store directory Subdirectories for attachments GroupWise client view files GroupWise working directory Remote direct connection directory MTA output queue directory POA input queue directory Live interactive requests Other interactive requests High priority messages High priority status responses Normal priority messages Normal priority status responses Low priority messages Low priority status responses POA log files Downloadable system Address Book 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 Message Transfer Storage Directories 67 y defer GWCheck subdirectory for deferred database maintenance requests de problem Directory for undeliverable messages LJ wphost db Post office database l gwpo dc Data dictionary for
113. flect the addition modification or deletion performed in ConsoleOne Administrative Database Update 55 56 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 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 Message Transfer Storage Directories on page 59 Agent Installation Directories on page 99 Software Distribution Directory on page 139 GroupWise Client Installation Directories on page 155 Directory Structure Diagrams 57 58 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 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 Domain Directory on page 59 Post Office Directory on page 66 MTA Local Queue Directory on page 78 Internet Agent Queue Directory on page 82 WebAccess Agent Queue Directory on page 88 Caching Mailbox Directory on page 91 Remote Mailbox Directory on page 95 Domain Directory Es domain Domain directory 2 wpcsin MTA input queue directory 3 0 Live interactive requests de 1 Other interactive requests Es 2 High priority messages E 3 High
114. ge code You can change the location of the cache directory as described in Modifying WebPublisher Settings in WebAccess in the GroupWise 7 Administration Guide 124 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure help 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 Monitor Agent Installation Linux Installation Directory on page 125 Windows Installation Directory on page 127 Linux Installation Directory E opt novell groupwise agents E bin Ll gwmon E iib L so B share J monitor xml E gwmonitor LJ gwmonitor cfg dl default ig logs E users E Jetc init d Ll grpwise ma Es rc3 d LJ S99grpwise ma En rc5 d L S99grpwise ma E Ivar log E novell groupwise GroupWise installation directory Linux agent installation directory Subdirectory for GroupWise agent executables Monitor Agent executable Subdirectory for GroupWise agent library files Supporting shared library files Subdirectory for agent shared files Monitor Agent configuration file Subdirectory for Monitor Application files Monitor Application configuration file Subdirectory for boilerplate configuration files Subdirectory for Monitor Application log files Directory for Monitor users session files Standard Linux location f
115. gs conf httpd conf file Directory for GroupWise Monitor files Subdirectory for service provider files Subdirectory for template files Directory for GroupWise WebAccess files Subdirectory for service provider files Subdirectory for template files Directory for GroupWise WebPublisher files Subdirectory for service provider files Subdirectory for template files Standard Tomcat directory Directory for Novell product configuration files Subdirectory for GroupWise Monitor Monitor Application configuration file Directory for Monitor Application log files Subdirectory for WebAccess WebAccess Application configuration file Communications Manager configuration file Novell Speller Application configuration file LDAP service provider configuration file Directory for WebAccess Application log files Temporary working directory Directory for WebAccess users session files Subdirectory for WebAccess Application files WebPublisher Application configuration file Communications Manager configuration file Subdirectory for boilerplate configuration files Subdirectory for WebPublisher Application log files The httpd conf file is the main Apache configuration file On NetWare 7 the GroupWise Installation program modifies it to include a reference to the GWApache2 conf file conf GWApache2 conf file The GWApache2 conf file includes the jkmount command that enables Apache and Tomcat to communicate with each other Agent Insta
116. gwtsa nlm GroupWise Target Service Agent GWTSA program LJ gwtsaxx fil GWTSA language information files L gwtsa ncf GWTSA load file LJ gwtmstmp nim GroupWise Time Stamp program ey help Subdirectory for GroupWise agent Web console help files NetWare agent installation directory gwenn5 nlIm file gwpoa nim file gwmta nIm file When you first install GroupWise Administration the GroupWise agents are initially installed in platform specific subdirectories in the agent directory in the software distribution directory However the agents cannot be run from this initial location They must be installed on the servers where they will run On a NetWare server the Group Wise agents are typically installed in the sys system directory You can choose a different location during installation The gwenn5 nlm file is the GroupWise 7 Agent Engine a program that is shared by all GroupWise agents It provides the following services to the agents Database management File operations Message handling Thread management Semaphores file record locking Date time services The first agent loaded on a server automatically loads the GroupWise Agent Engine The gwpoa nlm file is the Post Office Agent program You load this NLM program to start the Post Office Agent See Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide The gwmta nlm is the Message Transfer Agent program You load this
117. he message database msgnnn db corresponding to Post Office 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 notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office 5 The Notify component of the recipient s GroupWise client notifies the recipient Recipient s that a new message has arrived GroupWise Client 5 Each recipient opens the message in the GroupWise client Recipient pon 22 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon Description O Each recipient s GroupWise client creates an Opened status message in the Recipient s appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s GroupWise post office Client 0 For mapped and UNC links the MTA scans its input queue for messages to MTA for process You can control the rate at which the MTA scans its input queues See Local HTA Adjusti
118. he message to the MTA for the sender s domain by way of TCP IP and deletes the copy in the MTA input queue because the TCP IP transfer to the MTA was successful To see what would happen if the TCP IP link to the MTA were closed see TCP IP Link Closed Transfer between Post Offices Delayed on page 18 The MTA for the sender s domain receives the message and places it into the MTA in progress gwinprog queue The MTA for the sender s domain then communicates the message to the MTA for the recipient s domain by way of TCP IP If the TCP IP link to the recipient s domain were closed the message would be placed in the closed domain s holding queue in the MTA s mslocal directory for later transfer See TCP IP Link Closed Transfer between Domains Delayed on page 30 The MTA for the recipient s domain receives the message and places it into the MTA in progress gwinprog queue The MTA for the recipient s domain then communicates the message to the POA in the recipient s post office by way of TCP IP 28 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage POA for Recipient s Post Office 40 POA for Recipient s Post Office Recipient s GroupWise Client Recipient Recipient s GroupWise Client POA for Recipient s Post Office E MTA for Recipient s Domain MTA for Recipient s Domain Icon POA POA MTA Description When it receives th
119. he result directory and compares the conversation If the r file contains the correct 250 OK SMTP reply codes the SMTP service deletes the file and sends a transferred status message to the user s Sent Items folder in the Group Wise client The defer directory holds messages that are deferred and re queued according to the Retry Schedule If the Internet Agent SMTP service receives a temporary error such as Host Down it places the message in the defer directory for a specified time then transfers the file to the send directory for another attempt at sending to the Internet For more information see Configuring Basic SMTP MIME Settings in Internet Agent in the GroupWise 7 Administration Guide Message Transfer Storage Directories 87 dsnhold directory The DSN hold directory stores header information for inbound messages that request delivery status notifications For more information see Using Extended SMTP ESMTP Options in Internet Agent in the GroupWise 7 Administration Guide help directory The help directory holds the help files that you can view from the Internet Agent Web console See Using the Internet Agent Web Console in Internet Agent in the GroupWise 7 Administration Guide 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 processe
120. her de help al images Novell Apache configuration directory Standard Apache directory Standard Apache directory Standard Apache directory Standard Apache directory Standard Apache directory Standard Apache directory Novell Tomcat configuration directory Standard Tomcat file Standard Tomcat file Standard Tomcat file Standard Tomcat file Standard Tomcat file Web server configuration file Standard Tomcat directory Standard Tomcat directory Novell subdirectory under var Apache document root directory for WebAccess and WebPublisher Web server default Web page Directory for Novell product files Directory for Novell class files and properties files Directory for Novell product image files Directory for Inso viewer files for viewing attachments Directory for GroupWise WebAccess files Subdirectory for WebAccess client properties files Subdirectory for WebAccess client help files Subdirectory for WebAccess client image files Subdirectory for WebAccess Application Web console help files Directory for GroupWise WebPublisher files Subdirectory for WebPublisher help files Subdirectory for WebPublisher image files Agent Installation Directories 135 T WEB INF Ll web xml J classes com novell E collexion E webaccess EN providers Es templates Es webpublisher E providers Es templates E gwmon J index html Z com novell Es gwmonitor help Es images J WEB INF web xml Es gwmonitor de pro
121. hooting 3 Message Flow and Directory Structure Software Distribution Directory NetWare Windows Software Distribution Directory on page 139 Linux Software Distribution Directory on page 145 NetWare Windows Software Distribution Directory E software_distribution directory Master copy of GroupWise software Es agents L install exe 2 nim E nt E startups Es snmp E help Es domain E wpdomain dc LJ gwdom dc LJ wphost dc E gwpo dc T po LJ ngwguard dc LJ wphost dc LJ gwpo dc GroupWise agent software GroupWise Agent Installation program NetWare agent software Windows agent software Agent startup files GroupWise MIB files Agent Web console help files Domain data dictionary files Data dictionary for GroupWise 4 x domain databases Data dictionary for GroupWise 7 6 x and 5 x domain databases Data dictionary for GroupWise 4 x post office databases Data dictionary for GroupWise 7 6 x and 5 x post office databases Post office data dictionary files Data dictionary for message store databases Data dictionary for GroupWise 4 x post office databases Data dictionary for GroupWise 7 6 x and 5 x post office databases Software Distribution Directory 139 A client LJ setup cfg E win32 LJ setup exe Es addons E gwmailto de gwtip Es ofviews T zen El admin de c1admin ln monitor D utility Es gwcheck w gwcsrgen i setupip Es internet E gwia Es webaccess E license EN common
122. ient the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Message Delivery to a Different Domain 35 Mapped UNC Link Closed Transfer between Domains Delayed This message flow diagram illustrates how a GroupWise message travels from one user to another when the domains are connected by a mapped or UNC link and the link is closed L 9 7 MSHOLD DOMAINS POSTA L 9 7 POSTB Lo S i GATEWAY PO a Lo 7 DOMAINA 9 7 Stage Icon Description DO The user sends a message to recipients in a post office in a different domain Sender pon In this diagram the delivery mode setting for the local post office is Use App Thresholds and the threshold is not exceeded a The GroupWise client performs the following actions for the sender Sender s A Adds the message to the message database msgnnn db assigned to the GroupWise sender Client Creates a pointer in the sender s user database userxxx db so the message appears in the sender s mailbox as a sent item Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the sender s MTA input queue If client s
123. igned by WordPerfect Corporation WPCorp was named WP Office Remote Hence the wprof in wprof dc Some naming conventions have been preserved for backward compatibility The ngwguard db file in the remote data directory rofdata in the Remote mailbox directory is the guardian database for the GroupWise Remote mailbox It is parallel in function to the ngwguard db file in the post office The ngwguard dc file in the remote data directory rofdata in the Remote mailbox directory is the data dictionary for building the databases in the GroupWise Remote mailbox It is parallel in function to the ngwguard dc file in the post office The puxxxxx db files in the remote data directory rofdata in the Remote mailbox directory are databases for replicated items such as shared folders These databases prevent conflicts between user names of shared items from users in other post offices and user names in the Remote user s post office They are parallel to the puxxxxx db files in the post office The gwdms subdirectory in the remote data directory rofdata in the remote mailbox directory is 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 dmsh db file The dmsh db file in the remote document management subdirectory gwdms in the remote mailbox directory is a database shared by all libraries that
124. in the GroupWise 7 Administration Guide win32 directory The client win32 subdirectory contains all GroupWise client files installed for use with Windows See Windows Client on page 155 setup exe file The client win32 setup exe file is the program GroupWise client users run to install and set up the Group Wise client on their Windows workstations See Client in the GroupWise 7 Administration Guide addons directory The addons directory contains subdirectories for programs that can be used along with the GroupWise client to enhance aspects of its functionality gwmailto directory The gwmailto directory contains a program that makes the GroupWise Windows client the default e mail application in your Web browser For more information see GWMAILTO in Modifying the Configuration File in Client in the GroupWise 7 Administration Guide gwtip directory The gwtip directory contains a program that display a helpful tip about GroupWise each time the client starts For more information see GWTIP in Modifying the Configuration File in Client in the GroupWise 7 Administration Guide ofviews directory The client ofviews subdirectory contains platform specific subdirectories of view files for use by the Group Wise client In addition the gwviewxx ini and ofviewxx ini files configure custom views on the menus where users select views The gwviewxx ini file configures GroupWise 7 6 x and G
125. ion Guide 120 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure users directory The users subdirectory holds session files for WebAccess users If WebAccess times out after a period of user inactivity the user s session information is saved When the user logs back in the session information is retrieved so that the user can continue working without loss of data Also users message text is saved during each session so that if the WebAccess Application is restarted or goes down users do not lose the message text they were composing at the time Session files are deleted when users log back in webpublisher directory letc init d directory The webpublisher directory holds files used by the WebPublisher Application webpub cfg The webpub cfg file holds the same configuration information that is stored on the WebPublisher Application object named Group WiseWebPublisher in eDirectory For more information see Configuring the WebPublisher Application in WebAccess in the GroupWise 7 Administration Guide commgr cfg file The commgr cfg file holds the same configuration information that is stored on the Group Wise Provider object named Group WiseProvider in eDirectory including the IP address port number number of threads and encryption key for the WebAccess Agent This information enables the WebAccess Application to communicate with the WebAccess Agent For more information see Configuring
126. irectories GroupWise Agent Installation POA and MTA on page 99 Internet Agent Installation on page 109 WebAccess Agent Installation on page 115 Monitor Agent Installation on page 125 Apache Tomcat Installation on page 129 GroupWise Agent Installation POA and MTA The Post Office Agent POA and the Message Transfer Agent MTA are always installed together The agent installation directory differs depending on the platform where the agents are installed NetWare Installation Directory on page 99 Linux Installation Directory on page 102 Windows Installation Directory on page 107 NetWare Installation Directory E sys system J gwenn5 nlm LJ gwpoa nim J gwmta nim L strtu pxx poa LJ strtupxx mta post_office poa LJ domain mta LJ gwpoanxx hlp J gwmtanxx hlp LJ gwpoanxx fil LJ gwmtanxx fil J grpwise ncf NetWare agent installation directory GroupWise 7 Agent Engine Post Office Agent POA program Message Transfer Agent MTA program Boilerplate POA startup file Boilerplate MTA startup file POA startup file for a specific post office MTA startup file for a specific domain POA online help files MTA online help files POA language information files MTA language information files Agent load file Agent Installation Directories 99 L x 10 nlm XIS NLM programs LJ agent xml XIS agent configuration files J
127. irectory a Contents _ Pkginfo J Info plist A Macos El Resources J GroupWise icns D i LJ gwenlxxx fil J ngwguard dc wprof dc oa Java J jar L dylib Standard Macintosh directory for application files Standard Macintosh package info file Standard Macintosh package list file Standard Macintosh directory for operating system files Standard Macintosh directory for resource files Icons used by the Cross Platform client Subdirectory for Cross Platform client library files Data dictionary for local databases on the user s workstation Data dictionary for the local copy of the Address Book Cross Platform client language information files JRE used by the Cross Platform client Java archive jar files used by the Cross Platform client Dynamic libraries used by the Cross Platform client 160 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Applications GroupWise app directory The Applications Group Wise app directory contains the GroupWise Cross Platform client on Macintosh Contents directory The Contents directory is the standard location on Macintosh for all files that make up an application MacOS directory The MacOS directory contains the JavaApplicationStub file that enables the Cross Platform client to invoke the Java Virtual Machine JVM on Macintosh Resources directory The Resources directory is the standard location on Macintosh for files that support an application Grou
128. ise Remote user s master mailbox is located The POA polls its input queue regularly It quickly detects the new request from the GroupWise Remote user When the GroupWise Remote user sends a request for items from the master mailbox the POA performs the following actions Gathers the requested items from the GroupWise Remote user s master mailbox msgnnn db and userxxx db Gathers any attachments for requested items from the post_office offiles fd0 f6 subdirectory in the GroupWise Remote user s post office Compiles the information into a response file and places it in the priority 1 subdirectory of the MTA input queue wpcsin for return to the GroupWise Remote user When the MTA in the GroupWise Remote user s domain detects the response for the GroupWise Remote user the MTA picks it up from its post office input queue and transfers it to its output queue in the ofdirect directory in the post office where the GroupWise Remote user s master mailbox is located The MTA output queue in the ofdirect directory is the input queue for the GroupWise client on the remote computer GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon Description D The GroupWise client picks up the response in the post office and transfers it GroupWise to its input queue on the GroupWise Remote user s computer Remote E Taking the items from its input queue the GroupWise client performs the GroupWise following actio
129. ise Remote users do not connect to the post office where their master mailboxes are located 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 The priority 2 subdirectory of the MTA input queue wpcsin in the domain is for high priority messages For example MTAs for other domains place incoming high priority user messages here The local MTA then routes the messages to recipients post offices Message Transfer Storage Directories 61 3 directory 4 directory 5 directory 6 directory 7 directory MTAs for other domains place incoming administrative messages here to replicate database updates in the local domain The MTA admin thread places outgoing administrative messages here to replicate database updates to other domains 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 in Optimizing the MTA in the GroupWise 7 Administration Guide The priority 3 subdirectory of the MTA input queue wpcsin in the domain is for high priority 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 pos
130. ise Check Error Codes in Administration Error Messages in the GroupWise 7 Troubleshooting 1 Error Messages The remoten log files in the connection output queue wpcsout ofs are saved versions of the connection logs you can view in the GroupWise client by clicking Accounts gt Connection Log These log files can be useful for troubleshooting problems with your connection to your Online mailbox The gwdms directory is the Document Management Services directory It contains information about the libraries in your GroupWise system It has the same structure as the gwdms subdirectory in the post office dmsh db file The dmsh db file is a database shared by all libraries that contains a list of all available libraries and lookup tables for each library dmxxnn01 ff db files The dmxxnn01 ff db files are databases for library and document information They are parallel to the dmxxnn01 ff db files in the post office docs directory The docs directory holds cached copies of the documents in your Online mailbox index directory The index directory under the gwdms directory contains the QuickFinder index for the documents in your Caching mailbox Message Transfer Storage Directories 93 index directory The index directory under the rofdata directory contains the QuickFinder index for the messages in your Caching mailbox wpcsin directory The wpcsin subdirectory is the input queue for the connection that transfers messages
131. istribution Directory 153 154 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 4 0 GroupWise Client Installation Directories Windows Client on page 155 Cross Platform Client on Linux on page 158 Cross Platform Client on Macintosh on page 160 Windows Client E c novell groupwise Installation directory for GroupWise 7 Windows client software L grpwise exe LJ gwtip exe J notify exe _ addrbook exe J gwcheck exe LJ htrsetup exe LJ gwimpexe exe E gwmailto exe LJ gwreload exe L gwsync exe LJ ngwguard dc wprof dc L dil LJ OCX L fit Ll chm E ofviews es win LI vew L ini GroupWise client program GroupWise Tip of the Day program GroupWise Notify program GroupWise Address Book program GroupWise GWCheck program Hit the Road setup program GroupWise E Mail Importer Utility Web browser support program Mailbox mode switching program Mailbox synchronization program Data dictionary for databases Data dictionary for Remote Address Book DLL programs to support GroupWise Windows client OLE custom controls Graphics filters for Inso viewers Help files to support the GroupWise client GroupWise view files GroupWise view files for Windows View files View initialization files GroupWise Client Installation Directories 155 de ppforms Day planner forms LJ bfp Form description files J prs Print resource files c novell groupwise The Gr
132. itch in the WebAccess Agent configuration file webac70a waa in the WebAccess Agent installation directory if you want to move the WebAccess Agent home directory 000 prc directory mmddlog nnn file The NetWare and Windows WebAccess Agents use the 000 pre directory to store log files On Linux the 000 pre directory is located under var log The mmddlog nnn files hold error and status messages about the functioning of the WebAccess Agent The WebAccess 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 For more information about log files see Controlling WebAccess Agent Logging in WebAccess in the GroupWise 7 Administration Guide wpcsin directory No longer used The WebAccess Agent and the MTA communicate by way of TCP IP and do not need queue directories wpcsout directory webxxxx directory problem directory No longer used No longer used No longer used gwhold directory No longer used gwprob directory files directory No longer used The files directory holds documents that are cached after they have been viewed The gwcache db file keeps track of what documents are available in the files directory You can configure the maximum amount of disk space you want the cached documents to consume See Configuring the WebPublisher Application in WebAccess in the Gr
133. ks the sent items in his or her mailbox in the GroupWise Sender pen client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Mapped UNC Link Open Transfer between Domains Successful This message flow diagram illustrates how a GroupWise message travels from one user to another when the domains are connected by a mapped or UNC link and the link is open E WPCSIN WPCSIN 0 7 a o b WPCSOUT WPCSOUT amp LADS ans Lo L 9 7 b MTAb gt S WPCSIN MSLOCAL MSLOCAL Orat OFMSG ls le ko E nsg0 24a MSHOLD MSHOLD adi DOMAINS DOMAINIMIS as POSTA POSTA L FDO 7F e 07 0 7 WPCSOUT POSTB POSTB po L9 7 Lo 97 GATEWAY GATEWAY OFS Co az L 9 7 DOMAINE DOMAJNA POR Eo L_9 7 Message Delivery to a Different Domain 33 34 Stage Sender Sender s GroupWise Client E MTA for Sender s Domain D MTA for Recipient s Domain Icon a HTA MTA Description The user sends a message to recipients in a post office in a different domain In this diagram the delivery mode setting in the local post office is Use App Thresholds and the threshold is not exceeded The GroupWise client performs 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
134. le gwtsa ncf file help directory The gwtsa nlm is the GroupWise Target Service Agent GWTSA which provides reliable backups of a running GroupWise system by successfully backing up open files and locked files rather than skipping them as some backup software does For more information see Group Wise Target Service Agent GWTSA for NetWare 5 1 in Databases in the GroupWise 7 Administration Guide If you use the Group Wise Target Service Agent GWTSA of the GroupWise Target Server Agent for File Systems GWAFSGW to back up your Group Wise system the time stamping is an automatic part of the backup process However if you choose not to use one of these TSAs you must still make sure that user databases are time stamped so that items will not be prematurely purged The gwtmstmp nlm accomplishes this task For more information see GroupWise Time Stamp Utility in Databases in the GroupWise 7 Administration Guide These files contain all language specific information for the GWTSA The last two characters xx are a language code The gwtsa ncf file is the NetWare configuration file that automatically loads the GWTSA whenever the server is restarted A typical gwtsa ncf file would look similar to the following load sys system smdr load sys system gwtsa home sys gwsystem corpdom nome sys gwsystem acctpo The help directory contains language specific subdirectories for the help files available from the POA a
135. le is created with the home startup switch automatically set to the domain directory where the WebAccess Agent queue directory domain wpgate webac70a is located See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide The gwdva dva file is the Document Viewer Agent startup file The Viewer Agent is currently configured completely by startup switches For more information see Document Viewer Agent Startup Switches The gwwanxx dll files contain all language specific information for the WebAccess Agent The digit n is a version number The last two characters xx are a language code The gwwasnmp dll file provides interaction with the Windows SNMP Service so that you can monitor the WebAccess Agent using an SNMP monitoring program This file is not installed unless you enable SNMP during installation It cannot be installed if the SNMP Service is not installed on the Windows server The gwwww1l dll file provides parsing of MIME messages received from the Internet The x 10 dll programs provide XIS capability for the Group Wise agents so that you can create XML documents to monitor and change the agents as needed The gwia xml file is a specialized agent configuration file for use in the XIS environment cache template xx directory The cache template xx directory holds language specific HTML template files for viewing documents in WebAccess and WebPublisher The xx is a two letter langua
136. line mailbox 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 names wpcsin and ofs for the input queue though the MTA is not involved in processing messages in your Remote mailbox Some naming conventions were originally preserved for backward compatibility 0 7 directories The priority 0 7 subdirectories in the connection output queue wpcsout ofs parallel those found in the ofs directory in your post office 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 94 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Historical Note WP Office Remote the predecessor of GroupWise Remote was originally designed by WordPerfect Corporation WPCorp Hence the name wpgwsend Some naming conventions were originally preserved for backward compatibility wpgwrecv directory The wpgwrecv directory holds compressed files that contain messages or other information that have been received from your Online mailbox The GroupWise client decompresses the files and places the message files into the wpcsout ofs 1 directory Historical Note WP Office Remote the predecessor of GroupWi
137. llation Directories 131 htdocs index html file The index html file is the default HTML file that displays in your Web browser when you hit the IP address or hostname of the server 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 Providers in Monitor in the GroupWise 7 Administration Guide 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 webaccess providers directory The providers directory holds the Java class and properties files for the WebAccess providers For more information see Adding or Removing Service Providers in WebAccess in the GroupWise 7 Administration Guide webaccess templates directory The templates directory holds subdirectories for the various file formats used in various browser environments For more information see Modifying WebAccess Application Template Settings in WebAccess in the GroupWise 7 Administratio
138. me Sender da domain In this diagram the access mode setting in the local post office is Client Server Only Message Delivery to a Different Post Office 15 16 Stage Sender s GroupWise Client E POA for Sender s Post Office POA for Sender s Post Office 5 MTA for Local Domain O MTA for Local Domain Icon POA POA HTA HTA Description The GroupWise client communicates the message to the POA by way of TCP IP The POA receives the message from the GroupWise client and performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office in case the TCP IP link to the MTA is currently closed The POA then communicates the message to the MTA by way of TCP IP and deletes the copy in the MTA input queue because the TCP IP transfer to the MTA was successful To see what would happen if the TCP IP link to the M
139. message recipient lacks a MIME compliant mail reader For more information see Customizing MIME Preamble Text in Internet Agent in the GroupWise 7 Administration Guide The preamble all file contains the preamble text in multiple languages For more information see Customizing MIME Preamble Text in Internet Agent in the GroupWise 7 Administration Guide The blocked txt file contains a list of Internet sites that you have added to the Prevent Messages From list for your default class of service in ConsoleOne For more information see Controlling User Access to the Internet in Internet Agent in the GroupWise 7 Administration Guide 86 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwia mib file NetWare only statusxx xml file gwia directory send directory receive directory result directory defer directory The gwia mib file contains all the Trap Set and Get variables used for communication between the Internet Agent and SNMP management consoles For setup instructions see Using an SNMP Management Console in Internet Agent in the GroupWise 7 Administration Guide 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 The gwia directory is the SMTP service daemo
140. n WebAccess in the GroupWise 7 Administration Guide logs 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 users directory The users subdirectory holds session files for WebAccess users If WebAccess times out after a period of user inactivity the user s session information is saved When the user logs back in the session information is retrieved so that the user can continue working without loss of data Also users message text is saved during each session so that if the WebAccess Application is restarted or goes down users do not lose the message text they were composing at the time Agent Installation Directories 133 webpublisher directory The webpublisher directory holds files used by the WebPublisher Application webpub cfg The webpub cfg file holds the same configuration information that is stored on the WebPublisher Application object named GroupWise WebPublisher in eDirectory For more information see Configuring the WebPublisher Application in WebAccess in the GroupWise 7 Administration Guide commgr cfg file The commegr cfg file holds the same configuration information that is stored on the GroupWise Provider object named GroupWiseProvider in eDirectory including the IP address port number number of threads and encryption key for the
141. n WPCorp was named WP Office Hence the of in ofuser Some naming conventions were originally preserved for backward compatibility The userxxx db files in the ofuser subdirectory in the post office are user databases where the contents of users mailboxes are stored as displayed in the Group Wise client In addition each user database contains Some personal GroupWise client program settings Personal appointments Personal groups Personal notes Rules Personal client settings that remain the same regardless of what workstation a user logs in to are stored in the user database Personal client settings that are customized for a particular workstation are stored in the Windows Registry The xxx variable in the database names is each user s GroupWise file ID FID 72 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure puxxxxx db file index directory The puxxxxx db files in the ofuser subdirectory in the post office are databases for replicated items such as shared folders These databases prevent conflicts between user names of shared items from users in other post offices and user names in the local post office The index subdirectory in the ofuser subdirectory in the post office contains the QuickFinder index for users messages stored in the post office offiles directory fd0 f6 directories The offiles subdirectory in the post office contains subdirectories for messages attachments an
142. n home directory where messages are converted between GroupWise format and Internet format On NetWare and Linux the default location is wpgate gwia the same as the Internet Agent home directory On Windows the default location is the Internet Agent installation directory You can change the location using the dhome startup switch in the Internet Agent configuration file gwia cfg The Internet Agent SMTP service places outbound messages in the send directory after they have 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 The Internet Agent SMTP service places inbound messages in the receive directory converts them into Group Wise format and then passes them to the Message Transfer Agent by placing them in the wpcsin directory When the Internet Agent SMTP service processes the message it builds a file r in the result directory that contains several lines of comments and SMTP reply codes which might indicate possible errors or confirm correct transmission After the Internet Agent SMTP service has completed the transmission with the destination host it moves another file s from the send directory to the result directory The filenames for both files are identical except for the first letter which is either s or r The s file is the converted message file The SMTP service looks at the s and r files in t
143. n Guide webpublisher providers directory The providers directory holds the Java class and properties files for the WebPublisher providers For more information see Adding or Removing Service Providers in WebAccess in the GroupWise 7 Administration Guide webpublisher templates directory The templates directory holds subdirectories for the various file formats used in various browser environments For more information see Modifying WebPublisher Application Template Settings in WebAccess in the GroupWise 7 Administration Guide sys novell directory The sys novell directory holds subdirectories for each Novell product that uses application configuration files gwmonitor directory The gwmonitor directory is created when you install GroupWise Monitor 132 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwmonitor cfg file The gwmonitor cfg file holds the same configuration information that is stored on the Monitor Application object named Group WiseMonitor in eDirectory For more information see Configuring the Monitor Application in Monitor in the GroupWise 7 Administration Guide logs directory The logs subdirectory holds Monitor Application log files For more information see Modifying Monitor Application Log Settings in Monitor in the GroupWise 7 Administration Guide webaccess directory The webaccess directory holds files used by the WebAccess Appli
144. nd MTA Web consoles See Using the POA Web Console in Post Office Agent and Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide Linux Installation Directory E opt novell groupwise agents Linux agent installation directory ay bin Subdirectory for GroupWise agent executables LJ gwpoa Post Office Agent POA executable Ll gwmta Message Transfer Agent MTA executable J gwpoa xml POA XIS configuration file J gwmta xml MTA XIS configuration file J strtupxx poa Boilerplate POA startup file JJ strtupxx mta Boilerplate MTA startup file 102 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure J gwcsrgen J gwtmstmp E iib J gwpoaxxx fil LJ gwmtaxxx fil J libpoa so J libpoa_ui so L libmta so Ll libmta_ui so L so Es image E share LJ post_office poa L domain mta Es agtcon de help Ea webcon ds help E Jetc init d LJ grpwise dl rc3 d J S99grpwise En rco d E S99grpwise E var log I novell groupwise T post_office poa J mmddpoa nnn EA domain mta LJ mmddmta nnn GroupWise Generate CSR utility GroupWise Time Stamp utility Subdirectory for GroupWise agent library files POA language information file MTA language information file POA shared library files POA shared library files for the optional user interface MTA specific library files MTA specific library files for the optional user interface Supporting library files
145. nd display status information about the POA and MTA For more information about starting the agents see Linux Installing and Starting the GroupWise Agents in Installing a Basic GroupWise System in the GroupWise 7 Installation Guide rc3 d directory The rc3 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 3 multi user boots to a text mode login prompt without The X Window System The symbolic link to the grpwise script is S99grpwise It is created if you choose during installation to have the agents start automatically when the server boots See Starting the Linux POA in Post Office Agent and Starting the Linux MTA in Message Transfer Agent in the GroupWise 7 Administration Guide rc5 d directory The rc5 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 5 multi user boots to The X Window System login dialog box The symbolic link to the grpwise script is S99grpwise It is created if you choose during installation to have the agents start automatically when the server boots See Starting the Linux POA in Post Office Agent and Starting the Linux MTA in Message Transfer Agent in the GroupWise 7 Administration Guide Ivar log novell groupwise directory The var log directory is the standard location for log files on Linux All GroupWise agent log files are
146. nder 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 notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 76 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client creates an Opened status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the status message the MTA picks it up from the recipient s post office and transfers it to the MTA in progress
147. nder s GroupWise client nti b f TCP IP POA for Local y way o Post Office POA a When the sender checks the sent items in his or her mailbox in the Sender pen GroupWise client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Mapped UNC Link Open Transfer between Post Offices Successful This message flow diagram illustrates how a GroupWise message travels from one user to another between post offices in the same domain when the mapped or UNC link between the post office and the domain is open y E WPCSIN Co b WPCSOUT S L_ADS MTA WPCSIN P Lo OFMSG jui L msgo 24db GWINPROG 5 L 47 OFUSER MSHOLD L iserxardb DOMAINMS p 7F POSTA pi L 97 i POSOUT POSTB C de E 0 7 OFS GATEWAY L 97 s 0 7 POAb DOMAING o Stage Icon Description T The user sends a message to recipients in a different post office in the same Sender da domain In this diagram the delivery mode setting for the local post office is Use App Thresholds and the threshold is not exceeded Message Delivery to a Different Post Office 21 Stage Icon Description The GroupWise client performs the following actions for the sender Sender s BA Adds the message to the message database msgnnn db assigned to the GroupWise sender Client Creates a pointer in the sender s user database userxxx db so the message appears in the sender s mailbox as a s
148. ng MTA Polling of Input Queues in the Domain and Post Offices in Domain Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the status message the MTA picks it up from the recipient s post office and transfers it to the MTA in progress gwinprog queue From there the MTA transfers the message to the output queue in the sender s post office The MTA output queue is the input queue for the POA in the sender s post office D de 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 well Sender s POR if the recipient has opened the message Post Office do When the sender checks the sent items in his or her mailbox in the GroupWise Sender pen client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Mapped UNC 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 mapped or UNC link between the post office and the domain is closed K E WPCSIN Ca b WPCSOUT Caps 6 L 9 7 b li WPCSIN P L 9 7 OFMSG eE L msgd 24db GWINPROG OSER U L userxzxdbd MSHOLD OFFILES DOMAINMS L FDO7F e fone WPCSOUT ADS POSTE Ca o 7 OFS GATEWAY oz P L 9 7 POAb DOMAINK Lo Message Delive
149. ng installation you can create a software distribution directory on your network from which you subsequently install the GroupWise agents and GroupWise client software The default software distribution directory is opt novell groupwise software install file The install file is the script you use to install all components of Group Wise on Linux See Linux Setting Up a Basic GroupWise System in the GroupWise 7 Installation Guide agents directory The agents subdirectory contains all files associated with Group Wise agents Post Office Agent POA Message Transfer Agent MTA novell groupwise agents version date i386 rpm The novell groupwise agents version date 1386 rpm file is the GroupWise agent package that is installed by the Installation script It installs the POA and the MTA You can install the agent package manually if necessary To see what files are installed by the package see Linux Installation Directory on page 102 Software Distribution Directory 147 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 See Linux Installation Directory on page 102 S99grpwise file The S99grpwise file is the G
150. ns Gathers the requested items from the GroupWise Remote user s master mailbox msgnnn db Gathers any attachments for requested items from the post_office offiles fd0 f6 subdirectory in the GroupWise Remote user s post office Compiles the information into a response file and places it in the priority 1 subdirectory of the MTA input queue for return to the GroupWise Remote user Message Delivery to and from GroupWise Remote 51 Stage O MTA in Remote User s Domain Async Gateway Async Gateway a Async Gateway Modem Connection O GroupWise Remote GroupWise Remote Remote User Icon MTA a Description When the MTA in the GroupWise Remote user s domain detects the response for the GroupWise Remote user the MTA picks it up from its post office input queue and transfers it to its output queue in the Async Gateway directory under wpgate in the GroupWise Remote user s domain The MTA output queue in the Async Gateway directory is the input queue for the Async Gateway The Async Gateway picks up the response file and moves it to the priority 1 subdirectory of its output queue If the connection to the GroupWise Remote user is still active the Async Gateway compresses the response files and moves them to the CMP directory If the connection is no longer available the response files wait in the connection_id 1 subdirectory until a new connection is established by the GroupWis
151. ns for the GroupWise Remote user Remote Updates the GroupWise Remote message database msg db with any items requested from the GroupWise Remote user s master mailbox Creates pointers in the GroupWise Remote user database user db so the messages gathered from the master mailbox appear in the user s GroupWise Remote mailbox Places any requested attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments The user s GroupWise Remote mailbox now contains current copies of requested items from the user s master mailbox EN The GroupWise user can now review current GroupWise mail after the Remote pen connection to the master GroupWise system is no longer available User Modem Link to the Remote User through the Async Gateway This message flow diagram illustrates how a GroupWise Remote user can access the master Group Wise system through the GroupWise Async Gateway rR L GWOUT L CONNECTION JD Mi Message Delivery to and from GroupWise Remote 49 50 Stage Remote User GroupWise Remote GroupWise Remote o GroupWise Remote Modem Connection Async Gateway Async Gateway Icon a Description The GroupWise user who is not currently connected to the network sends a message to another GroupWise user or crea
152. nstallation a customized version of the Internet Agent startup file is created in sys system This customized version has the home startup switch automatically set to the domain directory where the Internet Agent s queue directories are located See Using Internet Agent Startup Switches in Internet Agent in the GroupWise 7 Administration Guide This file contains all language specific information for the Internet Agent The digit n is a version number The last two characters xx are a language code 110 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwia ncf file The gwia ncf file is the NetWare configuration file that automatically loads the Internet Agent whenever the server is restarted A typical gwia ncf file would look similar to the following load sys system gwia gwia cfg x 10 nlm files The x 10 nlm programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed gwia xml file The gwia xml file is a specialized Internet Agent configuration file for use in the XIS environment Linux Installation Directory Ea opt novell groupwise agents Linux agent installation directory 3 bin Subdirectory for GroupWise agent executables LJ gwia Internet Agent executable J gwia xml Internet Agent XIS configuration file 3 lib Subdirectory for GroupWlse agent library files J gwiaxxx fil Internet Agent language information file J
153. nternet Agent as it converts and builds messages for transfer across the Internet mmddlog nnn file The mmddlog nnn files hold error and status messages about the functioning of the Internet Agent 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 For more information log files see Using Internet Agent Log Files in Internet Agent in the GroupWise 7 Administration Guide Message Transfer Storage Directories 83 wpcsin directory wpcsout directory gwhold directory acct file The acct file contains information about the messages the Internet Agent sends each day It is e mailed to the accounts each day at midnight For more information about the accounting files see Tracking Internet Traffic with Accounting Data in Internet Agent in the GroupWise 7 Administration Guide set file The set file stores Internet Agent console settings such as color log settings and so on For more information see Using the Internet Agent Server Console stat file The stat file stores statistics about the Internet Agent s functioning For information about the statistics provided by the Internet Agent see Statistics in Internet Agent in the GroupWise 7 Administration Guide proc file The proc file is the lock file for the Internet Agent process The proc file is op
154. ode You can change the location of the cache directory as described in Modifying WebPublisher Settings in WebAccess in the GroupWise 7 Administration Guide 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 Linux Installation Directory E opt novell groupwise Novell GroupWise installation directory 3 agents Linux agent installation directory y bin Subdirectory for GroupWise agent executables LJ gwinter WebAccess Agent executable gwinter xml WebAccess Agent XIS configuration file L webac70axx waa Boilerplate WebAccess startup file 3 lib Subdirectory for GroupWise agent library files _ so Supporting shared library files Es image Subdirectory for icon images Agent Installation Directories 117 E share L webac70a waa LJ gwdva dva E webcon de help E webaccess J webacc cfg O commgr cfg J spellchk cfg J Idap cfg a default Es logs users En webpublisher o webpub cfg J commgr cfg Es default logs dl cache template xx LJ webacc tpt L publish tpt E Jetc init d grpwise wa E rc3 d Ll S99grpwise wa ey re5 d LJ S99grpwise wa E var log E novell groupwise Ea domain webac70a E 000 prc Ll mmddgwia nnn Subdirectory for agent shared files WebAccess Agent startup file Document Viewer Agent startup file Subdirectory for agen
155. ogress gwinprog queue If the TCP IP link to the recipient s post office were closed the message would be placed in the closed post office s holding queue in the MTA s mslocal directory for later transfer The resulting message flow would be parallel to what occurs when a domain is closed For a similar message flow that illustrates how messages to closed locations are handled see TCP IP Link Closed Transfer between Domains Delayed on page 30 Message Delivery to a Different Post Office 19 Stage Icon D POA for Recipient s POA Post Office 5 POA for Local Post Office POA O Recipient s GroupWise Client Recipient O Recipient s GroupWise Client da POA for Recipient s POA Post Office a MTA for Local Domain MTA a MTA for Local Domain MTA Description When it receives the new message the POA for the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachment
156. omain transfers the administrative message to the MTA in progress gwinprog queue From there the MTA communicates the administrative message to the POA in the post office by way of TCP IP The administrative message notifies the POA that a GroupWise object has been added modified or deleted Historical Note In earlier versions of GroupWise this function of the POA was handled by a separate agent the Administration Agent ADA The ADA no longer exists in GroupWise The POA creates a copy of the administrative message in the priority 2 subdirectory of the administrative input queue wpcsout ads in the post office After the update is made successfully the copy will be deleted The POA updates the post office database wphost db to reflect the addition modification or deletion performed in ConsoleOne and deletes the administrative message from its administrative input queue Mapped UNC Link between the Domain and the Post Office 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 Group Wise system In this diagram the MTA writes the administrative message into the POA input queue in the post office 54 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure D onn db Administrator ConsoleOne Ta MTA for Domain 5 HTA POA for Post Office 5 POA Ri
157. on is a sequence number for multiple log files created on the same day For example 0518web 002 is the second WebAccess Agent log file created on May 18 Windows Installation Directory Es c webacc Windows WebAccess Agent installation directory gwenv1a dll GroupWise Agent Engine LJ gwinter exe WebAccess Agent program _I strtweb bat WebAccess Agent batch file _ webac70a waa WebAccess Agent startup file l gwdva dva Document Viewer Agent startup file 122 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure c webacc gwenv1a dll file gwinter exe file strtweb bat file LJ gwwanxx dll WebAccess Agent language information file L gwwasnmp di Customized DLL program for SNMP L gwwww1 dll Customized DLL program for MIME L x 10 dll XIS DLL programs LJ gwinter xml XIS agent configuration file cache template xx Subdirectory for HTML template files J webacc tpt WebAccess template files LJ publish tpt WebPublisher template files 3 help Subdirectory for GroupWise agent console help files Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console See Apache Tomcat Installation on page 129 See also WebAccess Agent Queue Directory on page 88 On a Windows server the WebAccess Agent can be installed in any directory you choose The default location is c webacc The WebAccess Agent desktop icon is set up to include the full path to
158. onsole on the server where it runs See Using the POA Server Console in Post Office Agent and Using the MTA Server Console in Message Transfer Agent in the GroupWise 7 Administration Guide The first five characters of the filename are the agent name The digit n is a version number The last two characters xx are a language code nlm_agentnxx fil files grpwise ncf file x 10 nlm files nim_agent xml files These files contain all language specific information for the POA and the MTA The first five characters of the filename are the agent name The digit n is a version number The last two characters xx are a language code The grpwise ncf file is the NetWare configuration file that automatically loads the agents whenever the server is restarted A typical grpwise ncf file would look similar to the following load sys system gwmta nlm corpdom mta load sys system gwpoa nlm acctpo poa For more information see Starting the NetWare POA in Post Office Agent and Starting the NetWare MTA in Message Transfer Agent in the GroupWise 7 Administration Guide The x 10 nlm programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed The n m_agent xml files are specialized agent configuration files for use in the XIS environment Agent Installation Directories 1014 gwtsa nim file gwtmstmp nIm file gwtsaxx fil fi
159. or GroupWise agent console help files Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console See Apache Tomcat Installation on page 129 See also WebAccess Agent Queue Directory on page 88 NetWare Internet Agent installation directory gwenn5 nlIm file gwinter nIm file strtweb ncf webac70a waa file On a NetWare server the GroupWise WebAccess Agent is typically installed in the sys system directory You can choose a different location during installation The gwenn5 nlm file is the GroupWise 7 Agent Engine a program that is shared by all GroupWise agents It provides the following services to the agents Database management File operations Message handling Thread management Semaphores file record locking Date time services The first agent loaded on a server automatically loads the GroupWise Agent Engine The gwinter nlm file is the WebAccess Agent program The strtweb ncf file is the NetWare configuration file that automatically loads the WebAccess Agent whenever the server is restarted A typical strtweb ncf file would look similar to the following load sys system gwinter webac70a waa It includes the WebAccess Agent startup file in the load command For more information see NetWare and Windows Starting GroupWise WebAccess in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide
160. or application startup scripts Startup script for the Monitor Agent Standard Linux location for run level 3 symbolic links Symbolic link to the startup script for the Monitor Agent Standard Linux location for run level 5 symbolic links Symbolic link to the startup script for the Monitor Agent Standard Linux location for application log files Subdirectory for GroupWise agent log files Agent Installation Directories 125 agents directory bin directory lib directory share directory il gwmon Subdirectory for Monitor Agent log files L mmddmon nnn Monitor Agent event log files L mmddhist nnn Monitor Agent history log files On a Linux server the Monitor Agent is always installed in subdirectories of opt novell groupwise agents 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 Monitor Agent in Monitor in the GroupWise 7 Administration Guide The lib directory holds GroupWise shared library files so files These files are Linux shared library files that provide information to the Monitor Agent executable The share directory holds agent startup files and files that are used by the agent consoles and Web consoles monitor xml file The monitor xml file is a specialized configuration file for use in the XIS environment gwmonitor directory The gwmonitor
161. or prohibited nuclear missile or chemical biological weaponry end uses Please refer to www novell com info exports for more information on exporting Novell software Novell assumes no responsibility for your failure to obtain any necessary export approvals Copyright 1993 2005 Novell Inc All rights reserved No part of this publication may be reproduced photocopied stored on a retrieval system or transmitted without the express written consent of the publisher Novell Inc has intellectual property rights relating to technology embodied in the product that is described in this document In particular and without limitation these intellectual property rights may include one or more of the U S patents listed at http www novell com company legal patents and one or more additional patents or pending patent applications in the U S and in other countries Novell Inc 404 Wyman Street Suite 500 Waltham MA 02451 U S A www novell com GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure August 15 2005 Online Documentation To access the online documentation for this and other Novell products and to get updates see www novell com documentation Novell Trademarks Novell is a registered trademark of Novell Inc in the United States and other countries Novell is a registered trademark of Novell Inc in the United States and other countries NetWare is a registered trademark of Novell Inc in the United Stat
162. ority 6 subdirectory of the POA input queue wpcsout ofs in the post office is for low 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 mailboxes 7 directory The priority 7 subdirectory of the POA input queue wpcsout ofs in the post office is for low priority status messages coming back to senders in the local post office For example the MTA places status responses to low priority user messages here The POA then updates the message databases and senders mailboxes with current message status mmddpoa nnn files The mmddpoa nnn files are POA log files The POA creates log files to inform you of its processing and any problems it encounters By default these log files are created in the wpcsout ofs directory You can change the location if needed See Using POA Log Files in 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 The three digit extension is a sequence number for multiple log files created on the same day For example 0518poa 002 is the second POA log file created on May 18 Message Transfer Storage Directories 75 ads directory chk directory problem directory wprof50
163. orrespond to the priority 0 7 subdirectories located in each domain post office or gateway See the following directory structures for more information about its priority 0 7 subdirectories Domain Directory on page 59 Post Office Directory on page 66 The mtaname files in the closed location holding queues provide the name associated with the domain post office or gateway holding queue They can help you check links between MTAs in ConsoleOne without going to the MTA agent console to determine the location name To associate a location name with its holding queue directory from the MTA agent console click Configuration Status gt select the location gt click Details gwvsscan directory The gsvsscan subdirectory is the working directory where third party virus scanning programs that snap in to the MTA can perform their processing mtaconv directory The mtaconv subdirectory is the working directory where the MTA converts Group Wise 7 6 x and 5 x messages to 4 x format for transfer to a GroupWise 4 x system After the conversion is finished this directory should be empty Message Transfer Storage Directories 81 Internet Agent Queue Directory The following directories and files are found under the domain wpgate structure for the Internet Agent after the software has been installed and the Internet Agent has processed messages 3 domain wpgate gwia GroupWise Internet Agent home directory 3 000 prc Internet
164. ory After the Internet Agent completes the transmission with the destination host it moves the S file from the send directory to the result directory GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Internet Agent for Sender s Domain Actor Action GWIA The Internet Agent analyzes the files in the result directory comparing the SMTP reply codes in the R file Co If the Internet Agent was successful at sending the message meaning the R file had the 250 OK SMTP reply code then the two files are deleted The Internet Agent sends a Transferred status message to the sender s Sent Items folder If the R file has a temporary transmission error meaning it has a 400 level SMTP reply code such as 450 Host Down the Internet Agent moves the S file to the defer directory and re queues the message to the send directory according to the Retry Schedule At the end of the Retry Schedule if the Internet Agent is still unsuccessful at transmitting the message the Internet Agent moves the S file to the gwprob directory and deletes all the schedule files in the defer work directory The Internet Agent sends an Undeliverable status message to the sender s Mailbox and Sent Items folder If the R file has a fatal rather than a temporary error meaning it has a 500 level SMTP reply code such as 550 Host Unknown the Internet Agent sends an Undeliverable status message immediately to the sender s Mailbox and S
165. oupWise 7 6 x 5 x post offices in that domain The original gwpo dc file is located in the domain directory of the GroupWise CD There is also a copy in the po directory Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp Post offices were originally called hosts Hence the name wphost db Some naming conventions were originally preserved for backward compatibility The po subdirectory contains the files from which post offices are created The ngwguard dc file is the distribution copy of the data dictionary for building the following databases in the post office newguard db guardian database dmxxnn0 FF document management databases msgnn db message databases userxxx db user databases puxxxxx db databases for replicated items like shared folders If the ngwguard dc file is missing from a post office new databases cannot be created in the post office so the post office cannot grow The original ngwguard dc file is located in the po directory of the GroupWise CD GroupWise Remote also uses the ngwguard dc file as the data dictionary for its local databases The client subdirectory contains all files associated with GroupWise Windows client See Client in the GroupWise 7 Administration Guide The install file is the script that Group Wise Cross Platform client users run to install and set up the GroupWise client on their Linux or Macintosh
166. oupWise 7 Administration Guide Message Transfer Storage Directories 89 template directory The template directory holds the HTML templates used for viewing documents in HTML format commgr cfg file comint cfg file The commgr cfg file in the WebAccess Agent queue directory contains information for communication between the WebAccess Agent and the WebAccess Application including the IP address and port where the WebAccess Agent is running the number of threads that are running and the encryption key for the WebAccess Agent This communications information is gathered during installation For more information see Configuring the GroupWise Service Provider in WebAccess in the GroupWise 7 Administration Guide 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 webaccess on Linux and c novell webaccess on Windows The copies are synchronized automatically by the WebAccess Application The commer cfg file is also copied to the webpublisher subdirectory on the Web server The comint cfg file in the WebAccess Agent queue directory is read by the WebAccess Agent on startup It contains the same communications information as the commgr cfg file and is synchronized with it automatically mimetype cfg file The mimetype cfg file enables you to customize MIME content type mappings for various attachment types The
167. oupWise 7 Administration Guide The help directory holds the help files that you can view from the agent Web consoles See Using the POA Web Console in Post Office Agent and Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide domain directory wpdomain dc file The domain subdirectory contains the files from which domains are created The wpdomain dc file is the distribution copy of the data dictionary for rebuilding GroupWise 4 x domain databases wpdomain db files in secondary domains If the wpdomain dc file is missing from the primary domain you cannot rebuild Group Wise 4 x secondary domains The original wpdomain dc file is located in the domain directory of the Group Wise distribution media Historical Note WordPerfect Office WP Office the predecessor of GroupWise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain dc Some naming conventions were originally preserved for backward compatibility Software Distribution Directory 141 gwdom dc file wphost dc file gwpo dc file po directory ngwguard dc file The gwdom dc file is the distribution copy of the data dictionary for creating and rebuilding Group Wise 7 6 x and Group Wise 5 x domain databases wpdomain db files in secondary domains If the gwdom dc file is missing from the primary domain you cannot create or rebuild Group Wise 7 6 x 5 x secondary domains
168. oupWise 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 For a GroupWise Remote installation the GroupWise Remote directory contains the same files as would be installed on a workstation connected to the network Whenever GroupWise cannot make a network connection it checks for a GroupWise Remote mailbox to access See Remote Mailbox Directory on page 95 grpwise exe file The grpwise exe file is the GroupWise 7 client program for use with Windows gwtip exe file The gwtip exe file is the GroupWise Tip of the Day program which displays helpful information about a GroupWise feature each time you start the GroupWise client notify exe file The notify exe file is the program that alerts you whenever you have incoming items when your outgoing items are opened or when you have an upcoming appointment Notify can alert you in four ways a sound a dialog box a small icon or by launching an application addrbook exe file The addrbook exe file is the program that accesses the GroupWise Address Book The Address Book contains information for all Novell eDirectory users GroupWise external users GroupWise extern
169. ous Internet e mail programs See Internet Agent in the GroupWise 7 Administration Guide novell groupwise gwia version date i386 rpm file The novell groupwise gwia version date 1386 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 Internet Agent Installation on page 109 root directory The root directory contains boilerplate versions of the configuration files that are installed to the Internet Agent root directory under the domain directory For more information see Internet Agent Queue Directory on page 82 S99grpwise ia file The S99grpwise ia file is the Internet A gent startup script During installation it is named grpwise ma and placed in etc init d If you choose to have the Internet Agent start automatically when the server reboots the Installation script places symbolic links to it named S99grpwise ma in the rc3 d and rc5 d subdirectories of etc init d For more information see Linux Starting the Internet Agent in Installing the GroupWise Internet Agent in the GroupWise 7 Installation Guide Software Distribution Directory 151 webacces directory webserver directory The internet webacces subdirectory contains the GroupWise WebAccess software which allows users to access their GroupWise mailboxes from a Web browser See WebAccess in the GroupWise
170. ox Caching mailbox database directory Cached message database Cached user database Cached Address Book Data dictionary for cached Address Book Guardian database Data dictionary for guardian database Guardian database roll forward log Guardian database fall back file Database for shared folders GroupWise Check database Log file created by the Repair Mailbox feature Connection log Document Management Services directory Shared DMS database Document databases Subdirectory for documents in the Caching mailbox QuickFinder index for documents in the Caching mailbox QuickFinder index for messages in the Caching mailbox Input queue for the Caching mailbox Priority subdirectories Output queue for the Caching mailbox Priority subdirectories Output queue to the Online mailbox Input queue from the Online mailbox 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 It is created in the directory where the GroupWise client is installed which is typically novell groupwise Message Transfer Storage Directories 91 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 while you can restrict what gets downloaded into your Remote mailbox rofdata directory msg db file user db file wprof db file wp
171. pWise icns file The Group Wise icns file contains all the images that display in the Cross Platform client lib directory The lib directory holds library files that provide information required by the Cross Platform client gwen xxx fil file The gwenlxxx file provides the language specific strings for the localized versions of the Cross Platform client The xx is a two letter language code ngwguard dc file The ngwguard dc file is the data dictionary for building the databases used by the Cross Platform client It is parallel in function to the ngwguard dc file in the post office 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 Java directory The Java directory holds the version of the Java Runtime Environment JRE that is required by the Cross Platform client 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 GroupWise Client Installation Directories 161 dylib files The dylib files are dynamic library files the provide information to the Cross Platform client program 162 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure
172. priority Message Transfer Storage Directories 63 css directory problem directory 2 directory The priority 2 subdirectory of the MTA admin thread input queue wpcsout ads in the domain is 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 The MTA admin thread then processes the messages and makes the specified updates 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 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 It contains the eight standard priority subdirectories Historical Note In an earlier version of GroupWise the Message Transfer Agent MTA was called the Connection Server CS and this specialized subprocess was called the Connection Server Server css Some naming conventions were originally preserved for backward compatibility 0 directory The priority 0 subdirectory of the CSS input queue wpcsout css in the domain is for service requests that demand an immediate response from the MTA For example when you restart the MTA
173. ransfers it to the output queue in the recipient s post office The MTA output queue is the input queue for the POA in the recipient s post office GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage POA for Recipient s Post Office 6 Recipient s GroupWise Client Recipient Recipient s GroupWise Client MTA for Recipient s Domain MTA for Sender s Domain a POA for Sender s Post Office Sender Icon MTA HTA POA Description The POA polls its input queue regularly When it detects a new message the POA for the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office The Notify component of the
174. recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client creates an Opened status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office For mapped and UNC links the MTA scans its input queue in each post office 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the status message the MTA picks it up from the recipient s post office and transfers it to the MTA in progress gwinprog queue From there the MTA in the recipient s domain transfers the status message to the output queue in the sender s domain The MTA in the sender s domain also polls its domain input queues When it detects the status message the MTA in the sender s domain picks it up and transfers it to the output queue in the sender s post office The MTA output queue is the input queue for the POA in the sender s post office The POA in the sender s post office updates the sender s message database msgnnn db with the Delivered status information and possibly Opened as well if the recipient has opened the message When the sender checks the sent items in his or her mailbox in the GroupWise cl
175. riority 2 subdirectory of the POA input queue wpcsout ofs in the post office is for high priority user messages being delivered to recipients in the local post office 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 The POA then updates the message databases and senders mailboxes with current message status 4 directory The priority 4 subdirectory of the POA input queue wpcsout ofs in the post office is for normal priority user messages being delivered to recipients in the local post office For example the MTA places normal priority user messages here The POA then updates the message databases and recipients mailboxes Most messages in your GroupWise system pass through the priority 4 subdirectory 5 directory The priority 5 subdirectory of the POA input queue wpcsout ofs in the post office is for normal priority status messages coming back to senders in the local post office For example the MTA places status responses to normal priority user messages here The POA then updates the message databases and senders mailboxes with current message status 6 directory The pri
176. ripts that you want your Linux server to run when it is booted to run level 3 multi user boots to a text mode login prompt without The X Window System The symbolic link to the grpwise wa script is S99grpwise wa It is created if you choose during installation to have the WebAccess Agent start automatically when the server boots rc5 d directory The rc5 d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 5 multi user boots to The X Window System login dialog box The symbolic link to the grpwise wa script is S99grpwise wa It is created if you choose during installation to have the WebAccess Agent start automatically when the server boots Ivar 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 000 prc directory Within the 000 prc directory the WebAccess Agent creates log files mmddweb nnn to inform you of its processing and any problems it encounters For more information about log files see Controlling WebAccess Agent Logging in WebAccess in the GroupWise 7 Administration Guide The first two digits of the filename represent the month the next two digits represent the day of the month The three digit extensi
177. rof dc file ngwguard db file ngwguard dc file ngwguard rfl file The rofdata directory contains the databases accessed by the GroupWise Windows client when running in Caching mode The databases in rofdata are similar to the databases found in post offices For comparison see Post Office Directory on page 66 Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the rof in rofdata Some naming conventions were originally preserved for backward compatibility The msg db file is the cached equivalent of the msgnn db files in the ofmsg directory in your post office The msg db file contains copies of messages from your Online mailbox The user db file is the cached equivalent of the userxxx db files in the ofuser directory in your post office The wprof db file contains the cached version of the GroupWise Address Book Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the wprof in wprof db Some naming conventions have been preserved for backward compatibility The wprof dc file is the data dictionary for the cached Address Book wprof db Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the wprof in wprof dc Some naming conventions have been preserved for backward compati
178. roup Wise 5 5 views The ofviewxx ini file configures views from earlier versions of GroupWise Software Distribution Directory 143 zen directory The zen directory contains files that let you use ZENworks Desktop Management to distribute the Group Wise Windows client to users workstations See Using ZENworks Desktop Management to Distribute the GroupWise Windows Client in Client in the GroupWise 7 Administration Guide admin directory c1admin directory monitor directory utility directory The admin subdirectory contains subdirectories for administrative tools that can be used with Group Wise The admin cladmin subdirectory contains the GroupWise snap ins to ConsoleOne The admin monitor subdirectory contains the GroupWise 7 6 x Monitor program an SNMP monitoring program for use with the GroupWise agents See Monitor in the GroupWise 7 Administration Guide The admin utility subdirectory contains helpful GroupWise utilities gwcheck directory The admin utility gwcheck subdirectory contains the GroupWise Check utility See GroupWise Check in Standalone Database Maintenance Programs in the GroupWise 7 Administration Guide gwcesrgen directory The admin utility gwcheck subdirectory contains the GroupWise Generate CSR utility See Server Certificates and SSL Encryption in Security in the GroupWise 7 Administration Guide setupip directory The admin utility setupip subdirectory
179. roupWise agent startup script During installation it is named grpwise and placed in etc init d If you choose to have the agents start automatically when the server reboots the Installation script places symbolic links to it named S99grpwise are placed in the rc3 d and rc5 d subdirectories of etc init d For more information see Linux Installing and Starting the GroupWise Agents in Installing a Basic GroupWise System in the GroupWise 7 Installation Guide domain directory wpdomain dc file gwdom dc file wphost dc file The domain subdirectory contains the files from which domains are created The wpdomain dc file is the distribution copy of the data dictionary for rebuilding GroupWise 4 x domain databases wpdomain db files in secondary domains Ifthe wpdomain dc file is missing from the primary domain you cannot rebuild GroupWise 4 x secondary domains The original wpdomain dc file is located in the domain directory of the GroupWise distribution media Historical Note WordPerfect Office WP Office the predecessor of GroupWise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain dc Some naming conventions were originally preserved for backward compatibility The gwdom dc file is the distribution copy of the data dictionary for creating and rebuilding GroupWise 7 6 x and 5 x domain databases wpdomain db files in secondary domains Ifthe gwdom dc file is missing from the prima
180. ry o oo aaa a 147 agents directory y tema aie bla A a Ba eee ha ae a BE OR A O eee A 147 domain directory fei edo A ee Sede Bate ows Ga dee AE As eked ela AA CAS E 148 POIFECIOLY croea ge ee eb ae ed eb deb wee bee be eee bee be oa ee 149 cli nt directory NN 149 OlviewS directory cocoa aa ee ea oe ER ee ee a eee bee ep ee bP eee wee he 150 Contents 7 admin directory 2 4 4 4 4 2 2 2b oie ee a bet kb be BRR Le oe ER bbe ee 150 intermet directOny zee puke ace E Boe A eB ale 2k SR eA eh eR eee as 151 license directory 2 3 50 ee Pe A cee A et gly eve Al Ge ee 152 AOS AMECA he as ae hk e as ee ee ee a ee ne de hom eas arde 153 QWINSUGIFECIOLY A sp eas ee A A ee A ee BE eee Ye 153 10 GroupWise Client Installation Directories 155 Windows ClGAT 3 isc oe FH oe ee A Eo oR UM Re be dt eek Ee ae A 155 CA NOVeEll GroUPWiS s po oe he ee a ye eS on eee Bk ee be ns ee ES 156 OIpwise exe file co ia e oie ch Meas ae a EE he ns Ea ok in he e Ged ek 156 Qwiip exe file 2 20 ewan bg Eee ae ee ee a E aan ta sy GG eee EA se 156 notify Mile ca Bee a eS ek ei E a Ga ee AS eh on es a ee ee ee E 156 addrbook exe Tiles cre iror ei OB sor eS Bed Sok ee E A A ee ee Ee eS 156 gwehe ck exe fil n sere ae io daa Se eae Sa a Se eh EA eal de eee SSS WP Ed 156 htrsetupiexe filen cami ee FB AE de ee A ae A A be Bee onde ah ck eal hoe sls 156 Qwimpex exe fil 24 5 An ek koe Rk Bee ee ek RM Boe le Bk eo ek AO ee eo a 157 gwmailto exe file iis ane ee ek
181. ry domain you cannot create or rebuild GroupWise 7 6 x 5 x secondary domains The original gwdom dc file is located in the domain subdirectory of the GroupWise distribution media Historical Note WP Office the predecessor of GroupWise was originally designed by WordPerfect Corporation WPCorp Hence the wp in wpdomain db Some naming conventions were originally preserved for backward compatibility The wphost dc file is the distribution copy of the data dictionary for rebuilding Group Wise 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 There is also a copy in the po subdirectory 148 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure gwpo dc file po directory ngwguard dc file client directory install file 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 The gwpo dc file is the distribution copy of the data dictionary for creating and rebuilding Group Wise 7 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 Gr
182. ry to a Different Post Office 23 24 Stage Icon Sender Sender s GroupWise Client MTA for Local Domain MTA Description The user sends a message to recipients in a different post office in the same domain In this diagram the delivery mode setting for the local post office is Use App Thresholds and the threshold is not exceeded The GroupWise client performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the appropriate priority 0 7 subdirectory of the MTA input queue in the sender s post office If client server mode were in effect for the post office these actions would be performed by the POA instead of the GroupWise client See Access Mode Client Server on page 13 For mapped and UNC links the MTA scans its input queue in each post office 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 and Post O
183. s puxxxxx db databases for replicated items like shared folders ngwguard fbk file The ngwguard fbk file in the post office is a fall back copy of the ngwguard db file If the 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 See Guardian Databases in Databases in the GroupWise 7 Administration Guide Message Transfer Storage Directories 77 ngwguard rfl file The ngwguard rfl file in the post office is a roll forward transaction log of every database transaction that has taken place since the last copy of the ngwguard fbk file was created See Guardian Databases in Databases in the GroupWise 7 Administration Guide ngwcheck db The ngwcheck dbfile in the post office is the database that controls GWCheck s multithreaded processing It contains job and task records that are used to synchronize and summarize GWCheck requests as they progress agentinstall txt The agentinstall txt file in the post office records all the information that you provide when you install the POA for the post office MTA Local Queue Directory EA mslocal L mmddxxx nn Es msglog LJ mmddmsg nn Es gwinprog 0 7 y mshold E domainms
184. s For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office It also communicates the Delivered status message directly to the MTA by way of TCP IP and when that transmission is successful the copy in the MTA input queue is deleted The POA communicates to the GroupWise client by way of TCP IP that a new message has arrived The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client communicates the Opened status message to the POA by way of TCP IP The POA for the recipient s post office communicates the status message to the MTA by way of TCP IP The MTA places the status message into the MTA in progress gwinprog queue The MTA communicates the status message to the POA for the sender s post office by way of TCP IP 20 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Icon Description de The POA for the sender s post office updates the sender s message POA in database msgnnn db with the Delivered status information and possibly Sender s POA Opened as well if the recipient has opened the message Post Office de A The POA communicates the Opened status to the se
185. s ofviews Es admin Ll novell groupwise admin ver date i386 rpm LJ novell groupwise dbcopy ver date i386 rpm LJ novell groupwise gwcheck ver date i386 rpm L NOVLc1 Linuxjre ver i386 rpm monitor Es linux O novell groupwise gwmon ver date i386 rpm LJ novell groupwise monitor ver date i386 rpm Es startup J S99grpwise ma Es internet a gwia Es linux O novell groupwise gwia ver date i386 rpm Es root LJ gwia cfg J gwauth cfg J mimetype cfg J gwac dc E preamble txt J preamble all L statusxx xml E startup O S99grpwise ia Post office data dictionary files Data dictionary for message store databases Data dictionary for GroupWise 4 x post office databases Data dictionary for GroupWise 7 6 x and 5 x post office databases GroupWise client software Subdirectory for Linux software Cross Platform client installation script Cross Platform client package GroupWise client view files GroupWise administrator software GroupWise snap ins to ConsoleOne package GroupWise Database Copy Utility package GroupWise Check Utility package ConsoleOne JRE update package GroupWise Monitor software Subdirectory for Linux software Monitor Agent package Monitor Application package Subdirectory for startup files Monitor startup script Internet connectivity software GroupWise Internet Agent software Subdirectory for Linux software GroupWise Internet Agent package Subdirectory for boilerplate supporting files Internet Agent startup file
186. s from Group Wise Remote are processed through the priority 1 subdirectory of wpcsin When the user initiates the connection to the master GroupWise system GroupWise Remote polls the wpcsin 1 directory and compresses the outgoing messages requests or both into a file If the compressed file totals over 50 KB additional compressed files are created GroupWise Remote then moves the compressed files into the wpgwsend directory Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp The Message Transfer Agent MTA was originally named the Connection Server CS Hence the directory name wpcsin for the input queue although the MTA is not involved in processing messages in your Remote mailbox Some naming conventions were originally preserved for backward compatibility The priority 0 7 subdirectories in the connection input queue wpcsin in the remote mailbox directory parallel those found in the wpcsin directory in the remote user s post office on the master GroupWise system rofdata directory msg db file user db file wprof db file The rofdata subdirectory in the remote mailbox directory contains the databases accessed by GroupWise Remote The databases in rofdata are similar to the databases found in post offices Historical Note An earlier version of GroupWise Remote designed by WordPerfect Corporation WPCorp was named WP Office Remote Hence the rof in rofdat
187. s just a boilerplate file with no switches set during installation Linux The Linux Internet Agent uses the gwia cfg file created in opt novell groupwise agents share during installation The gwia cfg file under the domain 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 The route cfg file enables you to customize routing for specific hosts For more information see Using a Route Configuration File in Internet Agent in the GroupWise 7 Administration Guide The gwauth cfg file enables the Internet Agent to log in to SMTP hosts that require authentication For more information see SMTP Host Authentication in Internet Agent in the GroupWise 7 Administration Guide The mimetype cfg file enables you to customize MIME content type mappings for various attachment types For more information see Customizing MIME Content Type Mappings in Internet Agent in the GroupWise 7 Administration Guide Message Transfer Storage Directories 85 exepath cfg file frgnames cfg file xspam cfg file gwac db file gwac dc file preamble txt file preamble all file blocked txt file The exepath cfg file is used by ConsoleOne to locate the gwia cfg file This enables ConsoleOne to write any configuration setting changes to the gwia cfg file or update Novell eDirectory with any changes from the file Th
188. sages and or requests into a file If the compressed file totals over 50 KB additional compressed files are created The GroupWise client next moves the compressed files into the wogwsend directory then dials in to the gateway and logs in After the login process is completed GroupWise Remote transmits the compressed message request file s across the modem connection to the system where the user s master mailbox is located The GroupWise Async Gateway picks up the message request files and decompresses them The Async Gateway moves the message request files to the MTA input queue GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage D MTA for Remote User s Domain O POA for Remote User s Post Office Icon MTA POA Description For mapped and UNC links the MTA for the GroupWise Remote user s domain 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 and Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide When it detects the new message or request from the GroupWise Remote user the MTA picks it up from its domain input queue and transfers it to its output queue in the post office where the GroupWise Remote user s master mailbox is located The MTA output queue is the input queue for the POA in the post office where the GroupWise Remote
189. se 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 notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office It also communicates the Delivered status message directly to the MTA by way of TCP IP When that transmission is successful the copy in the MTA input queue is deleted The POA communicates to the GroupWise client by way of TCP IP that a new message has arrived The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived Each recipient opens the message in the GroupWise client Each recipient s GroupWise client communicates the Opened status message to the POA by way of TCP IP The POA for the recipient s post office communicates the status message to the MTA by way of TCP IP The MTA places the status message into the MTA in progress gwinprog queue The MTA communicates the status message to the POA for the sender s post office by way of TCP IP Message Delivery to a
190. se was originally designed by WordPerfect Corporation WPCorp Post offices were originally called hosts Hence the name wphost db Some naming conventions were originally preserved for backward compatibility The po subdirectory contains the files from which post offices are created The ngwguard dc file is the distribution copy of the data dictionary for building the following databases in the post office ngweguard db guardian database dmxxnn01 FF document management databases msgnnn db message databases userxxx db user databases puxxxxx db databases for replicated items like shared folders 142 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure If the ngwguard dc file is missing from a post office new databases cannot be created in the post office so the post office cannot grow The original ngwguard dc file is located in the po directory of the GroupWise CD Group Wise Remote also uses the ngwguard dc file as the data dictionary for its local databases client directory The client subdirectory contains all files associated with GroupWise Windows client See Client in the GroupWise 7 Administration Guide setup cfg file The setup cfg file enables you to automate installation of the GroupWise Windows client so that your users do not need to respond to the Setup program s prompts For more information see Installing with the Configuration File setup cfg in Client
191. se Remote was originally designed by WordPerfect Corporation WPCorp Hence the name wpgwrecv Some naming conventions were originally preserved for backward compatibility Remote Mailbox Directory E remote_mailbox T wpcsin 07 E rofdata J msg db _ user db Ll wprof db J wprof dc LJ ngwguard db J ngwguard dc LJ puxxxxx db de gwdms L dmsh db de index El wpgwsend Es wpgwrecv Bel wpcsoutlofs 0 7 J remoten log remote_mailbox directory GroupWise Remote mailbox Input queue for GroupWise Remote Priority subdirectories Remote database directory Remote message database Remote user database Remote Address Book Data dictionary for Remote Address Book Remote guardian database Data dictionary for Remote guardian database Database for shared folders Document Management Services directory Shared DMS database QuickFinder index for Remote mailbox Output queue to master mailbox Input queue from master mailbox Output queue for GroupWise Remote Priority subdirectories Remote connection log The GroupWise remote mailbox is a directory structure that functions similarly to a post office Like a post office it contains databases and input output queues Message Transfer Storage Directories 95 wpcsin directory 0 7 directories The wpcsin subdirectory in the remote mailbox directory is the input queue for the connection that will transfer messages to your master GroupWise system Message
192. se WebAccess in the GroupWise 7 Installation Guide On Linux you can install Apache and Tomcat along with WebAccess and Monitor This automatically integrates WebAccess and Monitor into Apache and Tomcat for you If you are already running Apache and Tomcat you can choose to integrate WebAccess and Monitor into that installation or you can have two Apache Tomcat installations on your server WebAccess and Monitor cannot be used without a supporting Web server For more information see Determining the WebAccess and WebPublisher Applications Configuration in Installing Group Wise WebAccess and Determining the Monitor Application s Configuration in Installing GroupWise Monitor GroupWise 7 Installation Guide license directory The license subdirectory contains the GroupWise Software License Agreement in multiple languages Use the more command to view the License Agreement 152 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure docs directory The docs subdirectory contains language specific subdirectories for the GroupWise 7 Installation 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 gwinst directory The gwinst subdirectory contains supporting files and subdirectories used by the Installation script Software D
193. start the MTA and specify the new location using the work startup switch Historical Note In earlier versions of GroupWise the Message Transfer Agent MTA was called the Message Server MS Hence the ms in mslocal Some naming conventions were originally preserved for backward compatibility The mmddxxx nnn file are MTA log files The MTA creates log files to inform you of its processing and any problems it encounters By default these log files are created in the mslocal directory You can change the location if needed See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide The first two digits of the filename represent the month the next two digits represent the day of the month the next three characters indicate what program created the log The three digit extension is a sequence number for multiple log files created on the same day For example 0518mta 002 is the second MTA log file created on May 18 Historical Note In earlier versions of GroupWise the Message Transfer Agent MTA was called the Message Server MS Hence the ms indicator representing the MTA Some naming conventions were originally preserved for backward compatibility msglog directory The msglog subdirectory contains message logging files It is created when you turn on message logging The MTA receiver threads log messages as they arrive so the MTA worker threads can process messages without having to scan th
194. t Office RE When the sender checks the sent items in his or her mailbox in the GroupWise Sender da client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Alternate Link Configuration Transfer Pull 38 This message flow diagram illustrates how a GroupWise message travels from one user to another when the domains are connected by a transfer pull configuration WPCSIN Lo nen WPCSOUT L_aps Lo b WPCSIN MSLOCAL 0 7 OFMSG ridge L msgo 24db OFUSER L ysereaxdb a OFFILES Lg L_FDO 7F POSTE pire L 0 7 L a7 GATE WAVY GATEWAY OFS L 9 7 Eo Ea DOMAINE DOMINA POAb L 9 7 L 9 7 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Sender Sender s GroupWise Client E MTA for Sender s Domain a MTA for Recipient s Domain Icon na 5 MTA MTA Description The user sends a message to recipients in a post office in a different domain In this diagram the delivery mode setting for the local post office is Use App Thresholds and the threshold is not exceeded The GroupWise client performs 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 Places attachments larger than 2
195. t Offices in Optimizing the MTA in the GroupWise 7 Administration Guide 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 wpcsin for the MTA input queue Some naming conventions were originally preserved for backward compatibility 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 For example ConsoleOne places restart requests and queue reconfiguration requests here for the MTA and gateways MTAs for other domains route Busy Search requests through here when users in other domains check schedules of users in the local domain You can increase throughput for the priority 0 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 The priority 1 subdirectory of the MTA input queue wpcsin in the domain is for service requests of the next highest priority For example ConsoleOne places directory synchronization requests here for the MTA admin thread ConsoleOne places statistics requests here for the MTA to relay to the message logging module for processing MTAs for other domains route GroupWise Remote requests through here when Group W
196. t Web console files Subdirectory for agent Web console help files Subdirectory for WebAccess Application files WebAccess Application configuration file Communications Manager configuration file Novell Speller Application configuration file LDAP service provider configuration file Subdirectory for boilerplate configuration files Subdirectory for WebAccess Application log files Subdirectory for users WebAccess session information Subdirectory for WebAccess Application files WebPublisher Application configuration file Communications Manager configuration file Subdirectory for boilerplate configuration files Subdirectory for WebPublisher Application log files Subdirectory for HTML template files WebAccess template files WebPublisher template files Standard Linux location for application startup scripts Startup script for the WebAccess Agent Standard Linux location for run level 3 symbolic links Symbolic link to the startup script for the WebAccess Agent Standard Linux location for run level 5 symbolic links Symbolic link to the startup script for the WebAccess Agent Standard Linux location for application log files Subdirectory for GroupWise agent log files Domain specific subdirectory for WebAccess Agent log files Processing directory for log files WebAccess Agent log files 118 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure agents directory bin directory lib directory share direc
197. t 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 The novell groupwise dbcopy version date i386 rpm file is the GroupWise Database Copy utility package It is not installed by the Installation script but must be installed manually as described in Using DBCopy on Linux Servers in Databases in the GroupWise 7 Administration Guide novell groupwise gwcheck version date i386 rpm file The novell groupwise gwcheck version date i386 rpm file is the GroupWise Check utility package It is not installed by the Installation script but must be installed manually as described in Starting GWCheck on a Linux Workstation in Databases in the GroupWise 7 Administration Guide NOVLc1Linuxjre version i386 rpm file The NOVLc1Linuxjre version 1386 rpm file is the package that updates ConsoleOne so that it is compatible with the GroupWise Administrator snap ins It is installed for you automatically when you install Group Wise administration monitor directory The monitor subdirectory contains the GroupWise Monitor software See Monitor in the GroupWise 7 Administration Guide 150 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure novell groupwise gwmon version date i386 rpm file The novell groupwise gwmon version date 1386 rpm file is the GroupWise Monitor Agent package that is installed
198. t executable See Installing the Group Wise Cross Platform Client in the GroupWise 7 Cross Platform Client User Guide lib directory The lib directory is the standard Linux location for library files gwen xxx fil file The gwenlxxx file provides the language specific strings for the localized versions of the Cross Platform client The xx is a two letter language code ngwguard dc file The ngwguard dc file is the data dictionary for building the databases used by the Cross Platform client It is parallel in function to the ngwguard dc file in the post office GroupWise Client Installation Directories 159 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 so files The so files are Linux shared library files the provide information to the Cross Platform client executable jre directory The jre directory holds the version of the Java Runtime Environment JRE that is required by the Cross Platform client logs directory The logs directory stores log files generated by the Cross Platform client when an error occurs Cross Platform Client on Macintosh El Applications GroupWise app GroupWise Cross Platform client installation d
199. t 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 in Optimizing the MTA in the GroupWise 7 Administration Guide The priority 4 subdirectory of the MTA input queue wpcsin in the domain is for normal priority user messages routed to recipients in local post offices For example MTAs for other domains place normal priority user messages here The local MTA then routes the messages to recipients post offices Most messages in your GroupWise system pass through the priority 4 subdirectory You can increase throughput for the priority 4 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 The priority 5 subdirectory of the MTA input queue wpcsin in the domain is for normal priority status messages routed back to senders in local post offices For example MTAs for other domains place status responses to normal 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 The priority 6 subdirectory of the MTA input queue wpcsin in the domain is for low priority user messages routed to recipients in local post offices For example
200. tes a request for items from the master mailbox This message flow diagram illustrates only the simplest case where the recipient is in the same post office as the GroupWise Remote user s master mailbox If the GroupWise Remote user sends a message to a user in any other post office the MTA would route the message to the appropriate destination When the GroupWise Remote user sends a message to another GroupWise user GroupWise Remote performs the following actions Adds the message to the GroupWise Remote message database msg db on the user s remote computer Creates a pointer in the GroupWise Remote user database user db so the message appears in the mailbox on the user s remote computer as a sent item Places attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments on the user s remote computer For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a copy of the message in the wpcsin 1 subdirectory of the remote input queue on the user s remote computer When the GroupWise Remote user sends a request for items from the master mailbox GroupWise Remote places the request in the WPCSIN 1 subdirectory of the remote input queue on the user s remote computer When the user initiates the modem connection the GroupWise client on the remote computer polls the wpcsin 1 subdirectory and compresses the outgoing mes
201. the recipient s domain The MTA in the recipient s domain also polls its input queue When it detects a new message the MTA in the recipient s domain picks up the message from its domain input queue and transfers it to the MTA in progress gwinprog queue From there the MTA transfers the message to the output queue in the recipient s post office The MTA output queue is the input queue for the POA in the recipient s post office The POA polls its input queue regularly When it detects a new message the POA in the recipient s post office performs the following actions 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 new message appears in the recipient s mailbox and updates the notification information in the user database so the recipient can be notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory corresponding to the one assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the appropriate priority 0 7 subdirectory of the MTA input queue in the recipient s post office The Notify component of the recipient s GroupWise client notifies the recipient that a new message has arrived
202. 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 The last two characters xx are a language code 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 The gwwww1l dll file provides parsing of MIME messages received from the Internet The x 10 dll programs provide XIS capability for the GroupWise agents so that you can create XML documents to monitor and change the agents as needed The gwia xml file is a specialized agent configuration file for use in the XIS environment WebAccess Agent Installation NetWare Installation Directory on page 115 Linux Installation Directory on page 117 Windows Installation Directory on page 122 NetWare Installation Directory Es sys system NetWare WebAccess Agent installation directory J gwenn5 nlm GroupWise 7 Agent Engine LJ gwinter nlm WebAccess Agent program L strtweb ncf WebAccess Agent load file _ webac70a waa WebAccess Agent startup file L gwdva dva Document Viewer Agent startup file L x 10 nim XIS NLM programs LJ gwinter xml XIS Internet Agent configuration file Agent Installation Directories 115 E cache template xx Subdirectory for HTML template files LJ webacc tpt WebAccess template files J publish tpt WebPublisher template files T help Subdirectory f
203. tory Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console See Apache Tomcat Installation on page 129 See also WebAccess Agent Queue Directory on page 88 On a Linux server the WebAccess Agent is always installed in subdirectories of opt novell groupwise agents The bin directory holds GroupWise executable files gwinter file The gwinter file is the WebAccess Agent executable You run this executable file to start the WebAccess Agent See Linux Setting Up GroupWise WebAccess in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide gwinter xml file The gwinter xml file is a specialized configuration file for use in the XIS environment webac70axx waa file The webac70axx waa file is the boilerplate file from which a domain specific webac70a waa file is created in the share directory The webac70a represents the name of the WebAccess Agent object in eDirectory The xx represents a two letter language code The lib directory holds GroupWise shared library files so files The so files are Linux shared library files that provide information to the WebAccess Agent executable image directory The image directory has subdirectories for agent icons for both color and monochrome displays The share directory holds agent startup files and files that are used by the agent consoles and Web consoles webac70a
204. tory vss02 rin a em be a a Ble A A ta ey ee ee Ee hab be 81 Internet Agent Queue Directory 0 oca ee oe EE ee Pe ee ea a 82 domain wpgate gwia directory a 83 QWia directory She a E AA ae eS a Bee hed WEES a AS te ee Be eee 87 WebAccess Agent Queue Directory a a 88 domain wpgate webac70a directory a a 89 QO0 pre directory ocio roe es be eee A Go ek a A eg o o a oe D Bs 89 WPCSIN lecitina oh a is de reel Ee AAE a ce eG Gods Be e 89 Wpcsout directory e anossa Al e dae ee eA da A a heb a eg ee A ue a 89 Qwhold directory co eee Se E bee RE hE Ro he ok Be ee ss a A 89 QWprob directory ari i ek RP a ee ee Re ee EA a a POP A es 89 fleS GIneClORy 2 3 teas O ee ee E eek an BM ER Bs BS eed 89 template directo s oeno aies a ete nw AAA ee weg ks a be ke Ge 90 COMMON CIA lt lt o a s oe KR dR Ri Eek ce ce ah cis e A ken Bleck A a A eB ok 90 COMINKCIGHIC sai n ie wer A See ee we als Bee ee 90 mimetype cfg tiles te boi at A ee ed A ia Sits en eee ee he a a a 90 Gweache db file aio a ae ela a he EEE A ea a ga Be ee haa bo 90 gwa OB TE 2 ita a ROE hg ee i eee Gee ae eee Eb Ro ewok PO Rr Re Bk S 90 OWacide fle 20200 So ea Sok Pee Pele ate Se ae oe a da ee Oe Sh ag De 90 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Caching Mailbox Directory ee 91 novel groupwise gwxxxxxx directory 2 0 a 91 rofdata directory voi Ge we A A A ro ee eee E ee 92 WPESIN dITEC O
205. ts using an SNMP monitoring program The gwwww1l dll file provides parsing of MIME messages received from the Internet The POA startup file contains startup switches for the POA Switch settings placed in the POA startup file override comparable options set for the POA in ConsoleOne The xx in the startup filename represents a two letter language code During installation a customized version of the POA startup file named post_office poa is created This customized version has the home startup switch automatically set to the post office directory the POA will service See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide 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 This customized version has the home startup switch automatically set to the domain directory the 108 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure agentnxx chm files agentnxx dll files x 10 dil files agent xml files help directory MTA will service See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide Online Help is available by clicking Help in the ag
206. ubdirectories in the agent directory However the agents cannot be run from this initial location They must be installed on the servers where they will run On a Windows server the GroupWise agents can be installed in any directory you choose The default is c grpwise The agent icons are set up to include the full path to whatever directory you choose Agent Installation Directories 107 gwenv1a dll file gwpoa exe file gwmta exe file gwsnmp dil file gwwww1 dll file strtupxx poa file strtupxx mta file The gwenvla dll file is the GroupWise Agent Engine a program that is shared by both Group Wise agents It provides the following services to the agents Database management File operations 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 The gwpoa exe file is the Post Office Agent program You run this executable file to start the Post Office Agent See Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide The gwmta exe file is the Message Transfer Agent program You run this executable file to start the Message Transfer Agent See Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide The gwsnmp dll file provides interaction with the Windows SNMP Service so that you can monitor the GroupWise agen
207. ue 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 and Post Offices in Optimizing the MTA in the GroupWise 7 Administration Guide For TCP IP links the POA passes messages to the MTA via TCP IP A copy is kept in the MTA input queue until the POA has successfully transferred the message Historical Note WP Office the predecessor of Group Wise was originally designed by WordPerfect Corporation WPCorp The Message Transfer Agent MTA was originally named the Connection Server CS Hence the directory name wpcsin for the MTA input queue Some naming conventions were originally preserved for backward compatibility 68 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 0 directory 1 directory 2 directory 3 directory 4 directory The priority 0 subdirectory of the MTA input queue wpcsin in the post office is for service requests that demand an immediate response from the MTA For example the GroupWise client places Busy Search requests here The MTA then routes the requests to the appropriate post offices so users schedules can be checked You can increase throughput for the priority 0 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 The priority 1 subdirectory of the MTA input
208. ue for the POA in the sender s post office The POA for the sender s post office updates the sender s message database msgnnn db with the Delivered status information and possibly Opened as well if the recipient has opened the message When the sender checks the sent items in his or her mailbox in the GroupWise client the message displays a status of Delivered for each recipient and possibly Opened as well if the recipient has opened the message Message Delivery to a Different Post Office 25 26 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Message Delivery to a Different Domain The MTA handles message transfer between domains TCP IP Link Open Transfer between Domains Successful on page 27 TCP IP Link Closed Transfer between Domains Delayed on page 30 Mapped UNC Link Open Transfer between Domains Successful on page 33 Mapped UNC Link Closed Transfer between Domains Delayed on page 36 Alternate Link Configuration Transfer Pull on page 38 For an explanation of link types and link protocols see Understanding Link Configuration in Domains in the GroupWise 7 Administration Guide TCP IP Link Open Transfer between Domains Successful This message flow diagram illustrates how a GroupWise message travels from one user to another when the domains are connected by a TCP IP link and the link is open a my MSHOLD DOMAINMS POSTA Lo7 POSTE
209. ueue wpcsout ads in the post office is for high priority administrative messages For example a database update request that could not be performed when the POA admin thread received it in its domain input queue would be placed here in the post office for later processing The chk subdirectory of the MTA output queue wpcsout in the post office is the working directory where the multithreaded GWCheck process keeps temporary files during database maintenance and where it tracks the activities of its various threads 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 Group Wise 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 For assistance see Message Is Dropped in the problem Directory in the Post Office in Strategies for Message Delivery Problems in the GroupWise 7 Troubleshooting 2 Solutions to Common Problems 76 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure wphost db file gwpo dc file The wphost db file in the post office is the post office database It contains all administrative information for the post office It also contains the Address Book for the post office In Group Wise 7 6 x and 5 x post offi
210. user s master mailbox is located This message flow diagram illustrates only the simplest case where the recipient is in the same post office as the GroupWise Remote user s master mailbox If the GroupWise Remote user sends a message to a user in any other post office the MTA would route the message to the appropriate destination The POA polls its input queue regularly It quickly detects the new message or request from the GroupWise Remote user When the GroupWise Remote user sends a message the POA performs the following actions Adds the message to the GroupWise Remote user s message database msgnnn db This updates the GroupWise Remote user s master mailbox 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 notified of the message Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory in the GroupWise Remote user s post office and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are also handled as attachments Creates a Delivered status message in the priority 1 subdirectory of the GroupWise Remote user s MTA input queue wpcsin When the GroupWise Remote user sends a request for items from the master mailbox GroupWise Remote performs the following actio
211. utbound TCP IP Link Open Transfer to the Internet Successful Under construction for GroupWise 7 Outbound TCP IP Link Closed Transfer to the Internet Delayed Under construction for GroupWise 7 Outbound Mapped UNC Link Open Transfer to the Internet Successful The diagram below shows the flow of outbound messages through the GroupWise directory structure to the Internet Destination o rersferers Message Delivery to and from the Internet 41 42 Stage Sender Sender s GroupWise Client MTA for Sender s Domain Internet Agent for Sender s Domain Internet Agent for Sender s Domain Internet Agent for Sender s Domain Actor HTA GWIA GWIA GWIA Action The user enters information for the message including the recipient s Internet address and sends it In this diagram the delivery mode in the local post office is Use App Thresholds and the threshold is not exceeded The GroupWise client performs the following actions for the sender Adds the message to the message database msgnnn db file assigned to the sender Creates a pointer in the sender s user database userxxx db file so the message appears in the sender s Out Box Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments Creates a copy of the message in the appropriate priority
212. viders Es templates E httpd E log E noviwww E run E tomcat4 Es bin El common isl conf E logs D server dal shared de temp Web server information directory Web server configuration file Web server configuration file Directory for language specific morphology files Directory for GroupWise WebAccess files Subdirectory for service provider files Subdirectory for template files Directory for GroupWise WebPublisher files Subdirectory for service provider files Subdirectory for template files Apache document root directory for Monitor Web server default page Directory for Novell product files Directory for GroupWise WebPublisher files Subdirectory for WebPublisher help files Subdirectory for WebPublisher image files Web server information directory Web server configuration file Directory for GroupWise Monitor files Subdirectory for service provider files Subdirectory for template files Standard Apache directory Standard Apache directory Home directory for the noviwww user created at installation Standard Apache directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory gt letc opt novell tomcat4 Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory Standard Tomcat directory 136 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure y webapps Standard Tomcat directory L admin xml Standard Tomcat file l manager xml St
213. 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 The startup file is named the same as the WebAccess Agent object in ConsoleOne The default is webac70a During installation a customized version of the WebAccess Agent startup file is created This customized version has the home startup switch automatically set to the domain directory where the WebAccess Agent s queue directories are located See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide Agent Installation Directories 119 gwdva dva file The gwdva dva file is the Document Viewer Agent startup file The Viewer Agent is currently configured completely by startup switches For more information see Document Viewer Agent Startup Switches webcon directory The webcon directory holds subdirectories and files used by the agent Web consoles such as help files webaccess directory The webaccess directory holds files used by the WebAccess Application webacc cfg file The webacc cfg file holds the same configuration information that is stored on the WebAccess Application object named GroupWiseWebAccess in eDirectory For more information see Configuring the WebAccess Application in WebAccess in the GroupWise 7 Administration Guide commgr cfg
214. whatever directory you choose The gwenvla dll file is the GroupWise Agent Engine a program that is shared by all GroupWise agents It provides the following services to the agents Database management File operations 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 The gwinter exe file is the WebAccess Agent program 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 cls gwinter exe webac70a waa Agent Installation Directories 123 webac70a waa file gwdva dva file gwwanxx dll files gwwasnmp dil file gwwww1 dll file x 10 dil files gwinter xml file You run this batch file to start the WebAccess Agent See NetWare and Windows Starting GroupWise WebAccess in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide The WebAccess Agent startup file contains startup switches for the WebAccess Agent Switch settings placed in the WebAccess Agent startup file override comparable configuration options set for the WebAccess Agent in ConsoleOne The startup file is named the same as the WebAccess Agent object in eDirectory The default is webac70a During installation the WebAccess Agent startup fi
215. when the domains are connected by a TCP IP link and the link is closed WPCSIN DOMAINMS DOMAINMS POSTA POSTA OFALES 0 7 0 7 FDO 7F POSTB POSTB PCSOUT Lo L 0 7 ADS GATEWAYX GATEWAYX Lo 0 7 Lo ae DOMAINE DOMAINA Lay L 9 7 Os 30 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Stage Sender Sender s GroupWise Client E POA for Sender s Post Office POA for Sender s Post Office MTA for Sender s Domain O MTA for Sender s Domain O MTA for Recipient s Domain O MTA for Recipient s Domain Icon MTA MTA HTA HTA Description 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 The GroupWise client communicates the message to the POA by way of TCP IP The POA receives the message from the GroupWise client and performs 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 Places attachments larger than 2 KB in the post_office offiles fd0 f6 subdirectory assigned to the sender and creates pointers from the message to its attachments For database efficiency messages and distribution lists larger than 2 KB are
216. wia file is the Internet Agent executable You run this executable file to start the Internet Agent See Starting the Internet Agent in Installing the GroupWise Internet Agent in the GroupWise 7 Installation Guide gwia xml file The gwia xml file is a specialized configuration file for use in the XIS environment The lib directory holds GroupWise shared library files 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 The image directory has subdirectories for agent icons for both color and monochrome displays The share directory holds agent startup files and files that are used by the agent consoles and Web consoles 112 GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure letc init d directory gwia cfg The Internet Agent configuration file contains startup switches for the Internet Agent Switch settings placed in the Internet Agent configuration file override comparable configuration options set for the Internet Agent in ConsoleOne The startup file is named the same as the Internet Agent object in ConsoleOne The default is gwia During installation the Internet Agent startup file is created in the share directory with the home startup switch automatically set to the domain
217. workstations See Setting Up the GroupWise Cross Platform Client on Linux in the GroupWise 7 Installation Guide Software Distribution Directory 149 novell groupwise gwclient version date i386 rpm The novell groupwise client version date 1386 rpm file is the Group Wise 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 Cross Platform Client on Linux on page 158 ofviews directory The client ofviews subdirectory contains platform specific subdirectories of view files for use by the GroupWise client On Linux the win subdirectory contains the view files for the Windows client so that users on a Linux post office can use the Windows client if desired The Cross Platform client does not use view files like the Windows client does In addition the gwviewxx ini and ofviewxx ini files configure custom views on the menus where users select views in the Windows client The gwviewxx ini file configures GroupWise 7 6 x and 5 5 views The ofviewxx ini file configures views from earlier versions of GroupWise admin directory The admin subdirectory contains subdirectories for administrative tools that can be used with Group Wise novell groupwise admin version date i386 rpm file The novell groupwise admin version date i386 rpm file is the Group Wise administrator package that is installed by the Installation script I
218. y The mshold subdirectory is a holding queue for messages addressed to domains post offices or 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 When a closed location is again open the MTA moves messages from the holding queue back into the normal message flow Historical Note In earlier versions of Group Wise the Message Transfer Agent MTA was called the Message Server MS Hence the ms in mshold Some naming conventions were originally preserved for backward compatibility domainms directory The domainms subdirectory in the holding directory mshold is used for internal processing by the MTA It does not contain any files a GroupWise administrator needs to access Historical Note In earlier versions of Group Wise the Message Transfer Agent MTA was called the Message Server MS Hence the ms in domainms Some naming conventions were originally preserved for backward compatibility postx directories 80 GroupWise 7 The postx subdirectories in the holding directory mshold represent post offices in the domain If a post office is closed the MTA routes messages for that post office into its holding queue in mshold When the post office is open the MTA moves the messages from the holding queue back into the regular message flow For more information see Message Delivery to a Different Post Office on pag
219. ystem TCP IP Link between the Domain and the Post Office on page 53 Mapped UNC Link between the Domain and the Post Office on page 541 TCP IP Link between the Domain and the Post Office 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 Group Wise system In this diagram the MTA transfers the administrative message to the POA by way of TCP IP WPCSIN L 9 7 YW PCSOUT ADS Eos OFS L9 7 wphost db GWINPROG ide POA 0 7 a ia DOMAINMS POSTA L 9 7 GATEWAY L 9 7 DOMAIN L_ 9 7 MSLOCAL Administrative Database Update 53 Stage GroupWise Administrator ConsoleOne D MTA for Domain POA for Post Office POA for Post Office Actor na Ta HTA Action The administrator uses the GroupWise Administrator snap in in ConsoleOne to add modify or delete a GroupWise object in a single domain single post office GroupWise system An object could be a GroupWise user resource distribution list post office secondary domain and so on ConsoleOne performs the following actions Updates the domain database wpdomain db to reflect the addition modification or deletion performed in ConsoleOne Creates an administrative message in the priority 2 subdirectory of the domain s MTA input queue wpcsin to replicate the update The MTA for the d

GroupWise 7 Troubleshooting 3: Message Flow

Contents

Download Pdf Manuals

Related Search

Related Contents