For documentation on upgrading Jama Connect® v9.6 (KOTS), please refer to the attached document at the bottom of this page.
**New updated and improved PDF added February 16, 2024, for installing and Upgrading Jama Connect® v9.6.4 (KOTS)
The attached media will appear as a downloadable file at the bottom of the article.
Upgrading Jama Connect to 8.79.6, 9.0.4, or 9.6.x requires that you first update the Jama Connect KOTS platform. The updated KOTS platform optimizes how data is stored in Jama Connect and how KOTS resources communicate.
Upgrading your current environment involves significant maintenance downtime and requires a recovery plan to revert to the original environment. We suggest installing a new Jama Connect® environment, referred to as a clean installation, and transferring elements from your current environment to the new one.
Here are the supported upgrade scenarios:
- (Recommended) Clean installation of Jama Connect KOTS — This recommended scenario requires you to install a clean Jama Connect KOTS instance on a new application server, then copy data assets and the tenant.properties file from your current environment to the new one. The new instance must point to a restored backup of your database.
- In-place upgrade of Jama Connect KOTS — This scenario requires upgrading your current environment in place, which involves significant maintenance downtime and requires a recovery plan in case you need to revert to the original version. You must run a pre-upgrade script before running the Kubernetes (kURL) installer.
- KOTS preflight installation and upgrade checks MUST be run
Recommended upgrade paths -
You can use this table to determine your organization's best upgrade path.
Perform a clean installation of Jama Connect®.
If your environment is internet-enabled or air-gapped, we recommend installing a new Jama Connect® environment (a clean installation) to support new versions of the Jama Connect® application.
The process includes using a new application server and a database instance restored from
a backup of your current production instance. Once the new environment is up and running, you must copy elements of your current environment to the new environment (move from one KOTS environment to another KOTS environment).
Additional Documentation and Resources: