1 2 3 79 Previous Next

SAP for Mobile

1,172 Posts

As a Canadian, I love the 4th of July for many reasons. One of which is the ability to blog uninterrupted while my American colleagues are out of the office enjoying parades and fireworks.

 

I read today on usnews.com that “80% of Americans attend a barbecue, picnic or cookout” on the 4th of July. That’s exactly the same percentage of people who download SAP Fiori with the intent of accessing SAP systems from mobile devices. While a very high number, this statistic shouldn’t be surprising considering mobile is the preferred consumption method of millions of employees working across a wide variety of roles at companies globally.

 

We often refer to the concept of taking SAP Fiori web applications and enabling them to act as true mobile applications on a mobile device as the “SAP Fiori mobile experience”. Delivering the best possible mobile app experience requires more than a good app level user interface.

 

The mobile environment is full of challenges. Anyone who has tried to use a browser on a mobile device to access corporate content behind a firewall can tell you the issues. But there are many unique challenges inherent to mobile that should be considered, such as:

  • Optimizing the experience so users can be productive away from their desktops
  • Making it easy for users to complete small tasks quickly and easily
  • Providing the option to work both online and offline
  • Taking advantage of the unique capabilities available of mobile devices
  • Addressing security concerns that may impact user experience
  • Providing an app store experience that users have come to expect.

 

The US smartphone market surpassed 150 million devices a year and a half ago. This weekend alone, Americans are expected to chow down on 150 million hot dogs. As we consume both hotdogs and mobile data, lets keep in mind that the average mobile consumer checks their device 150 times a day. It is in this environment of rapid change and heavy mobile usage that we have to provide easy access for employees to be productive at work. And we can help you do this with the SAP Fiori mobile experience.

 

As you’re planning to take SAP Fiori to your mobile users, and you’ve started to consider the issues you’ll face, I encourage you to join my colleague Scott Steadman and I as we deliver a webinar on this topic on July 22nd. If you’re interested in learning more and registering, check out the invitation here.

 

We’ll cover topics including the end-to-end development tooling and process, implementing security features like certificate provisioning, multi-factor authentication, and central policy management, and delivering a native, more responsive and better performing user experiences to Fiori mobile apps are top issues to consider.

 

While you’re enjoying your hotdog and fireworks display, think ahead to your plans to take SAP Fiori mobile in 2015. Join us as we help enable you to be successful in the mobile environment.

We are pleased to announce that SAP Mobile Platform 3.0 (SP08) was released for download on SAP Service Marketplace on 2015-06-28.

We are delivering new capabilities in the following three big areas:

  • Developer Experience
  • Security Enhancements
  • Administration enhancements

 

The enhancements for “Developer Experience” are around the integration Services and enhancements for retail scenarios.

For the Integration Services the performance and functionality was enhanced. This enables, for example, developers to do deep inserts to any level on the REST connector. With deep inserts the developer can now insert a parent with several children with a single REST call. Further the delta tokes for complex models are enabled for the JDBC connector. This will give mobile solutions, which integrate a Database the option to improve the runtime performance through the use of delta tokens.

 

The second enhancements for the retail scenarios include a Point of Sale (POS) optimized API, and Paypal integration. Through the POS API developers can now connect their remote POS system through the SMP to simplify the landscape for a specific solution. Through the Paypal integration developers can now leverage the Payment options in their mobile solutions through the SMP.


We also continue with our enhancements around Security.

With the new Service Pack 08, Administrators are enabled to now leverage the SMP3 as a SAP SSO2 provider. This allows Administrators to generate SAP SSO2 tickets for their mobile solutions. So the System Landscape can be optimized and no extra SAP Java stack is needed to generate such tickets anymore. Additionally the administrator can now validate with a single click if a security configuration which was just created. This saves the administrator testing and validation time to provide the expected services.

Screen Shot 2015-07-03 at 12.54.36.png

In the area enhancements for Administration we expanded the capabilities of the Solution Manager. Now the SAP Mobile Platform fully supports the System Landscape Directory, which gives Administrators easy access to the system information of the running mobile solutions.

Further we added the capability to import and delete certificates on the SAP Mobile Platform, which are deployed on a cluster. An Admin can now centrally manage the certificates.

Screen Shot 2015-07-03 at 12.51.14.png

Additional enhancements were made the SAP Mobile Platform Admin console, which is now unified with the Admin console for the Integration services. This Allows Administrators to easily drill into mobile solutions leveraging the Integration Services. Additionally we

You can consult the SMP PAM on Service Marketplace for details (SMP3 PAM (access to the Service Market Place is needed)).

 

 

Want more information?

 

Sami



blog+signature.png

We are inundated by the latest hype: Everyday, someone is launching a new wearable.  The Apple Watch sold out in its initial offering and of course, exceeded all expectations once again. Not to be outdone, Google is upgrading its own OS to create a better smartwatch that will rival the Apple Watch. In the automotive world, we are peppered by news stories about the “connected car” to the “fully autonomous self-driving car.”  That notwithstanding, we already enjoy many driving autonomous features such as adaptive cruise control, lane detection, and preventative braking. Already, Tesla is launching the first elements of its much anticipated “autopilot.”  Delphi recently completed a cross-country run of its self-driving technology and of course, Google thinks they can have an autonomous driving vehicle ready for the market in 5 years.

 

Mobile technology is not just about mobile phones anymore. Mobile means networks for access – you know the kind: 3G, LTE, LTE-Advanced, and beyond as well as Wi-Fi.  Mobile means connectivity and big data as well as communications and certainly a backbone for the Internet of Things (IoT). Mobile also means devices – but not just our favorite smartphone – but also wearables, automobiles, and things.

 

From today’s new wearables to connected cars, the technology – especially mobile-centric technology – that is taking root today will enable baby boomers as well as Gen-X’ers to live more independent lives as they age.  People want and need independence and mobility. The technology that is actively being tested now and starting to become mainstream will be the technology that frees many people from dependence and isolation.

Apple Watch Gallery-1.jpg

 

Let’s look at a few examples starting with wearables.  Wearables such as the new Apple Watch are becoming smarter and providing more capabilities to help people monitor their health.  While today these devices mainly are used for fitness tracking, as more functionality is added (and FDA approved), we’ll see these devices being to be used for more serious health monitoring with functionality including blood oxygenation (the Apple Watch actually contains photoplethysmography sensors to measure blood oxygenation; however, it is not yet activated), respiration rates, blood pressure and more.  With accelerometers already measuring movements discerning between riding in a bumpy car and actually walking, these are truly spectacular sensors.

 

Devices such as smart watches and other wearables are the new: Life Alert (“I’ve fallen and I can’t get up”). While today’s Apple Watch is still tethered to an iPhone, it is likely that future wearable devices from Apple will not require this.  With very sensitive accelerometers and the appropriate software, the ability to detect a fall is extremely likely.  In addition a smart wearable’s messaging and alerting capabilities (already available) can remind people to take medication
and perform other activities.  The current generation of wearables is very much geared toward fitness; however, I do expect we’ll see more and more applications that will cater to seniors to enable them to be more independent. Utilizing mobile connectivity as well as GPS and other sensors, the ability for a wearable user to gain greater independence through personal health monitoring will increase and likely become one of the dominant markets for wearable technology.

 

In the not too distant future, if you are older, living alone, you'll have some peace of mind as you are “connected” – your heart rate, O2 saturation, body temperature and even blood sugar are monitored. Your wearable knows where you are and reminds you of times to take medications and if you don’t an alert could be sent to a loved one or caregiver. If you fall, your wearable detects that and alerts someone to call you to see if you are okay and if not, alerts emergency responders. Does this seem to be an invasion of your privacy?  In a way, yes; however, it’s much better than complete loss of privacy by having to move to a full-time care facility.  In fact, as technologies within wearables improve, we should see improvements in capabilities to intervene before a medical emergency or even a devastating fall.

 

Now let’s discuss mobility – and I mean the ability to move around. As many people age, they lose the ability to drive. In  many communities, public transportation and transportation options for seniors is limited to abysmal. People are simply trapped in their homes. Today’s mobile-centric, ride-sharing companies such as Uber or Lyft would certainly be an option; however, many seniors just do not view this as a viable option. Additionally, for many, there is just too much drama around Uber and Lyft as many organizations are not endorsing them as many municipalities are not so friendly to either company. For many, taxis, if they can afford them, are their only option.

 

Technology will likely provide us with self-driving or at least semi-autonomous cars?  Some of these may be on the road and ready for sale by or before 2020 and will likely grow in popularity before 2030. Business Insider reports that a “fully autonomous vehicle that can drive from point A to point B and encounter the entire range of on-road scenarios without needing any interaction from the driver” will debut in 2019.   BI Intelligence - Installed base of autonomous vehicles.png

 

Image being able to hop into your car and ask it to take you to your medical appointment or to visit friends and family or to the local bar or restaurant for drinks and dinner!   Talk about independence! As these new generations of Fords, Chevrolets, and yes, Teslas, Land Rovers, BMWs, Toyotas, Hondas, Audis, and more proliferate; vehicles with more autonomous driving capabilities will become more affordable. Full autonomously-driving vehicles will help the coming generations of seniors achieve considerable mobility that they would not have otherwise had.  Additionally, as vehicles become more automated, they will also become more connected, sharing data with other automated vehicles around them as well as with/from “the road itself (likely sensors periodically spaced through connected roadways).” This data will be the ultimate in M2M and will very likely use LTE-A and yet-to-be-defined 5G standards (likely after 2020) to maintain safety and autonomous operation of multiple vehicles all communicating real-time situational awareness.

 

