Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
Installation · Lesson

Windows

Quick answer

On Windows, install a supported JDK, deploy the IdentityIQ WAR to Tomcat, point it at your database and initialize the schema.

Key takeaways

  • Prerequisites for Windows
  • Step-by-step install path
  • Common pitfalls and fixes
  • Verification after install

Installing SailPoint IdentityIQ on Windows Server means running the IdentityIQ web application inside a Java application server (Apache Tomcat is the reference) against a supported database such as Microsoft SQL Server. The steps mirror any other platform but follow Windows conventions for services, paths and permissions.

Prerequisites

  • A supported JDK version for your IdentityIQ release, installed with JAVA_HOME set.
  • A supported application server (Tomcat) matching the release notes.
  • A reachable database (SQL Server is common on Windows) with a schema account.
  • The IdentityIQ installation media and a service account with appropriate rights.

Step by step

  • 1. Install the JDK and set JAVA_HOME and PATH as system environment variables; confirm with java -version.
  • 2. Install Tomcat and set its heap in setenv.bat (for example -Xms/-Xmx sized for your volume).
  • 3. Prepare the database: create the database and login, then run the supplied DDL scripts to build the schema.
  • 4. Configure the datasource in IdentityIQ (iiq.properties/data source) pointing at SQL Server with the schema credentials.
  • 5. Deploy the identityiq WAR into Tomcat's webapps.
  • 6. Run schema/init using the IdentityIQ console, then start Tomcat (ideally as a Windows service).

Verify the installation

Confirm Tomcat starts cleanly, the schema is present at the expected version, and you can reach the login page and sign in as the default administrator. Then run a small test aggregation to prove connectivity end to end.

Windows-specific notes

  • Run Tomcat as a dedicated service account, not an interactive user, so it survives logoff and restarts.
  • Watch file and folder permissions on the Tomcat and IdentityIQ directories; permission errors are a frequent Windows startup failure.
  • Prefer a supported JDBC driver for SQL Server and, where appropriate, integrated security.

Common pitfalls

  • Java version mismatch with the release, the top cause of startup failure.
  • Database connectivity, wrong port, firewall, or login rights.
  • Insufficient permissions on the install directories for the service account.

Want to learn this properly?

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

See the courseAsk a question

Check your understanding

  1. What are the prerequisites for Windows?

    • 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.

  2. 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.

  3. Where do you look first on failure?

    • A. The application and app-server logs, which usually point to database, Java or permission issues.
    • B. Confirm the app server starts, the schema is present, and login works.
    • C. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
    Show answer

    A. 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 Windows refer to in SailPoint?

Installing SailPoint IdentityIQ on Windows Server means running the IdentityIQ web application inside a Java application server (Apache Tomcat is the reference) against a supported database such as Microsoft SQL Server.

What is involved in setting up Windows?

2. Install Tomcat and set its heap in setenv. bat (for example -Xms / -Xmx sized for your volume). 3. Prepare the database: create the database and login, then run the supplied DDL scripts to build the schema. 4. Configure the datasource in IdentityIQ (iiq.

Which systems are connected to Windows?

Run Tomcat as a dedicated service account, not an interactive user, so it survives logoff and restarts. Prefer a supported JDBC driver for SQL Server and, where appropriate, integrated security.

What tends to go wrong with Windows?

Java version mismatch with the release, the top cause of startup failure. Database connectivity, wrong port, firewall, or login rights. Insufficient permissions on the install directories for the service account.
CallWhatsAppEnquire