MSSQL as Airlock IAM database

This page describes how to use an MSSQL database with the Airlock IAM database schema. In order to use Airlock IAM with this database, a JDBC connector/driver library is required.

 
Notice
  • 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.
  • In order to use Airlock IAM with this database, a JDBC connector/driver library is required.

Schema creation and upgrade

SQLs scripts for MSSQL databases are available here:

SQL File

Description

Creates tables used for Airlock IAM.

Upgrades IAM 8.5 database schema for release IAM 8.6.

Upgrades IAM 8.4 database schema for release IAM 8.5.

Upgrades IAM 8.3 database schema for release IAM 8.4.

Upgrades IAM 8.2 database schema for release IAM 8.3.

Inserts an administrator “admin” with password “password” (works with demo configuration).

 
Notice

For performance tuning hints, see: Performance tuning and scaling best practices

JDBC connector (JDBC driver)

  1. Look up the JRE release version installed with Airlock IAM:
    • Read the release file in the /jre folder of the IAM installation with the following command.
    •  
      Terminal box
      cat /opt/<airlock-iam-folder>/jre/release

    • OR

    • Run the command java -version in the/jre/bin folder of the IAM installation with the following command.
    •  
      Terminal box
      /opt/<airlock-iam-folder>/jre/bin/java -version
  3. Download the appropriate JDBC connector from here: MSSQL JDBC driver download and support matrix
  4. Copy the driver (JAR file) to the libs folder of the common instance (or an instance's folder).
    Example: 
  5.  
    Terminal box
    cp mssql-jdbc-*.jre*.jar instances/common/libs/
  6. Restart the IAM instance(s): see e.g. Starting and stopping IAM.

Database schema version

The database schema includes a table named schema_metadata, which stores the schema version. Additional information may be added to this table in future releases.

The schema version information serves two purposes:

  • Schema upgrade scripts can be made more robust by asserting the correct previous schema version.
  • It enables automated database schema upgrades.
 
Notice

Do not manually modify the schema version value in the database. Futurae migration scripts may rely on it.

Further information and links

Internal links: