Tags

In the typical WebSphere MQ installation, both the MQ Server and the MQ Client features are installed. However, the MQ Client can be installed on a system where the MQ Server component is not installed, and no queue manager runs. In this configuration the MQ Client can do message queuing to one, or many queue managers that reside on different machines. If you have never used the WebSphere MQ Client feature and want to give it a try, here is a quick and easy way to configure an MQ Client to connect to a queue manager on an MQ Server. In this... [More]

Security is a hot topic these days and I'd like to explain the basic use of the mcauser attribute for controlling client access for WebSphere MQ. An inbound channel with a blank MCAUSER value will permit whatever is connecting to administer the local queue manager. To prevent this, some best practices include setting MCAUSER to the ID of the person using the respective channels, and give them the required access. The MCAUSER attribute of the SYSTEM.DEF.SVRCONN should be set to something that has no authorities on the server. Access control in... [More]

PASSWORD PROTECTION We've seen some interesting issues come up over the last several months. Many of these were related to security on all platforms. On z/OS some issues involving ICSF came to light this year. ICSF is used on the z/platform, among other things, to provide entropy that improves password protection. In particular users had experienced issues with version 8 clients that connect using the MQ Explorer where password protection was being invoked. To level set, when password protection is attempted, at version 8 MQ will... [More]