You might want to configure multiple Business Automation Workflow server instances to manage different
configurations or separate groups of applications. If you are running both Workflow and Workstreams
capabilities, it is a good idea to run them on separate server instances. You can have multiple
Workflow instances but you can have only one Workstreams instance.
About this task
To configure multiple server instances, you must duplicate the Business Automation Workflow sections in the custom resource YAML
file, prepare the databases, storage, and secrets for each server instance, and provide that
information to the instance configuration sections in the custom resource.
Intelligent Task Prioritization is deployed by default and
integrated with the Workflow server instance that hosts federated Process Portal. Workforce Insights is deployed by default and integrated
with all Workflow server instances.
Procedure
- Duplicate the Business Automation Workflow sections in the custom
resource YAML file for the number of server instances you want, making sure that
you set only one instance to
host_federated_portal: true.
This example shows three server instances.
baw_configuration:
- name: instance1
host_federated_portal: true
service_type: "Route"
hostname:
port: 443
...
# ----------------------------------------------------------------------------------------
# custom configuration in Liberty server.xml
# ----------------------------------------------------------------------------------------
custom_xml_secret_name:
# ----------------------------------------------------------------------------------------
# custom configuration in 100Custom.xml
# ----------------------------------------------------------------------------------------
- name: instance2
host_federated_portal: false
service_type: "Route"
hostname:
port: 443
...
# ----------------------------------------------------------------------------------------
# custom configuration in Liberty server.xml
# ----------------------------------------------------------------------------------------
custom_xml_secret_name:
# ----------------------------------------------------------------------------------------
# custom configuration in 100Custom.xml
# ----------------------------------------------------------------------------------------
- name: instance3
host_federated_portal: false
service_type: "Route"
hostname:
port: 443
...
# ----------------------------------------------------------------------------------------
# custom configuration in Liberty server.xml
# ----------------------------------------------------------------------------------------
custom_xml_secret_name:
# ----------------------------------------------------------------------------------------
# custom configuration in 100Custom.xml
# ----------------------------------------------------------------------------------------
- Repeat the preparation work for each Business Automation Workflow server instance you want.
For
each instance:
- Repeat the instructions in Preparing databases and secrets for your chosen capabilities by running a
scriptor Creating required databases and secrets without running the provided scripts.
- Repeat the instructions in Preparing storage.
- Repeat the instructions in Creating secrets to protect sensitive configuration data.
- Add the newly created database, storage, and secrets information to the corresponding
Business Automation Workflow server instance configuration
sections in the custom resource.
-
Ensure that each Business Automation Workflow instance has its own
object store for content integration. The same content integration object store cannot be used for
multiple Workflow instances. Each instance also requires its own Transport Layer Security (TLS)
secret.
You must set different values for these parameters in the custom resource YAML file for each instance:
baw_configuration.content_integration.object_store_name
baw_configuration.tls.tls_secret_name
Also ensure that
- The
oc_cpe_obj_store_asa_root_dir_path for each object stores is unique.
- Each
dc_os_label has a related dbusername and
dbpassword defined in the ibm-fncm-secret.
- The
oc_cpe_obj_store_conn.name is unique for each object store.
- Each instance has its own admin secret:
admin_secret_name: '{{ meta.name
}}-instance1-baw-admin-secret'
-
For all instances except the first one, delete the case subsection, which is the subsection
that contains the
baw_configuration[x].case parameters.
- Case Manager supports only one Business Automation Workflow server instance. Make
sure you remove all the case-related entries from the other Business Automation Workflow server instances.
- Workstreams does not support multiple server instances either.