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 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 the application server was installed with the default context root, the installed WAR file directory needs to be renamed:
    • Rename the ldx.war directory in the /server/liberty/clmServerTemplate directory
    • If the Liberty server has been started and the profile created, the ldx.war directory in /server/liberty/servers/clm/apps will need to be renamed.
• The LDX server will need to be registered with the common JTS server

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.
• Configure DN and ETM advanced properties to point to the new LDX server.

Related topics: Deployment web home, Deployment web home

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser