Installing the operator with command lines without Cloud Pak

This section describes how to install IBM Process Mining on Red Hat OpenShift Container Platform using command-line operations without Cloud Pak. The installation process involves creating a namespace and deploying the required catalog sources and operator dependencies. You must install mandatory components including IBM Cloud Pak foundational services, IBM Cert Manager, Cloud Native PostgreSQL, and either Usage Metering Service or IBM Licensing.

You can also install the optional catalog sources for the following dependencies:
IBM Redis
You must install Redis operator if you want to run the IBM Process Mining application with replicas. For more information, see Installing IBM Redis.
Usage Metering Service (UMS) or IBM Licensing
You can install UMS or IBM Licensing for tracking metrics. For more information, see Installing IBM Licensing or Usage Metering Service.

Creating a Namespace

Before installing the catalog and the IBM Process Mining custom resource, you must choose the namespace on which you want to perform the installation. You can install IBM Process Mining in an existing Cloud Pak or create a new namespace.

Do the following steps to create a new namespace:

  1. Get the login token from the Red Hat® OpenShift® Container Platform:
    1. Log in to the Red Hat® OpenShift® Container Platform.
    2. Under the profile of the admin user (e.g. kubeadmin), click Copy login command > Display Token. Save the <LOGIN-TOKEN> for the next step.
  2. Open a terminal window and use the following command to login to your Red Hat® OpenShift® Container Platform cluster:
    oc login --token=<LOGIN-TOKEN> --server=https://<SERVER URL>
  3. Enter the following command:
    export PM_PROJECT=processmining
oc new-project ${PM_PROJECT}

Setting the storage class

Set storage class that you want to use as a default with the following steps:
  1. Go to Storage > StorageClasses.
  2. Select the storage that you want to use and set it as default.

rook-cephfs is an example of storage class, replace it with your used storage class.

Installing mandatory operator dependencies and IBM Process Mining

You must install the mandatory catalog sources for the following dependencies:

  • IBM Cloud Pak foundational services
  • IBM Certification Manager
  • IBM Zen Services
  • Cloud Native PostgreSQL

Do the following steps to install the mandatory dependencies and IBM Process Mining catalog:

  1. Use the following commands to deploy the mandatory catalog sources to the cluster. Verify if the previous catalog source is deployed before you run the next command:
    1. Deploy the Cloud Pak Foundational services catalog with the following command:
      cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: ibm-cp-common-services-4.18.0
  publisher: IBM
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:37bfaf01968c8b14982a1151db90c48aa83bcbfbcf4183052b6b828a068a94ae
  sourceType: grpc
EOF

      For official Cloud Pak Foundational Services documentation, see Installing Foundational Services.

    2. Deploy the IBM Certification manager catalog with the following command:
      cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cert-manager-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-cert-manager-4.2.22
  publisher: IBM
  image: icr.io/cpopen/ibm-cert-manager-operator-catalog@sha256:cdfefe057e75b30c50b1cf9f8c2a71a07b498d09bb5b74c454d3a0a7c11aa989
  sourceType: grpc
EOF
    3. Deploy the Zen Services catalog with the following command:
      cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-zen-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-zen-ibm-zen-6.4.2+20260322.214626.9 
  publisher: IBM
  image: icr.io/cpopen/ibm-zen-operator-catalog@sha256:cf2a4c2f1b8bc2e03ba1d78e7650c7bbf5af9560f2c56352bdcf6b7cfc7b9bf9
  sourceType: grpc
EOF
    4. Deploy the CNPG catalog with the following command:
      cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: cloud-native-postgresql-catalog
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
spec:
  displayName: ibm-cloud-native-postgresql-5.31.1+20260310.150029.2714
  publisher: IBM
  image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:79042063952ee9683c972a83ebfa9085f8899ea73403ff7a0de74e537d7b84b3
  sourceType: grpc
EOF
  2. Use the following command to deploy the IBM Process Mining catalog:
    cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-automation-processminings
  namespace: ${PM_PROJECT}
