Prepare storage, including the required persistent volumes (PVs) and persistent volume
claim (PVCs) for the operator, Business Automation
Studio, IBM Business Automation Navigator, IBM FileNet® Content
Manager, Intelligent Task Prioritization, Workforce Insights, Java™ Message Service (JMS), IBM Process Federation Server, and IBM Business Automation Workflow Authoring.
Procedure
-
If you haven't done it already, prepare storage for the operator by following the instructions
in Preparing a namespace for the operator.
-
Prepare storage for Business Automation
Studio, by following the instructions in Optional: Implementing storage.
-
Prepare storage for IBM Business Automation Navigator, by following the instructions in Creating volumes and folders for deployment on Kubernetes.
Important: The value for the
workflow_authoring_configuration.case.network_shared_directory_pvc
(the persistent
volume claim (PVC) name for the case network shared directory) parameter in the custom resource must
be set to the same value as the IBM Business Automation Navigator
pvc_for_icn_pluginstore
parameter.
-
Prepare storage for IBM FileNet Content
Manager, by following the instructions in Configuring storage for the content services environment.
-
Prepare storage for Intelligent Task Prioritization.
The Intelligent Task Prioritization
feature requires a PV to be created before you can deploy. You have the following options, depending
on whether your Kubernetes environment supports dynamic provisioning.
- Option 1: If your environment supports dynamic provisioning:
Enable dynamic provisioning
by setting
baml_configuration.intelligent_task_prioritization.storage.use_dynamic_provisioning
to true
. The trained model files will use
shared_configuration.storage_configuration.sc_fast_file_storage_classname
in the PV
and the log file will use
shared_configuration.storage_configuration.sc_medium_file_storage_classname
in the
PV.
- Option 2: If your environment does not support dynamic provisioning:
Disable dynamic
provisioning by setting
baml_configuration.intelligent_task_prioritization.storage.use_dynamic_provisioning
to false
. Then, create two PVs and PVCs manually and set
baml_configuration.intelligent_task_prioritization.storage.existing_pvc_for_logstore
to the name of the log PVC and
baml_configuration.intelligent_task_prioritization.storage.existing_pvc_for_trained_pipelines
to the name of the trained pipelines PVC in the custom resource file.
-
Prepare storage for Workforce Insights.
The Workforce Insights
feature requires a PV to be created before you can deploy. You have the following options, depending
on whether your Kubernetes environment supports dynamic provisioning.
- Option 1: If your environment supports dynamic provisioning:
Enable dynamic provisioning
by setting baml_configuration.workforce_insights.storage.use_dynamic_provisioning
to true
. The log file will use
shared_configuration.storage_configuration.sc_medium_file_storage_classname
in the
PV.
- Option 2: If your environment does not support dynamic provisioning:
Disable dynamic
provisioning by setting
baml_configuration.workforce_insights.storage.use_dynamic_provisioning
to
false
. Then, create two PVs and PVCs manually and set
baml_configuration.workforce_insights.storage.existing_pvc_for_logstore
to the name
of the log PVC in the custom resource file.
-
Prepare storage for Business Automation Workflow.
The Business Automation Workflow
component requires a PV to be created before you can deploy. You have the following options,
depending on whether your Kubernetes environment supports dynamic provisioning.
- Option 1: If your environment supports dynamic provisioning:
Enable dynamic provisioning
by setting workflow_authoring_configuration.storage.use_dynamic_provisioning
to
true
. The dump file will use
shared_configuration.storage_configuration.sc_slow_file_storage_classname
in the PV
and the log file will use
shared_configuration.storage_configuration.sc_medium_file_storage_classname
in the
PV.
- Option 2: If your environment does not support dynamic provisioning:
Disable dynamic
provisioning by setting
workflow_authoring_configuration.storage.use_dynamic_provisioning
to
false
. Then, create the required PVs and PVCs manually. Also, set
workflow_authoring_configuration.storage.existing_pvc_for_filestore
to the name of
the generic file PVC and set
workflow_authoring_configuration.storage.existing_pvc_for_indexstore
to the name of
the search index file PVC.
What to do next
There are optional steps you can do next.
After you've done any optional steps and prepared for each capability that you want to install,
deploy the custom resource (CR) file. See Creating a production deployment.