Design
Use short names for Qmgr and MQ Objects
Always assign a DLQ
Use standards like JMS where ever possible
Build with performance in mind
Avoid fixed queue names in programs
When feasible, cluster your MQ server
Few Qmgr with more queues
Build
Capture completion and reason code for all MQI calls
Code application to continually process messages
Close and disconnect cxn properly
Be aware of the different features of various MQ clients
Run
Use security best practices
Restrict remote adminintrative authority using SYSTEM.ADMIN.SVRCONN channel of production-level boxes
Do not use sample get and put utilities
Use runmqlsr in lieu of inetd listener
Use SupportPacs to extend MQ functionality
Maintain
When not using third party tool, automate configuration with runmqsc scripts
Use appropriate logging mechanism
Schedule and apply fix packs on a regular basis
http://www.ibm.com/developerworks/websphere/library/techarticles/0807_hsieh/0807_hsieh.html
Use short names for Qmgr and MQ Objects
Always assign a DLQ
Use standards like JMS where ever possible
Build with performance in mind
Avoid fixed queue names in programs
When feasible, cluster your MQ server
Few Qmgr with more queues
Build
Capture completion and reason code for all MQI calls
Code application to continually process messages
Close and disconnect cxn properly
Be aware of the different features of various MQ clients
Run
Use security best practices
Restrict remote adminintrative authority using SYSTEM.ADMIN.SVRCONN channel of production-level boxes
Do not use sample get and put utilities
Use runmqlsr in lieu of inetd listener
Use SupportPacs to extend MQ functionality
Maintain
When not using third party tool, automate configuration with runmqsc scripts
Use appropriate logging mechanism
Schedule and apply fix packs on a regular basis
http://www.ibm.com/developerworks/websphere/library/techarticles/0807_hsieh/0807_hsieh.html
No comments:
Post a Comment