Installation · Lesson

Linux

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_HOME set 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_HOME in the service user's environment, confirm with java -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 identityiq WAR into webapps.
6. Initialise the schema via the console, then start Tomcat, ideally as a systemd unit 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 to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

What are the prerequisites for Linux?
- A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- B. Confirm the app server starts, the schema is present, and login works.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
How do you verify the install?
- A. Confirm the app server starts, the schema is present, and login works.
- B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- C. The application and app-server logs, which usually point to database, Java or permission issues.
Show answer
A. Confirm the app server starts, the schema is present, and login works.
Confirm the app server starts, the schema is present, and login works.
Where do you look first on failure?
- A. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- B. The application and app-server logs, which usually point to database, Java or permission issues.
- C. Confirm the app server starts, the schema is present, and login works.
Show answer
B. The application and app-server logs, which usually point to database, Java or permission issues.
The application and app-server logs, which usually point to database, Java or permission issues.

Frequently asked questions

What does the term Linux refer to in SailPoint?

Linux is the most common production platform for IdentityIQ.

What is another point to note about Linux?

Check the systemd service is active, the application logs show a clean start, the schema version matches, and login works.

What else is worth knowing about Linux?

A supported JDK with JAVA_HOME set for the service user. A supported Tomcat version. A reachable database (Oracle or SQL Server are typical) with a schema account.

What tends to go wrong with Linux?

Wrong JDK version for the release. Permission or ownership errors from installing as the wrong user. Firewall blocking the database or target systems.