Deploying Mobile Applications

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

Deploying to non-BlackBerry devices

There are several deployment options available from Mobile Development. To perform any of these options, right-click the approved mobile application, select Deploy to Mobile Devices|Deploy Mobile Application to M-Business, and choose one of the following:

Create Public Channel – deploys the mobile application into an M-Business public channel. See Deploying to an M-Business Public Channel.
Create Group Channel – deploys the mobile application into an M-Business group channel. See Deploying to an M-Business Group Channel.
Create Mobile Application – deploys the mobile application into an M-Business mobile application. See Deploying to an M-Business Mobile Application.

Your next step is to deploy and sync the mobile application to the mobile device. See After Deploying Mobile Applications.

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).

Deploying the Unwired Accelerator client files to a BlackBerry device

The Deploy BlackBerry wizard allows you to deploy the Unwired Accelerator Blackberry client files to your BlackBerry device. To access the Deploy BlackBerry wizard:

Right-click the mobile application and select Deploy to Mobile Devices.
Select Deploy 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. The Deploy BlackBerry wizard opens.

The blackberry.properties file may look similar to:

BlackberrySimulatorDir=C:\\Program Files\\Research In Motion\\Blackberry JDE 4.0\\simulator
BlackberryDesktopDir=C:\\Program Files\\Research In Motion\\BlackBerry\\UA
RemoteLocation=tomcat/webapps/onepage/BlackBerry
RemoteLocationEAS=../Repository/WebApplication/onepage/BlackBerry

Specify the directories for the simulator and the desktop. The default directories are provided based on the contents of the blackberry.properties file. Select 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.
For the desktop from which you are deploying/syncing, download the files to the BlackBerry device.

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>