IBM FileNet Content Manager common parameters
| Parameters | Description | Default or Example Values | Required |
|---|---|---|---|
| fncm_secret_name |
Contains the information about the database usernames and passwords, LDAP usernames and passwords, keystore password, and LTPA password for components. For details, see Creating secrets to protect sensitive configuration data. If FIPS is enabled, the keystore password must be more than 16 characters long. |
ibm-fncm-secret | Yes |
| route_ingress_annotations | By default all the components create ingress and routes with required annotations. In case any custom annotation is needed for the environment, use this parameter to specify the annotations. | - haproxy.router.openshift.io/balance: roundrobin | No |
| fncm_ext_tls_secret_name | Optional. Use an existing certificate for automatic creation of OpenShift routes. Set this key if you have an external TLS certificate. Leave this empty if you don't have an external TLS certificate, and the operator generates one for you. | None | No |
| fncm_auth_ca_secret_name | Optional. The Certificate Authority (CA) used to sign the external TLS secret for automatic creation of OpenShift routes. Set this key if you have a CA to sign the external TLS certificate. Leave this parameter empty if you don't have the CA of your external TLS certificate. | None | No |
| node_affinity.custom_node_selector_match_expression | Added in node selector match expressions. It accepts array list inputs. You can assign
multiple selector match expressions except (kubernetes.io/arch).Note: This can be
overwritten by the component level definition, for example
ecm_configuration.cpe.node_affinity.custom_node_selector_match_expression. |
|
No |
| custom_annotations | Values in this field are used as annotations in all generated pods. They must be valid annotation key-value pairs. | customAnnotationKey: customAnnotationValue |
No |
| custom_labels | Values in this field are used as labels in all generated pods. They must be valid label key-value pairs. | customLabelKey: customLabelValue |
No |
| zen_performance.proxy_connect_timeout |
Timeout for establishing a connection with a proxy server. For more information, see Tuning NGINX for Performance. The parameter can be overwritten by component level definition. For example,
For Content Platform Engine, you can
use more granular settings that takes precedence over
ecm_configuration.cpe.zen_performance.proxy_connect_timeout. For
example: |
300 | No |
| zen_performance.proxy_send_timeout |
Timeout for transmitting a request to the proxy server. The timeout is set only between two successive write operations, not for the transmission of the whole request. If the proxy server does not receive anything within this time, the connection is closed. For more information, see Tuning NGINX for Performance. The parameter can be overwritten by component level definition. For example,
For Content Platform Engine, you can
use more granular settings that takes precedence over
ecm_configuration.cpe.zen_performance.proxy_send_timeout. For
example: |
300 | No |
| zen_performance.proxy_read_timeout |
Timeout for reading a response from the proxy server. The timeout is set only between two successive read operations, not for the transmission of the whole response. If the proxy server does not transmit anything within this time, the connection is closed. For more information, see Tuning NGINX for Performance. The parameter can be overwritten by component level definition. For example,
For Content Platform Engine, you can
use more granular settings that takes precedence over
ecm_configuration.cpe.zen_performance.proxy_read_timeout. For
example: |
300 | No |