Home/Field Guide/Security & operations
CONCEPT 26
Upgrades, Jakarta, and compatibility
Rehearse the platform and application upgrade as one coordinated change.
Inventory the boundary
Liferay documents Jakarta beginning with DXP 2025.Q3 and the 2026 Q1 Portal releases. The impact includes server compatibility, affected imports, dependency coordinates, descriptors, generated code, and OSGi wiring. Some Java SE packages still start with javax, so use the documented migration tooling and review its changes. Confirm the JDK, server, database, and search engine in the matrix for the destination.
Run the rehearsal
- Collect the source and target builds, patch levels, supported upgrade route, and release notes. Inventory Java modules, templates, scripts, custom integrations, and feature flags.
- Make consistent backups of the database and document store. Restore them into a private rehearsal environment, and record recovery duration.
- Recompile extensions for the target. Migrate affected Java and dependency namespaces, regenerate REST Builder outputs as required, and run bundle and component checks.
- Run the documented platform and database upgrade and verify data and module schema upgrades. Run indexing steps as required.
- Test sign-in, permissions, Objects, workflow, search, API contracts, and site publishing with representative roles and data.
- Record go/no-go criteria, cutover timing, and the recovery procedure if an upgraded schema or dependency cannot be reversed in place.
Compare two failures
An unresolved OSGi import can indicate a missing or incompatible package after migration. Compare manifest imports with the target exports. A failed object or content query after an otherwise successful upgrade can indicate stale search data, permission filtering, or a change in the API contract. Read the upgrade log and isolate the failing layer.