Configuring the MQ connection
When you configure an SAG, use the amqc command to define an MQ connection. MQ connections contain information used to establish communication between an SAG and the FTM SWIFT services. For more information about MQ connections, see SWIFT Alliance Gateway: MQ Host Adapter Configuration Guide. For more information about the amqc command, see addMQConnection.
You can create only one MQ connection at a time. To connect an SAG to several queue managers, you must use an IBM MQ channel definition table that holds information about several IBM MQ connections. In this case you do not specify a value for the channel parameters 'ChannelName', 'TransportType', and 'ConnectionName' in the MQ connection. This forces the SAG to use the IBM MQ channel definition table.
- Because an SAG can have only one MQ connection at a time, there is no need to specify a name for an MQ connection when entering a command. FTM SWIFT internally uses the name DnfMqConnection when you create, update, read, and delete an MQ connection.
- You can use the IBM MQ Channel Definition Table (CDT) to configure dynamic MQ connections that enable a single SAG to work with several FTM SWIFT servers that belong to the same FTM SWIFT instance. How to do this is described in SWIFT Alliance Gateway: MQ Host Adapter Configuration Guide.
FTM SWIFT stores the MQ connection in its database. In order to configure the MQ connection in the SAG, you must approve and deploy it as described in Approving and deploying SAG configuration data. You can approve and deploy the MQ connection after you configured it, or after you finished the complete SAG configuration.
To configure an MQ connection, you must have the SagAdmin role in DNFSYSOU and the system configuration administrator (DniSA) role in SYSOU.