Creating the configuration file for the IBM MQ Bridge to blockchain

Enter your queue manager and your blockchain network parameters to create the configuration file for the IBM® MQ Bridge to blockchain to connect to your IBM MQ and IBM Blockchain networks.

1. Run the bridge to create a configuration file.
   You need the parameters from your blockchain network credentials file and from your IBM MQ Advanced queue manager.

   runmqbcb -o config_file_name.cfg

   As the following example illustrates, the existing values are shown inside the brackets. Press Enter to accept existing values, press Space then Enter to clear values, and type inside the brackets then press Enter to add new values. You can separate lists of values (such as peers) by commas, or by entering each value on a new line. A blank line ends the list.

   Note: You cannot edit the existing values. You can keep, replace, or clear them.
2. Enter values for the connection to your IBM MQ Advanced queue manager.
   Minimum values that are needed for the connection are the queue manager name, the names of the bridge input and identity queues that you defined. For connections to remote queue managers, you also need MQ Channel and MQ Conname (host address and port where the queue manager is running). To use TLS for connecting to IBM MQ in step 4, you must use JNDI or CCDT and specify MQ CCDT URL or JNDI implementation class and JNDI provider URL accordingly.

   
   Connection to Queue Manager
   ---------------------------
   Queue Manager                        : [adv_qmgr_name]
   Bridge Input Queue                   : [APPL1.BLOCKCHAIN.INPUT.QUEUE]
   Bridge User Identity Queue           : [SYSTEM.BLOCKCHAIN.IDENTITY.QUEUE]
   MQ Channel                           : []
   MQ Conname                           : []
   MQ CCDT URL                          : []
   JNDI implementation class            : 
     [com.sun.jndi.fscontext.RefFSContextFactory]
   JNDI provider URL                    : []
   MQ Userid                            : []
   MQ Password                          : []
   

3. 13. Enter the Hyperledger Fabric server credentials for your network.
   Examples of what you should expect are shown in the following code:

   
   Fabric Server
   --------------
   Network configuration file           : []connection-tls.json
   Wallet                               : []
   User Name                            : []User1
   Certificate                          : []<path_to_user_certificate>
   Private Key                          : []<path_to_private_key>/private_key.pem
   Organisation                         : []Org1MSP
   

4. Enter certificate stores values for TLS connections.
   Leave this area blank if you have none.

   
   Certificate stores for MQ TLS connections
   ----------------------------------------
   Personal keystore                    : []
   Keystore password                    : []
   Trusted store for signer certs       : []
   Trusted store password               : []
   

5. Enter the path of the logfile where the bridge logs are to be written.

   
   Behaviour of bridge program
   ---------------------------
   Runtime logfile for copy of stdout/stderr : []bridgelog.log
   Number of logfiles                   : [3]
   Maximum size of each logfile (bytes) : [2097152] 
   

   Attention: Previously, details regarding the Peers, Orderers, and the Certificate Authority were stored in this bridge setup. However, this information is now stored in the Network Configuration File, which is linked to in the Hyperledger Fabric server section of the setup.