Skip to Content

Set Up Initial Configuration for an MDK App

test
0 %
Set Up Initial Configuration for an MDK App
Details
// Explore More Tutorials

Set Up Initial Configuration for an MDK App

Configure a new app in the SAP Cloud Platform Mobile Services cockpit and assign some server side features.

You will learn

  • How to configure MDK apps in the Mobile Services cockpit


Step 1: Understand the mobile development kit feature

Mobile Development Kit (MDK) allows developers and technical business users to build new native mobile applications and customize select SAP native mobile applications in a highly productive environment. It’s architecture is based on NativeScript, so it supports native cross platform development which means you build your native mobile application once and deploy it to Apple and Android devices.

Mobile Development Kit provides robust online and offline capabilities, business logic, and mobile qualities such as access to the camera and barcode scanner. The first application developed with the Mobile Development Kit is SAP Asset Manager and can easily be customized using the Mobile Development Kit.

You can find more details in the Mobile Development Kit developer page.

MDK
Log on to answer question
Step 2: Configure a new MDK app in Mobile Services cockpit

Make sure that you have completed required pre-Prerequisites mentioned in this tutorial.

Navigate to SAP Cloud Platform Mobile Services cockpit on Cloud Foundry environment.

On the home screen, select Create new app.

MDK

Provide the required information:

Field Value
ID com.sap.mdk.demo
Name SAP MDK Demo App
MDK

Other fields are optional. For more information about these fields, see Defining Applications in the SAP Cloud Platform documentation.

Click Save.

Once you have created your application, you see a default feature Mobile Settings Exchange that is automatically assigned to the app.

MDK

Mobile Settings Exchange handles device registrations and provides exchange of general settings between mobile client and server, such as client policies.

Click on Mobile Settings Exchange and select Biometric Authentication Allowed option to get faster access in unlocking the app on your device.

MDK

Save the changes.

Click com.sap.mdk.demo to navigate back to the app configuration page.

MDK

Now, we will assign few more features like App Update, Offline in the app configuration. First, start with Mobile App Update. Click + icon to add this feature.

MDK

Mobile App Update keeps MDK apps up-to-date and manage the apps’ life cycles.

Click com.sap.mdk.demo and navigate back to app configuration page.

MDK

Repeat above step and assign Mobile Offline Access feature as well.

Mobile Offline Access enable secure, offline access to data on the device.

You will end up with below features assigned to the app.

MDK
Log on to answer question
Step 3: Add a sample backend to your MDK app

A sample OData service is available for developers to use during development and testing. The sample OData service also lets you evaluate how delta tokens are handled in your test application.

For more information about these fields, see Sample Back End in the SAP Cloud Platform documentation.

Click on the + icon to add Mobile Sample OData ESPM feature to your MDK app.

Here, you can view the root service and metadata URLs, and generate sample sales orders and purchase orders for multiple entity sets. You can view the data for each entity in a separate text file, and even can reset the sample data.

Select OData Version V2 and click Save.

MDK

For Offline OData capability only OData V2 is supported. OData V2 and V4 are supported for Online OData.

Click com.sap.mdk.demo to navigate back to app configuration page.

What is the default OData version was selected when you added the Sample Back End?
×
Step 4: Get familar with other assigned features
MDK

Mobile App Update: - Since we specified Mobile Development Kit as the app type, the App Update feature is assigned to the app by default. This feature keeps MDK apps up-to-date and manage the apps’ life cycles.

Mobile Offline Access: - Define offline settings for the selected application. Offline support enables client applications to access back-end data without a connection. When offline, applications access data from an offline store on the client. SAP Cloud Platform Mobile Services moves data between the back end and the client offline store.

Mobile Connectivity: - Define destinations for the selected application.

Mobile Sample OData ESPM: - Use OData sample service during development and testing.

Mobile Settings Exchange: - Set client policies like Client Passcode, locking and wiping, feature restriction, and network synchronization etc. for the selected mobile application.

You can find more information on available features in SAP Cloud Platform Mobile Services in help documentation.

Log on to answer question

Next Steps

Prerequisites

Back to top