Skip to content

Enabling Mobile Services

In SAP mobile service cockpit, set up developer and customer accounts.

Procedure for Trial Environments

Create an SAP Business Technology Platform Trial account and enable the mobile services service.

  1. In your browser, navigate to the SAP Business Technology Platform web site and click Start free Trial.
  2. Register for your Trial account. When you click Submit, you'll receive a confirmation message indicating that an activation link has been sent to your email account.
  3. Open the activation email and click the activation button.
  4. Log in to the SAP Business Technology Platform with your new account credentials. You'll be prompted to upgrade your account.
  5. Complete the Upgrade Account dialog and click Register. The SAP Business Technology Platform cockpit opens. SAP Business Technology Platform Trial
  6. Click the Enter Your Trial Account button on the SAP Business Technology Platform cockpit homepage. You are redirected to your Subaccount overview page.
  7. Navigate to your Subaccount by clicking the trial tile.
  8. Navigate to your development space by clicking the dev space.
  9. In the left-hand menu, choose Services > Service Marketplace.
  10. Search for mobile services and click on it.
  11. Click Support to open the SAP mobile service cockpit
  12. Choose your trial organization and dev space from the drop-down list, then click Open.
  13. You are now logged in to your trial SAP mobile service cockpit.

Enable Developer Accounts

A developer account allows you to explore the basic functionality of SAP Mobile Services. A developer account is also called a trial account, and access is open to everyone. As a mobile services developer, you may wish to test your applications in an end-to-end environment. A developer trial account gives you access to administrative features to help you do that. To learn more about the developer trial account, see Getting a Global Account and Getting Started with a Trial Account in the Cloud Foundry Environment.


Please be aware that trial accounts are restricted in usage. For example:

  • Trial length = 12 months
  • Total apps that can be created = 10
  • Total destinations per app = 5
  • Total user registrations per app = 3

Other restrictions may apply. Service Plans provides additional information.

The procedure to enable mobile services for developer trial accounts is identical to the procedure in Procedure for Production Environments.

When you select a space and log in, SAP mobile service cockpit performs a health check and informs you of configuration problem such as:

  • Missing core services
  • Missing mobile services
  • Exceeding instance limit threshold
  • Exceeding memory limit threshold

This enables you to figure out setup problems right away.

Procedure for Production Environments

An SAP Mobile Services customer account allows you to support production, business-critical applications. A customer account is also called a production account.

To explore and use the powerful capabilities of SAP mobile service cockpit, verify that you:

  • Have purchased a license for SAP Mobile Services.

  • Have a single user within your organization that has access to the global account, and is known as an administrator. This user has full access to SAP Business Technology Platform Cockpit and can assign subscriptions for SAP mobile service cockpit to your organization's SAP Business Technology Platform account.

  • Have one Global Account and at least one Subaccount in a Cloud Foundry Infrastructure. See Getting Started with an Enterprise Account in the Cloud Foundry Environment to verify.

  • Know whether Feature Set A or Feature Set B is assigned to your global account. To find out, right click your user name in the upper right corner of SAP Business Technology Platform cockpit, and select About. The Cloud Management Tools property identifies your assigned feature set. To learn more about feature sets, see Cloud Management Tools – Feature Set Overview.

  • Have basic knowledge of Cloud Foundry entitlements and quotas, and mobile services quotas. See Mobile Services Quotas.


Do not change any of these settings.

