Package Versioning and Deployment Mode Selection

Unwired Server supports both side-by-side package deployment (or versioned deployment) and replacement deployment. This gives administrators increased flexibility to determine which packages to keep, and when to remove legacy packages.

Versioning varies depending on the role of the deployer, as well as the package type and the deployment method used.

MBO recommendations for developers:
- Deployment mode – During development, teams typically use replacement deployment, which means the new project completely replaces the existing one. When the replacement project is deployed, all attributes for the project are replaced in the cache, and project-related tables are purged. As a result, the next time the application synchronizes, all client-side data in the client database is deleted. This reset is recommended for testing, because each deployment instance starts with a clean state.
- Versioning – In an MBO project, the version number is used only to find the correct package for deployment. Developers can provide any version number 0 - n to deploy successfully.
  By default, developers can keep the version number derived from the version associated with the project. However, if this is an incorrect version, developers can change the default version from the deployment wizard in Sybase Unwired WorkSpace - Mobile Business Object Development, by setting the Target version property when performing an update deployment.
MBO recommendations for administrators:
- Deployment mode – Sybase recommends only using update deployments. For MBO packages, update means the new package follows the backward compatibility guideline defined by Unwired Server. Supported update attribute changes include:
  - Adding MBOs to a new synchronization group
  - Changing the cache policy
  - Adding or removing Result Set Filters
  - Adding or removing Result Checkers
  - Adding or removing a logical role for different role mapping
  When an update is detected by the application, the client database is only updated instead of overwritten. This behavior tightly controls the change process, which is an important factor for production environments.
  
  If you want to perform a replace deployment, simple delete the MBO first, then redeploy deployment with update mode. All changes are audited by Sybase Control Center.
- Versioning – The administrator cannot change the version number during deployment. Therefore, adjust the version number before deploying the MBO package. To change the version number, open the package, and edit the deployment_descriptor.xml file.
Hybrid Apps recommendations for developers:
- Deployment mode – In Sybase Unwired WorkSpace - Hybrid App Package Development, the deployment mode selection is automatic.
- Versioning – To perform an update deployment, ensure that you set the version number to at least one minor version higher than the version that is currently deployed to Unwired Server. After deployment, both app versions coexist on both the server and device. This allows the user to decide which instance to launch. For a server-initiated Hybrid App, each inbox message (or notification) includes the Hybrid App name and version number. When the user opens the message, the correctly versioned Hybrid App instance is used.
  In contrast, for replacement deployments, the version number of the new Hybrid App must match the existing version. The replacement deployment mode then overwrites the deployed Hybrid App. When the newly-deployed Hybrid App is downloaded, the application user launches the Hybrid App with the existing icon; however, the application interface could be completely different.
Hybrid App recommendations for administrators:
- Deployment mode and versioning – Use New to deploy a new Hybrid App package and its files for the first time. If the uploaded file does not identify an Unwired Server, or an Unwired Server with the same name and version is already deployed to Unwired Server, you see an error message. In the latter case, use an update deployment. Review update mode and versioning behavior outlined for developers. For replace, administrators can replace an existing Hybrid App with a new one, but maintains the same name and version. Administrators typically use the replace deployment mode for minor changes and updates to the Hybrid App.