The Central Syslog structure in SM21 provide you with access for the syslog information of all available instances in the system.
Transaction SM21 and select System log -> Choose -> Central System logs.
Every SAP application server has its own shared memory with the syslog created by the kernel. The goal of the Central Syslog Information is concentrate logs from SAP application servers in a Central file that is determined by the parameter "rslg/central/file".
The SAP created 2 external tools called "rslgcoll" and "rslgsend" deamon that are responsible to read the local shared memory for every SAP applicaiton server and store the log information in the central file.
To this work the Collector (rslgcoll) must run in one instance (usually the central instance) and for every application server the Sender (rslgsend) have to be configured.
The Sender is responsible to read the shared memory and forward the logs to the Collector
through TCP protocol and the Collector is responsible to writte these logs in the central file. The SAP note 25526 has further information about this configuration with its TCP ports for the Collector and the Sender.
This configuration with the Collector and the Sender is usually configured in the instalation process of the SAP system and this works very well.
However, for standalone instances like ASCS and SCS the Sender is not configured and you are not able to check the logs from Message Server and Enqueue.
Altough these standalone instances are not a normal dialog instance they have the internal shared memory with the logs. In such way you can start the Sender for every standalone instance and it will solve the problem.
The goal of this "How to" if configure the Sender in a standalone SAP instance in some steps.
In my example I am going to configure in a SCS instance release 700
1) Make sure that the DIR_EXECUTABLE has the rslgsend
2) Set the start up configuration in the start profile
_SE = se.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_11 = local rm -f $(_SE)
Execute_12 = local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_02 = local $(_SE) pf=$(_PF) -F
Note that "Start_Program_XX" must be in a sequencial order of all others Start_Program_XX in the start profile, so you have to use the XX with a high number of the last one.
3) Stop the SCS instance
4) Restart the sapstartsrv service
5) Start the SCS instance
The Central Syslog do not work for Windows Enviroment.
For detailed information about the Central Syslog check the SAP documentation in this link:
As from 720 the Central Syslog is running under Web Services (sapstartsrv) instead of Sender and Collector.