Uploading and Deploying Apps¶
If the selected app uses the
AppUpdate plugin, you can activate a new version of the app.
You need a hybrid app package that:
- Contains the contents of the application's
wwwfolder and the
config.xmlproject file, with a separate folder in the archive for each mobile platform (
ios/wwwin all lowercase). The format structure for a hybrid apps is:
nohighlight |- android | |- config.xml | |- www |- ios
- Is compressed into a standard
.zipfile for upload.
To update and deploy versions:
In SAP mobile service cockpit, select Mobile Applications.
Select an application, then select Mobile App Update under Assigned Features (or add it first).
Select Configuration and then to import a new application or update an existing application version.
In the Import Application Version dialog, select Browse, and navigate to the directory that contains the
MDKor hybrid app package.
Select the package, and select Upload.
New version information appears for the uploaded app for each mobile platform. You cannot change this information.
MDK/Hybrid App Properties
Property Description Status State of the hybrid or Mobile Development Kit app version:
New Version– a newly uploaded version.
Staged Version– in testing. A user who is defined as a tester can download and test applications. Once testing is complete, an administrator can promote a version to the Current state, so it becomes active. If testing fails, the administrator can change the state back to New.
Current Version– the version that is currently active.
Operating System The operating system on which the application runs, such as Android, iOS, and
Type The application type, such as Hybrid and
Description The application description, such as
Mobile Development Kit App.
Revisions Identifies the production version revision. A revision number is assigned to a newly uploaded app and incremented when a new version is uploaded. When the app is deployed, the revision number is incremented.
Note: The server limits the number of old active revisions that are supported. Currently the maximum number of old active revisions is set to 3. Once the limit is reached, the oldest versions are removed.
Versions The app versions, depending on the app type. (1) For Hybrid apps,
Required Client Versionidentifies the SDK version that was used to develop the app, for example,
3.0.0.This version attribute is informational only; it is not used to determine whether device clients should receive a Web application update.
Development Versionidentifies the internal development version that was used to develop the hybrid app. (2) For
Metadata Versionis assigned to the collective settings used to build the app. A blank indicates that metadata version was not supported when the file was created.
Uploaded By The user who uploaded the hybrid or Mobile Development Kit app. Actions Actions to perform such as Deploy, Stage, or Delete.
Select Info to view feature details. You can also use Export Data to download mobile service data in JSON format.
Moving Applications Between States¶
|Beginning State||Action||Ending State|
Note that each platform can have an unlimited number of versions in the New state, but only one version in the Staged state, and one version in the Current state.
To deploy applications, select the check box for each application you want to deploy, and click Deploy.
Deployed hybrid app information appears as the current version, and the revision number is incremented.
For device-application users:
- If a hybrid app with the default version (revision = 0) connects to the server, the server downloads the full hybrid app.
- If a hybrid app with a version (revision = 1 or higher) connects to the server, the server calculates the difference between the user's version and the new version, and downloads a patch containing only the required changes.
- If the application implements the
AppUpdateplugin, the server checks for updates when the application starts or resumes. If the developer has made changes,
AppUpdatedetects them using the
wwwfolder content (the HTML-based content), and not with native plugins or changes made outside of that folder. For changes made outside the
wwwfolder, the developer must post a new copy of the app to the application download site, or use app stores or Mobile Device Management to push the app to users.
- To remove application versions that have been imported, but not yet deployed, select an application and then .
To optimize life-cycle management for applications and to provide more efficient client updates, SAP Mobile Services archive a limited number of applications that a client has previously downloaded to his or her device. If a client requests an application update and the client version of the application is available, the delta version is sent to the client; if the client version is not available, the full version is sent to the client.
Select Info to view feature details. Use Export Data to download mobile service data in JSON format.