Scribd
Upload
0 views

ca devtest ibm mq

This document outlines the steps to set up an IBM MQ Broker, including creating queue managers, queues, and channels, as well as sending and receiving messages using JMS and Native methods. Key steps include ensuring the installation is on a non-domain machine, configuring the queue manager, creating a channel, and adjusting user access policies. Additionally, it details the necessary JAR files for interaction and the process for sending messages through the IBM MQ Native Send Receive step.

Uploaded by

gshivamit
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0 views

ca devtest ibm mq

This document outlines the steps to set up an IBM MQ Broker, including creating queue managers, queues, and channels, as well as sending and receiving messages using JMS and Native methods. Key steps include ensuring the installation is on a non-domain machine, configuring the queue manager, creating a channel, and adjusting user access policies. Additionally, it details the necessary JAR files for interaction and the process for sending messages through the IBM MQ Native Send Receive step.

Uploaded by

gshivamit
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

CA SV - Steps to setup Queue Manager, Queue and Channel

on IBM MQ Broker and perform a JMS and Native


Send/Receive Step from Workstation
As part of working on a customer issue, I had to setup IBM MQ Broker and create some queue managers, queues and channels. There were
some hurdles in the way the default setup works which I try to explain in this post and how to work around the same.

Installer: You could download the trial version of IBM MQ Broker version 9.0.0.2

At the time of installation, make sure you install it on a machine which is not part of your TANT domain. I took a machine from Devcloud for this
purpose and made sure that the machine is just part of the workgroup.

During installation, one of the screens would ask about 'special privileged domain user'. Say that your machine is not part of the domain and the
installation should get through well.

Once installed, open MQExplorer, a thick client which you would use to setup your queues and also to monitor them.

"C:\Program Files\IBM\MQ\bin64\MQExplorer.exe"

To create a Queue Manager:

About Queue Manager: A queue manager in MQ is the component that the clients would talk to in order to read and write messages to a queue.

1. Open MQ explorer
2. Right click on 'queue managers' folder on the left and choose new Queue Manager
3. In the creation wizard, retain all default settings and make sure you choose a port that is unused. Queue manager port series start from
1414
4. Once the queue manager is created, you need to make couple of configuration changes
a. Create a channel - This is a very important step. Without a channel, the MQ server cannot listen to a client (such as CA Devtest
Workstation)
b. Disable default user access denial policy
5. To create a channel, expand the queue manager and right click on the folder 'Channels' New Server-connection Channel. Just give a
name and click finish. (More on why we need the channel here https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.1.0/com.ib
m.mq.explorer.doc/e_channels.htm)
6. Now click on the folder 'Channels' and you should see the channel on the right side
7. Right click on the channel and 'Start'. DONT WORRY IF YOU SEE THE OVERALL CHANNEL STATUS AS INACTIVE
8. The next step is to deactivate the default user-blocking policy. You do this by following steps below
a. Go to the queue manger that was just created
b. Expand and click on the folder 'Channel Authentication Records'
c. On the right side, you would notice a 'Block user' policy. Just right click and 'delete' it. You are all set to define necessary queue
and start using your message broker
d.
9. To send a message to a queue using JMS Send Receive step from Workstation, do the following
a. First define all the assets in project config
b. When you define the queue manager, you should give an username and password. I created a local non-admin user called
'admin' and used it. In case if you dont want to use username and password, you could change the 'EXTENDED PROPETIES' of
'QUEUE MANAGER' and change 'Connection Authentication' parameter. The default one
'SYSTEM.DEFAULT.AUTHINFO.IDPWOS' allows local system users to be used for authentication. If you set this to NONE, you
will be able to connect to queue manager without passing username and password.
c.

10. CHANGING AUTHENTICATION MODEL OF QUEUE MANAGER. MAKE SURE YOU RESTART THE QUEUE manager for this change
to effect
The IBM Native MQ Send Receive Step

1. Once the assets are defined, you could create a new test case
2. Add a test step 'IBM MQ Native Send Receive'
3. Once the step is added, we need to define the parameters to be used. Just click on the step and you would see the following screen. Now click
on the blue tab 'IBM Native MQ Send receive'

In order to interact with IBM MQ, we need the following JARS to be placed in lib/shared folder. These jars are all part of IBM MQ Server
installation. Please ignore activemq-all.jar file. It is not needed for IBM
4. You would see a properties palette. In order to send messge just select only IBM MQ PUT. Choose 'Put queue'. In the 'Request Editor' at the
bottom, fill some content and 'Exceute' button at top right corner. You could see the resuit of 'message PUT' operation in 'Execution Log' tab at
the bottom.

You might also like