Announcing the IdentityIQ 9.0 Upgrade Pre-Check Utility
The IdentityIQ 9.0 Upgrade Pre-Check Utility, iiq-precheck, is now available. This utility scans your IdentityIQ environment and tells you which of your customizations need to change before you upgrade to IdentityIQ 9.0. It ships as a ready-to-run distribution and covers two distinct areas of upgrade work required for IdentityIQ 9.0.
Note: IdentityIQ 9.0 is not yet available (Release Date TBD) and early access to this tool is intended to aid in resource planning for your upgrade.
Why this matters
IdentityIQ 9.0 moves from Java EE 8 to Jakarta EE 10. This change allows IdentityIQ to run on Apache Tomcat 10.1 and 11, JBoss EAP 8, and WebSphere Liberty 25 and 26, as application servers such as Tomcat 10 and later only accept Jakarta APIs.
Java EE to Jakarta EE namespace changes
Any code you own that references javax.* will fail on a Jakarta EE 10 application server until it is updated to jakarta.*. Those references are spread across rules, workflows, and forms containing BeanShell; custom plugins and connectors; deployment descriptors; .xhtml files using Java EE 8 namespaces; and third-party or custom JARs/classes.
iiq-precheck finds them all and reports each one with its exact location and the recommended Jakarta replacement. It can also write transformed Jakarta-safe copies of your files to a separate output directory, leaving your originals untouched so you review every change before adopting it.
This utility handles the bulk of the namespace conversion, while certain cases need remediation from your developers, and the use of tags from Tomahawk is no longer supported.
Custom application definitions moving from xhtml to xml
Separately, iiq-precheck inventories your Connector Registry application templates and reports which ones reference a form or access file. This is how you identify the custom application UIs that still need to move from .xhtml to the newly supported XML source configuration format. The inventory includes custom applications, forms, business logic, and any element that utilizes a <script> tag. A detailed reference guide outlining the new XML format is packaged with iiq-precheck.
iiq-precheck outputs the templates missing a definition, the ones that already have a definition to migrate, or a complete inventory. These results are informational and reported separately from the Jakarta findings, so your teams can scope and schedule the UI work independently of the namespace work.
What you get
SailPoint ships iiq-precheck as a pre-built distribution ZIP. The ZIP contains documentation as well as the JAR. There is no source code to compile and no build to set up. Your administrators install it into an existing IdentityIQ deployment. It is run using the standard iiq command line, and accepts parameters to point it at the directories they want examined.
Reports focus on your customizations rather than SailPoint shipped files.
Start now
You do not need to wait for your 9.0 upgrade window. Running iiq-precheck against your current 8.5 environment lets you size the effort, plan remediation into your sprints, and remove the largest unknown from your upgrade.
Note: This upgrade utility is supported on IdentityIQ 8.5 and 9.0 (Release Date TBD)
Downloads
iiq-precheck-1.0.0-distribution.zip
Verify your download against the checksum file before installing.
Documentation
SourceConfigXMLReferenceGuide.pdf
Installation and usage steps are in the Precheck User Guide. The Source Config XML Reference Guide covers the XML source configuration format for custom application definitions.