Show TOC

Application Log ViewerLocate this document in the navigation structure

For convenience, there is a specific viewer for application log entries created by SAP Gateway processes.

You can start the report in transaction /IWFND/APPS_LOG in the SAP Gateway hub system or /IWBEP/VIEW_LOG in the SAP Business Suite backend system. In the selection screen, you can search log protocols by object, subobject, log ID, content ID, request direction, GSDO type (for Generic Channel), user, log class, and date.

Runtime log protocols can be found under the Object /IWFND/ in SAP Gateway hub systems, including the SAP Gateway application-specific logs. Use the selection option GSDO Type to differentiate between the different application objects. In SAP Business Suite backend systems the Object is /IWBEP/.

Protocols for design time processes can be found under the Object /IWFND/ or /IWBEP/ and Subobject DESTIM. If the corresponding log protocol exists in the database, it will be displayed in the SAP Gateway Application Logs screen. All relevant subobjects can be selected using input help.

For object /IWFND/ the following subobjects are available:

Subobject

Description

CLEANUP

Cache and data persistence management

DESTIM

Design time processes

RUNTIM

Runtime processes

For object /IWBEP/ the following subobjects are available:

Subobject

Description

DESTIM

Design time processes

RUNTIM

Runtime processes

The log messages display for each request GUID, grouped by the agent, component or class that produced the log. On the next grouping level, the messages are separated into business and technical messages. The producer of each message also displays, with report/class/function module name, method, and the code line number. Details of the log message and the long text are displayed at the bottom of the screen. If the error message stems from an SAP Business Suite backend system, use Details to display the corresponding message long text.

Logging - What Information Is Recorded

The amount of logs created by the SAP Gateway agents corresponds to the log level specified in the customizing. See the Logging Settings activities in the SAP Implementation Guide. Different log levels types are available:

  • Global log level:

    This log level can be set for two different situations: for regular service adaptation layer (SAL) activities as well as for single activity trace. This setting will override any existing setting that has previously been defined.

  • User log level:

    You can set the log level that is to be used for a particular user.

Both can vary between:

  • All: Messages of type Information, Warning, and Error will be saved to the application log.

  • Step Completion Information: Messages of type Step Completion Information, Warning, Security and Error will be saved to the application log. (Messages of type Step Initiation Information will be omitted.)

  • Warning, Error, Security: Messages of type Warning, Error and Security will be saved to the application log. (Messages of type Step Initiation Information and Step Completion Information will be omitted.)

  • Error, Security: Messages of type Error and Security will be saved to the application log. (Messages of type Step Initiation Information and Step Completion Information will be omitted.)

  • Error: Messages of type Error will be saved in the application log. (Messages of type Warning, Step Initiation Information, Security and Step Completion Information will be omitted.)

  • None: No messages are created and saved.

If the log level for a particular user is set at a higher value than the global level, then for that user the individual log level will take precedence. If no log level is set, the lowest level (Error) is used.

Note

If the log level Security is chosen, messages are logged without message variables, because variables may contain sensitive business data.

Logging - How Should Each Trace Level Be Used

You can set the log levels in the SAP Gateway Implementation Guide (IMG) structure in the SAP Reference IMG in transaction SPRO in a SAP Gateway hub system under Start of the navigation path SAP Gateway Next navigation step OData Channel Next navigation step Administration Next navigation step Logging Settings End of the navigation path. In an SAP Business Suite backend system the path in the IMG in transaction SPRO is as follows: Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Business Suite Enablement Next navigation step Backend OData Channel Next navigation step Logging Settings End of the navigation path.

Clear Application Log

Over time the application log amasses a lot of entries, which periodically need to be cleared. As default the application log should only store one entry per request. In addition, there is no need to store these entries for more than a day or a few days. Application log cleanup is a standard requirement in productive systems and helps to improve the performance of the systems in your system landscape.

The application log cleanup scenario /IWFND/CLEANUP_APPSLOG comprises the integration of the central application log deletion program (report SBAL_DELETE) into the SAP Gateway cleanup framework.

For this IMG activities are available: You can clear the application log in the SAP Gateway Implementation Guide (IMG) structure in the SAP Reference IMG in transaction SPRO.

In a SAP Gateway hub system navigate to Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Next navigation step OData Channel Next navigation step Administration Next navigation step Cache Settings Next navigation step Clean Up Cache and Persistency End of the navigation path. Here the Cleanup Scenario is /IWFND/CLEANUP_APPSLOG.

In an SAP Business Suite backend system the path in the IMG in transaction SPRO is as follows: Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Service Enablement Next navigation step Backend OData Channel Next navigation step Logging Settings Next navigation step Clear Application Log End of the navigation path. Here you carry out the activity, plan a job, and use report sbal_delete to clear the application log.

The cleanup scenario /IWFND/CLEANUP_APPSLOG triggers the deletion of certain application log protocols. The following protocols will be deleted:

  • Expired protocols and protocols without expiration date.

  • Protocols of the provided users.

  • Protocols which have either the subobject RUNTIM or DESTIM of the object /IWFND/. The deletion can be started for each of the subobjects separately.

  • Protocols created before a certain date or today.

When using the SAP Gateway cleanup framework you can trigger the deletion periodically by using batch jobs.

For general information about application log deletion, see the SAP NetWeaver documentation about Delete Log.

Exposure of Service Id in Application Log Protocol

All messages of a Data Provider are stored in the Application Log protocol, so that you get an overview of the messages and warnings that are issued by the provider implementation. The SAP Gateway log agents store the service ID in the header of the protocol. It is also possible to search for protocols by service.

More Information

For more information, see Trace and Log Files.

A more comprehensive error log is also available. For more information, see Error Log.