IBM Business Automation Workflow Runtime and Workstream Services parameters

Each container needs a set of values for its configuration parameters to create a Kubernetes deployment. The following tables provide the description and default value for each parameter. Complete the custom resource YAML file for your deployment by supplying values for your environment and configuration.

The following tables list the configurable parameters and their default values. All properties are mandatory, unless they have a default value or are explicitly optional. Although the containers might seem to install correctly when some parameters are omitted, this kind of configuration is not supported.

Shared configuration parameters

See Shared configuration parameters. The pattern configuration parameters, LDAP configuration parameters, and all mandatory shared configuration parameters (including sc_deployment_baw_license) are required.

Resource Registry configuration parameters

For Resource Registry parameters, see the Resource Registry table in IBM Business Automation Application Engine parameters.

Business Automation Navigator configuration parameters

See IBM Business Automation Navigator parameters.

FileNet Content Manager configuration parameters

See IBM FileNet Content Manager parameters.

Business Automation Insights configuration parameters

See IBM Business Automation Insights parameters. Business Automation Insights is not available for stand-alone Business Automation Workflow on containers.

Application Engine configuration parameters

See IBM Business Automation Application Engine parameters.

Business Automation Workflow configuration parameters

Provide the details that are relevant to your Business Automation Workflow environment and your decisions for the deployment of the container.

The following tables list the parameters for configuring Business Automation Workflow:

Workflow Server configuration parameters

You can deploy multiple instances of Workflow Server and assign different configurations for each instance. For each instance, baw_configuration.name and baw_configuration.name.hostname must have different values. Keep the instance name as short as possible to avoid running into line length problems.

For each instance's database configuration, you can choose to use either different database instances, or one shared database instance. If you use a shared database instance:
  • In Db2 or PostgreSQL, you must assign different database names (baw_configuration[x].database.database_name)
  • In Oracle, you must assign different database users (the dbUser in the baw_configuration[x].database.secret_name)
For baw_configuration.tls.tls_secret_name, if you choose to use a customized Workflow Server TLS certificate, ensure that each instance has a different value.

The following table lists the parameters for configuring Workflow Server. The Required column shows the parameters that are required.

Table 1. Workflow Server configuration parameters (baw_configuration)
Parameter name Description Example values Required
name Name of the instance. The name for each item in the array must be different. The name can consist of lowercase alphanumeric characters or '-', and must start and end with an alphanumeric character. Keep the instance name short. The default value is instance1. instance1 No
host_federated_portal For Workflow only: Whether the Business Automation Workflow instance hosts federated Process Portal and integrates with Intelligent Task Prioritization. The default value is true. true No
federated_portal. content_security_policy_additional_origins For Workflow only: Content security policy additional origins for federating Business Automation Workflow traditional systems. For example, ["https://on-prem-baw1","https://on-prem-baw2"]. [] No
service_type Workflow Server service type. The default value is Route. Route No
hostname baw-server route hostname. If the hostname is not set, a default hostname with the following format is used.
baw-<BAW instance name>-<shared_configuration.sc_deployment_hostname_suffix>
This parameter is used only by stand-alone Business Automation Workflow on containers.		   No
port Workflow Server port. The default value is 443. 443 No
nodeport Workflow Server node port. The default value is 30026. 30026 No
env_type Workflow Server environment type. The default value is Production. Production, Staging, Test, Development No
capabilities Workflow Server capability. Valid values are workflow, workstreams, and workflow,workstreams. workflow Yes
replicas Workflow Server replica count. The default value is 1. 1 No
admin_user Designate an existing LDAP user to be given Workflow Server admin rights. Yes
admin_secret_name The name of Workflow Server admin secret. This secret name is optional. If the secret name is null, a default secret named <name>-<instance_name>-baw-admin-secret is generated, where <name> is the name of the custom resource that is used to generate the deployment environment. <name>-<instance-name>-baw-admin-secret No
monitor_enabled Whether to use the built-in monitoring capability. The default value is false. false No
customized_portal_endpoint For Workflow only: Required if you implemented your own portal. For example, https://portal.mycompany.com. No
external_connection_timeout External connection timeout. The default value is 60s. 60s No
external_tls_secret This parameter is used only by stand-alone Business Automation Workflow on containers. For the baw-server route, the name of the secret that contains the certificates and Transport Layer Security (TLS) private key to be used for the route. If you set this parameter, the setting overrides the default generated certificate and the shared setting for route certificates. If you need to customize the route's certificate, create a secret using the following command and set the secret name to the property.
kubectl create secret generic ext-tls-crt-secret --from-file=tls.crt=<path to crt file> --from-file=tls.key=<path to key file>
The crt file must contain the route certificate followed by any intermediate CA signer certificates and the root CA signer certificate in an unencrypted PEM format. The key file must also be in unencrypted PEM format.		 No
external_tls_ca_secret This parameter is used only by stand-alone Business Automation Workflow on containers. For the baw-server route, provide the name of the secret containing the root CA certificate that signed the route certificate. If a customized secret for external_tls_secret is provided, you must also set the external_tls_ca_secret using the following command.
kubectl create secret generic ext-tls-ca-crt-secret --from-file=tls.crt=<path to crt file>
The crt file should contain the root CA signer certificate in an unencrypted PEM format.		 No
tls.tls_secret_name Workflow Server TLS secret that contains the tls.key and tls.crt keys. If you want to use a customized Workflow Server TLS certificate, ensure it is signed by the CA in shared_configuration.root_ca_secret and that each instance has a different value. If you don't want to use a customized certificate, leave it empty and the operator will create one automatically. The default value is <cr_name>-<instance_name>-baw-tls-secret. <cr_name>-<instance_name>-baw-tls-secret No
tls.tls_trust_list Workflow Server TLS trust list. No
tls.tls_trust_store Secret to store your custom trusted keystore (optional). The type for the keystore must be JKS or PKCS12. All certificates from the keystore are imported into the trust keystore of the Workflow server. You might run the following sample command to create the secret: 
kubectl create secret generic baw_custom_trust_keystore_secret --from-file=truststorefile=./trust.jks --from-literal=type=JKS --from-literal=password=WebAS
   No
