BlackBerry_Java_SDK-Development_Guide--Network Comm

BlackBerry Java SDKNetwork CommunicationVersion: 6.0

Development Guide

Published: 2010-11-08SWD-1327377-1111022758-001

Contents1 Network communication overview........................................................................................................................................... 3

2 Communication API.................................................................................................................................................................... 4

Communicating with HTTP servers............................................................................................................................................... 5

Request data using a BlockingSenderDestination object................................................................................................. 6

Request data using a NonBlockingSenderDestination object.......................................................................................... 8

Send data using a FireAndForgetDestination object......................................................................................................... 10

Parsing a common Internet data format............................................................................................................................. 11

Subscribing to a push initiator...................................................................................................................................................... 12

Subscribe to a push initiator................................................................................................................................................. 13

Sending login information to an HTTP server............................................................................................................................. 14

3 Network tranports....................................................................................................................................................................... 15

Architecture: Network transports................................................................................................................................................. 15

Using the BlackBerry Enterprise Server as an intranet gateway.............................................................................................. 18

Using a wireless service provider's Internet gateway................................................................................................................ 18

4 Network connections.................................................................................................................................................................. 20

The Network API............................................................................................................................................................................. 22

Choosing network transports using the Network API....................................................................................................... 22

Opening a network connection using the Network API.................................................................................................... 22

Generic Connection Framework.................................................................................................................................................... 24

Open a network connection using the GCF........................................................................................................................ 25

Send and receive data using a network connection................................................................................................................... 26

Network transport options............................................................................................................................................................. 29

5 Working with radios.................................................................................................................................................................... 32

Query a radio's availability and change its status...................................................................................................................... 32

6 Code samples............................................................................................................................................................................... 34

Code sample: Requesting data using a BlockingSenderDestination object............................................................................ 34

Code sample: Requesting data using a NonBlockingSenderDestination object.................................................................... 37

Code sample: Parsing a JSON data structure............................................................................................................................. 40

Code sample: Retrieving a web page using the Network API................................................................................................... 44

Code sample: Retrieving a web page using the GCF................................................................................................................. 49

Code sample: Determining network transports with sufficient coverage using the Network API....................................... 52

Code sample: Controlling radios................................................................................................................................................... 54

Code sample: Determining the status of a network transport using the Network API.......................................................... 56

7 Glossary......................................................................................................................................................................................... 59

8 Provide feedback......................................................................................................................................................................... 62

9 Document revision history......................................................................................................................................................... 63

10 Legal notice.................................................................................................................................................................................. 64

Network communication overview 1

A BlackBerry® device uses radio communication technologies such as Wi-Fi® technology, CDMA, or GPRS to communicate overwireless connections. BlackBerry devices work with different network transports over those radio technologies to connect to theInternet or a private network. Each transport offers different advantages. As a developer, you should choose the transport thatis most appropriate for your requirements.

When you choose a transport for your application, you should consider a number of different factors, including:• Type of user• Importance of security and reliability• Networks that the application must use and support for roaming users• Amount of data that you expect to send and receive• Need to proactively push data for updates and alerts• Location of the destination server (Internet or intranet)

The BlackBerry® Java® SDK 6.0 includes three APIs that you can use to open a network connection.

API Description

BlackBerry

Device Software

version

Communication API The Communication API encapsulates all of the operations that are

required to connect to an HTTP server that is located on the Internet

or behind an organization's firewall.

6.0 and later

Network API The Network API provides a simple interface to access many

connection-related options and network transports.

5.0 and later

Generic Connection Framework The GCF provides a flexible way to create network connections

using the transport of your choice.

4.0 and later

In addition to the functionality that each API provides, you should consider whether the API exists in the version of the BlackBerry®Device Software that your target devices are likely to run. For example, the Communication API requires BlackBerry DeviceSoftware 6.0. You would need to write your own code to perform similar tasks on devices that run BlackBerry Device Software5.0 and earlier.

The BlackBerry solution also enables server-side applications to proactively push data to BlackBerry devices in a highly secureand reliable manner.

Development Guide Network communication overview

3

Communication API 2

The Communication API simplifies the process of interacting with web services and other applications. The objects that you createusing this API automate the process of finding an available network transport, creating a thread-safe connection, and negotiatingan exchange of data with the URI or URL end point that you specify. The API is implemented in thenet.rim.device.api.io.messaging package.

Within the Communication API, URI and URL end points are called destinations. You can use objects that implement theSenderDestination interface to send data to a web service and access the response. Similarly, you can use objects thatimplement the ReceiverDestination interface to subscribe to a push service and provide access to new messages fromthat service. You must use the DestinationFactory class to create an object that implements one of the Destinationsubinterfaces that suits your requirements.

Interface Description

BlockingSenderDestination You can use this interface to send a message to a web service, but this

object blocks thread execution while it waits for a response from the web

service.

Alternatively, BlockingSenderDestination can return a

MessageFuture object. This allows thread execution to continue until

you invoke one of the get() methods from the MessageFuture.

When you invoke sendReceive() in

BlockingSenderDestination to send a message and wait for a

response, you should not invoke it from the main event thread.

NonBlockingSenderDestination You can use this interface to send a message to a web service. In the

parameter list, pass your implementation of the MessageListener

interface to receive the response from the web service.

BlockingReceiverDestination You can use this interface to subscribe to a push service and block thread

execution until you receive confirmation of your subscription request.

NonBlockingReceiverDestination You can use this interface to subscribe to a push service. In the parameter

list, pass your implementation of MessageListener to receive push

messages.

FireAndForgetDestination You can use this interface to send data to a web service when you don't

expect a response.

Development Guide Communication API

4

Data that you send to and receive from a web service is wrapped in a Message object. You can set the headers and content ofthe data that is sent to a web service in the Message object. Alternatively, you can allow the Communication API to choosereasonable default values for your request. For example, you can request a web page by invoking SenderDestination.send() without specifying an HTTP GET command.

You can also instruct the API to automatically parse the response data from a web service. If you implement theMessageProcessor interface with your parser class, you can supply your parser object to the method inDestinationFactory that creates your Destination object. You can then retrieve the parsed response usingMessage.getObjectPayload().

The net.rim.device.api.io.parser packages contain message processors for a variety of standard data formats thatare used on the Internet. The packages include parsers for:• JSON• RSS (RDF, Atom)• SOAP• XML

To improve efficiency, the Communication API provides large responses from web services in an InputStream object. Anapplication can request additional data as required rather than downloading a large amount of data at once and storing it inmemory on the device. This approach enables you to make better use of both network bandwidth and memory.

Communicating with HTTP serversTo send a command to an HTTP server, you need a SenderDestination object to communicate with an end point. TheSenderDestination object is responsible for queuing messages for delivery, and retrieving incoming messages for delivery.The DestinationFactory class creates and maintains a list of Destination objects that you can use to communicatewith an end point.

Before you create a SenderDestination, you should check whether one exists by invoking getSenderDestination(). You can access an existing destination by providing the name of the Context object that you supplied when you invokedany of the DestinationFactory.create...() methods.

When you finish exchanging data with an end point, you should invoke DestinationFactory.release() orDestinationFactory.destory(). The release() method removes the association between a Destination andthe inbound and outbound message queues. After you invoke release(), the API continues to attempt the delivery of messagesin the queue. You can use release() when your application is not in a state to send and receive messages. In addition toremoving the association between a Destination and the a message queue, destroy() also destroys the message queue.After you invoke destory(), any messages in the queue will be deleted.

A message contains the details of your command, including the HTTP request method and any additional data that you require.If you do not specify all parameters for your message, default values are provided by the Communication API.

Development Guide Communicating with HTTP servers

5

After you send your message, you may need to listen for a response. For BlockingSenderDestination objects, you needto create a Thread object when you invoke one of the sendReceive() methods. ForNonBlockingSenderDestination objects, you must create a MessageListener object to receive the response.

In either case, you need to process a Message object that contains the response. By default, the body of the Message containsthe raw response data. You can choose to specify a message processor from the net.rim.device.api.io.parserpackage, or create your own using the MessageProcessor interface.

If necessary, you can connect multiple message processors together. The MessageProcessorChain class shares memorybetween the MessageProcessor objects to improve efficiency. For example, if you receive video data that uses customencoding and compression, you can separate the decoding and decompression logic into separate message processors, and thenuse MessageProcessorChain to group them together.

Request data using a BlockingSenderDestination object1. Import the required classes and interfaces.

import net.rim.device.api.io.messaging.*;import net.rim.device.api.io.URI;

2. Create a thread from which to call BlockingSenderDestination.sendReceive().

