Entering content frameProcedure documentation Using the AGate Performance Monitor Locate the document in its SAP Library structure

Use

You use this procedure to monitor AGate performance with the AGate performance monitor in ITS Administration.

The functions of the AGate performance monitor allow you to:

This includes thread usage info, transaction counters, SAP GUI for HTML browser data and HTML template cache counters.

Note

Before you can display any of these statistics, you must enable the AGate performance monitor explicitly in ITS Administration.

Procedure

  1. Start ITS Administration.
  2. Enable the AGate performance monitor by taking the following steps:
    1. Select an ITS instance and choose an AGate server hosted at the local machine.
    2. Choose Configuration.
    3. Choose Registry.
    4. Choose CCMS.

You see a screen similar to the following:

This graphic is explained in the accompanying text

    1. Enable the AGate performance monitor by setting the following parameter to 1:

Parameter

Description

PerfMonitoring

0

Performance monitoring switched off (default).

1

Performance monitoring switched on.

PerfTimeLoadShm

Frequency in seconds that performance data is written to shared memory.

The default value is 10.

PerfRemoteProcesses

Defines the number of remote AGate processes, for which you wish to display monitoring information.

The default value is 2.

When you change this parameter, the change takes effect after the next AGate instance restart. Setting PerfMonitoring to 1 has no noticeable impact on performance, so you can use it in production systems.

  1. On restart, select the relevant ITS instance and choose the same AGate server again.
  2. Choose Performance.

You see several functions in an expanded directory structure.

This graphic is explained in the accompanying text

If there are multiple AGate processes at the current host, you can run these functions for each process.

  1. Choose a function.

ITS Administration prompts you to enter the desired time interval.

This graphic is explained in the accompanying text

      1. Specify the following:
      2. Start Date and Time

        End Date and Time

        The start and end dates and times are inclusive

        Graph type (if you want a graph display)

        You can specify Averages (the average value for each time interval displayed) or Peaks (the maximum value for each interval).

      3. Choose View Performance Log or View Performance Graph.

If you choose View Performance Log, you see a screen similar to the following:

This graphic is explained in the accompanying text

If you choose View Performance Graph, you see a graphical representation of the above information.

You see a screen similar to the following:

This graphic is explained in the accompanying text

The three sections in this table contain:

The fields are described in the following table:

Field

Description

PID

Process ID.

TAT

Turnaround time.

Total

Total time for AGate + Wait + R/3 + Browse.

AGate

Time taken within AGate.

Wait

Time taken by dispatcher to assign request to a workthread.

R3

Time taken to send a request to R/3 and receive a response.

Browse

Time taken to send results to Web browser via WGate and Web server.

Kernel

Kernel CPU time usage.

User

User CPU time usage.

You see a screen similar to the following:

This graphic is explained in the accompanying text

The fields are described in the following table:

Field

Description

PID

Process ID.

Maximum

Maximum number of workthreads that can be used.

Current

Current number of workthreads used.

Created/Destroyed

Number of times that a workthread has been dynamically created and destroyed during peak loads of the AGate.

Transactions

Number of Web transactions executed.

Block Length

Average length of a block sent from R/3 (in bytes).

Blocks/Transaction

Average number of blocks per transaction.

Average Rendering Time

Average time taken to render an HTML page in the Web browser.

Average Request Time

Average time taken by a request, including the rendering time.

Requests

Number of requests.

Requests

Number of requests made to cached templates.

Found

Number of templates found in the cache.

Percentage

Percentage of templates found in the cache.

You see a screen similar to the following:

This graphic is explained in the accompanying text

The fields are described in the following table:

Field

Description

Session

Session ID.

Use

Session use flag.

Service

AGate service.

Client

R/3 client.

User

R/3 user.

Transaction

R/3 transaction or RFC/BAPI called.

SID R/3

System ID.

You see a screen similar to the following:

This graphic is explained in the accompanying text

The fields are described in the following table:

Field

Description

TID

Thread ID.

Status

Step executed in workthread.

Client

R/3 client.

User

R/3 user ID.

Transaction

R/3 transaction or RFC/BAPI call.

ETime

Time since request was received by Agate.

KTime

Kernel CPU usage.

UTime

User CPU usage.

You see a screen similar to the following:

This graphic is explained in the accompanying text

The fields are described in the following table:

Field

Description

PID

Process ID.

TID

Workthread ID.

Total

Total time for AGate + Wait + R/3 + Browse.

AGate

Time taken within AGate.

Wait

Time taken by dispatcher to assign request to a workthread.

R3

Time taken to send a request to R/3 and receive a response.

Browse

Time taken to send results to Web browser via WGate and Web server.

Kernel

Kernel CPU time usage.

User

User CPU time usage.

You see a screen similar to the following:

This graphic is explained in the accompanying text

To reset, choose Refresh.

For more detailed information about the AGate performance monitor, see ITS Installation Tuning.

Leaving content frame