Multiple Distributed LDX instances in a Modified Federated Topology

In some highly active environments, a single LDX server in the modified federated topology may not be sufficient. To alleviate this, one or more LDX instances can be deployed to manage versioned links for individual business units that only index the application sources used by that business unit.

Multiple Distributed LDX Servers in Modified Federated Topology

This document will provide the steps to configure a Modified Federated Topology to include additional LDX servers which are scoped for a particular business unit.

Deploy additional LDX server

• The additional LDX application should be deployed on its own server
• Install LDX application per the documentation
  • Install with a custom context root. Examples: /ldx-bu1, /ldx-bu2 or /ldx1,/ldx2
  • If Jazz Authorization Server is configured in the environment, make sure to check the box in the install to enable Jazz SSO during install.
  • If LDX was installed with the default context root, the best option is to re-install and set the correct context root.
• The LDX server will need to be registered with the JTS server after configuring the proxy (steps below).
• Run the LDX setup by going to https://elm.example.com/ldx-bu1/setup

Update proxy configurations to include the new instances

• Update proxy to add new LDX application(s) and their corresponding context root
  • Example: redirect /ldx-bu1 to https://ldx-bu1.example.com:9443/ldx-bu1
• For users of IBM Http Server, you will need to re-merge all of the application server plugin-cfg.xml files.
  • ELM deployments on Liberty will generate the individual plugin-cfg.xml files upon startup
  • Collect the plugin-cfg.xml file from each server to a directory on the JTS server, renaming each file to reflect the server the configuration is from (Example: jts-plugin-cfg.xml, ldx-bu1-plugin-cfg.xml)
  • Follow the documentation to merge the configuration files.
  • Update paths in the merged configuration file for the log file name and location, and where to find the certificate keystore file.
  • Deploy new merged configuration file for IHS to use. The location and name of the configuration file can be found in the IHS httpd.conf file. Either replace the existing file or update the httpd.conf file to point to the new file.

Configure additional LDX server for the business unit

• Configure LDX data sources - These will be only the systems required for use with the business unit.
  • Only the common LDX server will index all applications.
• Configure DN and ETM advanced properties to point to the new LDX server.
  • Change the value in the server Advanced Properties->com.ibm.team.links.service.internal.LinkIndexService->Link index provider URL to point to the new

Validation and testing the configuration

• Once configured the updated RM applications will only make link lookup requests to the LDX server configured in Advanced Properties.
• The new LDX server(s) will only have data sources for the RM, QM, and CCM instances that have links to or from the business unit RM server.
  • A link to or from the RM server to another application server that is not indexed by the business unit LDX server will not be shown in an RM artifact.
  • Links to or from the RM server from the application servers that are data sources in the business unit LDX server will be shown in RM artifacts.

Related topics: [StandardTopologyPatternsOverview][StandardTopologyPatternsOverview]], DeploymentPlanningAndDesign