Preparing to install Workflow Process Service Authoring

Before you install Workflow Process Service Authoring, you must prepare your environment.

Before you begin

The following diagram shows the components that you can select for Workflow Process Service Authoring. You must make sure that you prepare everything that is needed by these components before you apply your custom resource.

If you used the cp4a-prerequisites.sh script to generate the database SQL statement files (scripts) and YAML template files for the database secrets, then you do not need to create these resources and apply them again. For more information about running the cp4a-prerequisites.sh script, see Recommended: Preparing databases and secrets for your chosen capabilities by running a script.

Tip: When you use the cp4a-prerequisites.sh script, you must review the requirements in the documented steps to create a database. Make sure that the databases that you create satisfy your intended workload. For deployments that need to operate continuously with no interruptions in service, set up a high availability (HA) database.

1. Optional: You can create your databases and secrets without running the provided scripts.
   Restriction: If you previously installed another pattern that includes Business Automation Studio, you do not need to configure a new database for Business Automation Studio. Otherwise, PostgreSQL is the only database supported for Workflow Process Service Authoring.

   By default, EDB Postgres will be provisioned for Workflow Process Service Authoring. If you want to manually configure your own PostgreSQL database, you can use the script in step 2 and 3 in Creating PostgreSQL databases.
2. By default, dynamic provisioning is enabled when you deploy. If your environment supports dynamic provisioning, you can skip the rest of step 2 and step 3. If your environment does not support dynamic provisioning, complete the following steps to create persistent volumes (PVs) manually.

   To enable persistent storage for the server logs, dump files, or index files for Business Automation Studio, you can either use dynamic provisioning that you already set up in your cluster, or you can create the PV manually.

   Disable dynamic provisioning by setting bastudio_configuration.storage.enabled to false. Then, create the required PVs and persistent volume claims (PVCs) manually and set bastudio_configuration.storage.existing_pvc_for_logstore to the name of the log PVC and bastudio_configuration.storage.existing_pvc_for_dumpstore to the name of the dump PVC. The persistent storage configuration of index files is different from that of server logs and dump files.

3. Create a PV for the Workflow Process Service Authoring file store. 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.

   • 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 PV and PVC manually and set workflow_authoring_configuration.storage.existing_pvc_for_filestore to the name of the generic file PVC.

4. If you selected the optional IBM Business Automation Insights component, complete the following steps to configure it:
   1. Make sure that you complete all the steps in Preparing to install IBM Business Automation Insights.
   2. Optional: If you want Business Automation Insights to capture events from BPMN processes for further processing, install and configure the BPM event emitter application for Workflow Process Service Authoring. For more information, see Installing and configuring the BPM event emitter.