To set up the SAP mobile service cockpit and integrate it into your internal landscape, a super administrator must perform the following steps.

  1. Log in to your SAP Business Technology Platform Global Account, and navigate to the menu option Subaccount Assignments under Entitlements.

  2. Select the Subaccount for which you want to enable mobile services. If you haven't yet created a Subaccount, go to the menu option Subaccounts and create a new account first.

  3. Click on Configure Entitlements and select Add Service Plan.

  4. Select Application Runtime and Mobile Services. Depending on your license, mobile services might show up with two different service plans, "b2c" or "standard". Even though you can use both from one Subaccount, please only select the one you would like to use. The plans are charged for differently. See Service Plans to familiarize yourself with the price plans before using the service plans.

  5. Set the Subaccount Assignment for "mobile services" to 1 unit.

  6. Determine whether you need to assign additional Application Runtime to the Subaccount. The mobile services need at least 1GB (smallest unit) of Application Runtime assigned to the Subaccount. Application Runtime also controls routes and services instances. See Mobile Services Quotas for additional information.

  7. If you have not yet done so, create a Space and add Space Members using information provided in Managing Spaces. You'll need to be aware of whether your account uses Feature Set A or Feature Set B.

    Once the Space is created and set up, navigate to the Space and click on Service Marketplace in the left menu. A tile for Mobile Services should appear. If this is not the case then restart and ensure the right Subaccount is selected.


    If you're a Cloud Foundry space member administrator, your space member roles also apply when you access SAP mobile service cockpit. This enables you to apply role management as expected for all application types (Native/Hybrid, SAP Mobile Cards, and App Catalog), for example:

    • Space Developer role ‒ read and write access to mobile services.
    • Space Auditor role ‒ read access to mobile services.
    • Space Manager role ‒ read access to mobile services.

    For more information about Cloud Foundry default roles, see Organizations, Spaces, Roles, and Permissions.


    Although a Space Manager or Org Manager can assign self or others the Space Developer role, the Space Developer role is read-only, unless the Space Manager or Org Manager is also assigned the Space Developer role.

    By default, business users who don't have access to mobile services can't log in, and see the message You are not authorized for access. As the administrator you, can unselect Restrict to authorized users to enable read access for these users.

    Following are default Space roles for mobile services.

    Mobile Services Space Roles

    SAP Business Technology Platform Role Permissions Description (related to mobile services)
    Administrator read-write Space Developer ‒ manage your apps, services, and space-scoped service brokers in a space.
    Help Desk read-only Combines: Space Manager (administer a space within an org); Space Auditor (read-only access to a space); and Org Manager (administer the org).
  8. To access SAP mobile service cockpit, select Mobile Services in the Marketplace and click on the Support link shown in the service details. Or, create an instance or use an existing service instance, and open the dashboard link shown for each service instance.

    See the complete list of SAPUI5 supported browsers on SAP Help Portal.

    If a SAP mobile service cockpit session times out and displays a blank screen, refresh or restart the browser.

  9. (Optional) To access on-premise back ends, install and configure SAP Cloud Connector. See Installation.


    In SAP mobile service cockpit, configure on-premise HTTPS back-end connections as HTTP using the virtual host address. Communication between the cloud and your on-premise SAP Cloud Connector is secure. Communication between SAP Cloud Connector and your back-end system uses standard HTTPS security.

    1. In SAP Cloud Connector, verify that necessary back-end service URLs are allow-listed. Every on-premise URL that is configured in SAP mobile service cockpit, such as application endpoints or the security configuration, must be allow-listed. See Configure Access Control (HTTP).

    2. Generate a system certificate and import it into SAP Cloud Connector. See Initial Configuration (HTTP).

  10. Access one of the SAP mobile service cockpit URLs described in step 8.


    When you select a space and log in, SAP mobile service cockpit performs a health check and informs you of configuration problem such as:

    • Missing core services
    • Missing mobile services
    • Exceeding instance limit threshold
    • Exceeding memory limit threshold

    This can help you figure out setup problems. If a warning appears, return to the Entitlements section and try to fix the issue. Ignoring the warnings can lead to unexpected results.

  11. Create an application in SAP mobile service cockpit. See Configuring Applications.

Mobile Services Quotas

Describes how mobile services consumes Cloud Foundry Application Runtime. Use this information to analyze your requirements, and configure your quota plan for mobile services.

Basic Consumption

SAP Mobile Services creates one route and two service instances in a customer Space. SAP Mobile Services also creates some additional routes and service instances for system mobile apps (such as SAP Mobile Cards, mobile transaction bridge and Mobile App Catalog), and one Cloud Foundry application, BindMobileApplicationToMe, to which all routes are bound. Each of the system mobile apps holds one route and two service instances.

In summary, to create N mobile apps in mobile services requires:

  • 128MB memory

  • N+3 app routes

  • 2 * (N+3) service instances

In the Cloud Foundry environment, a quota of memory, routes and service instances is assigned per application runtime unit. One runtime unit is typically 1GB memory + 10 routes + 100 service instances. (For some old subaccounts, one runtime unit is 1GB memory + 10 routes + 10 service instances). Please refer to the platform documentation for information about mapping the application unit to memory, routes and service instances.

Consumption Example

If your account's application runtime = 1GB memory + 10 routes + 100 service instances, you need the following to create N mobile apps:

Application runtime units = Ceil( Max( (N+3)/10, (N+3)*2/100, 128M/1GB)

For example:

  • Units = 1 when N = 1, 2, 3, ... 7

  • Units = 2 when N = 8, 9, 10, ... 17

  • When N = 10, Max (1.3, 0.26, 0.128) = 1.3 ~= 2

Service Plans

Describes the service plans that are available for SAP Mobile Services. Use this information to analyze your requirements and select the right plan. The terms license type and service plan are used interchangeably.

Service Plans for mobile services

Service Plan Description Comments
Free This service plan is for mobile services in a non-trial landscape. No feature limitations, but quota limits apply: (1) Maximum of 10 apps, up to three users each, (2) Maximum destinations per app: 5, (3) Maximum concurrent requests per destination: 5, (4) Maximum request payload size: 1048576 MB, and (5) Cannot send a push message to the same registration within two minutes. Additional restrictions may apply. Note that only community support is available for free tier service plans and these are not subject to SLAs.
Lite This service plan is for mobile services in a trial landscape. Same as Free.
Users Billing is based on registered users. A named user is an individual who is authorized to access the cloud service. Users may be employees of customers or customer affiliates, or business partner users. No feature limitations. A registered user is a current named user that is associated with device registrations and application connections. At the beginning of each month, all registered user hashes are sent to our internal metering system. New registered user hashes are sent in the following days of the month. If a user is de-registered during the month, it is still counted in the current month and will not be counted in the next month. Users are considered registered until they de-register, whether they use the service during the month or not. A user is counted once if he or she uses the same user under multiple subaccounts.
Consumer Edition Billing is based on active users. An active user is an individual user of a platform application that connects to the cloud service at least once during any rolling three-month period. No feature limitations. Unlimited users and apps. An active user is a user who has accessed mobile services within the calendar month. Every day, user name hashes are sent to our internal metering service for every user who has accessed mobile services during the day. Each calendar month, cloud reporting and billing systems run distinction and aggregation processes for the user name hashes to get the final number of active users for the month. A user is counted once if he or she uses the same user under multiple subaccounts.

Next Steps

Last update: July 30, 2021