Airlock IAM instances directory

Creating a new instance

Creating a new instance can be done from the command line with the following command:

iam init -h

For more details on the CLI see IAM Command-Line Interface (CLI).

Structure of the instances directory

The structure of the instance directory is as follows:

Directory structure			Contents
`instances/`			The top-level directory that contains the data of all instances.
	`<instance_1>/`		Data and configuration specific to `instance 1`.
		`audit-logger/`	Configuration and key materials for the audit logger.
		`h2/`	Data directory for the h2 database. See H2 as Airlock IAM database for details.
		`libs/`	Directory for custom code, database, and other libraries that extend the functionality of IAM.
		`log4j/`	Configuration of IAM logging. See Log4j 2 configuration files for details.
		`logs/`	Directory for log files.
		`pdfs/`	Directory for generated letters.
		`profiles/`	Directory to store profiles. See Sandboxing with profiles for details.
		`workingcopies/`	Backup directory for configurations.
	`<instance_2>/`		Data and configuration specific to `instance_2`.
	`common/`		Data and configuration shared by all instances.
		`adminapp-texts/`	Directory for language-specific customizations of the Adminmapp. See Customizing text elements in the Adminapp for details.
		`libs/`	Directory for custom code, database and other libraries that extend the functionality of IAM. Libraries in this directory are shared by all instances of IAM.
		`loginapp-texts/`	Directory for language-specific customizations of the JSP Loginapp. See Customizing text elements in the Loginapp (JSP) for details.
		`report -templates/`	Directory with templates for letter generation.
		`server-truststore/`
		`transaction-approval-texts/`	Directory for language-specific customizations of the Transaction Approval. SeeCustomizing text elements in the Transaction Approval module for details.

Content of the instance directory

File	Contents
`instance.properties`	Application properties of an IAM instance. See Application parameters for details.
`medusa-configuration.xml`	Configuration of IAM. This file is managed by the Config Editor and should not be changed manually. See IAM Config Editor (UI) for details.
`sensitive-values.jcks`	Files used to store external config secrets. See Storing sensitive configuration values externally for details.
`sensitive-values.properties`
`server.p12`	Contains the server certificate of the IAM instance.

Deleting an instance directory

The instances directory contains all the configuration files, customizations, and data files of the H2 database of all instances.

To delete all instances it is sufficient to delete the instances directory.
To delete a specific instance, it is sufficient to delete the directory with the instance's name.