[UPDATE]: IBM Cloud Pak for Integration (CP4I) 2019.4.1, which is the latest release, is not supported on OCP 3.11. CP4I 2019.4.1 requires OCP 4.2. It is recommended to use latest release of CP4I
[UPDATE]: The article has been updated for installing ICP4I 2019.3.2 on OCP 3.11
In this blog post, I will explain the steps involved in installing IBM Cloud Pak for Integration version 2019.3.1 / 2019.3.2 on Openshift 3.11.
Storage: Appropriate storage has been configured. For example, for on-prem installation CephRBD is recommended for API Connect, NFS or GlusterFS is recommended for ACE & MQ and GlusterFS is recommended for AssetRepository. Similarly for Cloud-native installation, configure appropriate storage.
Note: The Red Hat OpenShift version you are using must be 3.11 if you are installing IBM Cloud Pak for Integration version 2019.3.1 or 2019.3.2. The IBM Cloud Private version you are using must be 22.214.171.1246 for 2019.3.1 and 126.96.36.1997 for 2019.3.2.
We will do the ICP4I installation from OCP Master node. If you want to do from a client machine outside the OCP cluster, make sure to configure oc and kubectl clients.
Login to OCP master with OCP cluster-admin authority having root-level access.
Login to OCP using below command:
For example OpenshiftURL is
Login to OCP docker registry using below command:
By default docker registry url would be:
1) Download IBM Cloud Pak for Integration (Openshift) installable from Passport Advantage (PPA)
Part number: CC40AEN
File name: IBM_CLOUD_PAK_FOR_INTEGRATION_201.tar.gz
2) Extract the Installable:
Extract the files using below command:
It will create a folder ‘installer_files’ and will extract the artifacts inside it.
3) Label Openshift master node as compute
If you want to deploy IBM Cloud Private on any OpenShift master or infrastructure node, Openshift master node(s) should be labeled as compute. You can see the OCP nodes by running the command:
Run below command to label OCP master nodes as compute nodes:
Now run “oc get nodes” to verify that Openshift master node(s) has/have been labeled as compute.
4) Set vm.max_map_count
On each storage node, set vm.max_map_count to 1048575. This is minimum required value if you want to install API Connect, else minimum required value is 262144.
Use below command to verify
You can also check using “vi /etc/sysctl.conf”
5) Patch Storage Class
If you want to make the storage class as default, you can do it else you can omit this step.
Check the storage class name by running the command:
For example, if you have configured glusterfs with storage class name ‘glusterfs-storage’, it will return this name. You can run below command to make this storage class default:
Now run “oc get sc” command to verify.
Note down this storage class name as it will be used while configuring config.yaml for installing ICP4I.
6) Verify subdomain
Get the subdomain configured in OCP cluster. Run the below command:
7) Configure config.yaml
Configure conf.yaml file for ICP4I installation. Here we will use OCP dedicated compute nodes for configuring ICP4I master, proxy and management nodes. Attached are sample config.yaml files.
Sample config.yaml for 2019.3.1:
Sample config.yaml for 2019.3.2:
Download and unzip to see the sample config.yaml file. Notice below sections in this yaml file and update accordingly in your config.yaml:
# A list of OpenShift nodes that used to run ICP components
Here master will be the OCP compute node that you have designated for ICP master, proxy will be the OCP compute node that you have designated for ICP proxy and management will be the OCP compute node that you have designated for ICP management.
Specify the storage class name:
Update below section:
In 2019.3.2 yaml file, yaml anchor has been added that allows us to refer to this value later when configuring the IBM Cloud Pak for Integration Platform Navigator. So below is the value of proxy_host:
Set the password for ‘admin’ user:
You can set the password rule by adding below section:
In archive-addons section for icp4i, update the hostname value for ibm-icp4i-prod to ICP proxy hostname. In sample config.yaml for 2019.3.2 it has been left to default, i.e.
- name: ibm-icp4i-prod
hostname: icp-proxy.188.8.131.52.nip.io # hostname of the ingress proxy to be configured
8) Extract the images
Run below command from installer_files directory:
Now extract the images and load them into docker.
Go to installer_files/cluster/images folder. Run below command:
It will take time to extract and load images to docker.
9) Install ICP4I
Install ICP4I using below command from /cluster directory:
sudo docker run -t --net=host -e LICENSE=accept -v $(pwd):/installer/cluster:z -v /var/run:/var/run:z --security-opt label:disable ibmcom/icp-inception-amd64:184.108.40.2066-rhel-ee install-with-openshift
sudo docker run -t --net=host -e LICENSE=accept -v $(pwd):/installer/cluster:z -v /var/run:/var/run:z --security-opt label:disable ibmcom/icp-inception-amd64:220.127.116.117-rhel-ee install-with-openshift
Installation will take some time.
10) Verify Installation
After installation is completed successfully, verify the installation.
Login to ICP Console using the url:
Login to Platform Navigator using below url: