Administrator

Defining Applications

Create a new native, hybrid, Web, Mobile BI, or Agentry application definition, which enables you to use Management Cockpit to manage the application.

Procedure

  1. In Management Cockpit, select Applications, and click .
  2. In the Create Application window, enter:
    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 SAP Mobile Platform, 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
    • Cannot be any of these case-sensitive keywords: Admin, AdminData, Push, smp_cloud, resource, test-resources, resources, Scheduler, odata, applications, Connections, public, lcm

    SAP recommends that application IDs contain a minimum of two periods, for example, com.sap.mobile.app1.

    Version Application version.
    Name Application name can contain only alphanumeric characters, spaces, underscores, and periods, and be up to 80 characters long.
    Type Application type.
    • Native – native applications, including Android, BlackBerry, iOS, and Windows Applications.
    • Hybrid – Kapsel container-based applications.
    • Web – application that runs in a Web browser.
    • Agentry – metadata-driven applications.
    • MobileBI – SAP BusinessObjects Business Intelligence applications.
    Description (Optional) The description can contain up to 255 alphanumeric and special characters, but cannot contain percent signs or ampersands.
    Vendor (Optional) Vendor who developed the application. The vendor name can contain only alphanumeric characters, spaces, underscores, and periods, and can be up to 255 characters long.

    Registration Threshold

    The registration threshold in seconds for the application. Leave blank (default) or set to 0 to remove threshold. Set a threshold value from 1 ‒ 2147483647. If the number of incoming registration requests per second exceeds the value, requests are throttled and the server generates HTTP error code "429 TOO MANY REQUESTS".

    Online Request Threshold

    The online request threshold in seconds for the application. Leave blank (default) or set to 0 to remove threshold. Set a threshold value from 1 ‒ 2147483647. If the number of incoming online requests exceeds the value, requests are throttled and the server generates HTTP error code "429 TOO MANY REQUESTS".

    Offline Request Threshold

    The offline threshold in seconds for the application. Leave blank (default) or set to 0 to remove threshold. Set a threshold value from 1 ‒ 2147483647. If the number of incoming offline requests exceeds the value, requests are throttled and the server generates HTTP error code "429 TOO MANY REQUESTS".

    Enable CSRF Protection Enable protection against cross-site request forgery (CSRF) attacks for the selected application. This option protects all services, such as registration, with CSRF tokens. Proxied endpoints are not protected, since they may be protected on the back end.
    Ignore Case for User Name (Not available for Agentry application type) By default, the server uses case-sensitive matching to compare registered user names for subsequent application access, to ensure that the connection is not shared by different users, and for push notification.

    Select this option to use case-insensitive matching for this application. This is useful when the server processes push notifications for Fiori applications that expect user names to be matched case-insensitively, as in ABAP systems.

    Security Profile Name Select a security profile from the list.

    A security profile protects application resources. See Configuring Security Profiles and Authentication Providers.

  3. Click Save. You see application-related tabs, such as Information, Back End, Authentication, Push, and so forth. The tabs you see differ by application type. You are ready to configure the application, based on the application type.