Monitoring Contexts in the Topology Display

Use

Use this function to obtain an overview of the monitoring contexts of the local or of a remote SAP system. A monitoring context is the uppermost node of a monitoring tree and contains all associated monitoring objects and monitoring attributes. A context is unique both in a segment and at system level. A segment can contain various contexts. Monitoring contexts can be defined system-wide or within an application server.

For more information about how you can start the topology display, see Calling the Technical Topology Display.

Features

By default, the system displays the following columns in the Local Contexts (<SID>) or Contexts (<SID>) tab pages:

Column	Meaning
Context Name	Self-explanatory
Context Type	The following entries are possible: 3x Appl. Serv. Instance-specific There is an instance-specific context in the segment of each instance. System-wide A system-wide context exists only once for each system. It holds data that does not exist for each instance, such as the context System Configuration. Depending on the start condition of the relevant data supplier, a context of this type is created in the segment either of any instance or a specific instance; if this instance is shut down, the context can switch instance. System-wide (fixed to segment) To prevent system-wide contexts switching segment, you can fix them to a segment. The context is then only available if the corresponding segment is available. The fixing represents a simple form of load distribution that should prevent the disk requirements of certain segments (especially the segment for the central instance) becoming too large due to a large number of system-wide contexts. Note You can activate and deactivate the fixing to a segment for every system-wide context (see below).
Segment Name	Segment to which the context belongs; the name of the monitoring segment has the structure SAP_CCMS_<name of the SAP instance> or, for CCMS agents, SAP_CCMS_<hostname>

Column

Meaning

Context Name

Self-explanatory

Context Type

The following entries are possible:

3x Appl. Serv.
Instance-specific
There is an instance-specific context in the segment of each instance.
System-wide
A system-wide context exists only once for each system. It holds data that does not exist for each instance, such as the context System Configuration. Depending on the start condition of the relevant data supplier, a context of this type is created in the segment either of any instance or a specific instance; if this instance is shut down, the context can switch instance.
System-wide (fixed to segment)
To prevent system-wide contexts switching segment, you can fix them to a segment. The context is then only available if the corresponding segment is available. The fixing represents a simple form of load distribution that should prevent the disk requirements of certain segments (especially the segment for the central instance) becoming too large due to a large number of system-wide contexts.

Note
You can activate and deactivate the fixing to a segment for every system-wide context (see below).

Segment Name

Segment to which the context belongs; the name of the monitoring segment has the structure SAP_CCMS_<name of the SAP instance> or, for CCMS agents, SAP_CCMS_<hostname>

Note

You can use transaction RZ20 to determine the associated context for every node of the monitoring tree. Select the desired node and choose Properties. The entry in the Properties field has the following structure:

<System ID>\<context name>\... [\<monitoring object>][\<monitoring attribute>]

You can also show the following columns by choosing the Change Layout... button for the ALV Grid Control:

Column	Meaning
Changed By	Unlike the Monitored, Remote SAP Systems tab page, an automatic user (usually SAPMSSY8) can be displayed as the last changer, since the application server automatically registers with the monitoring architecture during startup.
MTE Class	Class of the monitoring tree elements (MTEs) to which the uppermost node of the context belongs.
Client	Client to which the context data refers
Context Owner	Owner specified by an API call during the initialization of a context
Monitored System	Usually identical to System Systemand Monitored System for a segment can only be different if you are monitoring systems without a monitoring segment in shared memory, such as SAP R/3 3.x systems. In these cases, the CCMS agent responsible for the monitoring technically belongs to the central monitoring system.
System Changed on Changed at	These columns have identical meanings as those with the same names when Displaying Monitored Systems in the Topology Display.

Activities

In addition to the purely display functions, the following commands are available to you as buttons in the ALV Grid Control in change mode; to start change mode, choose the Display «Change button ():

Command	Explanation
Delete Entry	Delete the entry for the local context; this is useful, for example, to remove inconsistencies Note Deleting contexts has no effect on the function of the monitoring architecture - the system automatically renews entries for active monitoring contexts.
Fixing On	Fixes a system-wide context to a segment; on the following screen, select the segment to which you want to fix the context in the Segment input field Note If you move a context with this function, that is, fix it to a segment other than the one in which currently exists, you should then Reset the Segment to WARMUP-Status. This ensures that the startup methods are executed again and the nodes of the context continue to be supplied with values.
Fixing Off	Removes the fixing again for a context of the type System-Wide (Fixed to Segment)