IBM Rational 6.0.4 LDX - What Data Sources should be setup?
Good Afternoon,
I'm working with a new client and have a question with regard to the Data Sources in LDX. I can find information about Data Sources in LQE but it's unclear how and what should be setup for a full CLM Install automatically as part of he Install for LDX?
Should all Data Sources be configured Including the TRS 2.0 Feeds? or this is optional depending on what the customer wants/Needs. So could be added / updated later?
If data sources are NOT setup what is the implications for LQE/JRS etc.
Thanks - I can't find much documented on LDX so after some help.
Regards
Matt Muller
One answer
Matt,
links_ccm: https://<server>/ccm/oslc/workitems/trs2
Comments
Daniel,
Thanks for your response,
I'm still not sure exactly what the LDX Data Sources do and should you have all of them setup? When I look at the Data Sources in LDX I have: CCM, GC, QM.
However when you select add Data Sources I get the following:
TRS 2.0 feed for process resources in RTC
TRS 2.0 feed for SCM link resources in RTC
TRS 2.0 feed for SCM resources in RTC
TRS 2.0 feed for process resources in Design Management
Tracked Resource Set v2.0 for Design Management resources (server-wide)
TRS 2.0 feed for GC process resources
TRS 2.0 feed for GC process resources
TRS 2.0 feed Link Validity Resources
TRS 2.0 feed for QM resources
TRS 2.0 feed for process resources in DOORS Next Generation
Tracked Resource Set v2.0 for IBM DOORS Next Generation resources (server-wide)
If we are using RM, RTC, DM and DNG I can only assume we need these Data Sources?
Any ideas?
Thanks again
Matt
Matt,
If these were 'pre-configured' for you during the setup operations, the Link Index Provider (LDX) data sources that were already configured are likely all you need since they match ours (that said - I can't speak to the DM data source because we don't use that app).
See also https://jazz.net/forum/questions/208757/differences-between-ldx-and-lqe-for-v6 and https://jazz.net/forum/questions/223488/ldx-implementation-for-configuration-enabled-clm-provider