PUBLIC SAP HANA Cloud Platform Mobile Services

Transcription

1 1.3 Document Version: PUBLIC SAP HANA Cloud Platform Mobile Services

2 Content What's New Getting Started with Setting up an Developer Account....7 Setting up an Customer Account Administrator Overview Logging and Tracing Overview Application Usage Reporting Overview Offline Applications Overview Discovery Services Overview User Interface Push Overview Application Administration Security Administration Troubleshooting: Common Issues REST API Application Development Overview Set Up the Development Environment Configure Applications in Mobile Services Cockpit Application Development using REST API Reference Migration Migrating to Glossary: SAP SE or an SAP affiliate company. All rights reserved. Content

3 1 SAP HANA Cloud Platform Mobile Services SAP HANA Cloud Platform is an open, standards-based cloud platform that enables simple mobile application development, configuration, and management. 1.1 What's New New features and feature enhancements in SAP HANA Cloud Platform mobile services. Feature Type of Change Description Capability-based Push Support New SAP HANA Cloud Platform mobile services and SAP Mobile Platform now provide capability-based push support. This enables you to send push notifications to devices with a particular capability, rather than to individual applications. Changes include: A new form factor flag identifies the device type. This flag is sent from the device to the platform via the application connection during onboard registration. A new Capability API for pushing notifications to all application connections that match a certain capability name. If a device uses a wildcard for the capability name, the platform uses the form factor to help direct the notification (otherwise, the form factor is ignored). Documented in: SAP HANA Cloud Platform Mobile Services > Administrator. See Push Overview. SAP HANA Cloud Platform Mobile Services > REST API Application Development Overview. See: 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Feature Type of Change Description Push API Notification Scenarios in the Application Development using REST API section. Push-to-Capability Scenario also in the Application Development using REST API section. Create Application Connection with Capability Handling in the Reference section. Capability handling for application connections New Registration services have been updated to support capability handling and the form factor. Documented in: SAP HANA Cloud Platform Mobile Services > Reference. See the Create Application Connection with Capability topic group. Actionable push support for ios New The ios actionable push feature pushes notifications to users, and enables them to take action without changing focus. SAP HANA Cloud Platform mobile services support includes: New headers The headers provide non-sap gateway notification (X-SMP-APNS-CATEGORY, X-SMP-APNS-CONTENT-AVAILABLE), and SAP gateway notification (X-SAP- POKE-CATEGORY, X-SAP-POKE- CONTENT_AVAILABLE). New parameters The Category and Content-Available parameters are customparameters elements: "apns.category" and "apns.content-available". Actionable push notifications can be sent through SAP HANA Cloud Platform mobile services and SAP Mobile Platform directly, or via Push Hub. Documented in: SAP HANA Cloud Platform Mobile Services > REST API Application Development Overview. See topics: Push API Notification Scenarios, Notification Data Sent Through HTTP Headers, SAP Gateway Notification Support SAP SE or an SAP affiliate company. All rights reserved.

5 Feature Type of Change Description HCP SCIM and HCPms SCIM support for Basic Authentication CSV file download for usage analytics OAuth security configuration support New New New You can configure SAP HANA Cloud Platform SCIM and SAP HANA Cloud Platform mobile services SCIM to connect and manage user identities in external cloud or on-premise applications. Documented in: SAP HANA Cloud Platform Mobile Services > Administrator > Security Administration >Application Authentication >Configuring Basic Authentication. See topics: Configuring SAP HANA Cloud Platform SCIM Specification, Configuring SAP HANA Cloud Platform mobile services SCIM Specification. You can download a CSV file that contains usage analytics data. You can import the file to Lumira, Excel, and so on. Documented in: Administrator > Application Administration > Managing and Monitoring Applications > Reporting Usage Statistics You can now authenticate hybrid applications using the OAuth protocol, which uses. OAuth access tokens as credentials. Documented in: Administrator > Security Administration > Application Authentication > Configuring OAuth Authentication Same-origin policy New You can now allow or disallow cross-origin resource access in your application by enabling or disabling the same-origin policy in the Mobile Services Cockpit. Documented in: Administrator > Application Administration > Configuring Application > Defining Applications. REST API Application Development Overview > Reference > CORS-Enabled Browser-Based Applications. Supported Browsers An overview of supported browsers SAP SE or an SAP affiliate company. All rights reserved. 5

