Skip to content

Latest commit

 

History

History
40 lines (24 loc) · 2.42 KB

building.md

File metadata and controls

40 lines (24 loc) · 2.42 KB
Raw

Building a container image

Prerequisites

You need to have the following tools installed:

If you are working in the Windows Subsystem for Linux, follow this guide by Microsoft to set up Docker first.

You will also need a Red Hat Account to be able to access the Red Hat Registry.

Building a production image

This procedure works for building the MQ Continuous Delivery release, on amd64, ppc64le and s390x architectures.

  1. Create a downloads directory in the root of this repository
  2. Download MQ from IBM Passport Advantage or IBM Fix Central, and place the downloaded file (for example, IBM_MQ_9.2.0_LINUX_X86-64_NOINST.tar.gz) in the downloads directory
  3. Login to the Red Hat Registry: docker login registry.redhat.io using your Customer Portal credentials.
  4. Run make build-advancedserver

Warning: Note that from MQ 9.2.X, the MQ container build uses a 'No-Install' MQ Package, available under IBM MQ V9.2.x Continuous Delivery Release components eAssembly, part no. CJ7CNML

If you have an MQ archive file with a different file name, you can specify a particular file (which must be in the downloads directory). You should also specify the MQ version, so that the resulting image is tagged correctly, for example:

MQ_ARCHIVE=mq-1.2.3.4.tar.gz MQ_VERSION=1.2.3.4 make build-advancedserver

Building a developer image

Login to the Red Hat Registry: docker login registry.redhat.io using your Customer Portal credentials. Run make build-devserver, which will download the latest version of MQ Advanced for Developers from IBM developerWorks. This is currently only available on the amd64 architecture.

You can use the environment variable MQ_ARCHIVE_DEV to specify an alternative local file to install from (which must be in the downloads directory).

Installed components

This image includes the core MQ server, Java, language packs, GSKit, and web server. This is configured in the Generate MQ package in INSTALLATION_DIR section here, with the configured options being picked up at build time.