Home
How to use the communication examples
The following chapters contain example configurations:
- Example configuration - IBM WebSphere MQ for Windows
- Example configuration - IBM WebSphere MQ for AIX
- Example configuration - IBM WebSphere MQ for HP-UX
- Example configuration - IBM WebSphere MQ for Solaris
- Example configuration - IBM WebSphere MQ for z/OS
- Example configuration - IBM WebSphere MQ for iSeries
- Example configuration - IBM WebSphere MQ for z/OS using queue-sharing groups
The information in the example-configuration chapters describes the tasks that were carried out on a single platform, to set up communication to another of the platforms, and then describes the WebSphere MQ tasks to establish a working channel to that platform. Wherever possible, the intention is to make the information as generic as possible. Thus, to connect any two WebSphere MQ queue managers on different platforms, you should need to refer to only the relevant two chapters. Any deviations or special cases are highlighted as such. Of course, we can also connect two queue managers running on the same platform (on different machines or on the same machine). In this case, all the information can be derived from the one chapter.
The examples only cover how to set up communications where clustering is not being used. For information about setting up communications while using clustering, see the WebSphere MQ Queue Manager Clusters book. The communications’ configuration values given here still apply.
Each chapter contains a worksheet in which we can find the parameters used in the example configurations. There is a short description of each parameter and some guidance on where to find the equivalent values in your system. When you have a set of values of your own, record these in the spaces on the worksheet. As you proceed through the chapter, you will find cross-references to these values as we need them.
- Example queue manager names usually reflect the platform that the queue manager runs on, but MVS™ is used for both z/OS and MVS/ESA™, which are essentially the same.
- The sequence number wrap value for sender definitions defaults to 999999999 for V2 WebSphere MQ products.
Parent topic:
Example configuration chapters in this book
ic12130_
Home