Preparing a queue manager for each broker server

Each message broker requires its own queue manager. Create and customize one queue manager for each broker server. If any SAG servers or application servers are to use queue managers that are different from those used by the broker servers, create and customize those queue managers as well. It is recommended that you give each queue manager a name of the form MQMx, where x represents a number from 1 to 9.

If your FTM SWIFT instance is to use more than one queue manager, these queue managers must all be part of the same IBM MQ cluster. For information about implementing IBM MQ clusters, see the IBM Documentation for IBM MQ.

To prepare a queue manager:

Log in as an MQ administrator (for example, uwmqadm1). The access rights of this user are described in Table 1.
Create the queue manager by issuing the following command:
```
crtmqm -u SYSTEM.DEAD.LETTER.QUEUE qm_name
```
where qm_name represents the name of the queue manager.
Enable remote connections to the queue manager. For example, to automatically start the IBM MQ listener with the queue manager, use the following runmqsc command:
```
ALTER LISTENER(SYSTEM.DEFAULT.LISTENER.TCP) TRPTYPE(TCP) PORT(port_no) CONTROL(QMGR)
```
where port_no is the number of the TCP/IP port where the queue manager will listen. The default is 1414.
Because most of the message flows interact with a database, and because these interactions must be coordinated with other actions within the message flow, you must, for the queue manager used by the message broker, define an XAResourceManager stanza for each of the databases involved. To do this:
1. Create the necessary links to the Db2 switch load (db2swit) file that is provided by IBM Integration Bus:
  1. Log in as the root user
  2. Run mqsiprofile by issuing the following command (where brk_install_dir is the installation directory of the message broker product):
    - If you use IBM Integration Bus V10:
      . brk_install_dir/server/bin/mqsiprofile
    - Otherwise:
      . brk_install_dir/bin/mqsiprofile
  3. Issue the following mqsimanagexalinks command:
```
mqsimanagexalinks create DB2 brk_install_dir db2_install_dir/version
```
    where:
    
    brk_install_dir
    
    The installation directory of the message broker product.
    
    db2_install_dir
    
    The Db2 installation directory.
    
    version
    
    The Db2 version.
    
    For example:
```
mqsimanagexalinks create DB2 /opt/IBM/iib-10.0.0.7 /opt/IBM/db2/V11.1
```
    For information about the mqsimanagexalinks command, see IBM Documentation for Message Broker.
2. Append the following text to the /var/mqm/qmgrs/qm_name/qm.ini file:
```
XAResourceManager:
Name=XA_runtime_dsn
SwitchFile=db2swit
XAOpenString=runtime_dsn,brk_admin,brk_passwd,toc=t
ThreadOfControl=THREAD
```
  where:
  
  runtime_dsn
  
  The data source name of the run time database used by FTM SWIFT.
  
  brk_admin
  
  The user ID of the message broker administrator.
  
  brk_passwd
  
  The password of the message broker administrator.
3. Define the following environment variable or append it in the IBM MQ administrator profile:
```
export DB2INSTANCE=db2_inst_name
```
  where db2_inst_name is the name of the Db2 instance.