Deployment Mode and Target Version

You can set the version and modes in which a Mobile Application project or mobile deployment package are deployed to the target Unwired server.

Deployment modes and target version
Option	Description
Update	Updates the target package with an updated version.
No Overwrite	Deploys the source package only if there are no objects in the target package that have the same name as any of the objects being deployed
Replace	Replaces any of the target objects with those in the package.
Verify	Does not deploy the package but reports what, if any, errors would occur if you were to deploy the package using Update mode.
Target Version	Determines the version of the target package to which the package is to be deployed. By default, the current project version is used. You can enter a different version, if appropriate. The version consists of two numbers. For example, 1.0.
Package namespace	The location in which the deployed unit resides. The default value is the Mobile Application project name.
Replication based or Message based	Replication-based – all data within the package is replicated in the Unwired Server cache (CDB). Message-based – used within a Mobile Workflow package, which uses push synchronization through a dedicated channel. Note: This setting is now ignored: Unwired WorkSpace – the package type (MBS and RBS) in the deployment wizard is no longer relevant. Sybase Control Center – all packages display as Unified, and there is no package option in the deployment page.