Show TOC

 Data Supplier for Users Logged On: Decision TablesLocate this document in the navigation structure

The number of users logged on is to be displayed for each SAP instance. All questions asked in the decision tables (Decision Table: Organizational Decisions and Decision Table: Monitoring Attributes for the Attribute Types) are answered here using the example. The answers are italicized.

Example Decision Table: Organizational Decisions

Design Consideration Possibilities and Specifications

Monitoring Data (What type of information is to be reported?)

A performance attribute is to display the number of users logged on for each instance.

Scope of your data supplier

A local data supplier is to be executed once on each instance.

Start of the data supplier (how is your program started?)

If the Alert Monitor is to start the data supplier:

  • The Alert Monitor should start the data collection method every 300 seconds in a dialog work process.

Other specifications about the start behavior (you determine here how and where a data supplier runs)

How should the data collection method behave at the system start?

  • The data collection method should be automatically started when SAP NetWeaver is started.

Where should the data collection method be executed?

  • On the server or instance specified in the MTE

If the data collection method is started by the Alert Monitor, for which MTEs should it be started?

  • One start for each individual MTE

Messages (define the associated message IDs and numbers for the monitoring objects, attributes, and alerts)

Define message IDs and numbers from table T100 for the following objects:

  • A description of the monitoring object is not required, since the attribute node will hang under the existing monitoring object Dialog.
  • Message RT 068is assigned to the monitoring attribute (Application server: Number of logged-on users)).
  • Alerts for this attribute are assigned message RT 577(&1 > &2 Number of users logged on to application server exceeds threshold).

Properties of the MTE classes and attribute groups

  • No new MTE classes for monitoring objects (see above)
  • MTE class for all of the monitoring attributes: R3UsersLoggedIn
  • Attribute group for all of the monitoring attributes: R3UsersLoggedIn

Summary MTEs (enter any summary MTEs to structure your monitoring tree)

  • Headings for structural elements

    No new structural elements

  • Position in your monitoring tree:

    The node is at the following point in the tree structure: <System> → <instance> → Dialog → UsersLoggedIn

Example Decision Table: Monitoring Attributes for Performance Values

Design Consideration Possibilities and Specifications

Definition of the performance attribute

Name of the attribute in the Alert Monitor:            UsersLoggedIn

Superordinate MTE in the monitoring tree:            Dialog

Unit (up to four characters):                                No unit

MTE class:                                                       R3UsersLoggedIn

Attribute group:                                                  R3UsersLoggedIn

Alerts are to be triggered if the threshold values are exceeded.

Alerts during the warm-up time are to be ignored.

Threshold values for:

  • Yellow alert (warning):       50
  • Red alert (problem):    70
  • Resetting of status from red to yellow: 60
  • Resetting of the status from yellow to green:     40

Threshold values are not really meaningful here. To deactivate alert generation, you could also set the threshold values to MAXINT.

Note

For more information about this example, see the following sections:

 Start Page Creating a Data Supplier for the CCMS Alert Monitor