To create the JMS bindings file, you use the JMSAdmin application. This section provides a summary of how to create the JMS bindings file. For complete information on how to use the JMSAdmin application, refer to your WebSphere MQ documentation.
The following steps describe how to create the JMS bindings file:
JMSAdmin
def ctx(contextName)
chg ctx(contextName)
where contextName is the context you created in the previous step.
def qcf(connectionFactoryName) qmgr (queueManagerName) tran(client) chan(javaChannelName) host (MQHostName) port (MQport)
where:
def q(queueAliasName) qmgr (queueManagerName) queue (queueName)
end
The bindings file is created in a subfolder of the folder configured in the PROVIDER_URL field of the JMSAdmin.config file. The bindings file has the following name:
.bindings
The name of the subfolder is the name you chose for your JMS context.
Figure 32 shows the creation of a sample JMS configuration.
Figure 32. Commands to create sample JMS configuration
def ctx(JMS) change ctx(JMS)
define qcf(WBICHub) qmgr(bcg.queue.manager) tran(CLIENT) chan(java.channel) host(127.0.0.1) port(1414)
define q(inQ) queue (JMSIN) qmgr(bcg.queue.manager) define q(outQ) queue (JMSOUT) qmgr(bcg.queue.manager)
The commands in Figure 32, issued from within the JMSAdmin application, create the following JMS objects:
When these commands are complete, the JMSAdmin application has created a .bindings file in the following directory:
C:/filesender/config/jms