The goal of application management is to register an application to SAP Mobile Server as an entity, create an application template that specifies application connection details for a user, and activate application connections either manually or automatically.
Developers must invoke registration (manual or automatic) for native applications. For development details, see the Developer Guide for your application API and device platform type. For application, connection, and registration details, see Applications in the list of links below. .
| Task | Frequency | Accomplish by using |
|---|---|---|
| Create new applications to register application entities with SAP Mobile Server. A default application template is created automatically. Modify and delete applications as part of application life cycle. | As required | SAP Control Center for SAP Mobile Platform with Applications node, and Applications tab. |
| Create or modify application connection templates to specify details for native, Hybrid App, and proxy application connections. | As required | SAP Control Center for SAP Mobile Platform, with Applications node, and Application Connection Templates tab. |
| Create one or more push configurations for applications. | As required | SAP Control Center for SAP Mobile Platform, with Applications node expanded and an application selected, and Push Configurations tab. |
|
For applications that need to be registered manually, register an application connection to associate an application connection with a user. This is not necessary for applications that are registered automatically.
|
As required | SAP Control Center for SAP Mobile Platform, with Applications node, and Application Connections tab. |
| View activated users, once they have logged in with the activation code. Users must either supply the activation code manually, or the device client supplies the activation code automatically as coded. | As required | SAP Control Center for SAP Mobile Platform with the Applications node, and Application Users tab. |
| Create a new activation code for a user whose code has expired. | As required | SAP Control Center for SAP Mobile Platform, with Applications node, and Application Connections tab. |
| Review registered application connections and users, delete application connections to free licenses, delete application connections to remove users from the system. | As required | SAP Control Center for SAP Mobile Platform with the Applications node. |
| Change logical roles or modify role mappings for a security configuration to prevent users from accessing the application. | As required | SAP Control Center for SAP Mobile Platform with the Security node |
| Manage subscriptions | As required | SAP Control Center for SAP Mobile Platform with the Packages node. |
Application templates hold default connection properties that can be assigned to an application during the connection registration process. However, these templates are configured differently depending on what type of connection registration you enable for applications. See the recommendations documented in Creating Application Connection Templates in the Mobile Application Life Cycle guide.
When a client application connects to SAP Mobile Server its application ID is used to look up a matching template. If that template allows automatic registration (the Automatic Registration Enabled property is set to true), then the security configuration in the template is used to authenticate the user and establish an identity against which the connection is registered. If the template also specifies a logical role, then user is authorized using the mapped physical role(s) of the logical role in the security configuration. When there are templates with different logical roles for the same application id and security configuration, the priority of the template determines the order of evaluation of the associated logical roles.