This page describes how to use an MySQL database with the Airlock IAM database schema.
The chosen data layer has to be well managed and monitored. IAM is not responsible for the operation and backup/recovery. For production usage, the data layer should be clustered.
Compatibility
MySQL version 8.0 or higher is required for full compatibility with the IAM database schema. See Techzone for information on using older MySQL versions.
In order to use Airlock IAM with MySQL a JDBC connector/driver library is required.
The following MySQL database settings may be useful:
Purpose | Command Line | my.cnf |
|---|---|---|
Table names are used case insensitive. Note: Use this option to avoid issues with older demo configurations using table names in upper case. | --lower_case_table_names=1 | [mysqld] |
Set the database server to an explicit time zone. Do not use a dynamic time zone as CET/CEST. For further information, see | - | - |
SQLs scripts for MySQL databases are available here:
SQL File | Description |
|---|---|
Creates tables used for Airlock IAM. | |
Upgrades IAM 7.3 database schema for release IAM 7.4. | |
Upgrades IAM 7.4 database schema for release IAM 7.5. | |
Upgrades IAM 7.5 database schema for release IAM 7.6. | |
Upgrades IAM 7.6 database schema for release IAM 7.7. | |
Inserts an administrator "admin" with password "password" (works with demo configuration). |
For performance tuning hints, see: Performance tuning and scaling best practices
cp mysql-connector-java-*-bin.jar instances/common/libs/The MySQL JDBC connector license restrictions do not permit the distribution of the library with Airlock IAM.