When MQJExplorer is used to connect to a remote queue manager, by default, the queue manager will grant the connection and the user will be able to perform actions. This is exactly the same semantics as the IBM supplied MQExplorer tool for Windows.
In a test environment, this is usually sufficient but in a production environment, this can be a serious exposure. To resolve this issue, MQSeries architects the concept of a pair of security exits. These are code modules which plug-in at both the MQSeries queue manager and the application asking for service. The security exits can then communicate with each other to perform authentication to ensure that the user has sufficient privileges in order to connect.
MQJExplorer provides both the client side security exit as well as a server side exit that may be configured into the queue manager.
<TBC - Function tested and working, still to document further>
Last Updated: 08/10/2001