You can use the log messages generated by the Agentry Server to diagnose development or production issues, determine processing times for numerous aspects of synchronization, and to obtain various other pieces of information.
* - These log files can be viewed using the SAP Control Center.
These log files are always generated and cannot be disabled. Their contents do not have different verbosity levels.
Log files are enabled or disabled, configured, and managed using the SAP Control Center. The options available are to enable or disable the various log files, to specify whether log files are generated based on a processing thread or more narrow areas of functionality, and to set the verbosity level of the log message contents.
The contents of all log messages, regardless of category, include both error messages and informational or status messages. Each message includes a date and time stamp precise to the millisecond. The verbosity of the messages generated is configured when the category of log messages are enabled.
Log messages generated by the Agentry Server are stored in log files. When enabling and configuring the logging behavior of the Agentry Server, the contents of the log messages are configured. In addition, the files into which those messages are written is also configured. By default, when a log message category is enabled, those messages are written to a log file for a processing thread. Each Agentry Server processing thread will have its own log file containing all messages generated by the Agentry Server for processing within that thread, and for the category of log messages that have been enabled.
As an optional additional method for storing log messages, each category of log messages can be written to a category-specific log file. When this is enabled, all log messages generated by the Agentry Server for a specific category are written to the same log file, regardless of processing thread. The messages within the category-specific log files are grouped by the processing thread. Therefore, a category log file contains log messages resulting from processing related to that category.
Configuring the log files to generate separately based on the log message category will have a negative impact on Agentry Server performance, as multiple processing threads are logging messages to the same physical log file. Only a single message is written at a time to such a log file. Therefore, each thread must wait until the log file is available before it can write its log message to the log file. It is recommended to configure log files in this manner only for Agentry Development Servers with any regularity. It can be done in a production environment, but only when necessary and for limited durations.
All log files are written to the applicable Agentry application folder in C:\SAP\MobilePlatform\Servers\UnwiredServer\logs. Log files are rolled periodically by the Agentry Server, during Agentry Server startup or restart, and on command. The files are rolled to the sub-directory Logs-Rolled.