Server Configuration: Offline

Property	Description	Default	Notes
Initial cache size	Sets the initial cache size for offline OData refreshes.	50M	Use K, M, or G to specify units of kilobytes, megabytes, or gigabytes, respectively.
Restartable download cache size	The amount of cache memory the offline OData service should use to cache large downloads so clients can resume downloads.	1G	Restartable downloads are always turned on for offline OData clients. Downloads restart automatically at the client until the entire download is received. If the restartable download cache size is too small, the offline OData service may release download data, making it impossible to restart a download. Download data is not released until one of the following occurs: The refresh is successfully completed. A new refresh request is received without restart enabled. The cache is needed for incoming requests. The oldest pending refresh is cleared first. Use K, M, or G to specify units of kilobytes, megabytes, or gigabytes, respectively.
Network logging level	Sets the network stream logging level.	None	The logging setting for the offline component in SAP Mobile Platform must be set to `Info` for these verbosity settings to take effect. This option is used for debugging, and can be set to none, low, medium, or high. Information such as network bytes, network activity, and packet level information is logged. The network logging information is stored in the SAP Mobile Platform log. Enabling network logging may impact performance.
Period for logging performance values	Sets the frequency, in seconds, to log periodic performance values for offline OData refreshes.		The logging setting for the offline component in SAP Mobile Platform must be set to `Info` for this setting to take effect. The suggested period is 60 seconds. If the period is set too small, the log grows very quickly. Results are stored in the SAP Mobile Platform log. To aid in searching for and filtering out the values, each log line contains: PERIODIC: The periodic performance values are logged in the SAP Mobile Platform log.
Logging verbosity	Sets the logging verbosity level for offline OData refreshes.		The logging setting for the offline component in SAP Mobile Platform must be set to `Info` for this setting to take effect. For no verbosity, leave this option blank. For lowest verbosity, specify one or more blank spaces. The available levels are as follows. You can use a single option, or multiple options simultaneously, for example, nrm. + Turn on all of the verbosity levels. i Display the column values of each row uploaded. Use this option instead of r, which displays the column values of each row uploaded and downloaded, to reduce the amount of data being logged. Specifying i with q is the same as specifying r. n Show row-count totals per refresh. q Show download row values. r Display the column values of each row uploaded or downloaded. To log only the column values of each row uploaded, use i. To log only the column values of each row downloaded, use q.
Number of initial back-end worker threads	Sets the initial number of back-end worker threads for offline OData refreshes.	30	Each back-end worker thread accepts refresh requests one at a time, but also concurrently with all other back-end worker threads. Set his value with care. Increasing it may increase or reduce the overall throughput of offline OData refreshes. Use load testing to find the value that works best for your deployment. Use the maximum number of back-end worker threads setting to define a dynamic range of worker threads.
Maximum number of back-end worker threads	Sets the maximum number of concurrent back-end worker threads for offline OData refreshes.		The offline OData service monitors performance and automatically adjusts the number of back-end worker threads as necessary, using any value between the initial value and the maximum value. If you do not specify a maximum value, this value defaults to the value of the initial number of back-end worker threads, and they are not automatically adjusted.
Network worker thread count	Sets the number of network worker threads used for concurrent processing of network streams.		Having multiple network worker threads can improve performance, particularly when using CPU-intensive network stream options, like compression, with either large refreshes or many small refreshes. Each request in the system can be active on one network stream thread, at most.
Warning levels to log	Controls the levels of warning message to display.	1,2,3,4,5,	Warning codes are logged only if the offline component in the SAP Mobile Platform is set to `Warn`, `Info` or `Debug`. To specify multiple levels of warning messages, use a comma-separated list. The warning message levels are as follows: 0 Suppress all warning messages. 1 Server level: warning messages when the offline OData service starts. 2 Synchronization and user level: warning messages when a refresh starts. 3 Schema level: warning messages when the offline OData service is processing a client schema. 4 Script level: warning messages when the offline OData service executes scripts. 5 Table or row level: warning messages when the offline OData service performs table operations in an upload or download.
Warning codes to suppress	Disables specific warning codes.		Warning codes are logged only if the offline component in the SAP Mobile Platform is set to `Warn`, `Info` or `Debug`. You can disable specific warning codes so that are not reported, even though other codes of the same level are reported. To specify warning codes to suppress in the log, use a comma-separated list.
Warning codes to enable	Enables specific warning codes.		Warning codes are logged only if the offline component in the SAP Mobile Platform is set to `Warn`, `Info` or `Debug`. You can enable specific warning codes to be reported even though you have disabled other codes of the same level. To enable multiple warning codes, use a comma-separated list.
Reserved options	Enables the use of additional offline OData service configuration options.		This field is reserved for experimental or undocumented features and should only be used as instructed by Product Support.

