Please refer to the attached document for documentation on upgrading Jama Connect® from Traditional to KOTS version 9.6.x.
KOTS preflight installation and upgrade checks MUST be run
Jama Connect® is a Linux-based application that runs on Docker containers and uses replicated software to "orchestrate" the deployment of applications. The current version of Jama Connect® uses Replicated KOTS, while older versions use traditional Replicated software. Upgrading Jama Connect® from traditional to KOTS includes planning, preparing your environment, and installing the software.
Upgrade scenarios
Upgrade with new servers (recommended) — This recommended scenario uses new application and database servers to support your KOTS Replicated environment. It requires you to:
-
Copy targeted data from the existing application server into the new environment.
-
Restore a backup of your current database to the new database server.
While this scenario results in the temporary overhead of supporting two separate environments, it has less risk of unwanted downtime.
Upgrade with existing servers — This scenario reuses the current application and database servers from your traditional Replicated environment. This scenario:
-
It requires you to uninstall elements of the traditional Replicated platform before you can install the KOTS Replicated platform.
-
It can cause significant maintenance downtime. Make sure to inform your users of this maintenance window. Also, have an emergency plan to revert to the traditional Replicated environment if necessary.
-
Before you upgrade
-
-
Please get in touch with your Customer Success Manager to request a KOTS internet or airgap license.
-
Choose the upgrade scenario that works best for your organization. Whichever scenario you choose, expect production downtime while the new instance is configured. It is best to upgrade during off hours.
-
Please follow the instructions in the planning [2] and preparing [8] sections to ensure a successful upgrade.
- KOTS preflight installation and upgrade checks MUST be run
-
Additional Documentation and Resources:
Related to
Comments
0 comments
Please sign in to leave a comment.