Stage 4: Activate

The application activation stage defines all activities that relate to the start-up of and formal entry of an application and a known or anonymous user into the SAP Mobile Platform runtime. It ties all entities together by associating a user with the application and its resources (connections, customizations, and packages).

Note: Agentry applications have different steps in the Activate stage. For more information, see Creating Agentry Application Definitions in SAP Control Center for SAP Mobile Platform.

The activation process is dependent on a one-time handshake/setup between the application and SAP Mobile Server. This handshake is dependent upon the device being preseeding with required configuration and security artifacts. These artifacts and configuration values may come from one or more sources, such as the user, a provisioning file installed with the application, or delivered OTA with Afaria. See the Stage 3: Provision chapter for details.

After an application becomes activated:

SAP Mobile Platform client applications – can access all SAP Mobile Platform features, including complete data synchronization, push notifications, and so on.
HTTP open service client applications – can only access a subset of SAP Mobile Server services.

The Activation Process
Various features support the application activation process. Application types (for example, native applications or Hybrid Apps), and design decisions (for example, connection registration type, customizations) each might have a significant impact on the administration activities required to support your environment.
Enabling Application Activation with SAP Control Center
Application activation is the end result of the series of events by which a user can start consuming data or using platform services. Application activation is enabled by the administrator using SAP Control Center, then triggered by the application user upon a first connection attempt.

Parent topic: Mobile Application Life Cycle