Developers, technical administrators, and application administrators can use the log viewer to obtain the following information about connectivity issues:
Which runtime calls have been made.
What has happened during the processing of a call.
What information has been transferred during a call.
They can analyze this information to find the reasons for which services or applications fail.
The system is set to collect logging information in one of the following ways:
A logging configuration has been active for the time period for which you want to view the recorded calls.
For more information, see Configuring Connectivity Logging .
The log controller for Web services and Web service clients log is com.sap.engine.services.webservices . If you want the system to log more information, you can set the severity level of this controller to ALL or DEBUG. For more information, see Configuring Log Controllers .
Increasing the severity level may impact the performance of the system. We recommend that you increase severity only when necessary.
The user account that you use for viewing the connectivity log meets one of the following conditions:
Assigned to the NWA_SUPERADMIN or other role that contains the SAP_JAVA_LOGS_TRACES or WebServiceLogsAndTraces_ALL user management engine actions.
This type of account is typical for a technical administrator. It allows the user to view all logged information.
Assigned to the NWA_READONLY or other role that contains the WebServiceLogsAndTraces_DISPLAY user management engine action.
This type of account is typical for a business administrator. It allows the user to view all logged information except the payload.
Displaying the Log Viewer
Log on to SAP NetWeaver Administrator.
Alternatively, you can use the quick link /ws-logs in the following way: http://<host>:<port>/nwa/ws-logs
Choose Log Viewer .
If you want to specify which information should be displayed for the calls found, choose and select the columns you want to view.
You can also specify the number of rows in the list of results.
To find specific log entries in the list:
Enter the search criteria in the corresponding field in the filter row.
If you enter only part of the term for which you want to search, you should use the asterisk (*) wildcard character.
Basic Log Searching
If the log viewer displays the advanced search options, choose Basic in the top right part of the Calls screen area.
Specify which calls you want to find by choosing one or more of the following:
Select whether you want to see the successful, failed, or all calls.
Select the type of connectivity for which you want to find calls.
You can choose between all, Web service, Remote Function Call, and Software Component Archive.
Select the time period for which you want to perform a search.
Advanced Log Searching
If the log viewer displays only the basic search options, choose Advanced in the top right part of the Calls screen area.
When you want to find a call by identifier, you should select Identifier in the Find by menu, choose whether to search by message or transaction ID, and enter the corresponding value.
You should enter the whole identifier without using wildcard characters.
When you want to perform a more extensive search, you should select All Selection Criteria in the Find by menu and enter the search data:
Make sure you specify the date and time for the start of the time period for which you want to perform a search.
By default, the end of this period is the current date and time. If that is what you need, you can leave the corresponding fields blank. If you want to enter the end date and time for that period, make sure you enter both.
You can choose what should be the status and the connectivity type of calls you want to find.
When you want to find a call initiated by a particular user, in a particular direction, or on a particular application server, you can set the necessary values in the Other screen area.
Consider the following:
When entering a user name, you should enter the whole name without using wildcard characters.
The Application Server list displays the node name and cluster ID for each server listed.
You can also choose to search only calls whose processing time exceeds a particular value.
When you want to find only calls performed via particular interfaces, you can add these interfaces to the Interfaces list.
This can be of use when the system is configured to collect connectivity information for calls performed via all interfaces. In case you want to monitor only calls performed via particular interfaces, it is recommended that you create a dedicated logging configuration for each of them. This way the system stores only the information you require, and you can search the logs without needing to specify the interfaces in which you are interested.
The system displays the calls that match your search criteria in a table. When you select a call in the table, you can see the following details in the Details About Call screen area:
Choose General to view the status of the processing steps, as well as basic information about the call such as status, connectivity type, and other information.
Choose Headers if you want to view or download the runtime call headers.
Choose Traces to display extensive information for the selected call such as the severity, location, processor name and ID, and other information.
Choose Payload to view the content of the SOAP envelope transmitted during the call.
You can see the business payload only when all of the following conditions are met:
There is an active logging configuration for which business payload tracing is activated.
You have the necessary permissions to view the payload information
If the system obfuscates the business payload and displays it with “X” characters the reason can be one of the following:
There are no active logging configurations, and the severity level of the com.sap.engine.services.webservices controller is set to DEBUG.
There are active logging configurations for which the business payload tracing is not activated.
The system does not store and display the payload when there are no active logging configurations and the severity level of the com.sap.engine.services.webservices controller is lower than DEBUG (for example, ERROR).
Managing the Call Details
When there is a large amount of information displayed in the Headers and Traces views, you can set which part of this information should be displayed using the controls on the right above the corresponding table.
You can download the headers, the tracing information, and the payload as a file. You can send these files to your colleagues or to SAP Active Global Support when you need to discuss connectivity issues.