SAP Mobile Server logs collect data on
SAP Mobile Server health and performance by component. Configure
SAP Mobile Server log properties to specify the amount of detail that is
written to the log, as well as the duration of the server log life cycle.
Additionally, you should always use
SAP Control Center to configure server logs. If you
manually edit the configuration file, especially on secondary servers in a cluster,
the servers may not restart correctly once shut down.
- In the SAP Control Center left navigation pane, click
Configuration.
- In the right administration pane, click the Log Setting tab and select Mobile Server.
- The option "Start a new server log on server restart" is set by
default. When selected, this option means a new version of the log file is
created after server restart, and the old one is archived.
- Set the
MMS
server log size and backup behavior that jointly determine the
server log life cycle.
- Set the Maximum file
size, in kilobytes, megabytes, or gigabytes, to specify
the maximum size that a file can reach before a new one is created. The
default is 10MB.
Alternatively, select No
limit to log all events in the same file, with no
maximum size.
- Set the Maximum backup
index to determine how many log files are backed up
before the oldest file is deleted. The index number you choose must be a
positive integer between 1 and 65535. The default is 10 files.
Alternatively, select No
limit to retain all log files.
- Set the HTTP log settings.
- Select Enable HTTP request log to generate an
HTTP request log in the logs subdirectory. The generated log file name
is server-name-http.log.
Note: HTTP logging is off by default. Enabling HTTP logging can cause a
performance impact and possible logging of sensitive data.
- Set the Maximum file size of the log file.
Note: Maximum file size only takes effect when you select either
Perform rotation or
Archive.
- If you want to back up the log file when it reaches the limit, select
Perform rotation. The backup file is saved as
server-name-http.log.backup-number.
- If you want to continue to use the current log file when the server
restarts, select Reuse.If you do not select this
option, when the server restarts the current log file is copied to the
.\old subdirectory and a new log file is
created.
- If you want to archive the log file select
Archive, then specify the Archive
file name. If you want to compress the archive log file
select Compress.
- For each component, choose a log
level:
| Component |
Default Log Level |
|---|
| MMS |
Warn |
| PROXY |
Warn |
| Cluster |
Warn |
| MSG |
Warn |
| Security |
Warn |
| PUSH |
Warn |
| Mobilink |
Warn |
| DataServices |
Warn |
| Other |
Warn |
| DOEC |
Warn |
| Log level |
Messages logged |
|---|
| All |
Complete system information |
| Trace |
Finer-grained informational events than debug |
| Debug |
Very fine-grained system information, warnings, and all
errors |
| Info |
General system information, warnings, and all errors |
| Warn |
Warnings and all errors |
| Error |
Errors only |
| Console |
Messages that appear in the administration console only (when
SAP Mobile Server is running in
non-service mode) |
| Off |
Do not record any messages |
- Click Save.
Log messages are recorded as specified by
the settings you choose. The log file is located in:
SMP_HOME
\Servers\UnwiredServer\logs\<hostname>-server.log.
Log life cycle default example
If you keep the default maximum file size and default index, an
SAP Mobile Server writes to the log file until 10MB of data has
been recorded. As soon as the file exceeds this value, a new version of the log file
is created (for example, the first one is <hostname>-server.log.1). The
contents of the original log are backed up into this new file. When the <hostname>-server.log file again reaches its
limit:
- The contents of <hostname>-server.log.1 are copied to <hostname>-server.log.2.
- The contents of <hostname>-server.log are copied to <hostname>-server.log.1.
- A new copy of <hostname>-server.log is created.
This rollover pattern continues until the backup index value is reached, with the oldest log being deleted. If the backup index is 10, then <hostname>-server.log.10 is the file removed, and all other logs roll up to create room for the new file.