Installation · LessonReviewed by Imran Q, SailPoint Trainer, 7 yrs · Updated · Published · IdentityIQ 8.4 · all levels
SailPoint Linux
Installing IdentityIQ on Linux with Tomcat, a JDK and a supported database.
Quick answer
On Linux, install the JDK, set up Tomcat, deploy the WAR, configure the datasource and initialize the schema, then run Tomcat as a service.
Key takeaways
- Prerequisites for Linux
- Step-by-step install path
- Common pitfalls and fixes
- Verification after install
Linux is the most common production platform for IdentityIQ. The pattern is the same as elsewhere, a supported JDK, an application server (Tomcat), the IdentityIQ WAR and a supported database, but Linux deployments favour a dedicated service user, tight file permissions and a systemd-managed service.
Prerequisites
- A supported JDK with
JAVA_HOMEset for the service user. - A supported Tomcat version.
- A reachable database (Oracle or SQL Server are typical) with a schema account.
- A non-root service user that owns the Tomcat and IdentityIQ files.
Step by step
- 1. Install the JDK, set
JAVA_HOMEin the service user's environment, confirm withjava -version. - 2. Install Tomcat under the service user; set heap in
setenv.sh. - 3. Prepare the database and run the supplied DDL scripts to create the schema.
- 4. Configure the JDBC datasource in IdentityIQ with the schema credentials.
- 5. Deploy the
identityiqWAR intowebapps. - 6. Initialise the schema via the console, then start Tomcat, ideally as a
systemdunit so it starts on boot and restarts on failure.
Verify the installation
Check the systemd service is active, the application logs show a clean start, the schema version matches, and login works. Run a test aggregation to confirm connectivity.
Linux-specific notes
- Run everything as a non-root service user; never run Tomcat as root.
- Set correct ownership and permissions on install directories and logs.
- Use a systemd unit for lifecycle management and boot persistence.
- Mind SELinux/AppArmor and open firewall ports to the database and targets.
Common pitfalls
- Wrong JDK version for the release.
- Permission or ownership errors from installing as the wrong user.
- Firewall blocking the database or target systems.
Want this with a live instructor and a lab tenant?