CP4BA Workflow Process Service Runtime parameters

IBM Workflow Process Service Runtime needs a set of values for its configuration parameters to create a Kubernetes deployment.

The following tables list the configurable parameters and their default values. Complete the custom resource (CR) YAML file for your deployment by supplying values for your environment and configuration. All properties are mandatory, unless they have a default value or are explicitly optional. Although Workflow Process Service might seem to install correctly when some parameters are omitted, this configuration is not supported.

Workflow Process Service configuration parameters
Workflow Process Service custom resource status properties

Workflow Process Service configuration parameters

The following table lists the parameters for configuring Workflow Process Service.

Table 1. Workflow Process Service configuration parameters
Parameter name	Description	Example values
admin.username	The user that is entered for this parameter is configured as the administrator of Workflow Process Service. This user must be a valid user in Business Teams Service. After the first configuration of this value, it can no longer be updated.	`admin`
appVersion	The version at which the operator is reconciled.	`26.0.0`
authoringServer.heartbeatInterval	Heartbeat interval in seconds to connect to Workflow Process Service Authoring server. The default value is `60`.	`30`
authoringServer.secretName	The secret name of Workflow Process Service Authoring server that contains the username and password fields for connecting to Workflow Process Service Authoring server. If you are not connecting to the authoring server, this parameter is optional.	`authoring-secret`
authoringServer.url	The URL of Workflow Process Service Authoring server. If you are not connecting to the authoring server, this parameter is optional. The format of the parameter is similar to `"https://<bastudio_url>/bas/ProcessCenter"` If you know the authoring server name and port, you can replace `<bastudio_url>` with `<authoring_server_name>:<port>`. Otherwise, you can find `<bastudio_url>` by running the following command: `kubectl describe configmaps icp4adeploy-cp4ba-access-info`	`https://authoring_server_name:port/bas/ProcessCenter`
authoringServer.webPDUrl	The URL of Workflow Process Service Authoring web Process Designer. If you are not connecting to the authoring server, this parameter is optional. The format of the parameter is similar to `"https://<bastudio_url>/bas/WebPD"` If you know the authoring server name and port, you can replace `<bastudio_url>` with `<authoring_server_name>:<port>`. Otherwise, you can find `<bastudio_url>` by running the following command: `kubectl describe configmaps icp4adeploy-cp4ba-access-info`	`https://authoring_server_name:port/bas/webPD`
businessEvent.enable	Enable IBM Business Automation Insights for the event emitter. The default value is `false`.	`false`
businessEvent.EnableTaskRecord	Enable additional task information in generated events. This parameter is optional and equivalent to the `task-record-enabled` parameter mentioned in BPMN summary event formats. The default value is `true`.	`true`
businessEvent.EnableTaskApi	Enable the task instance identifier in generated events. This parameter is equivalent to the `enable-task-api-def` parameter mentioned in BPMN summary event formats. The default value is `true`.	`true`
businessEvent.subscription	List of business event types to monitor.	`subscription: - appName: "appname1" componentName: "" componentType: "" elementName: "" elementType: "" nature: "" version: "" - appName: "appname2" componentName: "" componentType: "" elementName: "" elementType: "" nature: "" version: ""`
businessEvent.subscription[x].appName	Name of the source application that has events to monitor. The default value is `*`, which means all applications are monitored.	`*`
businessEvent.subscription[x].version	Version of the source application that has events to monitor. The default value is `*`, which means all versions are monitored.	`*`
businessEvent.subscription[x].componentType	Type of the component to monitor. The default value is `*`, which means all component types are monitored.	`*`
businessEvent.subscription[x].componentName	Name of the component to monitor. The default value is `*`, which means all components are monitored.	`*`
businessEvent.subscription[x].elementType	Type of the element to monitor. BPMN types include `PROCESS`, `ACTIVITY`, `EVENT`, and `GATEWAY`. The default value is `*`, which means all element types are monitored.	`*`
businessEvent.subscription[x].elementName	Name of the element to monitor. The default value is `*`, which means all elements are monitored.	`*`
businessEvent.subscription[x].nature	Status of the event to monitor. Elements can send events of various statuses. The BPMN status types include `STARTED`, `COMPLETED`, `TERMINATED`, `DELETED`, `FAILED`, `CAUGHT`, `THROWN`, `EXPECTED`, `ACTIVE`, `READY`, `RESOURCE_ASSIGNED`, `ACTIVE`, `LOOP_CONDITION_TRUE`, `LOOP_CONDITION_FALSE`, and `MULTIPLE_INSTANCES_STARTED`. The default value is `*`, which means all status types are monitored.	`*`
capabilities.federate.additionalHeaders	List of HTTP headers that are added to Process Federation Server queries when performing requests against the federated system. The headers in the list must be separated with a comma. This parameter is optional. If this parameter is not set, the default value `X-PFS-ID=<namespace>-<pfs-custom-resource-name>` is used in the `federatedsystems` custom resource.	`X-PFS-ID=namespace-pfsCustomResourceName`
capabilities.federate.enable	Option to enable Workflow Process Service to be federated by Process Federation Server. This parameter is optional. The default value is `false`.	`false`
capabilities.federate.encryption_key_secret	Name of the secret containing the encryption key used by Process Federation Server. This parameter is optional. If it is not set, the secret will be dynamically resolved.
capabilities.fullTextSearch.adminGroups	Configures a list of IBM Cloud Pak® Platform UI (Zen) permissions for the `administrator`, `adminSavedSearch`, and `adminSharedSavedSearch` security roles from Process Federation Server. If `capabilities.fullTextSearch.enable` is set to `false`, you can ignore this parameter.	`example_group`
capabilities.fullTextSearch.enable	Option to enable or disable the full text search. By default, the option is disabled and the value is `false`.	`false`
capabilities.fullTextSearch.esSnapshotStorage.size	The storage size for persisting Elasticsearch snapshot data. The default value is `10Gi`.	`10Gi`
capabilities.fullTextSearch.esSnapshotStorage.storageClassName	StorageClass name for Elasticsearch snapshot data. The StorageClass should create the storage type of the Persistent Volumes in block mode rather than file system mode.	`rook-cephfs`
capabilities.fullTextSearch.esStorage.size	The storage size for persisting Elasticsearch data. The default value is `50Gi`.	`50Gi`
capabilities.fullTextSearch.esStorage.storageClassName	StorageClass name for Elasticsearch data. The StorageClass should create the storage type of the Persistent Volumes in block mode rather than file system mode.	`rook-cephfs`
capabilities.fullTextSearch.resources.limits	Maximum number of compute resources allowed for Elasticsearch. For more information, see Resource Management for Pods and Containers .
capabilities.fullTextSearch.resources.requests	Minimum number of compute resources required for Elasticsearch. If this parameter is not set for a container, it defaults to `capabilities.fullTextSearch.resources.limits` if it is set. Otherwise, the default implementation value is used. For more information, see Resource Management for Pods and Containers .
database.external.databaseName	Database instance name.	`wfpsdb`
database.external.dbCredentialSecret	Database secret name that has the database username and password. The secret key must include the username and password.	`example_secret_06`
database.external.dbServerCertSecret	Secret name for storing the database TLS certificate when SSL connections are enabled for the database. This value is required only when `enable_ssl` is `true`. For information about creating the secret, see step 1.c in "Deploying Workflow Process Service" in Installing Workflow Process Service Runtime deployments.	`example_secret_07`
database.external.enableSSL	Parameter to enable Secure Sockets Layer (SSL) support for the database connection. The default value is `true`.	`true`
database.external.sslMode	Type of Secure Sockets Layer (SSL). Required only when `enable_ssl` is set to `true`. If you want to enable SSL by itself, keep the default value `require`. If you want to enable SSL and database certificate-based authentication, change the value to `verify-ca` or `verify-full`.	`require`
database.external.jdbcUrl	The JDBC URL if database parameters `ServerName`, `DatabaseName`, and `Port` are not configured.	`jdbc:postgresql://<postgresql_server>:5432/your_database`
database.external.port	Database port. For PostgreSQL, the default value is `5432`.	`5432`
database.external.serverName	Database server name in the form of either a fully qualified domain name (FQDN) or an IP address.	`example.postgre.com`
database.external.type	Database type. Only PostgreSQL is supported and it is the default value.	`postgresql`
database.external.current_schema	Database schema name. This parameter is optional. If it is not set, the schema name is the same as database username.	`databaseschema`
database.managed.replicas	Managed database pod replica count. The default value is `1`.	`1`
database.managed.storage.size	The storage size for persisted and managed database data. The default value is `1Gi`.	`1Gi`
database.managed.resources.requests.cpu	Minimum number of compute resource CPUs required. The default value is `1`.	`1`
database.managed.resources.requests.memory	Minimum amount of compute resource memory required. The default value is `2Gi`.	`2Gi`
database.managed.resources.limits.cpu	Maximum number of compute resource CPUs allowed. The default value is `1`.	`1`
database.managed.resources.limits.memory	Maximum amount of compute resource memory allowed. The default value is `2Gi`.	`2Gi`
database.client.customJDBCPVC	Name of the persistent volume claim (PVC) that stores the custom JDBC driver files. Use the embedded PostgreSQL driver name if it is not set. Custom JDBC driver files are mounted at `/shared/resources/jdbc/postgresql`.	`pvc-name`
database.client.dbCheckWaitTime	Maximum wait time (in seconds) to check the database initialization status. The default value is `900`.	`900`
database.client.dbCheckIntervalTime	The interval time (in seconds) to check the database connection status. The default value is `15`.	`15`
database.client.jdbcDriverFiles	This value needs to be configured if you also configured `customJDBCPVC`. Values include custom JDBC driver file names, separated with a space. The default value is `postgresql.jar`.	`postgresql-42.2.15.jar`
database.client.maxConnectionPoolSize	Database connect pool maximum number of physical connections. The default value is `200`.	`50`
database.client.minConnectionPoolSize	Database connect pool minimum number of physical connections. The default value is `1`.	`1`
deploymentLicense	License type of the Cloud Pak for Business Automation deployment. The possible values are `non-production` and `production`.	`production`
elasticsearch.external.endPoint	Endpoint of external Elasticsearch, such as: https://<external_es_host>:<external_es_port>. This parameter is required if you want to use external Elasticsearch.	`https://elastic_hostname:9200`
elasticsearch.external.esCredentialSecret	The external Elasticsearch secret that contains the username and password keys. This parameter is required if you want to use external Elasticsearch. To create the secret, run `kubectl create secret generic wfps-es-secret --from-literal=username=<bawadmin> --from-literal=password=<password>`	wfps-es-secret
elasticsearch.external.esServerCertSecret	Secret name for storing the Elasticsearch TLS certificate if SSL connections for Elasticsearch are enabled. To create the secret, run `kubectl create secret generic wfps-es-cacert-secret --from-file=ca.crt=./cert.crt`	wfps-es-cacert-secret
image.imagePullPolicy	Image pull policy. The default value is `IfNotPresent`.	`IfNotPresent`
image.imagePullSecrets	Image pull secrets.	`- pullSecret_01`
image.repository	Image repository URL.	`example.repository.com/workflow/workflow-server-ps-mini`
image.tag	Image tag.	26.0.0
kafka_services.enable	Option to enable or disable the Kafka services. By default, `kafka_services.enable` is disabled and its value is false. When the Kafka component is configured in `shared_configuration.sc_optional_components`, the value of `kafka_services.enable` is true. For more information, see Creating a Kafka service.	`false`
license.accept	License accept parameter. This value can either be `true` or `false`.	`false`
managementState	Indicates whether the custom resources are monitored and managed by the Workflow Process Service operator. Possible values are `Managed` and `Unmanaged`. The default value is `Managed`.	`Managed`
node.auditLog.customAuditPVC	Name of the persistent volume claim (PVC) that stores the audit files.	`""`
node.auditLog.enable	Whether to enable the audit log. The default value is `false`. Note: If you enable `node.auditLog`, you cannot enable `node.audit_logging`. Only one of the parameters, `node.auditLog.enable` or `node.audit_logging.enabled`, can be set to `true` at a time.	`false`
node.auditLog.fileName	Audit log file name. The default value is `bawaudit.log`.	`"bawaudit.log"`
node.auditLog.maxHistoricalFiles	The maximum number of files to store audit logs. The default value is `5`.	`5`
node.auditLog.rolloverSize	The maximum size in MB that an audit log file can reach before it is rolled. The default value is `100`.	`100`
node.auditLog.verbose	Whether to enable the verbose audit log. The default value is `true`.	`true`
node.audit_logging.enabled	Whether to enable the Audit Logging service. The default value is `true`. This overrides the `sc_audit_logging.enabled` of the CP4BACluster CR. Note: If you enable `node.audit_logging`, you cannot enable `node.auditLog`. Only one of the parameters, `node.audit_logging.enabled` or `node.auditLog.enable`, can be set to `true` at a time.	`true`
node.audit_logging.log_dir_size	The maximum size of the audit log directory. The default value is `150Mi`.	`150Mi`
node.audit_logging.rolling_max_files	The maximum number of rolling files for audit log. The default value is `5`.	`5`
node.audit_logging.rolling_max_size	The maximum size of one audit log file. The default value is `20Mi`.	`20Mi`
node.autoScaling.enabled	If you set this value to `true`, pods are automatically scaled within the specified range. The default value is `false`.	`false`
node.autoScaling.minReplicas	Minimum number of pods that the Horizontal Pod Autoscaler can scale to. The default value is `1`.	`1`
node.autoScaling.maxReplicas	Maximum number of pods that the Horizontal Pod Autoscaler can scale to. This value must be greater than `node.autoScaling.maxReplicas`. The default value is `5`.	`5`
node.autoScaling.targetAverageUtilization	Percentage threshold of average CPU usage by pods for triggering horizontal scaling. The default value is `80`.	`80`
node.customAnnotations	Custom annotation properties in the form of an unstructured key-value map. Annotations are stored with a resource that enables external tools to store and retrieve metadata.	`myKey: myValue`
node.customFilePVC	The persistent volume claim (PVC) containing custom files which is mounted at `/opt/ibm/bawfile`. The `AccessMode` of the PVC should be `ROX` or `RWX`. `RWO` is not recommended. It has an adverse effect on high availability because all pods must be allocated to the same node.	`example-pvc-name`
node.customize.jvmOptions	Java™ Virtual Machine (JVM) options, separated with a space. For example: `-Dtest1=test -Dtest2=test2`. You need to update this value to restart the Workflow Process Service server pod manually.	`-Dtest1=test -Dtest2=test2`
node.customize.libertyXML	Server custom plain XML snippet. The `libertyXMLSecret` is also used for Workflow Server customization. You can set this configuration either in `libertyXML` or `libertyXMLSecret`. Do not set the configuration value in both locations. When you update this value, the Workflow Process Service server pod restarts automatically.	`<server><!--add your configuration here. --></server>`
node.customize.libertyXMLSecret	Server custom XML secret name. `libertyXML` is also used for Workflow Server customization. You can set this configuration either in `libertyXML` or `libertyXMLSecret`. Do not set the same configuration value in both locations. Create a customized secret using the command: `kubectl create secret generic custom-xml-secret-name --from-file=sensitiveCustomConfig=./custom.xml`. When you update this value, the Workflow Process Service server pod restarts automatically.	`example_secret_06`
node.customize.lombardiXML	Server Lombardi custom XML. This contains custom configuration that usually might be in `100Custom.xml`. When you add or delete this value for the first time, the Workflow Process Service server pod restarts automatically. If this value is already set and you want to update it, you need to restart the Workflow Process Service pod manually. To restart the pod, run the command: `oc delete pod <cr-name>wfps-runtime-server<x>`.	`<properties><!--add your configuration here. --></properties>`
node.customize.lombardiXMLSecret	Server Lombardi custom XML secret name. The secret contains custom configuration usually in `100Custom.xml`. Create a customized secret using the following command: `kubectl create secret generic custom-lombardi-xml-secret-name --from-file=sensitiveCustomConfig=./100Custom.xml`. When you add or delete this value for the first time, the Workflow Process Service server pod restarts automatically. If this value is already set and you want to update it, you need to restart the Workflow Process Service pod manually. To restart the pod, run the command: `oc delete pod <cr-name>wfps-runtime-server<x>`.	`example_secret_06`
node.customLabels	Custom label properties in the form of a map of string keys and values to categorize scope and select objects. For more information, see Labels and Selectors .	`myKey: myValue`
node.deploymentProfileSize	Deployment profile size. The profile size should be based on your cluster requirement. Possible values include `small`, `medium` or `large`.	`small`
node.environmentConfig.authorizationEnabledForOrgInfo	Option for enabling authorization to user management APIs. The default value is `true`.	`true`
node.environmentConfig.contentSecurityPolicyAdditionalConnectSrc	Additional hostnames for Content Security Policy `connect-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalDefaultSrc	Additional hostnames for Content Security Policy `default-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalFontSrc	Additional hostnames for Content Security Policy `font-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalFrameAncestor	Additional hostnames for Content Security Policy `frame-ancestor`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalFrameSrc	Additional hostnames for Content Security Policy `frame-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalImgSrc	Additional hostnames for Content Security Policy `img-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalObjectSrc	Additional hostnames for Content Security Policy `object-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.contentSecurityPolicyAdditionalScriptSrc	Additional hostnames for Content Security Policy `script-src`.	`['https://hostname1','https://hostname2']`
node.environmentConfig.csrf.originAllowList	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://test.com,https://test.com:443']`
node.environmentConfig.csrf.refererAllowList	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 hostnames.	`['test.com,test.com:443']`
node.logging.consoleFormat	Format for printing logs on the console. Possible values include `dev`, `simple`, and `json`. The default value is `json`.	`json`
node.logging.consoleLogLevel	Configuration for printing logs on the console. Possible values are `INFO`, `AUDIT`, `WARNING`, `ERROR`, and `OFF`. The default value is `INFO`.	`INFO`
node.logging.consoleSource	Source of the logs for printing on the console. The default value is `message,trace,accessLog,ffdc,audit`.	`message,trace,accessLog,ffdc,audit`
node.logging.enableFilebeat	Configuration to enable sending the log file to standard output, with JSON format by default. When this value is changed, the update is dynamically reflected at the container, but causes pods to rolling update. The default value is `false`.	`false`
node.logging.filebeatOutputSecret	Secret containing the filebeat configuration. If `node.logging.enableFilebeat` is set to `true`, you must set this value. The secret must contain the `filebeat-output.yml` key.
node.logging.maxFileSize	The maximum size that a log file can reach before it is rolled. This value is measured in MB. The default value is `50`.	`50`
node.logging.maxFiles	Maximum number of log files that are kept before the oldest file is removed. The default value is `10`.	`10`
node.logging.messageFormat	Format for printing trace logs on the console. Possible values are `simple` and `json`. The default Value is `simple`.	`simple`
node.logging.traceFormat	Format for printing trace logs on the console. Possible values are `ENHANCED`, `BASIC` and `ADVANCED`. The default value is `ENHANCED`.	`false`
node.logging.traceSpecification	Specification for printing trace logs. The default value is `'*=info'`.	`'*=info'`
node.nodeAffinity.customNodeSelectorMatchExpression.key	`nodeAffinity` expression label key that applies the operator.	`topology.kubernetes.io/zone`
node.nodeAffinity.customNodeSelectorMatchExpression.operator	The `nodeAffinity` expression logical operator that the key applies to the set of values. Possible operator values include `In`, `NotIn`, `Exists`, `DoesNotExist`, `Gt`, and `Lt`.	`In`
node.nodeAffinity.customNodeSelectorMatchExpression.values	The `nodeAffinity` expression's array of string values corresponding to the selected operator. If the operator is `In` or `NotIn`, the array must be non-empty. If the operator is `Exists` or `DoesNotExist`, the array must be empty. If the operator is `Gt` or `Lt`, the array must have a single value and the value is interpreted as a single integer. This array is replaced during a strategic merge patch.	`- region1 - region2`
node.replicas	Workflow Process Service replica count. The default value is `2`.	`1`
node.probe.livenessProbe.failureThreshold	Number of seconds to wait before the next probe. The default value is `6`.	`6`
node.probe.livenessProbe.initialDelaySeconds	Number of seconds after the Workflow Server container starts before the liveness probe is initiated. The default value is `5`.	`5`
node.probe.livenessProbe.periodSeconds	Number of seconds to wait before the next probe. The default value is `10`.	`10`
node.probe.livenessProbe.successThreshold	Number of seconds to wait before the next probe. The default value is `1`.	`1`
node.probe.livenessProbe.timeoutSeconds	Number of seconds to wait before the next probe. The default value is `10`.	`10`
node.probe.readinessProbeSpec.failureThreshold	Number of seconds to wait before the next probe. The default value is `6`.	`6`
node.probe.readinessProbeSpec.initialDelaySeconds	Number of seconds after the Workflow Server container starts before the readiness probe is initiated. The default value is `5`.	`5`
node.probe.readinessProbeSpec.periodSeconds	Number of seconds to wait before the next probe. The default value is `5`.	`5`
node.probe.readinessProbeSpec.timeoutSeconds	Number of seconds to wait before the next probe. The default value is `5`.	`5`
node.probe.readinessProbeSpec.successThreshold	Number of seconds to wait before the next probe. The default value is `1`.	`1`
node.probe.startupProbe.failureThreshold	Number of seconds to wait before the next probe. The default value is `30`.	`30`
node.probe.startupProbe.periodSeconds	Number of seconds to wait before the next probe. The default value is `20`.	`20`
node.probe.startupProbe.successThreshold	Number of seconds to wait before the next probe. The default value is `1`.	`1`
node.probe.startupProbe.timeoutSeconds	Number of seconds to wait before the next probe. The default value is `10`.	`10`
node.securityContext.runAsUser	Security configuration that applies to a container. This value must satisfy the uid-range in the namespace.	`1000740000`
node.securityContext.fsGroup	When volumes are mounted by a pod, the pod level group ID that has file permissions changed by Kubernetes. Map the service account to `scc` if you are on Red Hat® OpenShift® Container Platform (OCP) or `psp` if you are on Kubernetes. For example, if you are on OCP, use the command: `oc adm policy add-scc-to-user anyuid -z wfps-instance1-sa -n NAMESPACE`	`0`
node.securityContext.seccompProfile.type	The secure computing mode (seccomp) profile for the Workflow Process Service container. You can also define the seccomp profile globally by using `shared_configuration.sc_seccomp_profile`. This parameter is optional. The default value is `RuntimeDefault`.	`RuntimeDefault`, `Unconfined`, or `Localhost`
node.securityContext.seccompProfile.localhostProfile	Local path of a custom seccomp profile when the type `Localhost` is configured. The custom profile must be accessible by the pod.	`/profiles/fine-grained.json`
node.resources.limits	Describes the maximum number of compute resources. For more information, see Managing Resources for Container .
node.resources.requests	Describes the minimum number of computation resources required. If requests is omitted for a container, it defaults to the limits value if it is specified. If limits is not defined, it defaults to an implementation-defined value. For more information, see Managing Resources for Container .
node.serverType	Server type. The possible values are `Development`, `Test`, `Staging`, or `Production`. The default value is `Production`. If you update this value, the change is dynamically reflected at the container.	`Production`
persistent.data.enable	Enable persisting runtime data including JMS messages. The default value is `false`.	`false`
persistent.data.size	The maximum storage capacity for the persisted objects.	`1Gi`
persistent.data.storageClassName	StorageClass for data. If this value is not set, the value of `persistent.storageClassName` is used.	`rook-cephfs`
persistent.dump.enable	Enable persisting runtime dump data. The default value is `false`.	`false`
persistent.dump.size	The maximum storage capacity for the persisted objects.	`1Gi`
persistent.dump.storageClassName	StorageClass for runtime dump data. If this value is not set, the value of `persistent.storageClassName` is used.	`rook-cephfs`
persistent.logs.enable	Enable persisted bootstrap, initialization, and runtime logs. The default value is `false`.	`false`
persistent.logs.size	The maximum storage capacity for the persisted objects.	`1Gi`
persistent.logs.storageClassName	StorageClass for log files. If this value is not set, it uses the value of `persistent.storageClassName`.	`rook-cephfs`
persistent.storageClassName	The name of the storage class to use with creating persisted volume claim (PVC). For more information, see Storage Classes .	`rook-cephfs`
tls.serverTrustCertificateList	Server TLS trust list. You can enter a list of secrets, where every secret stores a trusted certificate. To create a secret, run the following command: `kubectl create secret generic wfps-tls-secret --from-file=tls.crt=./cert.crt`	`- example_secret_06`
tls.serverTrustKeyStore	Secret to store your custom trusted keystore. This parameter is 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 Process Service server. To create a secret, run the following command: `kubectl create secret generic wfps_custom_trust_keystore_secret --from-file=truststorefile=./trust.jks --from-literal=type=JKS --from-literal=password=WebAS`	`example_secret_06`

