Post Office Directory
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Post office directory
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 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 "Optimizing the MTA" in the GroupWise 6.5 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 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.
0 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 6.5 Administration Guide.
1 directory
The priority 1 subdirectory of the MTA input 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 GroupWise 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 6.5 Administration Guide.
2 directory
The priority 2 subdirectory of the MTA input queue (wpcsin) in the post office is for high priority user messages routed to recipients in other post offices, domains, or systems.
For example, the GroupWise 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 6.5 Administration Guide.
3 directory
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' 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 6.5 Administration Guide.
4 directory
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.
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 6.5 Administration Guide.
5 directory
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.
6 directory
The priority 6 subdirectory of the MTA input 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.
7 directory
The priority 7 subdirectory of the MTA input queue (wpcsin) in the post office is for low priority status messages routed back to senders in other post offices, domains, or systems.
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
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.
dmsh.db file
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 lib0001-ff 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 (lib0001-ff) in the post office are databases for library and document information.
The nn in the filenames represents the partition number, which is generated by a hashing algorithm to guarantee uniqueness.
The 01-ff in 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.
dmddnn01-ff.db file
The dmddnn01-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 (lib0001-ff) in the post office contain the QuickFinder index for the documents contained in the library.
archive directory
The archive subdirectories in the library subdirectories (lib0001-ff) in the post office contain an array of subdirectories for holding archived documents. 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.
docs directory
The docs subdirectories in the library subdirectories (lib0001-ff) 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
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.
msgnn.db file
The msgnn.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 in an array of subdirectories 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 GroupWise.
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 6.5 Administration Guide.
ngwdfr.db file
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.
guardbak directory
The guardbak subdirectory in the ofmsg subdirectory in the post office holds a backup copy of the ngwguard.fbk file.
ofuser directory
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 Corporation (WPCorp), was named WP Office. Hence, the of in ofuser. Some naming conventions were originally preserved for backward compatibility.
userxxx.db file
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 GroupWise 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).
puxxxxx.db file
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.
index directory
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
The offiles subdirectory in the post office contains subdirectories for messages, attachments, and recipient lists that are equal to or greater than 2 KB in size. These larger messages, attachments, and recipient lists are stored outside the actual message databases in the 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.
fd0-f6 directories
The fd0-f6 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 (msgnn.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 GroupWise client platforms. Within the platform-specific subdirectories (for example, win) are view (*.vew) files that create the various views displayed in the GroupWise 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 6 and GroupWise 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 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.
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
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 backward compatibility.
ofs directory
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.
2 directory
The priority 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 priority 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 6.5 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.
wprof50.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 6.5 Administration Guide guide.
ads directory
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 1 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 queue (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.
chk directory
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.
problem directory
The problem subdirectory of the mta output queue (wpcsout) in the post office is a holding area for damaged message files. Problem files are marked with an extension indicating which GroupWise agent placed each file in the problem directory.
You should check this directory periodically for problem files, resolve the problem, then place the files back into the appropriate queue for continued processing. For assistance, see "Message Is Dropped in the problem Directory in the Post Office" in "Strategies for Message Delivery Problems" in the GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems.
wphost.db 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 GroupWise 6.x and 5.x post offices, 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 6.x/5.x or 4.x post offices.
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.db. Some naming conventions were originally preserved for backward compatibility.
gwpo.dc file
The gwpo.dc file in the post office is the data dictionary for creating and rebuilding GroupWise 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 GroupWise 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 6.5 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:
- ngwguard.db (guardian database)
- dmxxnn01-ff.db (document management databases)
- msgnn.db (message databases)
- userxxx.db (user databases)
- 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 6.5 Administration Guide.
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 6.5 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.