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.
- In your browser, navigate to the SAP Business Technology Platform web site and click Start free Trial.
- 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.
- Open the activation email and click the activation button.
- Log in to the SAP Business Technology Platform with your new account credentials. You'll be prompted to upgrade your account.
- Complete the Upgrade Account dialog and click Register. The SAP Business Technology Platform cockpit opens.
- Click the Enter Your Trial Account button on the SAP Business Technology Platform cockpit homepage. You are redirected to your Subaccount overview page.
- Navigate to your Subaccount by clicking the trial tile.
- Navigate to your development space by clicking the
- In the left-hand menu, choose Services > Service Marketplace.
- Search for mobile services and click on it.
- Click Support to open the SAP mobile service cockpit
- Choose your trial organization and
devspace from the drop-down list, then click Open.
- You are now logged in to your trial SAP mobile service cockpit.
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.
Log in to your SAP Business Technology Platform Global Account, and navigate to the menu option Subaccount Assignments under Entitlements.
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.
Click on Configure Entitlements and select Add Service Plan.
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. Please familiarize yourself with the price plan before using the service plans.
Set the Subaccount Assignment for "mobile services" to 1 unit.
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.
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 usersto 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).
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.
(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.
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).
Generate a system certificate and import it into SAP Cloud Connector. See Initial Configuration (HTTP).
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.
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.
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:
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.
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)
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
- Managing Apps
- Getting started with the SAP BTP SDK for Android
- Getting started with mobile back-end tools
- Native Push Notification for a Back End
- REST API Application Development Overview
- Administration Troubleshooting