Configuring SAP Mobile Server General Properties

To optimize SAP Mobile Server performance, configure the thread stack size, maximum and minimum heap sizes, and user options such as enabling trace upload to SAP® Solution Manager.

  1. In the left navigation pane, expand the Servers folder and select a server.
  2. Select Server Configuration.
  3. In the right administration pane, select the General tab.
  4. Configure these replication payload properties, as required:
    • Host Name – the name of the machine where SAP Mobile Server is running (read only).
    • Maximum Heap Size – the maximum size of the JVM memory allocation pool. Use K to indicate kilobytes, M to indicate megabytes, or G to indicate gigabytes. For production recommendations on this value, see SAP Mobile Server Replication Tuning Reference in System Administration.
    • Minimum Heap Size – the minimum size of the JVM memory allocation pool, in megabytes. For production recommendations on this value, see SAP Mobile Server Replication Tuning Reference in System Administration.
    • Thread Stack Size – the JVM -Xss option.
    • User Options (in Show optional properties) – other JVM options.

      For example, you can enable JVM garbage collection logging by setting -XX:+PrintGCDetails. Or you can set the permanent space which is allocated outside of the Java heap with the DJC_JVM_MAXPERM environment variable (in SMP_HOME\Servers\UnwiredServer\bin\usersetenv.bat); the maximum perm size must be followed by K, M, or G, for example, -XX:MaxPermSize=512M. Note that DJC_JVM_MAXPERM is not visible to SAP Control Center.

      If you are in an SAP environment and want to define the Solution Manager URL into which trace files can be uploaded, use this user option: -Dcom.sap.solutionmanager.url=<SolutionManager_URL>.

      Note: Enter options as a series of Java system property and value pairs, delimited by spaces, with this syntax:
      -DpropertyName1=value1 -DpropertyName2=value2

      For information on troubleshooting JVM settings, see SAP Mobile Server Fails to Start Due to Incorrect JVM Settings in Troubleshooting.

  5. Click Save.