Deployment of Mobile Components 

Purpose

You use this process when working with the Mobile Administrator to deploy the mobile component to the server and client.

Prerequisites

●      If you are deploying a mobile application you must have created an RFC destination to the back end.

●      You have made the settings for the synchronization.

●      You have synchronized with the back end.

Process Flow

...

       1.      If your mobile component has a format other than SDA or SCA, you convert it using the Mobile Administrator (see Starting the Mobile Administrator and Converting Archives for a Mobile Component).

       2.      You deploy the mobile components (see Deploying Mobile Components on the Server).

       3.      You check in the Mobile Administrator whether the components are available (see Displaying Mobile Components).

For more information on the different types of files, see Mobile Applications, Database Files, Driver Files, Framework Files, and Database Files.

You can find more information on the Mobile Component Descriptor in Mobile Component Descriptor.

       4.      For mobile applications only: You set up the user-specific data filtering (see Defining User-Specific Data Filtering).

       5.      You assign the mobile components to the users (see Assignment of Mobile Components to Users).

When the users synchronize, the assigned mobile components are deployed to the mobile device. For more information, see Deployment of Mobile Applications on the Mobile Device.

       6.      After setting up the mobile devices, you can check if the deployment was successful by displaying the status of the mobile components (see Displaying the Status of Mobile Components).