An earlier article listed the new features added to SQL Anywhere 16 after its introduction (build 1324) up to and including build 16.0.0.1691.
This article lists the new features added after that, up to and including 16.0.0.1761.
1745 MobiLink Plugin support for -zup switch - for more information see 1723 MobiLink Server enhancements to LDAP authentication
1733 MobiLink Server support for Oracle 12.1
1723 MobiLink Server enhancements to LDAP authentication
1733 Oracle ODBC driver support for Oracle 12.1
1760 UltraLite support for Xcode 5 and iOS 7
1716 UltraLite support for Windows 8 and Windows Phone 8
MobiLink - Java Plugin for Sybase Central
================(Build #1745 - Engineering Case #751936)================
The MobiLink Plugin now supports:
The new MobiLink Server –zup switch. This switch can be accessed from the
Advanced tab of the property sheet for a MobiLink Server Command Line. An
error is reported if –zup is set and –zu is set to false, as this is not
allowed.
For user authentication policies we now support calling the standard MobiLink
authentication scripts: Never, Always or only when an LDAP server could not
be found. This change affects the LDAP Servers page of the New User Authentication
Policy wizard. It also affects the property sheet for user authentication
policies. The setting is also shown in the right hand pane when User Authentication
Policies are shown.
MobiLink - Synchronization Server
================(Build #1733 - Engineering Case #751199)================
The MobiLink server now supports consolidated databases running on an Oracle
12.1 server. In order to use any of these Oracle 12.1 new features: 32K-byte
varchar2, nvarchar2, raw data types, and implicit result sets, the build
numbers of the SQLA Oracle ODBC driver must be greater than or equal to 1733
and the Oracle OCI library must be installed from the Oracle 12.1 installation
image.
================(Build #1723 - Engineering Case #750296)================
Three new features/modifications have been introduced in the MobiLink server:
a) The setting for the ldap_failover_to_std property for a user authentication
policy is extended to be 0, 1, or 2 [it originally accepts only 0 (FALSE)
or 1 (TRUE)). The MobiLink server will authenticate users in the following
ways, when ldap_failover_to_std is
0: The MobiLink server will authenticate the user against LDAP server only.
If the user cannot be authenticated against a LDAP server, the MobiLink server
will fail the sync request, regardless of the types of the errors;
1: The MobiLink server will authenticate the user using the standard script-based
user authentication, if and only if the LDAP server(s) are not available.
The authentication status, 6000 will be passed to the user authentication
scripts, if the LDAP servers are not available;
2: The MobiLink server will authenticate the user against a LDAP server
first and then authenticates the user with the standard script-based user
authentication, no matter if the user is authenticated or not with the LDAP
server. The MobiLink server will pass one of the following values as a user
authentication status to the scripts:
1000: if the user is authenticated against the LDAP server;
4000: if the user is not authenticated against the LDAP
server; or
6000: if the LDAP servers are not available.
b) User authentication using a default authentication policy:
The MobiLink server now supports user authentication against a LDAP server
using a default user authentication policy. The default policy name can
be specified from the new MobiLink server command option: -zup
"set default policy name for user authentication (implies -zu+, cannot
be used with -zu-)"
When a policy name is specified on the MobiLink server command line with
this new option, any new MobiLink users that aren’t in the ml_user table
will be first authenticated against the LDAP server using this default policy,
and then optionally calls the user authentication scripts, if the ldap_failover_to_std
property for the default policy is configured with a value of 1 or 2. If
the user is fully authenticated, it will be added into the ml_user table
and the same user authentication policy will then be used to authenticate
this user later. This new command line option implies –zu+ and it cannot
be used with –zu-. The MobiLink server will complain, if both –zup and –zu-
are given on the command line.
Please note: the given default user authentication policy name must exist
in the ml_user_auth_policy table , otherwise the MobiLink server will complain
and refuses to start.
c) The MobiLink user password will be hashed and stored in the ml_user table
in the consolidated database, if and only if the ldap_failover_to_std property
is configured with a value of 1 or 2. The password will not be saved, if
this property is set to 0.
MobiLink - iAS Branded ODBC Drivers
================(Build #1733 - Engineering Case #751198)================
The SQL Anywhere Oracle ODBC driver now supports the following new features
when the database is running on an Oracle 12.1 server and the OCI library
is from the Oracle 12.1 installation:
- The maximum size of the VARCHAR2, NVARCHAR2, and RAW data types has been
increased from 4,000 to 32,767 bytes
- Implicit result sets can be returned from stored procedures. However
the number of implicit result sets is limited to one per stored procedure.
The implicit result set will be detected automatically by the ODBC driver
regardless of the setting for the “Procedure returns results or uses VARRAY
parameters” option in the DSN used by the ODBC application
When the database is running on an Oracle 12.1 server and the OCI library
is from the Oracle 12.1 installation.
UltraLite - Runtime Libraries
================(Build #1760 - Engineering Case #753086)================
UltraLite now supports Xcode 5 and iOS 7. Version 16 includes 64-bit libraries
for the new A7 (arm64) chip along with the 64-bit simulator.
================(Build #1716 - Engineering Case #750618)================
UltraLite is now supported for Windows 8 store applications and Windows Phone
8 applications.
Each bottom level directory in the following tree under the SQLA install
root contains a WinRT-based component (UltraLite.winmd/UltraLite.dll) that
implements the UltraLite API for the noted platform.
UltraLite
+-- WinRT
|-- WindowsPhone
| +-- 8.0
| +-- arm : Windows Phone 8 devices
| +-- x86 : Windows Phone 8 emulator
+-- Windows
+-- 8.0
+-- arm : Windows RT ARM-based devices
|-- x64 : Windows 8 store apps for x64 architecture
+-- x86 : Windows 8 store apps for x86 architecture
Developing UltraLite applications using this software requires SQL Anywhere
16 and Microsoft Visual Studio 2012 or later.
Developing Windows Phone applications requires the Windows Phone SDK 8.0,
which is available from:
http://dev.windowsphone.com/en-us/downloadsdk
Windows Phone SDK 8.0 requires Windows 8. Microsoft lists the complete
system requirements at:
http://www.microsoft.com/en-us/download/details.aspx?id=35471
Developing Windows store applications requires the Windows SDK for Windows
8, which is available from:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh852363.aspx
The UltraLite.WinRT directory under the SQLA samples root contains a Visual
Studio 2012 solution for the CustDb sample that appears in various forms
for other UltraLite supported platforms.
No comments:
Post a Comment