6 Note Mac OS on Mac OS, Safari is supported in version 5.1 or higher. Windows Touch is supported as of Windows 8. Multiple browsers cannot share the Cross-Site Request Forgery (CSRF) token. Ensure that only one browser tab or window is performing create, read, update, and delete (CRUD) operations. If the Mobile Services Cockpit session times out and displays a blank screen, refresh or restart the browser. Table 1: Browser Supported Prerequisites Internet Explorer Version 11 or higher Before you start the browser, ensure that the process iexplorer.exe does not exist in Task Manager, or, Open a new Internet Explorer browser window to log in and perform create, read, update, and delete operations. Mozilla Firefox Latest version and Extended Support Release. Before you start the browser, ensure that the process firefox.exe does not exist in Task Manager. Google Chrome Latest version Before you start the browser, ensure that the process chrome.exe does not exist in Task Manager, or, Safari No NA Opera No NA Use private browsing (incognito window) or use the Chrome - Wrench (tools) menu. For a complete list of SAP UI5 supported browsers, see helpdata/en/91/f079dc6f4d1014b6dd926db0e91070/content.htm. 1.2 Getting Started with SAP HANA Cloud Platform Mobile Services SAP HANA Cloud Platform mobile services offers authentication, secure on-boarding, native push notifications, and reporting capabilities for enterprise mobile applications. Mobile Services Cockpit provides a SAP SE or an SAP affiliate company. All rights reserved.

7 single comprehensive Web administration and monitoring portal for configuring and managing mobile applications Setting up an SAP HANA Cloud Platform Mobile Services Developer Account A developer account allows you to explore the basic SAP HANA Cloud Platform mobile services functionality. Access is open to everyone. The developer account is also called as trial account. Context For information about how to register and create a developer account, see Signing Up for a Developer Account. Procedure 1. Log in to 2. Subscribe your account to HTML5 application. a. Select Subscriptions from navigation pane. b. Select New Subscription. Select Application Name: hcpmsadmin and Provider Account: sapmobile. c. Click Save. 3. Assign the new or existing role to the predefined HanaMobileAdmin permission of your HTML5 application subscription. To assign the new or existing role: a. Select hcpmsadmin application. The Application Permissions section lists all permissions defined for the selected application. b. Choose Edit. c. To assign the role to the HanaMobileAdmin permission, select the appropriate role from the drop down. Save your entries. By default AccountDeveloper role is assigned in trial landscape and should be able to access Mobile Services Cockpit. 4. Assign custom roles to individual users and groups: a. Enter the Roles section. b. Select the role you want to manage assignments for. c. To assign a new user or group, choose Assign for the Users or Groups section respectively. d. Enter the user or group name. e. Save the changes. 5. Subscribed your account to JAVA application and assign roles. a. In the navigation area for the cockpit, choose Services SAP SE or an SAP affiliate company. All rights reserved. 7

8 b. Select, select Enable. c. To assign administrator role for performing all administrative operations in Mobile Services Cockpit, choose Configure Roles icon, select Administrator, and assign a user ID (SCN user name) to it. To assign notification user role for sending push notifications to the applications using Rest services, choose Configure Roles icon, select Notification User, and assign a user ID (SCN user name) to it. Note For more information on sending push notifications using REST API, see Native Push Notification for a Back End in REST API Application Development. To assign read-only administrator privileges for viewing all administrative operation in Mobile Services Cockpit, select Helpdesk and assign user ID to it. Note Helpdesk operator interacts with SAP HANA Cloud Platform mobile services to review system information and determine root cause of the reported problems. 6. For application connections such as onboarding, use base URL: <scn_username>trial.hanatrial.ondemand.com/ 7. For Mobile Services Cockpit, use base URLs: <scn_username>trial.dispatcher.hanatrial.ondemand.com/. The application URL for Mobile Services Cockpit can also be accessed from HTML5 Subscription Dashboard > Active Version Setting up an SAP HANA Cloud Platform Mobile Services Customer Account A customer account allows you to host productive, business-critical applications with 24x7 support using SAP HANA Cloud Platform mobile services. A customer account is also called as productive account. Prerequisites To explore and use the powerful capabilities of Mobile Services Cockpit, ensure: You have purchased the license for SAP HANA Cloud Platform mobile services and received an notification that the SAP HANA Cloud Platform mobile services has been configured for your account. SAP has performed below mentioned settings to enable SAP HANA Cloud Platform mobile services for your account: Subscribed your account to HTML5 Application Name: mobile available under Provider Account: hanamobileprod. Subscribed your account to JAVA Application Name: mobilejava available under Provider Account: hanamobileprod SAP SE or an SAP affiliate company. All rights reserved.

