Upgrading the server configuration on z/OS
This topic describes the steps required to upgrade a server for IBM® Engineering Lifecycle Management (ELM) applications that use Db2® for z/OS.
Before you begin
- Additional information about upgrade is available in the Upgrading section of the Jazz®.net Deployment wiki.
- Carefully review the compatibility reports and system requirements to ensure the upgrade configuration meets the new version requirements, with special attention to application server and Java™ support. Go to Software product compatibility reports and system requirements (https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html). In this interface, enter the product name and click the search icon. Select the relevant product in the search results and select the values of the required fields. Then, submit the search.
- Get the product installation media. You can download server installation files from jazz.net or Passport Advantage®.
- Upgrading from version 5 to version 7 is a two-step process. You must first upgrade your server to the latest fix pack of version 6 release, start the server and make sure your upgrade to version 6.x was successful, and then upgrade to version 7. For instructions on upgrading from version 5 to version 6.0.x, see the latest version 6 documentation.
- Understand the upgrade process. See Deployment and upgrade process.
- Plan for your applications to be unavailable: Your applications will be unavailable for a brief period while you back up everything and update your applications to version 7.0.2. All of the applications that are connected to Jazz Team Server will be offline while Jazz Team Server is offline. Be sure to provide time to completely back up your existing applications.
- Learn about licensing: Go to Step 24
to learn about licenses in this release.Important: You can download your token or term license key files from IBM License Key Center and your perpetual license key files from Passport Advantage.
- Check the client and server compatibility. 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. See Client and server version compatibility.
- Make copies of the SBLZSAMP JCL members so you can review the original files if necessary. Review the job logs of the samples after the jobs are submitted. The expected return code for every step is 0.
- Do not run jts/setup. The upgrade process configures the new installation based on your previous installation. To view or change the setup, use jts/admin.
- The upgrade process uses your existing ELM databases. The addTables and upgradeWarehouse commands will update the databases to the new version formats.
- If you are using Java ETLs in your current version,
install the Data Collection Component in the
new version. See Collecting data with the Data Collection Component.
To install and configure Data Collection Component on
z/OS, do the following:
- Install FMID HRRS702.
- Use the configuration utility, or directly create directories to support DCC using sample member BLZCPDCC and create database tables using sample member BLZCREDB.
- Register the DCC application using jts/setup.
- Starting with version 5.0.1, the Requirements Management (RM) application uses its own database.
- If you want to perform online migration for the Change and Configuration Management application, see Online migration for Engineering Workflow Management.
- If you installed multiple Jazz applications on the same application server profile, you must upgrade those applications at the same time. If you deployed each application into a separate application server profile, you can upgrade the applications independently.
- Before you upgrade your production environment, set up a test environment to avoid issues. For more information, see Staging a test environment for the upgrade process. Be sure to isolate the test environment from the production environment.