purge, flush threshold, and flush batch size settings to determine how
long domain log data is retained, how frequently it is written to database from server
nodes, and set a domain log database connection to configure where domain log data is
If you do not configure the auto-purge schedule, you can purge data
manually with the Purge
button. If you are
manually purging logs with hundreds of thousands of entries, note that
SAP Mobile Server removes these entries asynchronously to avoid
negatively impacting runtime performance. For smaller logs, the purge action tends to be
more instantaneous. To avoid large logs, use the auto purge
- In the left navigation pane of
SAP Control Center, select Domains.
- Under the default domain node, select Log.
- In the right administration pane, select the Settings tab. These settings are used for all domains.
- Click Configuration.
- Configure auto purge settings.
Auto purge clears obsolete data from the database once it reaches the specified threshold.
- Select Enable auto-purge
configuration to activate auto purge
- Enter the length of time (in days) to retain monitoring data before it is purged.
- Specify the Purge time. Auto-purge executes once per day at the
- Configure flush threshold settings:
The flush threshold indicates how often data is flushed from memory to the database. This allows you to specify the size of the data saved in memory before it is cleared. Alternately, if you do not enable a flush threshold, data is immediately written to the domain log database as it is captured.
- Select Enable flush
threshold to activate flush threshold
Note Enabling flush configuration is a good practice for performance considerations. Be aware there may be a consequent delay in viewing data, until data is stored in the database.
- Select one of:
Number of rows – domain log data that surpasses the specified number of rows is flushed from memory. Enter the desired number of rows adjacent to Rows. Disabled by default.
Time interval – domain log data older than the specified time interval is flushed from memory. Enter the desired duration adjacent to Minutes. The default is 5.
Either rows or time interval – domain log data is flushed from memory according to whichever value is reached first: either the specified number of rows or the specified time interval. Enter the desired rows and duration adjacent to Rows and Minutes, respectively.
- If you enabled a flush threshold, enter a Flush batch row size by specifying the size of each batch of data sent to the domain log database. The row size must be a positive integer.
The batch size divides flushed data into smaller segments, rather than saving all data together according to the flush threshold parameters. For example, if you set the flush threshold to 100 rows and the flush batch row size to 50, once 100 rows are collected in the console, the save process executes twice; data is flushed into the database in two batches of 50 rows. If the flush threshold is not enabled, the flush batch row size is implicitly 1.
Note By default, the domain log database flushes data
every 5 minutes. Alternatively, you can flush data immediately by removing or decreasing the default values, but doing so impacts performance.
- Optional. To change the data source, select an available
database from the Domain log database endpoint drop down
Available databases are those with a JDBC server connection type (SQL Anywhere) created in the default domain.
To create a new database, a platform administrator must set up a database by running the appropriate configuration scripts and creating a server connection for the database in the default domain. The database server connection then appears as an option in the Domain Log Database Endpoint drop down list.
- Optional. Change the maximum length of the payload data logged
in the payload column(s) of each sub-system. Large payload content is truncated
to the length specified as that value. The default max size is 12K (in bytes)
which is configured in the 'default' domain and applicable for all domains.
Increasing the domain payload size should be tested to identify proper
configuration for the server's JVM memory settings.
- Click OK.