SAP NetWeaver Gateway provides the following supportability tools for error analysis at runtime:
SAP NetWeaver Error Log
The Error Log in an SAP NetWeaver Gateway hub system (transaction /IWFND/ERROR_LOG) or in an SAP Business Suite backend system (transaction /IWBEP/ERROR_LOG) provides detailed context information about errors that have occurred at runtime. Some important information includes the source code and the call stack of the error location.
The goal of the SAP NetWeaver Error Log is in case of any error which leads to a termination of the request processing a log entry is written in the Error Log
containing the request data, response data, error context and especially, the source of the termination (mostly where the exception is raised) and the
corresponding ABAP call stack.
Release document: Error Log - SAP Documentation
See also FAQ: Error Log for more details.
SAP NetWeaver Gateway Client
The Gateway Client (transaction /IWFND/GW_CLIENT) for SAP NetWeaver Gateway is a powerful tool that provides the freedom to test any OData service. This enables you to test an OData service pro-actively and run a quality assurance test before a service is used by a mobile application, for example.
Release document: Gateway Client - SAP Documentation
See also FAQ: Gateway Client for more details.
SAP NetWeaver Performance Trace
The Performance Trace tool (transaction /IWFND/TRACES) enables developers, administrators, support consultants, and end users to monitor system
performance at service call level. You can trace the performance of both the SAP Business Suite backend system and the SAP NetWeaver Gateway hub system.
In case of a successful request processing the performance trace summary gives you an overview about the duration in different components involved in the processing such as the total duration, the framework overhead on hub system, the RFC and network overhead, the framework overhead on backend system and the duration of the provider application.
Release document: Performance Trace - SAP Documentation
See also FAQ: Performance Trace for more details.
SAP NetWeaver Payload Trace
The Payload Trace tool (transaction /IWFND/TRACES) enables developers, administrators, support consultants, and end users to monitor the flow of data
sent as part of service requests and responses. The tool is particularly helpful if you want to check the exact content of HTTP header and body data
sent and received. In some cases, for example, unexpected data might be contained in the response that did not lead to an actual system error that
would be displayed in the Error Log, but that nevertheless needs to be investigated.
Release document: Payload Trace - SAP Documentation
See also FAQ: Payload Trace for more details.
SAP NetWeaver Notification Monitor
There are two Notification Monitors for the OData Push Channel:
- The transaction /IWBEP/NOTIF_MONITOR provides an overview of all notifications to be sent using a background Remote Function Call (bgRFC) from an application in the SAP Business Suite backend system to the SAP NetWeaver Gateway hub system.
- The transaction /IWFND/NOTIF_MONITOR provides an overview of all notifications to be sent using a background Remote Function Call (bgRFC) from the SAP NetWeaver Gateway hub system to different OData consumers using the OData Push Channel.
Release document: Notification Monitor - SAP Documentation
See also FAQ: Notification Monitor for more details.