When Configuration Management is enabled in an IBM Engineering Lifecycle Management (ELM) project, OSLC back links are not stored along with the artifact itself, they are managed by IBM Link Index Provider (LDX) and it must be configured in order to see back links. LDX is required to be installed for back links to be discovered and displayed.

Starting with IBM Engineering Lifecycle Management (ELM) 7.2, Link Indexing is provided directly by IBM Lifecycle Query Engine (LQE). There is no longer a need to install and use IBM Link Index Provider (LDX). In that context, instructions provided in this page should be realized in LQE rather than in LDX.

You need to register data providers in LDX for ${local-app-connector}. This is done by providing the URL of the Root Services document to LDX. You need to ask the ${local-app-connector} administrator to share with you:

  1. The URL of the Root Services document. It is visible in the Consumers page, in server administration of ${local-app-connector}.
  2. The OAuth consumer key and secret to use. Those are defined by the ${local-app-connector} administrator in the Consumers page as well.

Once you have the URL of the Root Services document and OAuth information, follow the steps defined in Adding data providers to Lifecycle Query Engine by using root services documents to add ${local-app-connector} TRS feeds. The mentioned procedure is for IBM Lifecycle Query Engine (LQE) but is the same for LDX. You just need to change /lqe for /ldx in the URL provided in the first step of procedure, to access the right page and configure the new data providers.

LDX will discover TRS feeds declared in the Root Services document and will ask which one of them to register. You need to register all available TRS feeds, one by one, except the Process feed that is not relevant in this scenario and that you may skip.

If everything went well, you will see new data providers registered and updated in LDX Data Providers page.