Customizing Business Automation Workflow with multiple target object stores

You can configure more than one target object store for case management.

About this task

You can add additional target object stores by updating the Custom Resource (CR) file to include the additional target object store under the baw_configuration section for IBM® Business Automation Workflow Runtime and workflow_authoring_configuration for IBM Business Automation Workflow Authoring and by updating the target object store configuration under the initialize_configuration section and datasource_configuration sections.

Procedure

To create an additional target object store:

Follow the steps in Adding additional object stores post deployment for adding more object stores.
Use the existing target object store configuration as a guide to fill in the values for the required parameters under initialize_configuration.ic_obj_store_creation.object_stores.

Compared to object stores, target object stores require the following additional parameters:

oc_cpe_obj_store_enable_workflow: true
oc_cpe_obj_store_workflow_data_tbl_space: 
oc_cpe_obj_store_workflow_admin_group:
oc_cpe_obj_store_workflow_config_group:

Create the database and tablespace that are required by the target object store.
Edit the CR file and add the additional target object store to baw_configuration.case.tos_list for Business Automation Workflow Runtime and workflow_authoring_configuration.case.tos_list for Business Automation Workflow Authoring.
A Business Automation Workflow Runtime example:
```
baw_configuration:
-  name: instance1
   case: 
      tos_list:
          - object_store_name: "TOS1"
            connection_point_name: "cpe_conn_tos1"
            desktop_id: "navigator_desktop_id"
            target_environment_name: "project_area_name_or_target_env_name_1"
            is_default: true
          - object_store_name: "TOS2"
            connection_point_name: "cpe_conn_tos2"
            desktop_id: "navigator_desktop_id"
            target_environment_name: "project_area_name_or_target_env_name_2"
            is_default: false
```
A Business Automation Workflow Authoring example:
```
workflow_authoring_configuration:
  case: 
    tos_list:
    - object_store_name: "BAWTOS"
      connection_point_name: "pe_conn_target"
      desktop_id: "baw"
      target_environment_name: "dev_env_connection_definition"
      is_default: true
    - object_store_name: "TOS2"
      connection_point_name: "pe_conn_tos2"
      desktop_id: "tos2"
      target_environment_name: "project_area_name_or_target_env_name_2"
      is_default: false
```
Notes:
- Make sure that the value of tos_list.connection_point_name is the same as the value of oc_cpe_obj_store_workflow_pe_conn_point_name in the same object store.
- The value of target_environment_name must be different for each target object store.
- (For Business Automation Workflow Authoring only) If there is only one target object store, the value of target_environment_name must be dev_env_connection_definition. It will be set as the default. If there are multiple target object stores, the target_environment_name of the default target object store (is_default:true) must be dev_env_connection_definition.
- The URL of the Case client is displayed in the access information ConfigMap and CR endpoints only if the value of desktop_id is defined in the CR. If not, users can find other desktops in the desktop list page of the IBM Business Automation Navigator.
Apply the updated CR.