MQ15 - WebSphere MQ System Administration I

WebSphere MQ System Administration I for Distributed Platforms (Course Code MQ15)

Instructor GuideERC 7.0

IBM Certified Course Material

V1.2.2.2

cover

Instructor Guide

The information contained in this document has not been submitted to any formal IBM test and is distributed on an as is basis withoutany warranty either express or implied. The use of this information or the implementation of any of these techniques is a customerresponsibility and depends on the customers ability to evaluate and integrate them into the customers operational environment. Whileeach item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results willresult elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.

Copyright International Business Machines Corporation 1996, 2003. All rights reserved.This document may not be reproduced in whole or in part without the prior written permission of IBM.Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictionsset forth in GSA ADP Schedule Contract with IBM Corp.

TrademarksIBM is a registered trademark of International Business Machines Corporation.The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Intel is a trademark of Intel Corporation in the United States, other countries, or both.Linux is a registered trademark of Linus Torvalds in the United States and other countries.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Other company, product and service names may be trademarks or service marks of others.

AIX AS/400 BookManagerCICS DYNIX/ptx EveryplaceFFST First Failure Support

TechnologyIBM

IMS iSeries LotusLotus Notes MQSeries MVS/ESANetView Notes OS/2OS/390 OS/400 QMFRACF SP2 SupportPacThinkPad TXSeries VSE/ESAWebSphere WIN-OS/2 z/OSzSeries

February 2003 Edition

Instructor GuideV1.2.2.2

TOC Copyright IBM Corp. 1996, 2003 Contents iii

ContentsTrademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Instructor Course Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Unit 1. A Review of WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.1 Facilities and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5WebSphere MQ - Commercial Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Message and Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Applications Enabled by WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15MQI Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Message Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21Asynchronous Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25Parallel Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27Client/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Assured Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Connectionless Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Queue Manager Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36Distributed Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38Message Driven Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41Separate Processes as Units of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43Multiple, Asynchronous Units of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45Message Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47

1.2 WebSphere MQ Products and Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49WebSphere MQ Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50WebSphere MQ Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54WebSphere MQ Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56WebSphere MQ Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64

Unit 2. Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.1 Planning an WebSphere MQ Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Naming WebSphere MQ Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Special Local Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

Message Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-17iv WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20WebSphere MQ Windows Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . .2-24

2.2 Configuring a Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30Create Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-33Start Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36WebSphere MQ MQSC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39Run WebSphere MQ Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42Creating a Local Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45Displaying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-48Other Queue Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-51More WebSphere MQ Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-54Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-56End Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-59Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-64

Unit 3. The MQI and Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.1 The MQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8Object Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10Connecting and Disconnecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12Opening and Closing an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15Dynamic Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18Put Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23Get Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25Reply-to Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28More Fields in the Message Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30Message and Correlation Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32Retrieving Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35Order of Retrieving Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37Message Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40Message Segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43Distribution List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-46

3.2 Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49Components of Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50Queue Attributes Controlling Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52Process Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55Conditions for a Trigger Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-57Other Conditions for a Trigger Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-59Fields in the Trigger Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-61Trigger Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-64Trigger Monitor Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-67

3.3 WebSphere MQ Publish/Subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


TOC WebSphere MQ Publish/Subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70 Copyright IBM Corp. 1996, 2003 Contents v

Installing WebSphere MQ Publish/Subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73Setting Up the Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75Controlling the Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78Message Broker Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84

Unit 4. Robust Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Functional View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Physical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18WebSphere MQ Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21MQS.INI Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Queue Manager Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26QM.INI Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29Installable Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Installable Services and Supplied Components . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Stopping a Queue Manager Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Removing a Queue Manager Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

