1 2 3 72 Previous Next

SAP for Mobile

1,068 Posts


SAP TechEd was held last week in Berlin; a great technology event in the midst of a city celebrating the 25th anniversary of the Berlin wall coming down. I was lucky enough to arrive early enough to have a few hours to explore the city and soak in the historic celebration. Berlin was a fantastic city to host this year’s event, and the powerful 9km long trail of 8000 balloons and hundreds of thousands of visitors made it even more incredible. It amazes me how far we have come in only 25 years. A quick stop at CheckPoint Charlie, the Brandenburg Gate and Alexanderplatz gave me a good dose of perspective to start the busy week.


My week in Berlin was very memorable for many reasons, here are a few of my personal highlights.

Berlin-balloons.jpg


Mobile Secure Featured in the Keynote demo

The Mobile Secure team was again highlighted in the keynote demo as Bjorn Goerke demonstrated the SAP Mobile Secure Fiori Build Service. His story resonated with many attendees who are eager to find ways to simplify the deployment of mobile apps, in this case an SAP Fiori  app that was customized, configured, (could be wrapped) and then published to Mobile Place in a matter of 3 or 4 minutes (without coding!). The solution, set to be released by the end of the year, drew a lot of attention as SAP Mobile Secure helps simplify Fiori rollouts. The full demo can be watched here.


 

Customer perspectives

From many conversations on the show floor, I realized that every customer’s journey to mobilize their business vary widely. A large number of customers (almost everyone I talked to) are evaluating SAP Fiori and have a strong interest in simplification both at the application and connectivity level. The importance of the story we have been sharing for the past few months became abundantly clear: Mobile security today is no longer about strictly controlling access to corporate systems and enforcing policies at the device level. Instead it is about ensuring mobile apps are delivered to users in a simple way.


booth.jpeg

The Mobile team: Holger Gauss, Martijn Tielen, Britt Womelsdorf, Dennis Richards, Milja Gillespie and Jim Jaquet.


Talking with the Roaming Reporter

A short video interview with Senthil Krishnapillai summarizes many of the conversations and the importance of simplicity for IT and end users. Simplicity is a key theme going forward and was demonstrated with the recent launch of Mobile Place, our multi-channel enterprise app store, the Mobile Secure Fiori Build Service as well as the work we do with Mocana to simplify the connectivity experience to back end systems.


Customer Roundtable Featuring Colgate-Palmolive

One of the highlights for me was a fantastic roundtable discussion with Jason Russo of Colgate-Palmolive. Jason shared Colgate’s mobile journey – specifically the successful rollout of SAP Mobile App Protection by Mocana and Mocana Atlas to secure and drive employee usage of the company’s 50 mobile apps. His story highlighted the incredible things that can result from co-innovation. You certainly can’t beat having been in the room for this engaging discussion, but if you want to catch the highlights you can listen to Colgate’s case study on our recent webinar here. The best part for me was recognizing that all of the customers in the room are facing very similar challenges - they're deploying SAP Fiori UX and want to simplify the connectivity experience. A challenge that SAP Mobile App Protection can help to solve.


Cocktail Reception at the Pan Am Lounge

 

panam.jpeg

IMG_8080.jpeg

The most interesting corporate event that I’ve ever attended was a cocktail reception hosted by our partner Mocana at the Pam Am Lounge. The venue itself is worth commenting on. This was an apartment building that was the “home away from home” for Pam Am flight attendants and pilots in the 60s and 70s. “Stewardesses” served cocktails in original uniforms and the apartment sparkled in its original décor. We enjoyed a fantastic turnout of customers eager to continue their conversations from the conference and roundtable.  

 

Most conversations were based on the activity SAP and Mocana have been working on as we jointly deliver a solution to elegantly mobilize SAP Business Suite via SAP Fiori UX. Just before the conference, Mocana announced how SAP Mobile App Protection pairs with Mocana Atlas. I also wrote a separate blog about it here. Both SAP and Mocana were recently featured in a Gartner report that showcases a customer implementation of this solution. The report will be available from SAP soon.


Overall the conference was a fantastic event full of great conversations, demos, history and more. If you missed it we'll hope to see you next year!

 


Offer simplicity for your Fiori mobile users without sacrificing the security for your company!


With the latest support package (SP04) for SAP Single Sign-On 2.0, released on Nov. 03, 2014, SAP offersMobile Single Sign-On solution – a straightforward authentication mechanism to favorite applications and trusted websites on mobile devices.

Mobile SSO solution is based on the Time-based One-Time Password (TOTP) Algorithm of the open standard RFC 6238. This algorithm computes a one-time passcode from a shared secret key and a current time.

The server side of the TOTP implementation is an add-on module for SAP NetWeaver Application Server (AS) Java and it is part of the SAP Single Sign-On 2.0 product.

SAP Authenticator is the mobile application for the TOTP Client and it is available for iOS and Android platforms.

Once the solution is implemented, Fiori users will be able to use Fiori applications on their devices after a single click on a bookmark.

Fiori.png

For more details about the solution and a step-by-step guide, how to enable mobile single sign-on for SAP Fiori using the SAML 2.0 Identity Provider and One-Time Password Authentication mechanism, see:

Mobile Single Sign-On for SAP Fiori - Step-by-Step Guide

