Skip to main content
Version: 723.SP03

Logs

On occasion, issues may arise in the communication between SAP and hyperscalators via the HTTP Request protocol. To identify the source of the problem and determine a solution, we recommend utilising the Log Monitor. This straightforward tool enables users to trace a specific execution and gain insight into the underlying issue.

How to access the log monitor​

To gain access to the monitor, please use the transaction code /LNKAWS/MON_AL

How to operate with it​

  • Activate/deactivate log: To save and subsequently analyse the logs, it is necessary to activate the log. This can be done by clicking on the Change log status button, which can be found in the Actions section.To disable the feature, please click the same button again.

  • Check the log: Once the log status is set to active, you can then proceed to select the relevant dates1 and times1 and press the Query2 to initiate your search. The results will then be displayed in the first box3.

    The information is divided into two categories:

    1. For Archivelink/GOS: In the first box, the content server request information.
    2. For SDK: You will find the information about the petition in this section.

    The final column in the table indicates whether the HTTP request was successful or not.

    IMPORTANT

    To complete the information, please run the following report /LNKAWS/CREATE_LINKS to establish a connection to the SAP object. It is recommended that this process be run in the background as a job.

    In the second box, you will find the request and response from the REST service. To obtain further information regarding a specific query, simply double-click on the line of interest. This will display the various events associated with that line.

    If you wish to view the data transmitted or received, select a line1 in any of the boxes and click on the Show XML2 button and get the result in a pop-up3.

  • Download full query: To export the entire query, you may do so by clicking the Download button, which you will find in the Actions section. This will generate a file in JSON format.