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

SQL Anywhere 17 » SQL Anywhere - Changes and Upgrading

What's new in MobiLink version 17.0

MobiLink version 17.0 introduces several new, changed, deprecated, or removed features.

Deprecated features will be removed in future versions. Alter your applications to use recommended feature replacements instead of relying on deprecated features.

Note

Check the readme.txt file for additional information about the software, including feature information that was added after the documentation was completed.

MobiLink server
  • Support for SAP IQ

    The MobiLink server now supports consolidated databases running on SAP IQ 16.0 and higher servers.

    Note This enhancement was first released in a version 16 Support Package.
  • Support for Oracle 12.1 consolidated databases

    The MobiLink server now supports Oracle 12.1 consolidated databases. To take advantage of Oracle 12.1 features with SQL Anywhere 17, the SQL Anywhere - Oracle ODBC driver must be greater than or equal to build number 1733 and the Oracle OCI library must be installed from the Oracle 12.1 installation image.

    To take advantage of Oracle 12.1 features with SQL Anywhere 17, the SQL Anywhere - Oracle ODBC driver must be greater than or equal to build number 2087 and the Oracle OCI library must be installed from the Oracle 12.1 installation image.

  • Support for SAP ASE 16.0 consolidated databases

    The MobiLink server now supports SAP ASE 16.0 consolidated databases.

  • Support for Microsoft SQL Server 2014 consolidated databases

    The MobiLink server now supports Microsoft SQL Server 2014 consolidated databases.

  • Support for MySQL 5.6.20 consolidated databases

    The MobiLink server now supports MySQL 5.6.20 consolidated databases.

  • Support for IBM DB2 10.5 consolidated databases

    The MobiLink server now supports IBM DB2 10.5 consolidated databases.

  • Changes to MobiLink support for LDAP authentication
    The following changes have been made to the way MobiLink supports LDAP user authentication:
    • Settings for the ldap_failover_to_std parameter of the ml_add_user_auth_policy system procedure have been extended to be 0, 1, or 2. See ml_add_user_auth_policy system procedure.
    • The -zup MobiLink server option allows you to specify a default authentication policy name for user authentication against an LDAP server. See -zup option.
    • The MobiLink user password is only hashed and stored in the ml_user table in the consolidated database if the ldap_failover_to_std parameter is configured with a value of 1 or 2. The password is not saved if this parameter is set to 0. See ml_add_user_auth_policy system procedure.
MobiLink clients
  • New options for restartable download

    Use the -kpd dbmlsync option or the KeepPartialDownload synchronization profile option to save information that is required to allow a failed download to be restarted. In previous releases, when a download failed, dbmlsync always attempted to save the information required to restart a download. Now, when a download fails, dbmlsync only attempts to save the information required to restart the download if either the -kpd dbmlsync option or the KeepPartialDownload synchronization profile option is specified. See -kpd dbmlsync option, and KeepPartialDownload synchronization profile option.

  • dbmlsync provides the ability to restart downloads when no bytes of data have been received The dbmlsync utility now allows you to restart a failed download even if no bytes of the download have been received. Previously a download could only be restarted if at least one byte had been received. See MobiLink client utility (dbmlsync) syntax.
    Note This enhancement was first released in a version 16 Support Package.
  • dbmlsync offline transaction log retrieval has been extended

    The dbmlsync utility can now retrieve offline transaction logs from the SQL Anywhere database server instead of accessing them directly. If offline transaction logs are required but the given offline transaction log directory cannot be opened or it does not contain offline transaction log files, then dbmlsync retrieves the offline transaction logs through the database server. The following restrictions apply:

    • The user ID that is used by dbmlsync to connect to the synchronization database must have the READ FILE and WRITE FILE privileges and all the offline transaction log files must be in the online transaction log directory.
    • The SQL Anywhere database server must have Support Package build number 1691 or later to support this feature.

    There is a slight performance penalty when using this feature because the database server must do more work to retrieve the pages. If performance is critical, then using the dbmlsync OfflineDirectory extended option may be best for your deployment. See MobiLink client utility (dbmlsync) syntax.

    Note This enhancement was first released in a version 16 Support Package.
  • Improved authentication

    When making a TLS or HTTPS connection, if none of the certificate_name, certificate_company, or certificate_unit protocol options are set, then the host name of the database server is verified against the host name of the database server certificate. To prevent this host name check, set the new skip_certificate_name_check protocol option to ON when connecting with TLS or HTTPS. See skip_certificate_name_check protocol option.

  • New skip_certificate_name_check protocol option

    Use the skip_certificate_name_check protocol option to control whether the client library skips the check of the server host name against the database server certificate host names. See skip_certificate_name_check protocol option.

  • New allow_expired_certs MobiLink client network protocol option

    Use the allow_expired_certs protocol option to accept a server certificate that has either expired or is not yet valid and continue with the synchronization. See allow_expired_certs MobiLink client network protocol option.