Thread t = new Thread( new Runnable(){ public void run() {

3. Create a Message object to hold the response from the URL.

Message response = null;

4. Create a URI object to pass to the DestinationFactory class.

URI uri = new URI("http://www.blackberry.com");

5. Create a BlockingSenderDestination object.

BlockingSenderDestination bsd = null;

6. Retrieve the BlockingSenderDestination object for your context, if one exists.

try { bsd = (BlockingSenderDestination) DestinationFactory.getSenderDestination ("MyContext", uri);

7. If no BlockingSenderDestination exists, create one.


6

if(bsd == null) { bsd = DestinationFactory.createBlockingSenderDestination (new Context("MyContext"), uri); }

8. Send a message and wait for the response.

response = bsd.sendReceive();

9. If the web service sent a response, process the response.

if(response != null) { processResponse(response); } }

10. Catch any errors that occur if the message could not be sent for some reason.

catch (Exception e) { // Process the error }

11. Release the BlockingSenderDestination.

finally { if(bsd != null) { bsd.release(); } } }

});

12. Start the thread.

t.start();

After you finish: If your processResponse() updates the UI, you must do so on the main event thread, not on the threadthat you created in this task. For more information, read the knowledge base article at http://supportforums.blackberry.com/t5/Java-Development/Manage-UI-interactions/ta-p/502378.

For a complete code sample, see "Code sample: Requesting data using a BlockingSenderDestination object".


7

Request data using a NonBlockingSenderDestination object

Before you begin: To request data using the NonBlockingSenderDestination class, create an object that implementsthe MessageListener interface. For more information, see "Implement the MessageListener interface".

1. Import the required classes and interfaces.


2. Create a Message object to hold the response from the URL.

Message response = null;


URI uri = new URI("http://www.blackberry.com");

4. Create a NonBlockingSenderDestination object.

NonBlockingSenderDestination nbsd = null;

5. Create a reference to your MessageListener.

MyMessageListener msgListener = new MyMessageListener();

6. Retrieve the NonBlockingSenderDestination object for your context, if one exists.

try{ nbsd = (BlockingSenderDestination) DestinationFactory.getSenderDestination ("MyContext", uri);

7. If no NonBlockingSenderDestination exists, create one.

if(nbsd == null) { nbsd = DestinationFactory.createNonBlockingSenderDestination (new Context("MyContext"), uri, msgListener); }

8. Send a message to the web service.

nbsd.send();



After you finish: Release the NonBlockingSenderDestination when you are done processing the response.


8

For a complete code sample, see "Code sample: Request data using a NonBlockingSenderDestination object"

Implement the MessageListener interfaceYou can use the MessageListener interface to receive messages that are sent by aNonBlockingSenderDestination object, or push messages that are sent from a push initiator.


import net.rim.device.api.io.messaging.*;

import java.io.IOException;import java.io.InputStream;

2. Define a class that implements the MessageListener interface.

public class MyMessageListener implements MessageListener {

3. Implement onMessage().

public void onMessage(Destination dest, Message incomingMessage) {

4. Initialize a String variable to hold the response data.

String payload = null;

5. If the response is a ByteMessage object, retrieve the response as a String and assign it to payload.

if (incomingMessage instanceof ByteMessage) { ByteMessage reply = (ByteMessage) incomingMessage; payload = (String) reply.getStringPayload(); }

6. If the response is a StreamMessage, retrieve the response as an InputStream object.

else if(incomingMessage instanceof StreamMessage) { StreamMessage reply = (StreamMessage) incomingMessage; InputStream is = reply.getStreamPayload();

a. If the response is small, convert the contents of the stream into a byte array.

byte[] data = null; try { data = net.rim.device.api.io.IOUtilities.streamToBytes(is); } catch (IOException e) { // process the error }

b. If the conversion was successful, convert the byte array to a String and assign it to payload.


9

if(data != null) { payload = new String(data); } }

7. If payload contains data, display it.

if(payload!=null) { synchronized(Application.getEventLock()) { UiApplication.getUiApplication().pushScreen (new HTTPOutputScreen(payload)); }

}

After you finish: Implement onMessageCancelled() and onMessageFailed() to process other notifications.

For a complete code sample, see "Code sample: Request data using a NonBlockingSenderDestination object"

Send data using a FireAndForgetDestination object1. Import the required classes and interfaces.



URI uri = new URI("http://www.example.com");

3. Create a FireAndForgetDestination object.

FireAndForgetDestination ffd = null;

4. Retrieve the FireAndForgetDestination object for your context, if one exists.

try{ ffd = (FireAndForgetDestination) DestinationFactory.getSenderDestination ("MyContext", uri);

5. If no FireAndForgetDestination exists, create one.

if(ffd == null) { ffd = DestinationFactory.createFireAndForgetDestination (new Context("MyContext"), uri); }


10

6. Create a ByteMessage object and populate it with information to send to a web service.

ByteMessage myMsg = ffd.createByteMessage(); myMsg.setStringPayload("I love my BlackBerry device!");

7. Cast your message as an HTTPMessage to set the HTTP method that you want to use.

((HttpMessage) myMsg).setMethod(HttpMessage.POST);

8. Send the message to the web service.

ffd.sendNoResponse(myMsg);



Parsing a common Internet data formatYou can configure a Destination object to return a Java® object that contains data parsed from a standard format, such asJSON. To retrieve the data structure in a Java object, you should:

1. Specify a MessageProcessor object when you invoke DestinationFactory.create...().

2. Retrieve the response from your Destination.

3. Extract the data from the Message object that is returned in the response.

Code sample

The following code sample demonstrates the three actions that are required to retrieve a Java object that contains a JSON datastructure.

import net.rim.device.api.io.messaging.*import net.rim.device.api.io.parser.json.*

// Specify a MessageProcessor when you create your DestinationBlockingSenderDestination bsd = DestinationFactory(myContext, myURI, new JSONMessageProcessor());

// Retrieve the responseMessage response = bsd.sendReceive();

// Extract the Java object that contains the JSON data structureObject payload = response.getObjectPayload();

Development Guide

11

Subscribing to a push initiatorYou can use the Communication API to send a subscription request to a content provider's URI. In addtition to theSenderDestination object that sends the subscription request, you need to create a ReceiverDestination object thatdefines the MessageListener object to which the BlackBerry® device should deliver incoming push messages from a givenURI.

The following table describes the components that are involved in a subscription request.

Component Description

SenderDestination This component sends the subscription message to the

content provider. This component is optional. You can

send a subscription message using any type of network

connection. For example, you can use the Network API

to create an HTTPConnection and send the

subscription parameters manually.

Subscription message The Communication API can create a properly formed

subscription message for you. You can invoke

BpsSubscriptionMessageBuilder.createB

yteSubscriptionMessage() to retrieve a

ByteMessage object that is configured for your

SenderDestination,

NonBlockingReceiverDestination, and the

MessageListener where you want to receive

incoming push messages.

NonBlockingReceiverDestination This component associates a particular URI with a

MessageListener where you want to receive

incoming push messages, and an

InboundDestinationConfiguration object.

InboundDestinationConfiguration This component specifies a variety of push service

parameters, such as an indicator that specifies whether

your application should be started when a new push

message arrives. You can create an

Development Guide Subscribing to a push initiator

12

Component Description

InboundDestinationConfiguration using the

InboundDestinationConfigurationFactor

y class.

MessageListener This component processes incoming push messages.

Subscribe to a push initiatorThis task focuses on creating a subscription message and the NonBlockingReceiverDestination object for aBlackBerry® Push Service subscription. You must send your subscription message using a SenderDestination object, or bycreating a network connection manually.

Before you begin: Obtain an application ID and the local port number that your application should use to listen for incomingmessages. These details are provided to the content provider that creates a server-side push application.


import net.rim.device.api.io.messaging.*;

2. Initialize a NonBlockingReceiverDestination variable to manage the subscription.

NonBlockingReceiverDestination nbrd = null;

3. Create a MessageListener object to process incoming push messages.

try{ MyMessageListener pushListener = new MyMessageListener();

4. Create a URI object with the port information that the content provider assigns to you.

URI pushURI = URI.create("http://:101");

5. Create an InboundDestinationConfiguration object to set parameters for the push subscription.

InboundDestinationConfiguration config = InboundDestinationConfigurationFactory.createBPSConfiguration (true, // start this application when a push message arrives false, // allow other applications to receive these push messages false, // do not store these messages (persistence not supported) "12-Ab234cD5eF67h890", // application ID, BPSuri); // BlackBerry Push Service URI

6. Create a NonBlockingReceiverDestination.

nbrd = DestinationFactory.createNonBlockingReceiverDestination (config, pushURI, pushListener);

7. Create a SenderDestination to send a subscription message.

Development Guide Subscribing to a push initiator

13

NonBlockingSenderDestination bpsDestination = DestinationFactory.createNonBlockingSenderDestination (myContext, uri, responseListener);

8. Configure a subscription message.

ByteMessage subMsg = BpsSubscriptionMessageBuilder.createByteSubscriptionMessage (bpsDestination, nbrd, "user", "pwd");

9. Send the subscription message.

bpsDestination.send();

Sending login information to an HTTP serverA Destination object can supply login information, such as a user name and password, when a web server requests it. Logininformation is stored in the Context object that you supply when you create a Destination using theDestinationFactory class.

Code sample

context = new Context("DemoContext", new CredentialsCollector() { public UsernamePasswordCredentials getBasicAuthenticationCredentials (String aeID, Hashtable properties) { // Provide or retrieve authentication credentials here. // For example, you could display a dialog box to ask your user // to enter a username and password, then return them from // this method. return new UsernamePasswordCredentials("username", "password"); }});

Development Guide Sending login information to an HTTP server

14

Network tranports 3

Architecture: Network transportsA BlackBerry® device can connect to a wireless network by using different transports. Not all devices have access to all transports.For example, the BlackBerry® Mobile Data System transport is only available to devices registered with a BlackBerry® EnterpriseServer.

Development Guide Network tranports

15

Network transport Description

TCP Wi-Fi® The Wi-Fi transport creates a connection to the Internet, or to private networks such

as those in an organization or home. When the Wi-Fi radio is turned on, a BlackBerry

device user or an application can configure the device to connect to the Internet

using this transport.

Development Guide Architecture: Network transports

16


If appropriate, the device may automatically send data to a BlackBerry Enterprise

Server or BlackBerry® Internet Service over a Wi-Fi connection. For example, if the

device is connected to a Wi-Fi network and a VPN profile is configured for the user's

organization, the device attempts to connect to the BlackBerry Enterprise Server

over the VPN using the Wi-Fi connection because transmitting data over Wi-Fi is

usually less expensive than other transports. This behavior is known as least cost

routing.

TCP Cellular The TCP Cellular transport creates a connection to the Internet through a wireless

service provider's Internet gateway. This method creates the most direct type of

connection that uses the cellular radio.

Most wireless service providers configure a user's BlackBerry device to use the

provider's Internet gateway. However, when the user roams on a different network,

the user needs to configure the device manually to use the Internet gateway on the

host network.

If your application uses this transport, you should test it for each wireless service

provider that your application might use.

BlackBerry Internet Service The BlackBerry Internet Service transport creates a connection to the Internet

through the BlackBerry® Infrastructure. Data that you send and receive using this

transport is compressed and optimized for transmission over wireless connections.

Applications that use the BlackBerry Internet Service transport automatically

benefit from least cost routing. The device connects over a Wi-Fi network

automatically, if one is available.

Note: To use the BlackBerry Internet Service transport, you must sign up for the

BlackBerry® Push Service. For more information, visit http://na.blackberry.com/

eng/developers/javaappdev/pushapi.jsp

BlackBerry MDS The BlackBerry MDS transport enables a BlackBerry device to connect to its

associated BlackBerry Enterprise Server through the BlackBerry Infrastructure or

using a Wi-Fi connection.

For more information, see "Using the BlackBerry Enterprise Server as an intranet

gateway".

WAP The WAP transport creates a connection through a wireless service provider's WAP

gateway. WAP 1.0, 1.2, and 2.0 are supported.

Development Guide Architecture: Network transports

17

http://na.blackberry.com/eng/developers/javaappdev/pushapi.jsp



To support this transport, a user or wireless service provider must configure the WAP

connection parameters on the device. As a result, this transport might not be

supported on all wireless networks or with all data plans.

If your application uses this transport, you should test it for each wireless service

provider that your application might use. For more information, see "Using a wireless

service provider's Internet gateway".

To use WAP 2.0, you will need to retrieve the connection ID from the service book.

For more information about retrieving a connection ID, see the knowledge base

article at http://supportforums.blackberry.com/t5/Java-Development/What-Is-

Network-API-alternative-for-legacy-OS/ta-p/614822

Using the BlackBerry Enterprise Server as an intranet gatewayOrganizations host the BlackBerry® Enterprise Server behind their firewall to allow BlackBerry device users to access theorganization's intranet. The BlackBerry® Mobile Data System component of the BlackBerry Enterprise Server includes theBlackBerry® MDS Services, which provides an HTTP and TCP/IP proxy service to let third-party Java® applications use it as ahighly secure gateway for managing HTTP and TCP/IP connections to the intranet. When you use the BlackBerry EnterpriseServer as an intranet gateway, all data traffic between your application and the BlackBerry Enterprise Server is encryptedautomatically using AES encryption or Triple DES encryption. Because the BlackBerry Enterprise Server is located behind theorganization's firewall and provides inherent data encryption, applications can communicate with application servers and webservers that reside on the organization's intranet.

If your application connects to the Internet rather than an organization's intranet, you might be able to use the BlackBerryEnterprise Server that the device is associated with as a gateway. In this case, network requests travel behind an organization'sfirewall to the BlackBerry Enterprise Server, which makes the network request to the Internet through the firewall. Organizationscan set an IT policy to enforce the use of the BlackBerry Enterprise Server as the gateway for all wireless network traffic, includingtraffic destined for the Internet.

Using a wireless service provider's Internet gatewayMost wireless service providers provide an Internet gateway that offers direct TCP/IP connectivity to the Internet. Some wirelessservice providers also provide a WAP gateway that allows HTTP connections to use the WAP protocol. A BlackBerry® Java®Application can use either of these gateways to connect to the Internet. If your application is for BlackBerry device users whoare on a specific wireless network, using the wireless service provider's Internet gateway can often yield fast, and reliable

Development Guide Using the BlackBerry Enterprise Server as an intranet gateway

18

connections. If your application is for users on a variety of wireless networks, testing your application against the different Internetgateways can be challenging. In this case, you should use the BlackBerry® Internet Service transport, and use the wireless serviceprovider’s Internet gateway as a backup connection type if the BlackBerry Internet Service transport is not available.

Development Guide Using a wireless service provider's Internet gateway

19

Network connections 4

The BlackBerry® Application Platform offers two APIs that you can use to create network connections manually: the NetworkAPI and the GCF. Applications that target BlackBerry® devices that run BlackBerry® Device Software 5.0 and later can use theNetwork API. The Network API provides a simple interface for working with network transports, and setting a wide variety ofparameters for a connection. You can use the GCF to create network connections on devices that run previous versions of theBlackBerry Device Software. However, using the GCF requires knowledge of more BlackBerry® APIs to discover what transportsare available and how to configure them.

Regardless of which API you choose, the process of creating a network connection is similar. First, you open a network connection,then read and write data over that connection, and finally close the connection. Before you open a connection, you usually specifya transport, a protocol, and an end point. You can connect to network resources using a wide range of protocols. However, youshould be aware that not all transports support all protocols. For example, WAP 1.0 and 1.1 only support HTTP over WAP andHTTPS over WAP or WTLS. The BlackBerry Application Platform supports the following protocols:

• HTTP• HTTPS• Socket• TLS• SSL• UDP (Datagram)

The protocol and the end point are determined by your application, but the transport is determined by your users' operatingenvironment. You may need to try more than one transport before you can make a successful connection. The following tablesuggests preference orders for enterprise and consumer applications.

User type Preferred order of transports

Enterprise 1. BlackBerry® Mobile Data System

2. TCP Wi-Fi®

3. WAP 2.0

4. BlackBerry® Internet Service

5. TCP Cellular

6. WAP 1.0 or 1.1

Consumer 1. TCP Wi-Fi

2. WAP 2.0

3. BlackBerry Internet Service

Development Guide Network connections

20

User type Preferred order of transports

4. BlackBerry MDS

5. TCP Cellular

6. WAP 1.0 or 1.1

After you open a connection, you receive a Connection object that represents your connection. Thejavax.microedition.io package contains several interfaces that you can use to manipulate a Connection object.

Interface Description

HttpConnection This interface provides methods to set the HTTP request method (GET, POST, and

so on) and headers, and send and receive data over the connection.

HttpsConnection This interface includes all of the methods in the HttpConnection interface, and

adds getSecurityInfo() that returns the certificate that is supplied by the

web server.

SocketConnection This interface exposes methods to send data to and receive data from a network

host over a socket connection.

SecureConnection This interface provides methods to create TLS and SSL socket connections. This

interface includes all of the methods in the SocketConnection interface, and

adds getSecurityInfo() that returns security information about the

connection.

UDPDatagramConnection This interface provides methods to retrieve information about the connection, and

create new datagram objects.

InputConnection,

OutputConnection

These interfaces provide access to a connection's input and output data streams.

When you are ready to use your connection, cast the Connection object according to the protocol that you used to open theconnection. You will need the InputConnection and OutputConnection interfaces from thejavax.microedition.io package to access the Connection object's send and receive functions. Those interfaces exposethe Connection object's input and output streams. For more information about sending data over the connection, see theInputStream and OutputStream classes in the API reference for the BlackBerry® Java® SDK.

Development Guide Network connections

21

The Network APIThe Network API is implemented in the net.rim.device.api.io.transport andnet.rim.device.api.io.transport.options packages. Most of the functionality is provided by theConnectionFactory and TransportInfo classes. A ConnectionFactory object returns aConnectionDescriptor object that contains a Connection object and information about the transport over which theconnection was opened.

Choosing network transports using the Network API

In the Network API, the TransportInfo class provides information about the network transports that are available on aBlackBerry® device. You can retrieve a list of transports that currently have coverage, or use the API to determine whether aparticular transport is available and has coverage.

If you don't provide an ordered list of preferred transports when you open a connection, the Network API chooses a transport foryou. However, you should prioritize the transports that your application uses based on the type of user that your applicationtargets. The API steps through an array of transport types that you set by usingConnectionFactory.setPreferredTransportTypes().

After you list your preferred transports, you should set options for any transports that require specific options. For example, theWAP 1.0 and 1.1 transports require information about an APN, and the gateway authentication, and so on. For more information,see "Network transport options".

You should also create a CoverageStatusListener object (in the net.rim.device.api.io.transport package),and register it using TransportInfo.addListener(). The device notifies your application about changes in coveragestatus so that your application can respond appropriately.

Opening a network connection using the Network APIAfter you decide which network transports to use, you can open a connection and use it to send and receive data. TheConnectionFactory object is responsible for opening connections. In addition to your preferred transports, you can use theConnectionFactory to configure connection options such as:• Maximum number of connection attempts.• Maximum time to spend making connection attempts.• Delay between connection attempts.• Whether or not encryption is required between the connection end points.

When you are ready to open a connection, you should invoke one of the ConnectionFactory.getConnection() methods.Be sure that you call getConnection() on a thread that is separate from the main event thread. For more information aboutcreating a thread, see the Thread class in the API reference for the BlackBerry® Java® SDK.

Development Guide The Network API

22

When you open a connection successfully, the ConnectionFactory returns a ConnectionDescriptor object. TheConnectionDescriptor contains a Connection object, and information about the transport that was used to open theconnection.

For more information, see "Open a network connection using the Network API" and "Send and receive data using a networkconnection".

Open a network connection using the Network APICAUTION: The ConnectionFactory.getConnection() method blocks thread execution. You should create a separatethread to call getConnection().


import net.rim.device.api.io.transport.*;import net.rim.device.api.io.transport.options.*;import net.rim.device.api.io.transport.TransportInfo;import net.rim.device.api.ui.UiApplication;

2. Create an ordered list of preferred transports.

int[] intTransports ={ TransportInfo.TRANSPORT_TCP_WIFI, TransportInfo.TRANSPORT_WAP2, TransportInfo.TRANSPORT_TCP_CELLULAR}

3. Configure the options for the TCP Cellular transport, if applicable.

TcpCellularOptions tcpOptions = new TcpCellularOptions();if(!TcpCellularOptions.isDefaultAPNSet()){ tcpOptions.setApn("My APN"); tcpOptions.setTunnelAuthUsername("user"); tcpOptions.setTunnelAuthPassword("password");}

4. Create a ConnectionFactory object.

ConnectionFactory factory = new ConnectionFactory();

5. Set any other ConnectionFactory options that are applicable to your application. In this case, TCP Cellular is one ofthe preferred transports, so set the TCP Cellular transport options.

factory.setTransportTypeOptions(TransportInfo.TRANSPORT_TCP_CELLULAR, tcpOptions);factory.setAttemptsLimit(5);

6. Create a thread to retrieve the connection. If the connection was successful, then ConnectionFactory returns aConnectionDescriptor object that you can use. In this step, pass the ConnectionDescriptor object to anothermethod (displayContent()) that is responsible for displaying the content.

Development Guide The Network API

23

Thread t = new Thread(new Runnable(){ public void run() { ConnectionDescriptor cd = _factory.getConnection ("http://www.blackberry.com"); if(cd != null) { Connection c = cd.getConnection(); displayContent(c); } }

});t.start();

7. Implement displayContent(). In this case, push a screen that uses a Connection parameter to retrieve and displaythe content, after the connection retrieval thread completes.

private void displayContent(final Connection conn) { UiApplication.getUiApplication().invokeLater(new Runnable() { public void run() { UiApplication.getUiApplication().pushScreen(new HTTPOutputScreen(conn)); } });}

After you finish: For more information about using a connection and implementing the HTTPOutputScreen class, see "Sendand receive data using a network connection".

For a complete code sample, see "Code sample: Retrieving a web page using the Network API".

Generic Connection FrameworkIf you develop applications for BlackBerry® device users who are running BlackBerry® Device Software 4.7 or earlier, you needto use the GCF to open a network connection. However, any code that you write that uses the GCF also runs on later versions ofBlackBerry® Device Software. The GCF is implemented in the javax.microedition.io.Connector class. You can callConnector.open() to create any type of supported connection. The open() method accepts a connection string thatspecifies the type of connection to make, the end point, and optional configuration details for the connection.

The connection string that is used by the GCF comprises three parts:

<scheme> : <hierarchical location information> ; <additional information>

Development Guide Generic Connection Framework

24

The <scheme> indicates the protocol to use to establish the connection. The <hierarchical location information> describes theend point for the connection. Finally, the <additional information> controls the transport that is used, and provides authenticationdetails for a proxy server if they are required. For more information about transport options, see "Network transport options".

For example, in the following code sample, the connection string specifies the HTTP protocol and uses a host name to indicatethe connection end point. The interface=wifi parameter is included to specify that the Wi-Fi® radio should be used toestablish the connection.

HTTPConnection c = (HTTPConnection)Connector.open("http://example.com;interface=wifi");

Open a network connection using the GCFThe following task shows you how to open an HTTP connection using the BlackBerry® Mobile Data System transport. You canuse a similar process to open a connection using other protocols and transports.CAUTION: The Connector.open() method is not thread-safe. Ensure that you invoke open() on a thread that is separatefrom the main event thread.

Before you begin: Make sure that the transport that you want to use is available and has coverage.


import net.rim.device.api.ui.UiApplication;import java.io.IOException;import javax.microedition.io.*;

2. Create a new thread to open the connection.

Thread t = new Thread(new Runnable(){ public void run() {

3. Create a local variable for your Connection object.

Connection conn = null;

4. Invoke open(). Specify the connection string.

try { conn = Connector.open("http://www.blackberry.com;deviceside=false"); } catch (IOException e) { // Process your error condition }

5. If the connection attempt was successful, open() returns a Connection object that you can use. Pass the connectionobject to another method (displayContent()) that is responsible for displaying the content.

Development Guide Generic Connection Framework

25

if (conn != null) { displayContent(conn); } }});

6. Start your thread.

t.start();

7. Implement displayContent(). In this case, push a screen that uses a Connection parameter to retrieve and displaythe content, after the connection retrieval thread completes.

private void displayContent(final Connection conn) { UiApplication.getUiApplication().invokeLater(new Runnable() { public void run() { UiApplication.getUiApplication().pushScreen(new HTTPOutputScreen(conn)); } });}

After you finish: For more information about using a connection, and implementing the HTTPOutputScreen class, see "Sendand receive data using a network connection".

For a complete code sample, see "Code sample: Retrieving a web page using the GCF".

Send and receive data using a network connectionThe following task shows you how to send and receive data using an HTTP connection to a web site. The data that is returnedfrom the web site is displayed on the screen. You can use a similar process to send and receive data using other network protocols.To make this task as general as possible, the following code sends an HTTP GET command manually to a server. Normally, youwould use an HttpConnection interface, which constructs the HTTP command string according to the options that youconfigure.CAUTION: Network input and output operations are not thread-safe. Make sure that you create a separate thread when youuse a Connection object.

Before you begin: Open a network connection and pass a Connection object to the constructor of the class that is developedin this task. For more information about opening network connections, see "Open a network connection using the Network API"or "Open a network connection using the GCF".


import net.rim.device.api.ui.container.MainScreen;import net.rim.device.api.ui.component.RichTextField;import net.rim.device.api.ui.UiApplication;import java.io.IOException;

Development Guide Send and receive data using a network connection

26

import java.io.InputStream;import java.io.OutputStream;import javax.microedition.io.*;

2. Create a class that extends the MainScreen class.

public class HTTPOutputScreen extends MainScreen {

3. Create an instance variable for a RichTextField object to display the results.

RichTextField _rtfOutput = new RichTextField();

4. Create a constructor that accepts a Connection object as an argument.

public HTTPOutputScreen(Connection conn){

5. Add the RichTextField to your screen, and start a thread to access the network connection.

_rtfOutput.setText("Retrieving data. Please wait...");add(_rtfOutput);ContentReaderThread t = new ContentReaderThread(conn);t.start();

6. Create a method to populate your RichTextField with the data that is returned from the web site, afterContentReaderThread completes. You invoke this method in step 20.

public void showContents(final String result) { UiApplication.getUiApplication().invokeLater(new Runnable() {

public void run() { _rtfOutput.setText(result); } });}

7. In an inner class, create a thread to communicate with the web server. Accept a ConnectionDescriptor object as anargument.

private final class ContentReaderThread extends Thread{ private Connection _connection;

ContentReaderThread(Connection conn) { _connection = conn; } public void run() {

8. Initialize an OutputStream object and an InputStream object to exchange data with the web site.


27

OutputStream os = null; InputStream is = null;

9. Initialize a String object to store the response from the web site.

String result = "";

10. Create an OutputConnection object to send data over your connection.

try { OutputConnection outputConn = (OutputConnection) connection;

11. Retrieve an OutputStream from your OutputConnection.

os = outputConn.openOutputStream(); String getCommand = "GET " + "/" + " HTTP/1.0\r\n\r\n"; os.write(getCommand.getBytes()); os.flush();

12. Send an HTTP GET command to the web server over your OutputStream. Convert the GET command into a byte array.

String getCommand = "GET " + "/" + " HTTP/1.0\r\n\r\n"; os.write(getCommand.getBytes()); os.flush();

13. Create an InputConnection object to receive data from your connection.

InputConnection inputConn = (InputConnection) connection;

14. Retrieve an InputStream from your InputConnection.

is = inputConn.openInputStream();

15. Retrieve the stream data and store it in a byte array.

byte[] data = net.rim.device.api.io.IOUtilities.streamToBytes(is); result = new String(data);

16. Catch any errors that might be generated by your procedure.

catch(Exception e) { result = "ERROR fetching content: " + e.toString(); }

17. Close your OutputStream.

if(os != null) { try { os.close(); } catch(IOException e) {


28

// process the error condition } }

18. Close your InputStream.

if(is != null) { try { is.close(); } catch(IOException e) { } }

19. Close your Connection.

{ connection.close(); } catch(IOException ioe) { } }

20. Call showContents() that you created in step 6.

showContents(result);}}

Network transport options

Transport Additional information

TCP Cellular When you create a connection using the TCP Cellular transport, you may need to specify

the following parameters:

• APN

• Tunnel authorization user name

• Tunnel authorization password

Development Guide Network transport options

29


If you are using the Network API, you can use the TCPCellularOptions class to

configure these options. For BlackBerry® devices that are running BlackBerry® 6 and later,

you can determine whether these options are already set by invoking

TCPCellularOptions.isDefaultAPNSet().

If you are using the GCF, you could use a connection string that is similar to the following:

"http://www.blackberry.com;deviceside=true;

apn=carriergateway;[email protected];

TunnelAuthPassword=CARRIER"

TCP Wi-Fi® If you are using the GCF, you can use the Wi-Fi® transport with a connection string that

is similar to the following:

"http://www.blackberry.com;interface=wifi"

WAP 2.0 If WAP 2.0 is configured on a device, you need to retreive a connection ID from the service

book. If you are using the GCF, you could use a connection string that is similar to the

following:

"http://www.blackberry.com;deviceside=true;ConnectionUID=H6Q1234"

For more information about retrieving a connection ID, see the knowledge base article at

http://supportforums.blackberry.com/t5/Java-Development/What-Is-Network-API-

alternative-for-legacy-OS/ta-p/614822

WAP 1.0 and 1.1 Like TCP Cellular, you may need to specify additional parameters to use the WAP 1.0 or 1.1

gateway:

• Gateway APN

• Gateway IP address

• Gateway port

• Source IP address

• Source port

• Tunnel authorization user name

• Tunnel authorization password

• Enable WTLS

If you are using the Network API, you can use the WapOptions class to configure these

options.


30


If you are using the GCF, you could use a connection string that is similar to the following:

"http://www.blackberry.com;deviceside=true;

WapGatewayIP=127.0.0.1;WapGatewayPort:9201; WapGatewayAPN=carriergateway"

BlackBerry® Mobile Data System If you are using the GCF, you can use the BlackBerry MDS transport with a connection

string that is similar to the following:

"http://www.blackberry.com;deviceside=false"

BlackBerry® Internet Service To use the BlackBerry Internet Service transport, you must sign up for the BlackBerry®

Push Service. For more information, visit http://na.blackberry.com/eng/developers/

javaappdev/pushapi.jsp


31



Working with radios 5

There may be cases where you need to turn on a radio on a BlackBerry® device to use a particular network transport. For example,you may want your BlackBerry device application to connect over Wi-Fi® to make efficient use of bandwidth. Or, you may wantto compare your application's performance when you use different wireless technologies.

You can use the net.rim.device.api.system.RadioInfo class to gather information about the wireless technologiesthat are available on a device. Using the rim.device.api.system.Radio class, you can manage the radios on the device.You should also implement the net.rim.device.api.system.RadioStatusListener interface to receivenotifications about changes in radio status.

The wireless technologies that are available on BlackBerry devices are grouped into three wireless access families.

Wireless access family Description

3GPP® This family includes GPRS, EDGE, UMTS® GERAN, UTRAN, and GAN.

CDMA This family includes CDMA2000® and EVDO.

WLAN This family includes IEEE® 802.11™, 802.11a, 802.11b, 802.11g.

Query a radio's availability and change its statusYou can use the RadioInfo and Radio classes to determine whether a particular radio technology is supported on aBlackBerry® device, and to turn on or turn off the radio. For more information, see the API reference for the BlackBerry® Java® SDK.


import net.rim.device.api.system.Radio;import net.rim.device.api.system.RadioInfo;

2. Retrieve a bit field of supported wireless access families.

int intSupportedWAFs = RadioInfo.getSupportedWAFs();

3. Check if the wireless access family that you want to use is available on the device. Perform a bitwise AND operation thatcombines the intSupportedWAFs bit field and the constant for the wireless access family that you want to use. If thefamily is available, the result will be nonzero.

if ((intSupportedWAFs & RadioInfo.WAF_WLAN) !=0 ){

4. Retrieve a bit field of available radios.

int intSupportedWAFs = RadioInfo.getSupportedWAFs();

int intActiveWAFs = RadioInfo.getActiveWAFs();

Development Guide Working with radios

32

5. Check if the radio that you want to use is turned off. If it is turned off, a bitwise AND operation applied tointActiveWAFs and the constant for the radio returns 0.

if ((intActiveWAFs & RadioInfo.WAF_WLAN) = 0) {

6. If the radio is turned off, then turn it on.

Radio.activateWAFs(RadioInfo.WAF_WLAN); }}

Development Guide Query a radio's availability and change its status

33

Code samples 6

Code sample: Requesting data using a BlockingSenderDestination objectimport net.rim.device.api.io.messaging.*;import net.rim.device.api.io.URI;import net.rim.device.api.ui.*;import net.rim.device.api.ui.component.*;import net.rim.device.api.ui.container.*;import java.io.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new BlockingSenderSample()); }}

class BlockingSenderSample extends MainScreen implements FieldChangeListener{

ButtonField _btnBlock = new ButtonField(Field.FIELD_HCENTER);

private static UiApplication _app = UiApplication.getUiApplication();

private String _result;

public BlockingSenderSample() { _btnBlock.setChangeListener(this); _btnBlock.setLabel("Fetch page");

add(_btnBlock); }

public void fieldChanged(Field button, int unused) {

if(button == _btnBlock) {

Thread t = new Thread(new Runnable()

Development Guide Code samples

34

{ public void run() { Message response = null; String uriStr = "http://www.blackberry.com"; BlockingSenderDestination bsd = null; try { bsd = (BlockingSenderDestination) DestinationFactory.getSenderDestination ("CommAPISample", URI.create(uriStr)); if(bsd == null) { bsd = DestinationFactory.createBlockingSenderDestination (new Context("CommAPISample"), URI.create(uriStr) ); }

// Send message and wait for response response = bsd.sendReceive();

if(response != null) { BSDResponse(response); } } catch(Exception e) { // process the error } finally { if(bsd != null) { bsd.release(); } } }

}); t.start(); } }

private void BSDResponse(Message msg) { if (msg instanceof ByteMessage) { ByteMessage reply = (ByteMessage) msg;

Development Guide Code sample: Requesting data using a BlockingSenderDestination object

35

_result = (String) reply.getStringPayload(); } else if(msg instanceof StreamMessage) { StreamMessage reply = (StreamMessage) msg; InputStream is = reply.getStreamPayload(); byte[] data = null; try { data = net.rim.device.api.io.IOUtilities.streamToBytes(is); } catch (IOException e) { // process the error } if(data != null) { _result = new String(data); } }

_app.invokeLater(new Runnable() {

public void run() { _app.pushScreen(new HTTPOutputScreen(_result)); }

});

}

}

class HTTPOutputScreen extends MainScreen {


public HTTPOutputScreen(String message) { _rtfOutput.setText("Retrieving data. Please wait..."); add(_rtfOutput); showContents(message); }

// After the data has been retrieved, display it public void showContents(final String result) { UiApplication.getUiApplication().invokeLater(new Runnable() {

public void run() { _rtfOutput.setText(result); }

Development Guide Code sample: Requesting data using a BlockingSenderDestination object

36

}); }}

Code sample: Requesting data using a NonBlockingSenderDestinationobjectimport net.rim.device.api.io.URI;import net.rim.device.api.io.messaging.*;import net.rim.device.api.ui.*import net.rim.device.api.ui.component.ButtonField;import net.rim.device.api.ui.container.MainScreen;import net.rim.device.api.system.Application;import java.io.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new NonBlockingSenderSample()); }}

class NonBlockingSenderSample extends MainScreen implements FieldChangeListener{

ButtonField _btnNonBlock = new ButtonField(Field.FIELD_HCENTER);


public NonBlockingSenderSample() { _btnNonBlock.setChangeListener(this); _btnNonBlock.setLabel("Fetch page");

add(_btnNonBlock); }


if(button == _btnNonBlock)

Development Guide Code sample: Requesting data using a NonBlockingSenderDestination object

37

{ NonBlockingSenderDestination destination = null; try { URI uri = URI.create("http://www.blackberry.com");

NBSDMsgListener responseListener = new NBSDMsgListener(); destination = (NonBlockingSenderDestination) DestinationFactory.getSenderDestination ("CommAPISample", uri); if (destination == null) { destination = DestinationFactory.createNonBlockingSenderDestination (new Context("CommAPISample"), uri, responseListener); }

// Send message to retrieve the response destination.send();

}

catch(Exception e) { // process the error }

} }

}

class NBSDMsgListener implements MessageListener {

public void onMessage(Destination dest, Message msg) {

String payload = null;

if (msg instanceof ByteMessage) { ByteMessage reply = (ByteMessage) msg; payload = (String) reply.getStringPayload(); } else if(msg instanceof StreamMessage) { StreamMessage reply = (StreamMessage) msg; InputStream is = reply.getStreamPayload(); byte[] data = null; try { data = net.rim.device.api.io.IOUtilities.streamToBytes(is);


38

} catch (IOException e) { } if(data != null) { payload = new String(data); } } if(payload!=null) { synchronized(Application.getEventLock()) { UiApplication.getUiApplication().pushScreen (new HTTPOutputScreen(payload)); }

} }

public void onMessageCancelled(Destination arg0, int arg1) { // process message cancelled notification }

public void onMessageFailed(Destination arg0, MessageFailureException arg1) { // process message failed notification }

}



public HTTPOutputScreen(String message) { _rtfOutput.setText("Retrieving data. Please wait..."); add(_rtfOutput); showContents(message); }


public void run() { _rtfOutput.setText(result); }


39

}); }}

Code sample: Parsing a JSON data structureThe following code sample demonstrates one way to parse a JSON data structure. You can use a similar process to parse JSONor other data formats that are provided by the Message Processing API.

import net.rim.device.api.io.URI;import net.rim.device.api.io.messaging.*;import net.rim.device.api.ui.*import net.rim.device.api.ui.component.*;import net.rim.device.api.ui.container.*;import java.io.*;import org.json.me.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new ParseJSONSample()); }}

class ParseJSONSample extends MainScreen implements FieldChangeListener{

ButtonField _btnJSON = new ButtonField(Field.FIELD_HCENTER);


public ParseJSONSample() { _btnJSON.setChangeListener(this); _btnJSON.setLabel("Fetch page");

add(_btnJSON); }


if(button == _btnJSON)

Development Guide Code sample: Parsing a JSON data structure

40

{

Thread t = new Thread(new Runnable() { public void run() { Message response = null; String uriStr = "http://docs.blackberry.com/sampledata.json"; BlockingSenderDestination bsd = null; try { bsd = (BlockingSenderDestination) DestinationFactory.getSenderDestination ("CommAPISample", URI.create(uriStr)); if(bsd == null) { bsd = DestinationFactory.createBlockingSenderDestination (new Context("CommAPISample"), URI.create(uriStr), new JSONMessageProcessor() ); }

// Send message and wait for response response = bsd.sendReceive(); _json = response.getObjectPayload();

if(_json != null) { _app.invokeLater(new Runnable() {

public void run() { _app.pushScreen(new JSONOutputScreen(_json)); }

}); } } catch(Exception e) { System.out.println(e.toString()); } finally { if(bsd != null) { bsd.release(); } } }


41

}); t.start();

}

}

class JSONOutputScreen extends MainScreen implements TreeFieldCallback {

private TreeField _treeField;

public JSONOutputScreen(Object JSONData) { _treeField = new TreeField(this, Field.FOCUSABLE); add(_treeField); setTree(JSONData); }

void setTree(Object obj) { int parentNode = 0;

_treeField.deleteAll();

try { if(obj instanceof JSONArray) { parentNode = populateTreeArray (_treeField, (JSONArray) obj, parentNode); } else if(obj instanceof JSONObject) { parentNode = populateTreeObject (_treeField, (JSONObject) obj, parentNode); } } catch(JSONException e) { System.out.println(e.toString()); }

_treeField.setCurrentNode(parentNode); }

// Populate the trees with JSON arrays int populateTreeArray(TreeField tree, JSONArray o, int p) throws JSONException {


42

Object temp; int newParent;

newParent = tree.addChildNode(p, "Array " + p);

for(int i = 0; i < o.length(); ++i) { temp = o.get(i);

if(temp == null || temp.toString().equalsIgnoreCase("null")) { continue; }

if(temp instanceof JSONArray) { // Array of arrays populateTreeArray(tree, (JSONArray) temp, newParent); } else if(temp instanceof JSONObject) { // Array of objects populateTreeObject(tree, (JSONObject) temp, newParent); } else { // other values newParent = tree.addSiblingNode(newParent, temp.toString()); } }

return newParent; }

// Populate the tree with JSON objects int populateTreeObject(TreeField tree, JSONObject o, int p) throws JSONException { Object temp;

int newParent = tree.addChildNode(p, "Object" + p);

JSONArray a = o.names();

for(int i = 0; i < a.length(); ++i) { temp = o.get(a.getString(i));

if(temp == null || temp.toString().equalsIgnoreCase("null")) { continue; } if(temp instanceof JSONArray)


43

{ populateTreeArray(tree, (JSONArray) temp, newParent); } else if(temp instanceof JSONObject) { populateTreeObject(tree, (JSONObject) temp, newParent); } else { tree.addSiblingNode (newParent, a.getString(i) + ": " + temp.toString()); } }

return newParent; }

public void drawTreeItem(TreeField treeField, Graphics graphics, int node, int y, int width, int indent) { if(treeField == _treeField) { Object cookie = _treeField.getCookie(node); if(cookie instanceof String) { String text = (String) cookie; graphics.drawText(text, indent, y, Graphics.ELLIPSIS, width); } }

}

public boolean onSavePrompt() { // Suppress the save dialog return true; }

}

Code sample: Retrieving a web page using the Network APITo make this code sample as generic as possible, the InputConnection and OutputConnection interfaces are used inplace of the HttpConnection interface.

import net.rim.device.api.io.transport.*;import net.rim.device.api.io.transport.options.*;import net.rim.device.api.ui.component.RichTextField;

Development Guide Code sample: Retrieving a web page using the Network API

44

import net.rim.device.api.ui.container.MainScreen;import net.rim.device.api.ui.UiApplication;import net.rim.device.api.util.Arrays;import java.io.*;import javax.microedition.io.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { new HTTPConnectionSetup(); }}

class HTTPConnectionSetup {

ConnectionFactory _factory = new ConnectionFactory();

public HTTPConnectionSetup() {

// Create preference ordered list of transports int[] _intTransports = { TransportInfo.TRANSPORT_TCP_WIFI, TransportInfo.TRANSPORT_WAP2, TransportInfo.TRANSPORT_TCP_CELLULAR };

// Remove any transports that are not (currently) available for(int i = 0; i < _intTransports.length ; i++) { int transport = _intTransports[i]; if(!TransportInfo.isTransportTypeAvailable(transport) || !TransportInfo.hasSufficientCoverage(transport)) { Arrays.removeAt(_intTransports, i); } }

// Set options for TCP Cellular transport TcpCellularOptions tcpOptions = new TcpCellularOptions(); if(!TcpCellularOptions.isDefaultAPNSet()) { tcpOptions.setApn("My APN"); tcpOptions.setTunnelAuthUsername("user");


45

tcpOptions.setTunnelAuthPassword("password"); }

// Set ConnectionFactory options if(_intTransports.length > 0) { _factory.setPreferredTransportTypes(_intTransports); } _factory.setTransportTypeOptions(TransportInfo.TRANSPORT_TCP_CELLULAR, tcpOptions); _factory.setAttemptsLimit(5);

// Open a connection on a new thread Thread t = new Thread(new Runnable() { public void run() { ConnectionDescriptor cd = _factory.getConnection ("http://www.blackberry.com"); // If connection was successful, fetch and show the content from // the web server if(cd != null) { Connection c = cd.getConnection(); displayContent(c); } }

}); t.start(); }

private void displayContent(final Connection conn) { // When the connection thread completes, show the data from the web server UiApplication.getUiApplication().invokeLater(new Runnable() { public void run() { UiApplication.getUiApplication().pushScreen(new HTTPOutputScreen(conn)); } }); }

}



46


public HTTPOutputScreen(Connection conn) { // Create a container for the data, and put it on the screen _rtfOutput.setText("Retrieving data. Please wait..."); add(_rtfOutput); // Retrieve the data from the web server, using the connection, on a // separate thread ContentReaderThread t = new ContentReaderThread(conn); t.start(); }


public void run() { _rtfOutput.setText(result); } }); }

private final class ContentReaderThread extends Thread { private Connection _connection;

ContentReaderThread(Connection conn) { _connection = conn; }

public void run() { String result = ""; OutputStream os = null; InputStream is = null;

try { // Send HTTP GET to the server OutputConnection outputConn = (OutputConnection) _connection; os = outputConn.openOutputStream(); String getCommand = "GET " + "/" + " HTTP/1.0\r\n\r\n"; os.write(getCommand.getBytes()); os.flush();

// Get InputConnection and read the server's response InputConnection inputConn = (InputConnection) _connection;


47

is = inputConn.openInputStream(); byte[] data = net.rim.device.api.io.IOUtilities.streamToBytes(is); result = new String(data); // is.close();

} catch(Exception e) { result = "ERROR fetching content: " + e.toString(); } finally { // Close OutputStream if(os != null) { try { os.close(); } catch(IOException e) { } }

// Close InputStream if(is != null) { try { is.close(); } catch(IOException e) { } }

// Close Connection try { _connection.close(); } catch(IOException ioe) { } }

// Show the response received from the web server, or an error message showContents(result); } }


48

}

Code sample: Retrieving a web page using the GCFThis code sample uses the BlackBerry® Mobile Data System transport. To make this code sample as generic as possible, theInputConnection and OutputConnection interfaces are used in place of the HttpConnection interface.

import net.rim.device.api.ui.component.RichTextField;import net.rim.device.api.ui.container.MainScreen;import net.rim.device.api.ui.UiApplication;import java.io.*;import javax.microedition.io.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { new HTTPConnectionSetup(); }}

class HTTPConnectionSetup {

public HTTPConnectionSetup() {

Thread t = new Thread(new Runnable() {

public void run() { Connection c = null; try { c = Connector.open("http://www.blackberry.com;deviceside=false"); } catch (IOException e) { e.printStackTrace(); } if(c != null) { displayContent(c); }

Development Guide Code sample: Retrieving a web page using the GCF

49

}

}); t.start(); }

private void displayContent(final Connection c) { // When the connection thread completes, show the data from the web server UiApplication.getUiApplication().invokeLater(new Runnable() { public void run() { UiApplication.getUiApplication().pushScreen(new HTTPOutputScreen(c)); } }); }

}



public HTTPOutputScreen(Connection conn) { // Create a container for the data, and put it on the screen _rtfOutput.setText("Retrieving data. Please wait..."); add(_rtfOutput); // Retrieve the data from the web server, using the connection, on a // separate thread ContentReaderThread t = new ContentReaderThread(conn); t.start(); }


public void run() { _rtfOutput.setText(result); } }); }

private final class ContentReaderThread extends Thread { private Connection _connection;

ContentReaderThread(Connection conn)


50

{ _connection = conn; }

public void run() { String result = ""; OutputStream os = null; InputStream is = null;

try { // Send HTTP GET to the server OutputConnection outputConn = (OutputConnection) _connection; os = outputConn.openOutputStream(); String getCommand = "GET " + "/" + " HTTP/1.0\r\n\r\n"; os.write(getCommand.getBytes()); os.flush();

// Get InputConnection and read the server's response InputConnection inputConn = (InputConnection) _connection; is = inputConn.openInputStream(); byte[] data = net.rim.device.api.io.IOUtilities.streamToBytes(is); result = new String(data); // is.close();

} catch(Exception e) { result = "ERROR fetching content: " + e.toString(); } finally { // Close OutputStream if(os != null) { try { os.close(); } catch(IOException e) { } }

// Close InputStream if(is != null) { try { is.close(); }


51

catch(IOException e) { } }

// Close Connection try { _connection.close(); } catch(IOException ioe) { } }

// Show the response received from the web server, or an error message showContents(result); } }

}

Code sample: Determining network transports with sufficient coverage usingthe Network APIimport net.rim.device.api.io.transport.*;import net.rim.device.api.ui.*;import net.rim.device.api.ui.component.*;import net.rim.device.api.ui.container.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new ListTransportsWithCoverageScreen()); }}

