Choosing how you want to use IBM MQ in containers
There are multiple options for using IBM® MQ in containers: you can choose to use pre-packaged certified containers, or you can build your own images and deployment code.
Using the IBM MQ Advanced certified containers
- IBM MQ Advanced certified container for IBM Cloud Pak® for Integration. This is a separate IBM product that includes a version of a certified container.
- IBM MQ Advanced certified container
- IBM MQ Advanced for Developers certified container (unwarranted)
The certified containers include both pre-built container images, as well as deployment code for running on Red Hat OpenShift Container Platform. From IBM MQ 9.1.5 onwards, queue managers are managed using an IBM MQ Operator. Prior versions of IBM MQ, up to and including version 9.1.5, are managed using Helm charts.
- Use the REST APIs for administration or messaging
- Use any of the following MQ components:
- Managed File Transfer Agents and its resources. However you can use the certified containers to provide a Coordination/Command/Agent queue manager.
- IBM MQ Bridge to Salesforce
- IBM MQ Bridge to blockchain (not supported in containers)
- Use the web server when you're deploying using Helm charts (except for IBM Cloud Pak for Integration)
- Customize options used with crtmqm, strmqm and endmqm, such as configuring recovery logs
Building your own images and charts
This is the most flexible container solution, but
it requires you to have strong skills in configuring containers, and to
own the resultant
container. If you aren't planning to use Red Hat OpenShift Container Platform,
then you will need to build your own images and deployment code.