Aplicación de conceptos y normativas en el GAD Municipal de Otavalo

You can override the global settings for SAP GUI analysis by configuring rules for particular user-defined software services.

Before You Begin

See Configuring User-Defined Software Services in the RUM Console Online Help and Configuring Rules for User-Defined Software Services in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide to learn how to create and define user-defined software services.

For a broader perspective, see Basic Monitoring Configuration in the Data Center Real User Monitoring Web Application Monitoring User Guide.

To change the monitoring parameters: Configuring Services

1. After the software service is defined, right-click the Rules table to open the context menu and choose Add.

The Rule Configuration window opens.

2. On the Services tab, define services to be monitored. For more information, see Configuring Rules for User-Defined Software Services in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide. By default, the port number is 3201.

Configuring User Name Recognition

On the SAP GUI Operations tab, you can override most of the global settings for the analyzer. You can also define more detailed rules, such as the use of regular expressions in user name recognition.

NOTE

The differences in configuration of SAP GUI monitoring in earlier AMD versions prohibits the operation status and operation name configurations to be migrated to the current version. The default values will be applied in current version making some of the SAP GUI monitoring settings unavailable for editing.

3. Define a chunk ID containing user names and optional user name normalization.

User name chunk ID

The chunk ID string contained in the command chunk that also contains the user name. This may vary depending on the server.

Default value is 16.4.28 for AMD versions 12.1 and later. You can use regular expression to operate on the user name parts for a given chunk ID. Enter a regular expression that enables you to filter the user name. Regular expressions may be useful for cutting out the irrelevant or unnecessary parts of names. Use POSIX Basic Regular Expressions syntax.

User name regular expression

You can enter a regular expression to normalize the user names detected in SAP GUI traffic. This option enables you to shorten the string reported as the user name for a given chunk.

For example, if, by default, the AMD detects user names as long chains of characters such as usernameprefixUser2012affix, you can use the regular expression

User[0-9]* to see only a part of the whole field on reports (User2012 in this case).

Configuring Operation Name Chunk IDs (Legacy AMDs)

By default, Use global values is selected. The software service is monitored using the operation name normalization settings created in Global ➤ Front-End Monitoring ➤ SAP GUI. Clear this option to start overriding the global settings.

4. Override the global setting for operation name mapping.

It is possible to copy the chosen chunk IDs defined in the Global SAP GUI settings. The

Available global chunk IDs list contains all the IDs you entered as global values. You can

select and copy one or all given chunk IDs to the Current chunk IDs table using controls located between the tables. The IDs are moved together all of the mapping or normalization settings. The File Path or Regular Expression fields are automatically filled with the settings defined in Global ➤ Front-End Monitoring ➤ SAP GUI.

This table presents configuration elements that are responsible for operation name reporting. You can choose to have the AMD report operation chunks in their raw form or normalized, and you can customize chunk content reporting through regular expressions. For more information, see Operation Names Configuration in SAP GUI Monitoring (Legacy AMDs)

[p. 51].

You can also select which chunk ID will be used to extract operation status. Use Operation

status list to select chunk IDs entered in the operation name customization table. The value

will be later appended to the T-Code by the CAS when SAP GUI operations are reported. By default UI status (also referred to as window title) chunk ID is selected as operation

status (16.6.16). Note that you can make a selection based only on the IDs from the Current

chunk IDs table.

Attribute/Metric/Parameters (Current AMDs)

By default, Use global values is selected. The software service is monitored using the operation name normalization settings created in Global ➤ Front-End Monitoring ➤ SAP GUI. Clear this option to start overriding the global settings.

5. Define how the value should be extracted, where should it be reported, and the value that is reported.

Monitoring T-Code alone is often not enough to pinpoint performance problems, especially when complex SAP transactions are performed. You can identify and report SAP operations based on context retrieved from specific SAP form fields. To do this, you will need to define a field value to be retrieved from selected SAP form fields.

This table presents definitions for each configured value. It summarizes how the value should be extracted, where should it be reported and as what should the value be reported. Use the right-click to open the context menu and choose Add, Open or Delete.

a. Choose how value should be reported

Define how the extracted value should be reported in CAS or ADS. CAS counts occurrences of the defined attribute while ADS reports on actual values retrieved.

Attribute Metric

Operation name parameter

b. Choose where given value should be reported

Select the group based on automatically detected sets of operation attributes.

c. Configure how value should be extracted

Select the value extraction method:

• Chunk ID