As a new customer to the Mobile Secure cloud, or as a partner helping newbie customers you may want to rely on best practices for on-boarding. The SAP Mobile Secure rapid-deployment solution may cover your most pressing needs even now. For starting in the cloud, we cut through the clutter for you, and provide you with some simple steps to follow right here.

 

Download the package, access the files that matter to the cloud scenario, and get going:

 

1) To get to the RDS package, go to service.sap.com/rds-mobilesecure. If you like, click all the links your interested in, but most importantly, download the package with the big orange button that reads "Download package".


1.png

2)  Open the zip file, and in the zip file open the folder with_Afaria at the end: ” RDS_AFARIA_IMPL_AFARIA70_Afaria”.

2.png

 

3) Use the files with numbers X90-X94 covering the following business processes:

 

X90

Device Provisioning

X91

Device Configuration

X92

Device Application Onboarding

X93

Device Asset Tracking

X94

Device Operation

 

3.png   

The PowerPoint documents show overviews of the respective business processes, the Word documents explain how to configure them, point out best practices, and guide you through tests verifying your configuration actually works as you intended.

 

3) At the beginning of your configuration project, you may want to have business questions clarified, e.g. about the scope or the device types used, or BYOD. All these questions are combined in a comprehensive scoping questionnaire. To access the questionnaire, go one level back up in the zip file, open folder ”RDS”, and use file RDS_AFARIA_IMPL_AFARIA70_Scope_Q_EN_XX.xls.

 

4.png

4) Get your instance in the cloud following the Try or Buy Mobile Secure On-boarding Guide.


5) For connecting your Mobile Secure cloud instance with your on premise Active Directory or LDAP, and Certificate Authority, access help.sap.com/afaria-cloud, and scroll down to document ” Enterprise Access Installation Instsructions” [pardon the typo].

 

5.png


We are happy to take your suggestions and make our configuration documentation even easier. Let me know how it works for you. 


My co-founder Ole-André Haugen recently published a blog about the new Neptune GUI Client and our enhanced HTML5 powered editor. I will look into some other features in our new 3.0 release of the Neptune Application Designer.


For those of you attending TechEd && d-code in Berlin the Neptune staff there will gladly demonstrate and give you some on-site training if interested.

 

A great benefit for ABAP Add-on’s is that the software is running directly on the SAP core systems. This gives direct access to data and functionality, but also roles and authorizations. Instead of replicating users and roles, the existing setup that SAP customers have invested heavily in is reused.


This fact was the inspiration of Neptune Application Management (NAM) and Neptune Application Catalog (NAC), which we ship with our new 3.0 release.


Our previous Phonegap export and AppCache configuration, is integrated in the new solution and ported to UI5 running in the SAPGUI.


 

Neptune Application Management

 

NAM allows transformation of web applications to hybrid apps and managing them throughout their life-cycle - from application build, access, distribution, tracking and analyzing their usage.


Administrators can easily host and manage Neptune mobile and desktop applications in a cost efficient and secure way, delivering applications seamlessly on phone, tablet and desktop.

 

Below is an overview of the administration console, which is the central point for managing Neptune applications.

new.png


 

After creating web applications in the Neptune Application Designer, you want to distribute them to end-users and possibly create mobile apps and make these available through an enterprise store.


You also want to restrict access to the various apps and menu items - this is what the new management tool facilitates.


To provide user groups access to applications in the most convenient way NAM makes use of Bundle Applications. Bundle Applications group applications together based on policies related to the end-users SAP authorization roles.


2.png

 

The first thing to do in NAM is creating a bundle application. You can also use any previously made application as a template, something that is very handy if you have the same security setup and icons.


3.png

The traditional concept of an app was that it should have a limited set of functionality and preferable just cover a single process. This is still true in the consumer market, but these design guidelines have not proven successful in the enterprise space.


An obvious reason for this is simply the authentication and security requirements. You do not wish to log on for every single process. In addition working with enterprise applications is quite different than say - checking the weather for tomorrow. The consumerization of IT trend is a hot topic these days, but in some areas enterprise software needs to find its own path. Today the enterprise applications tend to provide a mobile portal experience as opposed to a single app and process functionallity.


Here is an example of how a Neptune bundle app can look with the UI5 framework on a phone with menus shown as tiles or as a list view. The second image in this example is set up as a sub-menu.

Skjermbilde.PNG


After creating you bundle app you can choose to run it with a user role based menu or directly just run a single app. Also you can choose if you want to create this application just as a web app, as a hybrid mobile application or both.


4.png


The next step is to choose the authentication settings. You can choose from a standard backend connection, authentication through the enterprise portal or logging on through the SAP Mobile Platform.


The last option will also take care of the onboarding and captcha code processes. We also added a two factor authentication using the email connected to the user in the backend system that requires the user to activate his device to be able to log on.

5.png

You now also have a choice to add a pin code authentication that will provide a simple and secure way for the end-user to log on to the system after the first successful on-boarding. In the example below, a two-factor authentication where the physical device needs to be activated is shown.


6.PNG


We also added a choice to automatically encrypt your local data base and now the packaging tool will automatically add a SQLite database instead of the standard web DB.


This provides you with near unlimited storage space for the app and also the option to have it encrypt the data automatically.


7.png


Choose settings for your app like preferences, permissions, plugins and media files for icons and splash screens.


