WebSphere MQ Mobile Transport

WebSphere MQ Mobile Transport is a service that connects mobile and wireless applications that use WebSphere MQ Everyplace.

WebSphere MQ Everyplace is an application designed primarily for messaging to, from, and between pervasive devices. These are typically small, handheld devices, such as mobile phones and PDAs. A bridge queue on the broker's queue manager provides an interface for the WebSphere MQ Everyplace clients to the broker services.

The operation of WebSphere MQ Everyplace is different from that of WebSphere Business Integration Message Broker, which means that there are different concepts and procedures involved in using a broker to operate with WebSphere MQ Everyplace, as explained in this and related topics.

Communication between WebSphere MQ Everyplace and a broker is achieved through the use of MQeInput, MQeOutput and Publication nodes in deployed message flows.

Using these nodes, you can write:

The MQeInput node allows WebSphere MQ Everyplace clients to connect and propagate messages into the broker using a WebSphere MQ Everyplace queue, and retrieve messages from the WebSphere MQ Everyplace queues. There must always be at least one MQeInput node in a message flow which uses WebSphere MQ Everyplace.

The MQeOutput node writes the current message to the WebSphere MQ Everyplace queue specified by the node properties (or defined by a destination list associated with the message), or to the reply queue specified in the message header.

The Publication node delivers a message to a set of WebSphere MQ, WebSphere MQ Everyplace, SCADA or Real Time subscribers that are defined in the subscription table and have a subscription for the node's subscription point. This node also stores retained publications when appropriate.

WebSphere MQ Everyplace Version 1.2.6 is used by WebSphere Business Integration Message Broker. This is compatible with later versions of WebSphere MQ Everyplace. Clients using later versions of WebSphere MQ Everyplace, for example Version 2.0, work correctly when connected to these nodes, although additional functionality not supported in Version 1.2.6 (for example JMS support) will not work.

Queue managers are not interchangeable between different versions of WebSphere MQ Everyplace. Therefore nodes must use a queue manager created using Version 1.2.6. Similarly, the client must use its level of the code when creating a queue manager.

WebSphere MQ Everyplace is not supported on z/OS. You cannot deploy a message flow that contains MQeInput or MQeOutput nodes to a broker that runs on z/OS. If you attempt to do so, the deploy fails and error messages are displayed in the log.

A number of WebSphere MQ Everyplace sample files are provided to help you start using WebSphere MQ Everyplace with WebSphere Business Integration Message Broker.

Related concepts
Interaction between WebSphere MQ Everyplace and a broker
WebSphere MQ Everyplace devices
WebSphere MQ Everyplace gateways
WebSphere MQ Everyplace client/server channels
WebSphere MQ Everyplace adapters
WebSphere MQ Everyplace queue managers
WebSphere MQ Everyplace queues
WebSphere MQ Everyplace messages

Related tasks
Enabling WebSphere MQ Everyplace applications

Related reference
MQeInput node
MQeOutput node
Publication node
WebSphere MQ Mobile Transport
WebSphere MQ Everyplace point-to-point methods
WebSphere MQ Everyplace publish/subscribe methods