Top 15 - Websphere MQ best practices

Design

• Use short names for queue managers and MQ objects
• Always assign a dead letter queue (DLQ) to the queue manager
• Use standards like JMS whenever possible
• Build with performance in mind
• Avoid location assumptions and fixed queue names in programs
• When feasible, cluster your MQ servers
• Design infrastructures with fewer queue managers with more queues

Build

• Capture completion and reason codes in all application MQI calls
• Code applications to continually process messages
• Close and disconnect connections properly
• Be aware of the different features of various MQ clients

Run

• Use security best practices
• Restrict remote administrative authority using SYSTEM.ADMIN.SVRCONN channels on production-level (restricted-access) boxes
• Do not use the sample get/put utilities for production purposes
• Use runmqlsr in lieu of inetd listener
• Use SupportPacs to extend MQ functionality

Maintain

• When not using third-party configuration tools, automate all configuration and changes via MQSC scripts
• Use the appropriate logging mechanism
• Configure automated maintenance of queue managers
• Schedule and apply fix packs on a regular basis

http://www.ibm.com/developerworks/websphere/library/techarticles/0807_hsieh/0807_hsieh.html?ca=dnb-wmq091808