Administrator

Agentry events.log File

The events.log file records various Agentry events that occur at run time. Events include startup and shutdown, opening and closing connections to the application’s system connections, loading of client-server communication components, memory usage, thread expansion, and used and available storage.

The events log persists until one of the following occurs:
  • The log files are rolled by SAP Mobile Platform Server, at which point they are moved to a backup folder named rolled, in a subdirectory named for the date and time. By default, this occurs once every 24 hours, provided the SAP Mobile Platform Server is running. With a change to the application configuration, this file may also be moved to a backup location based on file size.
  • SAP Mobile Platform Server is shut down and restarted. In this case, the events.log file is moved to the backup folder rolled, in a subdirectory named for the date and time.

The events.log file cannot be disabled.

The following is an excerpt from a typical events.log file.
07/31/2013 01:45:00, 0,   0,   0, Thr   548, Rollover 

time
07/31/2013 02:42:09, 0,   0,   7, Thr   548, 
07/31/2013 03:42:10, 0,   0,   7, Thr   548, 
07/31/2013 04:42:11, 0,   0,   7, Thr   548, 
07/31/2013 05:42:12, 0,   0,   7, Thr   548, 
07/31/2013 06:42:13, 0,   0,   7, Thr   548, 
07/31/2013 07:42:14, 0,   0,   7, Thr   548, 
07/31/2013 08:42:15, 0,   0,   7, Thr   548, 
07/31/2013 09:42:16, 0,   0,   7, Thr   548, 
07/31/2013 10:42:17, 0,   0,   7, Thr   548, 
07/31/2013 11:42:18, 0,   0,   7, Thr   548, 
07/31/2013 12:42:19, 0,   0,   7, Thr   548, 
07/31/2013 13:42:20, 0,   0,   7, Thr   548, 
07/31/2013 14:42:21, 0,   0,   7, Thr   548, 
07/31/2013 15:42:22, 0,   0,   7, Thr   548, 
07/31/2013 16:42:23, 0,   0,   7, Thr   548, 

Each log message is written to a single line that begins with a timestamp. The next three columns, separated by commas, are the message type, message group, and the message ID. A message type of 1 indicates an error message, while a message type of 0 indicates an informational message. The message type is followed by the thread ID, denoted by the text Thr, and finally the message itself.