Show TOC

Configuring Deployment PropertiesLocate this document in the navigation structure

Set the properties for packages being deployed on SAP Mobile Server.


A deployment file and an optional deployment descriptor file are created by developers in SAP Mobile WorkSpace. These files are typically delivered for deployment to a production version of the SAP Mobile Server by an administrator.

Note If the package is deployed to the primary server, it is cluster-level operation.


  1. When the Deploy wizard loads, click Next.
  2. Review the Deployment File name, or click Browse to navigate to the appropriate file.
    You can select either a single deployment unit (.XML) or an archive file (.JAR).
    The name of the Package Name appears. If this package does not already exist, the wizard displays a message that indicates the new package will be created. The name cannot exceed 64 characters or include any periods (".").
  3. Select a Deployment Mode.

    The deployment mode determines how the deployment process handles the objects in a deployment unit and package. The value you choose depends on whether or not a package of the same name exists on SAP Mobile Server. Allowed values are:

    • UPDATE – (default) updates the target package with updated objects. After deployment, objects in the server's package with the same name as those being deployed are updated.

      Use update where existing deployments and client applications need to continue to work. After a successful (or failed) Update deployment, existing client applications previously synchronized with SAP Mobile Server continue to function: existing surrogate keys do not change, all operations are fully functional, and so on. No data loss on the devices occur, and the existing client can synchronize and upload operations as if the Update deployment never occurred.

    • VERIFY – do not deploy package. Only reports what, if any, errors would occur if you were to deploy the package using UPDATE deploy mode.

      Verify ensures that any existing client is still able to operate fully after a deployment. A limitation for message-based synchronization clients is that the old client could receive unnecessary data that is ignored on the device.

    If the deployment mode is specified both in the descriptor file and the Deploy wizard, the Deploy wizard Deployment Mode option overrides the deployment mode specified in the descriptor file.
  4. Browse and select an optional deployment Descriptor File.
  5. Click Next.
  6. Select a Domain to deploy the package to.
  7. Select a Security Configuration for the package.
  8. Click Next.
    The Configure Role Mapping page appears.