Skip to Content

Getting Started with Kapsel – Appendix G — New Features


Appendix G:  New Features

The following are some of the new features to the SMP 3.0 platform since its initial release that may be of interest to Kapsel developers.

For SP09+ see
Getting Started with Kapsel – Part 1 (SP09+)

SMP 3.0 Server SP01
SMP 3.0 Server SP02
SMP 3.0 Server SP03
SMP 3.0 Server SP03 PL02
SMP 3.0 Server SP04
SMP 3.0 Server SP04 PL01
SMP 3.0 Server SP05
SMP 3.0 Server SP06

SMP 3.0 Server SP07

SMP 3.0 SDK SP01
SMP 3.0 SDK SP02
SMP 3.0 SDK SP03
SMP 3.0 SDK SP04
SMP 3.0 SDK SP05
SMP 3.0 SDK SP05 PL01

SMP 3.0 SDK SP05 PL03

SMP 3.0 SDK SP06

SMP 3.0 SDK SP07

SMP 3.0 SDK SP08

SMP 3.0 Server SP01

  • Final build dated Nov 15th, 2013.
  • Endpoints must now be specifically selected or enabled for an application.  Previously an application could use any endpoint.

    See also Using a Technical User to Connect to a Backend OData Source for an example showing how a Kapsel app can use more than one endpoint.

SMP 3.0 Server SP02

  • Final build dated Feb 18, 2014.
  • Applications can be exported and imported through the Management Cockpit.  This is intended to be used for moving applications from a test server to a production server.  Note that security profiles and registration information is not included in the exported zip.

    If the AppUpdate plugin is used, after completing the import, the Deploy button must be pushed to increment the revision.  To do this, select the newly imported app, click on App Specific Settings, New Version, Deploy. 

    The above screenshot shows the state following an import of a Kapsel app.  For the app to become available the Deploy button must be pressed which will update the revision from 1 to 2.

    Note, that the revision number on the server is incremented by one following the import/deploy.  If revision 10 of an app on a production server is exported, then the app is removed and then imported it will be at revision 1.  If the revision of the app on production server is 5 and a new version is imported on top of an existing version, its revision will be 6 following the import.

  • The shortcuts to start and stop the SMP 3.0 server from the start menu now can start and stop the server when it is running as a service.

SMP 3.0 Server SP03

  • Final build dated April 29, 2014.
  • The install can be run without having a previous installation of SMP 3.0 being present.
  • Support for running the SMP 3.0 server in a cluster.  For additional details see Cluster Installation.
  • Support for accessing the SMP 3.0 server using the Relay Server.
  • If an endpoint makes use of relative paths, they can be added a shown here. 

SMP 3.0 Server SP03 PL02

  • Final build dated July 18th, 2014.
  • Must be applied to an SMP SP03 server.
  • Adds the ability to have the backend rewrite the URL rather than the SMP server.

    When the request is made to the backend OData source or web server, a header indicating the host name and port is included.  The backend system then is responsible for rewriting the request.  An example of the header sent is shown below.


SMP 3.0 Server SP04

  • Final build dated Sept 13th, 2014.  Note this SP corresponds with the SP05 SDK.
  • Additional Cluster enhancements, proxy info is now set in the management cockpit.
  • Server ports are now configurable in the management cockpit.  The connections now have names in the default-server.xml file such as smpConnectorName=”oneWaySSL”.
  • New ability to send push notifications to all users of an application or to multiple devices based on user.  Notification Data Sent Using Push API
  • The SMP server logs are now in the List Log Format 2.0.  Some logs are now stored in a database rather than a file.

SMP 3.0 Server SP04 PL01

  • Final build dated Sept 13th, 2014.
  • This PL provides a feature vector which can be used to prevent a plugin from being called from JavaScript.  The SMP 3.0 SP04 PL01 server provides a REST API that can be used to specify which plugins cannot be called.  The Kapsel settings plugin enforces this policy and also provides an API named isFeatureEnabled that can be used before calling a plugin’s API.  For additional details see SAP Note 2064369 – Specifying mobile features to be restricted for an SAP Mobile Platform application.

SMP 3.0 Server SP05

SMP 3.0 Server SP06

  • Final build dated Feb 21, 2015.
  • Included default database is now SQL Anywhere instead of Derby

SMP 3.0 Server SP07

  • Final build dated April 18, 2015.
  • Feature Vector list is now updateable to include plugins not in the static list
  • HTTPS Listeners are configured now by default to only allow TLS 1.2.  In SP08 of the SDK, the Kapsel Logon plugin on Android cannot use TLS 1.2.  See also HTTPS Connection Problem.  This should be resolved in the SP09 SDK. 

SMP 3.0 SDK SP01

  • Final build dated Nov 8th, 2013.
  • Support for Cordova 3.1

