Advanced configuration of Workflow Authoring

Edit online

The following instructions help you complete the Advanced Configuration for Workflow Authoring in the OpenShift Installed Operators user interface.

For a starter deployment, set Automation Workflow/Workstream Services (olm_starter_workflow) to true and choose the optional components that you want to include.

For a production deployment, set Automation Workflow/Workstream Services (olm_custom_workflow) to true, and for Workflow Install Type, select workflow-authoring.

Advance Configuration:

LDAP Configuration: LDAP configuration is required.

Database Configuration:

Datasource	Description
GCD Datasource Configuration	This configuration is required.
Content Management OS Datasource Configuration	This configuration is required only if you are installing the FileNet Content Manager pattern.
Workflow OS Datasource Configuration	Three datasources, BAWDOCS, BAWDOS, and BAWTOS, are required.
Application Engine OS Datasource Configuration	This configuration is required only if you want to enable data persistence.
Navigator Datasource Configuration	This configuration is required.
ODM Datasource Configuration	This configuration is required only if you are installing the Operational Decision Manager pattern.
CA Datasource Configuration	This configuration is required only if you are installing the Automation Document Processing pattern.

Initialization Configuration:

LDAP configuration: This configuration is required.

Create Object Store Configuration:

Object store	Description
BAWDOCS	Use the default settings unless you changed them when configuring the database. Object Store Admin User groups is required.
BAWDOS	Use the default settings unless you changed them when configuring the database. Object Store Admin User groups is required.
BAWTOS	Use the default settings unless you changed them when configuring the database. Enter the values for Object Store - table space, Object Store - Workflow admin group, Object Store - Workflow config group and Object Store - Connection point for Workflow. Object Store Admin User groups is required.
AEOS	This configuration is required only if you want to enable data persistence. Object Store Admin User groups is required.

Navigator Initialization Configuration: This configuration is not required.

Business Automation Studio Configuration: This configuration is required.
Application Engine Configuration: This configuration is required. If you want to add Redis for high availability, add the following information before you configure an instance.
1. Change the configuration page from Form View to YAML View.
2. Find the one instance of the application_engine_configuration section and copy the required information into it.
```
session:
  use_external_store: true
redis:
  # Your external redis host/ip
  host:
  # Your external redis port
  port: '6379'
  # If your redis enabled TLS connection set this to true
  # You should add redis server CA certificate in tls_trust_list or trusted_certificate_list
  tls_enabled: false
```
Workflow Authoring Configuration: This configuration is required.
To configure and activate the Business Automation Machine Learning Server capabilities, including Intelligent Task Prioritization and Workforce Insights, switch to the YAML View and add the BAML configurations according to Completing configuration for Machine Learning Server. You must configure Business Automation Insights as described earlier because it is required by Machine Learning Server.

Optional Components:

Enable Data Persistence Data persistence is optional. For information, see Optional: Configuring Application Engine with data persistence.
Business Automation Insights This configuration is optional. It is required for Machine Learning Server. If you enabled Business Automation Insights and want to install and configure the emitter that you need to send raw events to ingestion jobs, add the following information before you create an instance.
1. Change the configuration page from Form View to YAML View.
2. Find the workflow_authoring_configuration section and copy the required information into it.
  To install and configure the BPMN event emitter:
```
##  IBM Business Automation Insights integration configuration
    business_event:
      enable: true
      enable_task_record: true
      enable_task_api: true
      subscription:
      - {'app_name': '*','version': '*','component_type': '*','component_name': '*','element_type': '*','element_name': '*','nature': '*'}
```
  For information about the BPMN event emitter, see Installing and configuring the BPM event emitter.
  To install and configure the case event emitter:
```
## The event emitter settings if you want to enable Case Event Emitter
      event_emitter:
        date_sql: 
        logical_unique_id: 
        solution_list: '*'
```
  For information about the case event emitter, see Installing and configuring the case event emitter.
  To install and configure the case history emitter:
```
## The case history emitter configuration
       case_history_emitter:
        enable: true
        case_history_store_schema_name: CHSCHEMA
        dc_common_cpe_datasource_name: CASEHISTORYDS
```
  For information about the case history emitter, see Optional: Enabling the Timeline Visualizer widget to display Business Automation Workflow process activity flow.

Remember:

Machine Learning Server (including Intelligent Task Prioritization and Workforce Insights) is not supported on Linux on IBM Z.
You can use the parameter descriptions in IBM Business Automation Workflow Authoring parameters to help you add more configurations.
You can copy and paste parameters from the custom resource (CR) custom pattern templates in the YAML View and edit the parameters.
You can edit the CR file in the editor, but it is best if you have the CR complete and verified before you save your changes in the editor. For example, go to http://www.yamllint.com/ to verify the contents of your file.