What's new in Jazz Foundation 7.1

Edit online

Learn more about what's new and changed in the Jazz Foundation.

Enhancements to the REST APIs
The following actions are available in the newly created or updated REST APIs:
  • Retrieve user account information. This information includes the date of creation, date it was last modified, the jazz repository permissions that are associated with the account, and the archived flag.
  • Retrieve information about the history of a user account, which includes information about the additions, changes, and deletions that were done to the user account.
  • Retrieve all the permissions within a project area or team area. You can also get all enabled permission for a role within a project area or a team area by passing that role ID as a query parameter.
  • Include the history of process specification changes, such as changes to role-based permissions, workflows, and e-signatures in the project area history.
For more information, see the following topics:
API Access Logging
Engineering Lifecycle Management REST API access logging can be enabled that provides basic auditing of information that is accessed through REST APIs. The JAZZ_ADMIN can enable logging and specify the location of the log file in the Jazz Team Server Advanced Properties page under com.ibm.team.repository.service.audit.acces.AccessAuditService.

This feature is NOT intended for security logging or full create, retrieve, update, and delete logging. It logs user activity from REST clients. It does NOT log APIs or integrations from Java APIs or potentially other clients. This feature is only supported on Jazz Team Server and IBM® DOORS® Next.

Important: API Access Logging significantly affects the performance. You should test the performance characteristics of API access logging for your topology and user load before deploying in a production environment. Regularly monitor performance to check for unacceptable degradation during production use.

The access log includes Sensitive Personal information such as user UUIDs and request parameters.

The following information is captured in the log:
  • UUIDs for:
    • Request identifier
    • Authenticated user
    • Project area
    • Artifact
    • Local configuration context
    • Global configuration context
  • Timestamp
  • Trace identifier
  • HTTP request action (method)
  • HTTP status
  • REST header name/value
  • Request URL
  • Request parameters
  • Attributes
  • Request body (if desired) - text content only

IBM DOORS Next provides additional information in the access log.

  • When downloading a reqif package, artefact URIs and Artefact IDs of all SPEC-OBJECTs and SPECIFICATIONS contained in the contained in the package are added to the access log.
  • View executions requested by the web UI will result in artifact URI and artifact ID of each artifact that is in the response being access logged.
  • View executions executed during CSV/Excel export will result in artifact URI and artifact ID of each artifact that is in the response being access logged.
Option to disable saving all historical states of user definitions
Added the Disable Save to All Historical States option in the administrative UI. When this option is selected, the Save to All Historical States option is disabled to prevent the historical user states being overwritten when they save a change. This option allows organizations to preserve past historical states and use them in audit reports that use the REST APIs.
Installer property name change that configures embedded or external Liberty installation
The web-installer contains the silent-install-server.xml response file that allows users to install Engineering Lifecycle Management with the embedded liberty server or an external liberty server. This customization uses the user.com.ibm.team.install.jfs.appserver.liberty.disable property in 703. In 7.1, this property is renamed to user.com.ibm.team.install.jfs.appserver.liberty.embedded.disable. For more information, see Installing by using command-line commands.

What's new in other Engineering Lifecycle Management applications