9 Enabled Principal Propagation property under Trust > Local Service Provider. A single user within your organization is assigned with super administrator rights. Super administrator has full access to SAP HANA Cloud Platform Cockpit and the subscription of Mobile Services Cockpit into your organization's HANA Cloud Platform account. Being a super administrator of your organization, you need to perform the following steps for the initial setup of Mobile Services Cockpit to integrate it into your internal landscape. Note Do not change any settings mentioned above configured by the SAP. Procedure 1. Log in to SAP HANA Cloud Platform Cockpit. Select Services in the left navigation pane. Ensure that Mobile Services Cockpit is enabled for your account. 2. Select > Overview. Assign the required privileges to the users to access Mobile Services Cockpit: a. For Java application subscription: 1. Under Service Configuration, select Configure > Roles. 2. Select Administrator and assign a user ID to it. b. For HTML5 application subscription: By default AccountAdministrator role is mapped to HanaMobileAdmin permission of your HTML5 application subscription and user should be added as Administrator member to your account. 1. In the HANA Cloud Platform Cockpit pane, select Member and add new user as Administrator. If you do not wish to add Mobile Services Cockpit user as Administrator to your account, skip to the next step. 2. Assign the new or existing role to the predefined HanaMobileAdmin permission of your HTML5 application subscription. To assign the new or existing role: 1. Select mobile HTML5 subscription. The Application Permissions section lists all permissions defined for the selected application. 2. (Optional) To create a new role: 1. Go to Roles. 2. Select New Role... and assign role name SAP SE or an SAP affiliate company. All rights reserved. 9

10 3. Choose the new role name and select Save. 4. Select the new role name and choose Assign... and assign user ID to it. 5. Select Overview. 3. Choose Edit under Application Permissions. 4. To assign the role to the HanaMobileAdmin permission, select the newly created or existing role from the drop down. Save your entries. 3. To assign notification user role for sending push notifications to the applications using Rest services, go to the SAP HANA Cloud Platform mobile services Java application subscription, select Notification User in Roles and assign a user ID to it. Note For more information on sending push notifications using REST API, see Native Push Notification for a Back End in REST API Application Development. To assign read-only administrator privileges for viewing all administrative operation in Mobile Services Cockpit, select Helpdesk and assign user ID to it. Note Helpdesk operator interacts with SAP HANA Cloud Platform mobile services to review system information and determine root cause of the reported problems. 4. For application connections such as onboarding, use one of the following base URLs: if your account is in hana.ondemand.com host. if your account is in us1.hana.ondemand.com host. if your account is in ap1.hana.ondemand.com host. 5. For Mobile Services Cockpit, use any one of the following URLs: if your account is in hana.ondemand.com host. if your account is in us1.hana.ondemand.com host. if your account is in ap1.hana.ondemand.com host. 6. (Optional) To access the on-premise back end, install and configure Cloud connector. See Installing the Cloud Connector Note In Mobile Services Cockpit, ensure that on-premise HTTPS back-end connections are specified as HTTP when you configure them using the virtual host address. The communication from the cloud to your on-premise cloud connector is secured. The communication from cloud connector to your backend still uses standard HTTPS security SAP SE or an SAP affiliate company. All rights reserved.

11 a. In Cloud connector make sure you have whitelisted necessary back-end service URLs. Every onpremise URL that is configured in Mobile Services Cockpit, such as application endpoints or the security configuration, must be whitelisted in Cloud connector. See Configuring Access Control (HTTP). b. Generate a system certificate and import it in the Cloud connector. See Installation of a System Certificate for Mutual Authentication. 7. Select the Mobile Services Cockpit URL provided in step Create an application in Mobile Services Cockpit. See Configuring Applications in Administrator. 9. Use the REST client to test application configuration. See REST API Application Development Overview. 1.3 Administrator Administrators interact with SAP HANA Cloud Platform 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 HANA Cloud Platform security features used for mobile applications. Overview [page 13] SAP HANA Cloud Platform mobile services provides services to mobile applications, such as application analytics, app resources, onboarding, HTTP/HTTPS configuration and so on. Logging and Tracing Overview [page 14] SAP HANA Cloud Platform mobile services provide supportability through logs and traces that enable administrators, developers, and support professionals to troubleshoot application issues. All logs use a common format and are stored in the server database. All log entries for a particular business or application flow (such as an OData request or a registration) are correlated across the client and server stack, providing an end-to-end flow, which helps identify the source of an application problem. Application Usage Reporting Overview [page 14] 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

12 You can collect standard usage information for applications, and view reports based on information logged by clients and uploaded to the server. Offline Applications Overview [page 15] Offline support enables client applications to access back-end data without establishing a connection to the back end. Discovery Services Overview [page 17] The SAP Discovery Service provides the configuration information necessary for a user to enroll a device with SAP Mobile Secure. This service enhances the user onboarding process by letting you distribute initial configuration data to mobile apps. User Interface [page 18] Frequently used icons in Mobile Services Cockpit. Push Overview [page 18] Use the push feature to push updates from the back-end data source to applications that are running on mobile devices. The back-end can also push notifications to apps that provide a certain capability or have a specific form factor, rather than to particular applications. Application Administration [page 19] 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. Security Administration [page 73] The security landscape for SAP HANA Cloud Platform mobile services includes application authentication, transport and session security, and data protection and privacy. Troubleshooting: Common Issues [page 82] Overview of common issues. Related Information Application Administration [page 19] Security Administration [page 73] SAP SE or an SAP affiliate company. All rights reserved.

13 1.3.1 Overview SAP HANA Cloud Platform mobile services provides services to mobile applications, such as application analytics, app resources, onboarding, HTTP/HTTPS configuration and so on. Mobile application services consist of the following: Application Analytics usage statistics that can be displayed graphically in Mobile Services Cockpit. App Resources containers of dynamic configurations, styles, or content that can be downloaded by native applications. Onboarding authentication of users who are registering through SAP Mobile Place. HTTP/HTTPS Configuration open standards for client communications. Lifecyle Management managing and deploying multiple versions of an application. Offline OData Service optimizes data transport between the back end and the client offline store. Push Notifications native notifications sent from back-end systems to the server, which forwards them on to the clients. Mobile Services Cockpit deploying, managing, and monitoring applications. Supportability logs for monitoring system health and troubleshooting. SAP HANA Cloud Platform mobile services can expose on-premise back-end services through SAP Cloud Connector, and on-demand back-end services directly. HANA Cloud Platform security enables you to use an on-premise identity management system for on-demand applications. You can use basic authentication using LDAP, or form-based application authentication using SAML. All configuration and runtime data is persisted in an SAP HANA database SAP SE or an SAP affiliate company. All rights reserved. 13

14 1.3.2 Logging and Tracing Overview SAP HANA Cloud Platform mobile services provide supportability through logs and traces that enable administrators, developers, and support professionals to troubleshoot application issues. All logs use a common format and are stored in the server database. All log entries for a particular business or application flow (such as an OData request or a registration) are correlated across the client and server stack, providing an end-to-end flow, which helps identify the source of an application problem. System logs collect log messages that allow administrators and support professionals to identify problem areas. Developers can identify code problems by capturing debug level log messages. You can control the amount of information that is captured by setting the log level for individual logging components.application tracing captures additional business data for a request (such as message data, HTTP headers, and URIs), which you can use to troubleshoot application problems. The business data captured in application traces is determined by the application developer. Enable tracing for individual logging components on an as-needed basis. Logs and traces are automatically synchronized with the server when an application is launched or switched to foreground or background on the client. Related Information Setting Log Levels [page 66] Enabling Application Traces [page 67] Viewing Logs and Traces [page 69] Application Usage Reporting Overview You can collect standard usage information for applications, and view reports based on information logged by clients and uploaded to the server. All records collected from the device are tagged with the following attributes: Application: application bundle ID and version Device and operating system: operating system platform, platform version and device model name User sessions: an instance of application running in the foreground The administrator has complete control over the usage reports upload in the SAP HANA Cloud Platform mobile services, and can view reports and carry out necessary operations. Enable Usage Collection for an Application The administrator can configure the uploaded records in the server remotely using Mobile Services Cockpit and optimize them using WiFi. This process minimizes the impact of usage collection on the end user's cellular data plan SAP SE or an SAP affiliate company. All rights reserved.

15 Enable Application-Specific Columns in the Database The administrator can enable developer-defined usage report collection in Mobile Services Cockpit, and enable or disable the creation of application specific columns in the database on per-application basis. The application developer must include a reporting library where a standard set of information is captured for every application. If developers have developed custom information to be logged, you can collect that information as well. Set the Maximum Threshold for Storing Records The administrator can set the maximum number of client records to be stored on devices. On exceeding this limit, data is uploaded over cellular data. Related Information Enabling Usage Report Policy [page 32] Reporting Usage Statistics [page 64] Offline Applications Overview Offline support enables client applications to access back-end data without establishing a connection to the back end. You might want to run applications offline to: Improve performance by accessing offline data instead of sending data requests to SAP HANA Cloud Platform mobile services. Enable users to continue to use applications when there is intermittent network coverage. Support business processes that must be executed by a user while the application is offline. To work offline, an application must initialize an offline store, which stores data that the application can access when it is offline. SAP HANA Cloud Platform mobile services provides an Offline OData Service that moves data between the back end and the client offline store SAP SE or an SAP affiliate company. All rights reserved. 15

