Skip to content

Exporting and Importing Application Configurations

The ability to import and export application configurations enables you to copy a configuration from one environment to another. For example, you can export an application configuration from the testing environment, and import it to the production environment.

Exporting Application Configurations

Export an application configuration zip file to your local system, retaining many of its settings. You can use the export feature to create a back-up of the application configuration, and as a prerequisite for importing the application configuration to SAP Mobile Services.

Before exporting an application to your local system, verify that the application status is consistent (marked in green).

Only the current version of an application is exported; new versions are not exported.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select the application, and then select Export in the upper right corner.

    The application configuration file is downloaded to the <appname>_<version>.zip file in the default location, which is specified in the browser. Passwords are not exported.

    • <appname>_<version>.zip contains a Common subfolder with the <appname>_<version>.smpconfig file that contains all the application information.
    • Passwords are not exported.

    Note

    You can export the application configuration to a shared directory to make it available to all the mobile services systems that have access to the shared directory.

Importing Application Configurations

Import an application configuration from one SAP Mobile Services environment to another. Many configuration settings are retained, but you must reconfigure some application settings for the target server environment.

Verify that the application *.zip file you want to import is available on the SAP Mobile Services network.

  • Importing an application configuration does not necessarily make it ready for use. Administrators must review the imported application, and if necessary, make adjustments to its configuration.
  • For hybrid apps that use the AppUpdate plugin, manage the application version using Applications > App Spec Setting.
  • If you make changes to an exported application configuration *.zip file, you cannot import it.

Note

You can import a Fiori application that was developed with SAP Business Technology Platform mobile service for app and device management, but you cannot edit its properties in SAP mobile service cockpit.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select Import in the upper right corner.

  3. Click Browse, and select the application configuration *.zip file.

    • To import an application with the same ID as an existing application, select Overwrite existing application; otherwise, you see the error message Application already exists.
    • If you import an application with a secondary connection that already exists in the target system, the connection is not overwritten.
    • Passwords such as those for APNS, BES, and anonymous user settings are not imported, so the application is marked inconsistent.
    • If any resource bundles were exported, they are uploaded during import.
    • Click Import.

    When the import completes, you see the message Application Created.

Configure the application for the target server environment.

Importing Micro App Configurations

Import a Micro App configuration from one SAP Mobile Services environment to another. Many configuration settings are retained, but you must reconfigure some application settings for the target server environment.

  1. In the SAP mobile service cockpit, select Mobile Applications > Micro App, then select Import in the upper right corner.

  2. In Import Application, click in the blank field or select Browse; choose a file name in the pop-up dialog; and then select Save. If you import a Micro App with the same ID as an existing one, you see the error message Application already exists.

  3. Update the Micro App by setting WeCom settings for App Secret, Encoding AES Key, and Token as described in Configuring WeCom Settings.

Exporting Data

SAP Mobile Services allows you to export a tenant database from the cloud to a local .csv file.

Exporting data is a role-based feature, and you'll need one of the following roles to perform this task:

  • Administrator
  • Helpdesk

Exporting a tenant database from the cloud to a local .csv file can be performed in the following systems:

  • SAP Mobile Services
  • Microservices / Storage
  • Microservices / Octane

You can export a tenant database from the cloud to a local .csv file by using the following URL: /mobileservices/origin/{origin}/exportdata/v1/admin

You can use the following link to export the data:

https://<mobile_services_host>/mobileservices/origin/hcpms/exportdata/v1/admin

Response Status and Error Codes

Code Repose Body Description
200 <exported data> Prompts the user to download the .csv file.
403 The user does not have the Administrator or Helpdesk role.
Last update: March 10, 2022