The following table shows the switch profiles used to control access to WebSphere MQ resources.
| Type of resource checking that is controlled | Switch profile name |
|---|---|
| Alternate user security | qmgr-name.YES.ALTERNATE.USER.CHECKS |
| Connection security | qmgr-name.YES.CONNECT.CHECKS |
| Context security | qmgr-name.YES.CONTEXT.CHECKS |
| Process security | qmgr-name.YES.PROCESS.CHECKS |
| Queue security | qmgr-name.YES.QUEUE.CHECKS |
For example, if you wanted to perform process security checks on queue manager QM_nwb_magd820, you would define the following switch profile:
QM_nwb_magd820.YES.PROCESS.CHECKS
If you wanted to perform queue security checks on QM_nwb_magd820, you would define the following switch profile:
QM_nwb_magd820.YES.QUEUE.CHECKS
Generic switch profiles such as qmgr-name.YES.** are ignored by Enterprise Server
If the switch is not found, security checks will be performed by default, and messages will appear on the console.log as:
CASKC0033I WebSphere MQ !QM_nwb_magd820 SUBSYSTEM security switch set ON, profile 'QM_NWB_MAGD820.NO.SUBSYS.SECURITY' not found CASKC0034I WebSphere MQ !QM_nwb_magd820 CONNECTION security switch set ON, profile 'QM_NWB_MAGD820.NO.CONNECT.CHECKS' not found CASKC0034I WebSphere MQ !QM_nwb_magd820 PROCESS security switch set ON, profile 'QM_NWB_MAGD820.NO.PROCESS.CHECKS' not found CASKC0034I WebSphere MQ !QM_nwb_magd820 CONTEXT security switch set ON, profile 'QM_NWB_MAGD820.NO.CONTEXT.CHECKS' not found CASKC0034I WebSphere MQ !QM_nwb_magd820 QUEUE security switch set ON, profile 'QM_NWB_MAGD820.NO.QUEUE.CHECKS' not found CASKC0034I WebSphere MQ !QM_nwb_magd820 ALTERNATE security switch set ON, profile 'QM_NWB_MAGD820NO.ALTERNATE.USER.CHECKS' not found