class ListTransportsWithCoverageScreen extends MainScreen{

private int[] _transportsWithCoverage;

Development Guide Code sample: Determining network transports with sufficient coverage using the Network API

52

private TransportDescriptor[] _transports; private RichTextField _rtfDisplay; private ButtonField _btnShowTransports;

public ListTransportsWithCoverageScreen() { VerticalFieldManager vfm = new VerticalFieldManager(); setTitle("Network Sample"); _rtfDisplay = new RichTextField ("Click button below to display available transports."); _btnShowTransports = new ButtonField ("Show Transports", Field.FIELD_HCENTER); _btnShowTransports.setChangeListener(new FieldChangeListener() { public void fieldChanged(Field field, int context) { getTransports(); } }); vfm.add(_rtfDisplay); vfm.add(_btnShowTransports); add(vfm);

}

public void getTransports() { StringBuffer sb = new StringBuffer(); sb.append("The transports currently available are: \n"); _transportsWithCoverage = TransportInfo.getCoverageStatus(); _transports = TransportInfo.getTransportDescriptors (_transportsWithCoverage); for(int i = _transports.length - 1; i >=0; --i) { switch(_transports[i].getTransportType()) { case TransportInfo.TRANSPORT_BIS_B: sb.append("BlackBerry Internet Service\n"); break; case TransportInfo.TRANSPORT_MDS: sb.append("BlackBerry Mobile Data Service\n"); break; case TransportInfo.TRANSPORT_TCP_CELLULAR: sb.append("TCP Cellular\n"); break; case TransportInfo.TRANSPORT_TCP_WIFI: sb.append("TCP WiFi\n"); break; case TransportInfo.TRANSPORT_WAP: sb.append("WAP 1.0 or 1.1\n"); break; case TransportInfo.TRANSPORT_WAP2:

Development Guide Code sample: Determining network transports with sufficient coverage using the Network API

53

sb.append("WAP 2.0\n"); break; } } _rtfDisplay.setText(sb.toString()); }}

