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 August 7, 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.
- Corrected Microsoft SQL Server instructions -- Changed the Jama Connect® version to 9.6.x, updated the SQL Server version to 2019 and 2022, and removed the collation step.
- Removed KOTS install curl command -- Removed the command "curl -sSL https://k8s.kurl.sh/jama-k8s-standardkots | sudo bash -s app-version-label=<version label>" to account for hotfix updates.
KOTS preflight installation and upgrade checks MUST be run
Upgrading Jama Connect® to versions 8.79.6 or 9.6.x requires updating the Jama Connect KOTS platform first. The updated KOTS platform optimizes data storage and communication for Jama Connect.
Recommended 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 restoring a database instance 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).
IMPORTANT
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
Related to
Comments
0 comments
Article is closed for comments.