Start by making sure you have identical software installations on each computer in the cluster, as described in WebSphere MQ for Windows, V6.0 Quick Beginnings.
For successful MSCS security, follow these guidelines:
Remember that an account that is local to one computer does not exist on the other one. Even if you create an account with the same name on the other computer, its security identifier (SID) is different, so, when your application is moved to the other node, the permissions do not exist on that node.
During a failover or move, WebSphere MQ MSCS support ensures that all files that contain queue manager objects have equivalent permissions on the destination node. Explicitly, the code checks that the Administrators and mqm groups, and the SYSTEM account, have full control, and that if Everyone had read access on the old node, that permission is added on the destination node.
You can use a domain account to run your WebSphere MQ Service. Make sure that it exists in the local mqm group on each computer in the cluster.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
mscssec |