Configuring the Logging Process 

Use

Logging provides you with information about the most important processing steps in the SOAP runtime. You can specify the log level for user names and interfaces (name service definition at design time).

Do not set the log level to 'Inactive'. If you do so, you will not have any data for analysis when an error occurs.

The log configuration is client-specific.   

Prerequisites

To configure the logging process, your user must be assigned one of the following roles.

●      SAP_BC_WEBSERVICE_ADMIN_BIZ

●      SAP_BC_WEBSERVICE_ADMIN_TEC

These roles provide authorization for the authorization object S_WS_LGTRC with activity 36.

More information: Authorizations

Procedure

...

       1.      Start SOA Management (transaction SOAMANAGER) and on the Logs and Traces tab page choose Logging Configuration.

       2.      Make the following entries for logging:

○       Enter the name of the user under which the system is to log calls in the SOAP runtime.

If you leave the field empty, the system creates a log for all users.

○       Enter the interface for which the system is to log calls in the SOAP runtime.

The interface is the service definition for the service provider, and the consumer proxy for the service consumer.

If you leave the field empty, the system creates a log for all interfaces.

○       Choose the log level:

■       Inactive (internal 0)

Logging is switched off.

■       Error (internal 1)

The system logs errors during processing. This is the default.

■       Error and performance (internal 2)

The system logs errors during processing. The system measures the runtime behavior against some SOAP runtime measuring points.

■       All events (internal 3)

All results of the SOAP runtime are logged and the system measures performance.

       3.      To reset the entire logging to the default value and to reset the logging of errors, choose Reset to Default Logging.

       4.      To switch off logging, choose Switch Logging Off.

Result

If you create an entry without specifying a user name and interface in the configuration table, the system creates logs during the SOAP runtime for all users and interfaces.

If you have made multiple entries in the table that overlap, the SOAP runtime will always apply the entry that leads to the greatest limitations.