Show TOC Anfang des Inhaltsbereichs

Funktionsdokumentation Monitoring the IGS with CCMS  Dokument im Navigationsbaum lokalisieren

Use

You can use an SAP system (Basis Release 6.10 and later) to monitor the IGS. The CCMS transaction RZ20 is used as the monitoring tool. You can find more information on CCMS in our Knowledge Warehouse documentation.

CCMS gives the administrator an overview of the current IGS configuration. The portwatchers available and their associated interpreters are displayed in a hierarchy. CCMS also displays various performance values for the relevant IGS components.

The performance values of the available components are updated automatically with the result that bottlenecks can be located and removed quickly.

Activities

In transaction RZ20, you can find the IGS as the Internet Graphics Server in the monitor set SAP CCMS Monitors for Optional Components. Just  double-click on this entry and a hierarchy with performance values is displayed. If no hierarchy is displayed, even though the IGS is running, call transaction SE38 and execute the program graphics_igs_admin. Choose Environment     Switch on CCMS to activate the IGS display in RZ20.

Monitoring Data Description

The following list contains the data that is monitored in CCMS together with a description:

Data

Description

Uptime

 

The "uptime" is a CCMS performance measurement. It specifies the number of seconds the portwatcher has already been running for.

Data volume in (min)

This specifies the smallest amount of data sent in a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically involve sending different amounts of data.)

Data volume in (max)

This specifies the largest amount of data sent in a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically involve sending different amounts of data.)

Data volume in (avg)

This specifies the average amount of data sent in a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically involve sending different amounts of data.)

Data volume out (min)

This specifies the smallest amount of data returned after a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically result in different amounts of data being returned.)

Data volume out (max)

 

This specifies the largest amount of data returned after a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically result in different amounts of data being returned.)

Data volume out (avg)

This specifies the average amount of data returned after a call from the multiplexer to the portwatcher and its interpreter. (Different calls typically result in different amounts of data being returned.)

Duration (min)

This specifies the minimum duration required for generating a graphic / for an interpreter task. The duration is expressed in milliseconds.

Duration (max)

This specifies the maximum duration required for generating a graphic / for an interpreter task. The duration is expressed in milliseconds.

Duration (avg)

 

This specifies the average duration required for generating a graphic / for an interpreter task. The duration is expressed in milliseconds.

 

Calls

This shows the number of calls from the multiplexer to the portwatcher.

 

 

Ende des Inhaltsbereichs