Sybase Unwired Platform (SUP) 2.1.2 vs 2.1.3 Comparison – Features

Sybase continues to add more and more functionality to its Mobile Enterprise Application Platform (MEAP), Sybase Unwired Platform ( SUP), with every new ESD release. Below are some of the major differences that you can notice…

Comparison of Features SUP 2.1.2 vs. 2.1.3

SUP 2.1.2 (ESD #2) SUP 2.1.3 (ESD #3)
No support for special characters in username Special characters are support in SUP username. You can use your email ID as your username
OnlineLogin, OfflineLogin, LoginToSync are the methods used for authentication All these methods are deprecated. You need to store the username & password in the Data vault for authentication
Password policy cannot be set for data vault You can set the password policy for Data Vault
iOS object API application uses MBS for synchronization iOS Object API application uses RBS for synchronization
Does not support SSO token as credentials for Synchronization SSO token can be passed as the credentials for Synchronization

New Features added in SUP 2.1.3

  • Entity Read Operation is added to the operation type which allows you to refresh a single instance of the MBO.
  • You can now interface your native code to the HWC application by calling your native code from the java script using PhoneGap API
  • New Command line Diagnostic tool added to verify the configuration. This toll can be installed in any machine to validate the setup.

2 thoughts on “Sybase Unwired Platform (SUP) 2.1.2 vs 2.1.3 Comparison – Features”

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.