Docker and IBM App Connect

Sajith Mohanan
4 min readFeb 2, 2021

--

Containerized Integration deployment with IBM App Connect Enterprise

Introduction : This article is all about using docker and IBM App Connect Enterprise and hosting REST API . Create multiple instance of same rest API. This article would be useful for Integration techies who want to try out dockers and ACE

Requirement : Host multiple instance of REST API on IBM App connect integration server.

To start with we will need Docker installation completed on the machine. Here I have used Docker for Windows 10 and I am using Ubuntu 20.04 LTS via Virtualization

Docker Link : Install Docker Desktop on Windows | Docker Documentation

Ubuntu can be enabled by installing any flavor via Store.

Step 1: Once the docker set up is compete docker version needs to be verified and the same can be done using below command.

Step 2: Search for docker image of IBM Ace connect . Ace connect image is available at docker hub . We can see the image is available and we can use it to spin up our container for Integration server. Which we will use to deploy BAR / Broker files .

Step 3: Spin up container using the image from docker hub. Map the host and container port , also pass the default parameters related to LICENSE acceptance.

docker run — name acelinkedNode1 -p 7602:7600 -p 7802:7800 -p 7845:7843 — env LICENSE=accept — env ACE_SERVER_NAME=ACESERVER ibmcom/ace

Step 4: Verify Integration server . To do this we will hit the URL with the host port that was mapped with container which we spinned up. In my case its 7600 .

http://localhost:7600

So that was quick !!

We have instance of Integration server up and running . Please note we are able to do this only because of changes that were done by IBM as part of ACE 11 . This was done to support containerization . Previously Integration servers were created under Integration Nodes. From Ace 11 we don’t need to create Integration Nodes. However integration nodes still exist in toolkit !!.

Step 5: Deploy BAR file which has all the flow related to API.

BAR file selected for deployment.
Deployed successfully !!
API details

The BAR file deployed is a sample one and returned static response .Same can be seen in the below screen grab. API accessed over localhost:7800

API and response

Step 6: Spin up another container with the image . We can also create new image which has bar file within it , however here we are going to repeat the same steps again .This time we will allocate different set of port numbers.

docker run — name acelinkedNode1 -p 7602:7600 -p 7802:7800 -p 7845:7843 — env LICENSE=accept — env ACE_SERVER_NAME=ACESERVER ibmcom/ace

New container up with the same image.

We can go ahead and deploy the same BAR file over here to have the new API listening over new port.

List all the containers that are now running. Below command will do it for us.

docker ps

There are lot more to dockers , images , containers and ACE . I hope I have been able to show how to use a combination of all these together.

Few Useful links

GitHub — ot4i/ace-docker

Thank you :)

--

--