This chapter describes how to develop and deploy applications to devices
from WebSphere Studio Device Developer (WSDD). To fully understand the
concepts outlined here we recommend that you have Java programming skills,
knowledge of J2ME and MIDlets, and basic knowledge of WebSphere MQ
Everyplace.
The example application aims to aid your understanding of the WebSphere MQ
Everyplace interface. The code can be split into 3 parts:
-
-
- The message service
- This runs WebSphere MQ Everyplace, controls a queue manager and performs
functions such as queue creation and message sending. This is the core
of the examples and allows them to be written with minimal calls to the
WebSphere MQ Everyplace API. This also means that to see the code
required to create a local queue for example, a user can simply look at the
relevant function within MQeMessageService.
- Example 1: The message pump
- This is a very simple application consisting of a single server and
client. The client is set to send a message to the server every 3
seconds which, when received by the server, will be displayed to the
user. Queues are asynchronous. Implementations of the client are
available for both MIDP and J2SE, while the server is only available for
J2SE.
- Example 2: The text application
- This is slightly more complex than the first example, consisting of 2
servers and a client. When initiating, the client is required to
register with the registration server. The registration server adds the
client to a store-and-forward queue on the gateway server and replies with a
success or failure message. The client can then send user-defined
messages to the gateway server (which it will display). The aim of this
application is to show how a seperate server can be used to create resources
necessary for a new client on the system to aid scalability of large WebSphere
MQ Everyplace networks.
This chapter presents information under the following headings:
© IBM Corporation 2002. All Rights Reserved