16 SAP HANA Cloud Platform mobile services retrieves data from an OData producer that is running in a back end, and from that data creates an inital database on the client. On an ongoing basis, SAP HANA Cloud Platform mobile services updates the client database based on changes, or deltas, that have been made to the data on the back end. Deltas between the back-end data and the client data are identified either by the back end or by SAP HANA Cloud Platform mobile services. You can configure offline applications to optimize offline performance by defining: Column indexes for the client database Common user data to cache on the server to reduce the amount of data that needs to be synchronized with the back end. When an application is offline, it accesses data from the offline store. Any updates that are made while the client is offline are stored locally and become pending updates for the back end. When the client comes back online, SAP HANA Cloud Platform mobile services updates the back end by processing the pending updates. Related Information Configuring Offline Settings for Applications [page 28] SAP SE or an SAP affiliate company. All rights reserved.

17 1.3.5 Discovery Services Overview The SAP Discovery Service provides the configuration information necessary for a user to enroll a device with SAP Mobile Secure. This service enhances the user onboarding process by letting you distribute initial configuration data to mobile apps. Ensure that the application developer has added the Discovery Service to the application, a procedure that is documented in SAP Mobile Platform SDK > Native OData Application Development > XXX Applications > Developing with MAF Logon for XXX > Onboarding with SAP Mobile Place. Note 'XXX' refers to the platform name, such as, ios, Android, or Windows. After the Discovery Service is added to the application, use the Mobile Services Cockpit to publish application configurations to the SAP Discovery Service, on which mobile applications can find their connection settings. Related Information Enabling Applications to Discover Configurations [page 46] 2015 SAP SE or an SAP affiliate company. All rights reserved. 17

18 1.3.6 User Interface Frequently used icons in Mobile Services Cockpit. Table 2: Icon Purpose Description New Add a new item, for example, an application. Sort Home Sort applications based on a criteria, for example, Registration ID. Go to the Mobile Services Cockpit home screen. Log out Log out of the application Push Overview Use the push feature to push updates from the back-end data source to applications that are running on mobile devices. The back-end can also push notifications to apps that provide a certain capability or have a specific form factor, rather than to particular applications. You can use SAP Mobile Platform or SAP HANA Cloud Platform mobile services to manage push for individual applications that use native notifications, or you can use SAP HANA Cloud Platform mobile services push hub to manage push for applications that are distributed via a public applications store and used by many enterprise users. Developers enable native push notification in the application code, and link the certificate with the mobile application at build time. Users download the application from a market place, such as Apple Store, Google Play, or similar service, and, when a change occurs in the back end, a push notification is sent to mobile applications on devices with push enabled. Push Notification For native mobile applications, SAP Mobile Platform or SAP HANA Cloud Platform mobile services manages the certificates, tokens, and push notifications for individual applications. When changes occur, the back end sends push notifications to mobile applications on devices that are push enabled. Push Hub For mobile applications that are distributed via a public app store and used by many different enterprise customers, SAP HANA Cloud Platform mobile services push hub manages push notifications for multiple applications SAP SE or an SAP affiliate company. All rights reserved.

19 Capabilities-based Push Support Capabilities-based push enables a back-end to trigger a push to applications that provide a certain capability. Developers configure application connections to handle capabilities using the REST API (see REST API Application Development). Devices send capability type information during registration or update. SAP HANA Cloud Platform mobile services maintains the mapping between capabilities and applications. Device-type (form factor) Support Devices send device type information to the server during registration. Device types are categorized into groups using the form factor property. The client can use any non-empty string for the device type (case insensitive), such as SmartPhone, phone, Watch, desktop, and so forth. Configuration of Capabilities Application capabilities are part of the central application connection configuration. Similar to how the administrator controls some device capabilities from the server through feature policies, users control some application capabilities from the device. Device capabilities are controlled by the application and sent to the server. The capabilities are exchanged between the mobile app as part of the registration and settings exchange. Through that mechanism, the mobile app can also override default capabilities. This gives users more control, enabling them to turn off certain capabilities for a mobile app instance, which translates into turning off native push notifications for a certain action into a particular application. Push can still be offered, but at the capability level, rather than individual application level. Actionable Push With ios 8, Apple supports actionable push notifications. The push API offered with SAP Mobile Platform and HANA Cloud Platform mobile services has been enhanced to support this feature. Using the API, the back end provides the capability for back ends to send the push 'category' through the platform to the device. This change applies to ios only; for Android actionable push is fully controlled on the device by the app 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 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

