Packaging and deployment of BlackBerry Application Development Guide

UseBlackBerryDesktop software deployment applications wireless deployment applications use BlackBerry desktop software to deploy applications application load tool is part of BlackBerry desktop software, it uses an application to load files (. alx) Load new applications to BlackBerry devices

Use BlackBerry desktop software to deploy applications

The application loading tool is part of the BlackBerry desktop software. It uses an application to load files (. alx) to load new applications to BlackBerry devices.

Create an application for each application to load the file (. alx), and then distribute. alx and. cod to the user. For more information, see online help for loading applications.

Create an application to load files

1. In BlackBerry IDE, select a project.

2. Click Generate. alx file.

Distribute the. alx and. cod of the application to the user. When the user connects the BlackBerry device to their computer, they can use the BlackBerrry desktop software to load the application to the BlackBerry device.

Note: The default value is application. cod file and Its. the alx file is stored in the same directory. if you change the sum. alx file-related. cod location, Edit. add a <directory> element to the alx file to specify the file location. see "Appendix :. alx File Format "for more information.

Wireless Application Deployment

Handheld device software allows users to use the BlackBerry browser to wirelessly download applications. you can download standard MIDlet and BlackBerry applications. to allow users to download applications wirelessly, you must provide an appropriate application Descriptor (. jad), and. cod or. jar file. in the BlackBerry browser, select. the jad file to download the application.

The system administrator can set an application control policy to control the use of third-party applications. For more information, see "application control" on page 16.

Use the following methods to allow users to download BlackBerry or MIDlet applications wirelessly:

Use the BlackBerry MDS service to convert the. jar file to the. cod file.

Use BlackBerry JDE to create your project and generate a. cod file.

Deploy the. jar File

BES's BlackBerry MDS optimization service provides a built-in encoding converter, which will. jar file. cod file, which allows users to download standard MIDlet. for example, the company administrator can maintain a series of licensed MIDlet in the LAN. you can browse the web page and select one for the application. download jad files. before BES sends them to the BlackBerry device, it will. jar file. cod file.

Note: The Web server must be. cod file and. set the MIME type in the jad file. for. cod file. The MIME type is application/vnd. rim. cod. for. jad file. The MIME type is text/vnd. sun. j2s. app-

Descriptor. For. jar files, the MIME type is application/java-archive.

BES of the following versions supports converting. jar files to. cod files.

Microsoft Exchange BES 3.6 and later versions

IBM Lotus Domino BES 2.2 and later versions.

Note: If you use BES with the MDS service to access the network, they can only download it. jar file. the MDS service will. jar file required to convert to BlackBerry device. cod file format. if you use a WAP gateway to access the network, you can only download it. cod file.

MIDlet application descriptor attributes

The application descriptor file has a. jad extension. A standard MIDlet. jad file contains the following predefined attributes, and may also contain additional attributes defined by the application.

Deploy the. cod File

When you compile the project, BlackBerry JDE creates a required. jad file. You can also use BlackBerry JDE to convert the MIDlet. jar file to the. cod file format.

Make the. cod and. jar files on the web server for users to download. By making the. cod file available, you can deploy the application to those users who use BES but cannot access the network.

Note: The Web server must be. cod file and. set the MIME type in the jad file. for. cod file. The MIME type is application/vnd. rim. cod. for. jad file. The MIME type is text/vnd. sun. j2s. app-descriptor. for. jar file. The MIME type is application/java-archive.

BlackBerry Application descriptor attributes

In addition to the MIDlet application attributes, the following attributes are also applied to the BlackBerry. jad file.

BlackBerry allows you to create a binary. jad file, which supports downloading the MIDlet file to BlackBerry devices and other wireless devices. to implement it, create one that includes both the RIM-COD-URL and RIM-COD-Size attributes, as well as the MIDlet-Jar-URL and MIDlet-Jar-Size attributes. jad file. on the BlackBerry device, you can download. cod file, which can be downloaded from other devices. jar file.

Set dependencies between. cod files

. Jad contains a RIM-COD-Module-Dependencies attribute, which specifies the modules required by the application but does not provide it. if there are no required modules, the BlackBerry browser will prevent wireless installation of the application and list the lost modules for the user. the RIM-COD-Module-Dependencies attribute prevents users from downloading an application that cannot run.