Code sample: Controlling radiosimport net.rim.device.api.system.*;import net.rim.device.api.ui.*;import net.rim.device.api.ui.component.*;import net.rim.device.api.ui.container.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) { NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new RadioControlScreen()); }}

class RadioControlScreen extends MainScreen implements FieldChangeListener {

boolean[] _intRadioOn = new boolean[3]; ButtonField _btn3G, _btnCDMA, _btniDEN, _btnWiFi;

public RadioControlScreen() { VerticalFieldManager vfm = new VerticalFieldManager(Field.FIELD_HCENTER);

int wafs = RadioInfo.getSupportedWAFs(); if ((wafs & RadioInfo.WAF_3GPP) != 0 ) { _btn3G = new ButtonField("3G Radio"); _btn3G.setChangeListener(this); vfm.add(_btn3G); } if ((wafs & RadioInfo.WAF_CDMA) != 0 ) { _btnCDMA = new ButtonField("CDMA Radio");

Development Guide Code sample: Controlling radios

54

_btnCDMA.setChangeListener(this); vfm.add(_btnCDMA); } if ((wafs & RadioInfo.WAF_WLAN) != 0 ) { _btnWiFi = new ButtonField("WiFi Radio"); _btnWiFi.setChangeListener(this); vfm.add(_btnWiFi); }

wafs = RadioInfo.getActiveWAFs(); if ((wafs & RadioInfo.WAF_3GPP) != 0 ) { _intRadioOn[0] = true; _btn3G.setLabel("3G Radio is on"); } if ((wafs & RadioInfo.WAF_CDMA) != 0 ) { _intRadioOn[1] = true; _btnCDMA.setLabel("CDMA Radio is on"); } if ((wafs & RadioInfo.WAF_WLAN) != 0 ) { _intRadioOn[2] = true; _btnWiFi.setLabel("WiFi Radio is on"); }

add(vfm); StandardTitleBar tb = new StandardTitleBar(); tb.addTitle("Radio Control Demo"); tb.addSignalIndicator(); setTitleBar(tb);

}

public void fieldChanged(Field field, int context) { if (field instanceof ButtonField) { if(field == _btn3G) { if (_intRadioOn[0]) { Radio.deactivateWAFs(RadioInfo.WAF_3GPP); _btn3G.setLabel("3G Radio is off"); _intRadioOn[0] = false; } else { Radio.activateWAFs(RadioInfo.WAF_3GPP); _btn3G.setLabel("3G Radio is on"); _intRadioOn[0] = true;

Development Guide Code sample: Controlling radios

55

} } else if(field == _btnCDMA) { if (_intRadioOn[1]) { Radio.deactivateWAFs(RadioInfo.WAF_CDMA); _btnCDMA.setLabel("CDMA Radio is off"); _intRadioOn[1] = false; } else { Radio.activateWAFs(RadioInfo.WAF_CDMA); _btnCDMA.setLabel("CDMA Radio is on"); _intRadioOn[1] = true; } } else if(field == _btnWiFi) { if (_intRadioOn[2]) { Radio.deactivateWAFs(RadioInfo.WAF_WLAN); _btnWiFi.setLabel("WiFi Radio is off"); _intRadioOn[2] = false; } else { Radio.activateWAFs(RadioInfo.WAF_WLAN); _btnWiFi.setLabel("WiFi Radio is on"); _intRadioOn[2] = true; } } }

}

}

