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 Sybase Control Center that allows the mobile application to be recognized by the runtime. The application definition on the server establishes 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.

A native application is the single client binary provisioned then installed to the device. It is associated with one or more MBO packages. The native Hybrid App is a collection of Hybrid App packages and typically constitutes one application. A non-native application uses no packages and therefor requires no package association.

While developers create the client application using either a native development tool for Unwired Platform or a third-party tool for non-native application types, applications must be defined, then managed and monitored by administrators in Sybase Control Center.

• 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 Unwired 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 Unwired 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
  You can 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
  Application connections define the manner in which the application connects to Unwired 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
  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. The application connection template assigned during application connection registration sets the default connection with common properties and values. You can then override the default template properties and specific values.
• Application Connection Properties
  Application connection properties are used to define the values used for an registered application connection. You can create a set of single-use properties or save a base set of defaults for an application connection templates if you have a set of values used by many applications.