Skip to content

Managing Apps

Administrators interact with SAP Cloud Platform Mobile Services (mobile services) to ensure the production environment works efficiently.

Administrator tasks fall into two main categories:

  • Application administration for configuring applications for deploying to users and monitoring application in the user community.
  • Security administration for determining the Cloud Platform security features used for mobile applications.

User Interface

Frequently used icons in the Mobile Services cockpit. Actual icon styles may vary slightly.

Icon Purpose Description
menu2 Toggle Menu Toggle between showing and hiding the navigation menu in the left pane. Display the menu for fast navigation; hide it to maximize the window area.
home Home Go to the Mobile Services cockpit home screen. Includes links to frequently used tasks, access to current event log XML files, and relevant KPIs. The title indicates "Preview" if you are accessing the Neo preview system, to distinguish it from the production system. Your login name appears in the upper right corner. Select your name to view a drop-down menu. If Helpdesk appears after your name, this indicates that you are in read-only mode. Some buttons and features will be grayed out or not available.
newspaper About View information about the platform. Click your login name in the upper-right corner to see the option.
settings User Setting Select your login name, then User Setting to change your settings. You can select the language to use for Mobile Services cockpit (the user interface reloads in the new language); and you can select either the local or UTC time zone format (reports are also displayed in the local or UTC format, depending on your selection). Select Save.
log Log Out Log out of the application. Click your login name in the upper-right corner to see the option.
create Create Configure a new resource for a feature, such as a new destination.
action-settings Action Settings View available actions, such as customizing table columns.
add New Add a new item, for example, a destination, a provider, or a feature restriction policy.
Ping Ping Ping a destination.
show-edit OData Application Destination Test Test an OData application destination.
popup-window Launch in Browser Test a destination for scenarios that do not work from Mobile Services cockpit, such as "Cloud Connector SSO" "Forward", and "OAuth2 User Token exchange", because they require a business user (end user) login.
sort Sort Sort a list based on criteria you choose, such as ascending or descending order, or the column name.
upload Upload Upload an object.
download Download Download an object.
menu Details See details about the selected resource.
copy Copy URL Copies a URL string to the clipboard, enabling you to paste the complete URL elsewhere.

Application Administration

Use Mobile Services cockpit and other tools to manage and monitor native, hybrid, and Web mobile applications. Managing includes defining and configuring applications, monitoring applications and application usage, viewing statistics and logs, checking system health, and troubleshooting problems.

Native (online and offline), hybrid (Kapsel - offline), and Web applications are developed using a variety of tools and methods. SAP tools facilitate the development of mobile apps, with modularized methods for downloading, logging on, push notification, and error reporting. During the development process, a unique application identifier is generated for each application, and the application is deployed to an application download site or to SAP Cloud Platform Mobile Services. Web applications are running on-premise, but securely exposed through SAP Mobile Platform or mobile services.

The administrator creates an application definition in Mobile Services cockpit, which includes the unique application identifier, plus the connection to its back-end data source in the production system, the security configuration, and application-specific entries.

The administrator provisions applications to devices through native application stores, or through enterprise Web site downloads. When a user logs in to an application (or accesses the application as an anonymous user), the application+user+device combination is registered in Mobile Services cockpit. This registration enables you to manage and monitor device applications in the field using Mobile Services cockpit, and to take advantage of individual and aggregate usage statistics.

You can add, edit, or delete applications, and export and import applications. You can view all applications, or retrieve a filtered subset of applications; you can sort by column, and refresh the list. From the list of applications, you can drill down to see summary and detailed information for a particular application. You can lock an application to prevent accidental changes. If an app is locked, you must unlock it to modify it.

For apps that have been migrated to single-service apps, enable detailed event logging at the application level. You can select individual services to include, and Mobile AppRouter, as described below for the Event Log tab.

For multiple-services apps (those that have not been migrated to single service), you must enable detailed event logging at the service level. Select Enable Detailed Event Log to collect detailed messages. Select Disable Detailed Event Log to stop collecting detailed messages (error messages are still collected).

