WebSphere MQ Everyplace code can run on a large range of platforms including pervasive and mobile devices. Unlike base WebSphere MQ, WebSphere MQ Everyplace has a single queue manager type. However, WebSphere MQ Everyplace queue managers can be programmed to act as traditional clients or servers.
The fundamental elements of the WebSphere MQ Everyplace programming model are messages, queues and queue managers. WebSphere MQ Everyplace messages are objects that contain application-defined content. When stored, they are held in a queue and such messages may be moved across an WebSphere MQ Everyplace network. Queues can either be local or remote and are managed by queue managers.
WebSphere MQ Everyplace queue managers communicate through WebSphere MQ Everyplace connections. These connections are created on demand and are referred to as dynamic, differentiating them from WebSphere MQ connections which have to be explicitly created. They can also be configured in two different ways, in peer-to-peer mode, and in client/server mode (see WebSphere MQ Everyplace connections).
The WebSphere MQ-bridge component also supports WebSphere MQ client channels to enable WebSphere MQ Everyplace networks to communicate with WebSphere MQ networks.
Figure 1 shows an example of an WebSphere MQ Everyplace network linked to a WebSphere MQ server and the following sections of this chapter give brief descriptions of WebSphere MQ Everyplace objects and their uses.
Figure 1. WebSphere MQ Everyplace client