20 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 HANA Cloud Platform mobile services. Web applications are running on-premise, but securely exposed through SAP Mobile Platform or SAP HANA Cloud Platform 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, through enterprise Web site downloads, or through Afaria. 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. Configuring Applications [page 20] Create an application definition that enables you to manage the application using Mobile Services Cockpit. The application definition includes a unique application identifier, connections to the back-end data source, and optionally, other application-specific settings. Enabling Applications to Discover Configurations [page 46] Using Mobile Services Cockpit, you can publish application configurations to the SAP Discovery Service, on which mobile applications can find their connection settings. You can update or delete published configurations at any time. Managing and Monitoring Applications [page 49] Use Mobile Services Cockpit to manage applications, registrations, users, back-end connections to the data source; view application usage statistics; and manage and view application reports Configuring Applications Create an application definition that enables you to manage the application using Mobile Services Cockpit. The application definition includes a unique application identifier, connections to the back-end data source, and optionally, other application-specific settings. To configure an application, provide a back-end URL. Other settings are optional. Defining Applications [page 21] Create a new native, hybrid, or Web application definition, which enables you to use Mobile Services Cockpit to manage the application. Defining Back-End Connections [page 23] Define a back-end connection for the selected application (native, hybrid, or Web). Configuring Offline Settings for Applications [page 28] (Does not apply to Web applications) 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 HANA Cloud Platform mobile services moves data between the back end and the client offline store. Defining Client Policies [page 29] (Does not apply to Web applications) Set policies related to client password and log management for a particular application on a device SAP SE or an SAP affiliate company. All rights reserved.

21 Defining Push Notifications [page 33] (Does not apply to Web applications) Configure push-related settings for the selected application. Uploading Client Resources [page 37] Upload client resources, or resource bundles, for the selected application. Resource bundles are containers used by applications to download dynamic configurations, styles, or content from the SAP HANA Cloud Platform mobile services. The administrator can modify the client resource bundle settings in Mobile Services Cockpit. Defining Application-Specific Settings [page 38] (Hybrid apps only, optional) Configure application-specific settings for the selected application, using Mobile Services Cockpit, configuration files, or other tools. Saving Application Settings [page 45] Save application settings Defining Applications Create a new native, hybrid, or Web application definition, which enables you to use Mobile Services Cockpit to manage the application. Procedure 1. In Mobile Services Cockpit, select Applications, and click. 2. Enter: 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

22 Table 3: Field Application ID Value 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 SAP HANA Cloud Platform mobile services, and the client application code uses the Application ID when sending requests to the server, reverse-domain notation for the object MyApp.sap.com is com.sap.myapp, for example. The Application ID: Must be unique Must start with an alphabetic character Can contain only alphanumeric characters, underscores, and periods Cannot include spaces Can be up to 64 characters long Note You cannot use these case-sensitive keywords as application identifiers: Admin, AdminData, Push, smp_cloud, resource, test-resources, resources, Scheduler, odata, applications, Connections, public, lcm. Formatting guidelines: SAP recommends that application IDs contain a minimum of two periods. For example: com.sap.mobile.app1. Application IDs cannot start with a period. Application IDs cannot include two consecutive periods. Version Name Type Displays the read-only version that is set by the application developer. The name: Can contain only alphanumeric characters, spaces, underscores, and periods Can be up to 80 characters long Application type: Native native applications, including Android, BlackBerry, ios, Windows Mobile 8, and Windows 8. Hybrid Kapsel container-based applications. Web application running on SAP Mobile Platform, and securely exposed on SAP HANA Cloud Platform mobile services. Description Vendor (Optional) The description: Can contain alphanumeric characters Can contain most special characters, except percent signs (%) and ampersands (&) Can be up to 255 characters long (Optional) The vendor name: Can contain only alphanumeric characters, spaces, underscores, and periods Can be up to 255 characters long SAP SE or an SAP affiliate company. All rights reserved.

23 Field Security Configuration Same-Origin Policy Value Change this value only if you require something other than the default. None (default) anonymous authentication. No authentication challenge is sent; requests are processed anonymously. Form SAML-based SSO authentication. Basic HTTP-Basic (user name and password) authentication. Certificate X.509 certificate authentication. OAuth access token-based authentication. Prevent or allow your application to be accessed by cross-origin resources, while creating or updating application. By default, same-origin policy is set as enable. Enable if enabled, accessing cross-origin resources is forbidden. Disable if disabled, accessing cross-origin resources is allowed. Note In case of legacy applications, by default same-origin policy is set as disable to allow cross-origin access. 3. Click Save. Note Application-related options, such as Back End, Client Policies, Push, and so on, appear in Mobile Services Cockpit only after an application has been successfully created Defining Back-End Connections Define a back-end connection for the selected application (native, hybrid, or Web). Context A back-end connection is a connection to the data source, also called the enterprise information system (EIS). SAP HANA Cloud Platform mobile services supports one primary endpoint per application ID. However, an administrator can create multiple secondary endpoints for other services used by the application; SAP HANA Cloud Platform mobile services treats these additional endpoints as proxy connections. For applications that access a Web service containing relative URLs, add the relative paths to enable SAP HANA Cloud Platform mobile services to handle requests correctly SAP SE or an SAP affiliate company. All rights reserved. 23