Access Analytics > Logs to view the event logs, as described in Viewing Event Logs.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.

    You can view a list of applications with summary information such as name, application ID, vendor, application state, creation date, and so forth. Use the search and sort options to locate the applications in which you're interested.


    Apps managed by App Lab do not appear in the application list. To manage App Lab updates, see Managing Application Versions using App Lab.

    Native/Hybrid Application Summary

    Column Description
    Application ID The unique application identifier.
    Name The application name.
    Vendor The vendor that supplied the application.
    License Type The application plan that was in place when the application was created, for example, "test" or "B2C".
    State The current state of the application, such as:
    • Started ‒ the application is running normally.
    • Inconsistent ‒ applications may become inconsistent if they are deleted or changed using the SAP Cloud Platform Cockpit. From Mobile Services cockpit, you can either delete or restore the application.
    • Deleted from SAP Cloud Platform Cockpit ‒ the application was deleted. You can restore or delete it in the Mobile Services cockpit.
    • Restoring ‒ the application is being restored from an inconsistent state.
    Outdated Whether the application is outdated. If checked, you are prompted to update the application to a newer version that contains fixes and improvements. Typically you should update the application.
    Creation Date (UTC/local) The application creation date, either in UTC or local format, depending on what you selected for your User Setting.
  2. Select an application to view its details.

    • Info provides a summary of settings for the selected application. To set the information on this tab, see Creating Applications. In the Cloud Foundry environment you can also configure a custom domain. See Editing an Application and Managing Custom Domains.

      To prevent accidental changes, you can lock an application once its configurations are complete. To make changes, you'll need to manually unlock the application.

      The list under Assigned Features identifies the features that are currently assigned to the application, and enables you to add and delete more. For more information, see Configuring Assigned Features.

    • APIs provides onboarding and API features.

      Under Onboarding, you can find one or two QR codes that can be used to configure the mobile application to connect to this mobile services instance.

      For In-app Scanning Code, the device user must first manually launch the app, then scan the QR code from within the app to initiate the onboarding process.

      For Default Configuration, native app developers can download a native-specific file containing the Discovery Service default configuration. Select iOS to download the configuration file in plist format, or select Android to download the file in JSON format. Add the file to your iOS or Android app project without further formatting.

      For Apple and Android Launch App Code, the device user can select the URL (or scan the QR code for Apple's Camera App or an Android application that allows reading QR codes). If the user enables Android app links, this also supports Android's camera app. The App-launch QR code is generated if you enable Apple Universal Links or Android App Links or both of them in the Application Links section. The label text of the QR code depends on which application links are enabled ("Apple launch app code," "Android launch app code," or "Apple and Android launch app code."

      For Apple and Android Launch App Code with URI Scheme, the device user can scan the QR code or select the URL, to use an application link URL to find and launch the application. This option only appears if you enabled Device Application URI Schemes in the Application Links tab. You must select one Device Type, and input the corresponding device application URI Scheme for iOS or Android.


      (Mobile Development Kit only) If you set up Apple and Android Device Application URI schemes in the Application Links tab, you see two separate QR codes, labeled Apple Launch App Code with URI Scheme and Android Launch App Code with URI Scheme.

      If the app security configuration changes, you must generate a new QR code. Also, please note that the URL can be very long and might be longer than the value shown on the screen. Use the copy to clipboard button to copy the complete value.

      Under API, you can view a list of frequently used API URLs. Use Copy URL ( copy ), to copy read-only URLs to the clipboard, to paste elsewhere, avoiding typing errors and ensuring accuracy.

    • You can use Application Links to enable universal links for Apple and application links for Android apps. Apple universal links and Android application links enable users to open an application locally without downloading the app or using a browser container. See Creating Application Links.

    • Users enables you to export or delete data for a user, and to block one or more users from using a Native/Hybrid or SAP Mobile Cards application.

    • Security enables you to manage security for the selected application. For details see Configuring App Security.

    • Alert lets you configure settings for server failures in various categories. Once configured, implement the SAP Cloud Platform Alert Notification Service to receive notifications. See Configuring Alert Settings and Subscribe to Mobile Service Alerts for information.

    • Event Log is for apps that have been migrated to the single-service model, and is used to enable event logs at the application level. You can specify any of the individual services that are assigned to the app, as well as Mobile AppRouter. This gives you more control over the event log information you want to see at the application level. See Enabling Event Logs for Apps. You can continue to view event logs as described in Viewing Event Logs.

Creating Applications

Create a new application definition, which enables you to use the Mobile Services cockpit to manage the application. When you define an application, you can choose a configuration template, or you can create a shell:

  • If you create a shell, only the security feature is added automatically, and you can add any other features you want.
  • If you use one of the templates for a native, hybrid, Web, or SAP Fiori application, available features for the template are included, including security. You can later add features that make sense for the application. After you define the application, configure the assigned features, or add more features. See Managing Application Features and Configuring Assigned Features.

  • In Mobile Services cockpit, select Mobile Applications > Native/Hybrid, and click New.

  • In New Application, enter:

    Application Properties

    Field Value
    ID Unique identifier for the application, in reverse-domain notation. This is the application or bundled identifier that is assigned or generated by the application developer. The administrator uses the application ID to register the application with mobile services, and client applications use the application ID when sending requests to the server. An application ID:
    • Must be unique
    • Must start with an alphabetic character
    • Can contain only alphanumeric characters, underscores, and periods
    • Can contain up to 64 characters
    • Cannot include spaces
    • Cannot begin with a period, and cannot contain two consecutive periods
    We recommend that you assign IDs that contain a minimum of two periods, for example, If you are building an Android application, its ID must follow the Google-defined rules, or the Android build fails:
    • The ID must have at least two segments (one or more periods).
    • Each segment must start with a letter.
    • All characters must be alphanumeric or an underscore [a-zA-Z0-9_].
    The prefix "" is reserved for packaged apps created using Web IDE.
    Name The application name can contain only alphanumeric characters, spaces, underscores, and periods, and can be as many as 80 characters long.
    Description (Optional) The description can contain up to 255 alphanumeric and special characters.
    Vendor (Optional) Vendor that developed the application. The vendor name can contain only alphanumeric characters, spaces, underscores, and periods, and can be up to 255 characters long.
    License Type The license type that you want to use for your account: Standard (default) and Business to Consumer. The license determines capabilities and charges. Once you've created an application, you can't change its license type; you must delete the application and create it again.
    XSUAA Service Select the XSUAA authentication and authorization service to use. You can select Default Instance to create a new instance, or you can select an existing service from the list. Using an existing XSUAA instance is useful if you already have a Cloud Foundry application deployed and want to connect from Mobile Services to this application. In this case it can be handy to re-use an existing XSUAA instance. Select the default instance for other scenarios.
  • Select Next.

  • In Assign Features for, select one of the configuration templates.

    • Native – applications built using the native SDKs for iOS or Android.
    • Mobile Development Kit - metadata-based applications.
    • Web – applications that run in a Web browser.
    • Hybrid – Kapsel container-based applications.

    The features selected for the template appear. You can select additional features and remove features (except for required features) at this time. Later you can make further changes as described in Managing Application Features.

Basic Features

Feature Description
Mobile App Catalog Upload mobile application artifacts for beta testing, and for deployment to external services.
Mobile App Update Upload new versions of a hybrid or Mobile Development kit application.
Mobile Setting Exchange Handles device registrations and provides exchange of general settings between mobile client and server, such as client policies.
Mobile Client Resources Add client resources to an application.
Mobile Connectivity Configure routes to back ends.
Mobile Offline Access Enable secure, offline access to data on the device.
Mobile Push Notification Register devices to receive native push notifications.
Mobile Client Log Upload Enable application to upload application log files and to analyze them on the server.
Mobile Network Trace Enable application to trace network activity based on user name or content type.
Mobile Sample OData ESPM Use OData sample service during development and testing.
Mobile Client Usage and User Feedback Enable application to upload client usage and feedback information and analyze it on the server.
Mobile Cloud Build Build binaries for your Fiori Launchpad or individual SAP Fiori business apps, and enable them to use the SAP Mobile Platform SDK.
  1. Click Finish and confirm to create the application definition. The Info page appears with current settings.

Editing an Application

Edit an existing application from the application list.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid.
  2. Select an application and click edit . See Defining Applications for application properties.

  3. (Native/Hybrid only) For Cloud Foundry, you can associate a custom domain with the application. Custom domains enable subaccount owners to make apps accessible via a domain that is different from the default domain.

    The custom domain can contain only alphanumeric characters, periods, or hyphens (“a-zA-Z0-9.-“). It must contain periods, and the length cannot exceed 200 characters. To remove the custom domain and the generated server, save the domain as a blank value. See Managing Custom Domains for information.

  4. Save your changes. If you added a custom domain, the value now appears on Info along with other application settings. It is important to verify the configured value is correct. An invalid custom domain name entry will make the application unusable.

Deleting an Application

Delete an application from the application list. For any SAP Fiori or hybrid apps regenerated with the Cloud Build Service, deleting the application also permanently deletes any binaries that are associated with the application.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.
  2. Select an application and click Delete.
  3. Click OK to confirm.


    Once an application has been deleted, users won't be able to use it. All existing logs and traces are deleted and cannot be retrieved. For SAP Mobile Cards, the card template is deleted, not the cards.

Managing App Users

Manage users at the application level.

You can delete or export data for a selected user, and block users.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid.
  2. Select Users.
  3. (Optional) Under User Data you can export or delete data for an individual user.
    1. Enter the user name. Valid entries include alphanumeric characters, numbers, period, underscore, and hyphen.
    2. (Optional) Select Export to download user data to a JSON file.
    3. (Optional) Select Delete, to delete user data, and select OK. The message "Delete user data successfully" indicates success.
  4. (Optional) Under Blocked Users, you can block one or more users from using the selected Native/Hybrid or SAP Mobile Cards application.
    1. Select add .
    2. Add the user you want to block.
    3. Click OK to confirm.

Last update: November 19, 2020