Skip to content

Managing Apps

Administrators interact with SAP 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 SAP Business Technology Platform security features used for mobile applications.

User Interface

Frequently used icons in the SAP mobile service 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 SAP mobile service cockpit home screen, which includes links to frequently used tasks, and access to current event log XML files and relevant KPIs. Your login name appears in the upper right corner. Select your name to view a drop-down menu.
  • If Preview appears in the title, you are accessing the preview system instead of the production system. Preview enables you to test new features for a week or so before they are released for production, but the preview landscape is not intended as a development or production environment.
  • If Helpdesk appears after your name, 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 Settings Select your login name, then User Setting to change your settings and then Save.
  • Theme: select your preferred color and contrast option from the list, which includes Default, High Contrast Black, or High Contrast White. The SAP mobile service cockpit user interface reloads in the new theme.
  • Language: select the language to use for the SAP mobile service cockpit. The user interface reloads in the new language. For supported languages, such as Arabic, the primary calendar is reloaded in right-to-left format and the Gregorian calendar is used as secondary. Note that business logic, such as calculating by periods and running business processes, is still based on the Gregorian calendar.
  • Time Zone: select either the local or UTC time zone format. Reports are also displayed in local or UTC format, depending on your selection.
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, or Launch Web App Depends on the context. When setting up a destination, use to test an OData application destination. When working with the ESPM sample data in SAP mobile service cockpit, use to launch a simple Web user interface to test your app.
popup-window Launch in Browser Test a destination for scenarios that do not work from SAP mobile service 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 SAP mobile service 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 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 SAP mobile service 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 SAP mobile service cockpit. This registration enables you to manage and monitor device applications in the field using SAP mobile service 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 SAP mobile service 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.

    Note

    Apps managed by App Lab do not appear in the application list. To manage App Lab updates, see Mobile App Catalog Artifacts.

    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, "free", "lite, or "b2c". See Service Plans for additional information.
    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 Business Technology Platform Cockpit. From SAP mobile service cockpit, you can either delete or restore the application.
    • Deleted from SAP Business Technology Platform Cockpit ‒ the application was deleted. You can restore or delete it in the SAP mobile service 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. 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,

    • 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.

      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 Configuration, you can view any application routes that you've associated with the application. Select edit to make changes. See Creating Applications for information about the XSUAA property, Domain of Application Route.

      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) to find and launch the application installed locally. If the user enables Android app links, it 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 appLink 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.

      Note

      (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.

      Note

      The Server URL is also the <mobile_services_host> name.

    • 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 Business Technology Platform Alert Notification Service to receive notifications. See Configuring Alert Settings and Subscribe to Mobile Service Alerts for information.

    • Log Settings 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 at the App Level. You can continue to view event logs as described in Viewing Event Logs.

Creating an Application

Create a new application definition, which enables you to use the SAP mobile service cockpit to manage the application. When you define an application, choose a configuration template. Keep in mind:

  • When you select a Native, Hybrid, Web, or Mobile Development Kit template, the most typical features for the application type are selected automatically. You can add or remove features at this time. or take care of it later.

  • Some features, such as Mobile Settings Exchange, are required, so you cannot remove them.

  • Other features have dependencies, so you either cannot remove them, or must remove them in a particular order. For example, Mobile Offline Access requires Connectivity, and Mobile Cloud Build requires Mobile App Catalog.

After you define the application, configure the assigned features, or add more features. See Managing Application Features and Configuring Assigned Features.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/Hybrid, and click New.

  2. In New Application, enter:

    Application Properties

    Field Value
    Application 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, com.sap.mobile.app1. 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 "com.sap.webide" 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: "free", "standard" (default), and "b2c". The "lite" plan is available only for trial subaccounts. The license determines capabilities and charges. You can change your service plan from "free" to "standard" or "b2c", enabling you to migrate your app without losing your work. Migration is not reversible. You cannot switch from "standard" or "b2c" to "free". See Service Plans for additional information.
    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.
    Domain of Application Route In regions that support multiple domains, select the application route through which end users can reach the application. Routes are associated with a space, and are configured in SAP Business Technology Platform cockpit. The drop-down list shows all shared and custom domains that are available for the customer organization. If you want to use a custom domain, you can create one according to information in What Is Custom Domain
  3. Select Next.

  4. 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.
  5. 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 SAP mobile service cockpit, select Mobile Applications > Native/Hybrid.

  2. Select an application and click edit on any tab to make modifications. See Defining Applications for application properties.

  3. Save your changes.

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 SAP mobile service cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.
  2. Select an application and click Delete.
  3. Click OK to confirm.

    Note

    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 SAP mobile service 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.

Managing a Single Application

A single-app version of SAP mobile service cockpit is available for Cloud Foundry. This enables a Business User to manage a single Cloud Foundry application, for example, within a Software as a Service (SAAS) context. The scope of single-app support includes Native, Hybrid, Micro App, and SAP Mobile Cards. The feature is only available for Cloud Foundry, and requires that the application has been migrated to a single service.

The following roles are related to the SAP Business Technology Platform cockpit. To learn more about setting roles and role collections see Building Roles and Role Collections for Applications.

  • Administrator ‒ read-write role. The Business User must be assigned the Administrator role.

  • Helpdesk ‒ read-only role.

Access to the single-app SAP mobile service cockpit is via a specific cockpit URL. The URL is in the format: https://<mobile_application_url>/mobileservices/Admin

For example, if the URL for the com.sap.myApp application is http://mobile-tenant1-groupX-tenant-com-sap-myapp.cfapps.sap.hana.ondemand.com, then the application is accessible at: https://mobile-tenant1-groupX-tenant-com-sap-myapp.cfapps.sap.hana.ondemand.com/mobileservices/Admin.

Tip

You can find the <mobile_application_URL> by navigating to the APIs tab, and copying the server URL.

Regular SAP mobile service cockpit access is only possible as a Platform User. The Platform User can also log in to the SAP Business Technology Platform cockpit, and is a member of the sub-account, organization and space.

The Business User, on the other hand, is authenticated against the Trust provider that is configured in the SAP Business Technology Platform sub-account. The Business User does not require general access to SAP Business Technology Platform accounts.

The functionality of the Business User is restricted. Because the logged in user is not allowed to perform actions on SAP Business Technology Platform accounts, Mobile Services cannot run operations that require interaction with the SAP Business Technology Platform infrastructure and other services. For example, the Business User cannot create a new application, which installs a new application route in the space; or change security settings, which would re-create the XSUAA (Security) Service Instance.

You'll notice these differences when using SAP mobile service cockpit as a Business User:

  • The left navigation pane no longer appears, and the navigation breadcrumbs are abridged, since there is only one app to manage.

  • The Delete, Export, and Lock operations no longer appear.

  • Several assigned features no longer appear, including Mobile App Catalog and Mobile Cloud Build.

  • The Discovery tab no longer appears.

  • On the Info tab under Application Details, the License Type does not appear, and Custom Domain is read only.

  • On the Security tab, the OAuth Settings and Role Settings are read only.

  • On the Logs tab, you can view event logs only for the single application.

Other than these basic differences, most SAP mobile service cockpit operations are the same for the single-app version.

  1. Access the single-app SAP mobile service cockpit from a browser using the cockpit URL in the format: https://<mobile_application_url>/mobileservices/Admin, as described above in Context.

    For example, https://mobile-tenant1-groupX-tenant-com-sap-myapp.cfapps.sap.hana.ondemand.com/mobileservices/Admin. You are prompted to log in, and then SAP mobile service cockpit appears with the single application.

  2. Use the SAP mobile service cockpit to manage the application and its assigned features, keeping in mind the differences and restrictions mentioned above in Context.


Last update: September 27, 2021