Deploying Composite Applications

Once you have created a composite application, associated it with the appropriate template, and performed the tasks described in Before Deploying Mobile Applications, you can deploy the composite application.

Deploying to non-BlackBerry devices

  1. There are several deployment options available from Mobile Development. To perform any of these options, right-click the approved composite application and select Deploy.

  2. In the Deploy Composite Application wizard, select from these deployment options:

    • Deploy Composite Application to M-Business – when you select this option, Create Mobile Application is the only available option, and, by default, it is selected. This option deploys the composite application into an M-Business mobile application. See Deploying to an M-Business Mobile Application.

    • Deploy Composite Application to BlackBerry – when you deploy the composite application to a BlackBerry device, a new mobile application is created.

    • Download the Unwired Accelerator BlackBerry Client – this option is available only if the file, blackberry.properties exists in the com.sybase.epclient plugin directory, which is created by the installation program. The installation program checks for the existence of the BlackBerry simulator and the BlackBerry desktop, and adds those directories to the blackberry.properties file. In addition, it adds two properties for the default location of the UAbbapp.cob and UAbbapp.alx files on the server.

    Click Next.

  3. This step varies according to which option you selected in the previous step. The table below describes the different wizards.

    Deployment wizards

    If you selected:You see this wizard
    Deploy Composite Application to M-Business

    Mobile Application wizard

    • Your configuration options are:

      • Group – the group for this database channel.

      • Protected – if selected, requires that AvantGo browser users use biometrics (finger-printing) authentication to view the content.

    Deploy Composite Application to BlackBerry

    BlackBerry Composite Application wizard – when you click Finish, a new mobile application is created with an HTML element structured as a table. The table headers are the tab names and the table content is each mobile application name.

    A server-side click-across event is attached to each mobile application, linking them to the actual mobile applications. Some basic record layout, split, and filter rules are set on the HTML element.

    Download the Unwired Accelerator BlackBerry Client

    BlackBerry wizard

    1. Specify the directories for the simulator and the desktop. The default directories are provided based on the contents of the blackberry.properties file. Click Browse to change the entries. When you click Finish, the selected .cod and .alx files are downloaded from the server to the specified directories. You need to do this only once. If you select Deploy BlackBerry at a later time, the Override option allows you to overwrite the .cod and .alx files.

    2. For the desktop from which you are deploying/syncing, download the files to the BlackBerry device.

  4. Click Finish.

  5. Your next step is to deploy and sync the mobile application to the mobile device.

Deploying to BlackBerry devices

Once you create the application, you must perform the deploy/sync operation. This is documented in the Unwired Accelerator 7.0 Quick Start Guide, and in the Unwired Accelerator 7.0 Mobile Application Development Tutorial (see Chapter 7, Deploying Applications to BlackBerry Devices).

Installing BlackBerry files after Unwired Accelerator

If you install BlackBerry software after Unwired Accelerator, the BlackBerry entries in the blackberry.properties file are not included. You need to add them manually (or, only the Desktop entry if the simulator or JDE is already installed). Either way, check the entries and correct as necessary. For example:

BlackberrySimulatorDir=<path of the blackberry simulator directory>
BlackberryDesktopDir=<path of blackberry JDE directory>\\UA
RemoteLocation=<path of the blackberry webapplication in tomcat>
RemoteLocationEAS=<path of the blackberry webapplication in EAServer>

Related Tasks

Before Deploying Mobile Applications

Deploying to an M-Business Mobile Application

After Deploying Mobile Applications

Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com