Deploying Packages

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

Prerequisites
If your developers have created a custom filter for the mobile business object you are deploying, you must copy class files to the primary server before you deploy the package that uses those filters. If you copy the filters to a slave server by mistake, they are deleted when you deploy the package to the primary server.

To locate the name of the master, look at the server list in Sybase Control Center. If a particular server is the master server of a cluster, it will be labeled as "primary" in the left navigation pane.

Task

Deploying is the process whereby whole or part of a mobile application is loaded onto an Unwired Server as one or more deployment units. Unwired Server can then make these units accessible to users via a client application that is installed on a mobile device.

Because the deployment unit file contains package name and other information, you do not need to select a package from the list of available packages; Unwired Server creates the package automatically according to what has been defined in the deployment file.
Note: If the connection properties of an MBO or operation use credentials that have been customized manually by a developer, the back-end data sources connection properties of these MBOs and operations cannot be updated by an administrator when using the Deploy Wizard.

Instead, the adminstrator can update these properties after the MBO or operation is deployed to an Unwired Server. When the server connection is created on Unwired Server, the administrator can then change connection properties in Sybase Control Center by clicking on the Connections node in the left navigation pane.

  1. Launching the Deploy Wizard
    Launch the Deploy wizard when the packages you require have already been created, or when you want Unwired Server to create a package for you from a deployment unit file.
  2. Configuring Deployment Properties
    Set the properties for packages being deployed on Unwired Server.
  3. Setting the Mapping State
    Map roles for a package by setting the mapping state. Mapping behavior is determined by the state that exists for the logical role. You can select AUTO or NONE; a third state, MAPPED, is set automatically after you manually map a physical role to the selected logical role.
  4. Updating Server Connection Properties
    Configure the production version of server connection properties. Typically, the endpoint and role mapping a developer would use are not the same for a production system. Administrators must reset these properties accordingly.
  5. Reviewing the Deployment Summary
    Review the properties you have supplied before deploying the package to Unwired Server. This allows you to change errors before making the deployment units available via the package created for that purpose.
Parent topic: Packages