MobiLink plug-in for SQL Central
  • Test Window Configuration window is now configurable

    Use the Test Window Configuration window to configure some of the options used for testing a synchronization model, enabling more complete testing of your synchronization logic and creating an environment closer to that of your production environment. See Configuring synchronization model testing.

  • Assign a user authentication policy to multiple users

    You can now assign a user authentication policy to multiple users at the same time. See Assigning a user authentication policy to multiple users.

  • Synchronization models can be duplicated The Synchronization Models menu in the MobiLink plug-in has a new option to duplicate a synchronization model. See Synchronization models.
    Note This enhancement was first released in a version 16 Support Package.
  • Changes to MobiLink plug-in support for LDAP authentication
    The following changes have been made to the way MobiLink plug-in supports LDAP user authentication:
    • The MobiLink plug-in now supports calling the standard MobiLink authentication scripts for LDAP authentication. You can specify Never, Always or If LDAP server unavailable for LDAP authentication on the LDAP Servers page of the New User Authentication Policy Wizard and on the General tab of the Authentication Policy Properties window.
    • The -zup MobiLink server option is supported. The -zup option allows you to specify a default authentication policy name for user authentication against an LDAP server. This option can be accessed from the Advanced tab of the Server Command Line Properties window. See -zup option.
  • Enhancement to Oracle support

    The dbmlsrv17 -dt option now supports Oracle consolidated databases.See -dt mlsrv17 option.

MobiLink behavior changes, deprecated features, and features that are no longer supported
  • Support for -cmax, -cmin, and -vk options has been removed from the MobiLink plug-in

    The Server command-line properties Line no longer supports the -cmax, -cmin, and -vk MobiLink server options. If an existing command line with one of these options is loaded, these options are removed.

  • Support for SAP HANA consolidated databases

    Previous releases of MobiLink supported SAP HANA consolidated databases. Now, to synchronize SQL Anywhere clients with an SAP HANA consolidated database, use SAP HANA remote data sync. All features except for server-initiated synchronization and the arbiter are supported (the HANA Platform has its own tools for high availability).

  • MobiLink server API package names have changed
    The package name for the MobiLink server Java API has been changed to:
    com.sap.ml.script
    The package name for the MobiLink server .NET API has been changed to:
    Sap.MobiLink.Script
  • mlrsa_tls17.dll and mlrsa_tls_fips17.dll have been replaced

    The MobiLink server no longer uses mlrsa_tls17.dll or mlrsa_tls_fips17.dll. Instead it uses dbrsa17.dll or dbfips17.dll See Windows 64-bit applications.

  • Support for -cmax, -cmin, -cm, and -vk MobiLink server options has been removed

    The MobiLink server no longer supports the -cmax, -cmin, -cm, and -vk options. They are ignored if specified.

  • MobiLink and UltraLite no longer support the Microsoft ActiveSync provider

    The Microsoft ActiveSync utility is not supported for MobiLink or UltraLite.

  • The -oe option has been removed

    The -oe option of the mlsrv17 -x option is no longer supported.

  • Integrated Outbound Enabler support removed The Integrated Outbound Enabler for MobiLink has been removed. You can no longer use the -x oe option with mlsrv17. Use the normal, standalone Relay Server Outbound Enabler instead.
  • User authentication classes for POP3 and MAPI have been removed
    The following convenience classes for MobiLink user authentication via POP3 and MAPI have been removed:
    • ianywhere.ml.authentication.IMAP

      ianywhere.ml.authentication.POP3

    These classes appeared in authenticate_user event scripts that were generated by using the MobiLink plug-in in SQL Central. If your MobiLink model includes such generated authenticate_user event scripts, then you must replace them with manually created authenticate_user event scripts. The generated authenticate_user event scripts are automatically deleted when you open your MobiLink model in SQL Central.