It's all about the answers!

Ask a question

Migrate LQE JRS reports onto production cloud with no LQE


Sean F (1.3k241145) | asked Sep 21 '18, 10:17 a.m.
retagged Sep 25 '18, 7:51 a.m. by Minakshi Jaint (5113)

I have developed a bunch of JRS metrics on a standalone environment using LQE.

I tried to migrate them to the production cloud environment and it failed since LQE is not a listed service nuder.

https://xxxx.clm.ibmcloud.com/rs/endpoint

The only option listed is Data Warehouse

On the standalone test environment LQE is already there.

I can click on Create New Data Source but I am not sure where to get the values for all of the following questions:-

 SPARQL data source URL:    https://xxxx.clm.ibmcloud.com/lqe/sparql     ?

Authorization type:   Jazz Team server

Authorization consumer key:
   ?

Authorization consumer secret:   ?

Jazz Team Server discovery URL:
   ?

Require a configuration to run a report: No

Allow only report managers to edit queries: Yes

Also I am not sure if LQE is supported in our cloud environment as our DNG Professional subscription does not include some features (such as Global Configurations)

Accepted answer


permanent link
Chuba Arah (1563) | answered Sep 21 '18, 2:36 p.m.
JAZZ DEVELOPER

Hi Sean,

You should NOT have to manually create new data sources in Report Builder. If the Jazz Team Server (JTS) that Report Builder is registered to does not have LQE installed, you can't utilize the reports you developed in your standalone environment as there's no data source for the reports to run against.

If LQE has been installed, registered and configured, you should be able go to https://xxxx.clm.ibmcloud.com/rs/setup and click Connect to data sources as stated in https://jazz.net/help-dev/clm/topic/com.ibm.team.jp.jrs.doc/topics/t_jrs_mng_ds.html. This should create the LQE based data sources in Report Builder automatically.

NOTE: As stated in the topic above, there are three scenarios when you should click Connect to data sources (after initial installation/configuration of CLM and Report Builder, after enabling configuration management (CM) in DNG or RQM and when adding new data sources).

If you confirm that LQE is registered and working correctly but the data source is not created, you can try creating it manually based off the properties of the LQE data source in your test environment. That being said, please see the following:

1. SPARQL data source URL: https://xxxx.clm.ibmcloud.com/lqe/sparql.

This is correct for the main Lifecycle Query Engine data source. If you want the Lifecycle Query Engine scoped by a Configuration data source, it should be https://xxxx.clm.ibmcloud.com/lqe/sparql-variable-config.

2. Authorization type: Jazz Team server.

This is correct unless you use Jazz Authorization Server (JAS) in your environment. If you use JAS, you should switch to Jazz Security Architecture SSO.

3. Authorization consumer key: This should use the same Consumer Key shown in jts/admin under Server > Registered Applications for Report Builder (/rs).

4. Authorization consumer secret: This should use the same Consumer Secret that's used when you click the Edit icon (under the Actions column) for /rs in jts/admin > Server > Consumers (Inbound). If Report Builder was registered during jts/setup, you won't know what this value is.

5. Jazz Team Server discovery URL: This should be https://xxxx.clm.ibmcloud.com/jts/discovery.

Sean F selected this answer as the correct answer

Comments
Sean F commented Sep 22 '18, 5:02 a.m.

Thanks Chuba

One other answer



permanent link
Davyd Norris (2.2k217) | answered Sep 21 '18, 8:52 p.m.
edited Sep 21 '18, 9:40 p.m.
If the SaaS instance is CLM on Cloud Professional the LQE is not installed or available.LQE is only available for Enterprise level SaaS instances.

You'll have to redevelop your reports using the regular DW unfortunately

Comments
Sean F commented Sep 22 '18, 5:02 a.m.

Thanks Davyd

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.