8.png


9.png


You are now ready to build the hybrid app and you can do this for Phonegap/Cordova and we also added Windows 8.x and Windows Phone 8.1 support.


We see a growing popularity for Windows 8.1 devices in the market and specifically the Surface and HP tablets that replace the traditional laptops for managers.


10.png

 

The major advantage of this solution compared to others, as we see it, is the usage of your SAP roles. Setting up policies and attaching them to your Menu Items will both show the user only the navigation he is authorized for and also directly protect the app. So even if you manage to find the url to an application you will not be able to access it without the correct roles.



11.png


The solution is client specific so you need to set up your role based menus per SAP client.  The effects are instant for the end users and new processes can be added on the fly so it is very rare that you need to publish a new bundle app and thus seldom that the end-users need to update their app. 


12.png


Neptune Application Catalog

 

When you have created your app you can publish it to the Neptune Application Catalog which will function as an enterprise app store. You can of course use the official app stores, SAP’s Mobile Place or solutions from other vendors such as XenApp, Air Watch or Mobile Iron.

 

If you set the published option to “yes” the bundle application will be visible in the catalog.


13.png


You can also add end-user documentation and contact information for the application owner and a feedback functionality enabling the user to get help.


14.png


When you upload the installation files for the different devices the user will be able to install these from the catalog which automatically detects the type of device.


15.png


For the end-user it will look like this:


16.png


For the complete NAM documentation you can find it here.


You can also download and test NAD 3.0 with this new NAM feature here.


And again, we hope those of you going to TechEd && d-code in Berlin pass by our booth for a live demonstration.


Offer simplicity for your mobile users without sacrificing the security for your company!


With the latest support package (SP04) for SAP Single Sign-On 2.0, released on Nov. 03, 2014, SAP offers “Mobile Single Sign-On” solution – a straightforward authentication mechanism to favorite applications and trusted websites on mobile devices.


Your mobile users will have only one password to remember, less typing of complicated UserIDs/Passwords and more time for actual work!

Your company will have stronger security and more simplicity for all business processes enabled for mobile access!


The solution is based on Time-based One Time Password (TOTP) Algorithm of the open standard RFC 6238.

The server side of the TOTP implementation is an add-on module for SAP NetWeaver Application Server (AS) Java.

SAP Authenticator is the mobile application for the TOTP Client and it is available for iOS and Android platforms.


For more information, check out my blog: Simple and Secure Mobile Single Sign-On with SAP Authenticator



As a veteran of many Sybase Unwired and SAP Mobility platform implementations using Mobile Business Objects or MBOs I am frequently faced with the question of whether to use MBOs or not for new projects. While my knee jerk reaction is a resounding no, the answer is a bit more complex than that. So let's explore it a bit more:

Why default to a no?

This is the easiest part of the answer to justify, it's because MBOs as a technology are not being developed by SAP any more. As of version 2.3 of the SAP Mobility Platform (SMP) the MBO runtime is end of life meaning that although supported for the moment, there will be no more updates with new functionality such as new mobile OS platforms. A great example is that the runtime currently does not support iOS 8 which currently makes up > 52% of the iOS install base.

However this doesn't mean that you can't use then as SMP version 3 supports the MBO runtime on the server no problem and the majority of MBO apps should run fine on that technology. But the technology in use to run the MBO component is literally copied from version 2.3 and runs as a sidecar on the server as opposed to being integrated with the newer aspects of the server.


Where would you use MBOs


There are still some times where MBOs are still worth using and they fall under two categories for me:

  • An existing MBO based mobile implementation on specific OS platforms that work perfectly today.
    • Depending on the app type, usage and business worth it may be more prudent to stay where you are
    • Although if that solution is planned to continue into the future on new platforms then an alternative should be explored to replace the MBO aspects of the application.
  • Platform specific implementations such as earlier blackberry or windows mobile applications on rugged devices which are still used in certain environments

 

Although I have listed two scenarios here where I would consider MBOs it is clear that any new implementation or any planned upgrade of an existing app should seriously consider changing the data synchronisation mechanism to some of the newer more device-agnostic methods.


What are the alternatives?

If we stick with the SAP Mobility platform then we are left with a clear migration path and that is of course to OData. OData is a open data web standard originally developed by Microsoft. It is a light-weight, self-describing and RESTful protocol. For a great overview of the standard check out this video or the OData website here.


OData is now natively supported by SAP systems with SAP Gateway installed or with NetWeaver 7.4 it is a standard built-in component. But on top of that, the newest version of the SAP Mobility Platform V3.0 has a neat component called "integration gateway" not to be confused with "SAP Gateway" which is an ABAP component. Integration gateway allows SMP to consume data from a variety of sources like SOAP, SAP, OData, ODBC and REST in general and turns the data (with some modelling help) into oData services that can be consumed through SMP.


All of this combined with SAP's end-user strategy points to a utopian world of oData everywhere. With SAP servers, Fiori and SMP all speaking oData for data access and communication it seems like a no-brainer right now that we should move the same way for our mobile apps. Not least because that leaves us worrying less about proprietary SDKs like MBOs and more about creating amazing experiences that our users will love!


So for me the answer is clear - give MBOs a REST and move to oData unless you have a clear reason not to!

SMP Environments:

 

