Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere 16 - Changes and Upgrading » What's new in version 16.0 » MobiLink behavior changes


MobiLink server changes

Following is a list of behavior changes to MobiLink servers introduced in version 16.0.

  • COMMIT always issued for successful end_synchronization scripts   The end_synchronization scripts are passed a synchronization_ok parameter to denote the state of the synchronization (0 if failed synchronization, 1 if successful). Before this change, end_synchronization scripts would be rolled back if the synchronization_ok parameter was zero. Now, if all of the end_synchronization scripts execute successfully, a COMMIT is issued regardless of the value of the synchronization_ok parameter.

    To achieve the old behavior, wrap an existing end_synchronization script body in an IF statement. For example:

    IF {ml s.synchronization_ok} = 1 THEN 
             -- existing script body here
    END IF;

  • Test MobiLink connectivity with a web browser   When using HTTP or HTTPS, with or without the Relay Server, you can use a web browser to verify MobiLink server is listening for requests. MobiLink server responds with a 404 Not Found error that also mentions the MobiLink server's major version. See MobiLink connectivity.

  • 32-bit MobiLink server is no longer supported on Linux   Only the 64-bit version of the MobiLink server is supported on Linux.

  • Windows 32-bit MobiLink server is no longer supported for some consolidated databases   The Windows 32-bit MobiLink server is not supported for the following types of consolidated databases:

    • Sybase Adaptive Server Enterprise
    • SAP HANA
    • SAP Sybase IQ
    • IBM DB2 LUW
    • MySQL

  • Columns name are now always sent during synchronization   In MobiLink, column names are now always sent during synchronization. See Send column names.