IBM Engineering Lifecycle Management version 7.0 Installation and Upgrade Notes

Note: The following changes are related to installation and upgrade procedures. Other changes and fixes are not included.

Installation notes


Upgrade notes


Installation notes

Description
Administering Configuring authentication session timeout

To control the authentication timeout behavior, you must set multiple configuration options in your application server and the ELM applications that you have installed. For details, see Configuring authentication session timeout.
All applications Adding a new application to an existing Jazz Team Server

There is a new Interactive Guide that you can use to add one ore more applications to an existing Jazz Team Server. You can use the Jazz Team Server administration web UI or the registerApp repository tools command to register new applications. Using the Jazz Team Server administration web UI is the most common method of registering new applications with an existing Jazz Team Server. After you register a new application, if applicable, a link to the setup wizard page in the message box will be provided. Click this link to go to the setup wizard page to configure the application registration such as the database connections and so on. For details, see Add new applications to an existing Jazz Team Server Interactive Guide.
Renaming the IBM Continuous Engineering Portfolio

The CE/CLM products were renamed in version 7.0. For details on the name change, read this blog.

Note: To avoid breaking the products, URLs, context roots, application war files, configuration directories, script file names, or error codes did not change.
The Launchpad program updates

In this release, the Launchpad program has been redesigned as follows:


-The server Evaluation installation and Custom installation sections contain updated guidance on planning installations for multiple server topologies.
-A section has been added for the Document Builder application.
-A section has been added to help users find additional download content (.zip files and other non-Installation Manager artifacts) for several ELM products.
-The version of Installation Manager bundled with the launchpad in the ELM web installer has been updated from 1.8.x to 1.9.
Clustering Quality Management clustered environment

Now you can set up a clustered environment to host a Jazz Team Server and multiple Quality Management (QM) WebSphere Liberty nodes. For details and installation instructions, see the Interactive Installation Guide.
Link Index Provider Installing LDX on a dedicated server

Starting in version 7.0, the Link Index Provider application can be installed on its own dedicated server. For details, see this Deployment wiki document.
Oracle database Troubleshooting Oracle password requirements

If during the Jazz Team Server setup wizard you encounter the error SQLSTATE: 99999, SQLCODE: 17067, you might have Oracle database password issues.

Oracle password complexity policy requires that passwords have minimum of 12 characters in length. In addition, the password must contain at least one uppercase character, one lowercase character, and one digit. If your password contains special characters, multibyte characters, or starts with numbers or special characters, you must enclose it in double quotation marks. For details, see the Oracle documentation.
Reporting Document Builder now available as an optional install

Document Builder, which previously was only available by installing IBM Engineering Lifecycle Optimization - Publishing (PUB), is now available to install as part of the IBM Engineering Lifecycle Management launchpad. If you use PUB to create customized printable documents, you can generate documents from Document Builder. See information about architecturedeployingtutorialsadministering, and generating documents.

Note: If you are deploying Document Builder along with IBM Engineering Lifecycle Management, Document Builder must be deployed on a separate application server profile from ELM. See this technote for details.
Rhapsody Model Manager Architecture Management Extension for CCM

Starting in version 7.0, the IBM Engineering Systems Design Rhapsody - Model Manager application is removed from the solution as a standalone application and is replaced by an extension to the Change and Configuration Management application.  The Change and Configuration Management application must be installed together with the extension, or prior to installing the extension. Also, both the Change and Configuration Management application and the Architecture Management Extension must be at the same version. For details, see the Interactive Installation Guide.
Troubleshooting Repository tools command to repair queryable tables

The CleanupUnreferencedCollectionRecordsAsyncTask can cause unintended deletion of rows from certain internal database tables resulting in the data not being displayed in some artifact section views. The CleanupUnreferencedCollectionRecordsAsyncTask is designed to remove rows that are no longer referenced from certain internal database tables. However, some rows that are still referenced might be incorrectly deleted. Though the rows are deleted, data is still available in the database and can be restored by using the repairQueryableTables command. For details, see Repository tools command to recreate incorrectly removed queryable table data.


Upgrade notes

Description
All applications Upgrade order

The upgrade order for an ELM solution is Jazz Team Server first followed by the Global Configuration Management application, and then other applications. The reason for this order is that the GC SDK which is bundled with the other applications, makes calls to the GCM server. If the GCM server is not newer or at the same level as the other applications, these calls could fail.
Upgrading from version 5.x

Upgrading to version 7.0 is only supported from a version 6 release. Upgrading from a version 5 release to version 7.0, is a two-step process. You must first upgrade your server to the latest fix pack of the version 6 release, start the server, ensure that the version 6 upgrade was successful, and then upgrade to version 7.0.

For instructions on upgrading from a version 5 release to the latest version 6 release, see the latest version 6 documentation.
Apache Tomcat Content removed from documentation