The RIM-COD-Module-Dependencies attribute is a comma-separated Module name parameter. For example, an application that requires the rim xml library uses the following application descriptor:

 
 

  
  
RIM-COD-Module-Dependencies:net_rim_cldc,net_rim_xml 
 
 

Deployment brother. cod File

BlackBerry creates a single. cod file and. jad file. if the application contains code or source data larger than 64 KB, BlackBerry IDE creates a file containing a sibling file. cod file. only the BlackBerry browser supports. cod File Installation.

Note: If the. cod file needs to be verified, update the size of the verified. cod file in the. jad file. See BlackBerry IDE for more information.

Determines whether the. cod file contains the brother. cod file.

1. Extract the content of the. cod file.

Any. cod file in the original. cod file is a sibling file.

Use the MDS Service

To use the BlackBerry browser to deploy an application to a BlackBerry device ,. this device is already connected to BES with the MDS service in version 3.6.4 or later. cod file and. place the jad file on the web server. to deploy an application to a BlackBerry device ,. jad file and. the cod file must be placed on the web server. the MDS service uses a browser to download each brother. cod file, one at a time.

BlackBerry first loads the. jad file. MDS Service's MDS Provisioning Service (MDS supply Service) to repeat this process for the sibling files in each original. cod file.

Use the BlackBerry Internet service or WAP browser

To use the BlackBerry browser to deploy the application to a device without BES, modify. the jad file lists each sibling file separately. you must start from the original. each sibling file is extracted from the cod file and placed on the web server. the BlackBerry browser will follow. the jad file is listed in the order that only one sibling is downloaded at a time. cod file.

Note: To avoid overwriting the original. cod file, extract the brother. cod file to a different directory instead of the directory where the original file is located.

To extract the sibling. cod file, complete the following operations:

1. Extract the original. cod file and extract the file brother. cod.

2. Place each sibling. cod file on the web server.

3. In the. jad file, list the sibling. cod file separately. For each sibling file, create the RIM-COD-URL-<#>, RIM-COD-Size-<#> parameter.

RIM-COD-URL-: for every brother. the cod file creates a RIM-COD-URL-<#> and places the sibling file name on the right of the parameter. # add a number of 1 to each sibling file. every brother. cod file name and original. the cod file name is the same, followed by-<#>.

RIM-COD-Size-<#>: for every brother. create a RIM-cod-Size-<#> parameter in the COD file, and place the Size of each file on the right of the parameter. # It is the same as the number added to the name of the sibling file. place the RIM-COD-Size-<#> parameter next to the RIM-COD-URL-<#>.

In the following example, there are two sibling files. in the original. after the cod file myApp, the developer named the brothers file myApp-1.cod and myApp-2.cod. the developer adds '. cod 'extension. create a RIM-COD-Size-<#> parameter for each sibling file.

 
 

  
  
Manifest-Version: 1.0  
  
  
MIDlet-Version: 1.0.0  
  
  
MIDlet-1: ,,  
  
  
RIM-COD-Module-Dependencies: net_rim_cldc  
  
  
MicroEdition-Configuration: CLDC-1.0  
  
  
RIM-COD-Module-Name: MyApp  
  
  
MIDlet-Name: My Application  
  
  
RIM-COD-URL: myApp.cod  
  
  
RIM-COD-Size: 55000  
  
  
RIM-COD-URL-1: myApp-1.cod  
  
  
RIM-COD-Size-1: 50000  
  
  
RIM-COD-URL-2: myApp-2.cod  
  
  
RIM-COD-Size-2: 25000  
  
  
MicroEdition-Profile: MIDP-1.0 
 
 

Note: It is brother. the cod file uses the following naming rules: <original. cod File Name>-<serial number>. you must assign a number to each sibling file. this number starts from 1 and Adds 1.

4. Download each file from the BlackBery browser on the device where you plan to deploy the application.

BlackBerry Widget Development

BlackBerry user interface development instance

Demonstration and Analysis of BES push Application Instances

Interaction between BlackBerry applications and MIDlet

The beginning of RIM's mobile system BlackBerry OS 4.1