Note: The following changes are related to installation and upgrade procedures. Other changes and fixes are not included.
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. |
IBM Automotive Compliance licenses You can download the Automotive license from the License Key Center. You can download a .zip file that contains all offering contents, including the templates, from Passport Advantage. Note: The Automotive Compliance content license must be assigned together with a license belonging to the particular application the automotive template is used in. For example, if you are accessing an EWM project created by the Automotive sample, you must obtain an EWM license such as Contributor, Developer, or Developer for IBM Enterprise. |
|
All applications | |
Adding a new application to an existing Jazz Team Server You can use the Interactive Guide to add one or 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 is 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 breakages, the product links, URLs, context roots, application war files, configuration directories, script file names, or error codes did not change. |
|
Launchpad program updates In this release, the version of IBM Installation Manager bundled with the launchpad in the ELM web installer has been updated to 1.9.1.3. |
|
Log out from the application when using floating license If you log in to any ELM application and obtain a floating license for that application, make sure you log out of the application. If you log out of JTS, the floating license is not released immediately. |
|
Authentication |
Jazz Security Architecture SSO authentication You can also use a variant of OIDC authentication where the Jazz Application Server is configured to delegate a third party identity provider to validate user credentials. See the Application Passwords for Native Client Authentication with OpenID Connect for more details. |
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.x, 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 as an optional install Starting with release 7.x, IBM Engineering Lifecycle Optimization - Publishing (PUB) - Document Builder is 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 architecture, deploying, tutorials, administering, 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 Change and Configuration Management The IBM Engineering Systems Design Rhapsody - Model Manager application is shipped as an extension to the Change and Configuration Management application. The extension can be installed in two deployment modes: Model Management Server and Model and Code Management Server. For a brief description of the difference between these two modes as well as to define a list of required licenses, see Client access license management. The extension must be installed together with the Change and Configuration Management application when any deployment mode is selected, or on top of the previously installed instance of this application in the Model and Code Management Server mode only. Make sure the Change and Configuration Management application and the Architecture Management extension are at the same version. |
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.x is only supported from a version 6 release. Upgrading from a version 5 release to version 7.x 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.x. For instructions on upgrading from a version 5 release to the latest version 6 release, see the latest version 6 documentation. |
|
Full-text search indexes must be rebuilt when you upgrade from 6.0.6.1 or earlier Full-text search indexes must be rebuilt for both the ELM servers and the IBM Engineering Workflow Management Client for Eclipse IDE. Typically, when you upgrade an installation by using the upgrade scripts, the full-text search indexes from the earlier installation are copied to the new installation. However, the upgrade scripts in 7.0 and later do not copy previous indexes from version 6.0.6.1 or earlier (including interim fixes). Instead, the new server automatically rebuilds the indexes in the background after you start it. 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. Alternatively, instead of allowing the server to rebuild full-text search indexes online, you can rebuild them manually by running the repotools-<app> -rebuildTextIndices command after the upgrade is complete, but before you start the server, where <app> is one of am, ccm, or qm. Note that reindexing might be a lengthy process and can take many hours for a large database. In the web client, a system alert in the banner states that reindexing is in progress. If you follow a manual upgrade procedure instead of running the upgrade scripts, you must ensure that the full-text indexes are not copied from the old installation to the new installation. If the new installation is configured to use the same full-text index location as the old installation (the value of the com.ibm.team.fulltext.indexLocation property in the old and new teamserver.properties file is the same absolute path name), you must either run the repotools-<app> -rebuildTextIndices command before you start the server, or delete the contents of the folder at that location before you start the server. You might want to preserve the old contents if you decide to abandon the upgrade and roll back to the previous release. If an application is clustered, the offline reindexing procedure (using repotools) or the online procedure (ensuring that the full-text index folder is empty before starting the server) must be performed on each node in the cluster. The IBM Engineering Workflow Management Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the IBM Engineering Workflow Management Client for Eclipse to version 6.0.6.1 or later, the full-text search index is automatically deleted, which means the artifact history is cleared and will accumulate artifacts again after the upgrade. For ELM servers, complete one of these steps:
|
|
Pre-upgrade data verification For each application that you upgrade, make sure that you have applied the latest iFix available for the version you are migrating from. Then run repotools_xx -verify level=4 (where xx corresponds to the name of the repotools command for the application). If any problems are reported, run the corresponding repotools repair command before proceeding with the upgrade. |
|
Run TRS validation It is recommended to run TRS validation after you perform any upgrade. For more information, see Validating TRS feeds and the LQE index. |
|
Backup your data before running the addTables command Use the addTables command to migrate your database to a newer release.
|
|
![]() If you apply 7.0.2 iFix008 or later on an existing 7.0.2 iFix007 or earlier version, make sure you run both the -rebuildIndices repotools commands as shown in the example section for each of the following applications: Note: Do not run the commands shown in the example if you are upgrading from 7.0.1 or previous version to 7.0.2 iFix008 or later version.
|
|
Apache Tomcat |
Apache Tomcat is not supported Starting in version 6.0.1, Apache Tomcat was replaced by WebSphere Liberty as the default application server. In version 7.x, to migrate your Apache Tomcat to WebSphere Liberty, see the Interactive Upgrade Guide. |
Global Configuration Management |
Adding release links in global configurations If you are upgrading to version 7.0.2 from an earlier release and have associated EWM releases with global configurations, you must import release links into the GCM application as described in Adding release links in global configurations. If you do not perform this step, incoming links from work items might not be displayed correctly in the IBM Engineering Requirements Management DOORS Next and IBM Engineering Test Management after upgrade. |
Jazz Authorization Server |
Upgrading Jazz Authorization Server when used in a cluster environment The Interactive Upgrade Guide in version 7.0.2 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.2 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.2
|
Microsoft 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.
|
Rational Rhapsody Design Manager |
End of support Starting in version 7.x, the Rational Rhapsody Design Manager application is no longer delivered. However, you can keep your current Rational Rhapsody Design Manager version 6.0.6.1 in an upgraded ELM version 7.x. If you want to keep your Rational Rhapsody Design Manager version 6.0.6.1 in your IBM Engineering Lifecycle Management version 7.x environment, read this article. |
Requirements Management |
Disable the CleanupUnusedIndexesVersionsTask There is an issue with this task in the Requirements Management application that is planned to be addressed in a future release. As a result, this task must be disabled in version 7.x. For details on how to disable this task, see the Interactive Upgrade Guide. |
Lifecycle Query Engine data sources must be reindexed when upgrading from any 6.x release 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. |
|
Check the minimum client compatibility version When you upgrade the Requirements Management application and select the Upgrade script as the upgrade method, after the configuration files are merged, an editor opens where you can check the Requirements Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, then the application teamserver.properties opens for review. If the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, review if the value is a supported version. If it is not a supported version, update the value or delete the entire property. |
|
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.x. |
|
Rhapsody Model Manager |
Updating license keys The Systems and Software Engineer license enables configuration management operations on your models in the Model Management Server deployment mode. Alternatively, if the Model and Code Management Server deployment mode is used, you are entitled to perform configuration management operations on both your models and code. To use the Model and Code Management Server deployment mode, the Developer role is required in addition to the Systems and Software Engineer role. If you are upgrading from release 7.0 to 7.0.2, the Systems and Software Engineer license must be updated for use with 7.0.2. If you plan to use Engineering Rhapsody Design Manager 6.0.6.1 with applications from IBM Engineering Lifecycle Management 7.x, the license keys for Engineering Rhapsody Design Manager must be updated. See Working with Rhapsody Design Management 6.0.6.1 in Engineering Lifecycle Management 7.x for more information. |
Upgrading from 6.x to 7.x Extension for CCM In version 7.x, 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. |
|
Improving the Rhapsody Model Manager application upgrade performance and execution If you have an AM application repository with a large number of artifacts, you can reduce the server downtime during migration by running the database migration tasks, while keeping the existing server active. See the Interactive Upgrade Guide for details. Note: It is recommended to run database migration tasks when you upgrade from version 7.0 or earlier. If you upgrade from version 7.0.1, items states are not updated; hence, it does not take a significant amount of time. |
|
WebSphere Application Server |
The required version of WebSphere Application Server is 9.0.5 In this release, the supported version of WebSphere Application Server is version 9. If you are using the traditional WebSphere Application Server rather than WebSphere Liberty installed by IBM Engineering Lifecycle Management, 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. However, it is recommended to move to WebSphere Liberty server. |
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here. |
© Copyright IBM Corporation 2020 | Contact | Privacy Policy | Terms of Use