image.repository Workflow Server (Process Server) image repository URL. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/workflow-server where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/workflow-server No
image.tag Image tag for Workflow Server container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3 No
image.pullPolicy Pull policy for Workflow Server container. The default value is IfNotPresent. IfNotPresent, Always No
pfs_bpd_database_init_job.repository Database initialization image repository URL for Process Federation Server. The default value is <path>/pfs-bpd-database-init-prod where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/pfs-bpd-database-init-prod No
pfs_bpd_database_init_job.tag Database initialization image repository tag for Process Federation Server. The default value is 21.0.3. 21.0.3 No
pfs_bpd_database_init_job.pullPolicy Pull policy for Process Federation Server database initialization image. The default value is IfNotPresent. IfNotPresent, Always No
upgrade_job.repository Workflow Server database handling image repository URL. The default value is <path>/workflow-server-dbhandling where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/workflow-server-dbhandling No
upgrade_job.tag Workflow Server database handling image repository tag. If you want to use a specific image version, you can override the default tag or digest. 21.0.3 No
upgrade_job.pullPolicy Pull policy for database handling. The default value is IfNotPresent. IfNotPresent, Always No
upgrade_job.trace_specification Trace specification for the Workflow Server database handling job. The default value is *.=finer. .=info:WLE.wle.=fine:com.ibm.workflow.*=finest No
bas_auto_import_job.repository Workflow Server Business Automation Studio toolkit init image repository URL. The default value is <path>/toolkit_installer where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/toolkit_installer No
bas_auto_import_job.tag Workflow Server Business Automation Studio toolkit init image repository tag. If you want to use a specific image version, you can override the default tag or digest. 21.0.3 No
bas_auto_import_job.pullPolicy Pull policy for Business Automation Studio toolkit init image.   No
ibm_workplace_job.repository IBM Workplace deployment image repository URL. The default value is <path>/iaws-ibm-workplace where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository is configured, <path> is the same value. <path>/iaws-ibm-workplace  
ibm_workplace_job.tag IBM Workplace deployment image repository tag. If you want to use a specific image version, you can override the default tag or digest. The default value is 22.0.1.  22.0.1  
ibm_workplace_job.pull_policy Pull policy for the IBM Workplace deployment image.    
database.enable_ssl Whether to enable Secure Sockets Layer (SSL) support for the Workflow Server database connection. The default value is false. false No
database.db_cert_secret_name Secret name for storing the database TLS certificate when an SSL connection is enabled.   Yes
database.type Workflow Server database type. The default value is DB2® DB2 Yes
database.server_name Workflow Server database server name. It must be an accessible address, such as an IP, hostname, or Kubernetes service name.   Yes
database.database_name Workflow Server database name.   Yes
database.port Workflow Server database port. For Db2, the default is 50000. For Oracle, the default is 1521. Yes
database.secret_name Workflow Server database secret name.   Yes
database.jdbc_url Oracle and PostgreSQL database connection string. This parameter is not required for PostgreSQL if you enter server_name, database_name, and port. For Oracle: jdbc:oracle:thin:@//<oracle_server>:1521/orcl

For PostgreSQL: jdbc:postgresql://<postgresql_server>:5432/<your_database>

 No
database.use_custom_jdbc_drivers Whether to use custom JDBC drivers. Set to true if you are using Oracle, PostgreSQL, or a special Db2® driver. The default value is false. false No
database.custom_jdbc_pvc Name of the persistent volume claim (PVC) that binds to the persistent volume (PV) where the custom JDBC driver files are stored. Yes
database.jdbc_driver_files The set of JDBC driver files. The default value is:
db2jcc4.jar
db2jcc_license_cisuz.jar
db2jcc_license_cu.jar
 
db2jcc4.jar
db2jcc_license_cisuz.jar
db2jcc_license_cu.jar
 No
