Skip to Content

SAP Mobile Platform SDK 3.0 SP08 – What is new ?

We are happy to announce the release of the latest version of the SDK for SMP and HCP Mobile Services, SMP SDK SP08.  The last version of the SDK already supports a wide range of capabilities including SAML Support, Usage collection and Offline APIs across iOS, Android (ARM), and Windows devices.  SP08 introduces a set of new features for native and hybrid development around developer experience, security & offline.

Let us start with a high level recap of the mobile SDK.

/wp-content/uploads/2015/05/sdk_705247.png

The figure above shows the different programming models that are available in the SDK (native, hybrid and agentry metadata) as well as different consumption paths (cloud, on premise) for platform services.

With every service pack release we focus on creating value in our SDK offering for the development community by addressing themes that are spread over the programming models and consumption paths. The focus themes in SDK SP08 were the following.

Native SDK

Developer Experience improvements

We took a close look at the experience of our developers and we are introducing a set of best practices in managing the SDK experience. The following are the specific improvements that will be available in SP08

  • Cocoa Pod support (IOS)– Cocoa Pods is the dependency manager for Swift and Objective-C Cocoa projects. It has thousands of libraries and can help you scale your projects elegantly. A pod spec file will be delivered as part of the sdk installer.

By running a pod install command, the xcode project with all the sdk dependencies could be easily set up.

  • Maven Support (IOS, Android) – Maven addresses two aspects of building software: First, it describes how software is built, and second, it describes its dependencies. Maven makes it easy to identify when a project has a dependency on code outside its source control folders. Developers and managers alike would prefer small, componentized builds because they allow code changes to be very quickly tested and integrated.

After installing new deploy.sh script is available under the appropriate OS folder. Through the execution of the script, all artifacts are deployed into the local Maven repository and using a pom.xml, it can be added to the xcode project

  • Gradle Support (Android) – We intend to provide more support for Gradle and android studio release-by-release. With SP08 we would start with a getting started guide for android studio based projects and the mobile sdk. We simplify the dependency management for android projects using gradle files that are added to the installation. For more details please refer to the help documentation and the following links.

Features & improvements

Media Support

  • The Online and Offline OData Stores now supports media resource handling, for example creating and downloading of image files. In previous versions of the SDK, the stores supported OData related operations (CRUD) only for OData entities, feeds, properties, links, but not for downloading (GET) of resources such as media files.


Appsettings enhancements

The new ApplicationSettings property of the LogonCore instance replaces the ConnectionData property on the RegistrationContext to access server application settings, allowing a common solution across multiple platforms and providing the following benefit:

  • Type safety of the stored settings.
  • Validity of downloaded application settings.
  • The ability of the application developer to modify settings those are writable with validation.
  • Enforcement of consistent state of application setting values on the client and server.
  • Prevention of an application developer from (intentionally or unintentionally) creating an inconsistent state by overwriting application setting values locally.

Enhanced SAML Support (iOS, Android)

Previous versions of Logon Manager supported HTTP-POST binding for getting redirected to the Identity Provider. The HTTP-REDIRECT binding is now also supported on iOS and Android. For more details on Http conversation manager and SAML redirects please refer to the following link http://scn.sap.com/community/developer-center/mobility-platform/blog/2014/11/14/request-response-challenge-filters-in-httpconversationmanager on the SAP Community Network Web site.

Hybrid SDK

Features & improvements

  • The Hybrid SDK (Kapsel) plugins now support a Voice Recording service that allows a user to record audio information using the new native audio recorder application.
  • The X.509 certificate provider interface now supports a new certificate provider library, which provides a new certificate provider interface to communicate with third-party certificate provider implementations.
  • The Offline OData plugin, which provides offline OData support to Cordova applications, now provides support for offline media elements.
  • The Online plugin has been enhanced to provide busy indicator support when a page starts loading from the server.
  • The Application Preferences plugin, Usage plugin, and Toolbar plugin are now supported for use in applications on the Windows 8.1 and Windows Phone 8.1 platforms, in addition to Android and iOS.

Agentry

Agentry Toolkit (64-bit only)

The Agentry Toolkit, which provides the components to create Agentry applications, is available in 64-bit format. The 32-bit version is no longer supported, or available for download. Links to the 32-bit download site have been removed from the documentation.

Agentry Client Changes

The screen-background feature is now available for the Agentry WPF client. (It was previously available only for Agentry Android, iOS, and legacy clients). This feature enables you to change the Screen Background Image, making it easier to distinguish between read-only, editable, and disabled fields on both transaction and non-transaction screens.

Password Validation Audits for Agentry Applications

Password validation audits are supported for Agentry applications using SQL and Java back-end connections. The developer must enable password validation in the application definition. A new script file provides a template for handling password validation audit records. When the user performs a password-related action, an encrypted password validation audit record is created on the client device. The encrypted audit record is sent to the server. Once the server receives the record, the server sends confirmation to the client, and the client deletes the encrypted audit record.

Agentry Publication Changes

Clusters were introduced in 3.0 SP03, which changed how application and server configuration is managed in SAP Mobile Platform. Configuration values are now stored in the SAP Mobile Platform data store, and available to all server nodes. For Agentry, this means the Agentry.ini functionality is no longer needed in production.

