Middleware monitoring - SAP RFC

In the SAP RFC section you set parameters specific to monitoring SAP RFC-based software services.

General

The Remote Function Call (RFC) interface system enables function calls between two SAP systems, or between a SAP system and an external system. Use the SAP RFC analyzer to configure the monitoring of communication between a SAP system and another SAP, or between a SAP system and a third-party system.

Most SAP RFC monitoring parameters are adjusted globally, which means that you can create most basic parameters for software monitoring when you create user-defined software services.

To change SAP RFC monitoring settings, open NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, Global ► Middleware Monitoring ► SAP RFC.

Attributes/metrics/parameters/users

  • Choose how value should be reported
    Define how the extracted value should be reported.

  • Choose where given value should be reported

    **Value reported as Attribute Select the group based on automatically detected sets of operation attributes: SAP RFC error, SAP RFC error indicator, Group 3, Group 4, Group 5

    **Value reported as Metric Select the group based on sets of metrics: Group 1, Group 2, Group 3, Group 4, Group 5

    **Value reported as Parameter Select the group based on automatically detected sets of parameters: Group 1, Group 2, Group 3, Group 4, Task name, Module name, Service name

    **Value reported as User Automatically reported in User name group.

  • Choose source to extract value from

    You can choose from which Field ID the value should be extracted. Options include Predefined set for Field IDs, Custom entry where you can manually enter the Field ID or a default set of CPIC errors.

    Predefined field Selecting a predefined Field ID will set the Field type automatically and known value decoding rules will be applied.

    Custom field Selecting the Custom option, you will have to select the value transformation method (Field type) and provide additional information depending on which method was selected. Make sure your custom entry uses the correct format: 0xNNNNN where “NNNNN” can be any value in 2-bytes hex format.

    CPIC Error This option will attempt to extract the value from an error occurring in Common Programming Interface-Communications API (available only for Attribute definition).

  • Apply given regular expression to the value
    This required field enables you to match and extract a particular value from the parameter name in the observed traffic.

Availability

Configuring the availability you can determine which attempt failures will be included in the availability metric calculation.

The availability is measured and presented as the percentage of successful attempts (operations) compared to all attempts. Each attempt is counted in one metric: operation, standalone, abort, network failure, transport failure or application failure. All operations with availability problems are included in the Failures (TCP), Failures (transport) and Failures (application) metrics.

You can configure SAP GUI availability globally or at the software service level.

For global configuration, open the NAM Probe configuration and go to Global ► Middleware Monitoring ► SAP GUI ► Availability. For the software service level, select the Availability tab in the Edit Rule window.

Failures (transport)

You can determine whether the Partial response errors are included in the calculation of Failures (transport) metric.

Failures (applications)

Enable or disable the automatically detected operation attributes to individually select which sets of operation attributes are included in the calculation of Failures (application) . The following operation attributes are available:

  • SAP RFC error
  • SAP RFC error indicator
  • Operation attributes (3)
  • Operation attributes (4)
  • Operation attributes (5)

Note that all of these are configurable. For more information, see SAP RFC.

SAP RFC

Use the following threshold settings to accurately identify the true source of the problem:

  • Server time threshold
    The Server time threshold relates to the server time portion of an overall operation time. Server times above the threshold limit are considered to be slow due to poor datacenter performance.
  • Idle time threshold Network time threshold
  • Retransmissions threshold
    Network time affected by high retransmission threshold
  • Request size threshold
    Network time affected by the transfer of a big request threshold
  • Response size threshold
    Network time affected by the transfer of a big response threshold
  • Number of hits threshold
  • Single hit duration threshold
  • Rtt threshold