Connecting Lifecycle Query Engine or Link Index Provider to applications that use a different Jazz Team Server
If you installed Lifecycle Query Engine or Link Index Provider on a
separate Jazz® Team Server from the lifecycle management applications, first you add the
client access licence for Lifecycle Query Engine or LDX on the JTS
where the lifecycle tools are registered, then you create a functional Lifecycle Query Engine
or LDX user that can run background tasks, you create an inbound consumer key for Lifecycle Query Engine or LDX on each lifecycle management application, and finally you add the data
providers by using root services documents or URLs. This configuration ensures that Lifecycle Query Engine or LDX can access the IBM® Engineering Lifecycle Management 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 Lifecycle Query Engine or Link Index Provider
Procedure
Creating an inbound consumer key for Lifecycle Query Engine or Link Index Provider on each lifecycle management application
Before you begin
Important: If
the lifecycle management applications are deployed to the same JTS as
Lifecycle Query Engine or LDX, it is not necessary to create inbound consumers. Complete
these steps only if the applications that you add as data providers for Lifecycle Query Engine or LDX, such as IBM Engineering Workflow Management, IBM Engineering Requirements Management DOORS® Next (DOORS Next), and IBM Engineering Test Management, run on a separate JTS.
Procedure
What to do next
- Connecting to a data provider using a root services document
- Connecting to a data provider using a URL
Correcting failed data providers
For LDX, some data providers are added automatically by JTS. And if the applications whose data providers are added in LDX are not local to LDX (registered with a different JTS) then those data providers can end up in a failed state.
Procedure
To correct the error, you can perform one of the following steps:
- Remove the data providers and again add them.
- Update the authentication properties for the failed data providers.
- 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.