KB000793OverviewThis application guide illustrates how Docker Enterprise 2.1 can be used to deploy an IBM MQ service communicating between two applications running on separate instances of WebSphere Liberty.The two applications can be staged using the build script, and the sample can then be deployed by using Docker Compose or Kubernetes. Docker allows you to package an IBM MQ queue manager or IBM MQ client application, with all of its dependencies, into a standardized unit for software development. Changes to your application can be deployed to test and staging systems quickly and easily. This feature can be a major benefit to continuous delivery in your enterprise. IBM-MQ: Configuring mutual TLS authentication between client and queue manager Posted on 16th February 2020 by ng247 I’m trying to set up TLS mutual authentication between client and IBM-MQ queue manager (using the ibmcom/mq Docker image).
In a previous blogpost, I described how you can install IBM MQ on your local development machine. This is still a lot of work just to get MQ up and running…
Mac Docker Machine
This post describes how to run IBM MQ in Docker and get you up and running in less than 5 minutes!(you should have of course already a working installation of Docker Desktop on your machine)
The official GitHub repository of the MQ Container can be found here: https://github.com/ibm-messaging/mq-container.
Step 1 – Run MQ with default config
These instructions are based on the official usage documentation. In this example, I will not use the default MQ_DEV config.
Step 2 – Disable security
The default configuration has security configured out of the box. And that is a good thing! But it might be a bit annoying for local development.
Connect to your container using the cli. Use runmqsc to disable security and create a new channel that runs under the mqm user.
At this point, security is disabled and the channel “DEMO.ADMIN.SVRCONN” can be used for messaging (from Java / .NET) and admin purposes (MQ Explorer) without any security.
Install Docker For Mac
DISCLAIMER: you should only disable security like this in a development scenario!