Sharing JMS connection information with external clients

After you have modified the JMS definitions file, JMS.def, the bindings file, .bindings, must be regenerated following a change and distributed to external clients.

  1. Open the JMS.def file located in /home/virtuser/soapolicyjmsdef/ and update the default (127.0.0.1) text, written as <Broker System Hostname/IPAddress> in the following example, with the hostname of the Message Broker system:
    $vi JMS.def 
    
    # Define a QueueConnectionFactory 
    # Only parameters being overridden from their default values 
    # are specified. 
    # This sets up a MQ client binding. 
    
    DEF QCF(QCF) + 
    TRANSPORT(CLIENT) + 
    QMANAGER(MB8QMGR) + 
    HOSTNAME(<Broker System Hostname/IPAddress>) + 
    PORT(2414) 
    
    # 
    
    DEF Q(REQUEST_IN) + 
    QUEUE(REQUEST_INQ) + 
    QMANAGER(MB8QMGR) 
    
    DEF Q(REPLY_OUT) + 
    QUEUE(REPLY_OUTQ) + 
    QMANAGER(MB8QMGR) 
    
    DEF Q(BACKOUT) + 
    QUEUE(SYSTEM.DEAD.LETTER.QUEUE) + 
    QMANAGER(MB8QMGR) 
    
    #Add new JNDI definition for jndi://<DESTINATION> routing message 
    # endpoint by replacing <DESTINATION> 
    
    <Destination MQ QueueName> values with actual values. 
    DEF Q(<DESTINATION>) + 
    QUEUE(<Destination MQ QueueName>) + 
    QMANAGER(MB8QMGR) 
    END 
  2. Run the following command to create the bindings definition file, located in /home/virtuser/JNDI-DIR/.bindings, that is used by the external remote MQ JMS client:
    $cd /home/virtuser/soapolicyjmsdef 
    $/opt/mqm/java/bin/JMSAdmin < /home/virtuser/soapolicyjmsdef/JMS.def 
  3. The generated /home/virtuser/JNDI-DIR/.bindings definition file is used by the remote JMS client to connect to the MQ JMS provider hosted on the Message Broker system.

Information Information

Feedback

Timestamp icon Last updated: Thursday, 3 July 2014
http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.soawmbwsrr.doc/topics/tsoa_distribute.htm