Connecting Lifecycle Query Engine or Link Index Provider to applications that use a different Jazz Team Server
If you installed Lifecycle Query Engine
(LQE) or Link Index Provider (LDX) on a separate Jazz
Team Server (JTS) from the
lifecycle management applications, first you add the client access licence for LQE or LDX on
the JTS where the
lifecycle tools are registered, then you create a functional LQE or LDX
user that can run background tasks, you create an inbound consumer key for LQE or LDX on
each lifecycle management application, and finally you add the data sources by using root services
documents or URLs. This configuration ensures that LQE or LDX
can access the IBM®
Engineering Lifecycle Management (ELM)
data.
Procedure
-
In a web browser, open the JTS
administration page:
https://server:port/jts/admin
. -
On the Server page, under Licensing, click .
- When prompted for a license, browse to the WEB-INF/classes/META-INF/licenses/TRS_Consumer_Internal.jar file in the lqe.war file. Follow the prompts in the wizard to accept the license agreement, and finish.
Creating the functional user that is required by LQE or LDX
Procedure
Creating an inbound consumer key for LQE or LDX on each lifecycle management application
Before you begin
Important: If
the lifecycle management applications are deployed to the same JTS as
LQE
or LDX, it is not necessary to create inbound consumers. Complete these steps only if the
applications that you add as data sources for LQE or LDX,
such as IBM Engineering Workflow
Management (EWM),
IBM Engineering Requirements Management
DOORS® Next
(DOORS Next), and IBM
Engineering Test Management (ETM), run on
a separate JTS.
Procedure
What to do next
Correcting failed data sources
For LDX, some data sources are added automatically by JTS. And if the applications whose data
sources are added in LDX are not local to LDX (registered with a different JTS) then those data
sources can end up in a failed state.![Error in the added sources](../images/data_source_error.png)
![Error in the added sources](../images/data_source_error.png)
Procedure
To correct the error, you can perform one of the following steps:
- Remove the data-sources and again add them.
- Update the authentication properties for the failed data-sources.
- Enter the OAuth Consumer Key and OAuth Consumer Secret that was created in the earlier application.
- You can obtain the OAuth URL from the root services document of the remote application.