Deployment and upgrade process
This topic introduces the key concepts that are involved in performing an upgrade.
Before you upgrade a production system, you should always test it first in a test environment. If this is a test upgrade, remember to set the older version's configuration files to point to the database clone and not the production database. For information about setting up a staged test environment, see Staging a test environment for the upgrade process.
Upgrade order
If you plan to upgrade multiple applications, follow these guidelines to determine the optimal order for performing the upgrades. In part, the order depends on the reporting solution that you used in the old version and will use in the new version. For further information about the impact of reporting on the upgrade process, see Reporting and the upgrade process.
- Jazz Team Server
- If you are using configuration management, the Link Index Provider and the Global Configuration Management applications must be upgraded after Jazz Team Server and before any other applications.
- If you are using a data warehouse or Lifecycle Query Engine for Jazz Reporting Service, update the data warehouse or Lifecycle Query Engine, and then update the Jazz Reporting Service.
- The other Engineering Lifecycle Management applications, in any order.
If you have set up Engineering Workflow Management and Engineering Test Management applications in a cluster environment and not using Eclipse Amen, upgrade your MQTT server from IBM Message Gateway to Eclipse Amen.
You must upgrade the WebSphere® Liberty server to a version that is compatible with the target Engineering Lifecycle Management version. Jazz Authorization Server must be upgraded to a version that is compatible with the WebSphere Liberty server.
Upgrade instructions
Step-by-step instructions are provided in the Interactive guide: Upgrading Engineering Lifecycle Management applications for performing an upgrade of each application using the upgrade scripts that are provided. Additional instructions are provided for performing a manual upgrade without using the upgrade scripts. It is recommended that you follow the upgrade script instructions if you are deploying to a single server or if you are performing a distributed deployment and you can mount and access the drives where each application and the Jazz Team Server are installed. Follow the manual upgrading instructions if you are performing a distributed network deployment and you cannot access the network drive. If you are upgrading from version 5, follow the steps in Upgrading from version 5 to the current release, and then use theInteractive guide: Upgrading Engineering Lifecycle Management applications.
Deployment considerations and limitations
In an Engineering Lifecycle Management deployment, Jazz Team Server must be at the same level as or newer than the applications that are registered with it, but the applications cannot have a newer version than Jazz Team Server. If you have a distributed environment with separate WebSphere Liberty server servers, you can upgrade each application separately. But remember, Jazz Team Server must be upgraded first. If you have one server, you can upgrade all products at the same time.
You can upgrade a single application or multiple applications. If you plan to upgrade multiple applications, it is highly recommended that you upgrade a single application and verify the success of the upgrade before moving on to the next application. Jazz Team Server must be upgraded first.
Database deployment considerations
Consider the following deployment plans for your databases.
- Be sure to back up your databases before beginning the upgrade.
- If you use Db2® or Oracle, review the instructions in the database setup topics before starting the upgrade. Proper database tuning is essential for optimized performance during the upgrade. For details about database setup, see Setting up a Db2 database, Setting up an Oracle database
Impact of an upgrade on your deployment
The old version and the new version Public URIs for each application must match. See Planning your URIs for further details about Public URIs.