Overview

If you have deployed Cloud Pak for Business Automation (CP4BA) on IBM Cloud in RedHat Openshift Kubernetes Service (ROKS) then you may experience an issue where you don't have the ability to create Case Business Automations and do not have the ability to use internal document store in your Business Automation applications.

Problem

The problem is that when you deploy CP4BA on ROKS in IBM Cloud and even if you enable all the features / capabilities you will see that the IBM FileNet P8 Content Platform Engine (CPE) is present but the internal document store (in Business Automation Workflow) is not working. You can recognize this if you goto BAStudio / Web Process Designer and try to create a Process and goto Folders tab, you will see this - 

The reason why you do not have internal document store is that the "Case" is missing in such a deployment. You need to enable and configure Case properly in order to be able to manage documents in your processes.

Resolution

In order to enable Case properly you need to check what kind of Objects you have in your Content Platform Engine (CPE). In order to do this login to ACCE console in your IBM Cloud Pak (you can check the exact URL in Openshift Web console -> Workloads -> ConfigMaps -> search for "cp4ba-access-info"). For example - 

https://cp4a-demo-project.mydomain.cloud/cpe/acce/

You will see something like - 

So, in this example (and most likely you will have the same objects in case you were using standard deployment of CP4BA on IBM Cloud ROKS cluster) we will use DESIGN and TARGET objects for the Case configuration.

Procedure

• Goto "OpenShift Web console" -> Operators -> Installed Operators -> find "IBM Cloud Pak for Business Automation" and click on it - 

• Inside the "IBM Cloud Pak for Business Automation" click on "CP4BA deployment" tab and then click on "icp4adeploy" cluster - 
  
  
• Inside the "icp4adeploy" click on "YAML" tab - 
  
  
• We need to edit YAML file and make a couple of changes. You may want to "Download" it first and save it somewhere on your system, so, if you need to go back to the original version you can always do so.
• First search for "Starter" word in the file (you can use Ctrl + F inside the editor to search in YAML file), make sure that your deployment is "Starter" one because below instructions are for this type of deployment - 

   sc_deployment_type: Starter

• Find a section that starts with "workflow_authoring_configuration" and add the following stanza:

  case:
   ## Domain name for CASE
   domain_name: "P8DOMAIN"
   ## Design Object Store name of CASE
   object_store_name_dos: "DESIGN"
   ## Target Object Store name of CASE
   object_store_name_tos: "TARGET"

  Make sure you make correct indents as that is critical for YAML file, at the end this section should look something like this - 
  

• Click on "Save" and make sure you receive a successfully saved message (if not, do it again)
• Open the same YAML again and this time we need to enable the Case functionality (add ",case" at the end of the following section):

  spec > shared_configuration > sc_optional_components: ...,baw_authoring,case

  

• Click on "Save" and make sure you receive a successfully saved message (if not, do it again)

The new YAML configuration needs to be picked up by the cluster and it might take some time. If you want to speed up the process you can goto OpenShift Web console -> Workloads -> Pods -> find "ibm-cp4a-operator-xxxxx" and delete it. It should then be redeployed automatically sooner.

Verification

There are a couple of ways how you can verify that the Case is now enabled and works fine - 

• Goto BA Studio and try to create Business Automation new application - you should now have a checkbox that allows you to create application that would include Case features -

• If you open any Business Automation app in Web Process Designer and create a Process and goto Folders tab you should now have the ability to check the checkbox to "Allow locally managed documents" that was previously greyed out / not available -