Allowing the Creation of Setup Packages


To create setup packages you have to configure the function. In doing so, you determine, for example, where the setup package is to be saved.


See Mobile Device Installation Using Setup Packages.



       1.      Start the Visual Administrator and log on to the J2EE system.

       2.      Choose the server you want on the Cluster tab page and then Service   ®  Configuration Adapter.

       3.      Change to the edit mode to edit the settings.

On the right side of the screen the system displays the node Mobile_setupGeneration with the assigned properties. You can configure the settings in the following ways:

Configuration Parameters




Required. Path and name of Java Virtual Machine that is to be used to create the setup packages.

Example: C:\j2sdk1.4.2_07


Optional. Additional options for the Java Virtual Machine (JVM). You can find information about the relevant parameters in the documentation for the JVM.

They include, for example, specifications for the minimum (-Xms) or maximum (-Xmx) JVM memory. If the setup package is to contain large amounts of data, it may be necessary to increase the maximum memory value setting.

Example: –Xmx512M


Required. Temporary directory in which the downloaded and extracted mobile components are stored. Use a directory on a partition with sufficient memory.

If parts of the downloaded application are to be edited manually, this must be done in the directory.

Example: C:\MITEMP


Required. Directory in which the setup packages are saved and generated.  Use a directory on a partition with sufficient memory for all the setup packages generated simultaneously.

Example: C:\MISP


Required if the setup packages are to be generated for devices with Windows Mobile.

Directory in which the tool for the creation of cab files is provided.

Use a backwards slash (\) at the end of the path.

Example: C:\Program files\Windows CE Tools\wce20\POCKET PC 2003\Tools\


Optional. Additional jar files that are to be used in the bootstrap process of the client.

Example: D:\java\ext\myBootstrapJar.jar


Required if MaxDB is used. Software installation directory for the second installation of the database.

Example C:\sapdb\data\wrk


Required if MaxDB is used. Data directory for second installation of MaxDB.

Example: C:\sapdb\mi 


Required if MaxDB is used. Directory containing the file sapdbc.jar.

Example: C:\sapdb\programs\runtime\jar


Optional. Time in minutes that the system must wait between downloading the application and the data. If the application is not completely downloaded, errors can occur when downloading the data.

The waiting time is required to populate the container with data from the back-end system. The waiting time depends upon the amount of data. You can determine the time required by displaying the worklist in the monitoring tool (see Displaying the Synchronization Overview). In this way, you can calculate the start and end time of the waiting period.

Possible values: Positive integers

Default: 2


Optional. Number of synchronization processes required to download the initial master data.

Determine the number required by setting up a test device and checking the number of synchronizations necessary for all the data to be visible following the two initial synchronization runs (see Synchronizing for the First Time). As part of the two initial synchronization runs, the device ID is assigned and the application is transferred. Do not include these initial synchronization runs in your calculation. Only take those runs into account that are used to transfer the data.

Possible values: Positive integers

Default: 3


Optional. Time in minutes between the synchronization processes when downloading data.

Possible values: Positive integers

Default: 0


Required if MaxDB is used. Directory with the installation files for the MaxDB installation. For more information, see Note 936639.

Example: C:\maxdb

       4.      Change back to the view mode. Your entries are automatically saved.