You can select which chunk ID will be used to extract the value. The value will be later appended to the T-Code by the report server when SAP GUI data is reported. By default Window Status (also referred to as window title) chunk ID is selected. (16.6.16).

• Form ID

Enter the SAP form ID that should be used to extract the value from selected SAP form fields.

• SAP GUI RFC Exception

SAP GUI traffic can contain information on RFC Exceptions and Errors. Selecting this option, you define the extracted value as a Remote Function Call (RFC) exception.

• SAP GUI RFC Error Message

Selecting this option, you define the extracted value as a RFC Error Message. Default configuration of RFC errors is applied.

d. Define if given elements occur more than once.

Select which of the values should be taken under consideration. Detected First, Last or All detected values.

e. Optionally, you can enter a regular expression that will be applied to the extracted value.

f. Search scope:

Select to which observed traffic the regular expression search should be applied:

response, request or both.

6. In the Operation settings table, click Add to open the Operation settings dialog box. Configuring Operation Settings

When monitoring complex systems such as SAP, you may experience anomalies when it comes to operation time reporting. It is typical for some SAP operations to take a very long time to execute (ranging from several minutes to several hours). They last significantly longer than the majority of operations you see on reports. Such operations, even though normal, will be classified as slow and will negatively affect the timing averages on reports.

In this case, you can configure individual operation load time thresholds for a chosen operation or exclude it from monitoring. Note that exclusion is not equal to ignoring the operation by the AMD. Exclusion means that load time for the particular operation will not be shown by the Central Analysis Server. If you use the Advanced Diagnostics Server, the statistics will be shown on its reports.

Since Central Analysis Server uses a different method to analyze the monitored traffic, the value of Slow Operation metric in drilldown reports will differ. This inconsistency occurs when Advanced Diagnostics Server does not account for the SAP GUI Safety Valve and reports operations that Central Analysis Server excludes of its reports.

For the slow operations flow, the following reports and drilldown reports are affected by this inconsistency: Tiers (SAP) ➤ Servers ➤ Slow Operation Cause Breakdown ➤ Slow

Operation Loads

7. In the Operation settings dialog, define the operation that requires individual rules. Provide a T-Code and indicate whether you want it to be excluded from monitoring or set a time threshold for the operation containing this T-Code as part of the name.

• Define an individual Operation load time threshold by clearing the instruction to use the value set for the whole software service. You can increase or decrease the value of the threshold.

• Exclude the operation from monitoring. Select this option if you do not want to see operation time statistics for the particular operation on Central Analysis Server reports. If you select this option, setting individual operation time thresholds for this operation is impossible. Note that this does not affect ADS reports.

You can define slow operations on three levels: for the analyzer globally, for the whole software service, and for individual operations. Choose the method most suitable to your environment to see accurate data on reports.

Configuring Additional Options

On the Options tab, you can override the global settings for AMD configuration.

8. Change the settings for monitoring TCP session-related options.

Enable monitoring of persistent TCP sessions

We highly recommend that you enable this option for SAP monitoring.

When this option is selected, non-SYN sessions (TCP sessions for which the start was not recorded) are included in the TCP statistics. When enabled, this option generally does not negatively affect the reported data because the SAP analyzer dynamically calculates network metrics. When disabled in the SAP software service rule, the report servers may show issues with missing traffic.

9. Optional: Change the settings for monitoring operation load time threshold or select ADS-related options.

Operation load time threshold

An operation that takes more than this many seconds is considered slow. When Inherit

from global setting is selected, the global setting is used. The global threshold value

depends on the analyzer.

Safe Threshold

Use this option to exclude long-executing operations (in minutes) from average measurements. This improves the precision of reporting for typical interactive operations while maintaining the full scope of SAP transaction monitoring.

Operations longer than the value set in Safe Threshold will be excluded from average measurements.

SAP server time method

Define the method of calculating the server time for SAP GUI. This impacts reports showing metrics for the operations, hits and aggregate metrics for operations and hits.

first – The server time from the first observed operation is reported. last – The server time from the last observed operation is reported.

average – The average server time based on all observed operations is reported. max – The maximum server time from all observed operations is reported. sum – The sum of all operation server times is reported.

Generate sequenced transactions and ADS data

Select this option to provide data to the report server that consists of low-level protocol information, such as raw HTTP traffic data, which enables you to view the full HTTP request-response dialog.

10. Define the availability by enabling or disabling specific attempts to be included in

availability calculation.

When Inherit from global setting is selected, the global setting is used. For more information, see Configuring SAP GUI Availability [p. 50].