Distributed Action Handler 26.1
Distributed Action Handler Help

# Unified Configuration

DAH is generally installed and operated as a stand-alone component, where you use a separate `dah.cfg` file to configure the DAH. However, in simple testing and training setups you can configure the DAH as part of a unified Knowledge Discovery configuration, by using the `idolserver.cfg` file.

For more details about unified and component setups, refer to the Knowledge Discovery Getting Started Guide.

If you use a unified configuration, use the `[DistributionSettings]` section of the `idolserver.cfg` file to enter the configuration options that normally appear in the `[Server]` section of the `dah.cfg` file for a stand-alone configuration. All other section names are the same in both configuration files.

There are three ways to configure the DAH child servers, DistributedEngines, `[DAHEngines]` and `[DistributionIDOLServers]`.

In a stand-alone DAH, you can use any of these options. However, you must use the same section format for all your child servers (that is, you must not specify some child servers in one type of sections, and some in another). The most common method is to use the DistributedEngines parameter with the `[DistributedEngineN]` child server configuration sections.

In a unified configuration, the section that you use depends on your system setup:

- If you use identical child servers for the DIH and the DAH, use `[DistributionIDOLServers]` with `[IDOLServerN]` child server configuration sections. For example, you might have DIH and DAH both sending actions directly to the Content components.

- If you use different child server configurations for the DIH and the DAH, use `[DAHEngines]` with `[DAHEngineN]` child server configuration sections. For example, you might be using a tiered set up, so that the DAH child servers are child DAH components, while the DIH child servers are child DIH components.

  In this case, you configure the DIH by using the `[DIHEngines]` with `[DIHEngineN]` sections. For more information, refer to the Distributed Index Handler Administration Guide.

The configuration examples in this guide generally consider DAH as a stand-alone component, with its own configuration file.

Related Topics

- Add Child Servers to the Distributed Action Handler

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: Unified Configuration