This is a step-by-step guide to help you easily and quickly deploy Content Services in Cloud Pak for Business Automation. It doesn’t require a whole lot of prerequisites steps like databases and LDAP preparations. This is a great way to get started and explore Content Services capabilities and features without needing full enterprise configuration and support from your IT teams. In fact, this quick deployment option can be used for other key capabilities within Cloud Pak for Business Automation like Automation Document Processing (ADP).

Prerequisite: Software Entitlement
Ensure you have software entitlement in order to pull images from the IBM entitlement registry. You can verify this by logging into https://myibm.ibm.com/ using your IBMid. Navigate to “Container software library” and “View library” to ensure you have entitlement to Cloud Pak for Business Automation software. Lastly, click on “Get entitlement key” to get the entitlement key needed later to create the image pull secrets.

Prerequisite: OpenShift Project/Namespace
Cloud Pak for Business Automation prefers and recommends to deploy within a project or namespace. So one of the first thing you need to create within OpenShift is a project. Login to the OpenShift web console with a user that has permissions to create a project like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and click “Create Project” button in the upper left-hand corner. Enter in a name for your project at a minimum (see example below).

Prerequisite: Dynamic Storage Class
A dynamic storage class that support RWX (ReadWriteMany) is needed in order to simplify the "Demo" deployment option. This storage class will be used to create the two persistent volume claims (PVC) for the CP4BA operator and by the individual components. For the purpose of this demonstration, we will setup a NFS server on the boot node and create a NFS dynamic storage class (attached below is an example script).

nfs-sc.sh

Prerequisite: Operator Persistent Volume Claims (PVC)
Prior to deploying the CP4BA operator, we need to create 2 PVCs using the dynamic storage class created previously. Login to the OpenShift web console with a user that has permissions to create PVC like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Now click on the + icon (import YAML action) next the ? icon and logged in user name to create the two PVCs used by the operator (see example below).



Prerequisite: Image Pull Secrets
Next we need to create two image pull secrets in order to pull IBM container images from the entitled registry. Login to the OpenShift web console with a user that has permissions to create image pull secrets for project like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Now navigate to Workload -->Secrets than click on "Create" button in the top-right (see example below).

Secret Name: admin.registrykey
Registry Server Address: cp.icr.io
Username: cp
Password: <entitlement key>

Secret Name: ibm-entitlement-key
Registry Server Address: cp.icr.io
Username: cp
Password: <entitlement key>



Prerequisite: Service Account and Permissions Needed for Demo Deployment Option
Prior to deploying using the "Demo" deployment option, we need to create two service accounts with elevated permissions needed by OpenLDAP and Gittea containers. Login to the OpenShift web console with a user that has permissions to create service account and modify permissions such as the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Now click on the + icon (import YAML action) next the ? icon and logged in user name in order to create the two service accounts. Next navigate to the drop-down next to the user name such as "kube:admin", select "Copy Login Command" and click on "Display Token". Now login to machine/server that has the "oc" CLI installed like the OCP boot node and past in the login token. Execute the following commands (see example below).

oc project cp4ba-demo
oc adm policy add-scc-to-user priviledged -z ibm-cp4ba-privileged -n cp4ba-demo
oc adm policy add-scc-to-user anyuid -z ibm-cp4ba-anyuid-n cp4ba-demo


Prerequisite: Catalog Source
Before we can deploy the Cloud Pak operators, we need to create the CatalogSource so that the Cloud Pak operators are shown within the OpenShift OperatorHub local catalog. Login to the OpenShift web console with a user that has permissions to create CatalogSource like the default cluster admin “kubeadmin”. Now click on the + icon (import YAML action) next the ? icon and logged in user name to create the two CatalogSource (see example below).


install CP4BA Operator
Login to the OpenShift web console with a user that has permissions to install the CP4BA operator in the project like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Then navigate to Operators -->OperatorHub. Now click on Automation and click on Cloud Pak for Business Automation tile to start the install process (see example below).


Configure & Deploy Content Service Demo Pattern
Login to the OpenShift web console with a user that has permissions to install the CP4BA operator in the project like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Then navigate to Operators -->Installed Operators. Now click on the Cloud Pak for Business Automation operator and then click on "Create Instance" under Provided APIs (see example below).

License: True
Shared Configuration-
Purchased CP4BA license: non-production
Platform: OCP
Storage Configuration-
Storage for Demo: rook-cephfs
Deployment Type: demo
FileNet Content Manager: True


Confirm Successful Deployment
Login to the OpenShift web console with permissions to the CP4BA project like the default cluster admin “kubeadmin”. Once logged in, navigate to Home -->Projects and select the CP4BA project created previously. Then navigate to Workloads -->Config Maps (see example below).



Resources
Cert-kubernetes package, Service account and permissions
https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=hub-preparing-operator-log-file-storage

CatalogSource
https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=hub-installing-operator-catalog