Applications

An application consists of two parts: the software user interface that consumes enterprise data from one or more data sources, and the definition created in SAP Control Center that allows the mobile application to be recognized by the runtime. Depending on the application type, the application definition on the server can establish the relationship among packages used in the application, the domain that the application is deployed to, the activation code for the application, and other application specific settings.

While developers create the client application using either SAP Mobile SDK or a third-party SDK, applications must be defined, then managed and monitored by administrators in SAP Control Center. The stages in the life cycle of an application may be different for different application types.

• Activating and Maintaining Applications
  The activation stage defines all activities that relate to the startup 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).
• Defining Applications
  Applications are recognized by SAP Mobile Server by the properties that define them. Administrators define applications with a unique application ID and other key application properties, such as domain, packages, security configuration, and connection templates.
• Maintaining Activated Applications
  Activated applications can be managed and have usage monitored.
• Transporting Applications Between Environments Using Export and Import
  Transport applications between different server environments by exporting them from one server, before importing them into another one. This sequence of events is typically performed by administrators when transporting applications from a development local server environment to a test network environment, or from a test or pilot environment to a production cluster environment.
• Application Connections
  (Not applicable to Agentry applications) Application connections define the manner in which the application connects to SAP Mobile Server and interacts with the runtime services the application requires. Connections are defined by the properties that are configured for it, frequently saved as a reusable template.
• Application Connection Templates
  (Not applicable to Agentry applications) An application connection template is a model or pattern used to standardize properties and values for application connections. When application share many of the same connection properties and values save them to a connection template.
• Application Connection Properties
  (Not applicable to Agentry applications) Set application connection properties through SAP Control Center to create application connections and application connection templates. These settings influence the application connection, including security, datasource connection, user registration, device and application, and so forth.