Upgrade AIQ on Linux
Recommended guidance
Plan AIQ upgrades on Linux as controlled maintenance activities. Confirm the target AIQ version, operating system compatibility, database requirements, browser/Test Node compatibility, integrations, repositories, and rollback plan before making changes.
Pre-upgrade checklist
- Back up the database, configuration files, certificates, repositories, and custom scripts.
- Record the current AIQ version, OS version, Java/runtime dependencies, browser versions, and Test Node configuration.
- Review release notes for breaking changes, deprecated features, and migration steps.
- Notify users and schedule downtime if required.
- Confirm there is enough disk space for backups, packages, logs, and rollback files.
Upgrade validation
- Confirm AIQ services start cleanly after the upgrade.
- Validate login, Scenario Editor playback, Service Suite execution, reports, integrations, and repository access.
- Run representative smoke tests before releasing the environment to users.
- Review Output Logs and server logs for migration or compatibility errors.
- Document the final version, date, validation results, and any follow-up actions.
Rollback note: Do not begin the upgrade unless the team knows how to restore the previous database, files, and application version if validation fails.
Last updated: October 5, 2026