Datasource parameters
Update the custom YAML file to provide the details that are relevant for your Content
Manager and Content Navigator datasource environment. The default parameter list assumes one Content
Platform Engine Global Configuration database, two object store databases, and one Content Navigator
database. Some parameters are specific to database vendors.
For information about data source parameters, see Configuring relational database connectivity in Liberty
.
| Parameters | Description | Default/Example Values | Required |
|---|---|---|---|
| dc_ssl_enabled | Used to support database connection over SSL. | true | No |
| Parameters | Description | Default/Example Values | Required |
|---|---|---|---|
| dc_database_type | Provide the database type from your infrastructure. The possible values are "db2", "db2HADR", "db2rds", "db2rdsHADR", "oracle", "sqlserver", or "postgresql". | postgresql | Yes |
| dc_common_gcd_datasource_name | The JNDI name of the non-XA JDBC data source associated with the global configuration table space or database. The name must be unique. | FNGCDDS | Yes |
| dc_common_gcd_xa_datasource_name | The JNDI name of the XA JDBC data source associated with the global configuration table space or database. The name must be unique. | FNGCDDSXA | Yes |
| database_servername | The host name where the database software is installed. It must be an accessible address,
such as an IP, hostname, or Kubernetes service name. If you enter an IPv6 literal address, the IP
address needs to be specified within square brackets "[]". For example, you can
specify the IP address as [2001:db8:a0b:12f0:1]. |
<hostname> | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_name | Provide the database name for the GCD. | GCDDB | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_port | Provide the database port. For Db2®, the default is "50000". | "50000" | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_ssl_secret_name | The name of the secret that contains the Db2/Oracle/PostgreSQL SSL certificate. The secret can contain multiple certificates in a single tls.crt field. | <secret_name> | Yes |
| dc_oracle_gcd_jdbc_url | For Oracle, provide the Oracle DB connection string. |
|
Yes, if the database type is Oracle |
| dc_hadr_standby_servername | For Db2 HADR: Enter the standby server name. | <hostname> | Yes |
| dc_hadr_standby_port | For Db2 HADR: Enter the standby server port. | "50000" | Yes |
| dc_hadr_validation_timeout | For Db2 HADR: Specify the validation timeout entry. | 15 | No |
| dc_hadr_retry_interval_for_client_reroute | For Db2 HADR: Specify the time in seconds between connection attempts made by the automatic client reroute (ACR) if the primary connection to the server fails. | 15 | No |
| dc_hadr_max_retries_for_client_reroute | For Db2 HADR: The maximum number of connection retries attempted by ACR if the primary connection to the server fails. This property is used only if the Retry interval for client reroute property is set. | 3 | No |
| connection_manager.min_pool_size | Specifies the minimum number of physical connections to maintain. With the default setting of 0, no connections are created with the database starts. | 0 | No |
| connection_manager.max_pool_size | Specifies the maximum number of physical connections that you can create in this pool. The maximum pool size for connections depends on the number of connections that are supported by your database driver. | 50 | No |
| connection_manager.max_idle_time | Use this setting to specify how long to wait to clean up idle connections. | 1m | No |
| connection_manager.reap_time | Specifies the interval, in seconds, between runs of the pool maintenance thread. | 2m | No |
| connection_manager.purge_policy | Specifies how to purge connections when a stale connection or fatal connection error is detected. | EntirePool | No |
| Parameters | Description | Default/Example Values | Required |
|---|---|---|---|
| dc_database_type | Specify the type for your Object Store database. This setting must be the same as the type for the Global Configuration Database. The possible values are "db2", "db2HADR", "db2rds", "db2rdsHADR", "oracle", "sqlserver", or "postgresql". | postgresql | Yes |
| dc_os_label | Provides a way to name your object store data sources. The name must not contain spaces. You then use the label value to include different database user names and passwords for the data sources in your ibm-fncm-secret. For more information, see Creating a secret to protect sensitive information. | os | No |
| dc_common_os_datasource_name | The JNDI name of the non-XA JDBC data source associated with the object store table space or database. The name must be unique. | FNOS1DS | Yes |
| dc_common_os_xa_datasource_name | The JNDI name of the XA JDBC data source associated with the object store table space or database. The name must be unique. | FNOS1DSXA | Yes |
| database_servername | The host name of the server where the database software is installed. This setting must be
the same as the type for the Global Configuration Database. If you enter an IPv6 literal address,
the IP address needs to be specified within square brackets "[]". For example, you
can specify the IP address as [2001:db8:a0b:12f0:1]. |
<hostname> | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_name | Provide the database name. | OS1DB | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_port | Provide the database port. For Db2, the default is "50000". | "50000" | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_ssl_secret_name | The name of the secret that contains the Db2/Oracle/PostgreSQL SSL certificate. The secret can contain multiple certificates in a single tls.crt field. | <secret_name> | Yes |
| dc_oracle_os_jdbc_url | Oracle: Provide the URL for the database. |
|
Yes, if the database type is Oracle |
| dc_hadr_standby_servername | Db2 HADR: Enter the standby server name. | <hostname> | Yes, if using HADR |
| dc_hadr_standby_port | Db2 HADR: The standby database server port. | "50000" | Yes, if using HADR |
| dc_hadr_validation_timeout | Db2 HADR: Specify the validation timeout entry. | 15 | No |
| dc_hadr_retry_interval_for_client_reroute | Db2 HADR: Specify the time in seconds between connection attempts made by the ACR if the primary connection to the server fails. | 15 | No |
| dc_hadr_max_retries_for_client_reroute | Db2 HADR: The maximum number of connection retries attempted by ACR if the primary connection to the server fails. This property is used only if the Retry interval for client reroute property is set. | 3 | No |
| connection_manager.min_pool_size | Specifies the minimum number of physical connections to maintain. With the default setting of 0, no connections are created with the database starts. | 0 | No |
| connection_manager.max_pool_size | Specifies the maximum number of physical connections that you can create in this pool. The maximum pool size for connections depends on the number of connections that are supported by your database driver. | 50 | No |
| connection_manager.max_idle_time | Use this setting to specify how long to wait to clean up idle connections. | 1m | No |
| connection_manager.reap_time | Specifies the interval, in seconds, between runs of the pool maintenance thread. | 2m | No |
| connection_manager.purge_policy | Specifies how to purge connections when a stale connection or fatal connection error is detected. | EntirePool | No |
| Parameters | Description | Default/Example Values | Required |
|---|---|---|---|
| dc_database_type | Specify the type for your Business Automation Navigator database. This setting must be the same as the type for the Global Configuration Database. The possible values are "db2", "db2HADR", "db2rds", "db2rdsHADR", "oracle", "sqlserver", or "postgresql". | "postgresql" | Yes |
| dc_common_icn_datasource_name | The JNDI name of the non-XA JDBC data source associated with the IBM Content Navigator table space or database. The name must be unique. | "ECMClientDS" | Yes |
| database_servername | The host name of the server where the database software is installed. If you enter an IPv6
literal address, the IP address needs to be specified within square brackets "[]".
For example, you can specify the IP address as [2001:db8:a0b:12f0:1]. |
"<hostname>" | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_port | Provide the database port. For Db2, the default is "50000". | "50000" | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_name | Provide the database name. | "ICNDB" | Yes, but not applicable to database type of Oracle which requires a JDBC URL |
| database_ssl_secret_name | The name of the secret that contains the Db2/Oracle/PostgreSQL SSL certificate. The secret can contain multiple certificates in a single tls.crt field. | "<secret_name>" | Yes, if using SSL with Db2 |
| dc_oracle_icn_jdbc_url | Oracle: Provide the URL for the IBM Content Navigator database. |
|
Yes, if the database type is Oracle |
| dc_hadr_standby_servername | Db2 HADR: Enter the standby server name. | "<hostname>" | Yes |
| dc_hadr_standby_port | Db2 HADR: Enter the standby database server port. | "50000" | Yes |
| dc_hadr_validation_timeout | Db2 HADR: Specify the validation timeout entry. | 15 | No |
| dc_hadr_retry_interval_for_client_reroute | Db2 HADR: Specify the time in seconds between connection attempts made by the ACR if the primary connection to the server fails. | 15 | No |
| dc_hadr_max_retries_for_client_reroute | Db2 HADR: The maximum number of connection retries attempted by ACR if the primary connection to the server fails. This property is used only if the Retry interval for client reroute property is set. | 3 | No |
| connection_manager.min_pool_size | Specifies the minimum number of physical connections to maintain. With the default setting of 0, no connections are created with the database starts. | 0 | No |
| connection_manager.max_pool_size | Specifies the maximum number of physical connections that you can create in this pool. The maximum pool size for connections depends on the number of connections that are supported by your database driver. | 50 | No |
| connection_manager.max_idle_time | Use this setting to specify how long to wait to clean up idle connections. | 1m | No |
| connection_manager.reap_time | Specifies the interval, in seconds, between runs of the pool maintenance thread. | 2m | No |
| connection_manager.purge_policy | Specifies how to purge connections when a stale connection or fatal connection error is detected. | EntirePool | No |