Mobile Device Installation Using Setup Packages


With the Mobile Administrator, the administrator can create a setup package containing an installation file. The user of the mobile device can use this setup package to install the client on the mobile device. The user can obtain the setup package from, for example, a CD or DVD, or from the network.

This procedure has the advantage that the user does not have to download all the mobile components, parameter sets, and application data to the mobile device from the Internet. The process is thus particularly suited to situations in which there is no stable broadband Internet connection.

Two possible scenarios exist for the creation of setup packages:

?      The administrator creates a setup package for an individual user, who, for example, wants to install the client on a new device because the old device is defective.

?      The administrator creates a setup package that can be used by multiple users, and not only by a single user.


?      The server on which the setup packages are to be created must have a Win32 operating system.

?      You have enabled the creation of setup packages (see Allowing the Creation of Setup Packages).

?      The following databases are possible:

0       For setup packages for Win32 systems: MaxDB (latest 7.6 version), DB2E, or file-based data storage

0       For setup packages for Windows Mobile System: DB2E or file-based data storage

?      If you want to create setup packages that contain a MaxDB database, you require an additional MaxDB installation on the server. For more information, see Note 936639. You can download the installation files for the mobile device under the internet address

?      If you want to create setup packages with DB2E, you must also create a DB2E add-on (see Creating the DB2E Add-On for Setup Packages).

?      If you want to create setup packages with Windows Mobile as the operating system, you need the Cabwiz tool to create cab files (see Preconfiguring on Windows Mobile Platforms).

?      The server user for the synchronization was entered as the logon user for the service mi_mds (see Setting Up a Synchronization Service).

?      The framework has been deployed (see Framework Files) and it is available as a mobile component in the Mobile Administrator. You can use the function Mobile Components to check whether the required mobile components MOBILEENGINE_JSP, MOBILEENGINE_UNCOMP, MOBILEENGINE_AWT or MOBILEENGINE_AWT_UNCOMP are available (see Displaying Mobile Components).

?      The mobile applications have been deployed (see Deployment of Mobile Components).

?      If you want to use parameter sets, you must have created these already (see Defining Parameter Sets).

?      Before setup packages can be installed on the mobile device, the following must already be installed:

0       For Win32 systems: JDK 1.3.* or JDK 1.4.*.

0       For Windows Mobile Systems: Java Virtual Machine CrEme (to find out which is the right version, see Note 765433).

Process Flow


       1.      As administrator, you prepare for the creation of the setup packages by creating device configurations and assigning them to the users (see Creating Setup Packages).

       2.      You create a setup package (see Creating Setup Packages and the section Creating Setup Packages). To do this, you use the Setup Packages function of the Mobile Administrator (see Setup Packages).

       3.      You download the setup package and transfer it to the user, or copy it to the mobile device yourself (see Creating Setup Packages and the section Installing a Package on the Mobile Device).

       4.      There are two ways to install a setup package on the mobile device and synchronize for the first time:

0       If the setup package is user-specific, the user installs the setup package on the mobile device. The user can then log on with the password INITIAL and change the password (see Installing the SAP MI Client Component Using a Setup Package).

0       If the setup package is meant for more than one user, you as administrator can install it. You create a user with a temporary password (for example, INITIAL), and then give the mobile device to the user. For more information, see Installing Setup Packages (Administrator).