Hi all,

 

This is my first post, and I am going to share some tips I hope it will be very useful for all who have to decide how to install the SMP in the different environments (Dev, QA and Prod).

Recently, I've been involved in an agentry project and I want to share with you some interesting tips about the different possibilities available to build an Agentry application on top of the SMP 3.0. I am going to focus this article on the development environment.

If you have the possibility to read the official SMP manual: "Introduction to SMP Mobile Platform 3.0" you wiill find there are two possible options to select when working in the SMP development environment: the Single and the Multi-User environments.

 

Single User Environment

If you decide to use this environment, each developer will need to install the SMP in each machine. Also, the agentry app will be needed to be configured in each machine.

In case there are several developers participating in the same project using this landscape option, it wil cause to have different versions of the same app.

Single User.jpg                

Multi-User Environment

 

In this option, the SAP Mobile Platform is installed is just installed in one server. Also, the agentry app will be installed in just one server.

In case there are several developers participating in the project, when one of them would like to test his local version of the app, he will have to deploy it in the SMP shared server. This can cause some difficulties when trying to consolidate all the different versions, each different developer has in his machine.

Multi User.jpg

Hybrid Single / Multi User Environments

 

Now, I am going to talk about what in my opinion is the best option of SMP development environment. I will call it "Hybrid Single / Multi User Environment".

This environment consist in installing SMP in each machine for each developer, but also have a shared SMP server to be able to test the integration of all the changes that are performed by each developer to the app. If the shared SMP server is not installed, then developers should find some way to integrate their code with other's developer code, without affecting the whole app behaviour. This sounds like a really hard task.

The reason of having an SMP local installation in each developer machine, is to be able to perform unitary testing. This can be done as long as each developer is capable of connecting their own SMP instance to the customer’s backend. In case it is not possible to connect the developers machine to the SAP backend (customer security restriction), then you could handle a single development instance. Nevetheless, developers should be able to publish their software changes to the shared server and this would require a shared folder on the server.

 

Another important thing of this environment, is that you have the possibility to install an SVN server in the SMP shared development server, to control the modifications that are made by the different developers in the Java code of the application.

This is a very useful tool when working in large agentry implementations. This installation is needed because the SAP Netweaver doesn't have a built-in a java code SVN (the only one I know about is the (DTR - Design Time Repository, but I think it is not good to mix the mobile app deployment with the desktop app deployment) as it have the ABAP SVN.

Some advantadges of using an SVN tool are: code sharing, versioning, etc.

 

environment.jpg

QA and Production environment

 

Generally, when an SMP project is implemented, it is installed in QA a very simple environment compared with the one that is installed n Production.

It’s highly recommended to have a silimar environment on QA and on Production, in order to be able to recreate any error that may surge in the Production environment. For example, if I had a clustered environment in Production, it's highly recommended to have a clustered environment in QA.

It is not necessary to have exactly the same environment in both environments. The QA environment could be based on virtual machines with less sizing (memory, cpu, disk). I would say the minimum requirement should suffice. Of course, a sizing should be done by the customer in order to provide at least enough throughput to perform integrated testing.

Below you can find images showing the most typical environments you can find at a customer.

 

Minimal Production Landscape for SMP 3.0

 

MinLands.jpg

 

High Availability and Disaster Recovery environment

 

High Availability.jpg

Hope this article was useful.

Have a nice day!

Recently, at SAP TechEd && d-code in Las Vegas, I had the opportunity to host a panel live from the ASUG studio on the show floor. I enjoyed a great discussion with four of our mobile experts covering several important topics when it comes to mobility areas; mobile security, mobile app development, and the user experience. Our discussion focused on mobile app usage in the enterprise touching all of these aspects. The panelists, Senthil Krishnapillai, of the Mobile Secure team, Chittu Ganesan of the SAP Fiori team, Gerhard Henig, of the SAP mobile platform team and Alan Panezic of our partner Mocana, all have a strong understanding of what it takes to ensure a great mobile user experience.


The interview was broken up into 3 phases – build, deploy and use. Each expert addressed questions regarding new ways to build and secure apps. The panelists agreed that user experience is not about pretty screens and nice graphics, but rather is something that affects the entire experience and has a major impact on the app’s usage. A great user experience helps the user get the information they need – in a secure fashion – without having to constantly sign in to networks and reenter credentials.


You can watch the recording of the 12 minute video below to see how the teams at SAP are working together to combat the burning issues of user experience, connectivity and security measures improved with SAP Mobile Secure, SAP Fiori and SAP Mobile Platform.


Hi,

 

 

 

Easy way to split Tablet/Desktop UI screens.

 

Details: To divide our SPLIT screen Detail page into 2 screen under mobile library, Splitter is the best solution to complete our task.

 

 

 

With resize option:


var oLayout = new sap.ui.layout.Splitter({

  contentAreas : [detailViewpage,detailViewpage2],

    });

 

Inside this content area, we have two views name. While using this SAP automatically split our detail page it into 2 parts, with resize option

 

Without resize option:

 

var nonResize = new sap.ui.layout.SplitterLayoutData({

  resizable : false,

  });

  detailViewpage.setLayoutData(nonResize);

 

we need to use above code.

 

1. According to Split App architecture, Layout data roles are important.

2. Under splitter i put two views

