As you know, there are some security functions in WebSphere MQ that require an exit. By now everyone should be familiar with BlockIP2, the well known channel security exit. But there are a couple of other requirements that a channel exit can’t meet. In this post I’ll describe what those are and post some specs [...]
Entries Tagged as 'design'
WANTED DEAD OR ALIVE: WMQ Security exits
May 15th, 2009 2 Comments
Tags: Best Practices · design · security · WebSphere MQ · WMQ · WMQ Security
Must-read article – Secure Software: ‘See No Evil’ is Not a Strategy
January 23rd, 2009 No Comments
Given that software currently enables or imperils most aspects of our buying, selling, and communicating, it is time that responsible people acknowledge that this is a massive problem, and stop looking in the opposite direction. “See No Evil” is not a strategy. [Read the full article on Network World.] Nice to see this sentiment showing [...]
Tags: Architecture · design · development · News · security · software · vulnerabilities
Question about benefits of WMQ Clustering
July 16th, 2008 No Comments
Here’s an email question I received today and my response: Does IBM have any write up for the advantage of using mq clustering vs non clustering setup? I am trying to get our application teams on board with using clustering. I was going to setup all our test servers in a test cluster and add [...]
Tags: Admin · Architecture · cluster · Consulting · design · Recommended Practices · WebSphere MQ · WMQ
Running a standalone Java application on WebSphere MQ V6.0
July 8th, 2008 No Comments
In October 2006 I updated an article of Bobby Woolf’s articles Developing a standalone Java application for WebSphere MQ. The article was updated to cover WMQ v6, JMS 1.1 and include a discussion of WMQ client vs. bindings mode connections. The result was Running a standalone Java application on WebSphere MQ V6.0. I don’t have [...]
Tags: Admin · articles · commentary · design · developerWorks · development · Errata · Publications · WebSphere MQ · WMQ