spec:
  displayName: ibm-process-mining-4.2.0
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/processmining-operator-catalog@sha256:cc2d6286fce49a84f9d9c24170d9a267158a91bfd104c8173de2f9efc8d94076
  updateStrategy:
    registryPoll:
      interval: 45m
EOF
Note: Wait until all catalog sources are in READY state before proceeding.

Installing IBM Cert Manager

Before Installing IBM Process Mining, you must install IBM Cert Manager:

  • Use the following commands to install IBM Cert Manager:
    cat <<EOF | oc apply -f -
apiVersion: v1
kind: Namespace
metadata:
  name: ibm-cert-manager
EOF

    cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: operatorgroup
  namespace: ibm-cert-manager
spec:
EOF

    cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ibm-cert-manager-operator
  namespace: ibm-cert-manager
spec:
  channel: v4.2
  installPlanApproval: Automatic
  name: ibm-cert-manager-operator
  source: ibm-cert-manager-catalog
  sourceNamespace: openshift-marketplace
EOF
Note: Wait until all pods are in Running state before proceeding. To check their state go to Workloads > Pods.

Installing IBM Zen Services

Note: The following configuration uses rook-cephfs as a storage class. You can change the storage class according to your requirements and configurations.

Do the following steps to configure IBM Zen Service (user authentication feature):

  1. Create the operator group for Process Mining. The Operator Group is a unit of multitenancy for operators that the Operator Lifecycle Manager (OLM) manages. It constrains the installation of operators in its namespace to a specified set of target namespaces.
    Note: If you already have an Operator Group for your namespace in Administration > CustomResourceDefinitions > OperatorGroup, skip this step.

    Use the following command to create the operator group:

    cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
  name: processmining-group
  namespace: ${PM_PROJECT}
spec:
  targetNamespaces:
  - ${PM_PROJECT}
EOF
  2. Create the process mining subscription. The subscription tracks changes to catalogs and ensures that the operators are up to date. Use the following commands to create a subscription:
    cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: processmining-subscription
  namespace: ${PM_PROJECT}
spec:
  channel: v4.0
  installPlanApproval: Automatic
  name: ibm-automation-processmining
  source: ibm-automation-processminings
  sourceNamespace: ${PM_PROJECT}
EOF
    Note: Wait until IBM Process Mining, IBM Certification Manager, IBM CPFS, and Operand Deployment Lifecycle Manager operators are successfully created before proceeding. Open the installed operators list to verify the status of installation.
  3. Create the OperandRequest with the following command:
    cat <<EOF | oc apply -f -
apiVersion: operator.ibm.com/v1alpha1
kind: OperandRequest
metadata:
  name: common-service
  namespace: $PM_PROJECT
spec:
  requests:
    - operands:
        - name: ibm-im-operator
        - name: ibm-platformui-operator
        - name: cloud-native-postgresql
      registry: common-service
      registryNamespace: $PM_PROJECT
EOF

    Note: Wait until all operands are successfully created before proceeding. Open the installed operators list to verify the status of installation.
  4. Create the Zen Service with the following command:
    cat <<EOF | oc apply -f -
apiVersion: zen.cpd.ibm.com/v1
kind: ZenService
metadata:
  name: lite-zen
  namespace: $PM_PROJECT
spec:
  blockStorageClass: rook-ceph-block
  fileStorageClass: rook-cephfs
  iamIntegration: true
EOF
    Note: Wait until Zen Service creates the ConfigMap platform-auth-idp. Also make sure the Zen Service completion is at least 37% before proceeding.
  5. Optional: If Zen Service is stuck at 4%, you need to update CNPG's subscription channel to 1.25.5. Go to Administration > subscriptions > cloud-native-postgresql > Update channel, click the pencil icon and choose the correct version.
  6. Wait for a while and verify that platform-auth-service, platform-identity-provider, and platform-identity-management are running with the following command:
    oc get pods | grep "platform-"
  7. NGINX pods are instantiated once the Zen Service completion progress exceeds 71%. Verify that the NGINX pods are running with the following command:
    oc get pods -n $PM_PROJECT | grep "ibm-nginx-"