April 23, 2019
The foundation of the Collaborative Lifecycle Management solution
Jazz Foundation 7.0 M4 Milestone
Fixes in this release
This release includes authorized program analysis report (APAR) and non-APAR fixes.
For a list of APAR fixes, see the APARs fixed in 7.0 query.
For a list of non-APAR fixes, see the non-APARs fixed in 7.0 query.
Known problems and workarounds
Floating, Token and Authorized license labels still reference Rational
The Floating, Token, and Authorized licenses still have the Rational labels, while EA licenses have the new product names. The Floating, Token and Authorized product labels will be fixed in the RC2 milestone.
Tomcat is no longer supported as an application server
Starting in Engineering Lifecycle Management (ELM) V7.0 release, Tomcat is no longer supported as an application server. See the blog about support and planning notes.
When upgrading a Tomcat-based deployment to 7.0 (or later), you must base the new deployment on WebSphere Application Server or WebSphere Application Server Liberty Profile. The Interactive Upgrade Guide generates instructions for migrating from Tomcat to Liberty Profile. Migrating to a WebSphere Application Server profile must be done manually.
The command options related to migrating to a new Tomcat installation are removed from the upgrade scripts and the repository tools migration commands. The following attributes are no longer supported, and result in errors if you use them:
Tip: For upgrade scripts, the attributes requires a leading dash such as -updateTomcatFiles. Whereas, the repository tools migration command is without a dash proceeding an attribute, such as:
repotools-<app> -migration_<app>_updateConfigurationFiles updateTomcatFiles=yes, where <app> is one of jts, ccm, rm, qm, gc, dcc, or relm.
To search for post-release issues that IBM Support documented, visit the IBM Support Community.