Calendario valorizado de avance de la obra: El documento en el que consta la programación valorizada de la ejecución de la obra, por períodos determinados en las

The enhanced method of extracting and processing user identification for HTTP can be configured globally for all HTTP-related software services configured on AMDs set to work in HTTP Mode, or it can be configured for a specific user-defined software service on the User Name

Recognition tab. For SAP GUI over HTTP software services, monitoring a predefined user

recognition policy is enabled by default. You can use the default setting, modify it, or add your own.

Before You Begin

It is assumed for this task that you have already created one or more user-defined software services for this protocol and that you are familiar with how to access global settings for user identification for HTTP and with user identification rule settings for a specific service.

Ensure HTTP analyzer is set to HTTP mode. For more information, see Choosing HTTP Analyzer Mode in the Data Center Real User Monitoring Web Application Monitoring User Guide.

When adding the detection rules used to identify the user names, you have to follow one the following scenarios.

User session context

The user name recognition is performed in the context of a particular user session. All monitored hits must contain the session ID, but only a single login hit contains the user name. In addition to defining the user detection rules, define session ID rules as well, as described in Configuring User Name Recognition for HTTP in HTTP Mode in the RUM Console Online Help.

The SAP GUI schema user name recognition policy is based on this scenario.

Non-context

The user name recognition is performed individually per hit, consequently each hit must contain a user name. You only need to add user detection rules as described in Configuring User Name Recognition for HTTP in HTTP Mode in the RUM Console Online Help

Ack URL (User session context, acknowledge URL)

The user name recognition is performed in the context of a particular user session and a login is validated by redirection to a special acknowledge URL. All monitored hits must contain the session ID, but only the ACK hit is the first one to contain the user name. Besides user and session ID rules, you need to provide the acknowledge URL (as described in the procedure) for the AMD to be able to discover a user session and retrieve the user name.

1. Open the User Name Recognition screen for a particular user-defined software service or open the corresponding screen for Global settings.

2. Select or clear Enable User Name Recognition for a specific service.

This option is available only for a specific software service. Clearing the setting here disables it for this service only, regardless of any global settings for HTTP. Selecting it gives you the choice of using global settings or of selecting settings specific for the given service. Service-specific settings always take precedence over global settings.

3. Select a search policy.

Add new or select an existing policy, that is a container for a set of detection rules. Right-click a cell in the Available Policies table and select Add or Edit.

Adding the detection rules 4. Adding user name rules.

Right-click a row in the User recognition rules table and select Add or Open. User

Recognition Rule Definition dialog opens. At least one user rule is required for user

recognition mechanism.

a. Choose a type of user recognition rule.

When adding the detection rules used to identify the user names, you have to follow one the following scenarios.

Ack URL (User session context, acknowledge URL)

The user name recognition is performed in the context of a particular user session and a login is validated by redirection to a special acknowledge URL. All monitored hits must contain the session ID, but only the ACK hit is the first one to contain the user name. Besides user and session ID rules, you need to provide the acknowledge URL (as described in the procedure) for the AMD to be able to discover a user session and retrieve the user name.

Session ID (User session context)

The user name recognition is performed in the context of a particular user session. All monitored hits must contain the session ID, but only a single login hit contains the user name. Besides user detection rules, you need to define session ID rules as well.

User Name (Non-context)

The user name recognition is performed individually per hit, consequently each hit must contain a user name. You only need to add user detection rules as described in Step 4 [p. 89]

b. Choose where to search for a value.

You can retrieve the user names and session identifiers from a number of entities, referred to as search scopes. For more information, see Choosing Search Scope for User Identification [p. 90].

c. Optional: Configure the Host and path settings.

Enter the following to filter the traffic used for user name recognition.

Host pattern

Server host name.

Path pattern

The leading part of a URL. Only hits beginning with this string will be matched. This parameter is optional. If it is not specified, the path is assumed to be “/”

and it will match any requested URL.

d. Configure the search and transformation rules to be applied.

It is sometimes difficult to perform a successful match resulting in a legible string in one pass. In such situations, you can perform further transformations to your initial search result.

Right-click a row in the Apply following search and transformation rules table and select Add or Open. Search or transformation rule definition dialog opens.

e. Advanced settings

Match only when response has one of the indicated HTTP status codes. The HTTP status codes can be defined by providing the HTTP status code range. Use the official HTTP status codes to narrow down qualifying responses.

• (100 - 200) Informational • (200 - 300) Success • (300 - 400) Redirection • (400 - 500) Client error • (500 - 600) Server error

Choosing Search Scope for User Identification

You can retrieve the user names and session identifiers from a number of entities, referred to as search scopes.

