Jazz Foundation 5.0.2 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:

• Change and Configuration Management 5.0.2
• Quality Management 5.0.2
• Requirements Management 5.0.2

New in previous versions of Jazz Foundation

For details about new features and functionality in previous releases, see these pages:

• Jazz Foundation New & Noteworthy 5.0.1
• Jazz Foundation New & Noteworthy 5.0

New in Jazz Foundation 5.0.2

• IBM Support Assistant Data Collector
  • What does IBM Support Assistant Data Collector collect?
  • What has changed between ISALite and ISADC?
• Refactor LPA to support CLM SSO by integrating with JTS
• Enable multiple sample scenarios and incorporate RELM into LPA
• Process Sharing improvements
• Jazz Foundation Services
• Initial user scenario capabilities

IBM Support Assistant Data Collector

The IBM Support Assistant Data Collector (ISADC) is the new data collection utility provided with CLM 5.0.2. It replaces its predecessor, IBM Support Assistant Lite (ISALite), providing the same level of collection with several enhancements and better environment collection abilities. ISADC is console-only and runs with straight-forward steps that are easy to follow.

What does IBM Support Assistant Data Collector collect?

ISADC collects various information about the system the product is installed on. It can collect environment information such as system specifications, resource usage, process information, network information, and software installations. It also collects product-specific information such as product configuration, logging configuration, and the actual log files for the product. All the information gathered can provide an overview of the system at a specific time, and can be used for quicker, more reliable problem determination.

What has changed between ISALite and ISADC?

ISADC has eliminated the need for a graphical user interface and instead provides a simple, improved console-mode user interface. The data collected for ISADC has the same structure and much of the same information that ISAlite's collection did, however ISADC features improved inventory collection that better captures the environment of the system by using better hardware discovery and improved installation tag analysis. The process for transferring the collection remains roughly the same as does the ability to filter the collection to filter more or less data as appropriate.

Refactor LPA to support CLM SSO by integrating with JTS

The Lifecycle Project Administration (LPA) application has been incorporated into the Jazz Team Server. It is no longer delivered as a separate WAR application.

Enable multiple sample scenarios and incorporate RELM into LPA

You can now use the Lifecycle Project Administration application to create lifecycle projects that include Rational Engineering Lifecycle Manager (RELM) project areas. The following predefined lifecycle project templates have been added:

• Product Engineer, Developer: This template sets up associated project areas for change and configuration management and product line engineering.
• Architect, Developer, Product Engineer: This template sets up associated project areas for design management, change and configuration management, and product line engineering.
• Architect, Product Engineer: This template sets up associated project areas for design management and product line engineering.
• Product Engineer: This template sets up a project area for product line engineering.

Process Sharing improvements

As you create a project area, you can now specify that the project area will consume the process of another project area that shares its process. In previous releases, you had to create a project first, then modify it to consume the process of another project area.

Jazz Foundation Services

Specifying the default indexer in indexing rules

Until 5.0.1, all rdf properties of an rdf document were indexed by default. Applications could specify for some properties that they should not be indexed. With 5.0.2, applications can now specify that no rdf properties should be indexed, except for some specified properties. This is achieved by specifying the default property in the indexing rule document. See the indexing rule specification for more details.

Exclude system properties from the index

System properties can take a large amount of space in the index. If they are not needed, applications can now exclude them from the index by using the following API: com.ibm.team.jfs.sdk.storage.IStorageArea.setSystemIndexer(Indexer) A query using system properties on such an index will find no results, unless the following API is used: com.ibm.team.jfs.sdk.query.ISparqlQuery.setUseDynamicSystemProperties(boolean)

Exclude selected system triples from the index

When only a subset of system triples need to be removed, indexing rules can be used to specify whether a system triple should be indexed. See the indexing rule specification for more details.

Extended compactTdb command

The repotools -compactTdb command can now compact more than one triple store. By default, it will compact all triple stores that belong to the server. It can also compact all triple stores contained in a given directory.

Initial user scenario capabilities

User scenario support capabilities are being introduced in this release. User actions will be identified by a scenario type and unique identifier that is surfaced in facilities through the platform. As a user action may consist of multiple threads of execution on a server and even across server nodes, these scenarios allow the gathering of information across the entire topology of a CLM deployment as it is related to user activities.

The facilities affected in this sprint are listed below.

Active Services

Thread Names

As part of the thread name.

Logging (Optional)

Two new (optional) entries in the log4j.properties:

 log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} [%t] %5p [%X{scenarioName}] [%X{scenarioInstanceID}] %-50.50c  - %m%n

Browser Client

Browser activities ("Scenarios") pass scenario information to the server using a new header ex:

x-com-ibm-team-scenario: id=cec7d0ef-72d0-4869-a0b2-43a356194a97;name=Load Plan

"id" is the scenario identifier and name is the scenario type.

Counters

• Counter pages
• Internal Admin Counter page
• Repo Debug Service

All Counter pages now have scenario information added. The wildcard "*" entry represents the old counter values (total counter values). You can include scenario counters by going to Server Advanced Properties from the admininstration page and setting these properties to true:

	Scenario Counters = true
	Scenario State Cache Counters = true
	Scenario License Tracking = true