Download 6.0.6 Release
June 15, 2018

Jazz Foundation

The foundation of the Collaborative Lifecycle Management solution

Jazz Foundation 5.0

Product Release / Trial | June 2, 2014
This is not the most recent version. We recommend Jazz Foundation 6.0.6 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Jazz Foundation 5.0 New & Noteworthy

Jazz Foundation 5.0 New & Noteworthy

Jazz Foundation is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about the CLM applications, see these pages:

New in previous versions of Jazz Foundation

For details about new features and functionality in the previous release, see:

New in Jazz Foundation 5.0

  • Web client
  • Jazz Foundation Services
  • Reporting
  • CLM Server Monitoring
  • Full-text indexing

    Web client

    The Project area and Team area Details pane was removed from dashboards

    The Details pane was removed from the right side of project and team dashboards so that you have complete control over the dashboard content. You can add some or all of the information that this pane displayed by using dashboard widgets.

    Support for LESS in style sheets

    When you author style sheets, you can now use LESS (lesscss.org) instead of CSS by using .less as a file extension instead of .css. When you refer to a style sheet (in CSS bindings, import operations, and other situations), continue to use the .css extension.

    Jazz Foundation Services

    Low disk space warning

    JFS index diagnostics now warns when the drive that contains the JFS indexes is low on disk space.

    JFS Low Disk Space Warning

    To configure the warning threshold, on the Administration page of the server, go to the Advanced Properties page and change the Low disk space warning threshold value.

    Potentially corrupted index diagnostics

    JFS index diagnostics now detects when a server does not shut down properly and reports that the indexes might be corrupted. This diagnostic is disabled by default. To enable it, on the Administration page of the server, go to the Advanced Properties page and change the Server shutdown tracking value.

    JFS Potentially Corrupted Indices Warning

    New Japanese and Chinese language analyzer

    The Japanese and Chinese analyzer that text-index JFS resources has limitations. You can use a CJK analyzer instead.

    1. On the Administration page of the server, go to the Advanced Properties page and change the value to true for Activate CJK analyzer.
    2. Shut down the server.
    3. Reindex the resources by using repotools -reindex all -scope=search.
    4. Restart the server.

    Support for VVC unreferenced resources garbage collection

    A task can be configured to run periodically and garbage collect resources that are unreferenced by any VVC configuration in JFS indices. To enable this task and configure the frequency it runs, go to the Advanced Properties of the Server Administration and change the values for:

    com.ibm.team.jfs.indexing.service.internal.CleanUpUnusedIndexesVersionsTask

    Support for index compaction

    A task can be configured to run periodically and compact the JFS indices. To enable this task and configure the frequency it runs, go to the Advanced Properties of the Server Administration and change the values for:

    com.ibm.team.jfs.indexing.service.internal.CompactIndexesTask

    Enhancements of the Java APIs for JFS services

    The Java APIs for JFS services have been enhanced with the following:

    • com.ibm.team.jfs.sdk.storage.IChangeService allows to accumulate resource changes and make them available later in one commit action.
    • com.ibm.team.jfs.sdk.storage.IStorageService.bulkUpdate(List, List) to modify a set of resources efficiently.
    • com.ibm.team.jfs.sdk.storage.IStorageService.bulkFetch(List, List) to fetch a set of resources efficiently.
    • com.ibm.team.repository.servlet.BridgeRestService allows implementors of IRestService to get inbound authentification for free, thus allowing to use 0.6 services.

    Online index backup progress

    The online backup command now reports progress.

    repotools-ccm -backupJFSIndexes toFile=indices_backup.zip

    Counters for fulltext indexing and search

    Counters have been added to measure the performance of fulltext indexing and search queries.

    Support for VVC Configuration Cache Service

    VVC Cache Pre-Population Control

    The number of VVC Configurations that are read into the cache at startup time can be controlled via a system property. To configure this, set the following property:

    com.ibm.team.repository.service.internal.vvc.noOfConfigsToCache
    The value must an integer between 0 and 2048.

    VVC Cache String Interning Enablement

    String interning can now be enabled in the VVC Configuration Cache. This greatly reduces the memory footprint of the cache as identical strings are now only referenced by a single memory location. To enable String Interning, set this system property to true:

    com.ibm.team.repository.service.internal.vvc.enableInternStrings
    The default value is 'false'.

    VVC Cache Method Counters

    Counters have been added to the VVC Configuration Cache. Enabling these counters can track how often cache requests are made, which can then be viewed via the Counters service at:

    %application URL%/service/com.ibm.team.repository.service.internal.counters.ICounterContentService/ 
    To enable counters, set the following system property to true:
    com.ibm.team.repository.service.internal.vvc.enableCounters
    The default value is 'false'.

    VVC Cache Unreferenced Version Updater Task Transaction Size Control

    The Unreferenced Version Updater Task is a background task which periodically scans VVC Cache information looking for versions no longer referenced by any configurations. A new advanced property has been added to allow administrators to configure the transacation size for this task, so that a limit can be placed to avoid impacting server throughput. To configure this property, go to the Advanced Properties page of the administrative interface and configure:

    com.ibm.team.repository.service.internal.vvc.UnReferencedVersionsUpdater
    The default value is 100.

    Reporting

    Creating and upgrading Oracle data warehouse without a database administrator

    Previously, creating or upgrading an Oracle data warehouse required a database user with administrator privileges. It is now possible to generate scripts to create or upgrade an Oracle data warehouse that can be run by a user who is not a database administrator. The scripts also automate some of the steps that were previously required to run the ETL jobs as a non-administrator user.

    Integration with the Jazz Reporting Service

    If the Jazz Reporting Service is installed, links to it are displayed in the reporting views.

    Example - Welcome to Reports page

    Example - Reports menu

    You can use the Jazz Reporting Service to create simple operational reports that show information across projects and tools.

    CLM Server Monitoring

    CLM Server Monitoring agent for Linux 64-bit and Windows 64-bit systems (technical preview feature)

    The CLM Server Monitoring agent provides reports and visualizations to identify key problem areas related to product user activity and resource bottlenecks. This is a technical preview feature, which is open to feedback for further improvement. For more information, see the Deployment wiki article on CLM Server Monitoring agent, which includes installation instructions and test scenarios.

    Full-text indexing

    Unique names for full-text index directories

    Before the 5.0 release, the default full-text index directory had a hard-coded subdirectory name, as shown in the following example: "JazzTeamServer\server\conf\ccm\indices\workitemindex\fulltext_index"

    However, a conflict occurred if multiple applications, for example CCM and QM, configured their full-text index directories to be the same folder. For details, see Work Item 285962. To avoid these conflicts, a unique identifier that is specific to each application is now used, as shown in the following example: "JazzTeamServer\server\conf\ccm\indices\workitemindex\_rgHxIpTTEeOSIqepiraiyw"