3. if we assigned splitter layout data with resizable as false, resize option will disapers




 

 

 

This is available in version 1.22

 

 

 

Thanks,

Karthik A

After a very successful few days in Las Vegas, SAP TechEd && d-Code is heading to Berlin, Germany! The event will take place from November 11th-13th. In that short time, you and your colleagues will have the chance to gain enterprise mobility insight and advice from our Mobile Secure experts, Senthil Krishnapallai, Britt Womelsdorf, Jens Koster and Allan van Lelyveld. They will be hosting sessions and networking events on how to create beautiful, easy to use applications that also have simple yet tight security guidelines that meet the security requirements of your company. SAP Mobile Secure has helped enterprises all over the world increase mobile app adoption and retention – if you know that going mobile is right for your enterprise, be sure to add these sessions to your agenda!

 

Lectures:

Increase Mobile App Adoption with Security that Enhances Usability: Senthil Krishnapillai & Britt Womelsdorf

Mobile apps can transform your business, but adoption may suffer unless end users can quickly and securely find and setup apps. Learn how SAP Mobile Secure integrates with the SAP Mobile Platform to streamline the experience for IT, app developers, and end users with seamless access to enterprise services like enrollment and single sign on.

Tuesday, 12:15pm-13:15pm Add to your agenda

 

A Simple – and Powerful – Approach to Enterprise Mobility Management: Senthil Krishnapillai & Britt Womelsdorf

Address the risk of going mobile with an integrated, cloud-based solution that makes it easy to manage and protect mobile devices, apps and content. See how SAP Mobile Secure enables IT admins to get up and running in minutes, even when establishing the most granular device or app-level policies, across corporate issued or BYOD mobile programs.

Thursday, 12:15-13:15 Add to Agenda

 

Run SAP Mobile Platform in the Cloud: Martin Grasshoff & Senthil Krishnapillai

Learn all you need to know in order to run mobile applications in the cloud. Topics to be covered include using Cloud Connector to access enterprise data, the new Admin UI, and how to leverage SAP Mobile Secure in the cloud.

Wednesday, 15:30-16:30 Add to Agenda

There will also be networking opportunities providing additional opportunities to talk about enhancing the user experience and mobile app management. On Tuesday, you’ll have a chance to attend a roundtable with Senthil Krishnapillai and Alan Panezic (Mocana) on SAP Mobile App Protection.

 

Steps to Creating a Secure Mobile Solution: Allan van Lelyveld

Learn how to develop secure mobile apps as we convert a simple HTML5 app into a secure enterprise-class app. See how you can leverage capabilities of SAP Mobile Platform during development, and enhance with SAP Mobile Secure for app wrapping after the development process is complete.

Tuesday, 15:30-16:30 Add to Agenda

 

Putting it all Together with Mobility Solutions by SAP: Allan van Lelyveld

This session will showcase an end-to-end scenario that customers could implement utilizing SAP Mobile Platform, SAP Mobile Secure, Cloud Edition, and SAP Mobile Place. We will demonstrate an end-to-end integration scenario that utilizes features from each of the components.

Thursday, 11:00-12:00 Add to Agenda

Thursday, 15:30-16:30 Add to Agenda

 

Networking Sessions

 

Simplify Mobile Security in the Cloud: Senthil Krishnapillai

This discussion explores the paramount need for security in mobile environments and the impact it can have on both IT and business users. See how you can get thousands of users secured quickly with a simplified, portal-based experience. Learn about the significant benefits of SAP Mobile Secure in the cloud, including new mobile app management and mobile app security capabilities.

Thursday, 14:00-14:30 Add to Agenda

 

Mobile App Management: Britt Womelsdorf

SAP Mobile Secure now includes Mobile Place, a secure mobile app management (MAM) solution that makes it easy for companies to simply and proactively push their mobile apps and services into the hands of employees, business partners and consumers. Learn how Mobile Place provides a secure, multi-channel central hub that offers self-service capabilities. This solution brings the management of content, apps and devices together in a seamless workflow for IT admins, application developers and end users.

Wednesday, 13:30-14:00 Add to Agenda

 

Securely Access and Share Your Documents Anywhere with SAP Mobile Documents: Jens Koster

Get answers to your questions about SAP Mobile Documents. Join us for an interactive session on this solution for secure mobile content management.

Tuesday 11:00 – 11:30 Add to Agenda

 

Q&A Session

 

Q&A: Putting It All Together with Mobile Solutions from SAP: Allan van Lelyveld

Centered on the SAP Mobile Secure portfolio, this interactive session explores the requirements for typical mobile app deployments.

Tuesday, 13:00-13:30 Add to Agenda

 

Roundtable

 

Customer Roundtable featuring Colgate

In today's security conscious world, many businesses need a solution that can provide advanced security for mobile apps without disrupting the user experience. This is where SAP Mobile App Protection, part of the SAP Mobile Secure portfolio, can help. The Colgate-Palmolive Company is a leading American multinational consumer products company focused on the production, distribution and provision of household, health care and personal products, such as soaps, detergents, and oral hygiene products. Colgate was looking for ways to improve the end user mobile experience and gain a faster time to value from their investment. Please join this interactive session to understand first hand from Colgate why security is so important. You'll gain insight into the company's selection process and have the opportunity to ask questions. We're excited to share our mobile app security strategy with you, to help you speed your mobile deployments while ensuring the strictest security requirements are met.

