Jazz Library Setup Rational Engineering Lifecycle Manager, Lifecycle Query Engine, Jazz Team Server and Tracked Resource Set Provider for Bugzilla
Author name

clm,elm,sse

Mon, 01 Jul 2013
5 min read
0

Setup Rational Engineering Lifecycle Manager, Lifecycle Query Engine, Jazz Team Server and Tracked Resource Set Provider for Bugzilla

Hirotaka Matsumoto, IBM
Last updated: June 10, 2013
Build Basis: Rational Engineering Lifecycle Manager 1.0.0.1, 4.0.3

This page describes a usage or software configuration that may not be supported by IBM.

Tracked Resource Set (TRS) is a protocol designed for servers to expose a set of resources in a way that allows clients to discover all additions, removals and modifications to the resource. Lifecycle Query Engine (LQE) utilizes this protocol to index lifecycle data and Rational Engineering Lifecycle Manager (RELM) provides the functions to visualize, analyze and organize such resources. Additionally Open Services Lifecycle Collaboration (OSLC) can be used to remotely view the lifecycle resource details and or navigate to them in a consistent regardless of where they are hosted. A TRS resource doesn’t have to be an OSLC provider in order to be indexed and searchable.

Eclipse Lyo provides the TRS Software Development Kit (SDK) which makes it easier to implement TRS provider. The TRS Workshop, which uses this SDK, provides the reference implementation of TRS Provider for Bugzilla. This workshop provides a foundation in the skills required for developing Tracked Resource Set Provider implementations, while this article serves as a supplement to the workshop to help explain:

  • How to configure RELM, LQE and Jazz Team Server to connect to TRS Provider for Bugzilla
  • Sample SPARQL query to search Bugzilla bugs
  • Sample RELM View configuration to visualize Bugzilla bugs

Prerequisites

  • Bugzilla v4.0.10 or later server and its administrator id and the password
  • Completed the TRS Workshop on Eclipse.org
  • TRS Adapter for Bugzilla
  • RELM v1.0.0.1 or v4.0.3 server and its administrator id and the password.

The instruction to setup TRS Workshop is here, which has all necessary instruction to prepare TRS Adapter for Bugzilla. The instructions for installation RELM v 1.0.0.1 is here and for RELM v4.0.3 is here. To learn more about RELM, please read this technical article on Jazz.net. The contents of this articles are :

  1. Create a trusted OSLC consumer key for LQE
  2. Register TRS4JBugzilla adapter to LQE
  3. Register TRS4JBugzilla adapter to RELM for OSLC preview
  4. Create a RELM (v1.0.0.1 or v4.0.3 ) Query for Bugzilla
  5. Create a RELM v1.0.0.1 View for Bugzilla
  6. Create a RELM v4.0.3 View for Bugzilla

How to set up and configure RELM, LQE and Jazz Team Server

