...
The following database management systems are supported:
- MySQL
- Microsoft SQL Server
- Oracle
Note |
---|
Databases that are compatible with and use the same JDBC drivers as the supported databases are also supported, for example AWS RDS (MySQL), MariaDB (MySQL), or Azure SQL Database (SQL Server). We recommend that customers periodically review the database documentation for Incompatibilities and Feature Differences as these may change over time. |
Anchor | ||||
---|---|---|---|---|
|
Note | ||
---|---|---|
| ||
MySQL versions 5.7.x and 8.0.x are supported. |
...
For Windows installations, you can speed up MySQL performance by adding the following parameter to the appropriate MySQL.ini
file:
Panel |
---|
innodb_flush_log_at_trx_commit=0 |
For more information about this parameter, see the MySQL documentation:
...
If you use SSL/TLS for JDBC communication to your MySQL environment, some additional configuration is required (depending on your needs). To use SSL/TLS for encryption only and bypass verification of the MySQL server certificate
The MySQL configuration property sslMode can be used to control the SSL behavior for database connections.
By default, network connections are SSL encrypted; the sslMode property permits secure connections to be turned off or different levels of security to be selected.
The following sslMode values are allowed:
sslMode Value | Description |
---|---|
"DISABLED" | Establish unencrypted connections. |
"PREFERRED" | Establish encrypted connections if the server enabled them, otherwise fall back to unencrypted connections. (Default value) |
"REQUIRED" | Establish secure connections if the server enabled them, fail otherwise. |
"VERIFY_CA" | Similar to REQUIRED; but additionally, verify the server TLS certificate against the configured Certificate Authority (CA) certificates. |
"VERIFY_IDENTITY" | Similar to VERIFY_CA; but additionally, verify that the server certificate matches the host to which the connection is attempted. |
To change the default behavior of SSL (PREFERRED), add the following to the uc.properties configuration file where sslModeValue is one of the values listed above (DISABLED, PREFERRED, REQUIRED, VERIFY_CA, VERIFY_IDENTITY):
Panel |
---|
uc.db.url.append.properties=&sslMode=sslModeValue |
This property replaced the deprecated legacy properties "useSSL
", "requireSSL
", and "verifyServerCertificate
...
To use SSL/TLS for encryption and verify the MySQL server certificate, add the following to the uc.properties configuration file AND import the MySQL server certificate CA into the Universal Controller Truststore:
...
", which are still accepted but translated into a value for "sslMode"
.
If "sslMode"
is not explicitly set:
- {
"useSSL=false"
} is translated to"sslMode=DISABLED"
. - {
"useSSL=true"
,"requireSSL=false"
,"verifyServerCertificate=false"
} is translated to"sslMode=PREFERRED
". - {
"useSSL=true"
,"requireSSL=true"
,"verifyServerCertificate=false"
} is translated to"sslMode=REQUIRED"
. - {
"useSSL=true"
AND"verifyServerCertificate=true"
} is translated to"sslMode=VERIFY_CA"
. - There is no equivalent legacy settings for
"sslMode=VERIFY_IDENTITY"
.
Note | ||
---|---|---|
| ||
For ALL server versions, the default setting of Applications that continue to use the legacy properties and rely on their old default settings should be reviewed. |
You may need to enable connections with TLSv1.2 and higher versions using the enabledTLSProtocols connection property. To specify the enabledTLSProtocols property, add the following to the uc.properties configuration file:
...
Prior to considering the enabledTLSProtocols connection property , you should verify the database connection using the latest Universal Controller maintenance release, as it may be using a more recent MySQL Connector/J, with functionality changed or added.
https://docsstonebranchdocs.stonebranchatlassian.comnet/confluencewiki/display/SMLRI/Universal+Controller+Maintenance+Lists
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html
...
Note | ||
---|---|---|
| ||
Oracle versions 12c (Release 2), 18c, 19c, and 19c 21c are supported. |
Step 1 | Download and install Oracle as per the Oracle documentation. |
---|---|
Step 2 | Create the Controller database. You can use any legal name, but we recommend the name uc. |
Step 3 | Make a note of the userid and password to be used later when installing the Controller. |
...
To check the current value for maximum open cursors, issue the following sql*plus utility command:
Panel |
---|
show parameter open_cursors |
A listing similar to the following will display:
Panel |
---|
SQL> show parameter open_cursors;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 1000 |
Setting a New Value for open_cursors
You can temporarily set the open_cursors
value with the following SQL:
Panel |
---|
alter system set open_cursors=1000 |
To make a permanent change, you must set the open_cursors
value in the initialization parameters file.
Note | ||
---|---|---|
| ||
If you do not set
|
Character Sets
Universal Controller does not stipulate a requirement for the Oracle database character set; for multilingual support, you can use the default Unicode character set of AL32UTF8.
...