Adapting to JakartaEE

As part of our continued modernization efforts, IdentityIQ is aligning with JakartaEE 10. While this upgrade brings significant long-term benefits in terms of platform modernization, supportability, and future innovation, we understand that it may require adjustments, particularly for customers with customized IdentityIQ environments.

This article outlines what the transition means for you and how to prepare.

If your organization has developed custom application connectors, plugins, or any custom Java code using the older Java EE standard, these components will require updates to align with the new Jakarta APIs. The most significant change is the package namespace: any references from javax.* will need to be rewritten to jakarta.*.

For example:

• If a plugin is invoking javax.servlet.* classes, that code will need to be re-written to invoke jakarta.servlet.*.
• References to javax.faces.*, javax.ws.*, and other javax packages will also need corresponding jakarta rewrites.

Learn More

For detailed technical information about JakartaEE 10, please refer to the official JakartaEE documentation.

We are here to support you!!

To facilitate your transition to JakartaEE 10 and the update of custom applications as part of the IdentityIQ 9.0 upgrade, we will provide a new pre-check utility. This pre-check tool with help to:

• Identify all custom Java classes which conflict with Jakarta 10, and their respective locations in your environment
• Identity custom objects (rules, forms, workflows, etc.) which contain bean shell scripts which conflict with Jakarta 10
• Detect custom IdentityIQ applications with formPaths which refer to XHTML files
• This utility will be your guide, helping you pinpoint which components need to be adjusted to meet the required JakartaEE syntax and Application configuration settings.

We will share these resources ahead of the next release to ensure you have time to plan and prepare.

The SailPoint IdentityIQ team will ensure that all relevant documentation is provided prior to the next release, giving you time to review and prepare. For any questions or concerns, please reach out your CSM.