As people in their forties and fifties today, reach their sixties, seventies and beyond – from the way we use mobile to communicate today (texting, video-calling, leveraging messaging, social and purpose-specific apps as well as yes, talking) to the wearables we are starting to embrace to the hints of automation and connectivity in our cars today – are all setting the stage to lead much more independent lives as they age.  Think back to where we were in mobile technology only ten years ago vs. where we are today. I refer to mobile, because it is mobile that, in my opinion, has made the greatest strides in spearheading how we live and work today. There is no reason to believe that innovation and positive steps forward won’t continue with mobile leading the way and playing a central role in the technology that will help our golden years become significantly more independent and healthy.

Mutual Authentication using X.509 Certificate with SMP 3.0 is very interesting topic. In order to help engineers configure SMP, I am posting the following white paper that explains the following:

 

  1. Generating X.509 certificates and configuring the SAP Backend
  2. User Mapping and adjusting profile parameters
  3. Converting PFX certificate to PKCS #12 (.p12)
  4. Configuring SMP 3.0
  5. Troubleshooting

 

Document: http://wiki.scn.sap.com/wiki/x/zgtYGQ

For those working with SMP 3 and Gateway for push notifications:

 

if you want to use the push functionality of SMP 3 together with Gateway and a SAP backend and are wondering how to configure the Gateway / Backend / SMP 3 connection, I have published a series of blogs on how to configure Gateway (FND) and backend (BEP).

 

The blogs hosted on my site are following the steps outlined at SAP Help, but they contain screenshots and some comments :-) Follow the blog links to go to my site and see the step-by-step doc, or click the SAP Help link to go to the corresponding page at SAP Help. I am still publishing the blogs. I will update this blog here on SCN until all blogs are published.

 

Backend (BEP)

 

1. Settings for Idempotent services Blog / SAP Help

2. Defining a remote function call to SAP Gateway Blog / SAP Help

3. Connection settings to SAP Gateway Blog / SAP Help

4. Configure the bgRFC supervisor destination Blog / SAP Help


Gateway(FND)

 

1.       Basic configuration activities: SAP Help

1.1   Set profile parameters to support SSO2 Blog / SAP Help

1.2   Activate ICF Services Blog / SAP Help

2.       User & Authorization SAP Help

3.       SAP Gateway to Consumer (FND to SMP3) SAP Help

3.1   Creating a bgRFC destination for outbound queues Blog /SAP Help

3.2   Registering bgRFC destination for the oubound queue Blog / SAP Help

3.3 Creating bgRFC supervisor destination Blog / SAP Help

4.       SAP Gateway to SAP Backend (FND to BEP) SAP Help

4.1   Create RFC on SAP Gateway (FND) to SAP backend (BEP) Blog / SAP Help

4.2   Define trust between SAP Gateway and SAP backend (FND <-> BEP) Blog / SAP Help

4.3   Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help

4.4   Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help

4.5   Configure SAP system alias for applications SAP Help

5.       Activate SAP NetWeaver Gateway SAP Help

More blogs on the push functionality, how to test it, etc will follow.

We are pleased to announce that the SAP Mobile Platform rapid-deployment solution (Direct Download) was released for download on SAP Service Marketplace on June 8, 2015. You can follow the included step-by-step guides yourself to get started directly or you can work with SAP Services or SAP Partners.  As usual for rapid-deployment solutions the download is free for SAP customers and partners.

 

What's new?

 

SAP's Mobile Platform Solution can now be deployed flexibly either on premise using SAP Mobile Platform 3.0 or in the cloud with SAP HANA Cloud Platform Mobile Services (HCPms). The deployments include run time and design-time setup, configuration, development environment setup, and validation with a sample SAP Fiori app to increase time to value. The updated solution package includes the following SAP Best Practices™ for a quick and simple start for your implementation:


  • Unified foundation for on premise and cloud deployment as well as for the development of SAP mobile solutions
  • Guided run time and design-time setup with pre-configuration scripts
  • Streamlined scenario to introduce different deployment choices
  • Accelerators to reduced platform and applications implementation time
  • Simplified deployment and integration complexity of SAP Mobile Platform/SAP HANA Cloud Platform Mobile Services (HCPms) with mobile applications
  • Deployment of an end-to-end enterprise platform solution that provides installation, configuration, security, and data integration

 

Scope
RDS_SYB_SMP30V6_Explanatory_Diagram_EN_XX.jpg

 

Deployment options

 

On Premise -  SAP Mobile Platform 3.0

SMP 6.PNG

 

In the Cloud -  SAP HANA Cloud Platform Mobile Services (HCPms)

SMP 7.PNG

 

Download the package simply by following the below few steps:

 