Tuesday 11:00am – 12:15pm

Requires registration

 

And of course, you can always visit us at the SAP Mobile Secure tables as well. We'll be happy to share demos with you and talk more about any topic.

We look forward to seeing you in Berlin!

Unless you’ve been completely sequestered away from technology news as well as mainstream news, you probably have heard of the new Apple iPhone 6 and 6 Plus as well as Apple’s new Point-of-Sale (PoS) ecosystem called Apple Pay.  Apple Pay became available on October 20th, coinciding with the release of iOS 8.1.  Apple Pay only works on the iPhone 6 and 6 Plus.  It will be compatible with Apple Watch when that rolls out in early 2015.

  contactless.png

Apple Pay.pngApple Pay is not the first PoS / mobile wallet to deploy. Google Wallet has been out for several years; however, many have deemed this a “failure.”  I wouldn’t go near as far as that. It was just a bit before its time, yet Google Wallet has persisted. Since that time, countless individuals have paid for goods and services at various brick and mortar locations around the globe using Google Wallet.  But what that has done is establish a number of PoS terminals where you might see a little Wi-Fi symbol with a hand holding a device (known as the “contactless payment symbol”).

 

There are anecdotal reports where people have completed purchases at retailers (not on Apple’s supported location list), using Apple Pay, on terminals that show the contactless payment option – e.g. those that currently support Google Wallet for payment from Android devices (KitKat 4.4 & above). This is not official and not confirmed, but it certainly shows that if Apple and Google would actually collaborate, their NFC-enabled devices would work in even more retailers.

 

googlewallet-transparent-300x254.png

Unfortunately, over this last weekend, a number of retailers began blocking Apple Pay and Google Wallet on their PoS terminals.  In many cases, both Apple Pay and Google Wallet were working fine (even though Apple Pay may have not officially been supported).  This started with CVS and Rite Aid and then extended to 7-11, Kohl’s, Lowes, Gap, Dunkin’ Donuts, Sam’s Club, Sears, Kmart, Bed, Bath & Beyond, Banana Republic, Stop & Shop, Wendy’s along with almost all of the major US gas station chains as well as many more. These companies will be supporting an alternative solution called CurrentC to launch in 2015.  CurrentC does not use NFC, but QR codes to be scanned by the mobile device at check-out time. Many technology press articles cite CurrentC being less secure than Apple Pay or Google Wallet (one says it “kind of sucks”).  TechCrunch noted that CurrentC (really Merchants Customer Exchange or MCX) is an attempt, spearheaded by Walmart, to reduce or avoid credit card fees among other revelations.  They imply that CurrentC is much more difficult to use than the NFC-based, contactless options.

 

CurrentC-Logo.jpgThe actions taken by MCX member companies has riled a lot of NFC (Google Wallet, Apple Pay and of course Softcard [Android only, currently]) users who were just fine with NFC-based contactless payment options that quite a few of these retailers supported. I think these retailers are taking a step backward, as the NFC-based PoS payment options did provide the level of security needed to take definitive steps to overcome the preponderance of retail hacking attacks that we’ve seen over the last few months. My bank just sent me a new Debit card, as I had used my old one at Home Depot during the time period that retailer was hacked. If I had, instead used a mobile payment option (PayPal works there), that would not have been an issue. In fact, if any major retailer, who has previously been hacked (that means you: Target, Home Depot, Neiman-Marcus, and many others) are NOT rolling out support for contactless payment options via high-security solutions such as Google Wallet and Apple Pay should be held suspect.

 

But, despite all of the posturing by MCX, Google, Apple, as well as the quieter Softcard, and PayPal, this means that contactless payments are now really off and running. For full disclosure, I do not yet have my Apple 6; however, it is on order. Once I do receive it, I will be experimenting with Apple Pay at a number of locations; including those that display the contactless payment symbol, but are not on the “Apple list” as well as those on the list.  I have paid with PayPal via my mobile a few times and with the old Square app (BTW: I’d love it, if Square would somehow enable support for contactless payments, going forward - that would help them AND consumers a great deal).soft-card.png

 

For the record, I think that CurrentC will ultimately fail as consumers will gravitate towards solutions that offer them security, ease of use, and privacy – areas where CurrentC is somewhat lacking, according to what I’ve seen. We’ve seen this before with mobile messaging – that’s why there are now a variety of messaging options besides SMS (WhatsApp, Kik, as well as SMS-enabled OTT messaging apps like Pinger, TextMe, and others) – consumers drive what is adopted in this mobile economy. Many, if not all of the retailers will ultimately come back to NFC-based contactless payment options and I think they’ll be welcomed. [NOTE: October 2015 marks the beginning of the time when a new payment system called EMV will usher in the new era of “chip-and-PIN” credit cards in the United States. It is very likely that the vast majority of these PoS terminals will also support contactless payments – good news for Apple Pay, Google Wallet, Softcard and other NFC enabled payment solutions – unless, by some odd reason, they remain blocked, as the retailer might still be hamstrung by MCX and CurrentC.]

 

In a way, we in the US and other markets where Apple Pay (as well as other contactless payment options) are catching up with markets such as Japan and Korea, where contactless payments are much more ubiquitous. Still, I think the age for mobile Point-of-Sale purchasing has finally arrived. Late, but it is finally here.

 

