The following topics help you monitor and control the POA from the POA agent console:
The POA agent console provides information, status, and message statistics about the POA to help you assess its current functioning.
Windows Note: You can suppress the Windows POA agent console by running the POA as a service. See Starting the Windows POA.
The POA agent console consists of several components:
Do not exit the POA agent console unless you want to stop the POA.
NetWare Note: At a NetWare® server console, you can use Alt+Esc to change screens. In a remote console window, you can use Alt+F1 to select a screen to view. You can use these keystrokes to display the POA agent console if it is not immediately visible on the NetWare console.
Windows Note: On a Windows machine, you can minimize the POA agent console, but do not close it unless you want to stop the POA.
The POA Information box identifies the POA whose POA agent console you are viewing, which is especially helpful when multiple POAs are running on the same machine.
PostOffice.Domain: Displays the name of the post office serviced by this POA, and what domain it is linked to.
Description: Displays the description provided in the Description field in the POA Identification page in ConsoleOne®. When you run multiple POAs on the same machine, the description should uniquely identify each one. If multiple administrators work at the machine where the POA runs, the description could include a note about who to contact before stopping the POA.
Up Time: Displays the length of time the POA has been running.
You can also view this information on the Status page at the POA Web console.
The POA Status box displays the current status of the POA and its backlog. The information displayed varies depending on whether the POA is processing client/server connections, message files, both, or neither.
Processing: Displays a rotating bar when the POA is running. If the bar is not rotating, the POA has stopped. For assistance, see Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
Busy: Displays the number of POA threads currently in use (busy) for client/server connections, message files, or both, depending on POA configuration. You can change the total number of threads available. See Adjusting the Number of POA Threads and Connections for Client/Server Processing and Adjusting the Number of POA Threads for Message File Processing.
User Connections (for client/server processing): Displays the number of active application ("virtual") TCP/IP connections between the POA and the GroupWise® clients run by GroupWise users. You can change the maximum number of user connections. See Adjusting the Number of POA Threads and Connections for Client/Server Processing.
Physical Connections (for client/server processing): Displays the number of active physical TCP/IP connections between the post office and the GroupWise clients run by GroupWise users. You can change the maximum number of physical connections. See Adjusting the Number of POA Threads and Connections for Client/Server Processing.
Priority Queues (for message file processing): Displays the number of messages waiting in the high priority message queues. You can control the number of threads processing message files. See Adjusting the Number of POA Threads for Message File Processing.
Normal Queues (for message file processing): Displays the number of messages waiting in the normal priority message queues. You can control the number of threads processing message files. See Adjusting the Number of POA Threads for Message File Processing.
File Queues (for message file processing): Displays the total number of messages waiting in all message queues, when client/server information and message file information is displayed together.
For information about the various message queues in the post office, see Post Office Directory in Troubleshooting 3: Message Flow and Directory Structure.
The number of messages displayed as waiting in message queues is not an exact count. For example, if the POA detects numerous messages to process in the priority 4 queue (normal messages), it does not scan and count messages in lower priority queues. Therefore, actual counts of message files waiting in queues might be higher than the counts displayed in the Status box.
You can also determine POA status on the Status page at the POA Web console.
The POA Statistics box displays statistics showing the current workload of the POA. The information displayed varies depending on whether the POA is processing client/server connections, message files, both, or neither.
C/S Requests (for client/server processing): Displays the number of active client/server requests between GroupWise clients and the POA.
Requests Pending (for client/server processing): Displays the number of client/server requests from GroupWise clients the POA has not yet been able to respond to. If the number is large, see POA Statistics Box Shows Requests Pending in Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
Users Timed Out (for client/server processing): Displays the number of GroupWise clients no longer communicating with the POA. If the number is large, see POA Statistics Box Shows Users Timed Out in Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
Total Messages (for message file processing): Displays the total number of messages processed by the POA. This includes user messages, status messages, and service requests processed by the POA.
Undeliverable (for message file processing): Displays the number of messages that could not be delivered because the user was not found in that post office or because of other similar problems. Senders of undeliverable messages are notified. For assistance, see Message Has Undeliverable Status in Strategies for Message Delivery Problems in Troubleshooting 2: Solutions to Common Problems.
Problem Messages (for message file processing): Displays the number of invalid message files that have problems not related to user error. It also displays requests the POA cannot process because of error conditions. For assistance, see Message Is Dropped in the Problem Directory in Strategies for Message Delivery Problems in Troubleshooting 2: Solutions to Common Problems.
Users Delivered: Displays the number of user messages delivered to recipients in the post office. A message with six recipients in the local post office is counted six times.
Statuses: Displays the number of status messages delivered to recipients in the post office.
Rules Executed: Displays the number of users' rules executed by the POA.
You can also gather POA statistics on the Status page at the POA Web console.
The POA Log Message box displays the same information that is being written to the POA log file. The amount of information displayed in the POA Log Message box depends on the current log settings for the POA. See Using POA Log Files.
You can also view the POA log file on the Log Files page at the POA Web console.
When you first start the POA, you typically see informational messages that list current agent settings, current number of threads, TCP/IP options (client/server), and scheduled events. As the POA runs, it continues to provide status and delivery information in the POA Log Message box.
If the POA encounters a problem processing a message, it displays an error message in the POA Log Message box. See Post Office Agent Error Messages in Troubleshooting 1: Error Messages.
The POA admin thread updates the post office database (WPHOST.DB) when users and/or user information are added, modified, or removed, and repairs it when damage is detected.
To display the POA Admin Thread Status box from the POA agent console, click Configuration, then click Admin Status.
The following tasks pertain specifically to the POA admin thread:
You can also display POA admin thread status at the POA Web console. In the General Settings section on the Configuration page, click Admin Task Processing.
You can perform the following tasks to monitor and control the POA from the POA agent console at the machine where the POA is running:
You might need to stop and restart the POA for the following reasons:
To stop the POA:
At the machine where the POA is running, display the POA agent console.
Click File > Exit, then click Yes to stop the POA.
NetWare Note: Use Exit (F7). If the POA does not respond to Exit, you can use the UNLOAD command to stop the POA. However, this would stop all instances of the POA running on the server.
Windows Note: If the Windows POA does not respond to Exit, you can close the POA agent console to stop the POA or use the Task Manager to terminate the POA task.
Restart the POA. See Starting the POA.
You can cause the POA to stop accessing the post office database (wphost.db) without stopping the POA completely. For example, you could suspend the POA admin thread while backing up the post office database.
To suspend the POA admin thread:
At the POA agent console, click Configuration, then click Admin Status.
Click Suspend.
NetWare Note: Use Options (F10) > Admin Status > Suspend.
The POA admin thread will no longer access the post office database until you resume processing.
To resume the POA admin thread:
At the POA agent console, click Configuration, then click Admin Status.
Click Resume.
NetWare Note: Use Options (F10) > Admin Status > Resume.
You can also suspend and resume the POA admin thread at the POA Web console. On the Configuration page, click Admin Task Processing, click Suspend or Resume, then click Submit.
It is important to keep the POA software up to date. You can display the date of the POA software from the POA agent console.
To display the POA date:
NetWare Note: To check the date of the POA NLM, you must list the gwpoa.nlm file in the agent installation directory (typically, in the sys:\system directory) or use the modules gwpoa.nlm command at the server console prompt.
You can also check the POA software date on the Environment page at the POA Web console.
You can list the current configuration settings of the POA at the POA agent console.
To display the current POA settings:
At the machine where the POA is running, display the POA agent console.
Click Configuration, then click Agent Settings.
The configuration information displays in the log message box and is written to the log file.
NetWare Note: Use Show Configuration (F4) > Show Configuration.
If information you need scrolls out of the log message box, you can scroll back to it. See Browsing the Current POA Log File.
For information about POA configuration settings, see Configuring the POA and Using POA Startup Switches.
You can check the current POA settings on the Configuration page at the POA Web console.
The POA agent console displays essential information about the functioning of the POA. More detailed information is also available.
To display detailed POA statistics:
At the machine where the POA is running, display the POA agent console.
Click Statistics, then click Misc. Statistics.
NetWare Note: This feature is not available in the NetWare® POA.
Review the Detailed Statistics dialog box. The following statistics are displayed and written to the log file for the current POA up time:
You can also get statistics on the Status page at the POA Web console.
When the POA and the GroupWise clients communicate in client/server mode, you can display statistics to indicate the performance level of the TCP/IP communication.
To display detailed client/server information:
At the machine where the POA is running, display the POA agent console.
Click Statistics, then click Client/Server.
NetWare Note: Use Configuration (F4) > Display Client/Server Information.
Click the type of statistics to display.
The selected type of statistics for the current POA up time are listed in the message log box and are written to the POA log file.
If information you need scrolls out of the log message box, you can scroll back to it. See Browsing the Current POA Log File.
All Statistics: Lists at one time the information for General Statistics, Throughput, Physical Connections, and Application Connections, as described below.
General Statistics: Lists the DNS address and IP address of the machine, along with the TCP port for the POA, the number of messages received, sent, and aborted, and the number of physical and application connections active and allowed.
Show Throughput: Lists the total number of messages processed by the POA for all users. Statistics are provided for the current elapsed time and as a per second average.
Clear Throughput: Resets the current elapsed time to zero.
Physical Connections: Lists the currently active physical connections. Physical connections are active TCP connections created whenever GroupWise users do something that requires communication and closed when the specific activities have been completed. By listing the physical connections, you can see what users are actively using GroupWise and how much throughput each user is generating. Users' IP addresses are also listed.
Application Connections: Lists the currently active application connections. Every user that starts GroupWise has an application connection for as long as GroupWise is running, even if GroupWise is not actively in use at the moment. By listing the application connections, you can see what users have started GroupWise and how much throughput each user is generating. Users' IP addresses are also listed.
Show Redirection List: Lists all POAs in your GroupWise system and indicates whether each is configured for TCP/IP. This redirection information is obtained from the post office database (WPHOST.DB).
Check Redirection List: Attempts to contact each POA in your GroupWise system and reports the results. If a POA is listed as "Connection Failed," see Post Office Agent Problems in Troubleshooting 2: Solutions to Common Problems.
You can also get some client/server information on the Status page at the POA Web console.
The POA uses eight queues to process message files. You can view the activity in each of these queues. For more information about message queues, see Post Office Directory in Troubleshooting 3: Message Flow and Directory Structure.
To list current activity in the message queues:
At the machine where the POA is running, display the POA agent console.
Click Actions, then click View MF Queues.
NetWare Note: Use Options (F10) > Actions > View MF Queues.
View the queue activity in the message log box. Use the scroll bar if necessary to scroll through the information.
If information you need scrolls out of the log message box, you can scroll back to it. See Browsing the Current POA Log File.
The information is also written to the POA log file.
You can also check queue activity at the POA Web console. In the Thread Status section on the Configuration page, click the type of thread to view queue activity for.
When the POA links to the MTA by way of TCP/IP, you can view the status of the TCP/IP link from the POA agent console.
To view status information about the TCP/IP link between the POA and the MTA:
At the machine where the POA is running, display the POA agent console.
Click Configuration, then click Message Transfer Status.
NetWare Note: Use Options (F10) > Message Transfer Status.
View the following information about the TCP/IP link:
Outbound TCP/IP Address: Displays the TCP/IP address and port where the MTA listens for messages from the POA.
Inbound TCP/IP Address: Displays the TCP/IP address and port where the POA listens for messages from the MTA.
Hold Directory: Displays the path to the directory where the POA stores messages if the TCP/IP link to the MTA is closed.
Current Status: Lists the current status of the TCP/IP link.
Open: The POA and the MTA are successfully communicating by way of TCP/IP.
Closed: The POA is unable to contact the MTA by way of TCP/IP
Unavailable: The POA is not yet configured for TCP/IP communication with the MTA.
Messages Written: Displays the number of messages the POA has sent.
Message Read: Displays the number of messages the POA has received.
Last Closure Reason: Provides an explanation for why the post office was last closed. For assistance resolving closure reasons, see Post Office Agent Error Messages in Troubleshooting 1: Error Messages.
You can also display message transfer status at the POA Web console. In the Thread Status section on the Status page, click Message Transfer Status.
When the POA links to the MTA by way of TCP/IP, you can restart the Message Transfer Protocol (MTP) thread that provides the link between the POA and the MTA.
To restart the MTP thread:
At the machine where the POA is running, display the POA agent console.
Click Actions, then click Restart MTP.
NetWare Note: Use Options (F10) > Actions > Restart MTP.
You can also restart the MTA thread at the POA Web console. On the Configuration page, click Message Transfer Protocol, click Restart MTP, then click Submit. In addition, you can control the send and receive threads separately. On the Status page, click Message Transfer Status; in the Send or Receive column, click the current status, then click Stop/Start MTP Send/Receive.
Status information for the POA admin thread is displayed in a separate dialog box, rather than on the main POA agent console.
To display POA admin thread status information:
At the machine where the POA is running, display the POA agent console.
Click Configuration, then click Admin Status.
NetWare Note: Use Options (F10) > Admin Status.
The following admin status information is displayed:
Admin Message Box
The Admin Message box provides the following information about the workload of the POA admin thread:
Completed: Number of administrative message successfully processed.
Errors: Number of administrative messages not processed because of errors.
In Queue: Number of administrative messages waiting in the queue to be processed.
Send Admin Mail: Select to send a message to the administrator whenever a critical error occurs. See Notifying the GroupWise Administrator about POA Problems.
Admin Database Box
The Admin Database box provides the following information about the post office database (WPHOST.DB):
Status: Displays one of the following statuses:
Normal: The POA admin thread is able to access the post office database normally.
Recovering: The POA admin thread is recovering the post office database.
DB Error: The POA admin thread has detected a critical database error. The post office database cannot be recovered. Rebuild the post office database in ConsoleOne. See Rebuilding Domain or Post Office Databases.
The POA admin thread will not process any more administrative messages until the database status has returned to Normal.
Unknown: The POA admin thread cannot determine the status of the post office database. Exit the POA, then restart it, checking for errors on startup.
DB Sort Language: Displays the language code for the language that determines the sort order of lists displayed in ConsoleOne and the GroupWise system Address Book.
Recovery Count: Displays the number of recoveries performed on the post office database by this POA for the current POA session.
Admin Thread Box
The Admin Thread box displays the following information:
You can also display POA admin thread status at the POA Web console. In the General Settings section on the Configuration page, click Admin Task Processing.
The POA admin thread can recover the post office database (wphost.db) when it detects a problem.
To enable/disable automatic post office database recovery:
At the machine where the POA is running, display the POA agent console.
Click Configuration > Admin Status > Automatic Recovery to toggle this feature on or off for the current POA session.
NetWare Note: Use Options (F10) > Admin Status > Automatic Recovery.
To change the setting permanently, see Configuring the POA in ConsoleOne.
To recover the post office database immediately:
At the machine where the POA is running, display the POA agent console.
Click Configuration > Admin Status > Perform DB Recovery.
NetWare Note: Use Options (F10) > Admin Status > Perform DB Recovery.
For additional database repair procedures, see Maintaining Domain and Post Office Databases.
You can also recover the post office database at the POA Web console. In the General Settings section on the Configuration page, click Admin Task Processing, select Automatic Recovery or Perform DB Recovery as needed, then click Submit.
The POA can recover user databases (userxxx.db) and message databases (msgnn.db) automatically when it detects a problem because databases can be open during the recover process. This procedure is a "recover" rather than a "rebuild," because a "rebuild" requires that all users and agents be out of the database being rebuilt. See Maintaining User/Resource and Message Databases.
To enable/disable automatic message and user database recovery:
At the machine where the POA is running, display the POA agent console.
Click Actions > Auto Rebuild to toggle this feature on or off for the current POA session.
NetWare Note: Use Options (F4) > Actions > Enable Auto Rebuild.
To change the setting permanently, see Configuring the POA in ConsoleOne.
GroupWise uses QuickFinder® technology to index messages and documents stored in post offices. You can start indexing from the POA agent console. For example, if you just imported a large number of documents, you could start indexing immediately, rather than waiting for the next scheduled indexing cycle.
To update QuickFinder indexes for the post office:
At the machine where the POA is running, display the POA agent console.
Click Actions > QuickFinder > Update Indexes.
NetWare Note: Use Options (F10) > Actions > Update QuickFinder Indexes.
You can set up indexing to occur at regular intervals. See Regulating Indexing.
If the indexing load on the POA is heavy, you can set up a separate POA just for indexing. See Configuring a Dedicated Indexing POA.
You can also update QuickFinder indexes at the POA Web console. On the Configuration page, click QuickFinder Indexing, select the needed action option, then click Submit.
QuickFinder indexes are automatically compressed at midnight each night to conserve disk space. You can start compression at any other time from the POA agent console. For example, if you just imported and indexed a large number of documents and are running low on disk space, you could compress the indexes immediately, rather than waiting for it to happen at midnight.
To compress QuickFinder indexes for the post office:
At the machine where the POA is running, display the POA agent console.
Click Actions > QuickFinder > Compress Indexes.
NetWare Note: Use Options (F10) > Actions > Compress QuickFinder Indexes.
You can also compress QuickFinder indexes at the POA Web console. On the Configuration page, click QuickFinder Indexing, select the needed action option, then click Submit.
In the log message box, the POA displays the same information being written to the POA log file. The amount of information depends on the current log settings for the POA.
The information automatically scrolls up the screen as additional information is written. You can stop the automatic scrolling so you can manually scroll back through earlier information.
To browse the current POA log file and control scrolling:
At the machine where the POA is running, display the POA agent console.
Click Log, then click Auto Scroll to toggle automatic scrolling on or off.
NetWare Note: Use View Log File (F9).
For explanations of messages in the POA log file, see Post Office Agent Error Messages in Troubleshooting 1: Error Messages.
See also Using POA Log Files.
Reviewing log files is an important way to monitor the functioning of the POA.
To select a POA log file to view:
At the machine where the POA is running, display the POA agent console.
Click Log, then click View Log.
NetWare Note: Use Options (F10) > View Log Files.
The following information is provided:
Log Files: Lists the current POA log files, ordered from the oldest log file at the top to the newest log file at the bottom. The current log file is marked with an asterisk (*).
Date/Time: Displays the date and time of each POA log file.
Space Used: Displays the amount of disk space currently occupied by that POA's log files. You can control the amount of space consumed by POA log files during the current POA session. You can also control the default amount of disk space for POA log files in the POA Log Settings page in ConsoleOne or in the POA startup file. See Configuring POA Log Settings and Switches.
Log File Directory: Displays the full path of the directory where the POA writes its log files. See Configuring POA Log Settings and Switches.
In the log file list, select the POA log file you want to view.
Windows Note: For the Windows POA, you can select the viewer to use by providing the full path to the viewer program. The default viewer is Notepad.
Click View.
For explanations of messages in the POA log file, see Post Office Agent Error Messages in Troubleshooting 1: Error Messages.
See also Using POA Log Files.
You can also view a selected POA log file at the POA Web console. On the Log Files page, select a log file, then click View Events.
You can have the POA start a new log file as needed.
To cycle the POA log file:
At the machine where the POA is running, display the POA agent console.
Click Log, then click Cycle Log.
NetWare Note: Use Options (F10) > Cycle Log.
Default log settings are established when you start the POA. However, you can adjust the POA log settings for the current session from the POA agent console. This overrides any settings provided in ConsoleOne or in the POA startup file. The modified settings remain in effect until you restart the POA, at which time the log settings specified in ConsoleOne or the startup file take effect again.
To adjust the POA log settings for the current session:
At the machine where the POA is running, display the POA agent console.
Click Log, then click Log Settings.
NetWare Note: Use Options (F10) > Logging Options.
Adjust the values as needed for the current POA session.
See Using POA Log Files.
You can also adjust POA log settings at the POA Web console. On the Configuration page, click Log Settings, set the log settings as needed, then click Submit.
You can change the configuration of the POA by editing the POA startup file from the POA agent console.
To edit the POA startup file:
At the machine where the POA is running, display the POA agent console.
Click Configuration, then click Edit Startup File.
NetWare Note: Use Options (F10) > Actions > Edit Startup File.
Make the necessary changes, then save and exit the startup file.
Stop and restart the POA.
Online Help varies by platform.
NetWare Note: Press F1 for information in any dialog box or menu.
Windows Note: Click the Help button for information in any dialog box. Click Help > Help on the menu bar for information about the POA agent console.