Deploying a Hybrid App Package with the Deploy Wizard

Use the Deploy wizard to make Hybrid App packages available on Unwired Server.

If you are deploying to a target domain, replicate the value in the context variable. The domain deployment target must match the context variable defined. If the developer has used an incorrect context variable (for example, one used for testing environments), you can change the value assigned to one that is appropriate for production deployments.

  1. In the left navigation pane of Sybase Control Center, click Hybrid Apps.
  2. From the General tab, click Deploy.
  3. Click Browse to locate the Hybrid App package.
  4. Select the file to upload and click Open.
  5. Select the deployment mode:
    • New – deploys an Unwired Server package and its files for the first time.

      If the uploaded file does not contain an Unwired Server, or an Unwired Server with the same name and version is already deployed to Unwired Server, you see an error message.

    • Update – installs a new Unwired Server package with the original package name and assigns a new, higher version number than the existing installed Unwired Server package. Sybase recommends that you use this deployment mode for major new changes to the Unwired Server package.
      During the update operation, Unwired Server:
      • Acquires a list of assigned application connections from the original package.
      • Installs and assigns the package a new version number.
      • Prompts the administrator to specify application connection assignments from the acquired list of assigned application connections.
      • Preserves existing notifications.
      • Preserves the previous Unwired Server package version.
    • Replace – replaces an existing Unwired Server package with a new package, but maintains the same name and version. Sybase recommends that you use the replace deployment mode for minor changes and updates to the Unwired Server package, or during initial development.
      During the replace operation, Unwired Server:
      • Acquires a list of assigned application connections for each user of the original package.
      • Uninstalls the original package.
      • Installs the new package with the same name and version.
      • Assigns the original application connections list to the new package, thus preserving any application connection assignments associated with the original package.
    The package is added to the list of deployed packages, which are sorted by Display Name.
Next
Configure the deployed package if you want it to have a different set of properties in a production environment.
Related concepts
Hybrid App Packages
Related tasks
Configuring a Hybrid App Package