WebSphere MQ: System Administration Guide - IBM
WebSphere MQ System Administration Guide Version 7.0 SC34-6928-01
WebSphere MQ System Administration Guide Version 7.0 SC34-6928-01
Note Before using this information and the product it supports, be sure to read the general information under notices at the back of this book. Second edition (January 2009) This edition of the book applies to the following product: v IBM WebSphere MQ, Version 7.0 and to any subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 1994, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Figures . . . . . . . . . . . . . . vii What you can do with the WebSphere MQ Explorer . . . . . . . . . . . . Setting up the WebSphere MQ Explorer . . Using the WebSphere MQ Explorer . . . Security on Windows . . . . . . . . Extending the WebSphere MQ Explorer . . . Who this chapter is for . . . . . . . What you need to know to understand this chapter . . . . . . . . . . . . . Introduction . . . . . . . . . . . Writing an Eclipse plug-in for the WebSphere MQ Explorer . . . . . . . . . . . Applying plug-ins to the WebSphere MQ Explorer . . . . . . . . . . . . Tables . . . . . . . . . . . . . . . ix Chapter 1. Introduction . . . . . . . . 1 Introduction to WebSphere MQ . . . . . . . . 1 WebSphere MQ and message queuing . . . . . 1 Messages and queues . . . . . . . . . . 2 Objects . . . . . . . . . . . . . . . 3 Clients and servers . . . . . . . . . . . 10 Extending queue manager facilities . . . . . 11 Security . . . . . . . . . . . . . . 12 Transactional support . . . . . . . . . . 13 An introduction to WebSphere MQ administration 13 Local and remote administration . . . . . . 14 Performing administration tasks using commands 14 Further methods of administration . . . . . 15 Understanding WebSphere MQ file names . . . 17 Chapter 2. Administration using WebSphere MQ commands . . . . . . 19 Managing queue managers . . . . . . . Using control commands . . . . . . . Using the WebSphere MQ Explorer . . . Creating a queue manager . . . . . . Starting a queue manager . . . . . . Stopping a queue manager . . . . . . Restarting a queue manager . . . . . . Deleting a queue manager . . . . . . Administering local WebSphere MQ objects . Supporting application programs that use the MQI . . . . . . . . . . . . . . Performing local administration tasks using MQSC commands . . . . . . . . . Working with queue managers . . . . . Working with local queues . . . . . . Working with alias queues . . . . . . Working with model queues. . . . . . Working with services . . . . . . . . Managing objects for triggering. . . . . Automating administration tasks . . . . . PCF commands . . . . . . . . . . Administering remote WebSphere MQ objects . Channels, clusters, and remote queuing . . Remote administration from a local queue manager . . . . . . . . . . . . Creating a local definition of a remote queue Using remote queue definitions as aliases . Data conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 19 20 20 25 25 27 27 28 . . 28 . . . . . . . . . . . . . . . . . . . . . . 29 36 38 43 45 46 52 54 54 57 57 . . . . . . . . 59 65 68 69 Chapter 3. Administration using the WebSphere MQ Explorer . . . . . . . 71 Administration using the WebSphere MQ Explorer Copyright IBM Corp. 1994, 2009 71 . . . . . . . . . . . . 71 73 79 81 85 85 . . . 85 . 85 . . 86 . . 91 Chapter 4. Configuring WebSphere MQ 93 Configuring WebSphere MQ. . . . . . . . . 93 Changing configuration information on Windows systems. . . . . . . . . . . . . . . 93 Changing configuration information on UNIX systems. . . . . . . . . . . . . . . 93 Attributes for changing WebSphere MQ configuration information . . . . . . . . 99 Changing queue manager configuration information . . . . . . . . . . . . . 105 WebSphere MQ security . . . . . . . . . . 119 Authority to administer WebSphere MQ . . . 120 Authority to work with WebSphere MQ objects 121 Connecting to WebSphere MQ using Terminal Services . . . . . . . . . . . . . . 126 Configuring additional authority for Windows applications connecting to WebSphere MQ . . 126 Creating and managing groups . . . . . . 127 Using the OAM to control access to objects . . 132 Channel security . . . . . . . . . . . 137 How authorizations work . . . . . . . . 140 Guidelines for Windows . . . . . . . . . 153 Transactional support. . . . . . . . . . . 156 Introducing units of work . . . . . . . . 156 Scenario 1: Queue manager performs the coordination . . . . . . . . . . . . . 157 Scenario 2: Other software provides the coordination . . . . . . . . . . . . . 182 The WebSphere MQ dead-letter queue handler . . 190 Invoking the DLQ handler . . . . . . . . 190 The DLQ handler rules table . . . . . . . 191 How the rules table is processed . . . . . . 197 An example DLQ handler rules table . . . . 199 Supporting the Microsoft Cluster Service (MSCS) 200 Introducing MSCS clusters . . . . . . . . 201 Setting up WebSphere MQ for MSCS clustering 202 Creating a queue manager for use with MSCS 205 Moving a queue manager to MSCS storage . . 205 Putting a queue manager under MSCS control 207 Summary of looksAlive and isAlive polling . . 209 iii
Removing a queue manager from MSCS control 209 Hints and tips on using MSCS. . . . . . . 211 WebSphere MQ MSCS support utility programs 214 Chapter 5. Recovery and problem determination . . . . . . . . . . . 217 Availability, recovery and restart . . . . . . . Making sure that messages are not lost (logging) Using checkpointing to ensure complete recovery . . . . . . . . . . . . . . Calculating the size of the log . . . . . . . Managing logs . . . . . . . . . . . . Using the log for recovery . . . . . . . . Protecting WebSphere MQ log files . . . . . Backing up and restoring WebSphere MQ . . . Recovery scenarios . . . . . . . . . . Dumping the contents of the log using the dmpmqlog command. . . . . . . . . . Problem determination . . . . . . . . . . Preliminary checks . . . . . . . . . . Looking at problems in more detail . . . . . Application design considerations . . . . . Error logs . . . . . . . . . . . . . Dead-letter queues . . . . . . . . . . Configuration files and problem determination Tracing . . . . . . . . . . . . . . First-failure support technology (FFST) . . . . Problem determination with WebSphere MQ clients . . . . . . . . . . . . . . . Java diagnostics . . . . . . . . . . . 217 217 220 222 224 227 229 230 234 236 240 240 244 250 251 254 254 255 264 269 269 Chapter 6. WebSphere MQ control commands . . . . . . . . . . . . 273 How to use WebSphere MQ control commands Names of WebSphere MQ objects. . . . Syntax diagrams . . . . . . . . . Example syntax diagram . . . . . . Syntax help . . . . . . . . . . . The control commands . . . . . . . . amqccert . . . . . . . . . . . . amqmdain . . . . . . . . . . . amqtcert . . . . . . . . . . . . crtmqcvx . . . . . . . . . . . . crtmqm . . . . . . . . . . . . dltmqm . . . . . . . . . . . . dmpmqaut . . . . . . . . . . . dmpmqlog . . . . . . . . . . . dspmq. . . . . . . . . . . . . dspmqaut . . . . . . . . . . . dspmqcsv . . . . . . . . . . . dspmqfls . . . . . . . . . . . . dspmqrte . . . . . . . . . . . . dspmqtrc . . . . . . . . . . . . dspmqtrn. . . . . . . . . . . . dspmqver . . . . . . . . . . . endmqcsv . . . . . . . . . . . endmqlsr . . . . . . . . . . . . endmqdnm . . . . . . . . . . . endmqm . . . . . . . . . . . . endmqtrc . . . . . . . . . . . . iv WebSphere MQ: System Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 273 274 275 276 276 277 278 284 289 291 296 297 301 302 304 307 308 310 318 319 320 321 323 323 324 326 mqftapp . . . . . . . . . . . . . . mqftrcv . . . . . . . . . . . . . . mqftrcvc . . . . . . . . . . . . . . mqftsnd . . . . . . . . . . . . . . mqftsndc . . . . . . . . . . . . . . rcdmqimg . . . . . . . . . . . . . rcrmqobj . . . . . . . . . . . . . . rsvmqtrn . . . . . . . . . . . . . . runmqchi. . . . . . . . . . . . . . runmqchl. . . . . . . . . . . . . . runmqdlq . . . . . . . . . . . . . runmqdnm . . . . . . . . . . . . . runmqlsr . . . . . . . . . . . . . . runmqsc . . . . . . . . . . . . . . runmqtmc . . . . . . . . . . . . . runmqtrm . . . . . . . . . . . . . setmqaut . . . . . . . . . . . . . . setmqcrl . . . . . . . . . . . . . . setmqprd . . . . . . . . . . . . . . setmqscp . . . . . . . . . . . . . . strmqcfg . . . . . . . . . . . . . . strmqcsv . . . . . . . . . . . . . . strmqm . . . . . . . . . . . . . . strmqtrc . . . . . . . . . . . . . . Managing keys and certificates . . . . . . . Preparing to use the gsk7cmd and gsk7capicmd commands . . . . . . . . . . . . . gsk7cmd, runmqckm, and gsk7capicmd commands . . . . . . . . . . . . . gsk7cmd, runmqckm, and gsk7capicmd options 328 328 331 334 336 338 340 342 343 344 345 346 348 350 352 353 354 361 362 362 363 364 365 367 373 374 375 387 Chapter 7. WebSphere MQ installable services and the API exit . . . . . . 391 Installable services and components . . . . . . Why installable services? . . . . . . . . Functions and components . . . . . . . . Initialization. . . . . . . . . . . . . Configuring services and components . . . . Creating your own service component . . . . Using multiple service components . . . . . Authorization service. . . . . . . . . . . Object authority manager (OAM). . . . . . Authorization service on UNIX systems . . . Authorization service on Windows systems . . Authorization service interface . . . . . . Name service . . . . . . . . . . . . . How the name service works . . . . . . . Installable services interface reference information How the functions are shown . . . . . . . MQZEP – Add component entry point . . . . MQZ AUTHENTICATE USER – Authenticate user . . . . . . . . . . . . . . . MQZ CHECK AUTHORITY – Check authority MQZ CHECK AUTHORITY 2 – Check authority (extended) . . . . . . . . . . MQZ COPY ALL AUTHORITY – Copy all authority . . . . . . . . . . . . . . MQZ DELETE AUTHORITY – Delete authority MQZ ENUMERATE AUTHORITY DATA – Enumerate authority data . . . . . . . . MQZ FREE USER – Free user. . . . . . . 391 391 392 394 394 396 397 398 398 399 400 401 402 403 404 404 405 406 409 414 419 421 424 427
MQZ GET AUTHORITY – Get authority . . MQZ GET AUTHORITY 2 – Get authority (extended) . . . . . . . . . . . . MQZ GET EXPLICIT AUTHORITY – Get explicit authority . . . . . . . . . . MQZ GET EXPLICIT AUTHORITY 2 – Get explicit authority (extended) . . . . . . MQZ INIT AUTHORITY – Initialize authorization service . . . . . . . . . MQZ INQUIRE – Inquire authorization service MQZ REFRESH CACHE – Refresh all authorizations . . . . . . . . . . . MQZ SET AUTHORITY – Set authority . . MQZ SET AUTHORITY 2 – Set authority (extended) . . . . . . . . . . . . MQZ TERM AUTHORITY – Terminate authorization service . . . . . . . . . MQZAC – Application context . . . . . MQZAD – Authority data . . . . . . . MQZED – Entity descriptor . . . . . . MQZIC – Identity context . . . . . . . MQZFP – Free parameters . . . . . . . MQZ DELETE NAME – Delete name . . . MQZ INIT NAME – Initialize name service . MQZ INSERT NAME – Insert name . . . MQZ LOOKUP NAME – Lookup name . . MQZ TERM NAME – Terminate name service API exits . . . . . . . . . . . . . . Why use API exits. . . . . . . . . . How you use API exits . . . . . . . . What happens when an API exit runs? . . . Configuring API exits . . . . . . . . API exit reference information . . . . . . . General usage notes . . . . . . . . . MQACH – API exit chain header . . . . . MQAXC – API exit context . . . . . . . MQAXP – API exit parameter . . . . . . MQXEP – Register entry point. . . . . . MQXEPO – Register entry point options . . MQ BACK EXIT – Back out changes . . . MQ BEGIN EXIT – Begin unit of work . . MQ CALLBACK EXIT – Callback . . . . MQ CLOSE EXIT – Close object . . . . . MQ CMIT EXIT – Commit changes . . . . MQ CONNX EXIT – Connect queue manager (extended) . . . . . . . . . . . . MQ DISC EXIT – Disconnect queue manager MQ GET EXIT – Get message . . . . . MQ INIT EXIT – Initialize exit environment MQ INQ EXIT – Inquire object attributes . . MQ OPEN EXIT – Open object . . . . . MQ PUT EXIT – Put message. . . . . . MQ PUT1 EXIT – Put one message . . . . MQ SET EXIT – Set object attributes . . . MQ SUB EXIT – Register subscription . . . MQ SUBRQ EXIT – Subscription request . . MQ TERM EXIT – Terminate exit environment . 428 . 431 . 435 . . . . . . Chapter 10. Directory structure (UNIX systems) . . . . . . . . . . . . . 531 . 438 . 441 443 . 447 . 449 . 452 . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 457 459 462 464 465 466 468 471 473 475 477 477 477 479 479 482 483 484 486 490 498 501 503 504 505 506 507 . 508 509 . 510 512 . 513 . 514 . 515 . 516 . 518 . 519 . 520 521 Chapter 8. System and default objects 523 Windows default configuration objects . SYSTEM.BASE.TOPIC . . . . . . Chapter 9. Directory structure (Windows systems) . . . . . . . . . 529 Chapter 11. Stopping and removing queue managers manually . . . . . . 537 Stopping a queue manager manually . . . . . Stopping queue managers in WebSphere MQ for Windows . . . . . . . . . . . . . . Stopping queue managers in WebSphere MQ for UNIX systems . . . . . . . . . . . . Removing queue managers manually . . . . . Removing queue managers in WebSphere MQ for Windows . . . . . . . . . . . . Removing queue managers in WebSphere MQ for UNIX systems . . . . . . . . . . . Chapter 12. File Transfer Application Introduction . . . . . . . . . . . . Advantages . . . . . . . . . . . Components. . . . . . . . . . . Installing and configuring . . . . . . . Installing the File Transfer Application on a WebSphere MQ server . . . . . . . Installing the File Transfer Application on a WebSphere MQ client . . . . . . . Setup tasks . . . . . . . . . . . Configuring the GUI . . . . . . . . File Transfer Application channel security . Using the File Transfer Application . . . . Sending a file . . . . . . . . . . Receiving a file . . . . . . . . . . Listing all sent and received files . . . . File status . . . . . . . . . . . Using the command line . . . . . . 537 537 538 538 539 540 541 . . . . . . . . 541 541 542 542 . . 542 . . . . . . . . . . . . . . . . . . . . 543 544 548 549 549 549 549 550 550 551 Chapter 13. Comparing command sets 553 Chapter 14. WebSphere MQ and UNIX System V IPC resources. . . . . . . 559 Queue manager commands. . . . . Command server commands . . . . Authority commands . . . . . . . Cluster commands . . . . . . . Authentication information commands . Channel commands . . . . . . . Listener commands . . . . . . . Namelist commands . . . . . . . Process commands . . . . . . . Queue commands . . . . . . . . Service commands. . . . . . . . Other commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 553 554 554 554 555 555 555 556 556 557 557 Clearing WebSphere MQ shared memory resources 559 Shared memory on AIX . . . . . . . . . . 560 . 525 . 527 Contents v
Chapter 15. WebSphere MQ and UNIX Process Priority . . . . . . . . . . 561 Index . . . . . . . . . . . . . . . 569 Sending your comments to IBM . . . 585 Chapter 16. Common Criteria . . . . 563 Notices . . . . . . . . . . . . . . 565 vi WebSphere MQ: System Administration Guide
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. Queues, messages, and applications . . . . 29 Extract from an MQSC command file . . . . 33 Extract from an MQSC command report file 34 Example script for running MQSC commands from a batch file . . . . . . . . . . . 35 Typical output from a DISPLAY QMGR command . . . . . . . . . . . . . 37 Typical results from queue browser . . . . 42 Remote administration using MQSC commands . . . . . . . . . . . . . 60 Setting up channels and queues for remote administration . . . . . . . . . . . 61 Example of a WebSphere MQ configuration file for UNIX systems . . . . . . . . . . 96 Example queue manager configuration file for WebSphere MQ for UNIX systems . . . . . 98 Sample XAResourceManager entry for DB2 on UNIX platforms . . . . . . . . . 166 Sample XAResourceManager entry for Oracle on UNIX platforms . . . . . . . . . 169 Sample XAResourceManager entry for Informix on UNIX platforms . . . . . . 171 Example contents of SYBASE/ SYBASE OCS/xa config . . . . . . . 172 Sample XAResourceManager entry for Sybase on UNIX platforms . . . . . . . . . 173 Sample XAResourceManager entries for multiple DB2 databases . . . . . . . . 174 Sample XAResourceManager entries for a DB2 and Oracle database . . . . . . . 174 Sample dspmqtrn output . . . . . . . 177 Copyright IBM Corp. 1994, 2009 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. Commented- out XAResourceManager stanza on UNIX systems . . . . . . . . . . Two-computer MSCS cluster . . . . . . Checkpointing . . . . . . . . . . . Checkpointing with a long-running transaction . . . . . . . . . . . . Sample WebSphere MQ error log . . . . . Sample WebSphere MQ for Windows trace Sample WebSphere MQ for HP-UX trace Sample WebSphere MQ for Solaris trace Sample WebSphere MQ for Linux trace Sample WebSphere MQ for AIX trace Sample WebSphere MQ for AIX trace Sample WebSphere MQ for Windows First Failure Symptom Report . . . . . . . . FFST report for WebSphere MQ for UNIX systems . . . . . . . . . . . . . Sample com.ibm.mq.commonservices properties file . . . . . . . . . . . Understanding services, components, and entry points . . . . . . . . . . . . UNIX authorization service stanzas in qm.ini Name service stanzas in qm.ini (for UNIX systems) . . . . . . . . . . . . . Default directory structure (UNIX systems) after a queue manager has been started . . . Using the File Transfer Application to send files between remote queue managers . . . Using the File Transfer Application to send files between a queue manager and a remote client . . . . . . . . . . . . . . 179 202 221 222 253 256 258 259 260 261 264 266 268 271 393 400 404 532 545 547 vii
viii WebSphere MQ: System Administration Guide
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. Categories of control commands . . . . . 19 User rights required to launch AMQMSRVN 82 List of possible ISO CCSIDs. . . . . . . 100 Default outstanding connection requests (TCP) . . . . . . . . . . . . . . 116 Default outstanding connection requests (SPX) 117 Security authorization needed for MQCONN calls. . . . . . . . . . . . . . . 142 Security authorization needed for MQOPEN calls. . . . . . . . . . . . . . . 142 Security authorization needed for MQPUT1 calls. . . . . . . . . . . . . . . 142 Security authorization needed for MQCLOSE calls. . . . . . . . . . . . . . . 143 What happens when a database server crashes. . . . . . . . . . . . . . 158 What happens when an application program crashes. . . . . . . . . . . . . . 159 XA switch function pointers. . . . . . . 160 Summary of XA function calls . . . . . . 181 XA switch load file names . . . . . . . 183 Alternative 64-bit XA switch load file names 183 64-bit transaction managers that require the alternate 64-bit switch load file. . . . . . 184 Essential code for CICS applications: XA initialization routine . . . . . . . . . 186 CICS task termination exits . . . . . . . 189 Log overhead sizes (all values are approximate). . . . . . . . . . . . 223 Queue manager error log directory . . . . 251 System error log directory . . . . . . . 251 Client error log directory. . . . . . . . 252 How to read railroad diagrams . . . . . 274 Specifying authorities for different object types . . . . . . . . . . . . . . 305 Specifying authorities for different object types . . . . . . . . . . . . . . 358 . . . . . . . . . . . . . . . . 372 Copyright IBM Corp. 1994, 2009 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. . . . . . . . . . . . . . . . Options that can be used with gsk7cmd, runmqckm , and gsk7capicmd . . . . . Installable service components summary Example of entry-points for an installable service . . . . . . . . . . . . . System and default objects: queues . . . System and default objects: topics. . . . System and default objects: channels System and default objects: authentication information objects. . . . . . . . . System and default objects: listeners . . . System and default objects: namelists System and default objects: processes System and default objects: services . . . Objects created by the Windows default configuration application. . . . . . . Default values of SYSTEM.BASE.TOPIC WebSphere MQ for Windows directory structure . . . . . . . . . . . . Content of a \queue-manager-name\ folder for WebSphere MQ for Windows . . . . Default content of a /var/mqm/qmgrs/qmname/ directory on UNIX systems . . . . . . File Transfer Application command files Queue manager commands . . . . . . Commands for command server administration . . . . . . . . . . Commands for authority administration Cluster commands . . . . . . . . . Authentication information commands Channel commands . . . . . . . . Listener commands . . . . . . . . Namelist commands . . . . . . . . Process commands . . . . . . . . . Queue commands . . . . . . . . . Service commands . . . . . . . . . Other commands . . . . . . . . . . 372 . 387 392 . 398 . 523 . 524 524 . 525 . 525 525 525 . 525 . 526 527 . 529 . 530 . 532 551 . 553 . 553 554 . 554 554 . 555 . 555 . 555 . 556 . 556 . 557 . 557 ix
x WebSphere MQ: System Administration Guide
Chapter 1. Introduction Introduction to WebSphere MQ This section introduces WebSphere MQ Version 7 from an administrator’s perspective, and describes the basic concepts of WebSphere MQ and messaging on UNIX and Windows systems. It contains these sections: v v v v v v v “WebSphere MQ and message queuing” “Messages and queues” on page 2 “Objects” on page 3 “Clients and servers” on page 10 “Extending queue manager facilities” on page 11 “Security” on page 12 “Transactional support” on page 13 For WebSphere MQ on z/OS system administration information, see the WebSphere MQ z/OS System Administration Guide; for WebSphere MQ on i5/OS system administration information, see the WebSphere MQ on i5/OS System Administration Guide. WebSphere MQ and message queuing WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. For example, HP-UX and z/OS applications can communicate through WebSphere MQ for HP-UX and WebSphere MQ for z/OS respectively. The applications are shielded from the mechanics of the underlying communications. WebSphere MQ implements a common application programming interface known as the message queue interface (or MQI) wherever the applications run. This makes it easier for you to port application programs from one platform to another. The MQI is described in detail in the WebSphere MQ Application Programming Reference. Time-independent applications With message queuing, the exchange of messages between the sending and receiving programs is independent of time. This means that the sending and receiving application programs are decoupled; the sender can continue processing without having to wait for the receiver to acknowledge receipt of the message. The target application does not even have to be running when the message is sent. It can retrieve the message after it is has been started. Message-driven processing When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. Copyright IBM Corp. 1994, 2009 1
Messages and queues Messages and queues are the basic components of a message queuing system. What is a message? A message is a string of bytes that is meaningful to the applications that use it. Messages are used to transfer information from one application program to another (or between different parts of the same application). The applications can be running on the same platform, or on different platforms. WebSphere MQ messages have two parts: v The application data. The content and structure of the application data is defined by the application programs that use it. v A message descriptor. The message descriptor identifies the message and contains additional control information, such as the type of message and the priority assigned to the message by the sending application. The format of the message descriptor is defined by WebSphere MQ. For a complete description of the message descriptor, see the WebSphere MQ Application Programming Reference manual. Message lengths: The default maximum message length is 4 MB, although you can increase this to a maximum length of 100 MB (where 1 MB equals 1 048 576 bytes). In practice, the message length might be limited by: v The maximum message length defined for the receiving queue v The maximum message length defined for the queue manager v The maximum message length defined by the queue v The maximum message length defined by either the sending or receiving application v The amount of storage available for the message It might take several messages to send all the information that an application requires. How do applications send and receive messages?: Application programs send and receive messages using MQI calls. For example, to put a message onto a queue, an application: 1. Opens the required queue by issuing an MQI MQOPEN call 2. Issues an MQI MQPUT call to put the message onto the queue Another application can retrieve the message from the same queue by issuing an MQI MQGET call For more information about MQI calls, see the WebSphere MQ Application Programming Reference. What is a queue? A queue is a data structure used to store messages. 2 WebSphere MQ: System Administration Guide
Each queue is owned by a queue manager. The queue manager is responsible for maintaining the queues it owns, and for storing all the messages it receives onto the appropriate queues. The messages might be put on the queue by application programs, or by a queue manager as part of its normal operation. WebSphere MQ Version 7.0 supports queues over 2 GB in size; “Enabling large queues” on page 43 discusses this in more detail. For information about planning the amount of storage you need for queues, see the Quick Beginnings guide for your platform, or visit the WebSphere MQ Web site for platform-specific performance reports: s/ Predefined queues and dynamic queues: Queues can be characterized by the way they are created: v Predefined queues are created by an administrator using the appropriate MQSC or PCF commands. Predefined queues are permanent; they exist independently of the applications that use them and survive WebSphere MQ restarts. v Dynamic queues are created when an application issues an MQOPEN request specifying the name of a model queue. The queue created is based on a template queue definition, which is called a model queue. You can create a model queue using the MQSC command DEFINE QMODEL. The attributes of a model queue (for example, the maximum number of messages that can be stored on it) are inherited by any dynamic queue that is created from it. Model queues have an attribute that specifies whether the dynamic queue is to be permanent or temporary. Permanent queues survive application and queue manager restarts; temporary queues are lost on restart. Retrieving messages from queues: Suitably authorized applications can retrieve messages from a queue according to the following retrieval algorithms: v First-in-first-out (FIFO). v Message priority, as defined in the message descriptor. Messages that have the same priority are retrieved on a FIFO basis. v A program request for a specific message. The MQGET request from the application determines the method used. Objects Many of the tasks described in this book involve manipulating WebSphere MQ objects. The object types are queue managers, queues, process definitions, namelists, channels, client connection channels, listeners, services, and authentication information objects. The manipulation or administration of objects includes: v Starting and stopping queue managers. v Creating objects, particularly queues, for applications. v Working with channels to create communication paths to queue managers on other (remote) systems. This is described in detail in WebSphere MQ Intercommunication. Chapter 1. Introduction 3
v Creating clusters of queue managers to simplify the overall administration process, and to balance workload. This book contains detailed information about administration in the following chapters: v “An introduction to WebSphere MQ administration” on page 13 v “Managing queue managers” on page 19 v “Administering local WebSphere MQ objects” on page 28 v “Automating administration tasks” on page 54 v “Administering remote WebSphere MQ objects” on page 57 v “Administration using the WebSphere MQ Explorer” on page 71 Object names The naming convention adopted for WebSphere MQ objects depends on the object. Each instance of a queue manager is known by its name. This name must be unique within the network of interconnect
Stopping queue managers in WebSphere MQ for Windows.537 Stopping queue managers in WebSphere MQ for UNIX systems .538 Removing queue managers manually .538 Removing queue managers in WebSphere MQ for Windows .539 Removing queue managers in WebSphere MQ for UNIX systems .540 Chapter 12.
In the three volumes of the IBM WebSphere Portal V4.1 Handbook, we cover WebSphere Portal Enable and Extend. The IBM WebSphere Portal V4.1 Handbook will help you to understand the WebSphere Portal architecture, how to install and configure WebSphere Portal, how to administer portal pages using WebSphere Portal; it will also discuss the
WebSphere 8. Welcome to the F5 Deployment Guide for IBM WebSphere. This document provides guidance for deploying the BIG-IP Local Traffic Manager (LTM) with IBM WebSphere 8. The BIG-IP system can optimize IBM WebSphere at many layers: in front of the IBM HTTP . Servers, between HTTP Servers and WebSphere Application Servers, or to eliminate .
Figure 2 WebSphere Manages the Middle Tier in a Three-Tier Model One of the WebSphere products, WebSphere Portal, manages a variety of enterprise applications and supports application development and delivery. In the Lean Retail WebSphere Solution, content development and document management functions of WebSphere Portal were tested.
Unit Objectives 2 This unit was designed to enable you to: Start a development project that implements WebSphere Commerce V7. Describe the Runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce by using both
Download and install WebSphere MQ 2. Configure WebSphere MQ 3. Install OEG Gateway . Oracle Enterprise Gateway 6 / 30 4. Configure Gateway to send messages to WebSphere MQ 5. Configure Gateway to listen for messages from WebSphere MQ queue 6. Test Setup 2. Setting up the WebSphere MQ environment
WebSphere Application Server WebSphere MQ Use the most appropriate protocol C .net Java C JMS COBOL Java Jacl JMS Jython Web-Sockets C# HTTP WebSphere Application Server is a fully compliant Java Enterprise Edition (JEE) application server. The Java Message Service (JMS) is the JEE application messaging protocol. WebSphere MQ provides a fully
IBM WebSphere Portal Version 5 Family Enable WebSphere Application Server IBM HTTP server WebSphere Portal Server Out-of-the-Box Portlets Collaboration Services API Portal Toolkit WebSphere Translation Server WebSphere Studio Site Developer Content Management Personalization Portal Document Manager
The Four Color Personalities For MLM: The Secret Language For Network Marketing By Tom "Big Al" Schreiter, Page: Intro & Details Instant bonding, instant communication, and how to get your network marketing prospects to fully understand and act on your message fun! This is the most fun of the 25 skills of network marketing. Our prospects have a different point-of-view than ours. So how do we .
