If Airlock IAM has been started by systemd (see Starting and stopping Airlock IAM (system service integration)), you can use systemctl to get status information about the Airlock IAM process.
$ systemctl status airlock-iam*
● airlock-iam-auth.service - Airlock IAM - auth
Loaded: loaded (/home/airlock/iam/instances/auth/airlock-iam-auth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-10-25 17:25:20 CEST; 20h ago
Main PID: 20172 (java)
CGroup: /system.slice/airlock-iam-auth.service
└─20172 /opt/airlock-iam-7.7/jdk-11/bin/java -Xmx4G -Dpicocli.usage.width=120 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dorg.apache.catalina.startup.EXIT_O...
...In the output, you will find information about the Airlock IAM process at system level. Please refer to the systemd documentation for further information.
You may also inspect the systemd journal to get more information about a running IAM instance started by systemd.
Example:
$ journalctl -u airlock-iam*
-- Logs begin at Don 2018-12-06 12:49:30 CET, end at Don 2018-12-06 12:50:54 CET. --
Dez 06 12:49:44 centos7 systemd[1]: Started Airlock IAM - auth.
Dez 06 12:49:44 centos7 systemd[1]: Starting Airlock IAM - auth...
Dez 06 12:49:49 centos7 iam[708]: Loading parameters from: [/home/airlock/iam/instances/auth/instance.properties]
Dez 06 12:49:49 centos7 iam[708]: Application Parameters:
Dez 06 12:49:49 centos7 iam[708]: iam.adminapp.classpath.ext = instances/auth/libs/*,instances/common/libs/*
Dez 06 12:49:49 centos7 iam[708]: iam.adminapp.log4j.configs = instances/auth/log4j/adminapp.xml,/opt/airlock-iam-7.7/res/log4j/common.xml
Dez 06 12:49:49 centos7 iam[708]: iam.adminapp.url.path = /auth-admin
Dez 06 12:49:49 centos7 iam[708]: iam.audit-logger.config = instances/auth/audit-logger/medusa-audit-logger.properties
Dez 06 12:49:49 centos7 iam[708]: iam.config = instances/auth/medusa-configuration.xml
Dez 06 12:49:49 centos7 iam[708]: iam.config-editor.activation.timeout = 20
...