ibmcom/iib repository overview

⁠Please note that we have now released IBM App Connect Enterprise v11, which you can find at ot4i/ace-docker⁠

⁠Overview

The image in this repository contains IBM Integration Bus for Developers. The scripts used to build the image can be found on GitHub. See the license section below for restrictions relating to the usage of this image.

⁠Usage

In order to run a container from this image, it is necessary to accept the terms of the IBM Integration Bus for Developers license. This is achieved by specifying the environment variable LICENSE equal to accept when running the image. You can also view the license terms by setting this variable to view. Failure to set the variable will result in the termination of the container with a usage statement. You can view the license in a different language by also setting the LANG environment variable.

⁠What the image contains

The built image contains a full runtime installation of IBM Integration Bus for Developers. It does not contain an installation of IBM MQ (neither MQ Server nor MQ Client), so IIB features requiring access to a queue manager are not available in this image.

⁠Running a container

Starting from this Docker image, you can run a container⁠ which will create and start an Integration Node to which you can deploy⁠ integration solutions.

In addition to accepting the license, you can optionally specify an Integration Node name using the NODENAME environment variable and an Integration Server name using the SERVERNAME environment variable.

The last important point of configuration when running a container from this image, is port mapping. The image exposes ports 4414 and 7800 by default, for Integration Node administration and Integration Server HTTP traffic respectively. This means you can run with the -P flag to auto map these ports to ports on your host. Alternatively you can use -p to expose and map any ports of your choice.

For example:

docker run --name myNode -e LICENSE=accept -e NODENAME=MYNODE -e SERVERNAME=MYSERVER -P iib

If you wish, you can also deploy an IBM Integration Bus BAR file by specifying a Docker volume⁠ which makes the BAR file(s) available when the container is started:

docker run --name myNode -v  /local/path/to/BARs:/tmp/BARs -e LICENSE=accept -e NODENAME=MYNODE -e SERVERNAME=MYSERVER -P iib

This will run a container that creates and starts an Integration Node called MYNODE and exposes ports 4414 and 7800 on random ports on the host machine. At this point you can use:

docker port <container name>

to see which ports have been mapped then connect to the Node's web user interface as normal (see the verification section below).

⁠Running administration commands

You can run any of the Integration Bus commands using one of two methods:

⁠Directly in the container

Attach a bash session to your container and execute your commands as you would normally:

docker exec -it <container name> /bin/bash

At this point you will be in a shell inside the container and can source mqsiprofile and run your commands.

⁠Using Docker exec

Use Docker exec to run a non-interactive Bash session that runs any of the Integration Bus commands. For example:

docker exec <container name> /bin/bash -c mqsilist

⁠Accessing logs

This image also configures syslog, so when you run a container, your node will be outputting messages to /var/log/syslog inside the container. You can access this by attaching a bash session as described above or by using docker exec. For example:

docker exec <container id> tail -f /var/log/syslog

⁠Verifying your container is running correctly

Whether you are using the image as provided or if you have customised it, here are a few basic steps that will give you confidence your image is running properly:

1. Run a container, making sure to expose port 4414 to the host - the container should start without error
2. Run mqsilist to show the status of your node as described above - your node should be listed as running
3. Access syslog as descried above - there should be no errors
4. Connect a browser to your host on the port you exposed in step 1 - the Integration Bus web user interface should be displayed.

At this point, your container is running and you can deploy⁠ integration solutions to it using any of the supported methods.

⁠License

The license for the product installed within the images is as follows:

• IBM Integration Bus for Developers⁠ (International License Agreement for Non-Warranted Programs)

Note that this license does not permit further distribution and restricts usage to a developer machine.

⁠User Feedback

For issues relating specifically to this Docker image, please use the GitHub issue tracker⁠. For more general issues relating to IBM Integration Bus you can get help through the IBM dWAnswers IBM Integration Bus Forum⁠