It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,961

question asked: Dec 23 '11, 11:14 a.m.
question was seen: 8,465 times
last updated: Dec 23 '11, 11:14 a.m.

Related questions

Creating new root labresourceattribute using API

0
Wayne Belshaw (148●8●7) | asked Dec 23 '11, 11:14 a.m.
Paul,
The API seems quite specific that users must select CPU, Operating Systems or Software Install as the qm:parent for creating a new labresourceattribute.

I am able to create a new root labresourceattribute using the GUI but need to confirm if the description below is stating that I CANNOT use the API currently to create new root entries, e.g., Switch (and I would add additional switch model types via API).

Please confirm if this is a limitation? If not, how do I set the root in the labresourceattribute XML to use my new root name "Switch?"

From API description for labresourceattribute:

"A Lab Resource Attribute can be used to add data to the lab resource catalog. This resource may only be use to add to the system, there is no DELETE for this service. The name of the new attribute must be indicated as the Id in the URL. The types that may be extended by this mechanism are: CPU, Operating System and Software Install. The parent where this attribute will show up in the hierarchy must also be indicated. If the new attribute is to be put at the root of the hierarchy, a special keyword must be used for the parent. These are: CPU, OperatingSystem and SoftwareInstall."

13 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Wayne Belshaw (148●8●7) | answered Jan 11 '12, 7:09 p.m.
As mentioned, the System log contains the following exception.:

java.lang.IllegalArgumentException: Duplicate lab resource type specified: VDX6730abc.

As such, this is a defect since labresourceattribute resources cannot be updated. Please open a defect (https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.newWorkItem).


Paul,
I have automation of the Types working with the catalog now. When I push the info into the API, it is taking 5-10 SECONDS to return with a 201 code. With cases, plans and other attributes it is around 300 msec per transaction using the RQMUrlUtility in 3.0.1.

Can you help explain why there is so much overhead with the catalog update process? Fortunately, this is something we typically only do once per project but it is still painful.

Thanks!

Sample XML below (resource name is same as title but with rqmtype.xml suffix added - dc is title, qm is parent - not displaying below).

<xml>
<labresourceattribute>
<dc>HP_DL185G5</dc>
<qm>Server Models</qm>
</labresourceattribute>
0
permanent link
Paul Slauenwhite (8.4k●1●2) | answered Jan 12 '12, 11:11 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Agreed. See https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/60542.
0
permanent link
Wayne Belshaw (148●8●7) | answered Jan 12 '12, 11:15 a.m.
Agreed. See https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/60542.


Thanks for filing and confirming the defect on my behalf! Sounds like the fix will get picked up in 4.0. We can manage until then.

Your answer

Register or to post your answer.


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.