Architectural Insights for Deploying WMQ

72bc51c957717159d35441bc03f0a508delicious

Architecture and Deployment for WMQ 7WebSphere MQ 7 is an impressive piece of software.  Not only is it easy to install on most platforms, but it is also easy to setup with default options.  However, if we look at the options offered to us while setting up WebSphere MQ and Queue Managers, we will see a lot of flexibility that can help take advantage of a user’s environment.  Two options that I would like go over specifically are:


  • DataPath, and
  • LogPath

Specifying the DataPath is as easy as passing -md flag to crtmqm along with the directory path.  Now a big use of the DataPath is when using MultiInstance Queue Managers. When setting up MultiInstance Queue Managers, you create multiple Queue Managers on different systems all having the same name, and the same DataPath location.  In doing this you ensure all instances will share the same data. Of course we need to make sure only one instance of the Queue Manager is up and running at a time.  With this functionality, no matter what machine is down you can always have your Queue Manager up and running.

Besides using DataPath for MultiInstance Queue Managers, it can also be used for finer control of your MQ environment.  You can have your Queue Manager data written to a SAN or a High Availability Disk so it can be used to make sure data is safe in the event an issue with the local system arises.  Or perhaps you just want to keep the data away from the rest of the local file system; the choice and flexibility are up to you.

LogPath can be specified with the -ld flag to crtmqm along with the directory path. This can be used just like the DataPath when dealing with MultiInstance Queue Managers, but it can also be used for finer control on an individual Queue Manager. Many times in an environment we don’t want our logs and actual data in the same location, or even on the same disk.  While Queue Manager data might be critical, the same can’t be said for our logs.  A good option is to make sure the log path is in a separate partition or separate drive altogether.  That way we can be sure the logs will never interfere with our data, no matter how full they might get, and we can avoid having a disk full of alerts that is also affecting the processing performance of our queues.

One thing to keep in mind when specifying DataPath and LogPath is that WebSphere MQ will not set the user/group authorities automatically.  This step will have to be done manually.

DataPath and LogPath are just two of the options we have that give us finer control over our Queue Managers.  Reading over the documentation for WebSphere MQ you will find plenty of other options that can help you take advantage of WebSphere MQ in your own environment.

One thought on “Architectural Insights for Deploying WMQ

Leave a Reply

Your email address will not be published. Required fields are marked *