Study guide

2.2 Installation Steps and Procedures

SailPoint Certified IdentityIQ Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The IdentityIQ Engineer Exam

1.1 Exam Format, Official Blueprint, and Study Strategy

2 Chapter 2: Infrastructure, Installation, and Extended Attributes

2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them

3 Chapter 3: Build, Deployment, Patching, Access, and Email

3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection

4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows

4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows

5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup

5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations

6 Chapter 6: Certification Campaigns and Certification Rules

6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules

7 Chapter 7: Policies and Policy Violations

7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations

8 Chapter 8: Reporting, Advanced Analytics, and Auditing

8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing

9 Chapter 9: Rules, Rule Libraries, and the SailPoint API

9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods

10 Chapter 10: Workflow Development

10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows

11 Chapter 11: Email Templates, Branding, and Localization

11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI

12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation

12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings

13 Chapter 13: Data-Loading Tasks and Application and Connector Rules

13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types

14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console

14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging

15 Chapter 15: Debug Pages and the Administrator Console

15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging

16 Chapter 16: Role Model and Identity Attribute Mappings

16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings

17 Chapter 17: Data Objects, Relationships, and Group Types

17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types

2.2 Installation Steps and Procedures

Key Takeaways Explain This Topic AI

Expand identityiq.war into a staging directory (identityiq_home) before changing any configuration files.

Change the .hbm.xml extended attribute mappings and run iiq schema before you create the database, because iiq schema regenerates the DDL scripts.

Database connection details for the IdentityIQ and plugin databases go in WEB-INF/classes/iiq.properties, and iiq encrypt produces an encrypted password for that file.

Load the base configuration by running iiq console and then import init.xml; Lifecycle Manager objects come from init-lcm.xml.

The default login is spadmin with password admin, and the installation guide says to change it immediately.

Last updated: September 2026

Installation Steps and Procedures

Objective 1.2 asks you to demonstrate knowledge of the IdentityIQ installation steps and procedures . DOMC items often describe one step and ask whether it is valid at that point, so learn the order and which file or command belongs to each step.

  • Step-by-Step Installation
  • 1. Stage the Application

Download the installation zip from SailPoint. It contains identityiq.war and the database , doc , and integration folders. Create a staging directory and expand the WAR into it, for example with jar -xvf identityiq.war . The installation guide calls this directory identityiq_home . On UNIX, make the launcher executable with chmod +x WEB-INF/bin/iiq .

2. (Optional) Change Extended Attribute Columns, Then Run iiq schema

If you need more searchable or extended attributes than the default mapping files provide, edit the .hbm.xml files in WEB-INF/classes/sailpoint/object now (section 2.3). Then run: cd identityiq_home/WEB-INF/bin

./iiq schema

iiq schema regenerates the database creation scripts from your changed mappings. This is why extended-attribute planning happens before you create the database.

3. Create the Databases and Tables

The DDL scripts are in identityiq_home/WEB-INF/database . Two naming patterns matter:

create_identityiq_tables-<version>.<db> (for example, create_identityiq_tables-8.1.mysql ) matches the default extended attribute layout.

create_identityiq_tables.<db> , without a version number, is the script iiq schema generates after you change the mapping files.

The scripts create the application database, the plugin database, their tables and indexes, and database users with the right privileges. From 8.4, they also create the Access History database. You can change names and passwords, but you must keep table names, column names, and column types. The Oracle script must be edited to set the DATAFILE location and uncomment the database creation commands. For SQL Server, Aurora, and Azure SQL, the guide requires a case-insensitive collation . Run the script with a database client, for example: mysql -u root -p

  • mysql> source create_identityiq_tables-8.4.mysql;
  • 4. Create Site-Specific Encryption Keys

A default encryption key is compiled into the product for demonstration environments . SailPoint strongly recommends a site-specific key so that secrets cannot be decrypted outside your installation. Run iiq keystore , then addKey , to create the file-based keystore. By default this is WEB-INF/classes/iiq.dat , with the master password file iiq.cfg . Then restart the application server. Every instance in a multi-host installation needs the same iiq.dat and iiq.cfg , either in WEB-INF/classes or at the path set in iiq.properties ( keyStore.file , keyStore.passwordFile ).

5. Configure iiq.properties

Edit identityiq_home/WEB-INF/classes/iiq.properties and set the host name, database type, database name, user, and password for both the IdentityIQ and plugin databases. A clear-text password works, but SailPoint recommends an encrypted one. Generate it from WEB-INF/bin : ./iiq encrypt MyDbPassword

Paste the output into the property. If the JDBC driver for your database is not bundled, copy it into WEB-INF/lib .

  • 6. Import the Initial Configuration Objects
  • Start the console from WEB-INF/bin and import the base objects: ./iiq console
  • > import init.xml
  • > import init-lcm.xml
  • > quit

init.xml loads the system configuration, default task definitions, rules, workflows, and other base objects. init-lcm.xml adds the Lifecycle Manager objects. Lifecycle Manager is a separately licensed module, and the installation guide points LCM customers to its activation steps. The console tries the default spadmin / admin credentials first and prompts you if they fail.

7. Deploy and Start the Application Server

Copy the staged directory into the application server, for example tomcat/webapps/identityiq , or package it as a WAR. If you deploy a WAR file instead of an expanded directory, set resources.checktimestamps=false in WEB-INF/classes/packtag.properties . IdentityIQ also needs class loader isolation so that its bundled libraries win over the application server's copies. WebSphere, JBoss, and WebLogic each have extra steps in the guide.

8. Log In and Secure the Default Account

Browse to the application, for example http://localhost:8080/identityiq on a default Tomcat install. Log in as spadmin with the password admin . Change that password right away under Identities > Identity Warehouse > spadmin > Change Password . spadmin is a protected user, so authorization lockout does not apply to it unless you enable protected-user lockout.

  • Step Key file or command Common mistake
  • Stage identityiq.war → identityiq_home Editing files inside the zip instead of the staging directory
  • Schema .hbm.xml + iiq schema Running it after the database already exists
  • Database WEB-INF/database/create_identityiq_tables* Using the versioned script after regenerating a custom one
  • Keys iiq keystore → iiq.dat , iiq.cfg Keeping the demo key in production, or keys that differ between hosts

Connection WEB-INF/classes/iiq.properties , iiq encrypt Configuring only the main database and forgetting the plugin database

  • Objects iiq console → import init.xml , init-lcm.xml Starting to configure the UI before init.xml is imported
  • Access spadmin / admin Leaving the default password unchanged
  • Why the Order Matters

Authentication is disabled while there are no identities. The documentation notes that this situation exists during setup, before init.xml is imported. After the import, spadmin exists and normal authentication applies. If you start using the UI against an empty database, core objects such as the system configuration are missing, and pages fail.