17.1 Using the POA Console

The web-based POA console enables you to monitor and control the POA from any location where you have access to a web browser and the Internet. The POA console provides several pages of information to help you monitor the performance of the POA.

17.1.1 Monitoring POA Status

When you first access the POA console, the Status page is displayed. Online help on the Status page helps you interpret the status information being displayed.

Click any hyperlinked status items for additional details. Click Help for more information about any field.

17.1.2 Monitoring POA Threads

The POA Status page provides links to detailed POA thread status for the following types of threads:

  • C/S handler threads

  • Message worker threads

  • GWCheck worker threads

  • SOAP threads

  • Calendar Publishing threads

The Thread ID column provides the information you need in order to track a specific thread through one or more POA log files. For more information, see Viewing and Searching POA Log Files.

17.1.3 Tracking Peak Values for Connections, Queue Contents, and Thread Usage

On the Status tab in the POA console, the statistics for client/server connections, message queues, and various types of POA threads include peak values. Peak values help you assess whether the current totals represent peaks.

To display the time of day for the peak values, click the number in the Peak column on the C/S User line.

You can set the peak value refresh interval to Daily, Weekly, Monthly, or Never.

Corresponding Startup Switches: You can also use the ‑‑peakrefreshinterval switch in the POA startup file to configure to configure the peak refresh interval.

17.1.4 Listing POA Scheduled Events

On the POA console menu, click Scheduled Events to view currently scheduled events and their status information.

QuickFinder indexing and remote downloadable Address Book generation can be controlled using links from the Configuration page, if the POA console is password protected. For more information, see Configuring the POA Console.

The Configuration page also displays information about disk check events and database maintenance events. However, scheduled events must be created and modified using the GroupWise Administration Console.

17.1.6 Taking Performance Snapshots

To help you assess the efficiency of the POA, you can configure the POA to gather statistics about CPU utilization, disk reads and writes, thread usage, message processing, and so on.

  1. Ensure that the POA console is password protected.

    For instructions, see Configuring the POA Console.

  2. In the POA console, on the Configuration page, click Performance Snapshots under the Performance Settings heading.

  3. Select Start, and then click Submit.

    The POA takes a snapshot every 60 seconds.

  4. Refresh your browser window to display data as it is collected.

  5. Specify the interval at which you want to write data to a file on disk for permanent storage.

    Performance data is saved to the mmddsnap.nnn file, where mmdd represents the current month and date and nnn starts with 001 and increments each time you enable performance snapshots to start gathering data. The performance data file is stored in the post_office\oftemp folder in comma-separated value (CSV) format, so that you can bring the data into a spreadsheet program for analysis.

  6. (Optional) Specify options to send the performance data to another user via email.

    You can specify to send the performance data Now, At the end of the day, or After running for x hours. You must specify the email addresses of the users to whom you want to send the performance data.

  7. When you have gathered sufficient performance data, select Stop, and then click Submit.

    Because gathering performance data uses POA resources, you should turn the feature off when you have gathered sufficient data. It is turned off automatically when you restart the POA.

  8. When you are finished using performance data files, delete them to conserve disk space.

    The POA does not automatically clean up old performance data files.

17.1.7 Monitoring SOAP Events

To help you work with third-party listener applications such as the GroupWise Mobility Service, the POA console lists SOAP notifications and SOAP events so that you can monitor the SOAP event traffic through the POA. These options are available if the POA console is password protected, as described in Configuring the POA Console.

Listing SOAP Notifications

The SOAP Notification List page shows the third-party listener applications that are notified by the POA when SOAP events occur.

  1. In the POA console, on the Configuration page, click SOAP Notification List.

    The columns provide the following information:

    UserID: Displays the name of the GroupWise user that is performing the event.

    Key: Displays the ID of the event configuration created by the third-party application. The event configuration describes the events that are being tracked for the user, such as creation, deletion, or modification of records.

    IP Address: Displays the IP address of the POA where the event took place.

    Port: Displays the port number used for communication between the POA and the listener application.

    Date/Time: Displays the date and time when the event took place. An asterisk (*) after the date and time indicates that the user has pending notifications. After the notifications have been sent, the asterisk is removed.

Listing SOAP Event Configurations

The Event Configuration List page displays the event configurations that are registered to receive GroupWise events from the POA. An event configuration is listed when an external application such as the GroupWise Mobility Service communicates with the POA and provides information about a specific type of event that it wants to receive.

For example, the GroupWise Mobility Service synchronizes GroupWise data to mobile devices. Whenever a user connects a mobile device to GroupWise through the GroupWise Mobility Service, an event configuration is created for that user and his or her mobile device. If the user has multiple mobile devices, there is an event configuration for each of the user's mobile devices.

  1. In the POA console, on the Configuration page, click Event Configuration List.

    The columns provide the following information:

    UserID: Displays the name of the GroupWise user associated with the event configuration.

    Key: Displays the ID of the event configuration created by the external application. For example, the GroupWise Connector uses a GroupWise trusted application key.

    IP Address: Displays the IP address of the external application that the POA notifies when events take place.

    Port: Displays the port number used for communication between the POA and the external application.

    Events: Displays the number of events that have transferred from the POA to the external application.

  2. To manage the event configuration for a specific user, click the user name.

    The Event Configuration page helps you manage an event configuration and the associated events that are stored in a user's database for an external application such as the GroupWise Mobility Service.

  3. Select Add to Notification List, and then click Submit to cause the POA to notify the external application whenever a new GroupWise event needs to be picked up.

  4. Select Show Events, and then click Submit to display the currently stored events for the event configuration.

    If the list is long, the external application might not be running.

  5. Select Delete Events, and then click Submit to delete any stored events for the event configuration.

    Use this option only when a backlog of events needs to be cleared, such as when a problem occurred with the external application.

  6. Click Delete Event Configuration, and then click Submit to delete the displayed event configuration.

    Use this option when the POA no longer needs to send events for the user associated with the event configuration. For example, if there was a problem removing a user from the GroupWise Connector, use this option to remove any residual events associated with the user.