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-10577	Disable properties when modifying default synchronization listener property values In Security > Server Security > Encrypting Synchronization for Replication Payloads > Modifying Default Synchronization Listener Properties with Production Values, step 5 refers to obsolete step 9. Disregard that reference.
SMPONP-10014	Consume REST services with HTTP or HTTPS connectivity In REST SDK Components - General Description, in the Developer Guide: OData SDK, it should state that Sybase Unwired Platform REST services can be consumed with pure HTTP/HTTPS connectivity, not only HTTPS.
SMPONP-9304	REST API allows access to external non-OData services In Developer Guide: REST API Applications > Developing the Application > Accessing a Service through a Proxy URL, we clarified that you can access an OData service or an external non-OData service.
SMPONP-8687	Clarifications to Creating and Enabling Domain Logging in SCC We have updated the topic in SAP Control Center for SAP Mobile Platform. See Creating and Enabling Domain Logging.
SMPONP-7214	Correction to No Workflow Message is Sent in Troubleshooting The first four paragraphs in the Troubleshooting guide No Workflow Message is Sent for Hybrid App DCN failures should read: Following response is returned if the request is sent for a user that has no application connection registered yet. no workflow message is sent because no device is found to send the notification Explanation: Server could not find a matching application connection for the user identified in the Hybrid App DCN request. In this case, the response is similar to: {"id":"dcntest_test_001","success":false,"statusMessage": "no workflow message is sent because no device is found to send the notification","result": [{"id":"dcntest_test_data_1","success":true,"statusMessage":""}]} The other text in the topic is correct.
RTC-419	In the Provisioning Properties Reference topic, the values for autoreghint= are not updated. The autoreghint= property sets the preferred method for initial connection registration. The application defaults to the configured method as determined by the value you set. 0 – No preference. The application implementation decides what is the default method to use 1 – Default to automatic registration using password authentication 2 – Default to manual registration 3 – Default to automatic registration using a provisioned certificate from Afaria. (Afaria Certificate) 4 – Default to automatic registration using certificate from a local source preferred. (Local Certificate) When an application does not support the requested registration method, an alternative method can be used as determined by the application.
RTC-395	Documentation is missing details related to enabling DCN request logging and payload in the domain log. Workaround: The following statements related to setting up domain log profile are currently missing from the documentation: To enable general DCN, you must select an MBO package, MBO, user, or security configuration. To enable Hybrid App DCN, you must select an MBO package, user, or security configuration. Enabling options in Payload category only enables payload logging for selected sub-system. Setting payload options alone, by itself, does not enable logging. Selecting application ID, by itself, in a domain log profile does not enable DCN logging.
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 ...
N/A	CHAPTER 10 Scripting Silent Installation, Upgrade, or Uninstallation of the Installation Guide for Runtime (PDF format only) on the Getting Started CD provides instructions for performing these tasks for SAP MobileSDK, instead of SAP Mobile Platform Runtime. Refer to the corrected chapter of Installation Guide for Runtime on the Product Documentation Web site at http://sybooks.sybase.com/sybooks/sybooks.xhtml?id=1289&c=firsttab&a=0&p=categories
N/A	Exclusions for application customization resource bundles. Topics about application customization resource bundles in Mobile Application Life Cycle and SAP Control Center for SAP Mobile Platform are applicable only for clients with supporting APIs. Currently, those clients include only Online Data Proxy, Object API, and REST API clients.
N/A	SAP Control Center Windows Service Deleted The \utility folder no longer exists, so the command shown in SAP Control Center Windows Service Deleted is incorrect. The correct command is: SMP_HOME\bin\amd64 (or x86)\sccservice.exe -install This topic appears in both SAP Control Center for SAP Mobile Platform and Troubleshooting.
N/A	SAP Control Center Windows Service Fails to Start A second explanation should be added to SAP Control Center Windows Service Fails to Start: Explanation 2: The process sccservice.exe was not stopped during previous stops of SAP Control Center (even though the Windows Service "SAP Control Center x.x.x" does not show that it is running). Solution: Use Windows Task Manager to kill the process tree of sccservice.exe, then restart SAP Control Center. This topic appears in both SAP Control Center for SAP Mobile Platform and Troubleshooting.
N/A	Creating log filters. The domain log filters are divided into three groups: package-related, security-related, and application connections. If certain combinations are selected, the log filter may not generate as expected. There are important guidelines you should consider when you are creating domain log filters. See Domain Log Filter Guidelines, and the troubleshooting topic Some Domain Log Files Do Not Generate Correctly. This topic appears in System Administration and SAP Control Center for SAP Mobile Platform.
N/A	Incorrect syntax for Retrieve Application Connections API The syntax for the Retrieve Application Connections API in Developer Guide: SAP Mobile Server Runtime is incorrect. The correct syntax is: PaginationResult<ApplicationConnectionVO> getApplicationConnections(AppConnectionFilterSortVO filter, Long offset, Integer length) throws SUPAdminException
N/A	User Activation Results in Error 404 When attempting to activate a user (sometimes referred to as on-boarding), Error 404 appears instead. Error 404 may indicate that the security configuration that is specified by the X-SUP-SC and/or X-SUP-DOMAIN settings in the header, does not exist, or is incorrect. The header values must be set to a valid security configuration. See User Activation Results in Error 404. This topic will be added to Troubleshooting, in the Application and Application User Management Issues section.