Deploying a Mobile Application Project

Deploy a Mobile Application project directly to an Unwired Server, and optionally create a reusable deployment profile.

To avoid errors or inconsistent behavior, client applications must be regenerated whenever a package has been redeployed. Restarting the client application is not sufficient to reset the client for a package that has been redeployed.
  1. Right-click the Mobile Application project and select Deploy Project.
    Alternatively, you can launch the deployment wizard, which automatically sets the Unwired Server portion of the wizard, by dragging a Mobile Application project folder from Workspace Navigator and dropping it on the Unwired Server in Enterprise Explorer to which you are deploying.
    Note: As an option, you can press F9 when your cursor is in the Mobile Application Diagram to launch the Deployment wizard for the corresponding project. If a deployment profile exists for the project, F9 performs quick deployment of the project according to the profile.
  2. Enter the deployment mode, target version, Package namespace, and click Next.
  3. Select the contents to be deployed and click Next.
  4. Create or add required JAR files for MBOs that use Resultset Filters or Custom Result Checkers and click Next.
  5. Select a target server for the project and click Next. (Optional) If no Unwired Server connection exists, click Create and define a connection profile for one to which you can connect and deploy the project.

    If a server connection has been open a long time without activity (a day or two for example), the connection may time out without your knowledge. While you may still be able to select the target server, deployment fails. Verify you have a working connection by pinging the server. If necessary, reconnect to the Unwired Server to which you are deploying from Enterprise Explorer.

  6. Map connection profile to server connections – You must map design-time connection profiles to server-side (run-time) enterprise information system (EIS) data sources referenced by the MBOs in the project. Deployment fails if the EIS data sources are not running and available to connect to. To map the connection profile to a server connection, select the connection profile from the list of available connection profiles then select the corresponding server connection to which it maps.

    Contact the system administrator in cases where your development environment permits access to systems that the Unwired Server prohibits.

    Note: You can also modify server connection properties (Web service connections only).
  7. If a logical role is defined in your MBO, map logical roles to physical roles. If there are no logical roles defined, this page is skipped. Click Next.
  8. (Optional) Specify the name and location for the new deployment profile:
    • Save the deployment settings as a deployment profile – if you do not save your settings to a deployment profile, they are lost when you exit the Deploy wizard.
    • Enter or select the parent folder – by default, Deployment is the folder in which the deployment profile is saved.
    • File name – the name of this deployment profile. The deployment profile is assigned a .deploy extension.
  9. Click Finish to deploy the project to the Unwired Server's Packages folder.