
You have configured logging and tracing.
More information: Configuring Logging, Configuring Tracing
You can display logs and traces for Web service provider and consumer calls on the AS ABAP.
The logs provide information about processing in the SOAP runtime. You can use information such as the name of the interface, the name of the operation, the message ID, and the user ID to perform further analyses in the Sequence Monitor.
More information, see Monitoring Sequences in the SOA Manager.
The tracing functionality allows you to perform detailed error analysis.
If a level other than Inactive or Errors is set for logging and tracing, the system saves all the data of the SOAP runtime components and all the information about the messages involved.
If logging and tracing is kept activated over a long time, this can have a negative impact on system performance.
You can select the following:
All calls
Success calls
Warnings
Failed calls
The default time period displays information for all the calls from the previous 30 minutes
|
Time |
Restrict the search to a specific time period. |
|
Design Time Selection |
Select the interface names. All the interfaces defined in the system are displayed. |
|
Performance |
Specify the upper limit for the processing time in milliseconds. |
|
Status |
You can specify status information, error types (system error, application error), and error areas for a specific time period. |
|
Other |
Specify a particular user, application, client, and consumer or provider. |
|
Identifier |
Enter identifiers such as a message ID, SOAP sequence ID, WSRM sequence ID (for consumer or provider), trace key, and call ID. The trace key groups together all the call IDs that belong to the processing of a Web service call. The trace key is a GUID. |
The following information is displayed:
|
Status |
Successful, error, or warning |
|
Timestamp |
Timestamp of Processing in the SOAP Runtime |
|
Interface Name |
The interface is the service definition for the service provider, and the consumer proxy for the service consumer. |
|
Location |
Shows where Web Service Processing occurs: Provider: incoming calls to the provider. Consumer: outbound calls from Web service consumers |
|
Is Prescheduled |
X indicates that the call is scheduled before the asynchronous boundary set in the bgRFC Scheduler. Empty indicates that the call is after the asynchronous boundary. More information: bgRFC (Background Remote Function Call) |
|
Communication Pattern |
Name of the operation in the Web service call If the name of the operation is not known, the name of the SOAP data provider (SOAP_RUNTIME_CONFIG, SOAP_RUNTIME_CORE, SEQUENCE_MANAGER) is displayed. |
|
Call ID |
A Web service call is divided into multiple calls. |
The following information is displayed:
|
Header |
Information that is the same for all measuring points within a call For example, the user name for the call, the client, the name of the application server, and the size of the request and response messages. Header data is always displayed if logging and tracing for errors is configured. To store header data in a file, choose Download Header Data. |
|
Log Records |
The processing steps of the call are displayed with descriptions. If an error occurs, the system always writes log data. The log data is displayed irrespective of the language you are logged on to the system with. |
|
Trace Records |
Detailed trace information is displayed, depending on which trace level is selected. If an error occurs, the system always writes trace data records. The trace records are only available in English. |
|
Payload Trace |
The payload trace contains business data - for example the SOAP envelope and the HTTP header. If the trace level is set to either payload trace or complete trace, the system writes the payload trace. To display the SOAP envelope and the fields of the payload header in a file, choose Download Header Data. You can only display the payload trace if the payload data was created in the client that you are logged in to. You need the authorization object S_SRT_PTRC. |