Rational solution for Collaborative Lifecycle Management (CLM) 6.0.6 iFix003
IBM Internet of Things Continuous Engineering Solution (IoT CE) 6.0.6 iFix003

New & Noteworthy

See the new and noteworthy information for the 6.0.6 iFix003 release listed by application:

Jazz Foundation and Global Configuration Management Rational Team Concert Rational DOORS Next Generation Rational Quality Manager Rhapsody Model Manager Rational Engineering Lifecycle Manager Jazz Reporting Service

Jazz Foundation and Global Configuration Management

Global Configuration Management Faster configuration tree updates

Several tasks that refresh and update global configuration trees are now faster, so you don’t have to wait as long for them to finish:
  • Adding configurations
  • Removing configurations
  • Replacing configurations
  • Moving configurations
  • Refreshing the tree
  • Expanding global configurations in the tree
These tasks are faster in both the web client and the REST API.
Improvements to the component skew report

To generate a component skew report, you right-click a configuration in the configuration tree and click Detect Component Skew.

The component skew report was enhanced as follows:
  • The Where Used column was renamed to Location.
  • The location is now shown for nested local configurations and external contributions. Previously, the location field was empty for these configurations.
    Note: Nested local configurations are only shown if the Use MQTT for contribution cache advanced property is enabled.
  • The name of the component is more prominent and an indicator shows which application the component is from.
TRS feeds Validate TRS feeds against data in the repository

You can now validate process, user, and validity TRS feeds against the data in the repository.

Validate TRS feeds if Jazz Reporting Service reports don’t show the artifacts that you expect, show artifacts more than once, or show a different number of artifacts than application views.

You can also ask a Lifecycle Query Engine (LQE) administrator to validate a TRS feed against the LQE index. If both validations finish with no errors, the LQE index matches the data in the application repository.

To validate TRS feeds:
  1. Open the application administration page for the TRS feed to validate:
    User and validity feeds for Jazz Team Server: https://host:port/jts/admin
    Process feeds for Rational Team Concert: https://host:port/ccm/admin
  2. On the toolbar, click Report Validation.
  3. In the Data Sources section, click a TRS feed and click Validate.

Image of a successful validation on the Report Validation page:

Image of a validation with errors:
Back to top

Rational Team Concert

Tracking and planning Report diagnostics include data sources for SCM

The Reports Diagnostics page now includes the data sources for source-control management (SCM).

Image of the Reports Diagnostics page:
Upgrading Instructions for upgrading a clustered environment

The Interactive Upgrade Guide now includes instructions for upgrading a clustered Rational Team Concert environment. To generate the upgrade instructions, in the interactive guide, select Yes for the question "Are you upgrading a cluster of Change and Configuration Management applications?"
Back to top

Rational DOORS Next Generation

Components Component picker shows components based on the current global configuration

When you select a component, if a global configuration is selected, the component picker shows a list of components based on the global configuration, even if the components are on a remote server.
Links OSLC link picker shows components based on the current global configuration

When you create a link, if a global configuration is selected, the link picker shows a list of components based on the global configuration, even if the components are on a remote server.
Paste as Link option works across servers in different domains

In previous releases, you could use the Paste as Link option between components on different servers if the servers were hosted by the same domain server. Now, you can use the Paste as Link option between servers in different domains.
Performance Clear long-running queries from the RM server

The Requirements Management (RM) server now has a query monitor, which cancels long-running SPARQL queries that exceed their time-out threshold and affect the responsiveness of the server.
Usability enhancements Heading styles have changed

The styles applied to text headings have changed. The new styles distinguish the different heading levels and more closely match the styles that browsers use. The new styles are also applied to existing documents.

Image of new heading styles:

Image of previous heading styles:
Back to top

Rational Quality Manager

TRS feeds Validate TRS feeds against artifacts in the repository

You can now validate Rational Quality Manager TRS feeds against artifacts in the repository.

Validate TRS feeds if Jazz Reporting Service reports don’t show the artifacts that you expect, show artifacts more than once, or show a different number of artifacts than application views.

To validate artifact TRS feeds:
  1. Open the validation service: https://host:port/qm/TRSValidator
  2. To perform a full comparison between the TRS feed and artifacts in the repository, select compare and runCompare. When the comparison starts, you can check the progress of the comparison or stop it. When the comparison ends, an Items match exactly or Discrepancies were found message is shown. For details, review the logs.
  3. To see the log of all validations that ran on the system, or any validation that it is still in progress, select trsLogs.
Note: To avoid out-of-memory errors, do not validate repositories with more than 7 million of these combined items: test plans, test cases, test scripts, test script steps, test execution records, test execution results, test execution result steps, test suites, test suite execution records, test suite execution results. If you must validate a system with more than 7 million items, increase the Java heap limit.
Usability enhancements Copy the OSLC URL of a test artifact

In OSLC artifact editors, when you click the Copy link for this page icon at the top of the page, you can now copy the link to a test artifact as an OSLC URL. You can copy the link as an OSLC versioned URL or as an OSLC concept URL.

This feature is useful for identifying the OSLC URL of a test artifact, because the browser URL contains the artifact ID and not the resource ID that is used for OSLC purposes. For example, you might need the OSLC URL to specify the test artifact when you debug with a HTTP client or use the command-line tool.

Image of the option to copy the link as an OSLC URL:
Back to top

Rhapsody Model Manager

Remote requirements Optimization to refresh load on the requirements server

Several enhancements were made to the handling of remote requirements in Rational Rhapsody models to improve the user experience and reduce the load on the requirements server. In addition to performance improvements, these are the most significant changes:

  • Remote requirements from Rational DOORS Next Generation are loaded in the background as much as possible to prevent disruptions when you work with Rational Rhapsody models.

  • Remote requirements in Rational Rhapsody models are no longer refreshed at regular intervals. Instead, the remote requirements are checked at a regular interval for changes and, if changes are detected, you see an overlay on the Refresh button on the Rhapsody Model Manager toolbar. Actual refreshes of requirement information only occur when you click Refresh or select Refresh on a context menu in the model browser. The interval for checking for changes is controlled by the RemoteArtifactRefreshInterval property, whose default value is 15 minutes. The property value must be set to at least 5 minutes.
Back to top

Rational Engineering Lifecycle Manager

CE Connector for IoT The base URL is set up automatically

You no longer have to update the teamserver.properties file to add the base URL for the IoT Platform. This URL is now configured when you run the Rational Engineering Lifecycle Manager setup.
Server rename Improvements for views and impact analysis

After a server rename, Rational Engineering Lifecycle Manager now supports the following scenarios:
  • In views, you can now select and save the data source, apply project area scope to a view or to containers in a view, and apply enumeration conditions to artifacts in a container.
  • When you do impact analysis, you can browse and create impact analysis filters, profiles, and diagrams.
Usability improvements Improved artifact selection, search, and icons

In views, you can now press Shift+Click to select multiple containers or artifacts. This improvement makes it easier to work with complex views.

When you build a traceability view, you can now search for a specific link type, and you can indicate how many link levels to show in the Link Types window. In large projects with a high number of artifacts and link types, this capability helps you find the correct link type easily.

Image of the link types filter in the "Show links to" wizard:

When you search for an artifact from the Queries menu in RELM, you get a list of results, and can start the impact analysis from that list. The Start Analysis buttons are now closer to the items and easier to find.

Image of the Start Analysis button in the search results list:

All the IoT Platform artifacts in the IoT Connector, such as schema, rule, space, and event type, are labelled with standard icons to make them easier to work with. New icons were added for the physical and logical interface of a device, generic objects, object type, event type, and JSON schema.

Image of IoT Platform artifact icons:
Back to top

Jazz Reporting Service

Data Collection Component Data warehouse trend reports now show only the final data for each day

In the past, trend reports such as burndown reports and Cumulative Value Flow diagrams showed multiple data points for the same day.

Now, the report shows only the last data point. This way, if an ETL job fails so there's only partial data and the administrator has to rerun the job, the subsequent run ensures that the report has the correct cumulative data for the day.
Lifecycle Query Engine Administrators can now easily access the logs

You can now download the Lifecycle Query Engine logs from the Advanced Properties administration page at https:<host_name>:<port>/lqe/web/admin/advanced. The settings in the install_dir/server/conf/lqe/log4j.properties file determine which logs are available.
Validate the index against TRS feeds

If you don’t find the right artifacts in your reports, you can use the new LQE validation, which compares the current TRS feed with the index. The validation process finds missing or extra artifacts but doesn't look at the content of the artifacts. The time required for validation depends on the size of the index.

To start validation, go to the Edit Data Source page. You can find the list of missing and extra artifacts in the lqe.log file after the validation has finished. However, if you see a discrepancy in the content of an artifact in a report, consider reindexing.

Note: This version of LQE introduces a new partition that is used for validation and shortens reindexing. When you first start LQE, a migration task creates the new partition. This process might take some time.

Image of the Validate button on the Edit Data Source page:
Report Builder Group conditions to exclude data from a report

When you define the conditions for a report, you now have more flexibility to define exact conditions of what to exclude. You can now negate a grouped condition by using the AND NOT or OR NOT options. For example, you can specify that all items must match one group of conditions but not another group of conditions.

The AND NOT operation is the negation of the AND group. That is, if a group has three conditions named A, B and C, the AND NOT operation is "NOT (A AND B AND C)." The name of the AND NOT operation is "Not all match."

Similarly, the OR NOT operation is the negation of the OR group. That is, if a group has three conditions named A, B and C, the OR NOT operation is "NOT (A OR B OR C)." The name of the OR NOT operation is "None of them match."

In addition, the Conditions section in the My Choices pane at the right now shows the logical operators and the group structures of the conditions.

Image of the grouped conditions:
Names at both ends of an RM relationship can now be the same

Report Builder now allows the names at both ends of a Requirements Management (RM) relationship to be the same. When this situation occurs, only one end is shown in the relationship picker. The generated query checks both ends of the relationship for a matching name.
Back to top

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