It's all about the answers!

Ask a question

RRC and RPE - Can not access data source and schema


Chris Hardy (3651619) | asked Feb 13 '13, 5:17 p.m.
edited Feb 13 '13, 6:03 p.m.

I am having a problem using RPE with RRC.
Firstly when I add the (Generic XML) data source schema in a new RPE template I use the location:
     https://localhost:9443/rm/publish/resources?metadata=schema
(I have confirmed that this path works in an internet browser)
after I have added this path the tool asks me to confirm username and password.
The user name and password I use are definitely valid but the only way i can get them to pass is to select "OAUTH"
This then creates the data source schema in the template correctly

I add in a simple query to access the title of the artifacts.

When i come to generate the document I set the data source to the following path:
https://localhost:9443/rm/publish/resources?projectName=JKE Banking (Requirements Management)
(Again I have confirmed this path works in an internet browser)
I configure the data source using same user name and password as previoulsy.

The generation then fails with the following messages:
CRRPE1064I Starting run...
CRRPE1064I Processing document template 1 of 1.
CRRPE3518W Native filters could not be applied.
CRRPE3522W Native sorts could not be applied.
CRRPE1064I Using URL: https://localhost:9443/rm/publish/resources?projectName=JKE%20Banking.
CRRPE1064I Cannot access https://localhost:9443/rm/publish/resources?projectName=JKE%20Banking. Verify that URL, user name and password are correct. Error is: HTTP: 0
CRRPE1064I Failed to configure data source RM with https://localhost:9443/rm/publish/resources?projectName=JKE%20Banking.
CRRPE3320E Failed to configure data source RM with https://localhost:9443/rm/publish/resources?projectName=JKE%20Banking.
CRRPE1064I Error in engine

HTTP: 0

CRRPE3011E IBM Rational Publishing Engine error.
HTTP: 0
CRRPE1064I Aborting engine execution...
CRRPE3094I 0 publishing commands are processed. 0 publishing commands remain to be processed.
CRRPE3097I The document template is processed. If there are no more templates to process, output files are being written.
CRRPE1064I Document generation finished in 1 seconds.
CRRPE1022I The process was completed in 1.955 seconds.
CRRPE1023E The document could not be generated.

This a test environment using tomcat, derby and the money matters example
Thew confusing thing is that I have another identical test environment
which work fine. The only difference is that when i create the data source schema i leave the user authentication to "Auto" rather than choosing "OAuth"

Any ideas on what is wrong?
I am using RRC 4.0.1 and RPE 1.2

Any thoughts at all?

Accepted answer


permanent link
Kristin Kronstain Brown (176) | answered Feb 18 '13, 10:09 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
You can set the authentication in the document specification in the Properties view in version 1.2. It isn't currently available when you configure the data source, so it might not be readily visible where you expect it to be.

To set the authentication type in the document specification:
  1. In the Document Specification view of the Launcher, select the data source.
  2. In the Properties view, locate the authentication field.
  3. Enter OAuth.
  4. In the user name and password fields, enter your credentials to authenticate with the data source.
  5. Save the changes and generate the document.

The only difference though seems to me to be what you are entering in the authentication fields. Use OAuth and not auto for data sources that use OAuth authentication.

Chris Hardy selected this answer as the correct answer

One other answer



permanent link
Kristin Kronstain Brown (176) | answered Feb 14 '13, 9:59 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
This is a known issue in Rational Publishing Engine 1.2.

For data sources that support only OAuth, you must set the authentication property to OAuth explicitly. An auto-detection algorithm results in failure and the OAuth cannot be verified. This failure occurs because the OAuth algorithm falsely reports authentication success. The auto algorithm stops, but the data that is accessed is actually the login page itself and not the real data.

I hope this helps!

Comments
Chris Hardy commented Feb 14 '13, 5:57 p.m.

Hi Kristin,
That partially answers my question but:
in the template when I add the data source schema I have the option to chose the authentication method, in this case "OAuth"
When i do so the schema imports.

However when I try to generate the document, and set the data source location I don't have the optionĀ  to select the authentication and i guess thats why the generation is failing?
Is there a way to specify the authentication method when setting up the data source for documentation generation ?

Also not sure why it works ok on one system and not on another?

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.