Database
The settings relating to the authentication requirements can be made via this dialog.
The modifications are applied during operation and also adjusted in the associated XML configuration so that they are applied again after a system restart.
►NOTE◄ If changes are to be made at this point, the connection to the database server is re-established in the background and may result in the necessary table definitions being created.
|
# |
Description |
|
1 |
Adapts the configuration of _pro, if necessary on all nodes of a cluster, and persists it in the associated XML configuration |
|
2 |
Selected database type and corresponding driver. A profile can be selected by using the "Change"-Button, which fills the necessary fields with the correctly formatted values |
|
3 |
The name of the catalog (schema) within the database is also an alias depending on the database type |
|
4 |
The JDBC URL that represents the connection to the database. This URL is database-dependent, e.g. jdbc:mysql://myserver:3306/db. |
|
5 |
The user name and password to be used for authentication with the database |
|
6 |
Specifies the time in milliseconds that a connection must be unused in the pool before its further validity is checked by the DatabaseService. |
|
7 |
If this option is activated, SQL statements used by applications are cached. All statements must be checked by the DatabaseService and adjusted if necessary. For systems with sufficient resources, it therefore makes sense to save the result of this check/modification for future use. However, if primarily dynamic statements are used, explicit deactivation can make sense in order to avoid unnecessary saving of SQL statements that are never used again. |
|
8 |
Is the SQL command to be used to check the validity of a database connection? If no command is specified, the list of available tables is retrieved. However, this information is cached by some JDBC drivers, so that a connection can be considered valid even though it no longer is. |
|
9 |
The initial and maximum size of the service's connection pool. |
|
10 |
If this item is activated, the pool may grow if all initially created connections have been issued to applications and another one is required. |
|
11 |
Function for testing the assigned connection data on all nodes. |