You can use the optional connection manager settings in the custom resource file to tune your database connection pooling performance according to the requirements of your environment.

spec:
 node:
  customize:
   libertyXML: |
    <server>
     <connectionManager
       id="ConMgr1"
       maxPoolSize="100"
       minPoolSize="20"
      />

     <!-- Override datasource to use custom connectionManager -->
     <dataSource id="jdbc/TeamWorksDB" jndiName="jdbc/TeamWorksDB" connectionManagerRef="ConMgr1">
     </dataSource>
    </server>

For more information, see Connection Manager (connectionManager).

Workflow Process Service custom resource status properties

The following table lists the properties that show the installation status of the components in the custom resource (CR) instance that is used by the Workflow Process Service operator.

Table 2. Workflow Process Service custom resource status properties
Status property	Description	Possible values
LicenseChecked	License verification status.	`Passed`, `Failed`
IAMClientRegistered	Identity Access Management client registration status.	`Registered`, `RegistrationFailed`
ZenProgressReady	Cloud Pak Platform UI (Zen) deployment status.	`Deployed`, `NotDeployed`
ZenExtensionReady	Cloud Pak Platform UI (Zen) extension status.	`Completed`, `NotCompleted`
ElasticSearchReady	Cloud Pak foundational services Elasticsearch deployment status.	`Deployed`, `NotDeployed`
PostgreSQLClusterReady	PostgreSQL cluster status.	`Available`, `NotAvailable`
ConfigMapReady	Workflow Process Service configMap status.	`Created`, `NotCreated`
IWfPSServerReady	Workflow Process Service server instance status.	`Available`, `NotAvailable`
IWfPSServiceReady	Workflow Process Service service status.	`Created`, `NotCreated`
IWfPSRouteReady	Workflow Process Service route status.	`Created`, `NotCreated`