Displaying WGate Load Balancing Information (SAP Library - ITS Tuning and Troubleshooting Guide)

Displaying WGate Load Balancing Information

Use

You use this procedure to display WGate load balancing information for an ITS instance distributed across multiple AGate servers.

If you have installed one or more ITS instances on remote machines or one or more of the AGate servers that run these ITS instances reside on remote machines, you can:

Display load balancing information to show the distribution across each AGate server
Reset the counters that track the total number of requests and the number of failed requests made to each AGate server

Prerequisites

You have started ITS Administration.

Procedure

Displaying Load Balancing Information

Under any ITS instance distributed across multiple AGate servers, choose Load Balancing.

You see a screen similar to the following:

This graphic is explained in the accompanying text

In this case, the load for the ITS instance IT1 is distributed across two AGate servers – pal002906 and itshost – and the following information is displayed for each one:

The Host name column displays the name of the AGate server
The State column specifies the status of the AGate server

There are three possible values:

Ready (as shown above) means that the AGate server is running

Polled means that the AGate server is not running, but is being polled to check when it is running again

Uncontacted usually means that the WGate has not needed to contact the AGate server for load balancing purposes since the WGate server was last restarted.

This state can also occur in the following special circumstances:

If the Web browser makes a request to WGate using the ~agate_routing parameter or an existing session cookie, which was generated before the WGate server was restarted, the request bypasses the load balancing mechanism, because a specific AGate has been targeted. Although the request count on this AGate is incremented, the state remains Uncontacted, because the AGate has not been contacted for load balancing purposes. As soon as the WGate has to make any load balancing decision (for example, when a new session is created), it is likely to use this AGate. The state then changes to either Ready or Polled and does not go back to Uncontacted until the WGate server is restarted again.

The Capacity column specifies the current load distribution for each AGate server. When an AGate is started, its CPU capacity is calculated. The capacity of all contacted Agates is summed and the capacity of each is displayed as a percentage of this total.
The Requests column specifies the total number of requests made to each AGate server
The Failures column specifies the number of failed requests made to each AGate server

Resetting Request Counters

To reset the request counters that track the total number of requests and the number of failed requests made to each AGate server, choose WGate Reset.