4.2 Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43Configuration Files and Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46First Failure Support Technology (FFST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

4.3 Transactions and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55Message Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56Types of Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58Recovering Persistent Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60Damaged Objects and Media Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62Dumping the Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64Syncpoint Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66Compensating Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68Coordinating Local Units of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70Internal Coordination of Global Units of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72Database Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74External Coordination of Global Units of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77CICS Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80Independent Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86

Unit 5. Distributed Queue Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

5.1 Configuration for Distributed Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

Identifying a Queue in the MQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8vi WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Assured Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10Queue Definitions for Distributed Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12Message Channel Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14Attributes of a Message Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19Choosing a Transmission Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21Queue Manager Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23Separating Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25Configuring TCP/IP for WebSphere MQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27Starting a Message Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31Channel Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34Channel States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-38

5.2 The MQI in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41Data Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42Three Fields in the Message Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-44Requesting Application Data Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-46What Application Data Conversion Can Be Done? . . . . . . . . . . . . . . . . . . . . . . . .5-48Writing a Data Conversion Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-50How a Data Conversion Exit Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-52What Applications Should Do . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-54Command Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-56Support for PCF Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-59Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-61Indirect Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-64Instrumentation Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-66Responding to an Instrumentation Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-69Dead Letter Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-71Dead Letter Queue Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-74Using Dead Letter Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-76

5.3 WebSphere MQ Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79What Is a Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-80Cluster Support Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-82More About Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-85Setting Up a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-88DHCP Support in Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-90Multiple Queue Occurrence - Workload Balancing . . . . . . . . . . . . . . . . . . . . . . . . .5-93Workload Balancing - Rerouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-95Cluster-Related Queue Manager Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-98Controlling Clusters - Cluster Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-100Controlling Clusters - DISPLAY CLUSQMGR . . . . . . . . . . . . . . . . . . . . . . . . . . .5-103Cluster-Related Queue Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-105Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110

Unit 6. More on Distributed Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.1 WebSphere MQ Family SupportPacs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


TOC Overview of SupportPacs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Copyright IBM Corp. 1996, 2003 Contents vii

Example: MD01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Example: MO01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Example: MS03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

6.2 WebSphere MQ Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17WebSphere MQ Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18WebSphere MQ Clients Explained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20Syncpoint Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24Defining a MQI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28Two Ways of Configuring an MQI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30Channel Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Auto-Definition of Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37

6.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39WebSphere MQ Security Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40WebSphere MQ Access Control Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42Object Authority Manager: Installable Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45Object Authority Manager: Installable Service... . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48Object Authority Manager: Access Control Lists... . . . . . . . . . . . . . . . . . . . . . . . . 6-50Object Authority Manager: The MQSeries 5.2 update . . . . . . . . . . . . . . . . . . . . . 6-52Object Authority Manager V5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54Security Management: setmqaut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56Security Management: dspmqaut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59Security Management: dmpmqaut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61Access Control for WebSphere MQ Control Programs . . . . . . . . . . . . . . . . . . . . . 6-63Authority Checking in the MQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65Security and Distributed Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67Message Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69The Context Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71No Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75Passing Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77Alternate User Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79Setting Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-81Channel Exit Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83Channel Exit Programs on MQI Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-88Secure Sockets Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-90SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100SSL Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102QMGR Attributes for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-104QMGR Authentication Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106Channel Attributes for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-108Access Control for an WebSphere MQ Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-110Remote Queueing and Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-112Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

Supplied Channel Exit Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-114viii WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-118

Unit 7. WebSphere MQ for Windows (optional) . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Unit Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.1 WebSphere MQ for Windows (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8Family Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10Channel Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16Dial-up Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22Administration on Version 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25Administration on Version 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-29Supported WebSphere MQ Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-33Initialization (INI) File on Version 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-36MQSeries Definition (MQD) File on Version 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . .7-39Example of an MQD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-42Unit Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-46

Appendix A. Checkpoint Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B. Selected WebSphere MQ Constants . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C. Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D. Glossary of terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . D-1Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


TMK Copyright IBM Corp. 1996, 2003 Trademarks xi

TrademarksThe reader should recognize that the following terms, which appear in the content of this training document, are official trademarks of IBM or other companies: IBM is a registered trademark of International Business Machines Corporation.The following are trademarks of International Business Machines Corporation in the United States, or other countries, or both:

Intel is a trademark of Intel Corporation in the United States, other countries, or both.Linux is a registered trademark of Linus Torvalds in the United States and other countries.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Other company, product and service names may be trademarks or service marks of others.

AIX AS/400 BookManagerCICS DYNIX/ptx EveryplaceFFST First Failure Support

TechnologyIBM

IMS iSeries LotusLotus Notes MQSeries MVS/ESANetView Notes OS/2OS/390 OS/400 QMFRACF SP2 SupportPacThinkPad TXSeries VSE/ESAWebSphere WIN-OS/2 z/OSzSeriesCourse materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guidexii WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Course materials may not be reproduced in whole or in part

without the prior written permission of IBM.


pref Copyright IBM Corp. 1996, 2003 Instructor Course Overview xiii

Instructor Course OverviewThis course is designed to teach the basic skills required by an administrator for any of the WebSphere MQ Level 2 queue managers except WebSphere MQ for z/OS. The course does not therefore apply to the following queue managers. WebSphere MQ for z/OS

The administration of this queue manager is the subject of the course MQ20, WebSphere MQ for z/OS System Administration.

Course StrategyThe basic strategy for teaching the course is to use the material in the order in which it is written. However, you may like to consider the following variations. The WebSphere MQ for Windows NT administrative functions can only be used on the WebSphere MQ for Windows NT and Windows 2000 V5.1 or higher queue manager. Skip the charts referring to that function if no NT is involved. Many of the practical sessions can be done using WebSphere MQ for Windows. In fact it is only practical for session 2 on triggering, the last part of practical session 3, which is concerned with media recovery, and the last portion of practical session 4 on clusters that cannot be done using WebSphere MQ for Windows. If WebSphere MQ for Windows is made available, and if there are students interested in using it for the practical sessions, Unit 7 could be taught in a piecemeal fashion at certain points throughout the course. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guidexiv WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003




pref Copyright IBM Corp. 1996, 2003 Course Description xv

Course DescriptionWebSphere MQ System Administration I for Distributed Platforms

Duration: 3 days

PurposeTo provide the basic skills required by an administrator for any of the MQSeries Level 2 queue managers except MQSeries for OS/390. Specifically, the queue managers covered by this course are as follows: WebSphere MQ for AIX,V5.3 WebSphere MQ for iSeries WebSphere MQ for HP-UX, V5.3 WebSphere MQ for Linux for Intel, V5.3 WebSphere MQ for Linus for zSeries, V5.3 WebSphere MQ for Solaris, V5.3 (SPARC and Intel Platform

Editions) WebSphere MQ for Windows MQSeries for Compaq OpenVMS Alpha MQSeries for Compaq OpenVMS VAX MQSeries for Compaq Tru64 UNIX MQSeries for OS/2 Warp MQSeries for SINIX and DC/OSx MQSeries for Tandem NonStop Kernel WebSphere MQ for Windows

AudienceTechnical personnel who require the skills to be an administrator for any of the MQSeries Level 2 queue managers except WebSphere MQ for z/OS, or to provide support to others performing this task.

PrerequisitesThe course assumes a knowledge of WebSphere MQ to the level covered by MQ01, A Technical Introduction to MQSeries. The participant should also be reasonably familiar with, and be able to invoke simple function within, the operating system environment used for the practical exercises. A basic knowledge of how SNA LU6.2, TCP/IP, or NetBIOS is configured would be advantageous. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

Objectivesxvi WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

After completing this course, you should be able to: Plan the implementation of WebSphere MQ on a selected platform Install WebSphere MQ Perform simple customization and administration tasks Enable a queue manager to exchange messages with another Enable a queue manager to support an WebSphere MQ client Implement basic restart/recovery procedures Perform basic problem determination

Contents A Review of WebSphere MQ Installation and Configuration The MQI and Triggering Robust Messaging Distributed Queue Management More on Distributed Queuing WebSphere MQ Everyplace In theory, the practical exercises may be done using any of the queue managers covered by the course. In practice, however, the systems used for a specific class will depend on the equipment available. The exercise guide is tested for WebSphere MQ for Windows and for WebSphere MQ on UNIX Systems.

Curriculum relationship Course providing prerequisite knowledge:

- MQ01: A Technical Introduction to WebSphere MQ Other WebSphere MQ courses:

- MQ05: WebSphere MQ Application Programming - MQ20: WebSphere MQ for z/OS System Administration - MQ30: WebSphere MQ Advanced System AdministrationCourse materials may not be reproduced in whole or in part without the prior written permission of IBM.


pref Copyright IBM Corp. 1996, 2003 Agenda xvii

AgendaDay 1

(00:15) Welcome (00:30) A Review of WebSphere MQ (01:00) Installation and Configuration (01:00) Exercise 1 - Working with queues (02:00) The MQI, Triggering and Publish/Subscribe (01:15) Exercise 2 - Implementing triggering

Day 2(01:30) Robust Messaging (00:45) Exercise 3 - Recovery (02:15) Distributed Queue Management (01:30) Exercise 4 - Distributed queuing

Day 3(00:30) Queue Manager Clusters (01:15) Exercise 5 - A simple cluster (01:30) More on Distributed Queuing (01:00) Exercise 6 - Implementing clients (00:45) WebSphere MQ for EveryplaceCourse materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guidexviii WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003



Instructor GuideV2.0

Uempty Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-1

Unit 1. A Review of WebSphere MQ

What This Unit is AboutThis unit provides an introduction to WebSphere MQ and its products. It forms the basis for the remainder of the course.

What You Should Be Able to DoAfter completing this unit, you should be able to: Describe the features and benefits of WebSphere MQ Identify the level of function in each WebSphere MQ queue

manager Classify the application models that WebSphere MQ can support Find further information on specific aspects of WebSphere MQ

How You Will Check Your ProgressAccountability: Checkpoint questions Instructor questions

ReferencesSC34-6055 WebSphere MQ Script (MQSC) Command Reference SC34-6068 WebSphere MQ System Administration Guide

If using WebSphere MQ for iSeries use: SC34-6070 WebSphere MQ doe iSeries V5.3 System

Administration Guide Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide1-2 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Figure 1-1. Unit Objectives MQ157.0

Notes:This unit provides an introduction to WebSphere MQ and its products. It forms the basis for the remainder of the course. After completing this unit, the student should be able to: Describe the features and benefits of WebSphere MQ. Identify the level of function of each WebSphere MQ queue manager. Classify the application models that WebSphere MQ can support. Find further information on specific aspects of WebSphere MQ.

!

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Instructor Notes: Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-3

Purpose To highlight the unit objectives. Details In theory, all students should have attended the course MQ01, A Technical Introduction to WebSphere MQ, before attending this one, and so this unit should merely be a revision of previously acquired knowledge. Transition Statement We start by looking at the benefits that WebSphere MQ can provide. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty 1.1 Facilities and Functions Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-5

This topic provides an introduction to the facilities and functions of WebSphere MQ and discusses the benefits they provide.

Instructor Topic IntroductionWhat students will do Students will listen to a review of the facilities and functions of WebSphere MQ. For all students, it should simply be a revision of what was covered in the course MQ01, A Technical Introduction to WebSphere MQ. How students will do it No student activities are planned for this topic. What students will learn Students will learn the benefits of WebSphere MQ and the types of applications it can support. How this will help students on their job This knowledge will help the students to understand the reasons for selecting WebSphere MQ in the first place. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 1-2. WebSphere MQ - Commercial Messaging MQ157.0

Notes:WebSphere MQ is a means of program-to-program communication using messages and queues. The communicating applications can be on the same system, or they can be distributed across a network of IBM and non-IBM systems. As well as depicting the basic mechanism by which one application communicates with another, the visual also states five major benefits of WebSphere MQ. There is a common application programming interface, the MQI, that is consistent

across all the supported platforms. WebSphere MQ can transfer data with assured delivery; messages don't get lost, even

in the event of a system failure. Just as important, there is no duplicate delivery. The communicating applications don't have to be active at the same time. For example,

a sending application can still be putting messages on a queue even though the receiving application is not active.

Message driven processing is an style of application design. An application is divided into discrete functional modules which communicate with each other by means of

A

B

Queue

Queue

"

#

$



Uempty messages. In this way, the modules can execute on different systems, be scheduled at Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-7

different times, or they can act in parallel. Application development is made faster by shielding the developer from the

complexities of the network. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

Instructor Notes:1-8 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

Purpose To explain the principle of program to program communication through the use of messages and queues, and to state the benefits of WebSphere MQ. Details Additional Information None. Transition Statement Next we look at where we can find more information about WebSphere MQ. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-3. Further Information MQ157.0

Notes:The WebSphere MQ publications are listed in the bibliography at the back of these course notes. Some publications describe function that relates to two or more queue managers, the so called cross-platform publications. Other publications are platform-specific. Discover WebSphere MQ on the World Wide Web. The Web address for the WebSphere MQ home page is:

http://www.ibm.com/software/ts/mqseries/

%

$

$

!

%

&&''&&& &

(

)

*Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To identify other sources of information about WebSphere MQ. Details These notes alone don't contain all there is to know, and certainly not the latest news.

Additional Information None. Transition Statement Next we consider two basic questions. What is a message, and what is a queue? Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-4. Message and Queue MQ157.0

Notes:A message is any information that one application wishes to communicate to another. A message may convey a request for a service, or it may be a reply to such a request. It may also report on the progress of another message; to confirm its arrival or report on an error, for example. A message may also simply carry information for which no reply is expected. A queue is a place to store messages until they can be processed. The time a message has to wait in order to be retrieved and processed could be very short, or it could be a long time if it has to wait for the receiving application to be started. Either way, the ability to store a message safely is an important characteristic of a queue.

(


Instructor Guide


Purpose To clarify what is meant by a message and a queue. Details Additional Information None. Transition Statement Next we see that a wide range of applications can be built on these simple concepts. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-5. Applications Enabled by WebSphere MQ MQ157.0

Notes:

!"

*%%

%

"&

+

"

,Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To explain how the basic concepts of WebSphere MQ can be applied to a wide range of business applications. Details The simple concepts of a message and a queue are not new. They are ones that enable applications to work in many different ways. The components of an application can run independently on different systems and environments, and may involve a number of processing steps. A key aspect of WebSphere MQ with respect to messages and queues is the assurance against the loss or duplication of messages. Additional Information None. Transition Statement Next we introduce the concept of a queue manager, and the application programming interface it provides to an application. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-6. Queue Manager MQ157.0

Notes: The component of WebSphere MQ software which owns and manages queues is called

a queue manager. A queue manager also provides a family of application programming interfaces.

- The Message Queue Interface (MQI) enables an application to access its queues and the messages they contain. The MQI is a simple application programming interface which is consistent across all platforms supported by WebSphere MQ. The MQI effectively protects applications from having to know how a queue manager physically manages messages and queues. The MQI allows full access to WebSphere MQ messaging support.

- The Application Messaging Interface (AMI) is a high-level API that simplifies programming for application messaging and publish/subscribe. It provides a high level of abstraction, moving message-handling logic from the application into the middleware. The AMI allows programmers to use policies and services to define how and where the messages are sent.

$

#-.-/

#

-.-/

#0.0/

-

1

2

3

-

0Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

- The Java Message Service (JMS) is a specification of a portable API for 1-16 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

asynchronous messaging. JMS has been developed by Sun Microsystems in collaboration with IBM and other vendors interested in promoting industry wide standard frameworks. JMS is an object-oriented Java API with a set of generic messaging objects for programmers to write event-based messaging applications. JMS supports both request/reply and publish/subscribe models as separate object models. JMS is available in WebSphere MQ V5.2.

All three of the APIs can interoperate. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Instructor Notes: Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-17

Purpose To introduce the concept of a queue manager and the three APIs: The MQI, the AMI and the JMS. Details Having a common application programming interfaces across all supported platforms is one of the major benefits of WebSphere MQ. We shall see later the platforms which are supported. Additional Information None. Transition Statement Next we look a little more closely at the calls provided by the MQI. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 1-7. MQI Calls MQ157.0

Notes:The most basic calls allow an application to put a message on a queue and get a message from a queue. MQPUT and MQPUT1

Put a message on a named queue. Generally, a message is added to the end of a queue.

MQGET Gets a message from a named queue. Generally, a message is removed from the front of a queue.

The other calls are as follows. MQCONN, MQCONNX, and MQDISC

Enable an application to connect to a queue manager and disconnect from a queue manager. An application must connect to a queue manager before it can issue any further MQI calls.

MQOPEN and MQCLOSEEnable an application to open a queue for specified operations and close

4'''

*5#

*5#1

'''

6#

7

"7,,"7,,8+-"

7*,"(7

-,#

)6-,"-#)"9Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty the queue when access to it is no longer required. An application must Copyright IBM Corp. 1996, 2003 Unit 1. A Review of WebSphere MQ 1-19

open a queue before it can access it in any way; to put messages on it, or get messages from it, for example.

MQINQ and MQSETInquire on and set the attributes of an object. All WebSphere MQ objects, such as a queue, a process, and the queue manager object, have a set of attributes.

MQBEGIN, MQCMIT, and MQBACKEnable an application to put and get messages as part of a unit of work. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To introduce the calls in the MQI. Details The visual lists all the MQI calls. Sample programs illustrating their use are supplied with WebSphere MQ. Additional Information We shall discuss the MQI calls in a little more detail later. The following references provide more information. The Application Programming Reference describes each call in the MQI and, more

generally, defines the MQI. The WebSphere MQ Application Programming Reference describes each call in the

MQI and, more generally, defines the MQI. The WebSphere MQ Application Programming Guide describes all the samples

programs delivered With WebSphere MQ. It also provides the information required to build an application.

Transition Statement Next we look at a simple application model and introduce the message descriptor. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-8. Message Descriptor MQ157.0

Notes:A message consists of two parts: Message descriptor Application data The message descriptor contains information about the message. The sending application supplies both the message descriptor and the application data when it puts a message on a queue, and both the message descriptor and the application data are returned to the application which gets the message from the queue. Some of the fields in the message descriptor are set by the application which puts the message on a queue; others are set by the queue manager on behalf of the application.

#

1

2


Instructor Guide


Purpose To explain the basic conversational model, and to introduce the message descriptor. Details The simplest application model using messages and queues is depicted on the visual. Program A puts a request message on queue Q1 and then waits for a reply to appear on queue Q2 before continuing. Program B gets the message from queue Q1 and puts the required reply message on queue Q2 to complete the process. In the basic conversational model depicted on the visual, a message descriptor will accompany the message that is put on queue Q1, and another will accompany the message that is put on queue Q2. Additional Information None. Transition Statement The basic conversational model is a synchronous one. Next, we shall look at an asynchronous version. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-9. Asynchronous Model MQ157.0

Notes: In the asynchronous model, instead of waiting for a reply to its first message, Program A

continues to send further requests to Program B. It is a separate process, Program X, which receives the replies when they arrive.

In this model, Program A is not dependent on Program B to be running when the requests are sent. It can continue to do work even when Program B is stopped.

Of course the application does expect Program X to receive the replies at some time, but not necessarily at the same time that Program A or Program B is running. All this illustrates another of the major benefits of WebSphere MQ, time independence.

"

,

#

1

2


Instructor Guide


Purpose To explain the asynchronous model and how it leads to the benefit of time independence. Details Nothing in addition to the student notes. Additional Information None. Transition Statement Next we look at how triggering enhances the implementation of time-independent processing. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-10. Triggering MQ157.0

Notes:WebSphere MQ provides an enhancement to the implementation of time-independent processing, triggering. The arrival of a message on an application queue may indicate that it is an appropriate time for another application to be started in order to process the messages on the application queue. When the right conditions are detected by the queue manager, it is the triggering facility which starts the application to service the application queue. We will revisit triggering in some depth later.

$

#

-

"

%

&

'

(

-

*5#%

*

6#%

6#-%

#

*)

)

*

*

7:Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To introduce the concept of triggering. Details The previous example showed how Program A could continue running even though its partner, Program B, was stopped. Of course, Program B must start some time. Additional Information None. Transition Statement Next we look at how WebSphere MQ allows parallel processing within an application. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Figure 1-11. Parallel Processes MQ157.0

Notes: This model allows several requests to be sent by a application without the application

having to wait for a reply to one request before sending the next. All the requests can then be processed in parallel.

The application can process the replies when they have all been received, and produce a consolidated answer. The program logic might also specify what to do when only a partial set of replies is received within a given period of time.

++

;

"

*6#DE

*

>2@

"

,

.,%Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Instructor Notes: Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-9

Purpose To provide the rules for naming an WebSphere MQ object, viz a queue, a process, the queue manager object, and a channel. Details The rules for naming WebSphere MQ objects are the same on all supported platforms. There is no implied structure in a name such as you might find in the rules for file names on many operating systems. Additional Information None. Transition Statement After installation, the first WebSphere MQ object to be created is a queue manager. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-3. Queue Manager MQ157.0

Notes:Again, queue manager names are case-sensitive. After installation, the first WebSphere MQ object to be created is a queue manager. Typically, you only need to create one queue manager per system, but you can create others, for example, for testing purposes. The exception is WebSphere MQ for iSeries for which only one queue manager per system is allowed. Every queue manager has a name which should be unique within a network of queue managers exchanging messages with each other. The reason for this is that, when generating a unique message identifier for a message, a queue manager uses the first 12 characters of its name as part of the identifier.

6

,

5

$>#"*&-*

,(5

!Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Purpose To indicate some of the considerations that apply when creating a queue manager. Details Although a longer name is allowed, a queue manager is usually given a short name. Common options are to give a queue manager the same name as the TCP/IP host name, the Windows NT system name, or the LU alias of the SNA LU which is supporting it, and so on. Additional Information WebSphere MQ V5.3 supports queues over 2GB in size. Limit now 2 TB. Minimum queue footprint in memory is reduced from 250KB to 64KB. This allows more queues to be opened. On AIX, HP-UX, and Sun Solaris you will need to enable large queues to be used. This process must be performed before you create queues with large sizes. Transition Statement Next we look at the various types of queues and some naming conventions for them. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-4. Queues MQ157.0

Notes:Queue names are case-sensitive. There are some useful conventions for naming a queue. The name of a queue should not contain an indication of its type or location. In this way,

if a queue changes from being a local queue to being a remote queue for example, you can still use the same name for the queue and applications referencing the queue require no change, not even a recompilation. Instead, the name of a queue should describe its function.

Using a common prefix for the names of related queues can aid administration, for example, searching for all queues related to an application.

7

(

>

5

#

>




Purpose To identify the different types of queue and to provide some recommendations for naming a queue. Details Every queue is owned by a queue manager and possesses a name. An application identifies a queue by its name, but this may need to be qualified by the name of the owning queue manager if the queue does not have a local definition. Generally, the type of a queue is transparent to an application. The exceptions are when opening a model queue and closing a dynamic queue as these may require some special processing. Additional Information None. Transition Statement Next we look at some special local queues that are used by WebSphere MQ. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-5. Special Local Queues MQ157.0

Notes:There are some local queues which have special purposes in WebSphere MQ. A dead letter queue is a designated queue upon which a queue manager will put

messages that cannot otherwise be delivered. It is not mandatory for a queue manager to have a dead letter queue, but it is strongly recommended.

An initiation queue is a queue which is used to implement triggering. We shall be discussing triggering in more detail later in the course.

We have already seen the role of a transmission queue in relation to message channels.

In this way, a queue manager can be controlled by an administration application running locally or remotely.

When a queue manager detects an instrumentation event, it puts an event message describing the event on an event queue. An event queue can be monitored by a system management application which can get each message put on the queue and take the appropriate action.

1

+

7

+

-

5

#

"

+ Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty The purpose of the default queues is to identify the default values of the attributes of Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-15

any new queue you create. There is one default queue for each of the four types of queues, namely, local, alias, remote, and model. Thus, you only need to include in the definition of a queue those attributes whose values are different from the default values. You can change the default value of an attribute simply by redefining the appropriate default queue. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To introduce some special local queues that are used by WebSphere MQ. Details Additional Information None. Transition Statement Next we look at message channels. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-17

Figure 2-6. Message Channel MQ157.0

Notes: A message channel is a one-way link between two queue managers for the

transmission of messages. It consists of an MCA at the sending end, an MCA at the receiving end, and a communications connection between the two. The communications connection may be an SNA LU6.2 conversation, a TCP connection, and so on.

Each end of a message channel has a separate definition. Both definitions contain the name of the message channel. Among other things, the definition at each end of a message channel also indicates: - Whether it is the sending end or the receiving end of the channel, and - The communications protocol to be used.

A transmission queue is required for each message channel. - A transmission queue is really just a local queue, but it has an attribute whose value

indicates its special role.

6#

*5#

,(5F'2#"*&-*


Instructor Guide

- A transmission queue is located at the sending end of a message channel. As a 2-18 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

result, only the definition of the message channel at the sending end contains the name of the transmission queue.

- Any message destined for a remote queue is put by the queue manager onto a transmission queue. But how does the queue manager know which transmission queue to use? One way is to give the transmission queue the same name as the name of the destination queue manager. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Purpose To explain the need to define a message channel at both ends of the channel and to define its associated transmission queue. Details Nothing in addition to the student notes. Additional Information None. Transition Statement Next we look at the various administration interfaces provided by WebSphere MQ. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-7. Administration Interfaces MQ157.0

Notes:

."/

*"$.*"$/

*

*"$

*

#,9

65-

-

7&D@@"(

-,-+

*




Purpose To identify the interfaces available for the administration of a queue manager. Details The visual depicts all the administration interfaces provided by WebSphere MQ. WebSphere MQ commands (MQSC)

WebSphere MQ commands can only entered by means of an interface supplied with WebSphere MQ.

There are two modes of entering WebSphere MQ commands: - Interactively, by typing an WebSphere MQ command at the

keyboard and waiting for the result. This mode is not available on WebSphere MQ for iSeries.

- Using a text editor, you can create a file containing a sequence of WebSphere MQ commands and then submit the file for execution.

The WebSphere MQ commands are described in the WebSphere MQ Script (MQSC) Command Reference.

Programmable Command Format (PCF) commands PCF commands have a highly structured format and contain binary

information as well as character information. The structured format makes it easier for an application to generate the components of a PCF command dynamically. A reply to a PCF command has a similar format which makes it easier for an application to parse.

An application can construct a message containing a PCF command and put it on the command queue of a queue manager. The message is then got by the command server of the queue manager, the PCF command in the message is executed, and the reply is put on the specified reply-to queue.

The existence of a command queue and a command server on each queue manager in a network of queue managers enables each queue manager to be managed from just one system in the network. This concept is known as a single point of control.

The Escape PCF command is used to submit an WebSphere MQ command which is held as text within the PCF command. This command can be useful for managing up-level queue managers or queue managers with unique features.

PCF commands are described in WebSphere MQ Programmable Command Formats and Administration Interfaces. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

WebSphere MQ Administrative Interface (MQAI)2-22 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

The MQAI is a programming interface to WebSphere MQ, using C language and also Visual Basic for Windows. It performs administrative tasks on a WebSphere MQ queue manager using data bags. Data bags allow you to handle properties (or parameters) of objects in a way that is easier than using the other administrative interface, PCFs.

You can use MQAI to: Implement self administering applications and administration tools. Simplify the use of PCF messages. You dont have to write your

own PCG messages and thus avoid problems associated with complex data structures.

Handle error conditions more easily. It is difficult to get return codes back from the WebSphere MQ script (MQSC) commands, but MQAI makes it easier.

Control commands Control commands are entered at a command prompt of the

operating system in use, or they can be included in an operating system command file such as a shell script on a UNIX system.

Control commands are described in MQSeries System Administration for a Version 5 queue manager and in the relevant System Management Guide for each of the remaining queue managers.

Administration application MQSeries for Tandem NonStop Kernel also has a panel driven

administration facility, but it can only be used to manage a queue manager on the system you are working on. Its use is described in the MQSeries for Tandem NonStop Kernel System Management Guide.

WebSphere MQ for Windows NT and Windows 2000 V5.1 and higher has some additional administration interfaces.

No other queue manager covered by this course has an administration application.

OS/400 CL commands The WebSphere MQ CL commands are only supported on

WebSphere MQ for iSeries and can be entered anywhere an OS/400 CL command can be entered. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty The WebSphere MQ CL commands are described in the Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-23

WebSphere MQ for iSeries V5.3 System Administration Guide. INI file and MQD file on WebSphere MQ for Windows

An initialization (INI) file or an WebSphere MQ definition (MQD) file is used to define all the WebSphere MQ components required on a Windows workstation in preparation for running applications.

An INI file is only used on WebSphere MQ for Windows Version 2.0 and is processed by the Create and Go utility. An MQD file is only used on WebSphere MQ for Windows Version 2.1 and may be processed when WebSphere MQ is installed, or when WebSphere MQ starts, or by selecting Run MQD file now from the WebSphere MQ icon menu, depending on the requirement.

Event messages When a queue manager detects an instrumentation event during

its operation, it puts an event message on an event queue. The event message contains information about the event that has occurred.

Event messages have a format similar to PCF commands and are therefore intended to be processed by applications. An event queue can therefore be monitored by a system management application which can get each message put on the queue and take the appropriate action, for example, by putting a message containing a PCF command on the command queue of the queue manager.

Event messages are supported by all the queue managers covered by this course except WebSphere MQ for Windows Version 2.0.

Additional Information None. Transition Statement With the introduction of WebSphere MQ for Windows V5.1, there are several new available interfaces. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-8. WebSphere MQ Windows Administration Interfaces MQ157.0

Notes:In addition to the administration interfaces listed on the previous page, WebSphere MQ for Windows offers some additional interfaces to accomplish administration tasks. The WebSphere MQ Explorer snap-in

This runs under the Microsoft Management Console (MMC), providing a graphical user interface for controlling resources in the network. It allows definition and control of: - Queues - Channels - Process definitions - Namelists - Clusters - Client connections - Queue managers

>

%

"."/

/



Uempty With the WebSphere MQ Explorer, you can stop or start a queue manager and its Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-25

associated tasks (such as channel initiator, listener, and so forth), view queue managers and the objects it owns and check the status of channels, queue managers and clusters. It is recommended that the WebSphere MQ Explorer not be used with a queue manager that has a large number of objects defined. Delays can result as the WebSphere MQ Explorer extracts information to build its view. Large clusters can also cause difficulties because they are presented by the WebSphere MQ Explorer in a tree structure; large tree structures can be difficult to work with. The built-in message browser displays the first 200 messages on a queue; and, it only formats and displays the first 1000 bytes of user message data on the screen. Repository queue managers (to be described in greater detail later) can not be administered with the WebSphere MQ Explorer if they are on WebSphere MQ for z/OS. At least one repository should be on a non-z/OS platform.

The WebSphere MQ Services Snap-in. This also runs under MMC and allows for more advanced tasks, generally setting up and fine tuning the WebSphere MQ environment. Some of the tasks duplicate things that can be done in the WebSphere MQ Explorer while others cannot be done in the Explorer facility. - Start or stop a queue manager. - Change the default queue manager.

Be careful that this does not affect the running of your system. If the current default queue manager is running when this is done, it may still think it is the default queue manager for some things (like the well-known TCP/IP port it is using).

- Start or stop individual processes like a listener or trigger monitor. - Start or stop the command server. - Start or stop the service trace. - Set the queue manager so that it will automatically start when the system is brought

up. The WebSphere MQ Services snap-in uses Component Object Model (COM) and distributed Component Object Model (DCOM) technology to communicate between servers and between processes on a server. The COM server application (AMQMSVRN) is shared among client processes making use of the WebSphere MQ Services snap-in component. It runs under a special user account called "MQAdmin", created when WebSphere MQ is installed. To grant other users access to the WebSphere MQ Services snap-in a tool called DCOMCFNG.EXE must be run to configure their permissions properly.

WebSphere MQ Web Administration Support for Web Administration has been removed. If you have these features installed from a previous release for the product you will lose then when you upgrade.Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

In addition to the above interfaces, there are some functions available in the administration 2-26 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

arena for WebSphere MQ for Windows NT V5.1 that will allow you to easily learn to work with the product. These can be seen by looking at the First Steps menu. Included are the ability to create a default configuration, use a postcard function to send instant messages and an API exerciser to test the setup of a queue manager and its queues. In addition, the reference library and a quick tour give you access to additional information. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.



Purpose To introduce WebSphere MQ for Windows Administration interfaces. Details The visual shows a high level review of the additional interfaces introduced for Windows. If the system setup allows, the following is a recommended demonstration to show students some of the new functions: Take the time to bring up the WebSphere MQ First Steps and show students how to use

the DEFAULT CONFIGURATION to set up a queue manager. Using the default setup, demonstrate the use of POSTCARD. Create a local queue for the default queue manager and show the use of the API

EXERCISER Additional Information None. Transition Statement End of the topic. Now we are ready to create and configure a queue manager. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty 2.2 Configuring a Queue Manager Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-29

After a brief look at what you need to consider when installing WebSphere MQ, the topic continues by describing the tasks of creating, configuring, and controlling a queue manager.

Instructor Topic IntroductionWhat students will do Students will listen to a presentation on configuring a queue manager. How students will do it Following the presentation, the students will have an practical exercise in configuring a queue manager. What students will learn Students will learn how to create a queue manager, how to provide a basic configuration for it, and how to start and stop it. How this will help students on their job These are the first steps in using WebSphere MQ within an actual installation. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Figure 2-9. Installation MQ157.0

Notes: The general rules are as follows:

- Installing WebSphere MQ is like installing any other software on the same platform. - Always follow the instructions in:

The appropriate Quick Beginnings Guide for the WebSphere MQ queue manager.

The WebSphere MQ for iSeries V5.3 System Administration Guide. The appropriate System Management Guide for each of the remaining queue

managers. Pay particular attention to instructions about what to do before installation. For

example: - For WebSphere MQ on UNIX systems, you must create a user ID with the name

mqm whose primary group is mqm. - For MQSeries for Tandem NonStop Kernel, you must create a user ID in the group

MQM and log on as that user in order to install the product.

5"7888

8880/

.:#,;

!.+"&7>/

.-,-8/

"+%7

!

$.+:

,%

-,#((

"-+

,'==

67(-"*6

1;

I*!

888Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Pay particular attention to instructions about what to do before using WebSphere MQ. Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-31

For example, on some UNIX systems, you are advised to change the values of certain kernel parameters if they are not sufficient to support WebSphere MQ.

You may install WebSphere MQ for AIX using SMIT, or you may choose the easy installation. The easy installation only places a minimal typical set of components on your system. It excludes, for example, the online documentation and the application development support. Further details can be found in WebSphere MQ for AIX, V5.3 Quick Beginnings GC34-6076.

During the installation of MQSeries for Tandem NonStop Kernel, you are prompted to enter the name of the volume to be used for the installation. If you do not enter a name, the default installation volume, $SYSTEM, is used instead. The name $SYSTEM is used in the examples throughout these course notes. If your installation volume is different, you will need to replace the name $SYSTEM with the name of your installation volume wherever appropriate. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide


Purpose To highlight the more important points to bear in mind when installing WebSphere MQ. Details During the installation of WebSphere MQ for Windows, the local group mqm is created automatically if it does not already exist on the system. The installation of WebSphere MQ for iSeries creates a special user profile QMQM which cannot have a password allocated to it. WebSphere MQ for iSeries libraries and objects are owned by this user profile. During installation, WebSphere MQ automatically creates an WebSphere MQ configuration file which contains information relevant to all queue managers that will be created on the system. There is only one WebSphere MQ configuration file per system. When a queue manager is created, a queue manager configuration file is automatically created at the same time. This file contains information that is relevant to a specific queue manager. There is one queue manager configuration file for each queue manager. Both of these files contain text and are therefore readable. Their contents may be changed by certain commands and, in special circumstances, you may need to edit them, but this is the exception rather than the rule. They are described more fully later on. At this stage, it is enough to be aware that they exist and that they are used by WebSphere MQ. Additional Information For WebSphere MQ V5.3 both WebSphere MQ base Java and WebSphere MQ JMS are installed with WebSphere MQ. Please refer to the WebSphere MQ using Java manual for prerequisites to fully support WebSphere MQ for Java. Transition Statement Next we look at how to create a queue manager. Course materials may not be reproduced in whole or in part without the prior written permission of IBM.


Uempty Copyright IBM Corp. 1996, 2003 Unit 2. Installation and Configuration 2-33

Figure 2-10. Create Queue Manager MQ157.0

Notes: crtmqm, create queue manager, and dltmqm, delete queue manager, are examples of

control commands. The name of the queue manager is a required parameter on both of these commands.

Some of the following optional parameters of the crtmqm command may be useful in the practical exercises. -q Specifies that this queue manager is to be made the default queue

manager. -lc Circular logging is to be used. This is the default logging method. -ll Linear logging is to be used. Linear logging is needed for recovery from

media failures. -lf LogFileSize

The size of each of the log files expressed as a multiple of 4 KB. -ld LogPath

The directory to be used to hold the log files.

--

-

4

% Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Instructor Guide

On MQSeries for Tandem NonStop Kernel, the crtmqm command has two additional 2-34 WebSphere MQ System Administration I Copyright IBM Corp. 1996, 2003

required parameters besides the name of the queue manager. -n PATHMONProcessName

The name of the TS/MP

Documents

MQ15 - WebSphere MQ System Administration I