You can use security exit programs to verify that the partner at the other end of the channel is genuine.
When you start the Message Brokers Toolkit, it does not invoke a security exit to monitor its connection to the Configuration Manager by default. If you want to protect access to the Configuration Manager from client programs, you can use the WebSphere MQ channel security exit facility. This works in a standard way for the Configuration Manager end of the connection. You can find information about how to set up the security exit at the server end of the connection in the WebSphere MQ Intercommunication manual.
If you want to use a security exit, define when creating a new domain within the Domains view of the Message Brokers Toolkit to provide connection security. These security exits are standard WebSphere MQ security exits, written in Java, and implementing the WebSphere MQ exit interface.
For an overview of security exits, refer to the section "Channel security exit programs" in the chapter "Channel exit programs" in the WebSphere MQ Intercommunication manual on the WebSphere MQ library Web page.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ap12500_ |