Please follow me on Twitter: @wdudley2009

In some presentation from SAP I saw a little user picture on the right top corner near the name.

 

Today I invest a little bit time to  find how does it works.

 

In the default the picture is show from the SAP JAM Account :

 

Social Media Integration - User Interface Add-On for SAP NetWeaver - SAP Library

 

But in our company we have no SAP JAM.

 

So I searched for a solution to integrate a image from the hcm system.

 

The solution I found in two default classes:

 

Enable JAM Integration

Class CL_SMI_COLLAB_PLATF_CHECKER

Method: IS_JAM_CONFIGURED

 

 

Gateway Class for the image (GETSTREAM):

Class : CL_SMI_ODATA_SRV_702

Method : GET_STREAM

 

First I have enhanced the class CL_SMI_COLLAB_PLATF_CHECKER in the method IS_JAM_CONFIGURED.

"return True"

METHOD IOW_YCL_SMI_COLLAB_PLATF_CHEC~IS_JAM_CONFIGURED.

*"------------------------------------------------------------------------*

*" Declaration of Overwrite-method, do not insert any comments here please!

*"

*"class-methods IS_JAM_CONFIGURED

*"  returning

*"    value(RV_IS_JAM_CONFIGURED) type ABAP_BOOL .

*"------------------------------------------------------------------------*

rv_is_jam_configured = abap_true.

ENDMETHOD.

Next I enhanced the class CL_SMI_ODATA_SRV_702

 

 

if iv_source_name = 'Member' and it_navigation_path is not initial and lines( it_navigation_path ) = 1.

     field-symbols <ls_navigation_segment> like line of it_navigation_path.

     read table it_navigation_path index 1 assigning <ls_navigation_segment>.

     if <ls_navigation_segment>-nav_prop = 'ProfilePhoto'.

*      " Obtain the member's id.

*      data lv_member_id type cl_sm_integration_mpc_ext=>ts_member-id.

*      lv_member_id = get_first_key( it_key_tab ).

 

       " Get the member's profile photo.

       field-symbols <lr_stream> type /iwbep/if_mgw_appl_srv_runtime=>ty_s_media_resource.

       create data er_stream type /iwbep/if_mgw_appl_srv_runtime=>ty_s_media_resource.

       data lv_picture type XSTRINGVAL.

              CALL FUNCTION 'YFIORI_GET_IMAGE' DESTINATION 'HCM_SYSTEM'

         IMPORTING

           EV_PICTURE       = lv_picture

                  .

 

       assign er_stream->* to <lr_stream>.

 

    <lr_stream>-mime_type = 'image/jpg'.

             <lr_stream>-value  = lv_picture.

 

*      move mo_smi_odata_srv_helper->get_member_profile_photo( lv_member_id ) to <lr_stream>.

     endif.

   else.

*    raise_operation_not_supported( ).

endif.

On the HCM System I wrote a little function to get the user image and return this image as xstring to gateway system.

 

 

imge.png

Motivation:

1. You want to show a different background on ipad and a different one on the iphone based on the orientation. If you are familiar with xcode, you would know that you actually require different images for iPhones and iPads. It further requires different images for the orientation(portrait or landscape).

2. Fiori apps use sap.m library. The controls of this library are designed with mobile touch devices in mind. Some controls occupy a lot of space on the screen although the fiori app on the desktop doesn't need those empty spaces. You would like to redesign the theme just for desktop to differentiate the mobile apps and the desktop version.

3. You want to use a strong color contrast on your mobile devices which is used by field personnel in the outdoors. But simultaneously, you want to have a soothing theme similar to sap_bluecrystal for you desktop users who are always indoors.

 

How do you do that?

Use the 'Theme Designer'. Refer Fiori Theme Designer for more basic info on how to use the tool.

Once you are in the tool, jump right into the CSS tab.

css tab.png

To start writing our custom CSS, we will first need the element class. I would recommend using chrome's developer tools. use the inspect element option when you right click on the element to desire to theme.

inspect element.png

Find out the class attribute for the element you desire to theme. in this case, i have selected the tile on the launchpad.

class-show.png

Make sure you select the class from the root most element. otherwise there is change of some properties getting over-written by parent element's class properties.

So, here we have the class sapUshellTileBase and on the right side you can see the properties.

.sapUshellTileBase {

color: #333333;

height: 100%;

-webkit-box-sizing: border-box;

}

Here you can change the color of the tiles or actually you can add an image to the tile using background-image property. You can add all your images into the MIME repository in the backend.

 

You can add this to your CSS tab and change any parameter or add any new styling parameter.

 

Now the good stuff

To ensure the same theme behaves differently in different devices, you need to use CSS media queries.

Media queries can be used to determine what type of device is being used. It uses parameters like pixel ratio, width, height, orientation of the device and others to determine the type of device. This is how it looks

 

This media query would work for iPad 3, iPad 4, iPad Mini 2, iPad Air. iPad Air 2 when it is in 'landscape' mode. So, if you have you css defined inside the media query, it will be considered only when run on an ipad when it is in landscape mode

@media only screen

and (min-device-width : 768px)

and (max-device-width : 1024px)

and (orientation : landscape)