Create a trusted OSLC consumer key for LQE

  1. In order to make sura that TRS Adapter for Bugzilla is working, open the root service page ( http://<TRS adapter host name>:8085/OSLC4JBugzilla/rootservices ) by your browser.
  2. Open RELM JTS admin page ( https://<RELM host name>:<port number>/jts/admin )
  3. Click Manage Server in Manage Server pane, and then navigate to Friends (Outbound) in the left pane.
  4. Click Add… link at the right of the Friends List section title
  5. Fill the fields
    1. Name: TRS4JBugzilla
    2. Root Services URI: http://<TRS adapter host name>:8085/OSLC4JBugzilla/rootservices
    3. OAuth Secret: xyz
    4. Trusted: Checked
  6. Click Create Friend button
  7. Click Next
  8. Click Grant access for the provisional key link
  9. Fill the form using [[Bugzilla admin id (default root@localhost.here)]] and [[Bugzilla admin password (passw0rd)]], and then click Continue

    NOTE: You may not see the login message if you have already logged in to the TRS4JBugzilla adapter as the administrator.
  10. Type LQE in Name field, check Trusted checkbox, and then click Allow button
  11. Click Finish
  12. Now you have TRS4JBugzilla friend definition
  13. Copy the OAuth Consumer Key for the next step.

Register TRS4JBugzilla adapter to LQE

  1. Open LQE Data Sources page ( https://<RELM host name>:<port number>/lqe/web/admin/data-sources)
  2. Click Add Data Source button at the right top
  3. Fill the dialog as follow:
    1. Data Source: Check Root Services document URL
    2. Put http://<TRS adapter host name>:8085/OSLC4JBugzilla/rootservices into the edit box
    3. Select http://<TRS adapter host name>:8085/OSLC4JBugzilla/services/trs radio button
    4. Label: TRS4JBugzilla
  4. Click Next, and then fill the form:
    1. OAuth Consumer Key: [one copied in Friends screen]
    2. OAuth Consumer Secret: xyz (in this document)
  5. Click Finish. Now the TRS4JBugzilla TRS is added to LQE

Register TRS4JBugzilla adapter to RELM for OSLC preview

  1. Open RELM admin page ( https://<RELM host name>:<port number>/relm/admin )
  2. Click Friends (Outbound) in the left pane
  3. Click Add… link at the right of the Friends List section title
  4. Fill the fields:
    1. Name: TRS4JBugzilla
    2. Root Services URI: http://<TRS adapter host name>:8085/OSLC4JBugzilla/rootservices
    3. OAuth Secret: xyz
    4. Trusted: Checked
  5. Click Create Friend, click Next
  6. Click Grant access for the provisional key link
  7. Fill the form using [[Bugzilla admin id (default root@localhost.here)]] and [[Bugzilla admin password (passw0rd)]], and then click Continue. (NOTE: You may not see the login message if you have already logged in to the TRS4JBugzilla adapter as the administrator. )
  8. Type RELM in Name field, check Trusted checkbox, and then click Allow button
  9. Click Finish

Note: If you will change the value of the property, adapter_host, in org.eclipse.lyo.oslc4j.bugzilla.trs/src/main/resources/bugz.properties, you need to remove the consumer keys.

  1. Open RELM JTS admin page ( https://<RELM host name>:<port number>/jts/admin )
  2. Click Manage Server in Manage Server pane, and then navigate to Friends (Outbound) in the left pane.
  3. Click a red X icon in Actions field for "TRS4JBugzilla" to remove it.
  4. Open RELM admin page ( https://<RELM host name>:<port number>/relm/admin )
  5. Click Friends (Outbound) in the left pane
  6. Click a red X icon in Actions field for "TRS4JBugzilla" to remove it.
  7. Remove org.eclipse.lyo.docs/org.eclipse.lyo.oslc4j.bugzilla.trs/bugzillaOAuthStore.xml file.

Try RELM Query and View

Before try RELM, please add several Bugzilla bugs. By default, Bugzilla requires Product, Component, Version and Summary fields to be filled in. At this moment, these fields are enough. For example,

After the bug is created, please fill in "See Also" field in Bugzilla bug. For example,

In this field, you need to type "http://<Bugzilla host name>:<port number>/<Bugzilla context root>/show_bug.cgi?id=XXX" where XXX is a Bugzilla Bug ID, and "http://<Bugzilla host name>:<port number>/<Bugzilla context root>" is the value of the property, bugzilla_uri, in org.eclipse.lyo.oslc4j.bugzilla.trs/src/main/resources/bugz.properties. So for example, See Also will look like :

Query

  1. Open https://<RELM host name>:<port number>/relm/web and navigate to one of your RELM project area
  2. From RELM menu bar, select Queries > Create – Create Query
  3. Type BugzillaQuery to Name
  4. Select My Queries in Folder
  5. Replace the SPARQL with the following query. It is to find all Bugzilla Bugs with their identifier, title, contributor and last modified time.
    # Bugzilla resources :  sample SPARQL  PREFIX dcterms: <http://purl.org/dc/terms/>  PREFIX oslc_cm: <http://open-services.net/ns/cm#>  SELECT ?uri ?id ?title ?contributor ?modified  WHERE {     ?uri a oslc_cm:ChangeRequest;         dcterms:identifier ?id;         dcterms:title ?title;         dcterms:contributor ?contributor;         dcterms:modified ?modified.         FILTER regex (str(?uri), "Bugzilla")  }  ORDER BY ASC (?id)  # end of the query
  6. Click Create button.
  7. Click Run button
  8. If you will see User Authentication window, click all Authorize links and type the appropriate user id and its password.
  9. For TRS4JBugzilla, if you will see the following dialog, type Bugzilla’s user id and its password. ( for example, user : bugs@localhost.here password : bugs4me )
  10. Or if you will see the following dialog, click Allow button.
  11. After the authorization is completed, close the following windows
  12. If you don’t see any result, click on Refresh button in the query result page.
  13. Confirm that the bugs in your Bugzilla bugs are listed:
  14. Try to move the cursor on "uri" column. If you will see the following small window, click "Log in".
  15. You will see "Connect to Bugzilla" dialog, type Bugzilla’s user id and its password. Or if you will see "Authorize Application" dialog, click Allow button. Try to move the cursor on "uri" again.
  16. OSLC preview windows brings up.

View (for RELM 1.0.0.1)

  1. Open https://<RELM host name>:<port number>/relm/web and navigate to one of your RELM project area
  2. From RELM menu bar, select Views > Create – Create View
  3. Type BugzillaView to View name.
  4. Select Simple Sample in View template
  5. Select My Views in Folder
  6. Click Finish
  7. Click a pencil icon in Actions column of "BugzillaView" row to edit it
  8. Type "BugzilaView" in ID field.
  9. Click Query in the left pane.
  10. Replace the SPARQL in SPARQL Definition with the following query. This query is used to find out Bugzilla Bugs which are visualized in this view.
    PREFIX dcterms: <http://purl.org/dc/terms/>  PREFIX oslc_cm: <http://open-services.net/ns/cm#>  SELECT *  WHERE {    ?resource dcterms:identifier ?identifier ;              dcterms:title ?title ;              oslc_cm:status ?status .             FILTER regex (str(?resource ), "Bugzilla")  }  ORDER BY ${order}(?title)  LIMIT 20
  11. Click Resource in the left pane.
  12. Remove rtc_cm:com.ibm.team.workitem.linktype.relatedworkitem.related in Link types for Status.
  13. Remove the following definitions from Hover Definition.
    1. Description
    2. Related tasks
    3. Follow-on tasks
  14. Add the following definition to Hover Definition
    1. Name: Related Bugs
    2. Layout: Vertical
    3. Query: Default Query
    4. Property Name : oslc_cm:relatedChangeRequest
  15. Change PrpertyName of "ID" in Hover Definition
    1. dcterms:identifier
  16. Hover Definition defines the content of the preview window, so Bugzilla Bug’s ID, its title, its status and "See Also" bugs will be displayed in the preview window.
  17. Remove the following actions from Actions
    1. Open Resource with Children
    2. Open Traceability View
    So Resource content looks like :
  18. Click Connection in the left pane
  19. Change Link Type to oslc_cm:relatedChangeRequest because Bugzilla’s "See Also" is mapped to this OSLC resource type.
  20. Click Component Info in the left pane
  21. Replace the current content with the following. This defines what will be displayed in the view. In this case, Bugzilla’s ID and its title are displayed.
    [{"name":"summary","value":"${title}"},   {"name":"uri","value":"${resource}"},   {"name":"fill","value":"{type:'linear',x1:0,y1:0,x2:0,y2:100,colors:[{offset:0,color:'white'},{offset:1,color:'#d7d7d7'}]}"},   {"name":"width","value":120},   {"name":"height","value":30},   {"name":"summary","value":"${title:/^(.{1,20}[ ])(.*)$/$1/}"},   {"name":"summary2","value":"${title:/^(.{1,20}[ ])(.{0,20})(.*)$/$2/}"},   {"name":"status","value":"${status}"},   {"name":"identifier","value":"${identifier}"},   {"name":"targetShapes","value":[       {"fill":"${fill}","height":"${height}","r":10,"stroke":"#d7d7d7","type":"rect","width":"${width}"},  	 {"dojoAttachPoint":"identifier","fill":"black","font":{"family":"normal","size":"8pt"},"text":"${identifier}","type":"text","x":2,"y":15},  	 {"dojoAttachPoint":"summaryShape","fill":"black","font":{"family":"normal","size":"8pt"},"text":"${summary}","type":"text","x":20,"y":15},  	 {"dojoAttachPoint":"summaryShape2","fill":"black","font":{"family":"normal","size":"8pt"},"text":"${summary2}","type":"text","x":5,"y":25}  	 ]}  ]
  22. Click Save and Close buttons
  23. Click BugzillaView in My Views’s list
  24. You will see some Bugzilla bugs are displayed with the connections (arrows). For example,
  25. Try to move the rectangles, which stand for Bugzilla’s bugs, to anywhere. For example,

    The "arrow" stands for Bugzilla’s "See Also" relation. So from this view, Bug "1 Improve the usability" has two "See Also" relations. ( to "2 Improve the login panel" and "3 Improve the installer usability" bugs )
  26. Try to move the cursor on the rectangle. If you will see the following "Authentication Required" dialog, type Bugzilla’s user id and its password.
  27. OSLC preview brings up
  28. Click the rectangle so that the down arrow icon brings up. Click it.
  29. Try to select "Open Artifact". You will see Bugzilla’s bug.

View (for RELM 4.0.3)

  1. Open https://<RELM host name>:<port number>/relm/web and navigate to one of your RELM project area
  2. From RELM menu bar, select Views > Create – Create View
  3. Type BugzillaView to View name.
  4. Select Simple Sample in View template
  5. Select My Views in Folder
  6. Click Finish
  7. Click a pencil icon in Actions column of "BugzillaView" row to edit it.
  8. Type "BugzillaView" to ID field in General section.
  9. Click a pencil icon in Actions column of "allcm" row in Queries section to edit it.
  10. Replace the SPARQL in SPARQL with the following query. This query is used to find out Bugzilla Bugs which are visualized in this view.
    PREFIX dcterms: <http://purl.org/dc/terms/>  PREFIX oslc_cm: <http://open-services.net/ns/cm#>  SELECT *  WHERE {    ?resource dcterms:identifier ?identifier ;              dcterms:title ?title ;              oslc_cm:status ?status .             FILTER regex (str(?resource ), "Bugzilla")  }  ORDER BY $order$(?title)  LIMIT 20
  11. You can try this query when Preview Query Result link is clicked.
  12. Click Cancel button on Query Result dialog, and click OK button.
  13. Click Edit UI Types… link in UI Types section.
  14. Click Duplicate… button in UI Type ID field
  15. Type resourceNodeBugzilla in Component Info ID field, and click OK button.
  16. Click Add… link at the right of Attributes row.
  17. Type identifier for Name field
  18. Type ${identifier} for Value field.
  19. Click OK button.
  20. Click Value column of title field, then type the following code.
    ${title:/^(.{1,20}[ ])(.*)$/$1/}
  21. Click Value column of summary filed, then type the following code
    ${title:/^(.{1,20}[ ])(.{0,20})(.*)$/$2/}
    so that you will see the following Values for title and summary fields.

  22. Remove two "image" rows in Shapes area by clicking X icon in Actions column.
  23. Click OK button if being asked to remove it.
  24. Click Add… link in at the right of Shapes row.
  25. Select Text in Shape Type list box.
  26. Click OK button.
  27. Click the newly created text row.
  28. Type the following code
    {"dojoAttachPoint":"identifier","fill":"black","font":{"family":"normal","size":"8pt"},"text":"${identifier}","type":"text","x":2,"y":15}

  29. Click OK button in UI Types dialog.
  30. Click a pencil icon in Actions column of "Default" row in Nodes section to edit it.
  31. Click Duplicate… button in Node field
  32. Type BugzillaNode in Name field.
  33. Select resourceNodeBugzilla in UI Type list box.
  34. Remove the following definitions from Hover Definition by clicking X icon in Actions column.
    1. Description
    2. Related tasks
    3. Follow-on tasks
  35. Click Add… link in at the right of Hover Definition row.
  36. Add the following definition to Hover Definition
    1. Label: Related Bugs
    2. Layout: Vertical
    3. Check Property Value
    4. Property Name : oslc_cm:relatedChangeRequest
  37. Click OK Button.
  38. Change PropertyName of "ID" in Hover Definition
    1. dcterms:identifier
  39. Hover Definition defines the content of the preview window, so Bugzilla Bug’s ID, its title, its status and "See Also" bugs will be displayed in the preview window

  40. Remove rtc_cm:com.ibm.team.workitem.linktype.relatedworkitem.related in Link types for Status Calculation..
  41. Remove the following actions from Actions
    1. Open Resource with Children
    2. Open Traceability View
    so they have nothing now.
  42. Click OK button in Nodes dialog.
  43. Click X icon in Actions column of "Default" row in Nodes section to delete it so that you will see the BugzillaNode instead.
  44. Click a pencil icon in Actions column of "Blocks" row in Connections section to edit it.
  45. Change Link Type to oslc_cm:relatedChangeRequest because Bugzilla’s "See Also" is mapped to this OSLC resource type.
  46. Click OK button in Connections dialog.
  47. Click Save button at the top right of BugizllaView.
  48. You will see some Bugzilla bugs are displayed with the connections (arrows). For example,
  49. Try to move the rectangles, which stand for Bugzilla’s bugs, to anywhere. For example,

    The "arrow" stands for Bugzilla’s "See Also" relation. So from this view, Bug "1 Improve the usability" has two "See Also" relations. ( to "2 Improve the login panel" and "3 Improve the installer usability" bugs )
  50. Try to move the cursor on the rectangle. If you will see the following "Authentication Required" dialog, type Bugzilla’s user id and its password.
  51. OSLC preview brings up
  52. Right click the rectangle so that the its context menu is opened.
  53. Try to select "Open Artifact". You will see Bugzilla’s bug.

Learn More

Eclipse Lyo

Jazz.net

About the author

Hirotaka Matsumoto is the member of Systems and Software Engineering Jumpstart Program team. He works in Tokyo Software Development Laboratory in IBM Japan. He can be contacted at jljlmatu@jp.ibm.com

Copyright © 2013 IBM Corporation

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.

Mon, 01 Jul 2013