Code sample: Determining the status of a network transport using theNetwork APIimport net.rim.device.api.io.transport.TransportInfo;import net.rim.device.api.ui.*;import net.rim.device.api.ui.component.*;import net.rim.device.api.ui.container.*;

public class NetworkSample extends UiApplication { public static void main(String[] args) {

Development Guide Code sample: Determining the status of a network transport using the Network API

56

NetworkSample app = new NetworkSample(); app.enterEventDispatcher(); } public NetworkSample() { pushScreen(new ProbeSpecificTransportScreen()); }}

class ProbeSpecificTransportScreen extends MainScreen implements FieldChangeListener {

private TextField _tfTransportStatus; private ObjectChoiceField _ocfTransports;

public ProbeSpecificTransportScreen() { String[] strTransportNames = {"none", "TCP Cellular", "WAP 1.0/1.1", "WAP 2.0", "MDS", "BIS", "TCP WiFi" };

VerticalFieldManager vfm = new VerticalFieldManager();

_tfTransportStatus = new TextField(Field.FIELD_HCENTER); _tfTransportStatus.setText ("Select a transport from the list above, then click 'Probe Transport'");

_ocfTransports = new ObjectChoiceField ("Select Transport to Probe: ", strTransportNames, 0, Field.FIELD_HCENTER); _ocfTransports.setEditable(true);

ButtonField btnProbe = new ButtonField("Probe Transport", Field.FIELD_HCENTER); btnProbe.setChangeListener(this);

vfm.add(_ocfTransports); vfm.add(btnProbe); vfm.add(_tfTransportStatus); add(vfm); }

public void fieldChanged(Field field, int context) { int intTransportType = _ocfTransports.getSelectedIndex(); if(intTransportType > 0) { if(TransportInfo.isTransportTypeAvailable(intTransportType)) { if(TransportInfo.hasSufficientCoverage(intTransportType)) { _tfTransportStatus.setText ((String)_ocfTransports.getChoice(intTransportType)


57

+ " is available."); } else { _tfTransportStatus.setText ((String)_ocfTransports.getChoice(intTransportType) + " is available but has insufficient coverage."); } } else { _tfTransportStatus.setText("Sorry, " + (String)_ocfTransports.getChoice(intTransportType) + " is not available.");

} } else { _tfTransportStatus.setText ("Please select a transport first, then click 'Probe Transport'");

} }

}