and (-webkit-min-device-pixel-ratio: 2) {

/*your css goes here */

}

 

Similarly, any CSS written inside this media query would run on iphone 5 in 'Portrait' mode and sets the background to a corresponding portrait image with an opacity of 72% and scaled to fit the entire screen.

@media only screen

and (min-device-width : 320px)

and (max-device-width : 568px)

and (orientation : portrait)

and (-webkit-min-device-pixel-ratio: 2) {

.sapMGlobalBackgroundImage {

display: block;

position: absolute;

box-sizing: border-box;

left: 0;

top: 0;

bottom: 0;

right: 0;

opacity: 0.72222222;

background-image: url("http://<server>:<port>/content/iPhone5-Port-640x1136.png");

background-repeat: no-repeat;

background-position: left top;

background-size: 100% 100%;

}

}

final.png

Similarly you can handle for desktops which have considerably higher pixel widths than most of the mobile devices.


A good reference for device heights, widths and pixel ratios can be found here. Note that the width here is the css-pixel width and not the device pixel width. Many devices don't share the same number.

It has been a while since I have seen such a passionate CEO. I read her Message of the Day every morning which helps me start my day with optimism and a great belief in the human spirit. I follow her blog series about the impact Design Thinking is bringing to the IT world and now I’m excited not only because her company’s new app is the first Fiori app that was certified by SAP but because it also won the 2014 SAP and Google Apps Challenge.

 

I’m talking about Sana Salam, the president and founder of Sodales Solutions. The company is a certified SAP partner focused on mobile and big data solutions. The company believes in bringing the human factor to the technology world, resulting in an easy user experience within the constraints of a business environment.

 

The winning app is their Labor Cockpit App, a mobile app following the SAP Fiori design guidelines. It allows the collaboration between companies, their external recruitment agencies, various regulatory bodies and of course the candidates around labor management processes. Using this app will result in higher efficiencies and transparency. Using its self-service, personalized Launchpad, hiring teams and project managers can save time and costs and quickly onboard, assign work, schedule and track staff productivity and share documentation such as policies and licenses.

 

When I was reviewing the app, I could really see how teams can take faster (and better) informed decisions backed by analytics that will surely improve profitability down the road.

 

Now that the Labor Cockpit app is certified, customers can get it via the SAP Store, which will feature partner apps that expand the SAP Fiori app portfolio for various industries, lines of business and roles.

 

The certification process ensures that all apps built are robust regardless of the creator (SAP or a partner). When submitting apps for the certification program, partners need to provide relevant documentation on the UI design (e.g. following SAP Fiori Design guidelines, app template, and product definition) and complete a Technical Product Profile (TPP). Then SAP staff technically test the apps on their installation and configuration, registered development namespaces and usage, SAP Gateway content configuration and more. Functional spot checks will be performed alongside a review of the documented comprehensive test scenario performed by the partner. 

 

Stay tuned for other blog posts about partners providing Fiori apps.

This week at SAP TechEd && d-code in Las Vegas, some cool innovations were shared on the main stage in Bjorn Goerke’s keynote. As part of the demo watched by over 7,000 people in person (and thousands more online), a story weaving together Mobile Security and SAP Fiori was center stage. SAP is innovating and leading how enterprise apps are mobilized, secured and deployed in a holistic manner. Our vision is to make it simple for enterprises to securely mobilize SAP enterprise apps all the way across the development, test and deployment life cycle. This week we moved one step closer to this vision by showing the integration for SAP Fiori apps spanning our cloud platforms.

 

The concept is fantastic. You can build custom Fiori apps with unique icons, splash screens, and names and publish multiple Fiori apps on single device. Without coding - and within minutes - you can log in to the SAP Mobile Secure cloud and build a native custom Fiori app. Its as easy as naming the app, adding an icon, choosing security policies, pasting in the URL, compiling and publishing the app – a few simple steps.

 

Previously you could build the app but it was a complicated process involving many systems and tools. Now you can build and launch a custom Fiori app on SAP’s mobile app store in minutes.

 

In Bjorn’s demo there were three steps outlined. Ian Kimball entertained the crowd and jumped in to Step 3, showing this Fiori build service in detail.

 

Developers are excited about this service. Here’s why:

  • They can develop, customize and build Fiori apps for iOS and Android devices using cloud based Web IDE without maintaining multiple local native development environments.
  • They can easily extend the basic Fiori app functionality through the use of on-device capabilities, using a catalog of SAP-provided, vendor-provided and Open Source Cordova plugins that can be added with one click.
  • They have the ability to add HANA Cloud Platform Mobile Services to enhance Fiori apps with support for user provisioning and offline OData support.
  • They can easily build for multiple platforms and publish to end users via Mobile Place with a single click (for trial or final deployment of the Fiori app)

 

IT Administrators love the following:

  • They can mobilize Fiori apps to work on iOS and Android devices with great user-experience
  • They can manage end-to-end app life cycle from building app to Trials and Production deployment on both managed (MDM) and Unmanaged devices
  • They can increase end-user adoption with simple but complete on-boarding experience with SAP Mobile Place (discovery, download, provision, configuration, update..)
  • They can secure the app with optional App Wrapping policies & per-app VPN connectivity options.


You can watch the video of the demo here:



Actions

Filter Blog

By author:
By date:
By tag: