Short text
Standardization of names of “Request Entry Points” for tools, such as the SQL Monitor.
Parameter Description
The SQL Monitor and other tools, such as the ABAP Call Monitor, use the information “Request Entry Point”, which is set for each internal session. The information for the “Request Entry Point” consists of:
- the type of request, for example:
- TA Transaction
- RFC: Remote Function Call
- SUBMIT: SUBMIT <report>
- BTC Batch processing
- UPD: Update
- URL: HTTP Request
- and the name of the request.
In the SQL Monitor, the type of the request and the request name are used for the aggregation of the datasets. This results in a problem for the request names that carry context information (for example, if used in a URL or a GUID) that identifies the context in the back end. Data that occurs in requests with such names can no longer be aggregated correctly by the SQL Monitor.
The profile parameters “abap/sqlm/replace_request_n<n>” (there are altogether 7 parameters; “<n>” can stand for values 0-7 annehmen) provide help in this case. Using the example of the profile parameter “abap/sqlm/replace_request_1” with its default value, we can explain the structure of the parameter:
abap/sqlm/replace_request_1 = REQ=URL,PATT=”([0-9]|[A-F]){32}”,REPL=”[..]”
The first part “REQ=URL” specifies HTTP requests. Here it is also possible to specify a different request type – for example, “RFC” for “Remote Function Calls” (see above).
For the argument “PATT”, you can specify a standard expression that will be searched for in the request name. If it is found, this part of the name is replaced by the entry specified in the argument “REPL”.
Here, the replace function works in the same way as for the ABAP command
replace regex ‘([0-9]|[A-F]){32}’ in url with ‘[..]’.
The content of the profile parameter “abap/sqlm/replace_request_1”, as specified above, is the primary content for HTTP requests; the GUIDs with length 32 in the name contribute to a replacement of the GUIDs with “[..]”, for example.:
/sap/public/my_app?guid=5056A7004E1EE5B79395E5BF68940E –> /sap/public/my_app?guid=[..]
All the seven profile parameters are applied, one after another, in the kernel upon request entry.
The profile parameters are delivered with default values and can, as required, be changed or added to.
