Example use of command-line tools

You can use the command-line tools to create an initial queue manager configuration using a script, without needing to know how to program in Java™.

The following example demonstrates how to use these tools to configure the network topology shown in the following figure:

Figure 1. MQe administration scenario
Graphic showing three branch offices (Branch000, Branch001, and branch002) connected to a central office MQe server (GATEWAY00) that is itself connected, through a LAN to an MQ server (CENTRAL00)
In this scenario:
  • The branch offices need to send sales information to the central site for processing by applications on the MQ server
  • Each branch has a single machine with DNS names BRANCH000, BRANCH001, and BRANCH002 respectively. These machines all run MQe, and each has a single queue manager called BRANCH000QM, BRANCH001QM, and BRANCH002QM respectively.
  • The central office machine GATEWAY00 runs a single gateway queue manager GATEWAY00QM
  • The central office machine CENTRAL00 runs MQ with a single queue manager called CENTRAL00QM
  • When a sale occurs, a message is sent to the MQ queue manager called CENTRAL00QM, into a queue called BRANCH.SALES.QUEUE.
  • The messages are encoded in a byte array at the branch, and sent inside an MQeMQMsgObject.
  • The MQ system must be able to send messages back to each branch queue manager.
  • The topology must also be able to cope with the addition of a Firewall later between the branches and the gateway.
  • The MQ-bound queue traffic should use the 56-bit DES cryptor.

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.