Distributed Action Handler 26.1
Distributed Action Handler Help

# Add Child Servers to the Configuration File

You configure distribution child servers differently for a stand-alone DAH setup and a unified Knowledge Discovery configuration that includes a DAH.

In Simple Combinator Mode (`SimpleCombinatorMode=TRUE`) you can start the DAH without having Content engines configured. You can add Content engines after startup by using the EngineManagement action.

To add a distribution child server for stand-alone DAH operation

1. Open the DAH configuration file in a text editor.

2. Find the `[Server]` section.

3. In the `[Server]` section, set the DistributedEngines parameter to the number of distribution child servers that you require.

4. Add a new `[DistributedEngineN]` section for each distribution child server that you require, in consecutive order starting at 0 (zero). For example, for two child servers:

       [DistributedEngine0]
       Host=testserver1
       Port=9100
       Type=IDOL

       [DistributedEngine1]
       Host=testserver2
       Port=9100
       Type=IDOL

   The above example shows two child servers. To add a new child server, increase the DistributedEngines parameter in the `[Server]` section by one and add a new `[DistributedEngineN]` section for the new child server:

       [DistributedEngine2]
       Host=testserver3
       Port=9100
       Type=IDOL

5. Save and close the configuration file.

6. Restart the DAH for your changes to take effect.

To add a distribution child server for integrated DAH operation in which DAH and DIH are configured together

1. Open the Knowledge Discovery unified configuration file in a text editor.

2. In the `[DistributionIDOLServers]` section, set the `Number` parameter to the number of distribution child servers that you require.

3. In the `[DistributionIDOLServers]` section, add a new `[IDOLServerN]` section for each distribution child server that you require, in consecutive order starting at 0 (zero). For example, for two child servers:

       [DistributionIDOLServers]
       Number=2

       [IDOLServer0]
       Host=localhost
       Port=9100

       [IDOLServer1]
       Host=localhost
       Port=9200

   The above example shows two child servers. To add a new child server, increase the `Number` parameter in the `[DistributionIDOLServers]` section by one and add a new `[IDOLServerN]` section for the new child server:

       [IDOLServer2]
       Host=localhost
       Port=9300

4. Save and close the configuration file.

5. Restart the unified Knowledge Discovery service for your changes to take effect.

To add a distribution child server for an integrated DAH operation in which DAH and DIH are configured separately

1. Open the unified configuration file in a text editor.

2. In the `[DAHEngines]` section, set the `Number` parameter to the number of distribution child servers that you require.

3. In the `[DAHEngines]` section, add a new `[DAHEngineN]` section for each distribution child server that you require, in consecutive order starting at 0 (zero). For example, for two child servers:

       [DAHEngines]
       Number=2

       [DAHEngine0]
       Host=localhost
       Port=9100

       [DAHEngine1]
       Host=localhost
       Port=9200

   The above example shows two child servers. To add a new child server, increase the Number parameter in the `[DAHEngines]` section by one and add a new `[DAHEngineN]` section for the new child server:

       [DAHEngine2]
       Host=localhost
       Port=9300

4. Save and close the configuration file.

5. Restart the unified Knowledge Discovery service for your changes to take effect.

Copyright 2025 Open Text
Version 26.1 | Last updated January 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery Distributed Action Handler 26.1

Topic Title: Add Child Servers to the Configuration File