Groupwise Web Agent Test

This test reports performance metrics that indicate the overall health of the GroupWise Web Access Agent (GwWeb).

Target of the test : A GwWeb application

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the name specified.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which this test is to be configured.


The port at which the server listens.


The port at which the monitored target exposes its SNMP MIB; The default value is 161.


By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.


The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear.


This parameter appears only when v3 is selected as the SNMPVersion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. 


This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box.  By default, this parameter is set to none.


Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3.

Confirm Password

Confirm the AuthPass by retyping it here.


This parameter too appears only if v3 is selected as the SNMPversion. From the Authtype list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

  • MD5 – Message Digest Algorithm
  • SHA – Secure Hash Algorithm


This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. 


If this EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:

  • DES – Data Encryption Standard
  • AES – Advanced Encryption Standard


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds.

Data Over TCP

By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No.


The distinguished name of the WebAccess agent. Refer to Determining Distinguished Name of Web Agent to know how to find it.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Request rate

Indicates the rate at which requests were serviced by the GwWeb.


A high value over a long period of time may be indicative of an excessive load on the agent.

Request failures

Indicates the number of failed requests per second


This value must be low. A high value over a period of time indicates a problem in performance.

Available threads

Indicates the number of available threads.


If this value remains as 0 for a considerable period of time, increase the total number of threads.

Busy threads

Indicates the number of currently busy threads



Current users

Indicates the number of users currently connected



Determining Distinguished Name of Web Agent

The distinguished name has to be specified in the format, <webagentname>.<domainname>. To know the <webagentname>, do the following:

  1. First, execute Novell's ConsoleOne utility. This utility allows you to manage eDirectory objects, rights, and schema, and Netware file system resources.
  2. Upon logging into the console, you will find a tree-structure in the left pane that hosts an NDS container (see Figure 1). Expanding this container will reveal the eDirectory trees that you are currently logged into. Expand the eDirectory that hosts the GwWeb application to be monitored. Upon expanding, the list of contexts defined within the tree will appear. Next, expand the context within the eDirectory, which houses the GwWeb application (see Figure 1).


    Figure 1 : The Novell ConsoleOne window

  3. The complete list of objects within the selected context will then be available to you. The objects in the list that are prefixed by the domain symbol represent the domains within the context (see Figure 1). Now, click on the domain that hosts the GwWeb application to be monitored. The name of this domain will become the <domainname>. Upon clicking the domain, the applications that exist within will appear in the right pane (see Figure 1). From this right pane, select the GwWeb application to be monitored. The name of this application will become the <webagentname>. In Figure 1, "WEBAC65A" is the agent name, and "dell"is the domain name. Therefore, the webagentname should be specified as “”.