Displaying Logs and Traces
Use
You can search for logs and traces for Web service provider and consumer calls on the AS ABAP, and display them.
The logging function provides information on processing steps 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 Message Monitoring and in the Sequence Monitor.
More information:
Monitor for
Processed XML Messages, Monitoring Sequences
in the SOA Manager
Using the tracing function, you can analyze errors in detail.
If another 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 for further tracking. This information is displayed in the tab pages.
If logging and tracing is activated over a lengthy time period, this can have a negative effect on performance.
Prerequisites
You have configured logging and tracing.
More information: Configuring Logging, Configuring Tracing
Procedure
...
1. Start SOA Management (transaction SOAMANAGER) and choose the tab Logs and Traces and Logs/Trace Viewer.
2. You have the following options:
¡
To display an
overview, under Show select which calls you want to display. You can
select the following: all calls, failed calls, successful calls
Under From, select the time period.
Choose Go.
The default time period displays information for all calls from the previous 30 minutes.
¡ To show specific information, choose Extended. Under Search by you have the following options:
§ Performance
Specify the upper limit for the processing time in milliseconds.
§ Design Time Selection
Select the interface names. All the interfaces defined in the system are displayed.
§ Status
You can specify status information, error types (system error, application error), and error areas for a specific time period.
§ Identifier
Enter identifiers such as message ID, SOAP sequence ID, WSRM sequence ID (for consumer or provider), trace key, and call ID.
The trace key groups together all call IDs that belong to the processing of a Web service call. The trace key is a GUID.
In addition to these options, enter a time period for which you want to execute the search.
3. The calls found are displayed.
¡ Status
Successful, error, or warning
¡ 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 displays where Web Service Processing occurs:
§ Provider shows incoming calls to the provider.
§ Consumer shows outbound calls from Web service consumers.
¡ Scheduled
X shows that the call is scheduled before the asynchronous boundary set in the bgRFC Scheduler.
Empty shows that the call is after the asynchronous boundary.
More information: bgRFC (Background Remote Function Call)
¡ Communication Pattern
Name of operation in 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.
4. To display the details for a specific call, select the call.
The following information is available.
¡ Header
Contains 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, select Download Header Data.
¡ Log Records
The processing steps of the call are displayed together with descriptions. Whenever 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
The trace records are only available in English.
Depending on which trace level is selected, detailed trace information is displayed.
Whenever an error occurs, the system always writes trace data records.
¡ 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 Request or Download Response.