Handshaking properties

The following table defines the properties for handshaking that need to be added to the Gateway configuration.
Table 1. Handshaking configuration properties
Keyword Values or example Description
handshakeEnabled true|false Controls whether handshaking is enabled or disabled.
handshakeExpectedByDefaultWait 300000 The time, in milliseconds, that is added to the current time to indicate when the incoming transmission is to be expected. The default value is 300,000 milliseconds or 5 minutes.
handshakeMQUserId   The user ID used to access the queues.
handshakeMQPassword   The password for the user ID used to access the queues.
handshakeMQQmgrName QM1 The name of the Gateway queue manager.
handshakeMQSendQueue GWOUTQ The name of the Gateway remote queue that is used for sending messages.
handshakeMQReceiveQueue FXH.GATEWAY.INPUT.QUEUE The name of the Gateway local queue used to receive messages.
handshakeMQKeyStore C:/ssl/gateway.jks The location of the SSL keystore file. It is required only if SSL is being used.
handshakeMQKeyStoreFormat PKCS12 Format of the keystore file. The allowed values are JKS or PKCS12. The default value is PKCS12.
handshakeMQKeyStorePassword password The password for the SSL keystore. It is required only if SSL is being used.
handshakeMQTrustStore C:/ssl/gateway.jks The location of the SSL trust store file. It is required only if SSL is being used.
handshakeMQTrustStoreFormat PKCS12 Format of trust store file. The allowed values are JKS or PKCS12. The default value is PKCS12.
handshakeMQTrustStorePassword password The password for the SSL trust store. It is required only if SSL is being used.
handshakeReplyToQueueAlias CL1Response_qalias The alias value to use for the reply-to queue.

Configuring the client channel definition table (CCDT) file to connect to IBM MQ

All application pods connect to IBM® MQ by using a JSON formatted CCDT file that is called mq-ccdt.json. This JSON file contains the following parameters.
  • The channel name.
  • Client-connection-related parameters such as the host name, port number, and the queueManager name.
  • Transmission security parameters such as the cipherSpecification.
This JSON file cannot be edited, but you can use a configmap to configure values for all these parameters except the channel name.

Add your values for IBM MQ to the ftm-mq-<ftm-instance>-ccdt-config configmap in Red Hat® OpenShift®. The FTM operator uses the contents of this configmap to update the mq-ccdt.json file.