1) Go to SAP Mobile Platform rapid-deployment solution's page http://service.sap.com/public/rds-sup


2) Tab on the orange button on the right hand side Download package


3) Select the link Installation


4) You get to a new page to download a ZIP file


5) Extract the ZIP file on your local hard disk. All documentation assets will be available offline on your desktop


6) Chose Start.htm to open the Content Library to flexible select or deselect scope items as you need them and get the related Configuration Guides

 

 

Available Mobile Rapid Deployment Solutions

 

  • SAP Mobile Secure rapid-deployment solution

          (Service Marketplace Page | Direct Download)

  • SAP Mobile Platform rapid-deployment solution

          (Service Marketplace Page | Direct Download)

  • SAP Work Manager rapid-deployment solution

          (Service Marketplace Page | Direct Download)

 

Feel free to comment, give feedback or ask questions via the comment section below.

Apple's WWDC Developer Conference has kicked off this week. This is not only the event where Apple announces new services like Apple Music, but also introduces new desktop and mobile operating system versions.

 

Frederic Jacobs has blogged about his initial impressions, and there is one thing that caught my eye:

 

2015-06-09 12_53_59-Frederic Jacobs auf Twitter_ _Apple introduces HSTS for your apps in iOS9, they .png

 

You see, one of the ongoing threats to mobile applications are badly secured connections. This threat category comes in many flavours:

 

  • Plain http connections:

 

    • all data can be read in transport by any network it passes through
    • the server you're talking to may not be the one you want to talk to (IP spoofing, DNS attacks - google "Pineapple WiFi")
    • anyone can intercept the connection and inject data into your stream, attacking the server code (or the client)

 

  • Badly implemented SSL connections

 

           Implementing SSL is not trivial, and I've witnessed many insecure implementations. Here are some of the more common issues:

 

    • #1 - not validating the SSL Server certificate. You may be talking encrypted, but not necessarily to the right server. This also makes man in the middle attacks (MITM) just as easy as on plain http connections.
    • validating the certificate, but not handling the different errors (certificate expired, mismatched host name etc.). That would also allow you to be misdirected.
    • you get a valid certificate, but it's a rogue server. Yes, attackers buy valid certificates, too. The mitigation against this is called Certificate Pinning, which basically hard codes the expected server data (certificate, key) into your code for verification.
    • accepting connections to a misconfigured server, i.e. a server with low grade security (vulnerable hash algorithms or small key sizes)

 

There are many more such issues. Apple is now taking a stand and effectively deprecating http connections, and giving your code a mechanism to do so in an automated way. This is a message that will be heard loud and clear in the market, and I wouldn't be surprised to see them reject apps from the store that don't implement this properly.

 

What is your experience with mobile applications? Were you aware of these issues? If you're a developer, is this a change you welcome?

 

UPDATE: Gizmodo also has a detailed list of security changes from WWDC

As a proactive support to our SAP Work Manager IBM Maximo customers, we have setup a quick start guide on how to install and get the SAP Work Manager 8.0 for the IBM Maximo (Maximo 7.5.2 version of the backend) to sync with the typical Agentry Test Environment (ATE) or SAP Agentry WPF clients.

 

This SAP Work Manager for Maximo 8.0 or 8.1 is a standalone SAP product to support the IBM Maximo backend enterprise system (Maximo 7.5.x and 7.6.x).

 

Most of these created Quick Start Guides reviewed multiple support tickets, QA tricks and request for help from the SAP Community Network (SCN discussions) to enhanced our documentation. This means by following the steps outline in the guide, the user will not see the same common error as reported in SCN or SAP ticketing (incidents). This will help each user tremendously in setting our products.

 

Thanks for making our SAP Work Manager for IBM Maximo successful. We wanted to share more hands on guide to help you in setting this product easily for your project and the customers.

 

The Quick Start Guide is to demo Microsoft SQL Server Backend database - adjust accordingly for Oracle or DB2. The user is expected to still run the SQL Admin script in the backend to generate the needed Agentry (Syclo) tables, procedures, triggers and others. If more information is needed the user may review the main installation guide.

 

  1. Quick Start Guide to install SAP Work Manager 8.0 with SMP 3.0  - Agentry - See SAP KBA # 2174180 - Quick Start Guide to install SAP Work Manager 8.0 for IBM Maximo with SMP 3.0 (Maximo 7.5.x).

 

# Note: The Quick Start Guide above can be reused for SAP Work Manager 8.1 (For Maximo 7.6).

 

Additional References:

 

 

Best Regards

Mark Pe
SAP Senior Support Engineer

Hi everyone,

 

This is the second part of the blog post to detail out the steps to build an X Code project for SAP Work Mgr. 6.2 with ESRI GIS libraries and SAP EAM SDK included. The first part of the blog is at the below link:

Integrate GIS libraries in SAP Work Mgr. - iOS - part 1

 

 

SAP EAM Mobile App SDK 1.0

 

1) Download the SAP EAM SDK from SAP Support Portal. You can find this under Installation and upgrades-> A-Z-> E

 

2) Now we need to include the SAP EAM libraries and resources in the X Code project. Right click in the blank area in X Code -> Show in Finder. Create a “Resources” folder in your project where the .xcodeproj file is located. Create 2 new folders under the “Resources” folder, CommonResources, GISResources

create folders.jpg

 

2 folders.JPG

 

3) Copy contents from the following path SDK/Common/Common.framework/Resources to the CommonResources folder that was created in step above. Copy contents from following path SDK/GIS/GIS.framework/Resources and past them in the GISResources folder just created

 

resources.jpg

 

4) In the end, your “Resources” folder should look like this

 

assets folder.jpg

 

 

 

5) Right click in blank area in your X Code, add files to your project and add this newly created “Resources” folder. Current project structure is in thebelow screenshot.

 

add resources.jpg

 

proj struc.jpg

 

6) Now we need to add the Common. Framework and GIS. Framework to the project. Click on the “target” in the project navigation view in X Code and then click on “Build Phases”-> Link Binary. Click “+” button and choose add other

 

add common 1.jpg

 

 

add common 2.jpg

 

7) Navigate to the folder where you installed the Arc GIS SDK and add the common.framework file to the project (path SDK/Common/Common.framework). Repeat to add GIS.framework file to the project (path SDK/GIS/GIS.framework).

 

add gis and common.jpg

 

8) Add systemconfiguration.framework by navigating to build phases->Link Binary

 

system config.jpg

 

9) Build your project and run in simulator. You have now finished building a project with the ESRI and SAP EAM libraries included. IF ALL BACKEND CONFIGS(from a Syclo and GIS standpoint) are in place, you should start seeing asset data under the locations tab in the app.

 

Hope this helps.

 

Cheers,

Abhinav

Hi everyone,

 

This is my first SCN blog post :-). I just wanted to write a detailed step-by-step integration with screenshots on how to include ESRI/GIS libraries with SAP Work Mgr. on the iOS client. The entrie process will be detailed out in 2 blogs.

 

I am not an iOS/client side developer and had to learn this process with a lot of trial and error and with support from SCN members. I hope this document helps anyone who is trying to accomplish this. This document is written from a "non-iOS" developer point of view, so there might be too much detail for iOS developers.

 

P.S - this post is open to suggestions/modifications, there might be other(and even better) ways to do this. I have followed this process at least 6-7 times on different Mac books and it has worked for me.

 

P.P.S - Please review the “SAP EAM and service mobile app SDK 1.0 Installation Guide” in the “Installation & Upgrade guides” section of the SAP Support Portal to get an overview of all the components that are needed to enable GIS in SAP Work Mgr. This document is a step-by-step guide to include all libraries, once you understand what pieces that are needed.

 

SMP SDK set up

 

1)  Install SMP SDK for Mac(I used SMP SDK SP06) AND Windows(yes, you need the SDK for Windows also as the file you need SMPAgentryClientFramework-iOS-70.6.0.tgz is not available in the Mac version of the SMP SDK - strange!). Technically, installing SMP SDK on your Mac is optional if you are able to transfer the SMPAgentryClientFramework-iOS-70.6.0.tgz file from the Windows version of the SMP SDK to your Mac under the $Home\SAP\MobileSDK3 folder- see below screenshot(SMP SDK installation creates this directory for you, if you have chosen not to install the SDK you can create this folder manually)

 

windows file.jpg

2) Extract the contents of this file on your Mac

extract on Mac.jpg

XCode set up

 

1) There is a sample X Code project already included in the SDK. This is part of the SMPAgentryClientFramework-iOS-70.6.0.tgz that was extracted in step above.Path = SMPAgentryClientFramework - >iOS->Samples->SMPAgentryFrameworkSetup->SMPAgentrySetup.xcodeproj. Double click on this file, it should open in X Code.

 

2) Build and run this project in simulator just to make sure that there are no errors.

initial build success.jpg

3) Download ESRI SDK to your local machine. Navigate to https://developers.arcgis.com/ios/objective-c/guide/install.htm to install the latest version of the libraries (version number used in this document is 10.2.4). Assumption is that your organization/client have the required licenses from ESRI, covering that is beyond the scope of this document

 