When you create a user name or session ID rule definition, you have to apply it to only one search scope, which you have to choose as a first step in creating the definition. Identify the entities containing user or session identification, consider applicable scenarios, then choose one of the following scopes:

Request or Response Headers Request or Response Body Request parameter

Cookie

Note that available search methods depend on the selected search scope. For more information, see Choosing Method of Searching for User Identification [p. 91].

When you create a number of definitions for one policy, the definitions are applied in the order in which they were entered in the rules table. The first successful match is used.

Choosing Method of Searching for User Identification

Choose one of the available search methods to detect the user names in the selected search scope.

Depending on the selected search scope, choose one the methods of extracting user names. Each search method requires you to specify a different set of extraction rules.

Add prefix

Use this method if you expect the value to always be preceded by a specific prefix. To extract the value, provide the prefix expected to precede the value.

Cookie name search

Specify the cookie from which to extract the value. Provide the value of a specific cookie name confirming a successful login. The session ID, for mapping to the value, is extracted from this cookie. Successful logins are normally recognized by a SET COOKIE operation for the named cookie

Basic

Use this method if you expect the value to always be carried by a specific parameter. To extract the value, provide the name of the parameter. Depending on the selected search scope, the term parameter refers to a specific entity, such as a cookie name when the search scope is set to cookie, or a header field when the search scope is set to request or response header. Enter the parameter name without delimiters. The search is not case sensitive and no wildcard characters are permitted in the string unless the wildcard character “*” is to be used literally. This search method is not available for the response body search scope.

Decode / decompress

If you expect to perform a search on a compressed or encoded data, or URL encoded in case of URL parameters, you can bring the search results to a human readable form by using one of available decoders, Base64, Base64 + Gzip, Gzip or URL encoding. You can also extract parts of your initial search results by using Text search or Regular

expression search methods. Choosing Method of Searching for User Identification [p. 91]

Mime encoded list filter

Use this method if you expect to find a value in an MIME format. Including text in character sets other than ASCII, message bodies with multiple parts and in header information encoded in non-ASCII character sets.

NTLM search

Use this method to search for a value in an NTLM authentication request header. Depending on your choice, the value can be composed of the following fields: workstation, domain, or user. Select the fields that compose an identified value and, if necessary, change the default character used to separate the selected components in the resulting value.

Parameter name and value search

Use this method if you expect the value to always be carried by the specific parameter. To extract the value, provide the parameter name. Depending on the selected search scope, the term parameter may refer to a specific entity, such as a cookie name (when the search scope is set to cookie), or a header field (when the search scope is set to request or response header).

Parameter name prefix search

Use this method if you expect the value to always be carried by a specific parameter with a specific prefix. To extract the value, provide the parameter name prefix and indicate what data should be reported. The results of the search can be presented as a parameter name and the value, just the parameter value or just a parameter prefix.

Parameter value suffix search

Use this method if you expect the user name to always be carried by the specific value of a parameter with a specific suffix. To extract the user name, provide the value for the suffix.

Regex search

You construct a regular expression that, when applied to a selected search scope, returns the value. The regular expression must contain at least one group enclosed in parentheses. If the regular expression returns a number of search groups, you can define the custom group order by entering a comma-separated list in the order of your choice (for example,

2,1,3). This method is not available for the cookie and response body search scopes. For

more information, see Regular Expression Fundamentals [p. 233].

You can test the patterns that will be used by the AMD using the Regular Expressions

Test tool, which is activated after you click Test located next to the regular expression

pattern field. For more information, see Testing Regular Expressions [p. 235].

Example 3.

The following is an example of extracting the value of REMOTE_ADDR field from the HTTP

header.

An HTTP header might contain the following information:

GET http://www.slow-server.com/login.jsp HTTP/1.1 Accept: */*

Referer: http://www.slow-server.com/ Accept-Language: en-us

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) Host: www.slow-server.com

Connection: Keep-Alive

Cookie: FPB=061j8hura11q56cv; CRZY9=t=1; REMOTE_ADDR: 10.1.0.2

The following regular expression extracts the address 10.1.0.2 from the REMOTE_ADDR

field:

REMOTE_ADDR: ([.0-9]*) Text phrase search

Use this method if you expect the user name to always be found in the text . The provided value for the search parameter will be used to match the text phrases in the analyzed traffic.

Text search

Use this method if you expect to find a user name between the first occurrences of strings defined by Match start and Match end. Because it is not always possible to extract the user names directly, you can use this method as a first step in preparing content for search result transformations. You can set a Search limit in bytes to avoid lengthy search results. This method is not available for the cookie search scope.