database.cm_max_pool_size Workflow server database connect pool maximum number of physical connections. The default value is 200. 200 No
database.dbcheck.wait_time The maximum wait time (in seconds) to check the database initialization status. The default value is 900. 900 No
database.dbcheck.interval_time The interval time (in seconds) to check the database initialization status before the database is ready and bootstrapped with system data. The default value is 15. 15 No
database.hadr.standbydb_host Database standby host for high availability disaster recovery (HADR). To enable database HADR, configure both standby host and port. No
database.hadr.standbydb_port Database standby port for HADR. To enable database HADR, configure both standby host and port. No
database.hadr.retryinterval Retry interval for HADR. No
database.hadr.maxretries Maximum retries for HADR. No
workflow_center.url For Workflow only: The URL of Workflow Center.   No
workflow_center.secret_name For Workflow only: The secret name of Workflow Center that contains username and password.   No
workflow_center.heartbeat_interval For Workflow only: Heartbeat interval (seconds) to connect to Workflow Center. The default value is 30. 30 No
workflow_center.webpd_url For Workflow only: URL that is used by Workflow Center to link to the web Process Designer. For example, https://hostname:port/WebPD.   No
appengine.hostname Hostname of Application Engine. The value must be the same as application_engine_configuration[x].hostname.   No
appengine.admin_secret_name Secret name of Application Engine. The value must be the same as application_engine_configuration[x].admin_secret_name.   No
content_integration.init_job_image.repository Image name for content integration container. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/iaws-ps-content-integration where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/iaws-ps-content-integration No
content_integration.init_job_image.tag Image tag for content integration container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3 No
content_integration.init_job_image.pull_policy Pull policy for content integration container. The default value is IfNotPresent. IfNotPresent, Always No
content_integration.domain_name Domain name for content integration. The value must be the same as initialize_configuration.ic_domain_creation.domain_name. The default value is P8DOMAIN. P8DOMAIN No
content_integration.object_store_name Object Store name for content integration.   No
content_integration.cpe_admin_secret Admin secret for connecting to Content Platform Engine (CPE). This parameter is optional. If not set, it will autodetect CPE's admin secret in the same namespace.   No
case.init_job_image.repository For Workflow only: Image name for CASE init job container. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/workflow-server-case-initialization where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/workflow-server-case-initialization No
case.init_job_image.tag For Workflow only: Image tag for CASE init job container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3 No
case.init_job_image.pull_policy For Workflow only: Pull policy for CASE init job container. The default value is IfNotPresent. IfNotPresent, Always No
case.domain_name For Workflow only: Domain name for CASE. The value must be the same as initialize_configuration.ic_domain_creation.domain_name. The default value is P8DOMAIN. P8DOMAIN No
case.object_store_name_dos For Workflow only: Design Object Store name of CASE. The value must be the same as the oc_cpe_obj_store_symb_name value of one of the object stores defined in initialize_configuration.ic_obj_store_creation.object_stores. The default value is DOS. DOS No
case.object_store_name_tos For Workflow only: Target Object Store name of CASE. The value must be the same as the oc_cpe_obj_store_symb_name value of one of the object stores defined in initialize_configuration.ic_obj_store_creation.object_stores. The default value is TOS. TOS No
case.connection_point_name_tos For Workflow only: Connection point name for Target Object Store. See initialize_configuration.ic_obj_store_creation.object_stores[x].oc_cpe_obj_store_workflow_pe_conn_point_name. If oc_cpe_obj_store_workflow_pe_conn_point_name is not specified explicitly, the default value is pe_conn_<TOS_OS_DB_NAME>. cpe_conn_tos Required if the Target Object Store does not exist in initialize_configuration.ic_obj_store_creation.object_stores.
case.datasource_name_tos For Workflow only: Name of the non-XA datasource of the Target Object Store (from dc_common_os_datasource_name in the dc_os_datasources section). This name is not used if the Target Object Store exists in initialize_configuration.ic_obj_store_creation.object_stores. FNDSTOS Required if the Target Object Store does not exist in initialize_configuration.ic_obj_store_creation.object_stores.
case.target_environment_name For Workflow only: Name of the target environment or project area to register with the case components and associate with an IBM Content Navigator desktop. The default value is target_env. target_env No
case.network_shared_directory_pvc For Workflow only: Persistent volume claim (PVC) name for case network shared directory. If navigator_configuration.datavolume.existing_pvc_for_icn_pluginstore is not specified explicitly, the default value is icn-pluginstore. See IBM Business Automation Navigator parameters. icn_pluginstore No
case.custom_package_names For Workflow only: Custom package names for installing custom packages, where the value format is similar to package1.zip, package2.zip.   No
case.custom_extension_names For Workflow only: Custom extension names for installing custom packages, where the value format is similar to extension1.zip, extension2.zip.   No
cpe_metadata_cache_time_to_live For Workflow only: Number of seconds before a newly added or modified asset will take effect in the Case Client. The value must be an integer. A default value is used at run time if this parameter is not set. 100 No
resources.limits.cpu CPU limit for Workflow Server. The default value is 2. 2 No
resources.limits.memory Memory limit for Workflow Server. The default value is 2096Mi. 2096Mi No
resources.requests.cpu Requested amount of CPU for Workflow Server. The default value is 500m. 500m No
resources.requests.memory Requested amount of memory for Workflow Server. The default value is 1048Mi. 1048Mi No
probe.ws.liveness_probe.initial_delay_seconds Number of seconds after the Workflow Server container starts before the liveness probe is initiated. The default value is 360. 360 No
probe.ws.liveness_probe.period_seconds Number of seconds to wait before the next probe. The default value is 10. 10 No
probe.ws.liveness_probe.timeout_seconds Number of seconds after which the probe times out. The default value is 10. 10 No
probe.ws.liveness_probe.failure_threshold When a probe fails, number of times that Kubernetes tries before it gives up and restarts the container. The default value is 3. 3 No
probe.ws.liveness_probe.success_threshold Minimum consecutive successes for the probe to be considered successful after it failed. The default value is 1. 1 No
probe.ws.readinessProbe.initial_delay_seconds Number of seconds after the Workflow Server container starts before the readiness probe is initiated. The default value is 360. 360 No
probe.ws.readiness_probe.period_seconds Number of seconds to wait before the next probe. The default value is 5. 5 No
probe.ws.readiness_probe.timeout_seconds Number of seconds after which the probe times out. The default value is 5. 5 No
probe.ws.readiness_probe.failure_threshold When a probe fails, number of times that Kubernetes tries before it marks the pod as unready. The default value is 6. 6 No
probe.ws.readiness_probe.success_threshold Minimum consecutive successes for the probe to be considered successful after it failed. The default value is 1. 1 No
logs.console_format Format for printing logs on the console. The default value is json. json No
logs.console_log_level Log level for printing logs on the console. The default value is INFO. INFO No
logs.console_source Source of the logs for printing on the console. The default values are message, trace, accessLog, ffdc, audit. message, trace, accessLog, ffdc, audit No
logs.message_format Required format for the messages.log file. The default value is SIMPLE. SIMPLE, JSON No
logs.trace_format Format of the trace log. The default value is ENHANCED. BASIC, ADVANCED, ENHANCED No
logs.trace_specification Specification for printing trace logs. The default value is *=info|. *=info| No
logs.max_files Maximum number of log files that are kept before the oldest file is removed. The default value is 10. 10 No
logs.max_filesize Maximum size (in MB) that a log file can reach before it is rolled. The default value is 50. 50 No
storage.use_dynamic_provisioning Set to true to use dynamic storage provisioning. If set to false, you must set existing_pvc_for_logstore and existing_pvc_for_dumpstore. The default value is true. true No
storage.existing_pvc_for_logstore Persistent volume claim (PVC) for logs.   No
storage.size_for_logstore Minimum size of the persistent volume (PV) that is mounted as the log store. The default value is 1Gi. 1Gi No
storage.existing_pvc_for_dumpstore PVC for dump files.   No
storage.size_for_dumpstore Minimum size of the PV that is mounted as the dump store. The default value is 5Gi. 5Gi No
storage.existing_pvc_for_filestore PVC for files. This includes temporary files that are created by the SQL integration facility Invoking SQL Integration services.   No
storage.size_for_filestore Minimum size of the PV that is mounted as the file store. The default value is 1Gi. 1Gi No
autoscaling.enabled Whether to enable automatically scaling the number of pods. The default value is false. false No
autoscaling.max_replicas Upper limit for the number of pods that can be set by the autoscaler. If it is not specified or negative, the server uses the default value. The default value is 3. 3 No
autoscaling.min_replicas Lower limit for the number of pods that can be set by the autoscaler. If it is not specified or negative, the server uses the default value. The default value is 2. 2 No
autoscaling.target_cpu_utilization_percentage Target average CPU utilization (represented as a percent of requested CPU) over all the pods. If it is not specified or negative, the default is used. The default value is 80. 80 No
environment_config. show_task_prioritization_service_toggle For Workflow only: Whether to show the Intelligent Task Prioritization service toggle button in the web user interface to allow the user to enable or disable this service. This parameter is valid only for the first Workflow instance. The default value is false. false No
environment_config. always_run_task_prioritization_service For Workflow only: Whether to display the Intelligent Task Prioritization service toggle button. If this parameter is set to true, the previous parameter is ignored. This parameter is valid only for the first Workflow instance. The default value is false. false No
environment_config.csrf.origin_whitelist Security-hardening property that protects against Cross-Site Request Forgery (CSRF) attacks. Specify the values that are acceptable in the origin header field of an incoming request. The value of this property must be a comma-separated list of prefixes. https://example.com, http://example2.com:8080 No
environment_config.csrf.referer_whitelist Security-hardening property that protects against CSRF attacks. Specify the values that are acceptable in the referer header field of an incoming request. The value of this property must be a comma-separated list of fully qualified host names. example1.com, example2.com No
environment_config.csrf.user_agent_keyword_white_list_for_old_restapi_csrf_check Comma-separated list of user agents. For the REST API requests with the path pattern /rest/bpm/wle/v1/* that is sent by the agents in the list, the server will not validate the XSRF-TOKEN cookie. The value of this property must be a comma-separated list, for example, agentkeyworkd1, agentkeyworkd2. java,wink client,httpclient,curl,jersey,httpurlconnection No
environment_config.csrf.check_xsrf_for_old_restapi Whether to validate the XSRF-TOKEN cookie against incoming REST API requests (POST/PUT/DELETE) with the path pattern /rest/bpm/wle/v1/*. The default value is true. true No
federation_config.workflow_server. index_number_of_shards Number of primary shards of the Elasticsearch index used to store Workflow server data. The default value is 3. 3 No
federation_config.workflow_server. index_number_of_replicas Number of shard replicas of the Elasticsearch index used to store Workflow server data. The default value is 1. 1 No
federation_config.case_manager[x]. object_store_name For Workflow only: Case Manager object store name. The default value is TOS. TOS No
federation_config.case_manager[x]. index_number_of_shards For Workflow only: Number of primary shards of the Elasticsearch index used to store Case Manager object store data. The default value is 3. 3 No
federation_config.case_manager[x]. index_number_of_replicas For Workflow only: Number of shard replicas of the Elasticsearch index used to store Case Manager object store data. The default value is 1. 1 No
jvm_customize_options JVM options separated with spaces, for example: -Dtest1=test -Dtest2=test2.   No
liberty_custom_xml Workflow Server custom plain XML snippet. The custom_xml_secret_name is also used for Workflow Server customization. Put your configuration values either in liberty_custom_xml or custom_xml_secret_name. Do not set the configuration value in both places.   No
custom_xml_secret_name Workflow Server custom XML secret name. The liberty_custom_xml is also used for Workflow Server customization. Put your configuration values either in liberty_custom_xml or custom_xml_secret_name. Do not set the same configuration value in both places.   No
lombardi_custom_xml_secret_name Workflow Server Lombardi custom XML secret name.   No

Java Message Service (JMS) configuration parameters

The following table lists the parameters for configuring JMS. All parameters are optional.

Table 2. Java Message Service (JMS) configuration parameters (baw_configuration)
Parameter name Description Example values
jms.image.repository Image name for JMS container. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/jms where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/jms
jms.image.tag Image tag for JMS container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3
jms.image.pull_policy Pull policy for JMS container. Possible values are IfNotPresent and Always. The default value is IfNotPresent. IfNotPresent, Always
jms.tls.tls_secret_name TLS secret name for JMS. The default value is ibm-jms-tls-secret. ibm-jms-tls-secret
jms.resources.limits.memory Memory limit for JMS configuration. The default value is 2Gi. 2Gi
jms.resources.limits.cpu CPU limit for JMS configuration. The default value is 1000m. 1000m
jms.resources.requests.memory Requested amount of memory for JMS configuration. The default value is 512Mi. 512Mi
jms.resources.requests.cpu Requested amount of CPU for JMS configuration. The default value is 200m. 200m
jms.storage.persistent Whether to enable persistent storage for JMS. The default value is true. true
jms.storage.size Size for JMS persistent storage. The default value is 1Gi. 1Gi
jms.storage.use_dynamic_provisioning Whether to enable dynamic provisioning for JMS persistent storage. The default value is true. true
jms.storage.access_modes Access modes for JMS persistent storage. Refer to Kubernetes documentation for available options. The default value is ReadWriteOnce. ReadWriteOnce
jms.storage.storage_class Storage class name for JMS persistent storage. The default value is shared_configuration.storage_configuration. sc_fast_file_storage_classname. shared_configuration.storage_configuration. sc_fast_file_storage_classname
jms.liveness_probe.initial_delay_seconds Number of seconds after the container starts before the liveness probe is initiated. The default value is 180. 180
jms.liveness_probe.period_seconds How often (in seconds) to perform the probe. The default value is 20. 20
jms.liveness_probe.timeout_seconds Number of seconds after which the probe times out. The default value is 10. 10
jms.liveness_probe.failure_threshold When a pod starts and the probe fails, Kubernetes tries this number of times before giving up. The minimum value is 1. The default value is 3. 3
jms.liveness_probe.success_threshold Minimum consecutive successes for the probe to be considered successful after failing. The minimum value is 1. The default value is 1. 1
jms.readiness_probe.initial_delay_seconds Number of seconds after the container starts before the readiness probe is initiated. The default value is 30. 30
jms.readiness_probe.period_seconds How often (in seconds) to perform the probe. The default value is 5. 5
jms.readiness_probe.timeout_seconds Number of seconds after which the probe times out. The default value is 5. 5
jms.readiness_probe.failure_threshold When a pod starts and the probe fails, Kubernetes tries this number of times before giving up. Minimum value is 1. The default value is 6. 6
jms.readiness_probe.success_threshold Minimum consecutive successes for the probe to be considered successful after failing. Minimum value is 1. The default value is 1. 1
jms.startup_probe.period_seconds How often (in seconds) to perform the startup probe. The default value is 10. 10
jms.startup_probe.timeout_seconds Number of seconds after which the startup probe times out. The default value is 10. 10
jms.startup_probe.failure_threshold When a pod starts and the startup probe fails, Kubernetes tries this number of times before giving up. The minimum value is 1. The default value is 20. 20
jms.startup_probe.success_threshold Minimum consecutive successes for the startup probe to be considered successful after it fails. The minimum value is 1. The default value is 1. 1

BPM event emitter configuration parameters

The following table lists the parameters for configuring BPM event emitter. All parameters are optional.

Table 3. BPM event emitter configuration parameters (baw_configuration)
Parameter name Description Example values Required
business_event.enable Whether to enable event monitoring for Dynamic Event Framework events for the Workflow Services container. If Business Automation Insights and the Machine Learning Server parameters are configured, this parameter must be set to true. The default value is false. false No
business_event.enable_task_api Whether to record additional task information in generated events. If Business Automation Insights and the Machine Learning Server parameters are configured, this parameter must be set to true. This parameter is equivalent to the enable_task_api_def parameter. See BPMN summary event formats. The default value is false. false No
business_event.enable_task_record Whether to enable the task record in generated events. This optional parameter is equivalent to the task-record-enabled parameter. See BPMN summary event formats. The default value is true. true No
business_event.subscription List of the subscription configurations. Each subscription attribute is listed in the rest of this table.
 [{'app_name': '*','version': '*','component_type': '*','component_name': '*','element_type': '*','element_name': '*','nature': '*'}]
See Event point key and filter.		   No
business_event.subscription[x].app_name Name of the application that is the source of the events that are to be monitored.   No
business_event.subscription[x].component_name Name of the component to be monitored.   No
business_event.subscription[x].component_type Type of the component to be monitored.   No
business_event.subscription[x].element_name Name of the element to be monitored.   No
business_event.subscription[x].element_type Type of element to be monitored. BPMN types are PROCESS, ACTIVITY, EVENT, and GATEWAY.   No
business_event.subscription[x].nature Nature of the event. One element can send events of various natures, such as STARTED, ACTIVE, COMPLETED. The BPMN nature categories are STARTED, COMPLETED, TERMINATED, DELETED, FAILED, CAUGHT, THROWN, EXPECTED, ACTIVE, READY, RESOURCE_ASSIGNED, ACTIVE, LOOP_CONDITION_TRUE, LOOP_CONDITION_FALSE, and MULTIPLE_INSTANCES_STARTED.   No
business_event.subscription[x].version Version of the application to be monitored.   No
To enable event monitoring for Dynamic Framework Events, add the configuration business_event related to each instance of baw_configuration in your custom resource YAML file, as in the following example:
  baw_configuration:
    - name: instance1
      business_event:
	#The main switch 
        enable: true
	#Performance tuning switches. You must set these to true so the task-related events can be monitored.
        enable_task_api: true
        enable_task_record: true
	#Subscription related settings
        subscription:
        - app_name: '*'
          component_name: '*'
          component_type: '*'
          element_name: '*'
          element_type: '*'
          nature: '*'
          version: '*'

Case event emitter configuration parameters

The following table lists the parameters for configuring Case event emitter. All parameters are optional.

Table 4. Case event emitter configuration parameters (baw_configuration)
Parameter name Description Example values
case.event_emitter.date_sql For Workflow only: Creation date of the events. The emitter starts processing the events from that date. If a bookmark exists, the emitter ignores this parameter and processes the events from the bookmark.  
case.event_emitter.logical_unique_id For Workflow only: An 8-character alphanumeric string without underscores. This value is always required. While processing, the emitter tracks the events that are processed by using the Content Engine Audit Processing Bookmark with a display name that is based on this value. Therefore, if the emitter is restarted and if the bookmark exists, the emitter processes the events from the last bookmark.  
case.event_emitter.solution_list For Workflow only: Comma-separated list of all the case solution names that need to be processed. Add all the solutions that you want to be processed before you deploy the Case event emitter.  
case.event_emitter.emitter_batch_size For Workflow only: Case event emitter batch size. The default value is 1000. 1000
case.event_emitter.process_pe_events For Workflow only: Whether to process FileNet® Process Engine events in addition to IBM Business Automation Workflow events. The default value is true. true
The following example shows sample values:
event_emitter:
  date_sql: 20200630T002840Z
  logical_unique_id: bawinst1
  solution_list: SampleSolution1,SampleSolution2
You can use the * wildcard if you want events from all the case solutions to be processed by the Case event emitter. Use: solution_list: *

Case History emitter configuration parameters

The following table lists the parameters for configuring Case history emitter.

Table 5. Case History emitter configuration parameters (baw_configuration)
Parameter name Description Example values
case.case_history_emitter.enable For Workflow only: Whether to enable Case History emitter. true
case.case_history_emitter.case_history_store_schema_name For Workflow only: Schema name of Case History store. CHSCHEMA
case.case_history_emitter.dc_common_cpe_datasource_name For Workflow only: Content Platform Engine datasource name of Case History store. CASEHISTORYDS
The following example shows sample values:
case_history_emitter:
        enable: true
        case_history_store_schema_name: CHSCHEMA
        dc_common_cpe_datasource_name: CASEHISTORYDS

Machine Learning Server configuration parameters

The following tables list the parameters for configuring Machine Learning Server.
Restrictions:
  • Machine Learning Server is available only when Business Automation Insights is installed. It is not available for stand-alone Business Automation Workflow on containers.
  • Machine Learning Server is not supported on Linux on IBM Z.

Intelligent Task Prioritization configuration parameters

The following table lists the parameters for configuring Intelligent Task Prioritization. All parameters are optional. These parameters are not supported on Linux on IBM Z or stand-alone Business Automation Workflow on containers.
Important: To use Intelligent Task Prioritization, you must set the following Business Automation Insights parameter to true: 
bai_configuration:
    bpmn:
      install: true
Table 6. Intelligent Task Prioritization configuration parameters (baml_configuration)
Parameter name Description Example values
intelligent_task_prioritization.replicas Intelligent Task Prioritization pod count. The default value is 2. 2
intelligent_task_prioritization.probes. readiness.initial_delay_seconds Number of seconds after the Intelligent Task Prioritization container starts before the readiness probe is initiated. The default value is 40. 40
intelligent_task_prioritization.image.repository Image for Intelligent Task Prioritization container. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/bui-task-prioritization, where <path> is cp.icr.io/cp/cp4a/baw. If sc_image_repository has a value, the path is that value. <path>bui-task-prioritization
intelligent_task_prioritization.image.tag Image tag for Intelligent Task Prioritization container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3
intelligent_task_prioritization.image.pull_policy Pull policy for Intelligent Task Prioritization container. The default value is IfNotPresent. IfNotPresent, Always
intelligent_task_prioritization.resources.limits.cpu CPU limit for Intelligent Task Prioritization container. The default value is 2. 2
intelligent_task_prioritization.resources.limits.memory Memory limit for Intelligent Task Prioritization container. The default value is 2048Mi. 2048Mi
intelligent_task_prioritization.resources.requests.cpu Requested amount of CPU for Intelligent Task Prioritization container. The default value is 500m. 500m
intelligent_task_prioritization.resources.requests.memory Requested amount of memory for Intelligent Task Prioritization container. The default value is 1024Mi. 1024Mi
intelligent_task_prioritization.storage.use_dynamic_provisioning Whether to use a dynamic storage provisioner. If this parameter is set to false, existing_pvc_for_logstore and existing_pvc_for_trained_pipelines must also be set. The default value is true. true
intelligent_task_prioritization.storage.existing_pvc_for_logstore Persistent volume claim (PVC) for logs.  
intelligent_task_prioritization.storage.size_for_logstore Minimum size of the persistent volume (PV) that is mounted as the log store. The default value is 1Gi. 1Gi
intelligent_task_prioritization.storage. existing_pvc_for_trained_pipelines PVC for Intelligent Task Prioritization trained pipeline files.  
intelligent_task_prioritization.storage. size_for_trained_pipelines Minimum size of the PV that is mounted as the storage for Intelligent Task Prioritization trained pipeline files. The default value is 10Gi. 10Gi
intelligent_task_prioritization.autoscaling.enabled Whether to enable Horizontal Pod Autoscaler for Intelligent Task Prioritization pod. The default value is false. false
intelligent_task_prioritization.autoscaling.max_replicas Upper limit for the number of pods that can be set by the autoscaler. It cannot be smaller than min_replicas. The default value is 3. 3
intelligent_task_prioritization.autoscaling.min_replicas Lower limit for the number of replicas to which the autoscaler can scale down. The default value is 2. 2
intelligent_task_prioritization.autoscaling. target_cpu_utilization_percentage Target average CPU utilization over all the pods. The default value is 80. 80

Workforce Insights configuration parameters

The following table lists the parameters for configuring Workforce Insights. All parameters are optional. These parameters are not supported on Linux on IBM Z or stand-alone Business Automation Workflow on containers.
Important: To use Workforce Insights, you must set the following Business Automation Insights parameters to true: 
bai_configuration:
    bpmn:
      install: true
      force_elasticsearch_timeseries: true
Table 7. Workforce Insights configuration parameters (baml_configuration)
Parameter name Description Example values
workforce_insights.replicas Workforce Insights pod count. The default value is 2. 2
workforce_insights.probes.readiness.initial_delay_seconds Number of seconds after the Workforce Insights container starts before the readiness probe is initiated. The default value is 40. 40
workforce_insights.image.repository Image for Workforce Insights container. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/bui-workforce-insights where <path> is cp.icr.io/cp/cp4a/baw. If sc_image_repository has a value, the path is that value. <path>/baw/bui-workforce-insights
workforce_insights.image.tag Image tag for Workforce Insights container. If you want to use a specific image version, you can override the default tag or digest. 21.0.3
workforce_insights.image.pull_policy Pull policy for Workforce Insights container. The default value is IfNotPresent. IfNotPresent, Always
workforce_insights.resources.limits.cpu CPU limit for Workforce Insights container. The default value is 2. 2
workforce_insights.resources.limits.memory Memory limit for Workforce Insights container. The default value is 2048Mi. 2048Mi
workforce_insights.resources.requests.cpu Requested amount of CPU for Workforce Insights container. The default value is 500m. 500m
workforce_insights.resources.requests.memory Requested amount of memory for Workforce Insights container. The default value is 1024Mi. 1024Mi
workforce_insights.storage.use_dynamic_provisioning Whether to use a dynamic storage provisioner. If this parameter is set to false, existing_pvc_for_logstore must also be set. The default value is true. true
workforce_insights.storage.existing_pvc_for_logstore Persistent volume claim (PVC) for logs.  
workforce_insights.storage.size_for_logstore Minimum size of the persistent volume (PV) that is mounted as the log store. The default value is 1Gi. 1Gi
workforce_insights.autoscaling.enabled Whether to enable Horizontal Pod Autoscaler for Workforce Insights pod. The default value is false. false
workforce_insights.autoscaling.max_replicas Upper limit for the number of pods that can be set by the autoscaler. It cannot be smaller than min_replicas. The default value is 3. 3
workforce_insights.autoscaling.min_replicas Lower limit for the number of replicas to which the autoscaler can scale down. The default value is 2. 2
workforce_insights.autoscaling. target_cpu_utilization_percentage Target average CPU utilization over all the pods. The default value is 80. 80

Process Federation Server configuration parameters

The following table lists the parameters for configuring Process Federation Server. All parameters are optional.

Table 8. Process Federation Server configuration parameters (pfs_configuration)
Parameter name Description Example values
hostname <meta-name>-pfs-route hostname. If the hostname is not set, a default hostname with the following format is used.
pfs-<shared_configuration.sc_deployment_hostname_suffix>
This parameter is used only by stand-alone Business Automation Workflow on containers.		  
port Process Federation Server port. The default value is 443. 443
service_type How the HTTPS endpoint service should be published. The default value is Route. Route, ClusterIP, NodePort
elasticsearch.endpoint Endpoint of external elasticsearch, such as: https://external_es_host:external_es_port.  
elasticsearch.admin_secret_name The external Elasticsearch administrative secret that contains the following keys:
  • .htpasswd: A file listing the users and associated passwords that are allowed to authenticate.
  • username: The name of a user referenced in the .htpasswd file. Process Federation Server pods use this user to connect to Elasticsearch.
  • password: The password of the user provided through the username key. Process Federation Server uses this password to connect to Elasticsearch.
  
elasticsearch.connect_timeout External Elasticsearch connection timeout setting. The default value is 10s. 10s
elasticsearch.read_timeout External Elasticsearch read timeout setting. The default value is 30s. 30s
elasticsearch.thread_count External Elasticsearch thread count setting.  
admin_secret_name Name of the Kubernetes secret that contains the Process Federation Server administration passwords, such as keystorePassword, ltpaPassword, oidcClientPassword, sslKeyPassword, and truststorePassword. The default value is ibm-pfs-admin-secret, ibm-pfs-admin-secret
config_dropins_overrides_secret Name of the Kubernetes secret that contains the files that will be mounted in the /config/configDropins/overrides folder.
enable_notification_server Whether to enable the notification server. The default value is true. true
enable_default_security_roles Whether to enable default security roles. The default value is true. true
admin_user_id Designate a list of users for the Process Federation Server administrator by entering the distinguished name for the LDAP user. This parameter is only used when enable_default_security_roles is true. uid=cp4baAdminUser,ou=cp4ba,dc=company,dc=com
admin_group_id Designate a list of groups for the Process Federation Server administrator by entering the distinguished name for the LDAP group. This parameter is only used when enable_default_security_roles is true. uid=cp4baAdminGroup,ou=cp4ba,dc=company,dc=com
image.repository Process Federation Server image. By default, the path points to the URL and location in the IBM Entitled Registry. The default value is <path>/pfs-prod where <path> is cp.icr.io/cp/cp4a/baw/. If sc_image_repository has a value, the path is that value. <path>/pfs-prod
image.tag Process Federation Server image tag. If you want to use a specific image version, you can override the default tag or digest. 21.0.3
image.pull_policy Process Federation Server image pull policy. The default value is IfNotPresent. IfNotPresent, Always
liveness_probe.initial_delay_seconds Number of seconds after Process Federation Server container starts before the liveness probe is initiated. The default value is 300. 300
readiness_probe.initial_delay_seconds Number of seconds after Process Federation Server container starts before the readiness probe is initiated. The default value is 240. 240
replicas Number of initial Process Federation Server pods. The default value is 1. 1
service_account Service account name for the Process Federation Server pod.
anti_affinity Whether Kubernetes can (soft) or must not (hard) deploy Process Federation Server pods onto the same node. The default value is hard. hard, soft
resources_security_secret Name of the Kubernetes secret that contains the files to be mounted in the /config/resources/security folder.
custom_libs_pvc Name of an existing Kubernetes Persistent Volume Claim which can optionally be provided to mount files on the Process Federation Server pod into the /config/resources/libs folder. ltpa.keys
external_tls_secret This parameter is used only by stand-alone Business Automation Workflow on containers. For the pfs-route, the name of the secret that contains the certificates and Transport Layer Security (TLS) private key to be used for the route. If you set this parameter, the setting overrides the default generated certificate and the shared setting for route certificates. If you need to customize the route's certificate, create a secret using the following command and set the secret name to the property.
kubectl create secret generic ext-tls-crt-secret --from-file=tls.crt=<path to crt file> --from-file=tls.key=<path to key file>
The crt file must contain the route certificate followed by any intermediate CA signer certificates and the root CA signer certificate in an unencrypted PEM format. The key file must also be in unencrypted PEM format.
external_tls_ca_secret This parameter is used only by stand-alone Business Automation Workflow on containers. For the pfs-route, provide the name of the secret containing the root CA certificate that signed the route certificate. If a customized secret for external_tls_secret is provided, you must also set the external_tls_ca_secret using the following command.
kubectl create secret generic ext-tls-ca-crt-secret --from-file=tls.crt=<path to crt file>
The crt file should contain the root CA signer certificate in an unencrypted PEM format.
monitor_enabled Specify whether to use the built-in monitoring capability. The default value is false. false
tls.tls_secret_name Existing TLS secret that contains the tls.key and tls.crt keys. The certificate should be signed by the CA in shared_configuration.root_ca_secret. If you don't want to use a customized TLS certificate, leave it empty.
tls.tls_trust_list Existing TLS trust secret.
tls.tls_trust_store Secret to store your custom trusted keystore (optional). The type for the keystore must be JKS or PKCS12. All certificates from the keystore are imported into the trust keystore of the Process Federation Server server. You might run the following sample command to create the secret: 
kubectl create secret generic pfs_custom_trust_keystore_secret --from-file=truststorefile=./trust.jks --from-literal=type=JKS --from-literal=password=WebAS
  
resources.requests.cpu Requested CPU for Process Federation Server Resource Registry configuration. The default value is 500m. 500m
resources.requests.memory Minimum memory required (including JVM heap and file system cache) to start an Elasticsearch pod. The default value is 512Mi. 512Mi
resources.limits.cpu CPU limit for Process Federation Server Resource Registry configuration. The default value is 2. 2
resources.limits.memory Maximum memory (including JVM heap and file system cache) to allocate to each Elasticsearch pod. The default value is 4Gi. 4Gi
saved_searches.index_name Name of the Elasticsearch index used to store saved searches. The default value is ibmpfssavedsearches. ibmpfssavedsearches
saved_searches.index_number_of_shards Number of shards of the Elasticsearch index used to store saved searches. The default value is 3. 3
saved_searches.index_number_of_replicas Number of replicas (pods) of the Elasticsearch index used to store saved searches. The default value is 1. 1
saved_searches.index_batch_size Batch size used when retrieving saved searches. The default value is 100. 100
saved_searches.update_lock_expiration Amount of time before an update lock is considered to be expired. Valid values are numbers with a trailing 'm' or 's' for minutes or seconds. The default value is 5m. 5m
saved_searches.unique_constraint_expiration Amount of time before a unique constraint is considered to be expired. Valid values are numbers with a trailing 'm' or 's' for minutes or seconds. The default value is 5m. 5m
security.sso.domain_name SSO domain names property of the webAppSecurity tag.
security.sso.cookie_name SSO cookie name property of the webAppSecurity tag. The default value is ltpatoken2. ltpatoken2
security.sso.ltpa.filename keysFileName property of the ltpa tag. The default value is ltpa.keys. ltpa.keys
security.sso.ltpa.expiration Expiration property of the ltpa tag. The default value is 120m. 120m
security.sso.ltpa.monitor_interval monitorIntervalproperty of the ltpa tag. The default value is 60s. 60s
security.ssl_protocol sslProtocol property of the ssl tag that is used as default SSL configuration. The default value is SSL. SSL
executor.max_threads Value of the maxThreads property of the executor tag. The default value is 80. 80
executor.core_threads Value of the coreThreads property of the executor tag. The default value is 40. 40
rest.user_group_check_interval Value of the userGroupCheckInterval property of theibmPfs_restConfig tag. The default value is 300s. 300s
rest.system_status_check_interval Value of the systemStatusCheckInterval property of the ibmPfs_restConfig tag. The default value is 60s. 60s
rest.bd_fields_check_interval Value of the bdFieldsCheckInterval property of theibmPfs_restConfig tag. The default value is 300s. 300s
custom_env_variables.names Names of the custom environment variables that are defined in the secret that is referenced in customEnvVariables.secret.
custom_env_variables.secret Secret holding custom environment variables.
logs.console_format Format for printing logs on the console. The valid values are basic or json format. The default value is json. json
logs.console_log_level Log level for printing logs on the console. The valid values are INFO, AUDIT, WARNING, ERROR, and OFF. The default value is INFO. INFO
logs.console_source Source of the logs for printing on the console. This property applies only when the consoleFormat is json. Valid values are message, trace, accessLog, ffdc, and audit. message, trace, accessLog, ffdc, audit
logs.trace_format Format for printing trace logs. The default format for the Liberty server is ENHANCED. The BASIC and ADVANCED formats are for WebSphere® Application Server. The default value is ENHANCED. ENHANCED
logs.trace_specification Specification for printing trace logs. An example value is =info:com.ibm.bpm.federated.=all. The default value is *=info. *=info
logs.storage.use_dynamic_provisioning Whether to use dynamic provisioning for storing the log data for Process Federation Server. The default value is true. true
logs.storage.size Minimum size of the PV used mounted as Process Federation Server Liberty server /logs folder. The default value is 1Gi. 1Gi
logs.storage.storage_class Storage class if using dynamic provisioning. The default value is shared_configuration.storage_configuration.sc_fast_file_storage_classname. shared_configuration.storage_configuration. sc_fast_file_storage_classname
logs.storage.existing_pvc_name PVC for logs if not using dynamic provisioning  
dump.persistent Whether to enable persistent storage for Process Federation Server dump files. The default value is false. false
dump.storage.use_dynamic_provisioning Whether to use dynamic provisioning for Process Federation Server dump storage. The default value is true. true
dump.storage.size Minimum size of the PV that is mounted as the dump store. The default value is 5Gi. 5Gi
dump.storage.storage_class Storage class if using dynamic provisioning for Process Federation Server dump file storage. The default value is shared_configuration.storage_configuration.sc_slow_file_storage_classname. shared_configuration.storage_configuration.sc_slow_file_storage_classname
dump.storage.existing_pvc_name PVC for dump files if not using dynamic provisioning.  
dba_resource_registry.lease_ttl Duration of the lease that creates the Process Federation Server entry in the DBA Service Registry, in seconds. The default value is 120. 120
dba_resource_registry.pfs_check_interval Interval at which to check that Process Federation Server is running, in seconds. The default value is 10. 10
dba_resource_registry.pfs_connect_timeout Number of seconds after which Process Federation Server is considered as not running if no connection can be established. The default value is 10. 10
dba_resource_registry.pfs_response_timeout Number of seconds after which Process Federation Server is considered as not running if it has not yet responded. The default value is 30. 30
dba_resource_registry.pfs_registration_key Key under which Process Federation Server should be registered in the DBA Service Registry when running. The default value is /dba/appresources/IBM_PFS/PFS_SYSTEM. /dba/appresources/IBM_PFS/PFS_SYSTEM
dba_resource_registry.resources. limits.memory Memory limit for Process Federation Server and Resource Registry integration pod. The default value is 512Mi. 512Mi
dba_resource_registry.resources. limits.cpu CPU limit for Process Federation Server and Resource Registry integration pod. The default value is 100m. 100m
dba_resource_registry.resources. requests.memory Requested amount of memory for Process Federation Server and Resource Registry integration pod. The default value is 512Mi. 512Mi
dba_resource_registry.resources. requests.cpu Requested amount of CPU for Process Federation Server and Resource Registry integration pod. The default value is 50m. 50m
dba_resource_registry.liveness_probe. failure_threshold When a probe fails, number of times that Kubernetes tries before it gives up and restarts the container. The default value is 3. 3
dba_resource_registry.liveness_probe. initial_delay_seconds Number of seconds after the Process Federation Server registration container starts before the liveness probe is initiated. The default value is 5. 5
dba_resource_registry.liveness_probe. period_seconds Number of seconds to wait before the next probe. The default value is 5. 5
dba_resource_registry.liveness_probe. success_threshold Minimum consecutive successes for the probe to be considered successful after it failed. The default value is 1. 1
dba_resource_registry.liveness_probe. timeout_seconds Number of seconds after which the probe times out. The default value is 5. 5
dba_resource_registry.readiness_probe. failure_threshold When a probe fails, number of times that Kubernetes tries before it gives up and restarts the container. The default value is 3. 3
dba_resource_registry.readiness_probe. initial_delay_seconds Number of seconds after the Process Federation Server registration container starts before the readiness probe is initiated. The default value is 1. 1
dba_resource_registry.readiness_probe. period_seconds Number of seconds to wait before the next probe. The default value is 10. 10
dba_resource_registry.readiness_probe. success_threshold Minimum consecutive successes for the probe to be considered successful after it failed. The default value is 1. 1
dba_resource_registry.readiness_probe. timeout_seconds Number of seconds after which the probe times out. The default value is 5. 5