Show TOC

Defining ApplicationsLocate this document in the navigation structure

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 New.
  2. In the New Application window, enter:
    Field Value
    ID

    Unique identifier for the application, in reverse domain notation. This is the application or bundled identifier that the application developer assigns or generates during application development. The administrator uses the application ID to register the application with the server, and the client application uses the application ID to send requests to the server. Reverse domain notation means reversing a registered domain name; for example, reverse domain notation for MyApp.sap.com is com.sap.MyApp.

    The application identifier:
    • 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 Keywords that you cannot use as application identifiers include: Admin, AdminData, Push, smp_cloud, resource, test-resources, resources, Scheduler, odata, applications, Connections, public, lcm (and its variations, such as LCM, Lcm, lCM, LcM, lcM). These keywords are case-sensitive.
    Formatting guidelines:
    • SAP recommends that application IDs contain a minimum of two periods. For example, this ID is valid: com.sap.mobile.app1.
    • Application IDs cannot start with a period. For example, this ID is invalid: .com.sap.mobile.app1.
    • Application IDs cannot include two consecutive periods. For example, this ID is invalid: com..sap.mobile.app1.
    Name Application name. The name:
    • Can contain only alphanumeric characters, spaces, underscores, and periods.
    • Can be up to 80 characters long.
    Vendor (Optional) Vendor who developed the application. The vendor name:
    • Can contain only alphanumeric characters, spaces, underscores, and periods.
    • Can be up to 255 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.
    • Mobile BI- Mobile Business Intelligence applications.
    Description (Optional) Short description of the application. The description:
    • Can contain alphanumeric characters.
    • Can contain most special characters, except percent signs (%) and ampersands (&).
    • Can be up to 255 characters long.

    Enable same-origin policy

    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.

    Ignore case for user name

    Once users are registered, SAP Mobile Platform uses case-sensitive matching by default when comparing the registered user name 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 push notifications are processed by SAP Mobile Platform Server for Fiori applications that expect the user names to be matched case-insensitively, as in ABAP systems.

  3. Click Save. You see application-related tabs, such as 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.
    Note These tabs appear in Management Cockpit only after you define or select an application. Task descriptions use a "navigational shorthand"—such as "select Start of the navigation path Applications Next navigation step Back End End of the navigation path—to indicate the tab where tasks are performed, relative to that selected application, rather than repeating the entire navigation instruction.
  4. (Optional) To edit application attributes, under ABOUT in the left pane, select Change.
    1. To update Name, Description, Version, or Vendor, enter the new value.
    2. To enable the same-origin policy, or to ignore case for user names, select the respective option.
    3. To define how long inactive registrations exist, select Automatic Removal, and enter the number of seconds, hours, days, or months. If a registration is inactive for the specified time period, the server removes it.
    4. To define an application icon, click Browse, and choose the image file.
    5. Click Save.