Using external breakpoints you can debug the execution of the ON_START, ON_MESSAGE, ON_CLOSE and ON_ERROR methods similarily to an HTTP handler in the Internet Communication Framework (ICF), i.e. by setting breakpoints in the respective methods.
In transaction SAPC you can activate/deactivate the following supportability tools for a specific APC application:
Debugging : select
To activate deugging, proceed as follows:
In the pop-up window, enter a User name.
Define whether or not to use System Debugging .
Note
Select System Debugging , if you want to perform debugging on a system-wide level and not just limited to a single application server.
Check the Application ID .
Press Activate .
Runtime Analysis : select
Note
The runtime analysis records which start with the prefix APC:<application path> , e.g. APC:/sap/bc/apc/sap/ping for a PING application, can be monitored in transaction SAT .Transaction SMWS shows the list of active WebSocket connections and their associated APC application on each application server.
To activate runtime analysis, proceed as follows:
In the pop-up window, define whether or not the runtime analysis is to be User-Dependent .
Note
If you select this option, you can also specify if traces are to be written for All Users or not.
Enter a Validity Period for the activation in format <hh:mm:ss>.
Enter a User Variant and a Variant .
Note
In transaction ATRA , you can create a User Variant for your specific settings and enter it here. Generally, you can also create a Variant to specify all settings for runtime analysis, like type of measurement (aggregated or not), statements to be measured (ABAP statements, database access etc.) and program parts to be measured.
Define whether or not to use high Precision .
Note
Precision defines the measurement precision (X = high precision, 1 microsecond) for the statement GET_RUN_TIME.
Select the Processing Type
Composite entries: all entries will be saved in one file.
Single entries: each entry will be saved in a separate file.
Check the Application ID .
Press Activate .
Kernel Trace : select the required application in the tree and choose
Note
You should only activate traces if troubleshooting with debugging has not been successful, and the analysis of the application process needs to be continued at kernel level. Active kernel traces may affect your system performance.
To activate kernel traces, proceed as follows:
In the pop-up window, define whether or not the trace is to be User-Dependent .
Enter a Validity Period for the activation in format <hh:mm:ss>.
Check the Application ID .
Select the required Trace Level (2 or 3).
Note
The trace levels provide different information details about the kernel processes:
Level 2: technical traces are displayed which are to help follow the exact process flow for troubleshooting.
Level 3: all details for every file are displayed, including all attributes and detailed content of messages.
Press Activate .