58

Glossary 7

3GPPThird Generation Partnership Project

AESAdvanced Encryption Standard

APIapplication programming interface

APNaccess point name

BlackBerry MDSBlackBerry® Mobile Data System

CDMACode Division Multiple Access

EDGEEnhanced Data Rates for Global Evolution

EVDOEvolution Data Optimized

GANgeneric access network

GERANGSM-EDGE Radio Access Network

GCFGeneric Connection Framework

GPRSGeneral Packet Radio Service

GSMGlobal System for Mobile Communications®

HTTPHypertext Transfer Protocol

Development Guide Glossary

59

HTTPSHypertext Transfer Protocol over Secure Sockets Layer

IPInternet Protocol

JSONJavaScript Object Notation

RDFResource Description Framework

RSSReally Simply Syndication

SOAPSimple Object Access Protocol

SSLSecure Sockets Layer

TCPTransmission Control Protocol

TLSTransport Layer Security

Triple DESTriple Data Encryption Standard

UDPUser Datagram Protocol

URIUniform Resource Identifier

URLUniform Resource Locator

UMTSUniversal Mobile Telecommunications System

UTRANUMTS Terrestrial Radio Access Network


60

VPNVirtual Private Network

WAPWireless Application Protocol

WLANwireless local area network

WTLSWireless Layer Transport Security

