Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Essentials edition. Server & Application Monitor (SAM) is also available in a standalone module.

Novell GroupWise Post Office Agent (Unix)

You can this SAM application monitor template to check GroupWise Post Office Agent (POA) statistics by retrieving it from POA's webpage.

Prerequisites

Perl must be installed on the target server. SNMP installed on the target server and permission to monitor the gwpoa processes.

Credentials

Root on target server.

Component monitors

Post Office Agent: Statistic 1

This monitor returns different POA statistics. The returned values are as follows:

  • Users – This component returns the number of users, who are connected to the post office using client/server connections. These could be Windows clients or Cross-Platform clients.
  • Application Connections – This component returns the number of active application ("virtual") TCP/IP connections between the POA and GroupWise clients (Windows or Cross-Platform). Each GroupWise user uses one application connection when he or she starts GroupWise. Depending on what activities the user is doing in the GroupWise client, additional application connections are used. For example, the GroupWise Address Book and GroupWise Notify will use individual application connections.
  • Physical Connections – This component returns the number of active physical TCP/IP connections between the post office and the GroupWise clients run by GroupWise users.
  • Priority Queues – This component returns the number of messages waiting in the high priority message queues. You can control the number of threads processing message files.
  • Normal Queues – This component returns the number of messages waiting in the normal priority message queues. You can control the number of threads processing message files.
  • Requests – This component returns the number of active client/server requests between GroupWise clients and the POA.
  • Requests Pending – This component returns the number of client/server requests from GroupWise clients the POA has not yet been able to respond to. If the number is large, increase the number of POA connections so that more users can be serviced by the POA.
  • Users Timed Out – This component returns the number of GroupWise clients no longer communicating with the POA. Having users timed out does not indicate a problem with the POA, but rather a problem with users. Users who have timed out are users for which the POA has closed the connection because the GroupWise client was no longer communicating. Timed out users might not be exiting GroupWise normally or might be having other problems with their workstations. The number of timed-out users might tend to increase on a daily basis during the hour after users leave to go home. This is not a problem.
  • Rules Executed – This component returns the number of users' rules executed by the POA.

You should set correct arguments in the following order:

perl ${SCRIPT} IP_address port

where

IP_address – IP address of target server with installed POA. By default it uses value ${IP} which will automatically set the IP address of target node

port – POA HTTP access port. By default it is set to 7181

If the monitor returns a value of -1, this can mean that the statistic cannot be found on POA's web page.

Post Office Agent: Statistic 2

This monitor returns different POA statistic. The returned values are as follows:

  • Users Delivered – This component returns 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.
  • Message Files Processed – This component returns the total number of messages processed by the POA. This includes user messages, status messages, and service requests processed by the POA.
  • Messages Undelivered – This component returns 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. This value should be as low as possible. See Novell documentation for reference.
  • b – This component returns 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. This value should be as low as possible.See Novell documentation for reference.
  • Users Deleted – This component returns the number of GroupWise user accounts that the POA has deleted.
  • Statuses Processed – This component returns the number of status notifications that the POA has delivered.
  • Databases Recovered – This component returns the number of databases that the POA has recovered. When database damage is detected, the POA can repair the post office database, user databases, and message databases.
  • GWCheck Messages Processed – This component returns the number of GWCheck (mailbox/library maintenance) requests that the POA has received from scheduled mailbox/library maintenance events and from a GroupWise administrator in ConsoleOne.
  • GWCheck Problem Messages – This component returns the number of GWCheck (mailbox/library maintenance) requests that the POA was unable to process successfully. Look in the POA log file on the Log Files page for more information about the problem. This value should be as low as possible.

Set correct arguments in the following order:

perl ${SCRIPT} IP_address port

where

IP_address – IP address of target server with installed POA. By default it uses value ${IP} which will automatically set the IP address of target node

If the monitor returns a value of -1, the statistic was not found on POA's web page.

Post Office Agent: Statistic 3

This monitor returns different POA statistic. The returned values are as follows:

  • Caching Requests – This component returns the number of times GroupWise clients running in Caching mode have requested to download messages into Caching mailboxes. These could be Windows clients or Cross-Platform clients.
  • Caching Primings – This component returns the number of times GroupWise clients have needed to download entire mailboxes when Caching mode is first selected by client users.
  • Rejected Caching Requests – This component returns the number of caching requests that the POA was too busy to respond to successfully. Rejected caching requests are retried until they are successful. The number of rejected caching requests helps you fine tune the number of C/S handler threads the POA should be configured to use. This value should be as low as possible.
  • Rejected Caching Primings – This component returns the number of priming requests that the POA was too busy to respond to successfully. Rejected caching primings mean that some GroupWise users have been unable to change over to Caching mode immediately. The GroupWise client will retry the priming at a later time. This value should be as low as possible.
  • Total Handler Threads – This component returns the maximum number of client/server handler threads the POA can start. C/S handler threads service client/server requests from GroupWise users.
  • Busy Handler Threads – This component returns the number of how many handler threads are currently busy. C/S handler threads service client/server requests from GroupWise users. To handle occasional heavy client activity when there are pending client/server requests but CPU utilization is still below the configured threshold, the POA automatically starts additional C/S handler threads above the number configured in ConsoleOne to handle the workload. When the workload returns to normal, the C/S handler threads return to the number configured in ConsoleOne.
  • Total Message Worker Threads – This component returns the maximum number of message worker threads the POA can start. Message worker threads process message files, delivering messages to users' mailboxes.
  • Busy Message Worker Threads – This component returns the number of how many message worker threads are currently busy. Message worker threads process message files, delivering messages to users' mailboxes.
  • Total GWCheck Worker Threads – This component returns the maximum number of GWCheck worker threads the POA can start. GWCheck worker threads perform mailbox/library maintenance.
  • Busy GWCheck Worker Threads – This component returns the number of how many GWCheck worker threads are currently busy. GWCheck worker threads perform mailbox/library maintenance.

You should set correct arguments in the following order:

perl ${SCRIPT} IP_address port

where

IP_address – IP address of target server with installed POA. By default it uses value ${IP} which will automatically set the IP address of target node;

port – POA HTTP access port. By default it is set to 7181.

If the monitor returns a value of -1, this can mean that the statistic cannot be found on POA's web page.

Client and Server port

This component monitor tests the ability of a POA to accept incoming sessions. By default it monitors 1677 TCP port. You should put correct POA Client/Server port here, which you set during POA installation.

Message Transfer port

This component monitor tests the ability of a POA Message Transfer to accept incoming sessions. By default it monitors 7101 TCP port. You should put correct POA Message Transfer port here, which you set during POA installation.

HTTP port

This component monitor tests the ability of a POA HTTP access to accept incoming sessions. By default it monitors 7181 TCP port. You should put correct POA HTTP port here, which you set during POA installation.

Process: Post Office Agent

This monitor returns CPU and memory usage of Post Office Agent process (gwpoa). If this counter is unavailable, there may be problems with SNMP configuration or this process has stopped.

HTTP Monitor

This component monitor tests a web server's ability to accept incoming sessions and transmit the requested page. By default it monitors web site on 7181 TCP port.