Administrator

Server Configuration: Offline

There are several properties you can use to configure behaviors such as cache sizes and logging levels for the offline OData service. You must restart the server for the changes to take effect.

In Management Cockpit, select Start of the navigation path Settings Next navigation step Offline End of the navigation path, and configure the property values.

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. 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. 0 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 Server log.

Logging Verbosity Sets the logging verbosity level for offline OData refreshes.   The logging setting for the offline SAP Mobile Platform component must be set to Info for this setting to take effect.

For no logging, leave this option blank.

The available levels are as follows. You can enter a single option, or multiple options simultaneously, for example, inq.
  • + – turn on all of the verbosity levels.

  • i – log the column values of each uploaded row.

  • n – log row-count totals per refresh.

  • q – log downloaded row values.

  • r – log the column values of each row that is uploaded or downloaded.

    To log only the column values of each uploaded row, use i. To log only the column values of each downloaded row, 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 this 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. 100 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. 1 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 that are shown. 1,2,3,4,5 Warning messages are logged only if the SAP Mobile Platform offline component is set to Warn, Info, or Debug.

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

The warning message levels are:
  • 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 during an upload or download.

Warning Codes to Suppress Disables specific warning codes.   Warning codes are logged only if the SAP Mobile Platform offline component is set to Warn, Info, or Debug.

These codes apply to MobiLink only—see MobiLink server warning messagesInformation published on SAP site.

You can disable specific warning codes so that they are not reported. Use a comma-separated list for multiple codes.

Warning Codes to Enable Enables specific warning codes.   Warning codes are logged only if the SAP Mobile Platform offline component is set to Warn, Info, or Debug.

These codes apply to MobiLink only—see above. .

You can enable specific warning codes to log. Use a comma-separated list for multiple codes.

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.