RPE - Artifact Type URI different between project areas (using same type system)
Hi,
I'm trying to publish by filtering using a typeURI in the format:
https://server/rm/publish/text?typeURI=[typeURI]&oslc_config.context=[configURI]
I have got this working, however, The typeURI seems to be different between different Project Areas even though they are using the same Type System. this was achieved by creating the component in the project area then "Import Component Properties" from my template component.
The Artifact Type definition in the Component Properties have the same artifact name and artifact URI which is in the format:
However, in one Project Area, the TypeURI is _mvyesFHLEeuMrfkR2rtkWQ and in the other it's _bLvB4ldLEeuMrfkR2rtkWQ.
By using a consistent Type system and URI name space scheme, I was expecting that I could do publishing by "artifact type" across multiple projects without having to specify the typeName AND ProjectURI (just specify typeURI).
|
One answer
David Honey (1.8k●1●7)
| answered Aug 31 '21, 4:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER A common technique used by applications is to use system-generated type URIs and/or predicate URIs and then use
|
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.
Comments
Hi,
It looks like RPE is expecting the UUID of the type as the value of its ?typeURI parameter, which as you've correctly pointed out, differs in every project area. Have you tried using the URI of the type (the property of the type that you are allowed to set, which actually is a URI)? If not, we'll need an RPE expert to come up with some suggestion.