Documentation Issues and Updates for SAP Mobile Platform Runtime

Read about updates, corrections, and clarifications to the documentation released with SAP Mobile Platform Runtime.

Issue #Description
SMPONP-16215

The SAP Control Center online documentation provided with the product and the Web documentation on SAP Help Portal may be different starting with SAP Mobile Platform 2.3 SP04 and earlier. The SAP Control Center online help may contain information regarding the Resumable Synchronization feature, which is not available in SAP Mobile Platform.

For SAP Mobile Platform 2.3 SP04 PL01, the SAP Control Center Web documentation version contains the latest information.

SMPONP-16206

SAP Mobile Server fails to start if you remove the JVM option EnableDebuggingOnDemand from the SAP Control Center JVM Properties dialog.

SMPONP-16204

A warning message does not display to prevent you from running the SAP Mobile Platform Runtime 2.3 SP04 PL01 32-bit installer on a 64-bit system.

SAP Mobile Platform does not support running the 32-bit installer on a 64-bit system.

SMPONP-11422
SQL Anywhere® version 16 is included as part of SAP Mobile Platform versions 2.3 SP03 and later.

Previous releases of SAP Mobile Platform included SQL Anywhere version 12. The current documentation still contains references to SQLAnywhere12 as a product, directory path, and documentation location. These references should be SQL Anywhere 16 (product), SQLAnywhere16 (path), and http://dcx.sybase.com/index.html#sa160/en/sqlanywhere_en16/help_top_index.htm (documentation location).

SMPONP-3399
Improvement to sample test program for MBS performance testing with LoadRunner.

In System Administration, the Enabling MBS Performance Testing with LoadRunner topic provides sample test program to show how to perform load testing of MBS in SAP Mobile Platform with LoadRunner. The documentation includes the BeginOnlineLogin method in Action.cs.

An update to this content is that it is better to call BeginOnlineLogin in vuser_init.cs, rather than in Action.cs. A client application should not need to login more than once, even if the Action is to be repeated multiple times during a benchmark run.

N/A
Requirements for a computer name, used as default server or cluster name when installing SAP Mobile Server, are not listed.
The Installation Guide for Runtime, Selecting Installation Options sections of the tasks that install a new instance of SAP Mobile Server, list the requirements for a server or cluster name that you enter. However, if you do not specifically select the option to Set SAP Mobile Server name (Set SAP Mobile Server name and cluster name on first SAP Mobile Server in a cluster), the documentation does not state:
  • The installer uses the computer name by default for the server name (and cluster name on the first SAP Mobile Server in a cluster).
  • The computer name must meet the same requirements for server and cluster names as names that you enter.

The requirements for server and cluster names are documented in the Installation Guide for Runtime, in the Selecting Installation Options sections of the tasks that install a new instance of SAP Mobile Server. See the step that begins, "(Optional) If you selected Set SAP Mobile Server name ..."

If the computer name does not meet those requirements, you have two options for installing SAP Mobile Server on that system:

Workaround 1: Keep the computer name as is. In the Selecting Installation Options section of the installation task, select the option to Set SAP Mobile Server name ..., and then specify a name that meets the requirements listed in the step that follows immediately after making that selection.

Workaround 2: Before running the installer, change the computer name so that it meets all the requirements for user-entered server and cluster names. Then, in the Selecting Installation Options section of the installation task, do not select the option to Set SAP Mobile Server name ...