Security scenarios

A set of scenarios that demonstrate applying security to different configurations.

The available security scenarios are described in the following subtopics:

Security scenario: two queue managers on z/OS
In this scenario, an application uses the MQPUT1 call to put messages to queues on queue manager QM1. Some of the messages are then forwarded to queues on QM2, using TCP and LU 6.2 channels. The TCP channels can either use SSL/TLS or not. The application could be a batch application or a CICS® application, and the messages are put using the MQPMO_SET_ALL_CONTEXT option.
Security scenario: queue sharing group on z/OS
In this scenario, an application uses the MQPUT1 call to put messages to queues on queue manager QM1. Some of the messages are then forwarded to queues on QM2, using TCP and LU 6.2 channels. The application is a batch application, and the messages are put using the MQPMO_SET_ALL_CONTEXT option.
Server-to-server message channel interception example configurations
Server-to-server message channel interception requires configuration of channel definitions, as well as Advanced Message Security policies, to ensure that inbound and outbound messages can be correctly protected or unprotected. The configuration varies depending on whether the channel is inbound or outbound.
Connecting two queue managers using SSL/TLS
Secure communications that use the TLS cryptographic security protocols involve setting up the communication channels and managing the digital certificates that you will use for authentication.
Connecting a client to a queue manager securely
Secure communications that use the TLS cryptographic security protocols involve setting up the communication channels and managing the digital certificates that you will use for authentication.

Parent topic: IBM MQ Scenarios

Related tasks

Setting up security on z/OS