The Database configuration category includes the following configurable options:
Database Type
Database Connection URL
Database Username
Database Password
Database Update Mode
Min Idle Connections
Max Idle Connections
Max Total Connections
Connection Max Lifetime (millis)
Max Wait (Seconds)
Default Query Timeout (Seconds)
Pool Prepared Statements
SQL Parameter Bind Mode
|
|
|
| ENUM | |
| Values |
|
|
The database platform being used. Smile CDR supports several relational database platforms for persistence so this setting selects the dialect that is specific to the platform being used. For example, if you are using Postgres 9.4, select the POSTGRES_9_4 dialect.
|
|
| (no default) | |
| No |
|
|
|
| STRING | |
|
JDBC Connection URL for the persistence database. The following examples show JDBC URLs for a few different database platforms:
|
|
| (no default) | |
| No |
|
|
|
| STRING | |
| Username for the persistence database. | |
| (no default) | |
| No |
|
|
|
| PASSWORD | |
| Password for the persistence database. | |
| (no default) | |
| No |
|
|
|
| ENUM | |
| Values |
|
| Controls whether Smile CDR should attempt to update the FHIR storage database schema on startup. If the database schema is out of date, Smile CDR automatically run migration on the FHIR storage schema at startup if the value is "UPDATE" If the value is "NONE", then Smile CDR will abort starting the FHIR storage module if its schema is out of date. When set to "NONE", you should use the "smileutil migrate" command to upgrade the database manually. | |
UPDATE
|
|
| No |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The minimum number of idle connections to keep in the database connection pool at any given time. | |
0
|
|
| No |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The maximum number of idle connections to keep in the database connection pool at any given time. | |
8
|
|
| No |
|
|
|
| POSITIVE_INTEGER | |
| The maximum total number of connections to allow the database connection pool to hold at any given time. Set this value carefully as it may negatively impact database performance when set too low or too high. | |
8
|
|
| No |
|
|
|
| POSITIVE_INTEGER | |
| If set, provides the maximum total number of milliseconds that a connection is allowed to live. Any connections that are open for longer will be closed instead of being reused. Note that this setting applies only to idle connections in the pool, it does not affect active database operations even if the timeout is exceeded. | |
| (no default) | |
| Yes |
|
|
|
| POSITIVE_INTEGER | |
| The maximum number of seconds that a request should wait for a database connection before timing out and aborting. | |
30
|
|
| No |
|
|
|
| NON_NEGATIVE_INTEGER | |
| This setting is the maximum number of seconds that a query may run before being automatically aborted by the database. This setting is a failsafe to prevent overly taxing searches from dominating the database. | |
60
|
|
| No |
|
|
|
| BOOLEAN | |
| If enabled, prepared statements will be pooled by the connection pool. Note that when using schema-based multitenancy, Smile CDR may choose to ignore this setting. | |
false
|
|
| No |
|
|
|
| ENUM | |
| Values |
|
| Specifies whether parameters in SQL statements should be inlined or bound to parameters. | |
NEVER_INLINE
|
|
| No |