Installation overview
How IdentityIQ is installed and configured: prerequisites, the application server, the database and first login.
Installing IdentityIQ means deploying its WAR file to a Java application server (Tomcat, WebSphere or JBoss), pointing it at a prepared relational database, running the schema scripts, and installing IQService near any Windows targets. After the console import, you log in and begin defining applications and identities.
- Java app server plus a relational database are prerequisites
- Deploy the WAR and run the schema (create tables) scripts
- The iiq console imports initial objects and patches
- IQService is installed separately for Windows/AD targets
- Environments are promoted with deployment (object export/import)
The installation module covers standing up SailPoint IdentityIQ across the platforms and components you are likely to use, from operating systems and cloud providers to the application server, Java runtime, database and TLS. It goes deeper than most sites because the details are where installations succeed or fail.
What this module covers
IdentityIQ is a Java web application on an app server backed by a database, so installation is really about assembling those pieces correctly on your chosen platform. Each page walks one platform or component with prerequisites, steps, verification and pitfalls.
What you will find here
- Operating systems, Windows and Linux.
- Containers and cloud, Docker, Kubernetes, AWS, Azure, GCP.
- Components, Tomcat, Java, database, SSL.
- Operations, backup and restore.
How to use it
Read the platform page for your target environment (Windows, Linux, a cloud, or a container platform), then the component pages (Java, Tomcat, database, SSL) for the details. Always match the supported versions in the release notes.
Common pitfalls
- Unsupported Java version, the top cause of failed installs.
- Under-sized or mis-configured database.
- HTTP-only deployments exposing credentials.