XMLExtensible Markup Language


61

Provide feedback 8

To provide feedback on this deliverable, visit www.blackberry.com/docsfeedback.

Development Guide Provide feedback

62

http://www.blackberry.com/docsfeedback

Document revision history 9

Date Description

8 November 2010 Changed the following topics:

• Architecture: Network Transports

• Communicating with HTTP servers

• Network tranport options

27 September 2010 First draft released.

Development Guide Document revision history

63

Legal notice 10

©2010 Research In Motion Limited. All rights reserved. BlackBerry®, RIM®, Research In Motion®, and related trademarks, names,and logos are the property of Research In Motion Limited and are registered and/or used in the U.S. and countries around theworld.

3GPP, UMTS are trademarks of the European Telecommunications Standards Institute. Java, JavaScript are trademarks of OracleAmerica, Inc. CDMA2000 is a trademark of the Telecommunications Industry Association. Wi-Fi is a trademark of the Wi-FiAlliance. All other trademarks are the property of their respective owners.

This documentation including all documentation incorporated by reference herein such as documentation provided or madeavailable at www.blackberry.com/go/docs is provided or made accessible "AS IS" and "AS AVAILABLE" and without condition,endorsement, guarantee, representation, or warranty of any kind by Research In Motion Limited and its affiliated companies("RIM") and RIM assumes no responsibility for any typographical, technical, or other inaccuracies, errors, or omissions in thisdocumentation. In order to protect RIM proprietary and confidential information and/or trade secrets, this documentation maydescribe some aspects of RIM technology in generalized terms. RIM reserves the right to periodically change information thatis contained in this documentation; however, RIM makes no commitment to provide any such changes, updates, enhancements,or other additions to this documentation to you in a timely manner or at all.

