Deploying Open Mobile 1.0 for BlackBerry

Open Mobile for BlackBerry is an easy-to-use Wi-Fi network connectivity manager for Wi-Fi enabled BlackBerry handheld devices. This guide provides the details of deployment options and tips for troubleshooting.

Deployment Options

Open Mobile for BlackBerry can be deployed in three different ways:

  • Directly to the device through the BlackBerry Web browser
  • Through BlackBerry Enterprise Server (BES)
  • Using BlackBerry Desktop Manager

Installing from the Web

Installing from the Web enables quick user-initiated installation for end users with existing Internet connectivity. This method requires configuration of your Web server, and then publication of the installation URL.

Installation Files

After creating the installer on the Open Mobile Portal, download the installation files.

Your Web server must be configured for two MIME types so that the server can deliver the installation files to the BlackBerry Web browser. The necessary MIME types are as follows:

  • .JAD files: text/
  • .COD files: application/vnd.rim.cod

Sample entry in Apache Webserver configuration file mime.types:

text/ jad

application/vnd.rim.cod cod

Sample entry in Apache Webserver .htconfig file:

AddType text/ .jad AddType application/vnd.rim.cod .cod

Configuration Procedure

To configure web installation:

1. Configure the required MIME types for the Web server as described earlier.

2. Upload the deployment files (.JAD and .COD files) to a public location on your Web server. Note the complete URL of the .JAD file.

3. Distribute this installation URL to your users.

User Actions

The BlackBerry user connects to the Internet (by Wi-Fi or Mobile Broadband), and browses to the installation URL. The browser will download the application and install it interactively, prompting the user as needed.

Deployment using BlackBerry Enterprise Server

Enterprises wishing to distribute Open Mobile for BlackBerry to a large number of users will generally find BlackBerry Enterprise Server (BES) to be the most efficient method of distribution. This method is suitable for large-scale push installation to many BlackBerry devices.

iPass Technical Support is not responsible for supporting the BES or other third-party applications, but will support configuration of the Open Mobile distribution steps shown here.

Configuring the BES

To configure the BlackBerry Enterprise Server for Open Mobile deployment:

1. On the BES, create or select an Open Mobile installation folder.

2. Extract the.COD and .ALX installation files and upload them to the designated installation folder.

3. Launch the Apploader tool, and run loader/index to index Open Mobile application and add it to the application software list.

4. Create a software configuration for the Open Mobile application and set the Delivery field to Wireless.

5. Set the correct application control policy for Open Mobile in the Software Configurations window.

6. Using the Device Management features, select the BlackBerry device user and assign the appropriate software configuration to install Open Mobile.

7. The application will subsequently be delivered to each device.

Depending on the version of BES you are using, there may be additional client-side steps required to configure application deployment. Consult your BlackBerry Enterprise Server documentation, available from RIM, for details.

Deployment using BlackBerry Desktop Manager

The BlackBerry Desktop Manager software enables a BlackBerry user to add new applications and software updates to the device over a local connection (usually a USB cable). Open Mobile installation can be combined with updates to the operating system or third party software.

This method is detailed in the Open Mobile 1.0 for BlackBerry User’s Guide.


Event Logs

Open Mobile uses the BlackBerry Event Logger utility to record events for diagnostic purposes at three different levels of verbosity: Warning, Information, and Debug Info.

* Warning events consist primarily of failures to complete an operation visible to the user, such as a failure to login. This is the default log level. * Information events are primarily used to announce the start or end of an operation, such as initiation of a login or its successful completion. Taken together, warning and information events from Open Mobile are intended to provide technical support staff with an effective problem isolation tool.

* Debug Info events are reserved for low-level diagnostic information, such as network protocol messages. The events logged at this level are normally intended for interpretation by iPass development.

Managing Event Logs

To invoke the BlackBerry Event Log:

1. On the BlackBerry main menu, press and hold the ALT key and type LGLG (not case sensitive).

By default, the log level is set to Warning, but you can change the log level to any other level. When troubleshooting Open Mobile, we recommend elevating the log level to at least the Information level.

To change the log level:

1. From the Event Log, press the menu key and click Options to open the EventLogger Options window.

2. For Min Log Level, select a new level, such as Information or Debug Info.

3. In the list of apps, locate Open Mobile and make sure it is checked. To reduce the total size of Event Logger logs, you may optionally choose to disable logging for other applications.

Reviewing Event Logs

BlackBerry event logs can be extracted to a Windows PC with a USB cable, using the RIM-supplied JavaLoader executable tool (included with the BlackBerry SDK). Launch the tool and enter the following command line:

javaloader -usb eventlog > event.log

The event logs are in text format, which can be viewed using any text editor.


©2015 iPass Inc. All rights reserved. Terms of Use