What's Hot in the WebSphere MQ World? (Part 3)
Gregory(Greg)Bowman 1000007M77 Visits (12515)
It has been a while since I wrote about what is hot in the WebSphere MQ (WMQ) support world and there have been quite a few new and helpful documents or articles that have been written or updated since the last time I wrote about what was hot. In case you did not read the previous blogs that I wrote on this topic here are links to the first 2 blog articles because the items in those articles are still relevant today. Many of those items are timeless. They cover topics that someone, somewhere in the world is going to be dealing with today.
Now, let's get to the new stuff! The WebSphere MQ team has developed some new articles and technotes that deal with a few areas that have been getting a lot of attention in the past few months. Because they are drawing a lot of attention, I think you are likely to find one or more of these will help you with some issues you are dealing with now or perhaps will be dealing with soon. Here are 5+ topics that relate to some hot spots in WMQ and the recent articles the WMQ support team developed to address them. Note that these are in no particular order.
1. The WebSphere MQ CHLAUTH parameter
The CHLAUTH parameter, which is short for Channel Authentication, is relatively new in WebSphere MQ and a lot of people are still trying to get a handle on exactly how it works and how to best use it for their different environments. Morag Hughson is one of the WMQ developers who is quite familiar with CHLAUTH and she has written a series of articles here in the WebSphere and CICS Support Blog to try to help everyone better understand CHLAUTH and the ways you can and should be using it.
Bonus: Here is another blog entry that Morag contributed which is not technically dealing directly with CHLAUTH but it is related and could prove quite useful:
2. Troubleshooting Java/JMS SSL Configurations
The majority of WMQ SSL setup issues deal with Java™ or JMS connections so the WMQ support team put together a technote to outline most of the common configuration errors, identify the symptoms for that type of problem and then list the most common solution to resolve that error. I wrote a short blog article to introduce that when it first was published, "Web
3. WebSphere MQ Java or JMS "Bindings" problems (mqjbnd)
When WMQ Java or JMS applications attempt to connect to a queue manager your Java application environment needs to be able to find the WebSphere MQ native libraries. The setup of this environment has long been a thorn in the side of many customers and there have been a lot of items written to try to help address the different symptoms and problems that surround that setup. Here are several technotes that have been written or updated recently to address problems in that general area.
4. Coexisting versions of WebSphere MQ on the same machine
When IBM first announced that WMQ V7.1 was adding the ability to allow multiple versions of WMQ to live together in harmony on the same machine, it was sweet music to the ears of many people. It was an instant hit and has been near the top of the charts ever since and we really like singing the praises of this hit. Recently Angel Rivera from the WMQ support team delivered a webcast discussing the topic and it was quite well received. In case you missed the webcast or in case you want to go back and hear it again or use it as a reference tool, here is the link to a replay of that popular webcast.
We have some previous webcasts on this same topic that were also big hits. These webcasts were delivered by Barry Robbins, Justin Fries & Rich Montjoy from the WMQ support team last year. They are a two part series introducing the topic and detailing it's configuration and use.
5. Automatic Client Reconnect
Network reliability has improved over the years but even with those improvements, there are always going to be some problems which, from time to time, will cause your WMQ clients to lose their connection to a queue manager. In those situations, it would be nice to have a way to cause those clients to attempt to reconnect to the queue manager without you or your developers having to write any special code in your applications. This is where the Automatic Client Reconnect feature, introduced in WMQ V7.0.1, can be your friend. Angel Rivera, the same fellow who talked to us about coexisting versions of WMQ, delivered a great webcast on this topic a little earlier this year. Here is a link to a replay of that webcast, so you can enjoy it any time you would like to listen to it or review the presentation materials.
Bonus: Here are a few additional recent technotes written on the topic of automatic client reconnection:
That covers the main topics that I wanted to talk about in this article but if you have any other topics you would like to have us discuss or if you just want to leave feedback in general, please leave a comment below. "Remember, We Still Love Your Feedback!"