Show TOC

 Example Decision Table: Organizational DecisionsLocate this document in the navigation structure

Work through the following table to make your design decisions and to provide the information that you require to implement your data supplier. Use the results to adjust one of the template reports available in the system (see Data Supplier for Users Logged On: Report RSDSUSER). Your data supplier will then be ready to use.

The table starts with organizational and structural decisions. These are adopted in the function modules for the creation of monitoring objects and attributes (function modules SALI_*_CREATE_ATTACH). For information about the object-specific and attribute-specific implementation decisions that you need to make, see Decision Table: Monitoring Attributes for the Attribute Types.

Design Consideration Possibilities and Specifications

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

Use the following monitoring attributes, depending on which data you want to display in the alert monitor:

  • Performance attributes
  • Status attributes
  • Log attributes
  • Text attributes

The attribute determines the function module of the monitoring architecture that you need to use.

Scope of your data supplier

  • Is the data supplier to be started only once for each SAP NetWeaver system (system-wide data supplier)?
  • Is the data supplier to be started on one or on all SAP NetWeaver instances (local data supplier)?

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

If the Alert Monitor is to start the data supplier:

  • Should the alert monitor start the data collection method in a dialog work process, and how often should it do so (every so many seconds)?
  • Should the alert monitor start the data collection method in a background work process, and how often should it do so (every so many hours)?

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

Behavior of the data collection method at the system start:

  • Should the data collection method be automatically started when SAP NetWeaver is started?
  • Should the instrumented component execute the data supplier as required?

Execution location of the data collection method:

  • Should the method be executed on the server or instance specified in the MTE?
  • Should the method be executed on any server or instance?
  • Should the method be executed on the database server?

Start behavior of the data collection method when the Alert Monitor is started:

  • Should the method of each MTE be started individually?
  • Should the method be started for all associated MTEs? If possible, choose this option.

You need to set these options manually in the definition of a data collection method in the Alert Monitor (transaction RZ21); see Data Supplier for Users Logged On: Settings in RZ21.

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:

  • Which messages (ID/numbers) describe the monitoring objects or your component in the Alert Monitor?
  • Which messages (ID/numbers) describe the individual monitoring attributes in the Alert Monitor?
  • Which messages (ID/numbers) describe the alerts generated for the monitoring attributes?

Messages in status and log attributes are T100 messages and therefore automatically have access to F1 help.

Properties of the MTE classes and attribute groups

Assign the nodes that you want to create using the data supplier to MTE classes and attribute groups:

  • MTE class for the object
  • MTE classes for each monitoring attribute
  • Attribute groups for the monitoring attributes (attribute groups exist only for monitoring attributes)

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

Structure your alert monitoring tree:

  • Which headings are required for structural elements (summaries for the display) to group subordinate MTEs (length of the name up to 20 characters)?
  • At which points in your monitoring tree are the summaries to appear in the form of summary MTEs? What are the parent nodes?

 Start Page Creating a Data Supplier for the CCMS Alert Monitor