In this blog posting, I will show how to use a send the same message to multiple queues at the same time. In this example, Universal File Mover (UFM) will connect to the queue manager in “client mode”.
In this example, the following servers are used but they only have WebSphere MQ (WMQ) Client installed (no queue managers):
– aix002 is an AIX server with WMQ Client and UFM software installed
– linux002 is a Linux server with WMQ Client and UFM software installed
In this example, the following queue managers are used:
– MQA1 is a queue manager residing on a AIX (aix001) server (sender)
– MQL1 is a queue manager residing on a Linux (linux001) server (receiver)
– TEST.LINUX.QL, TEST.LINUX.QL2, TEST.LINUX.QL3 and TEST.LINUX.QL.BK are local queues defined in queue manager MQL1 (receiver)
– MQL1 is a queue manager alias defined in queue manager MQA1 (sender) if your XMIT queue is not called MQL1
If you do not know how to define/setup communication between 2 queue managers then follow the instructions in this blog posting:
https://www.capitalware.com/rl_blog/?p=509
Step #1: On the linux002 server, create a file in the mq directory called mql1.xml and copy the following into the file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE UFM_MQ SYSTEM "UFM_MQ.dtd">
<UFM_MQ>
<QMgrName>MQL1</QMgrName>
<QueueName>TEST.LINUX.QL</QueueName>
<Hostname>linux001</Hostname>
<ChannelName>SYSTEM.DEF.SVRCONN</ChannelName>
<Port>1414</Port>
<UserID>tester</UserID>
</UFM_MQ>
The mql1.xml (UFM_MQ XML) file describes how to connect to the remote MQL1 queue manager on server linux001. The connection will use UserID of tester. If you do not have that UserID defined on the linux001 server then use a UserID that is defined.
Step #2: On the linux002 server, in the UFM install directory, create a file called ufm_receive_test_3.xml and copy the following into the file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE UFM_Workflow SYSTEM "UFM_Workflow.dtd">
<UFM_Workflow>
<Actions>
<MQReceive getwithconvert="Y" run="D">
<MQ>
<MQFile>mql1.xml</MQFile>
<BackOutQName>TEST.LINUX.QL.BK</BackOutQName>
</MQ>
<Default>
<Directory override="Y">/home/roger/UFM/</Directory>
</Default>
</MQReceive>
</Actions>
</UFM_Workflow>
When UFM is started, it will run as a daemon (run=”D”) and use a backout queue called TEST.LINUX.QL.BK just in case there is an issue with a message. UFM will use ‘get with convert’ option when retrieving the messages. UFM will override the message’s specified directory and use the one provided. Either create /home/roger/UFM/ directory on your Linux server or use a directory that already exist on your Linux server.
Step #3: On the linux002 server, start UFM to receive the file transfers:
./ufm.sh ufm_receive_test_3.xml &
Step #4: On the aix002 server, create a file in the mq directory called mqa1-dl.xml and copy the following into the file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE UFM_MQ SYSTEM "UFM_MQ.dtd">
<UFM_MQ>
<QMgrName>MQA1</QMgrName>
<DistributionList>
<QueueName qmgrname="MQL1">TEST.LINUX.QR</QueueName>
<QueueName qmgrname="MQL1">TEST.LINUX.QR2</QueueName>
<QueueName qmgrname="MQL1">TEST.LINUX.QR3</QueueName>
</DistributionList>
<Hostname>aix001</Hostname>
<ChannelName>SYSTEM.DEF.SVRCONN</ChannelName>
<Port>1414</Port>
<UserID>tester</UserID>
</UFM_MQ>
The mqa1-dl.xml (UFM_MQ XML) file describes how to connect to the remote MQA1 queue manager on server aix001 and use 3 queues in the distribution list. The connection will use UserID of tester. If you do not have that UserID defined on the aix001 server then use a UserID that is defined.
Step #5: On the aix002 server, create a file in the data directory called test.txt and put a simple text message in the file (i.e. This is a test message.)
Step #6: On the AIX server, in the UFM install directory, create a file called ufm_send_test_3.xml and copy the following into the file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE UFM_Workflow SYSTEM "UFM_Workflow.dtd">
<UFM_Workflow>
<Actions>
<MQSend delete="N" format="S">
<File>data/test.txt</File>
<MQ>
<MQFile>mqa1-dl.xml</MQFile>
</MQ>
<Remote>
<Directory>/var/mqm/</Directory>
</Remote>
</MQSend>
</Actions>
</UFM_Workflow>
When UFM is started, it will send the specified file to the 3 queues in the distribution list and mark the message’s MQMD format as ‘string’.
Step #7: On the aix002 server, start UFM to send the file:
./ufm.sh ufm_send_test_3.xml
UFM will start and put the file as a message to the specified queue then terminate.
Step #8: On the linux002 server, verify that the test file (i.e. test.txt) was put into the /home/roger/UFM/ directory or whatever directory you specified in the ufm_receive_test_3.xml file.
Step #9: Finally, we need to stop UFM daemon that is running on the linux002 server. In the UFM install directory, create a file called ufm_putquit_test_3.xml and copy the following into the file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE UFM_Workflow SYSTEM "UFM_Workflow.dtd">
<UFM_Workflow>
<Actions>
<MQPutQuit>
<MQ>
<MQFile>mql1.xml</MQFile>
</MQ>
</MQPutQuit>
</Actions>
</UFM_Workflow>
Step #10: On the linux002 server, run UFM with the MQPutQuit action:
./ufm.sh ufm_putquit_test_3.xml
This blog demonstrates how to use UFM at both the sender and receiver ends as MQ clients that connect to remote queue managers.
Regards,
Roger Lacroix
Capitalware Inc.
