The kernel will write the syslog messages which are stored in the SCSA to an OS file SLOG$$ on operating system level. These files are created in
an instance specific directory /usr/sap/<SID>/<INST>/log.
On Windows systems the SCSA is created by the kernel executables. You can use the transaction “ST02>Detailed analysis menu>Additional
functions: Storage>Shared memory details” to see if the SCSA area which belongs to ipc key 05 is correctly created for the ABAP instance.
Starting from 7.02 system release the central syslog sender and collector daemon are not used (supported) anymore (note 1565427). Also starting
from 7.02 the RFC function calls and RFC communication is not used anymore for the Remote System Log functionality but is replaced by Web
Services methods and SOAP (Simple Object Access Protocol) communication (sending XML based on HTTP or HTTPS or SMTP or FTP). For this
new concept the dispatcher and dialog resources of the remote instance are not used anymore but this is replaced by the SAPSTARTSRV program
which is used to start the ABAP instance. In the SAPSTARTSRV program the Web Services method functionality is implemented and this
functionality can be used by using the SOAP communication protocol.
1508049 - Problems when writing the central system log
1550906 - Information about the system log files
1517379 - Which system log format does the 720 kernel write
Excerpt of note 1041390:
"
rslg/central/log/new
The following values are allowed:
0 = old version, that is RSLGCOLL/RSLGSEND
1 = HTTP
2 = HTTPS
If the new profile parameter is not available, the default is 1 (which is HTTP)."
In this system this is the case -> HTTP is set.
The Central syslog no longer work with the sender and collector. This concept was changed with kernel 720 and netweaver > 7.02.
For further information check the notes:
1041390 - SM21: Central system log via HTTP or HTTPS
1741743 - Central syslog as of Basis Release 7.02
1774185 - Welches Syslog-Format schreibt der 720 Kernel