24 Procedure 1. Create a new application. 2. Select Back End, and enter: Field Back-End URL Value The URL (back-end connection, or service document) the application uses to access business data on the back-end system or service. The service document URL is the document destination you assign to the service. The URL must include a trailing slash to avoid triggering a redirection of the URL, and losing important HTTP header details. This is especially important when configuring the application with security, such as SSOToken and Certificates, and when Rewrite URL is enabled. Examples: help/abc/app1/opg/sdata/testflight/ <tenantname>.hana.ondemand.com/sap/opu/odata/rmtsample/ Proxy Type Select either: Internet HTTP destinations use Internet proxy. Back-end systems are in the public domain and accessible to everyone. For example, OnPremise back-end systems are behind a firewalls and HTTP destinations use SAP HANA cloud connector to connect to these systems. Note If the proxy type is Internet, the back-end URL can be either a gateway or a cloud connector URL; if the proxy type is OnPremise, the back-end URL must be a cloud connector URL. Authentication Type SAP HANA Cloud Platform uses the HTTPS protocol to integrate into the existing security landscape without disruption. Select one of these authentication types: Principal Propagation allows destinations to forward the identity of on-demand users to the Cloud connector, and then to the back-end of the relevant on-premise system. An ondemand user need not provide his or her identity for each connection to an on-premise system via the same Cloud connector. Note Proxy Type must be OnPremise; otherwise, the destination cannot be saved. No Authentication back ends do not require credentials for authentication. Your destination is provided direct access to the relevant on-premise service. SAPAssertionSSO configure the back-end system to accept SAP assertion tickets that are signed by a trusted x.509 key pair SAP SE or an SAP affiliate company. All rights reserved.

25 Field Value Basic Authentication enter user name and password credentials to authenticate. Client Certification Authentication prepare a client certificate and have it signed by a SAP HANA Cloud Platform mobile services certification authority (CA). The client certificate must be trusted by back-end systems. Note Proxy type must be Internet, the back-end URL must use HTTPS, and you must provide both keystore and truststore parameters. Maximum Connections Rewrite Mode The number of back-end connections that are available for connection pooling for this application. The larger the pool, the larger the number of possible parallel connections to this specific connection. For primary endpoints, the default range is connections. Factors to consider when resetting this property: The expected number of concurrent users of the application. The load that is acceptable to the back-end system. The load that the underlying hardware and network can handle. Increase the maximum number of connections only if SAP HANA Cloud Platform mobile services hardware can support the additional parallel connections, and if the underlying hardware and network infrastructure can handle it. Select one of: Rewrite URL on HANA Mobile Server in request and response messages, SAP HANA Cloud Platform mobile services replaces all back-end URLs with the server URL. The Rewrite URL format for Web type applications <ApplicationID>. Rewrite URL on Backend the back end rewrites the URLs. SAP HANA Cloud Platform mobile services forwards its host name and port to the back end as an HTTP header, and the back end creates the URL to retrieve back-end entities. To expose the full URL to clients, the server passes the endpoint in an X-SMP-ENDPOINTNAME header. For example: Back-end URL FINCUSTFACTSHEET/ URL exposed to clients FINCUSTFACTSHEET/ URL format for Web type applications of Backend>?X-SMP-APPID=<ApplicationID>. For example: FioriLaunchpad.html?X-SMP-APPID=xxxxxBE. Note When you switch the rewrite mode configuration to or from "Rewrite URL on Backend" in the Mobile Services Cockpit, it is required that the application developer is aware of the change. He/she should accordingly change the base URL of the application in case of online and offline mobile application scenarios SAP SE or an SAP affiliate company. All rights reserved. 25

26 Field Value If the rewrite mode is selected as "Rewrite URL on Backend", the base path of the URL must correspond to the path of the backend URL. In other rewrite modes, the base path must contain the Application ID (as shown above in the example). It is recommended that you do not change the rewrite mode arbitrarily, without reconfiguring the mobile application information. Depending on the configuration of other applications configured in your account, it might not be possible to detect from the browser URL which exact application is targetted. Therefore it is always recommended you append the application ID as a URL parameter to the start URL when opening an application in a browser: APPID=<appid>. For example: APPID=webapp. In the case where the URL needs other query parameters, you can simply append it to the end of the URL: other=parameter&needed=true&x-smp-appid=webapp" Via HCP HTML5 App: If selected, the host name is sent to the back end in the HTTP header <X- FORWARDED-FOR>. If not selected, the host name is sent to the back end in the standard HTTP header "Host". Note When the SAP HANA Cloud Platform mobile services sends a request to fetch data from the back end, an HTTP header includes host information. This mechanism causes failures when connecting via a HTML5 application hosted on HANA Cloud Platform. In case of failures, select Via HCP HTML5 App. The request host is then sent in the x-forwarded-for header, which is used by HTML5 applications, and sent as the host header to a back end. Web type applications: For transparent onboarding of Web type applications that are using the Rewrite URL on Backend option, use the URL parameter X-SMP-APPID to specify the requested Web Application. Keep in mind: You can specify any application using the X-SMP-APPID parameter. If the parameter is used without an existing application, no application is used. If the parameter is used without an existing Web application, no application is used. If the parameter is used for an application without a valid endpoint for the called path, no application is used. No Rewriting request and response messages are not modified; SAP HANA Cloud Platform mobile services passes messages directly between clients and the back end. The URL format for Web type applications <ApplicationID> SAP SE or an SAP affiliate company. All rights reserved.

