Deployment and upgrade process

This topic introduces the key concepts that are involved in performing an upgrade.

The upgrade process is a side-by-side installation. Each product must be upgraded by installing the new version of the product and updating configuration files, adding or updating tables in existing database repositories, and upgrading the data warehouse. For an overview of the workflow, see the flow diagram at Example: Upgrade stand-alone products to an integrated solution.

Note: The old version of the product is not replaced when you install the new version. Do not uninstall the old version of the product until you have verified that the upgrade was successful and everything is functioning. For post-upgrade verification steps, see Verifying the 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 products, 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.

In an ELM deployment, Jazz Team Server must be upgraded first.

Upgrade instructions

Step-by-step instructions are provided in the Interactive upgrade guide for performing an upgrade of each product 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 (JTS) 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 the Interactive upgrade guide.

Deployment considerations and limitations

In an ELM 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 application servers or separate WebSphere® Application Server profiles, 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 product or multiple products. If you plan to upgrade multiple products, it is highly recommended that you upgrade a single product and verify the success of the upgrade before moving on to the next product. Jazz Team Server must be upgraded first.

If you upgrade multiple products that were on multiple application servers, those applications will continue to run on separate application servers after the upgrade. You cannot merge multiple products into a single application server. However, you can still register multiple applications with the same Jazz Team Server application.

Database deployment considerations

Consider the following deployment plans for your databases.

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.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki