(r1) GC-Broken-Link-Must-Gather < Deployment

Engineering Lifecycle Management Wiki - Deployment
Community information and contribution guidelines
~~EditAttach~~Printable
TWiki > Deployment Web > DeploymentPlanningAndDesign > LifecycleQueryEngineBestPractices > GC-Broken-Link-Must-Gather
Revision 1 - 2020-05-06 - 15:54:42 - NatarajanThirumeni
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Must Gather to troubleshoot Broken Links in GC enabled Project Areas <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.TWikiUser, Main.TWikiUser <br>
Build basis: ELM (formally known CLM - Collaborative Life-cycle Management) v6.0.6.1 / 6.0.6
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

---++ Introduction

Must gather if a user report a broken links when working on Global Configuration enabled project areas. This document do not explain where links are stored or in details about LDX. This is high level document to explain as to what kind of logs to be collected to investigate broken link issues in GC context. 

Troubleshooting broken links in GC enabled project area is complex and this document is to assist list of logs which needs to gathered out broken configuration.  The broken links could be classified in several ways, lets us consider following two use cases:

1.   Creating a link from QM Test Case to DNG requirement is expected to establish a link between TC and  requirement. In some cases, you'd see a link of TC on DNG requirement but not in Test Case or vice-versa.

2.   Populating artifacts from a GC baseline into a GC stream. In GC baseline link between Test case and DNG requirement exist as expected, however GC stream created out that baseline contain a broken links. 

Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph Introductory paragraph

---++ Log Collections

1.   Output of Contribution tree, copy outcome into a text file called GC-ID.txt

escaped: ! https://<server>:<port>/rm/gcsdk/tree?configurationUri=https://<server>/gc/configuration/<GC-ID>

2.   GC ID (e.g https://<server>:<port>/gc/configuration/4)

3. Local configuration URI of QM. This can be obtained from the web UI of where GC Test case exist. Click on Current Configuration, hover over Local Configuration name and copy link (e.g https://<server>:<port>/qm/oslc_config/resources/com.ibm.team.vvc.Configuration/<_1QceYBSuEequ-JEash4SxA>)

4. GC verioned Test Case URL. From test case, click on "Copy link for this page" and then select Copy OSLC URL. This should contain full versioned test case (e.g https://<server>:<port>/qm/oslc_qm/contexts/<_0VIssRSuEequ-JEash4SxA>/resources/com.ibm.rqm.planning.VersionedTestCase/<_Ggks8xSwEequ-JEash4SxA>/<_4dfh2xSxEequ-JEash4SxA>)

<_Ggks8xSwEequ-JEash4SxA> : VersionedTestCase Item ID

<_4dfh2xSxEequ-JEash4SxA> : VersionedTestCase State ID

5. Local configuration URI of RM. This can be obtained from the web UI of where GC Requirement exist (e.g https://<server>:<port>rm/cm/stream/<_xQvHkBSuEeqCl9XOGtTvzQ>)

6. DNG Requirement link that was add to Test Case. From requirement use, pick up Share Link option and then copy a link (e.g https://<server>:<port>/rm/resources/<_-5ElgxSuEeqCl9XOGtTvzQ> )

7. QM Test Case history PDF. From Test Case menu, go to History, click on Export History to save TC history.

8. TRS Feed. Go to trsConsole (https://<server>:<port>/qm/trsConsole) and click on download, this should download a ZIP of the TRS2 feed (RQM Resources (TRS 2.0)) including all base page(s) and change log page(s).

9. LDX graph query output for Test Case. To run this query, go to https://<server>:<port>/ldx/web/query#sparql. Select Configuration scope: to where TC is exist (eg gcStream1)

<verbatim>
prefix dcterms: <http://purl.org/dc/terms/>
prefix oslc_config: <http://open-services.net/ns/config#>
prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>

SELECT ?selected WHERE 

{ <https://<server>:<port>/qm/oslc_config/resources/com.ibm.team.vvc.Configuration/<uuid-lc-qm>/selections>; <http://open-services.net/ns/config#selects>; ?selected FILTER regex(str(?selected), "<uuid-gc-qm-itemID>")

} 
</verbatim>

note:

<uuid-lc-qm> : this is UUID of the local config, see step 3)

<uuid-gc-qm-itemID> : VersionedTestCase Item ID, see step 4)

10. DNG resource query against LDX, this query should be scoped to GC where the link exists (eg gcStream1) in LDX. It’s the query that DNG uses to fetch the links from LDX

<verbatim>
prefix dcterms: <http://purl.org/dc/terms/>
prefix oslc_config: <http://open-services.net/ns/config#>
prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
prefix owl: <http://www.w3.org/2002/07/owl#>
SELECT ?sURL ?linkType ?tURL ?indLinkType 
WHERE {
	{
		VALUES ?linkType {
			<http://jazz.net/xmlns/prod/jazz/calm/1.0/implementsRequirementCollection>
			<http://open-services.net/ns/qm#validatesRequirementCollection>
			<http://open-services.net/ns/qm#validatesRequirement>
			<http://open-services.net/ns/cm#implementsRequirement>
			<http://open-services.net/ns/cm#affectsRequirement>
			<http://open-services.net/ns/cm#tracksRequirement>
		}
		VALUES ?tURL {
			<RM resource URI>
		}
		{
			?sURL ?linkType ?tURL.
			BIND( ?linkType as ?indLinkType ) .
		}
		UNION
		{
			?indLinkType owl:sameAs ?linkType .
			?sURL ?indLinkType ?tURL .
		}
	}
	OPTIONAL
	{
		?reification rdf:subject ?sURL .
		?reification rdf:predicate ?indLinkType .
		?reification rdf:object ?tURL .
		?reification ?property ?release .
		?release oslc_config:configuration ?config
	}
}
ORDER BY ?tURL ?linkType ?sURL LIMIT 1000
</verbatim>

11. Verification of the selections page if the state ID is same as the "_uX2E3GjiEeqN_eb5TIbnUg". The selection page 

https://<server>:<port>/qm/oslc_config/resources/com.ibm.team.vvc.Configuration/<uuid-lc-qm>/selections

---+++ Heading 2 (use sentence-style capitalization)

Sub-Section text Sub-Section text  Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

---+++ Heading 2 (use sentence-style capitalization)

Sub-Section text Sub-Section text  Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

---++ Heading 1

---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[DeploymentWebHome][Deployment web home]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

---+++++!! Additional contributors: Main.TWikiUser, Main.TWikiUser

<sticky></div></sticky>
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.