Installing Link Index Provider (LDX) on its own Server todo.png

Authors: Richard Watts
Build basis: 6.0 and later

When we introduced the Link Index Provider (LDX) as part of the Configuration Management (CM) feature set, we decided to reduce complexity and install it along with the Jazz Team Server (JTS) on the same server. By doing this, we made the configuration largely invisible to our customers. This eliminated configuration complexity but it meant that the two applications share the single server resources. If you have a large CM enabled deployment, you might want to separate the two, putting LDX on its own server. This document describes how to do that.

Implications

When you move LDX to its own server, the Jazz Team Server will not be able to configure LDX automatically. You (the administrator) will need to configure LDX yourself. This process is exactly the same as configuring the Lifecycle Query Engine (LQE). Specifically, you will need to add the TRS feeds yourself.

Steps

  1. Install Liberty
  2. Install Security Certificates
  3. Deploy LDX on Liberty
  4. Register LDX with the Jazz Team Server
  5. Add TRS Feeds
  6. Configure Jazz Team Server

Setup and Configuration of LDX

Related topics: Installing & Upgrading, Deployment web home

External links:

This topic: Deployment > WebHome > DeploymentInstallingUpgradingAndMigrating > DistributedLDX
History: r6 - 2018-10-10 - 20:29:36 - RichardWatts
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project