When you publish an Agentry application in the cockpit, configuration values are added to the data store, and distributed to all server nodes. When you upload an updated version of an Agentry application, the configuration values are updated in the data store, and distributed to all server nodes.

To report this post you need to login first.

18 Comments

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

      1. Michael Appleby

        Hi Midhun,

        I tried to get it into the right community as soon after it was posted as I could so that would not happen.  The urls do change for blogs, but I had thought that there was a fix in place as others had been moved without impact.  My apologies for causing any problems.  This is the main reason why blogs more difficult to deal with than SCN Documents or Discussions.  They are tied tightly to the original community in which they are created.  Documents and Discussions are only loosely tied.  Their urls do not change after being moved from one community to another.

        Regards, Mike (Moderator)

        (0) 
        1. Midhun VP

          No worries Mike.

          I think this is something to be managed by SCN. Something like maintaining both the URLs. That solves this problem.

          Regards, Midhun

          (0) 
  1. Sivakumar V

    Hi Kiran,

    Very interesting set of features and appreciate the pace of innovation and releases.  One question which I have been trying to get an answer from various quarters in SAP to support our customers, is the way in which changes to Agentry.ini (formerly) and now the Management cockpit configuration for Agentry apps be transported across systems.  In the standard documentation, it is said not to package Agentry.ini file within the deployment archive when moving publishing the application to Production systems.  And now you have said “Configuration values are now stored in the SAP Mobile Platform data store”.  So in a customer landscape how can we transport the configurations from SMP data store of SMP development server to SMP production server.  Appreciate if you can throw some light on this

    Best Regards

    Siva

    (0) 
    1. Karl Stevens

      Hi Siva,

      One strategy is to have three different instances of your Agentry application.

      1. Agentry in development mode on an SMP Development server
      2. Agentry in production mode on an SMP Development server
      3. Agentry in production mode on an SMP Production server

      Development occurs in instance number 1.

      QA testing (or pre-production staging) occurs in instance number 2.  This can be configured to be the same as your production environment.  Once satisfied with the functionality, the application is exported via the Management Cockpit.

      Production system is in instance number 3.  The export from instance number 2 would be imported via the Management Cockpit.

      Hope that helps.

      Karl

      (0) 
      1. Jens Schwendemann

        Hi Midhun,

        we are not (yet) entitled for SMP SDK in Service Marketplace (can’t see it under Installations & Upgrades –> A-Z –> M). Is there any chance that we’ll see the SDK via the SAP Store?

        I’d like to authenticate a Fiori client with user certificates to our FES. We don’t have SMP or Afaria but do have MobileIron. Hence I’m looking if the new certificate provider interface that doesn’t enforce Afaria and SMP would help in that.

        Many thanks and kind regards

        Jens

        (0) 
  2. Frankie Fan

    Hello Kiran,

    Do you know how to obtain the user name after onboarding to HCPms using kapsel logon plugin by SAML? Could you give me some advice?

    Thanks for your reply.

    Regards,

    Frankie.

    (0) 
      1. Frankie Fan

        Thanks for your reply, Kiran.

        Before asking you, I have asked this problem to Daniel(the author of the blog you have proposed), he told me that SAML cannot return the user name to client.

        (0) 
  3. Raja Poranki

    Kiran,

    Does SMP offer SAML for SSO for Agentry based applications, for instance Sales Manager (agentry app) deployed on SMP 3.0 SP7 ? Sorry If missed reading all the content if this was mentioned. Do we have to still rely on SAP portal for SSO with JAAS  custom login module ? Any guidance would be highly appreciated.

    Thanks,

    Raja

    (0) 
    1. Bill Froelich

      Raja,

      The Agentry client does not yet support SAML for SSO.  The Agentry client currently still requires a username and password to be entered but then has options for authentication through the use of the Open Auth (part of the Open UI Framework) in conjunction with the SMP3 authentication mechanisms.

      Regarding needing the Portal, as I understand it Agentry should be able to take advantage of the new option in SP08 so portal wouldn’t be needed but I have not have time to fully investigate and test yet myself.

      –Bill

      (0) 
      1. Narasimha Chundi

        Hello Bill,

        We are using the WorkManager 6.1 agentry app connecting to SAP ECC. We have set up the SMP3.0 for SAML based authentication with ADFS. I have included the Authentication in the App for SAML based authentication. However, we are seeing that this configuration is not woven. We need help in getting this configuration working. Can you please help?

        Warm Regards

        Narasimha

        (0) 
        1. Jitendra Kansal

          Narasimha Chundi

          Please create a new Discussion marked as a Question.  The Comments section of a Blog (or Document) is not the right vehicle for asking questions as the results are not easily searchable.  Once your issue is solved, a Discussion with the solution (and marked with Correct Answer) makes the results visible to others experiencing a similar problem.  If a blog or document is related, put in a link.

          NOTE: Getting the link is easy enough for both the author and Blog.  Simply MouseOver the item, Right Click, and select Copy Shortcut.  Paste it into your Discussion.  You can also click on the url after pasting.  Click on the A to expand the options and select T (on the right) to Auto-Title the url.

          Regards,

          JK (Moderator)

          (0) 

Leave a Reply