Skip to main contentDemoHub - Cloud Pak for Integration

Installing Cloud Pak for Integration using Operators

The installation of IBM Cloud Pak for Integration (CP4I) is simplified with Operators support starting from release 2020.2.1. The IBM Cloud Pak for Integration can be installed by adding the IBM Operator Catalog and the IBM Common Services Catalog to your cluster and using the Operator Lifecycle Manager (OLM) to install the operators. You can then deploy the CP4I capabilities and runtimes using Platform Navigator or Operator Hub.

The following instructions apply to CP4I on all supported platforms including IBM Cloud, AWS, Azure, and on-prem.

Prerequisites

  • OpenShift cluster 4.4.9 or higher
  • Administrator access to Openshift console
  • IBM Entitlement Registry Key
  • Minimum 3 worker nodes with 16 cores and 32gb memory, block and file storage access
  • oc command line tool

OLM Catalog Sources

\1. Login to your OpenShift cluster using userid and password or token. You must be a cluster administrator to add CatalogSource objects to a cluster. You can obtain OpenShift

![](images/tutorial_html_2e43fe0eb354ddda.png)
The login command using a token looks like below (your token and cluster
address will be different)
oc login --token=19P1E8JTTT307A4DpncdR-WNYTCCeTF0OiPFx5UJirw
--server=https://c104-e.us-east.containers.cloud.ibm.com:30339
  1. Add the IBM Common Services operators to the list of installable operators by running the following command:
oc apply -f - << EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: opencloud-operators
namespace: openshift-marketplace
spec:
displayName: IBMCS Operators
publisher: IBM
  1. Add the IBM operators to the list of installable operators by running the following command:
oc apply -f - << EOF
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: ibm-operator-catalog
namespace: openshift-marketplace
spec:
displayName: ibm-operator-catalog
publisher: IBM Content

Install Platform Navigator

  1. Get your entitlement key from the Container Library

  2. Create a namespace for Platform Navigator

oc new-project cp4i
  1. Create an entitlement secret using the entitlement key from step-1.
oc create secret docker-registry ibm-entitlement-key \
--docker-username=cp \
--docker-password=<entitlement-key> \
--docker-server=cp.icr.io \
--namespace=<target namespace>
  1. Deply Platform Navigator using the Red Hat OpenShift web console. Go to OperarorHub and look for Platform Navigator

    tutorial html f2a37c17b4133251
  2. Select Install to install Platform Navigator.

    tutorial html a4e2c82e2c70f39c
  3. Add Operator Subscription. The new subscription can be added for a specific namespace or all namespaces. Select cp4i for namesace.

    tutorial html 18e1412b3c9fb509
  4. When you add Platform Navigator, Deployment Lifecycle Manager and Common Services Operators are also installed. Select Platform Navigator to create an instance.

    tutorial html 9ef1a0066bc419c8
  5. Click on Create Platform Navigator to create an instance.

    tutorial html eceebe3d26810729
  6. Accept license and select Create.

    tutorial html 3eb02207706873
  7. When platform navigator and dependent services are successfully installed. You can obtain admin password by running the following command.

oc get secrets -n ibm-common-services platform-auth-idp-credentials -ojsonpath='{.data.admin_password}' | base64 --decode && echo ""

You can get the login URI for Platform Navigator using the following command:

oc get route -n cp4i -ojsonpath='{.items[0].spec.host}'
  1. Open the URI in a browser and login using admin and \<password> using Default authentication option.

    tutorial html cf798b43ee903b02 tutorial html 6118328489008c1e

Installing Capabilities and Runtimes

  1. Initially when Platform Navigator is installed the Capabilities and Runtimes will be blank. You can add Cloud Pak capabilities and Runtimes using Plaform Navigator or Openshift web console..

    tutorial html 153a9d62568c2653

    Make sure you subscribe to the capabilities from Operator Hub prior to creating instances, otherwise you will see a message similar to below.

    tutorial html c51e95c4349324e9
  2. Add Operations Dashboard capability

    tutorial html f109e1ca9a249130 tutorial html f1cd021813a91d85 tutorial html ce63597305b72024 tutorial html 1718e538fab19667 tutorial html 479612f9fcbd9dd5
  3. Add Asset Repository capability

    tutorial html ba86ece4ad72a9eb tutorial html 79ed45052e2dfb4 tutorial html addfbe7477948a6d
  4. Add App Connect Dashboard capability

    tutorial html df6dd892fe99414e tutorial html 4c1641cf21c45572 tutorial html b9bdf47f775de865
  5. Add AppConnect Designer capability

    tutorial html 6aae3b3402ea6f61 tutorial html b1d3acd907b6c25d tutorial html c0905665a46852b tutorial html 2f05450267c40128
  6. Add API Connect capability

    tutorial html d3ed2953a5a9e5f4 tutorial html 1abfe6c4d96ed38e tutorial html f86a9f552f66f16d
  7. Select Runtimes tab and add EventStreams runtime by selecting Kafka cluster

    tutorial html 93c4b6177464a875 tutorial html 7e5bf6329a90c763
  8. Add an MQ Queue Manager runtime. Select Availability type, Tracing, Persistence as needed. Choose default values for quick installation.

    tutorial html a69ebb8a2537f6fe tutorial html 5b4663c2a4c790cf tutorial html 73ab4241512c55da
  9. Add highspeed file transfer capability

    tutorial html d96ef3586f62d582 tutorial html b93e5b10339b08f0 tutorial html 487ac9f78f0b0632 tutorial html aa7f7f5268a287f5
  10. When all the capabilities and runtimes are installed, the Cloud Pak web console menu displays the instances (the name of you instances may be different from what is shown here).

    tutorial html 2a4b49c2cfb34f50

Post installation steps

The following additional steps are needed after deploying all the capabilities.

  1. If you enabled Tracing capabilities for API Connect and MQ, capabilities must be registered from Operations Dashbard Setting tab. Follow the instructions from here.

  2. Setup notification, create provider organization, add catalogs and portal server as API admin.

You have successfully installed and deployed Cloud Pak for Integration capabilities!!