What's new in IBM Engineering Lifecycle Management in 7.0.3

Learn more about what’s new and changed in ELM 7.0.3.

Redesigned Engineering Lifecycle Management product documentation

The hosting of Engineering Lifecycle Management documentation is redesigned in IBM® documentation. The following changes are made to the hosting of ELM product documentation.

Common to ELM applications

Java™ 11 upgrade
IBM Semeru Runtime Certified Edition 11 (OpenJDK) is now included with ELM applications. Java 11 is the new prerequisite level of Java.
New stand-alone WebSphere® Liberty deployment option
The ELM installer now provides an option to install ELM to use in a separately-installed instance of the WebSphere Liberty application server. Previously, you installed an embedded instance of Liberty while installing the ELM applications. This option is similar to the way ELM applications were installed in prior releases to use with the traditional WebSphere Application Server. For more information, see Configuring ELM on a stand-alone IBM WebSphere Liberty server.
IBM Plex® typeface

Fonts from the IBM Plex typeface are introduced as part of the ongoing user experience transformation and alignment with open source Carbon Design system.

For example, the IBM Plex Sans font replaces Arial as the base sans-serif font. The IBM Plex typeface is now common across the following applications:
  • Engineering Requirements Management DOORS Next
  • IBM Engineering Test Management
  • Engineering Workflow Management
  • Engineering Rhapsody Model Manager
  • Engineering Insights
  • Data Collection Component
  • Global Configuration Management
  • Jazz® Team Server
Support for SameSite cookie attributes
The default IBM WebSphere Liberty server now automatically marks the required cookies as SameSite=None to ensure that they are shared with any server that requests them, enabling ELM to work as expected with browsers that recognize the SameSite cookie attribute.
Log4j version 2 adoption
ELM applications updated its logging from Log4j version 1 to Log4j version 2 in 7.0.2SR1 (iFix015). If you are upgrading from a release earlier than that, consider the following points while migrating to 7.0.3:

The format of the configuration properties file is changed. You can refer to a sample file, Log4j2.xml in the Install_Dir/server/conf/qm directory.

Merge your changes from the old log4j.properties file in the new Log4j2.xml file. For more information about the new properties format, see the logging services in the Apache Log4j2 documentation.

By default, logging dates follow ISO8601 format.

  • The format of the configuration properties file is changed. You can refer to the sample file, Log4j2.xml in the Install_Dir/server/conf/qm directory.
  • Merge your changes from the old log4j.properties file in the new Log4j2.xml file. For more information about the new properties format, see the logging services in the Apache Log4j 2 documentation.
  • By default, logging dates follow ISO8601 format.
Oracle Enterprise Edition usage
When you open ELM performance-related support cases on an Oracle database, the IBM support teams can help you if you can provide performance-related diagnostics. Oracle Enterprise Edition with Oracle Diagnostics Pack and Oracle Tuning Pack provide features for analyzing database performance that are not available in Standard Edition. Hence, the support teams may ask you to recreate the issue using Oracle Enterprise Edition.

Global Configuration Management

Display ID for components and configurations
To allow better identification of global components, configurations and baselines, especially with long names, GCM now displays the ID of these resources along with their names across the application. The IDs are visible on many pages like Browse and create components, Browse configurations, View configurations, and many more. You can add, remove, re-add, and sort columns.
The application now allows users to perform the following tasks:
  • Use ID as a query string in the Queries page.
  • Search or filter using ID of global components or configurations, wherever available.
  • Sort results based on the ID column.
  • Navigate to the Show history page from any configuration, and view the ID prefixed to configuration and baseline names.
Improved release pages
The Add releases and Import release links pages in GCM are updated with the following enhancements:
  • EWM project areas are grouped by servers.
  • Only project areas that the current user can access are displayed.
  • Performance is improved, where multiple EWM project areas exist.
Custom application badge labels in the configuration tree
GCM now provides the option to customize ELMapplication badge labels in the Configuration tree, Compare configurations, and Component skew pages. You can change the labels from domain abbreviations to product name abbreviations. For example, you can change the CCM domain abbreviation for Change and Configuration Management to the product abbreviation EWM. You can customize badge colors and define custom application labels.

A GCM admin can provide custom labels for ELM applications on the Advanced properties page.

Normalized whitespace in GCM artifact titles
GCM has now improved and expanded its whitespace normalization of artifact titles to prevent unwanted characters from data entry errors. Extra and redundant whitespace-related characters are removed or collapsed into a single space. For example, a global configuration title that is entered as <tab>Electric<space><space>Vehicle<space> is normalized to Electric<space>Vehicle.

Deprecated features

When a feature is deprecated, IBM continues to support the feature, but no longer plans to enhance it and might remove the capability in a subsequent release of the product.

Deprecated EWM integrations
The following EWM integrations are deprecated:
  • IBM Rational® ClearCase® via Bridge, Synchronizer, and Importers
  • IBM Rational ClearQuest® via Bridge, Synchronizer, and Importer
  • IBM Rational Change
  • IBM Rational Synergy
  • IBM Sametime®
  • Subversion and SVNKit
  • IBM announced end of life for Rational Change and Rational Synergy effective September 2024. For more information, see announcement letter 921-121.

Removals and replacements

IBM Watson® IoT Platform - Message Gateway

In prior releases, IBM Watson IoT Platform - Message Gateway provided MQTT services when the EWM and ETM nodes were clustered, where two-level GCs from EWM SCM and RMM were displayed in the GCM webUI, and where EWM Enterprise Edition (EWM-EE) live logging was implemented. In this release, ELM products use Eclipse Amlen as the replacement prerequisite.

Support removed for IBM AIX®
Use one of the following operating systems supported by ELM:
  • Red Hat® Enterprise Linux® is available on POWER®, x86 and other hardware platforms.
  • Microsoft Windows Server and SUSE Linux are supported on x86. Your database can continue to run on AIX.
Support removed for IBM WebSphere Application Server (Traditional WAS)
Use WebSphere Liberty, either embedded and installed with ELM applications, or separately installed.
Support removed for Microsoft SQL Server
Use Oracle or IBM Db2®.
EWM Enterprise Edition features are removed
Support removed for IBM Knowledge Center Customer Installed (KCCI)
Use IBM documentation offline. For more information, see the IBM documentation offline site.
Developer-10-C client access license
The Developer-10-C client access licenses for EWM are discontinued. These licenses will not be available for download from jazz.net. You can purchase Workflow Management Workgroup Developer licenses, or if you are only using the work item system, purchase Workflow Management Stakeholder licenses.