Multiple Distributed LDX instances in a Modified Federated Topology

Authors: RichRakich
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.

Page contents

Multiple Distributed LDX Servers in Modified Federated Topology

In some highly active environments, a single LDX server in the Modified Federated Topology may not be sufficient. To alleviate this multiple LDX instances can be deployed to provide links to individual business units that only index the application sources used by that group. This is similar to the configuration in the full Federated Topology where individual business units can deploy their own LDX where there may be performance issues due to overall load or volume.

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 server should be deployed on its own server
Install LDX application server 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 install LDX with that enabled.
- If the application server 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 common JTS server

Update proxy configurations to include the new instances

Update proxy to add new root contexts added
- 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.

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 application instances.
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

External links:

Additional contributors: TWikiUser, TWikiUser

Deployment

Community information and contribution guidelines

Status icon key:

To do
Under construction
New
Updated
Constant change
None - stable page

Smaller versions of status icons for inline text:

Copyright © by IBM and non-IBM 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.