SMP 3.0 SDK SP02

  • Final build dated Feb 14, 2014.
  • Support for Cordova 3.3
  • The below code shows the new progress event for the app update plugin.
    sap.AppUpdate.addEventListener("progress", function(e) {
        if (e.lengthComputable) {
            var percent = Math.round(e.loaded / * 100);
            //console.log("Progress " + percent);
            document.getElementById('statusLabel').innerHTML = "Download progress " + percent + "%";

    The above code is contained in the sample provided in the App Update section.  Note that for updates other than a full update, the download will be very quick since only changed files or deltas are sent.

  • The EncryptedStorage plugin now deletes its data if the Logon plugin’s data vault is deleted.  This can occur when the user clicks the Forgot Application Passcode button on the unlock screen of the Logon plugin, if the user enters too many incorrect passcodes or if the method  sap.Logon.core.deleteRegistration is called.  Previously it was not possible to delete an existing encrypted store and create a new one with the same name.  A new method is provided named deleteStore.
    store.deleteStore(successCallback, errorCallback);
  • Previously the whitelist was not respected by the Kapsel plugins such as the AuthProxy or Logon.  The whitelist is respected in SP02 by the Kapsel plugins.

SMP 3.0 SDK SP03

  • Final build dated April 29, 2014.
  • Cordova 3.4.0-0.1.3 support.
  • Android 4.4 (KitKat) support.
  • The EncryptedStorage plugin now requires the Logon plugin and uses its data vault to store the encryption keys.  It no longer requires or uses a user provided password.  Data stored in Kapsel projects is not migrated after upgrading the EncryptedStorage plugin from a prior version to SP03.
    A new method was added to the Logon plugin named initPasscodeManager to support the use case where the application does not register with an SAP Mobile Platform or Gateway server and the developer still wishes to use the Encrypted Storage plugin.  Examine the sample provided in the section Encrypted Storage for further details.
  • A new interface was added to the Logon plugin to enable it to call a native method whose implementation provides a client certificate.  Previously this was only possible using SAP Afaria.  For additional details see Using the X.509 Certificate Provider to Register using a Client Certificate.
  • The ability to skip a screen was added to the Logon Plugin.  See the section Customizing the Logon Plugin’s UI for further details.

SMP 3.0 SDK SP04

SMP 3.0 SDK SP05

SMP 3.0 SDK SP05 PL01

SMP 3.0 SDK SP05 PL03

  • Final build dated Oct 31, 2014.
  • Cordova 3.6 support
  • iOS 8 support
  • New attachment viewer plugin.
  • In the app preferences plugin, iOS settings can now be defined via JSON in the same way as Android.  The settings on iOS can be accessed from within the app.  New readonly attribute.
  • Fiori Client settings changes.  New settings (proxy, appid, reset) shown when fioriURLIsSMP is set to true.

SMP 3.0 SDK SP06

  • Final build dated Dec 19, 2014.
  • Calendar Plugin
  • Printer Plugin
  • A Usage Plugin that can be used with the HANA Cloud Platform mobile services server to collect timing information from an application.
  • Ability to replace the Android webview with Crosswalk.
  • Log viewer and email log option for SAP Fiori Client.

SMP 3.0 SDK SP07

  • Final build dated March 13, 2015.
  • Offline OData plugin support on Windows
  • Fiori Client UI changes to registration screens (configuration, set passcode, and unlock) as well as ability to provide parameters on the Fiori URL that indicates the app id and if the URL is proxied through an SMP server or to specify an email address to support Mobile Secure.  This was also included in SP06 PL02.

SMP 3.0 SDK SP08

  • Final build May 15, 2015.
  • iOS 8.3 support
  • SAP Fiori Client will be available on Windows Phone Store for Windows 8.1 and Windows 8.1 Phone.  The Fiori Client script that is included in the Kapsel SDK currently supports Android and iOS.
  • Offline OData Plugin supports Deep Inserts and Media Resources.
  • The Fiori Client contains a demo mode option that when selected loads a trial Fiori Launchpad.  The URL used is
  • The Fiori Client now includes a menu item to enable Printing of the current page.
  • In the Fiori Client, it is now possible to use an X.509 certificate provisioned from SAP Afaria without an SMP server by passing in the following URL parameter
  • Toolbar Plugin on iOS has been improved.  Previously it would pop up at the location that was double tapped (on an iPad) and contained a more button.  The toolbar now appears at the bottom of the screen.
  • New Voice Recording plugin that enables capturing of encrypted audio recordings.
  • A busy indicator has been added to the Online plugin.  It is displayed when resources (HTML, JavaScript etc.) are being loaded or can be programmatically shown and hidden.
  • The Online plugin now also attempts to provide a more detailed error pages when a network or certificate problem is detected.
  • New SAPUI5 Barcode Scanner Button.  For additional details see the Barcode Scanner section.
  • The Feature Vector is now enforced.

Back to Getting Started With Kapsel

You must be Logged on to comment or reply to a post.