Starting in version 6.0.1, Apache Tomcat was replaced by WebSphere Liberty as the default application sever. However, it was unofficially supported and documented. In version 7.0, Apache Tomcat documentation is removed from the IBM Knowledge Center. For migrating your Apache Tomcat to WebSphere Liberty, see the Interactive Upgrade Guide.
 
Jazz Authorization Server Upgrading Jazz Authorization Server when used in a cluster environment

The Interactive Upgrade Guide in version 7.0 includes steps to upgrade the Jazz Authorization Server when used in a Change and Configuration Management or Quality Management cluster environment. For details, see the Interactive Upgrade Guide.
Jazz Reporting Service The Reporting applications must be at the same level as Jazz Team Server

If you upgrade Jazz Team Server to version 7.0 at this time and leave the Reporting applications at previous version, the Jazz Reporting Service will not work until it is upgraded to the same level as Jazz Team Server.
Licensing New licenses are required in version 7.0

You must obtain new licenses for version 7 applications if you are upgrading from any release of version 6. Version 7 applications do not work with version 6.x licenses. However, version 6.x applications work with version 7 licenses. For details, see the Interactive Upgrade Guide.
Rational Rhapsody Design Manager End of support

Starting in version 7.0, the Rational Rhapsody Design Manager application is no longer supported. However, you can keep your current Rational Rhapsody Design Manager version 6.x in an upgraded ELM version 7.0. If you wish to keep your Rational Rhapsody Design Manager version 6.x in your IBM Engineering Lifecycle Management version 7.x environment, read this article.
Reporting Lifecycle Query Engine data sources must be reindexed

If you use Lifecycle Query Engine, you must reindex your Requirements Management application after the upgrade. All other applications do not require reindexing in this release. For details, see the Interactive Upgrade Guide.
Requirements Management Disable the CleanupUnusedIndexesVersionsTask

There is an issue with this task in the Requirements Management application that will be addressed in a future release. As a result, this task must be disabled in version 7.0. For details on how to disable this task, see the Interactive Upgrade Guide.
Link validity data migration

To migrate your Requirements Management link validity data, you can use the -migrateLinkValidity switch while executing the rm_upgrade script, or use the Repository tools command to export the link validity data to a .CSV file and then re-import it to the Jazz Team Server tables. See the Interactive Upgrade Guide for details.

To upgrade the Requirements Management application and migrate the link validity data, Jazz Team Server must be running and the Requirements Management application must be shut down. If these two are installed on the same server, you must interrupt the upgrade execution several times. For details about this scenario, see this Deployment wiki document.
Reindexing might be required

After you upgrade the Requirements Management server and before you start it, run the repairUnreferencedVersions repository tools command to ensure that unreferenced versions of artifacts do not exist in the Jena index files.

If the repair utility finds errors and repairs them or if you used configuration management in your Requirements Management application for merging and delivering via changesets, run the reindex repository tools command to reindex the index files. For details, see the Interactive Upgrade Guide.
The upgrade is only supported from 6.0.2 and later

The Requirements Management application upgrade is only supported from version 6.0.2 and later. If your current Requirements Management application is at a different version, you must first upgrade to one of these supported versions and apply the latest interim fix for that version, before you can upgrade to version 7.0.
Rhapsody Model Manager Upgrading from 6.x to 7.0 Extension for CCM

In version 7.0, the IBM Engineering Systems Design Rhapsody - Model Manager application is removed from the solution as a standalone application and is replaced by an extension to the Change and Configuration Management application.

If your previous RMM application was installed on the same server as the CCM application, you must use server rename to move one of the applications to a new location before you can upgrade. See the Interactive Upgrade Guide for details.
SQL Server database Resolving the CRJAZ1431E error message

If during the upgrade you encounter the following error message: CRJAZ1431E - The model COMPONENT_ID_IDX was illegally changed to be unique, you can use the SQL Server Management Studio to resolve the issue.
  1. Log into SQL Server Management Studio.
  2. Set the indices property to Unique for both VVCMODEL_CHANGE_SET_ID_IDX and VVC_MODEL_COMPONENT_ID_IDX.
Upgrade Full-text search indexes must be rebuilt when you upgrade

After the upgrade, the new server automatically rebuilds the indexes in the background after you start it. This might take a while depending on the size of your index files. Results of full-text searches might be incomplete until the reindexing operation is finished; the progress of the reindex is periodically written to the server log file and also displayed as a system alert in the web UI banner.
WebSphere Application Server The required version of WebSphere Application Server is 9

In this release, the supported version of WebSphere Application Server is version 9. You must first upgrade your WebSphere Application Server to version 9, and then upgrade Jazz Team Server and ELM applications. For migrating WebSphere Application Server, see the WebSphere Application Server documentation.

© Copyright IBM Corporation 2019  |  Contact  |  Privacy Policy  |  Terms of Use