Documentation Issues and Updates for SAP Mobile Platform Runtime

Applies to: Mobile Data Models: Using Mobile Business Objects > Datatype Support > Datatype Default Values and Limitations > Remote Operation Default Value Precedence.

In step 1.b, the documentation should specify that the structure wrapper node behavior moves the original default values at the wrapper level to the structure fields of its single child structure node if its single child structure does not have a default value and if the project was created in a version of SUP earlier than 2.2.

The SQL Anywhere database servers and the SAP Mobile Server can recover if the database connections between the SAP Mobile Server and the SMP database servers (defaultdb, clusterdb, monitordb) break due to a temporary network outage or other issue.

1. For all the startup command line options to start the SQL Anywhere database servers, set a non-zero value for the "-ti" option, for example:

   -ti5

   This setting ensures that SQL Anywhere automatically closes any connections into the database server that remain idle for more than 5 minutes. That releases row, table, and database locks that would otherwise be held by those connections.

   It is not recommended to set the timeout value less than 2 minutes, and it may need to be larger than 5 minutes if the longest duration of remote database synchronization is over 5 minutes (or else the closing of idle connections may cause one or more user's sync sessions to fail).

2. The "pingConnections" Data Source property (shown as "Ping Connections" in SAP Control Center) for each data source must be set to true. For clusterdb, you cannot do this in SAP Control Center; you must edit the properties file, for example:

   C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource\clusterdb.properties

   Make that change on each SAP Mobile Server host.
3. The "maxIdleTime" Data Source property (shown as "Max Idle Time" in SCC) for each data source SHOULD be set to 60. For clusterdb, this cannot currently be done using SCC, so can only be done by editing the properties file, for example:

   C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource\clusterdb.properties

   Make that change on each SAP Mobile Server host.

This information was omitted from the New Platform Features topic of the New Features Guide.

In Security, the Enabling HTTPS with Mutual Certificate Authentication topic states that all client types support mutual certificate authentication. Only Object API, Hybrid Web Container, and OData native clients support mutual authentication. Agentry applications do not support mutual authentication.

In System Administration, the Relay Server Configuration (rs.config) topic describes the contents of the Relay Server configuration file. In the backend farm section of the file, there is an additional property:

• socket_level_affinity – Specifies whether socket level affinity is required or not.
  Possible values are:

  • yes
  • no

  Default is yes.
  Note: For REST API applications (including those running inside Hybrid Web Container, socket_level_affinity should be set to no). 

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).

In System Administration, two topics in the documentation for backup disaster recovery omit a step for updating property values in the cluster database manually. The affected topics are:

• Rebuilding a New Data Tier Host Node
• Failing Over to a Standby Disaster Recovery Environment

Perform the following step after the step where you are instructed to run change-datatier.bat:

Step: Using dbisqlc, connect to the cluster database.

• Update installation_info by setting "host_name"='<new_hostname>', where "host_name"='<old_hostname>'
• Update installation_history by setting "host_name"='<new_hostname>' where "host_name"='<old_hostname>'

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.

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 ...