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. |
| 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. |
|
|
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 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 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. |
| 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. |
|
|
Full-text search indexes must be rebuilt when you upgrade 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 6.0.6.1 and later do not copy previous indexes from version 6.0.6 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:
|
|
| 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.0, to migrate 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. |
| 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.
|
| Quality Management |
Run the 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. |
| Rational Rhapsody Design Manager |
End of support Starting in version 7.0, 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.0. If you wish to keep your Rational Rhapsody Design Manager version 6.0.6.1 in your IBM Engineering Lifecycle Management version 7.0 environment, read this article. |
| Requirements Management |
For Configuration Management enabled project areas, install ELM 7.0 iFix001 before upgrading to the next version If you enable Configuration Management in a project area and run the upgrade script, the upgrade process might leave some data in an incorrect state leading to unexpected changes in the requirements. Install ELM 7.0 iFix001 on version 7.0 before running the rm_upgrade script . See Work Item 130288 for more information. |
|
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. |
|
|
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. |
|
|
Link validity data migration To migrate your Requirements Management link validity data, you will use the -migrateLinkValidity switch while executing the rm_upgrade script or 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. |
|
|
Faster upgrade and indexing To ensure your Requirements Management application upgrade and indexing during product runtime completes faster, it is recommended to apply ELM 7.0 iFix001. After applying the ELM 7.0 iFix001, make sure you update the teamserver.properties file for RM by adding com.ibm.team.jfs.reindex.all.by.storageArea=true. For more information, see Work Item 499982. |
|
|
Check the minimum client compatibility version When you upgrade 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.0. |
|
|
Upgrading on IBM i operating system When you upgrade the Requirements Management application on IBM i operating system, additional considerations are required. In the section titled Run the upgrade script on IBM i in the Interactive Upgrade guide, instead of the step Enter this command to upgrade the Requirements Management application, perform the steps provided in the Deployment wiki in section titled Migrating the link validity data in a single-server topology using upgrade script with interaction, whether your server has link validity data or not. This section provides steps to upgrade a server with Requirements Management and Jazz Team Server installed on the same application server. You can use the same procedure for a distributed server as well. After you complete the steps in the wiki, resume with the remaining steps in the Interactive Upgrade Guide. |
|
|
Run the -repairVersionsWithIdenticalTimestamp repotools command If you used the Configuration Management feature of the Requirements Management application prior to version 7.0, there might be more than one version of an artifact in the configuration with the same timestamp. This could lead to ambiguity when determining the correct version of an artifact in a baseline. Before you upgrade to version 7.0, run the repotools -repairVersionsWithIdenticalTimestamp command in the IBM Engineering Requirements Management - DOORS Next application. For more details, see Repository tools command to repair versions with identical timestamps for details. |
|
| Rhapsody Model Manager |
Update license keys Write access to RMM requires the Developer role in addition to the Systems and Software Engineer role. Modification of architecture management artifacts can be done only in Rhapsody client; Developer license is used for Check In/Deliver operations. If you plan to use Rhapsody Model Manager 6.0.6.1 with applications from IBM Engineering Lifecycle Management 7.x, the license keys for Rhapsody Model Manager must be updated. See Working with Rhapsody Design Management 6.0.6.1 in Engineering Lifecycle Management for details. |
|
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. |
|
|
Register corresponding TRS feeds as data sources in LQE and LDX applications IBM Engineering Systems Design Rhapsody - Model Manager (RMM) version 6.x did not contribute to LQE and LDX. However; during the upgrade, RMM is converted to Change and Configuration Management with AM Extension for Change and Configuration Management application which supports Tracked Resource Set (TRS) specification. Therefore, you must register the corresponding TRS feeds as data sources in both LQE and LDX applications. If LQE/LDX are installed on a separate JTS from the CCM application, then perform the steps described in Connecting Lifecycle Query Engine to applications that use a different Jazz Team Server article, else perform the steps described in Connecting Lifecycle Query Engine to applications that use the same Jazz Team Server article. If you do not register the corresponding TRS feeds, you will not be able to fetch details of OSLC links established between EWM artifacts owned by the upgraded server and artifacts owned by other EWM or ETM applications. Details of such OSLC links are fetched from LQE when generating JRS reports, where LDX is used to display data in Web Clients. |
|
|
When using custom context root, specify the context root used by RMM 6.x IBM Engineering Systems Design Rhapsody - Model Manager (RMM) application V6.x is a standalone application that uses "/am" context root by default. In version 7.0, RMM is removed from the solution as a standalone application and is replaced by an extension to the Change and Configuration Management (CCM) application. The upgrade of RMM application V6.x to CCM application 7.x with extension must be treated in the same way as the upgrade of CCM application V6.x to CCM V7.x with the custom context root "/am". When you perform this migration using the Interactive Upgrade Guide, make sure you select Yes for Did you use a custom context root in your previous deployment? option. In the Enter the context root you used for your application section, specify the context root used by RMM 6.x ("am" or the other root if it is not equal to the default one). |
|
| 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