This documentation might contain references to third-party sources of information, hardware or software, products or servicesincluding components and content such as content protected by copyright and/or third-party web sites (collectively the "ThirdParty Products and Services"). RIM does not control, and is not responsible for, any Third Party Products and Services including,without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency,links, or any other aspect of Third Party Products and Services. The inclusion of a reference to Third Party Products and Servicesin this documentation does not imply endorsement by RIM of the Third Party Products and Services or the third party in any way.

EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALL CONDITIONS,ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDINGWITHOUT LIMITATION, ANY CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OFDURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY, MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR ARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALINGOR USAGE OF TRADE, OR RELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCEOF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN, AREHEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR PROVINCE. SOME JURISDICTIONSMAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENTPERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TO THE EXTENTTHEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY LIMITED TO NINETY (90) DAYS FROMTHE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL RIM BE LIABLEFOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCEDHEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY,INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR AGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES,FAILURE TO REALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF

Development Guide Legal notice

64

http://www.blackberry.com/go/docs

BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMSASSOCIATED WITH ANY APPLICATIONS USED IN CONJUNCTION WITH RIM PRODUCTS OR SERVICES, DOWNTIME COSTS,LOSS OF THE USE OF RIM PRODUCTS OR SERVICES OR ANY PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST OFSUBSTITUTE GOODS, COSTS OF COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARYLOSSES, WHETHER OR NOT SUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF RIM HAS BEEN ADVISEDOF THE POSSIBILITY OF SUCH DAMAGES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, RIM SHALL HAVE NO OTHEROBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO YOU INCLUDING ANY LIABILITYFOR NEGLIGENCE OR STRICT LIABILITY.

THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE OF THECAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF CONTRACT, NEGLIGENCE,TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL BREACH OR BREACHESOR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT OR OF ANY REMEDY CONTAINED HEREIN; AND (B)TO RIM AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS, ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIMESERVICE PROVIDERS), AUTHORIZED RIM DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIRRESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.

IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR, EMPLOYEE,AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF RIM OR ANY AFFILIATES OF RIM HAVE ANY LIABILITYARISING FROM OR RELATED TO THE DOCUMENTATION.

Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility to ensure that yourairtime service provider has agreed to support all of their features. Some airtime service providers might not offer Internet browsingfunctionality with a subscription to the BlackBerry® Internet Service. Check with your service provider for availability, roamingarrangements, service plans and features. Installation or use of Third Party Products and Services with RIM's products and servicesmay require one or more patent, trademark, copyright, or other licenses in order to avoid infringement or violation of third partyrights. You are solely responsible for determining whether to use Third Party Products and Services and if any third party licensesare required to do so. If required you are responsible for acquiring them. You should not install or use Third Party Products andServices until all necessary licenses have been acquired. Any Third Party Products and Services that are provided with RIM'sproducts and services are provided as a convenience to you and are provided "AS IS" with no express or implied conditions,endorsements, guarantees, representations, or warranties of any kind by RIM and RIM assumes no liability whatsoever, in relationthereto. Your use of Third Party Products and Services shall be governed by and subject to you agreeing to the terms of separatelicenses and other agreements applicable thereto with third parties, except to the extent expressly covered by a license or otheragreement with RIM.

Certain features outlined in this documentation require a minimum version of BlackBerry® Enterprise Server, BlackBerry® DesktopSoftware, and/or BlackBerry® Device Software.

The terms of use of any RIM product or service are set out in a separate license or other agreement with RIM applicable thereto.NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS WRITTEN AGREEMENTS OR WARRANTIESPROVIDED BY RIM FOR PORTIONS OF ANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.

Research In Motion Limited295 Phillip StreetWaterloo, ON N2L 3W8


65

Canada

Research In Motion UK Limited Centrum House 36 Station Road Egham, Surrey TW20 9LF United Kingdom

Published in Canada


66

Documents

BlackBerry_Java_SDK-Development_Guide--Network Comm