WebSphere Message Brokers
File: ac34710_
Writer: Jane Brockbank

Reference topic

This build: July 31, 2007 21:20:30

Designing MQe connections

Design the connections used by your MQe message flows when you migrate from Version 5.0 to Version 6.1.

This topic describes one in a sequence of migration tasks; complete these tasks in the order shown:

  1. Migrating a message flow that contains WebSphere MQ Everyplace nodes
  2. Designing MQe connections (this topic)
  3. Deploying an MQe message flow
  4. Configuring after MQe message flow deployment

This topic describes the connection options between WebSphere MQ Everyplace device clients and WebSphere Message Broker.

The following two diagrams represent how the connections are made; the table following the diagrams provides the details.

  1. The connection options for Version 5.0:
    • Direct:

      The diagram is described in the text.

    • Through an MQe Gateway:

      The diagram is described in the text.

  2. The connection option for Version 6.1:
    • Through an MQe Gateway:

      The diagram is described in the text.

The following table lists connection options between WebSphere MQ Everyplace device clients and WebSphere Message Broker.

Connection considerations Version 5.0 Version 6.1
MQe devices connect directly to the broker Yes No
MQe devices connect to an MQe Gateway that connects to the broker Yes Yes
The format of messages into and out of the broker is: MQe format or MQ format MQ format only

The next task in this migration sequence is Deploying an MQe message flow.

For help with configuring WebSphere MQ Everyplace, see the documentation supplied with that product.

Related reference
Migrating a message flow that contains WebSphere MQ Everyplace nodes
Deploying an MQe message flow
Configuring after MQe message flow deployment
MQeInput node
MQeOutput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:20:30

ac34710_ This topic's URL is: