Creating new root labresourceattribute using API
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."
The API seems quite specific that users must select CPU, Operating Systems or Software Install as the qm:parent for creating a new labresourceattribute.
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:
13 answers
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
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>
page 2of 1 pagesof 2 pages