Initial cache size

Sets the initial cache size for offline OData refreshes.

50M

Use K, M, or G to specify units of kilobytes, megabytes, or gigabytes, respectively.

Restartable download cache size

The amount of cache memory the offline OData service should use to cache large downloads so clients can resume downloads.

1G

Restartable downloads are always turned on for offline OData clients. Downloads restart automatically at the client until the entire download is received.

If the restartable download cache size is too small, the offline OData service may release download data, making it impossible to restart a download. Download data is not released until one of the following occurs:

The refresh is successfully completed.
A new refresh request is received without restart enabled.
The cache is needed for incoming requests. The oldest pending refresh is cleared first.

Use K, M, or G to specify units of kilobytes, megabytes, or gigabytes, respectively.

Network logging level

Sets the network stream logging level.

None

The logging setting for the offline component in SAP Mobile Platform must be set to Info for these verbosity settings to take effect.

This option is used for debugging, and can be set to none, low, medium, or high. Information such as network bytes, network activity, and packet level information is logged. The network logging information is stored in the SAP Mobile Platform log.

Enabling network logging may impact performance.

Period for logging performance values

Sets the frequency, in seconds, to log periodic performance values for offline OData refreshes.

The logging setting for the offline component in SAP Mobile Platform must be set to Info for this setting to take effect.

The suggested period is 60 seconds.

If the period is set too small, the log grows very quickly. Results are stored in the SAP Mobile Platform log.

To aid in searching for and filtering out the values, each log line contains:

PERIODIC:

The periodic performance values are logged in the SAP Mobile Platform log.

Logging verbosity

Sets the logging verbosity level for offline OData refreshes.

The logging setting for the offline component in SAP Mobile Platform must be set to Info for this setting to take effect.

For no verbosity, leave this option blank.

For lowest verbosity, specify one or more blank spaces.

The available levels are as follows. You can use a single option, or multiple options simultaneously, for example, nrm.

+ Turn on all of the verbosity levels.
i Display the column values of each row uploaded. Use this option instead of r, which displays the column values of each row uploaded and downloaded, to reduce the amount of data being logged. Specifying i with q is the same as specifying r.
n Show row-count totals per refresh.
q Show download row values.
r Display the column values of each row uploaded or downloaded. To log only the column values of each row uploaded, use i. To log only the column values of each row downloaded, use q.

Number of initial back-end worker threads

Sets the initial number of back-end worker threads for offline OData refreshes.

30

Each back-end worker thread accepts refresh requests one at a time, but also concurrently with all other back-end worker threads.

Set his value with care. Increasing it may increase or reduce the overall throughput of offline OData refreshes. Use load testing to find the value that works best for your deployment.

Use the maximum number of back-end worker threads setting to define a dynamic range of worker threads.

Maximum number of back-end worker threads

Sets the maximum number of concurrent back-end worker threads for offline OData refreshes.

The offline OData service monitors performance and automatically adjusts the number of back-end worker threads as necessary, using any value between the initial value and the maximum value.

If you do not specify a maximum value, this value defaults to the value of the initial number of back-end worker threads, and they are not automatically adjusted.

Network worker thread count

Sets the number of network worker threads used for concurrent processing of network streams.

Having multiple network worker threads can improve performance, particularly when using CPU-intensive network stream options, like compression, with either large refreshes or many small refreshes. Each request in the system can be active on one network stream thread, at most.

Warning levels to log

Controls the levels of warning message to display.

1,2,3,4,5,

Warning codes are logged only if the offline component in the SAP Mobile Platform is set to Warn, Info or Debug.

To specify multiple levels of warning messages, use a comma-separated list.

The warning message levels are as follows:

0 Suppress all warning messages.
1 Server level: warning messages when the offline OData service starts.
2 Synchronization and user level: warning messages when a refresh starts.
3 Schema level: warning messages when the offline OData service is processing a client schema.
4 Script level: warning messages when the offline OData service executes scripts.
5 Table or row level: warning messages when the offline OData service performs table operations in an upload or download.

Warning codes to suppress

Disables specific warning codes.

Warning codes are logged only if the offline component in the SAP Mobile Platform is set to Warn, Info or Debug.

You can disable specific warning codes so that are not reported, even though other codes of the same level are reported.

To specify warning codes to suppress in the log, use a comma-separated list.

Warning codes to enable

Enables specific warning codes.

Warning codes are logged only if the offline component in the SAP Mobile Platform is set to Warn, Info or Debug.

You can enable specific warning codes to be reported even though you have disabled other codes of the same level.

To enable multiple warning codes, use a comma-separated list.

Reserved options

Enables the use of additional offline OData service configuration options.

This field is reserved for experimental or undocumented features and should only be used as instructed by Product Support.