It's all about the answers!

Ask a question

RPE and DOORS Next Generation


Chris Noble (2735) | asked Jul 09 '14, 8:01 a.m.
I have downloaded and installed DOORS Next generation with Configuration Management 5.0 Beta (https://jazz.net/downloads/rational-doors-next-generation/betas/5.0CMBeta1) and everything is working ok. I want to try using Rational Publishing Engine on this and I am not sure where to find the schema and what url to use for the rest server (I assume it uses a Rest server link Requirements Composer). I have not been able to find any documentation that has these integration details.

Accepted answer


permanent link
Benjamin Silverman (4.1k610) | answered Jul 15 '14, 3:42 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I just tried this on the beta and you do need to specify an additional parameter.  You can get the resources like this:

https://clmweb.ibm.com:9443/rm/publish/resources/*?vvc.configuration=https%3A%2F%2Fclmweb.ibm.com%3A9443%2Fvvc%2Fconfigurations%2F1

To get the reference supplied for the newly required "vvc.configuration" property, open an artifact in the configuration you are reporting on and select the link icon in the navigation breadcrumb.  Hope it helps!
Chris Noble selected this answer as the correct answer

Comments
Chris Noble commented Jul 16 '14, 9:34 a.m. | edited Jul 16 '14, 9:35 a.m.

Hi Benjamin
Yes, that seems to work, at least RPE contacts the datasource. Now I need to work through some other errors being thrown up, but these look like RPE-DOORS NG stuff that is probably in the documentation somewhere.
Thanks for your help.
Chris

2 other answers



permanent link
Benjamin Silverman (4.1k610) | answered Jul 09 '14, 9:06 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Chris,

There is a reporting wiki page for RDNG on jazz.net.  Here are some of the links that should help you get started:

1)  REST API Documentation
2)  Main reporting wiki page

Hope it helps,

Comments
Chris Noble commented Jul 09 '14, 10:09 a.m.

Hi Benjamin
Thanks for your pointers. However I am still struggling, it may be I do not have enough background yet. I am coming from the point of view of having used RPE with Rhapsody. With Rhapsody I can add the Default.xsd schema from the Rhapsody installation folders and I have access to all the model element types from this schema. I can then point the data source to the Rhapsody Rest server and all is well with the world. I was expecting a similar sort of setup for DOORS Next generation. However if I go to the installation directories I can find a host of .xsd files, none of which jump out as being correct for DOORS Next Generation or even Rational Requirements Composer.
One of your links above gives a 'get schema' url but when I try this url (with my server:port details) in the 'Rest Schema Discovery' menu item I get to a dialogue box with a number of items in the "XML schema" panel but if I select one and click next I get the following error " Authentication error 'Auto: connection to https://server:port/rm/publish/resources failed. None of the known protocols succeeded.' occurs."

Chris


Benjamin Silverman commented Jul 09 '14, 11:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Hi Chris,

What's the URL you are using?  You can get the schema using https://server:port/rm/publish/text?metadata=schema where "text" is the schema you are interested in using (ie - text, resources, etc..).  The links I sent earlier describe each schema, but that format should work for loading the schema (xsd) locally in to RPE.  The difference between RDNG and Rhapsody is that Rhapsody provides the .xsd files, and for RDNG, you download it remotely from the server to pull it in to RPE.


permanent link
Abish Mathew Zachariah (252511) | answered Jul 09 '14, 1:17 p.m.

Hi Chris,

You don't have to use "Schema Discovery" in RPE to add a RRC data source schema. Instead, you can use 'Data > Add Data Source schema' wizzard, use "Generic XML" as the schema type, the URL https://server:port/rm/publish/text?metadata=schema as the Schema file and 'OAuth' as the authentication type to load a RRC schema.

Rhapsody also offers you live schema like RRC. Because the Default.xsd will only give you the generic types and in case if you custom types in the model then you have to use the live schema. Also, if you have other profiles loaded into the Rhapsody model like SysML or HarmoneySE, then RHP provides you schema specific to these profiles, which can be loaded from the "Profiles" folder. Hope this helps.

Best Regards
Abish M Zachariah


Comments
Chris Noble commented Jul 10 '14, 5:02 a.m. | edited Jul 10 '14, 5:03 a.m.

Hi Abish
Thanks for your response. I used the get data and now have the schema loaded. Why is this a "Generic XML" rather than a "REST"? I guess my knowledge is lacking here.
Can you tell me the data source url form I need to use in the generate document wizard? For example in the Rhapsody version I had to use "http://localhost:xxxxx/Rational/Rhapsody/".
I tried using "https://server:port/" and "https://server:port/rm/publish" but both gave different errors in the generation log shown below:
 "CRRPE1064I Error in engine The general entity "nbsp" was referenced, but not declared.CRRPE3012E IBM Rational Publishing Engine error. The general entity "nbsp" was referenced, but not declared"

"CRRPE1064I Error in engine Bad Request Request URL: https://server:port/rm/publish/ Response code: 400 Response message: Bad Request"
Regards
Chris Noble


Chris Noble commented Jul 10 '14, 8:30 a.m.

Hi Abish
I am using the DOORS Next Gen with Configuration Management V5.0 - is this likely to be a problem? I assume the hierarchy is going to be different?
Regards
Chris


Abish Mathew Zachariah commented Jul 11 '14, 2:41 a.m.

Hi Chris ,

Good that you are not able to load the schema into the studio. For RRC you can use REST as well as “Generic XML”. When you use REST, RPE will append field parameters at the end of the REST call to filter data. In case if the source product does not support this filtering mechanism then it will cause performance issues. But either will work.With respect to base RRC base URL in the RPE specification file, if you have loaded the test schema then you can use https://server:port/rm/publish/text/*  or https://server:port/rm/publish/text?projectName=project_name  to fetch text artifacts pertaining to a project. You can refer the below link for more information on the query parameters that is supported by RRC:
https://jazz.net/wiki/bin/view/Main/RRCReportableRestAPI .Also, make sure that you set the authentication type in the RPE .dsx file as OAuth to communicate to RRC. Let me know how it goes.

Best Regards
Abish M Zachariah


Chris Noble commented Jul 11 '14, 4:56 a.m.

 Hi Abish


If I use https://server:port/rm/publish/text/* or https://server:port/rm/publish/text?projectName="projectname" in either the document generation wizard or the Datasource "preview data" (in the Outline tab of the template) I get a Internal Server error: Response code 500.
As I am using the Configuration Management Beta that has configuration spaces, is this what is causing the problem? Presumably there should be a way to address a particular configuration space to retrieve the correct version of the artifacts? I am wondering if this has been implemented in the Beta yet?
Thanks for your help on this
Chris


Abish Mathew Zachariah commented Jul 11 '14, 8:38 a.m.

Hi Chris

To rule out this, access the URL  https://server:port/rm/publish/text?projectName=projectname in a web browser or a REST client and check if the RRC server returns valid XML file. Also note, you do not have to include the projectname within "". May be you can try accessing this also : https://server:port/rm/publish/resources?projectName=projectname in a web browser.

Best Regards
Abish M Zachariah


Chris Noble commented Jul 11 '14, 9:29 a.m.

Hi Abish
When I try either of these I get the error below. Because the error mentions VVC, it leads me to think it is CM related. Any thoughts would be appreciated.
Regards
Chris

Error 500: Internal Server Error

JAFConfigurationCacheService.getVersions(): No VVC Configuration in queryScopeParams (More info found at entry [3f4fc6c1a17a1f0e] in the RM application server log)


showing 5 of 6 show 1 more comments

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.