Study guide
3.2 Installing Patches and Performing Upgrades
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
3.2 Installing Patches and Performing Upgrades
Key Takeaways Explain This Topic AI
Back up the database and every customization and stop all running tasks before patching or upgrading.
A patch archive is expanded into the existing installation directory, then the patch DDL script and iiq patch <version> are run.
A new version must be expanded into an empty directory, because expanding over an old version leaves obsolete files that cause failures.
iiq upgrade runs once per installation, not once per application server, after upgrade_identityiq_tables has been applied.
E-fixes match one patch level and must not be carried into an upgraded installation, and the IQService version must match the IdentityIQ version.
Last updated: September 2026
Installing Patches and Performing Upgrades
Objective 1.5, understand the process of installing patches and upgrades , is about two procedures that look alike but are not interchangeable. The exam often describes one step and asks whether it belongs to a patch, an upgrade, or neither.
Vocabulary
- Term Meaning Example
- Release (GA) A full product version IdentityIQ 8.4
- Patch A cumulative maintenance release for one version 8.4p2
- E-fix A narrow fix delivered for one specific patch level An e-fix built for 8.4p2
- Upgrade Moving to a new version 8.3 → 8.4
Read the release notes (for an upgrade) or the patch README (for a patch) first. They list supported platforms, required actions, and behavior changes. SailPoint's upgrade chapter opens with "Do not perform the upgrade until you have completely read the Release Notes."
Preparing: Identical for Both
Check what is running. On the Task Results and Report Results pages, confirm that no task-generated processes are running, and terminate any that are before shutting down. Workflow approvals also appear on Task Results. They are not running processes, so do not terminate them .
Back up the database and customizations. Any customization inside the installation directory can be overwritten. This includes .hbm.xml extended-attribute files in WEB-INF/classes/sailpoint/object and web content such as XHTML, JavaScript, and images. SailPoint recommends keeping customized files in a separate custom directory so that you can copy them back.
Stop the application servers on every host.
Installing a Patch
The patch archive is designed to go over the current installation:
Expand the patch archive into identityiq_home , for example jar -xvf identityiq-8.4p2.jar .
Run the patch database script from WEB-INF/database for your database type, for example upgrade_identityiq_tables-8.4p2.mysql .
From WEB-INF/bin , run the patch command with the patch version: ./iiq patch 8.4p2 .
Reapply any overwritten customizations, restart the application servers, and verify the version on the Debug About page.
Every host must run the same patch level. An SSB-based build (section 3.1) handles this by putting the patch archive in base/patch and rebuilding the WAR.
Performing a Version Upgrade
SailPoint's installation guide sets the upgrade order:
Confirm the starting version. The guide says you can upgrade only from the latest released version, at any patch level.
Delete old installation files and download the new release.
Expand the new identityiq.war into a clean directory. The guide warns that unlike a patch release , a new version cannot be expanded into the same directory as the old one, because obsolete files would remain and cause unexpected failures.
Do not add previously used e-fixes. They are compatible only with the patch level they were built for.
Reapply file customizations. Copy your customized IdentityExtended.hbm.xml , LinkExtended.hbm.xml , and CertificationItemExtended.hbm.xml into the new installation. Account attribute changes must also be made to certification item attributes.
Upgrade the database. Edit upgrade_identityiq_tables.<db> the same way you edited the original creation script (names, schema), then run it with the client set to continue on error . If patches were applied to the old version, errors such as Duplicate column iiqlock are expected, because the patch already made those changes. If you need a plugin database that does not exist yet, run the plugin creation script separately.
Run iiq upgrade from WEB-INF/bin . It updates configuration and managed data in the database and runs once per installation , no matter how many application servers you have.
Upgrade external components together. Upgrade the IQService (stop with IQService.exe -k , uninstall with -u , extract the new version, install with -i , start with -s ) and any Connector Gateway, keeping the gateway's init.xml .
Start and verify , then run the post-upgrade steps: post_upgrade_identityiq_tables.<db> removes tables, columns, and indexes that were needed only during the upgrade. The Data Export tables have their own upgrade script.
Reapply database-side customizations. Out-of-the-box task definitions, reports, rules, and workflows are overwritten by the upgrade. Reapply any edits you made to them. Also refresh any externally saved XML copies by exporting them again, because objects from the old version may no longer match.
Patch vs. Upgrade Side by Side
- Question Patch Upgrade
- Where are the files expanded? Over the existing identityiq_home Into an empty directory
Database script upgrade_identityiq_tables-<patch>.<db> upgrade_identityiq_tables.<db> , then post_upgrade_...
- Command iiq patch <patch-version> iiq upgrade (once per installation)
- E-fixes Check the README for which e-fixes the patch includes Never carry old e-fixes forward
External components Keep IQService at the matching version Upgrade IQService and Connector Gateway at the same time
Customized product objects Review the README Reapply modifications to OOTB rules, workflows, tasks, and reports
Exam Traps
Running iiq upgrade separately on every host is unnecessary, because the command changes shared database content.
Terminating pending workflow approvals from Task Results before an upgrade is wrong. They are not running processes.
Expanding a new major version over the old directory is the classic upgrade failure.
An IQService left at the old version after an upgrade breaks Active Directory provisioning.