27 Field Value Note To enable applications using an external back end to run offline, you must select one of the rewrite options. Relative Paths If an application requires data from a back end that uses relative URLs, you must configure those relative URL patterns in Mobile Services Cockpit. SAP HANA Cloud Platform mobile services rewrites the relative URLs to include the Connection ID (connection name), enabling access to the back-end data. For example, a Web service application requests an HTML page named abc.html, which contains the relative URLs /sap/bc and /sap/public/bc in its src or href tags. When a request is made, SAP HANA Cloud Platform mobile services rewrites the relative URLs contained in the response, so that subsequent requests (to these relative URLs in the response) can be processed correctly. For example, if "webapp" is the connection name and the response contains the relative URLs /sap/bc,/sap/public/bc; SAP HANA Cloud Platform mobile services rewrites these relative URLS to /webapp/sap/bc,/ webapp/sap/public/bc. Without the relative URLs, the request cannot be processed. To add relative paths, you can either enter one relative URL per table row (for example, /sap/bc in one row, and /sap/public/bc in another); or you can enter a comma-delimited list of relative URLs in one table row (for example, /sap/bc,/sap/ public/bc), and the URLs are redistributed to separate rows after you Save. Note To use the Relative Path option, you must select Rewrite URL in HANA Mobile Server option in Rewrite Mode. Keystore Location Keystore Password User Name Password Use Default JDK Truststore (For mutual SSL authentication) If the back-end URL begins with HTTPS and the proxy type is Internet, either: Select a certificate from the list, or Click Upload and Delete Certificates, and select a certificate to upload. (For mutual SSL authentication) A valid password for the keystore you selected. (Optional) The user name to access the back-end system. (Required if you set the user name) The password to access the back end. To validate remote HTTPS certificates, select to use the default JDK truststore certificate. 3. (Optional) Under Back-End Connections, view additional connections, or add new connections. a. To add back-end connections (secondary endpoints) in the server, select New. b. Enter values for the new back-end connection, using the values shown above. c. Select Save. The new back-end connection is added to the list. You can maintain the list of server-level back-end connections (including all the connections in SAP HANA Cloud Platform mobile services), and of application-specific back-end connections. Application-specific back-end connections are the secondary connections that are enabled for an application; by default, no 2015 SAP SE or an SAP affiliate company. All rights reserved. 27

28 secondary connections are enabled. You must explicitly enable additional back-end connections for an application. Users who are registered to an application can access only these back-end connections. If a user attempts to access a back-end connection (request-response) that is not enabled for an application, a 403, Forbidden, error is thrown. 4. Select Application-specific Connections to show the back-end connections that are enabled for the application. Select Server-level Connections to show all available connections for the server. Select additional connections for the application to enable them. Note You can authenticate multiple back ends using various authentication provider options in the backend security profile. If the back-end system issues a 302 Redirect or "307 Redirect" response, which means it is redirecting the request to a different URL, then you must also add the target URL to the list of application-specific connections Configuring Offline Settings for Applications (Does not apply to Web applications) 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 HANA Cloud Platform mobile services moves data between the back end and the client offline store. Context The back-end connection settings determine how SAP HANA Cloud Platform mobile services create the initial offline store database on the client, and how it processes requests for updates from the back end. Define offline back-end connection settings for an application by importing a configuration (.ini) file that has been prepared by a developer. You cannot update the settings using Mobile Services Cockpit. To adjust any settings, remove the current configuration, update the configuration file, and then reimport the file. Before updating this file, confer with a developer. See the Development documentation in the Native Data Application Development section: ios Developing ios Offline OData Applications Android Developing Android Offline OData Applications. Windows Developing Windows Offline OData Applications Procedure 1. From the Mobile Services Cockpit, select Applications, select the application to configure, then click Configure SAP SE or an SAP affiliate company. All rights reserved.