4) Set up your X Code project to include the ESRI libraries (all instructions can be found at https://developers.arcgis.com/ios/objective-c/guide/install.htm

Below screenshots are from my X Code project corresponding to steps 1-4 in the ESRI instructions (in above screenshot). Again, the instructions on the ESRI website are quite detailed, please follow them carefully.

 

- Add ArcGIS to the framework search paths

framework search path.jpg

- Add build flags (I only copied part of the text from the Arc GIS website -> -framework ArcGIS -| c++

other linker flag.jpg

- Add dependencies(screenshot is only for adding the Assets library framework, likewise add all framework as mentioned on the ESRI website)


add dependencies.jpg

 

add dependencies2.jpg.png

- Add Arc GIS bundle to project. Navigate to the path where Arc GIS SDK is installed. Typically this is ${HOME}/Library/SDKs/ArcGIS/iOS/ArcGIS.framework/Versions/Current/Resources

add dependencies.jpg

 

add dependencies2.jpg.png

 

5) Build your project to check if there are any errors, you should see the app logon screen. I did not have to import the ArcGIS.h file to get the build to succeed

 

build with arc gis.jpg

 

I will complete the rest of the process in the next blog. The next step is to download the EAM SDK from SAP.

 

Cheers,

Abhinav

To all Agentry and SMP 2.3/3.0 users,

 

As a proactive effort by SAP Support (One Service), we would like to share an issue discussed by users when they upgrade their laptop/computers to Windows 8.X Enterprise system. This is normally seen when the IT department starts to order new laptops for new users or changing existing computers.

 

When this is done, the normal problems shown are that the standalone Agentry Test Environment provided by SAP in the Service Marketplace is not fully functional and not responsive. This is a known issue and the solution and changes to fix this is documented under:

 

SAP KBA article # 2167661 - Agentry Test Environment (ATE) - does not work in Windows Enterprise 8.0 or 8.1.

 

If you read the article, it will tell you what the problems  are, the causes and the solution. Under the solution it will include the limitation. Under reference, you will see the related SCN articles describing the changes.

 

Hope this helps.

 

Best Regards,

Mark Pe
SAP Senior Support Engineer

While our priority is to enable our customers to "Run Simple", it is sometimes easier said than done, especially when first starting out.  SAP Knowledge Management (KM) is aware of the challenges customers (both internal and external) face when using Mobility products to create business solutions.

 

For example, you want to build a Native OData App. Some of the questions you need to answer include:

 

  • Is there some way to simplify dependency/build management in my IDE: podspec file, maven repository, other?
  • I'm building an Android app, do I use Eclipse with ADT plugin or Android Studio?
  • Is my app going to be online, offline, or occasionally offline?
  • What is a defining request?
  • Will clients be connecting to SAP Mobile Platform Server or SAP HANA Cloud Platform mobile services, and are the same services provided on each?
  • Which version of the SDK is compatible with which version of the server/HCP?
  • Does the back-end OData service support ETags, server-side paging, what version of OData is supported?
  • Do I need to use Integration Gateway to access the datasource?
  • How do I build the app efficiently (pulling in only the required data)?
  • What kind of authentication will my app require?
  • How do I debug this thing?

Too many ????????

A couple things are clear:

  1. It takes a village...to build a worthwhile app: Customer, Developer, SMP/HCP Administrator, OData service support, and more
  2. Sometimes you don't even know what questions to ask

 

Where to start:

Help Portal - the starting point for SAP Mobile Platform documentation:

SAP Mobile Platform – SAP Help Portal Page


Select the SDK release of interest. For example:

SAP Mobile Platform SDK 3.0 SP08 – SAP Help Portal Page

 

Native OData SDK Release Notes - describes what is new for that release, and other important notes. If unsure when a feature was introduced, the release notes provide the answer:

Native OData SDK - Release Notes Summary - SAP Library


Core Content (Native OData App Development) -

 

App Development:

Setup information: Setting Up the Native OData Development Environment - Developer - SAP Library

 

Online: Native OData App Development Using the OData API - Developer - SAP Library

 

 

Offline: Developing iOS, Android, an Windows Offline OData Applications - Developer - SAP Library

 

Ocassionally offline: Developing iOS, Android, and Windows Occasionally Offline OData Applications - Developer - SAP Library

 

API Documentation location – the relevant APIs are described in the core documentation, but the actual API doc ships with the SDK:

Native OData API Reference - Developer - SAP Library

 

           Hana Cloud Platform Mobile Services:

         Configuring applications: SAP HANA Cloud Platform Mobile Services

 

 

SCN – webinars, blogs, how-to guides targeted to Native App developers:

Mobile Application Development Platform for Developers - Native Apps

 

PAM - the SAP Product Availability Matrix includes a complete list of product compatability and requirements:

Product Availability Matrix | SAP Support Portal

Click the Mobile link at the top of the page. Scroll to find the appropriate product and version in the product list.

Access to PAM requires an SAP Service Marketplace login: http://help.sap.com/disclaimer?site=http://service.sap.com/request-user


Google it - a quick search for "SAP Integration Gateway" includes this:

Integration Gateway in SAP Mobile Platform 3.0

 

And a search for "SAP delta calculation" returned this:

Delta Calculation using the SAP Exchange Framework

Android for Work is an enterprise mobility management (EMM) platform function that lets companies deliver a secure, productive, and rich mobile experience to their employees on Android mobile devices. Solutions built on Android for Work include these benefits:

 

  • Security and Data separation
  • Support for BYOD and Corporate owned/provisioned devices
  • Remote device and application management capabilities
  • Seamless user experience (Personal and Work on same device)
  • Simplified Application Deployment
  • Support for Divide Productivity Suite (E-mail, Calendar, Tasks, etc.)
  • Secure communication

 

SAP offers Android for Work solution as part of SAP Mobile Secure (Cloud).


Read detail introduction from Milja Gillespie - Google Announces Android for Work

https://www.google.com/work/android/img/security-2x.jpg

 

Current Android for Work requirements are:

 

  • Android 5.0+ Lollipop devices with managed profile support.
  • Android 4.0 - 4.4 (Ice Cream Sandwich, Jelly Bean and KitKat) devices using the Android for Work App (to be supported at a later date).

 

What is an Android for Work Profile?

 

A work profile is a managed corporate profile associated with the device’s primary user profile. When managed profiles are provisioned on the device, the corporate account, apps and data will remain under the control of the IT administrator and are kept separate from personal accounts, apps and data. By default, pre-configured Work apps are enabled in the work profile and will appear ‘badged’ with a red briefcase at the end of the personal apps drawer. Enforcing the work profile allows IT departments to secure the environment where business apps and data are running on a user’s device, without restricting personal apps and profile usage.

 

The work policy controller sets up a work profile to separate your personal and work space on Android 5.0+ devices.

 

Additional Resources

 

Thomas Saueressig, SVP & Global Head of IT Services for SAP SE, discusses how SAP delivers a consumer-focused mobile experience in the workplace with Android for Work.

 

Milja Gillespie explains how SAP is Working with Google to Accelerate Android for Work

 

In this blog, read details on SAP Mobile Secure Support for Android for Work Now Available

 

Read Android for Work Security white paper

 

Sapphire 2015 - SAP tightens Google partnership with software integration plans

 

How to setup Android for Work in SAP Mobile Secure

 

 

 

Start your FREE 30-day trial of SAP Mobile Secure...

 

Your free trial of SAP Mobile Secure includes unrestricted access to our mobile device management (MDM), mobile app management (MAM) and mobile app security solutions. Get up and running in minutes. Try Enterprise Mobility Management (EMM) Software with a Free Trial of SAP Mobile Secure.

In this post, you'll learn how to publish Fiori iOS application type in SAP Mobile Secure.

 

Requirements

 

  • SAP Mobile Secure
  • iOS Developer Enterprise Certificate
  • iOS Provisioning file

 

Obtain iOS Developer Enterprise Certificate


It is recommended using iOS Developer Enterprise Program's Production certificate with SAP Mobile Secure, if deploying app to all users.  While you can use certificate from iOS Developer Program with SAP Mobile Secure, be aware that app deployment is limited to registered devices only and there may be other restrictions.  If using iOS Developer Program certificate, be sure to register your device using UDID under app's Provisioning Profile.


1. Obtain iOS Developer Enterprise Program account

 

2. Login to iOS Developer Console


applelogin.png


3. Click Certificates, Identifiers & Profiles


applecert.png


4. Under iOS Apps, click Certificates (All)


appleapps.png


5. Add Production, AppStore and AdHoc, and Continue


appleaddcert.png

 

7. Upload CSR and click Generate

 

applecsr.png

 

8. Download your certificate

 

applegencert.png

 

9. Click Provisioning Profiles (All) and click on name used for certificate (Download file)

 

appleprovisioningfile.png


 

Add Application to SAP Mobile Secure App Catalog


Okay, now we are ready to add Fiori type application to SAP Mobile Secure.


1. Login to SAP Mobile Secure


mobsec_login.jpg


2. Click Add new application

 

mobsec_add_app.jpg


3. Select Application Type as Fiori Application (and click Next)


mobsec_fiori_app.jpg


4. In Details section, provide Name (e.g. E2E Mobile Cloud Demo App); other fields are optional


appdetails.png


5. Multimedia - optionally provide app icon and Banner image (only required if app will be featured in SAP Mobile Place)


appmm.png


6. Categories - select a Category (where this app be listed under); simply drag-n-drop from Available to Selected


appcat.png


7. Owner info - add additional app owners (co-owners who can manage this app's lifecycle)


appown.png


8. Supported Platform - click Get Started to add platform type


appplatform.png


9. Add new platform > Info

  1. OS Platform - iOS
  2. Base URL - You can use any website or Fiori App URL (e.g. Fiori Launchpad)
  3. Icon - optional
  4. Splash Screen - optional

 

platinfo.png


10. Add new platform > App Signing

  1. Singing Certificate - Upload certificate
  2. Private key passphrase - Input passphrase
  3. Provisioning Profile - Upload file

 

platsign.png

 

11. Add new platform > Multimedia (optional)

 

mobsec_add_app9.jpg

 

12. Add new platform > Documents (optional)

 

mobsec_add_app10.jpg

 

11. Add new platform > Trial Users (skip) and click OK

 

mobsec_add_app11.jpg

 

12. The Fiori build service is generating .ipa on the fly for publishing to SAP Mobile Place

 

platsuccess.png

 

13. Once the app is uploaded, click action button to set the app to production so users can view and install application from SAP Mobile Place.

 

prodpublish.png

 

Congratulations!  You have successfully added the Fiori app for iOS in the App Catalog.  Your users will be to navigate to SAP Mobile Place and download the application.

 

 

About SAP Mobile Secure

 

For more information on this topic, head over to SAP Mobile Secure Cloud.

 

You can start your free 30-day trial of SAP Mobile Secure today!

Hi there,

 

I’m very proud to announce that as of today we have released a major feature release for SAP HANA Cloud Platform mobile services. You probably you have not noticed, but since January we have updated mobile services at the end of each month and provided some patches. This is true for the Trial as well.

But today is different. Today we have deployed a major feature release, which includes:

 

  • SAP Fiori Support
  • Staging Area
  • Push Hub
  • SAP Logon Ticket Support

 

SAP Fiori Support

Fiori_1.png

SAP HANA Cloud Platform mobile services supports routing of Fiori Apps in proxy-mode adding additional Mobile Qualities to Fiori Apps (using Fiori Client, Custom Fiori Client or Packaged Fiori App). Fiori Client refers to the public Fiori Client App that is available here (AppStore, Google Play).

It can be used to consume a Fiori Endpoint URL directly or via HCPms.

Using the SAP Mobile SDK you can create your own version of the Fiori Client to customize it. For example, you want to create your own home screen icon, apply your own App signing or add any special behavior you want. This is what we typically call a Custom Fiori Client.

If you want know more about the the Fiori Client you should read John Wargo’s blog here: Introducing SAP Fiori Client 1.2.

The last option is potentially worth an own blog entry, but you can get an idea of what is meant by “Packaged App” when you read the blog about our Hybrid Application Toolkit, which let’s you build mobile Apps in the WebIDE and deploy them as Hybrid Apps to iOS or Android. In this latest scenario you are walking away from a Mobile WebApp consumed by the Fiori Client to a real mobile Application running entirely on the device – well, you still need to fetch the data from the backend.

Anyhow, all these three consumption options are possible with mobile services as of today.

But this is not all that we deliver. With this release we will extend our Client Policy to let you remotely enable/disable the mobile capabilities of the Fiori Client. So this allows an administrator in the Mobile Services Cockpit to remotely enable the barcode scanner plugin or disable the camera plugin for a given application.

 

Staging Area

If you have experience with the Hybrid App lifecycle and used the AppUpdate plugin of our SDK you know that you can easily update an already distributed App. With the new staging area you can allow developers to update a new version of your HTML5 content and assign this version to a specific group of people – we call them Testers – for access. This new version will only be available to the Testers and not to the public users. Once the Testers are ok with the new version, it could easily be moved to the productive area where the usual rollout process starts. This greatly enhances the rollout process and makes it more manageable. It supports an enterprise to deliver the user experience that mobile users are expecting today.

And this is how it looks like:

Staging.png

 

SAP Logon Tickets

In order to allow Single Sign On for SAP back-end systems HANA Cloud Platform mobile services will now be able to create MYSAPSSO2 logon tickets after successful authentication of a user. This is implemented in the way that the token will never hit the device and is entirely handled and stored on the server side. Once the trust between the SAP back-end system (e.g. a SAP CRM) is established a token, issued by the mobile services will authenticate a users request against that system. Since trust can be established between multiple systems this token will authenticate the users request against multiple systems

LogonTickets.png

 

 

Push Hub

The Push Hub is a very special service. It is only meaningful if you have a mobile app, distributed via a public app store and many different enterprise customers use this particular app – so we are talking about reselling business now. This app now is signed with your push certificate or contains your notification API key and only you are allowed to send notifications to it. But the back-end systems of your customers are generating the business event that needs to be distributed.

The Push Hub is an abstraction service that allows you to store your push certificate/API Key there and point your SAP Mobile Platform or the mobile services to the Push Hub, which will be the hub for your notifications. The following picture explains the Push Hub:

PushHub.png

The trial landscape will be updated as well, so that you can get your hands dirty with those new features.

 

 

Have Fun,

Martin Grasshoff

Actions

Filter Blog

By author:
By date:
By tag: