| Description | |
|---|---|
| EWM ClearCase and ClearQuest Connectors |
ClearCase Synchronizer and ClearQuest Synchronizer are not shipped with 7.0.2
IBM Engineering Lifecycle Management now only supports 64-bit clients in the 7.0.2 release. As ClearCase Synchronizer and ClearQuest Synchronizer are 32-bit applications, they are not shipped with the 7.0.2 release. You can continue to use the 7.0.1 release of ClearCase and ClearQuest Synchronizers with the ELM 7.0.2 server. |
| Jazz source control |
Source control TRS feed for streams, snapshots, baselines, and files
Source control streams, snapshots, and baselines can now be included in a Tracked Resource Set (TRS) feed with their files so that they can be reported in Report Builder through the Lifecycle Query Engine (LQE). The name of the new TRS feed is EWM SCM Configuration Resources (TRS 2.0). The data that is published through this feed is configuration-based and compatible with other Engineering Lifecycle Management (ELM) products when they are in opt-in mode. Publishing streams and other configurations Source control project areas can have many streams, snapshots, and baselines. Hence, not all configurations are published by default. The user selects the configurations that must be published. After a stream is published, any changes to the components or the files in the stream result in changes sent through the TRS feed. Publishing a stream also publishes any snapshots that are owned by the stream. The following screen capture of the CCM admin web UI shows how to publish a stream. Image of the Publish Stream dialog:  The UI also has a table that shows the streams that are published. Image of the Published Streams table:  Publish permissions The abilities to publish streams and other configurations and validate published items are controlled by permissions. If a user must publish a configuration or validate a published item, they must be assigned a role that has the required permission. The permissions are assigned in the project area editor at the permissions path: Source Control/Tracked Resource Set/Publish & Unpublished. By default, no role has the permissions to publish SCM resources. Image of the Publish & Unpublish option that is displayed on the Permissions page:  Reports in Report Builder After a stream is published, the data for that stream is included in the new TRS feed. The TRS feed is available in LQE through the Lifecycle Query Engine scoped by a configuration data source. You can use the artifact type selection widget to generate reports for files or include files in the reports with related artifacts, such as requirements or test resources. An important aspect of an SCM file is the path of the file in the component. Due to how OSLC versioned resources work, the path of a file that is needed must be modeled separately. You can include the path of the file in the report by selecting the Enable multiple paths or add other source artifacts option. Then, you can merge the file to path relationship with any other relationship you are querying on. The following image shows a query for all files that implement a requirement in a configuration, merged with the path of the file. Image of the artifact relationship specification:  You can also configure which fields appear in the query output. The following image shows that the file component, path, name, and version ID are included in a report with the requirement ID and title. Image displaying the attributes to be included in the report:  You can then select a Global Configuration (GC) that contains the published SCM stream. Additionally, you can select a Requirements stream that contains requirements that are linked to one or more files in the SCM stream. Image of the report:  |