IBM Websphere MQ can be an overwhelming product to use as a message broker if you have worked in the past with Microsft’s MSMQ or the Azure Service Bus. The best way to learn and understand a product is to have your local lab environment, that you can recreate when needed.
With this post I share with you some links how you can setup your own local IBM MQ 9 installation for development purposes.
Direct link: IBM MQ 9.0.3 fo
This very well written blog posts explain how you can setup a queue manager, configure a channel and create a queue.
(Skip step 10 as it isn’t the best way to disable security)
Step 3: Disable MQ Security
The default installation of IBM MQ has security turned on. Without disabling this you won’t be able to use your .NET client application or the BizTalk Adapter to send/receive messages. Be aware that you should only do this on your development environment!
Step 4: Add a firewall exclusion rule
If you are planning to host your local IBM MQ setup in a seperate VM, you will most likely need to setup a firewall exlusion rule so you can access the queue manager from another machine. (If you install IBM MQ as a service it will listen by default on all IP addresses)
Simply add an exclusion rule to allow inbound TCP traffic for the port your queue manager is running on (default is 1414).
Optional: .NET Sample Applications