To test the performance of the agents in your GroupWise system, you can send performance test messages from a specially configured Monitor domain to target domains anywhere in your GroupWise system. The Monitor Agent measures the amount of time it takes for replies to return from the target domains, which lets you ascertain the speed at which messages flow through your GroupWise system.
Before you can use the GroupWise Performance Testing feature to configure and enable GroupWise performance testing, you must create a specially configured Monitor domain and select an MTA to receive performance test messages from the Monitor Agent. It does not matter which MTA you decide to use. It could be the MTA for the domain to which the external Monitor domain is linked.
The Monitor Agent uses an external GroupWise domain as part of measuring GroupWise agent performance. By creating an external domain, you enable the Monitor Agent to approximate the round-trip time for email messages to travel to recipients and for status messages to travel back to senders. If you also plan to set up gateway accounting reports, you can use this same external domain for collecting accounting data. For more information, see Section 85.5, Collecting Gateway Accounting Data.
In the GroupWise Admin console, connect to a domain where the MTA will communicate with the Monitor Agent for the purpose of measuring agent performance.
Create an external GroupWise domain.
For background information about external GroupWise domains, see Section 11.2, Using an External Domain to Connect GroupWise Systems.
Name the external domain to reflect its role in your GroupWise system.
For example, you could name it ExternalMonitorDomain.
Continue with Configuring the Link for the External Monitor Domain.
The Monitor Agent needs to send its performance testing messages to a specific MTA in your GroupWise system. It does not matter which MTA you decide to use. It could be the MTA for the domain to which the external Monitor domain is linked.
Continue with Configuring the Monitor Agent for Agent Performance Testing.
After you have created an external Monitor domain and configured a link from it to an MTA, you are ready to configure the Monitor Agent for performance testing.
In the Monitor Agent console, click , then scroll down to the section.
Fill in the fields:
Domain to Send Messages To: Select the external Monitor domain that you configured for system performance testing.
You might need to restart the Monitor Agent in order to see the new Monitor domain in the drop-down list.
Minutes between Messages: Specify in minutes the time interval for the Monitor Agent to send performance test messages.
Enable GroupWise Performance Testing: Select this option to turn on performance testing. Deselect this option when you have finished your performance testing.
Send Performance Messages To: Selectto send performance test messages to all domains in your GroupWise system. Select to send performance test messages only to the agents currently listed at the Monitor Agent console.
Clickto put the performance testing settings into effect.
Continue with Section 85.4.4, Viewing Agent Performance Data.
A performance testing report enables you to measure how long it takes messages to travel through your GroupWise system. The performance testing report lists each domain that a performance test message was sent to, when it was sent by the Monitor Agent, and the number of seconds between when it was sent and when the Monitor Agent received a response from the tested agent.
In the Monitor Agent console:
Selectto generate a performance testing report for all domains in your GroupWise system.
Select one domain to generate a performance testing report for it.
Clickto generate the performance testing report.
Continue with Receiving Notification of Agent Performance Problems.
If you want the Monitor Agent to notify you if system performance drops to an unacceptable level, you can create a threshold to check the mtaLastResponseTime and mtaAvgResponseTime MIB variables. The average response time is a daily average that is reset at midnight. See Section 83.5.2, Customizing Notification Thresholds for setup instructions.