Open topic with navigation

# 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 IDOL Server, by using the `idolserver.cfg` file.

For more details about unified and component setups, refer to the IDOL 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 two ways to configure DAH for a unified configuration:

- Configure DAH and DIH together.

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

  - Use the `[DistributionIDOLServers]` and `[IDOLServerN]` sections to configure the child servers. Refer to the IDOL Server Administration Guide.

  In this type of configuration, all child servers perform both indexing and actions, and the configuration options that you set apply to both DAH and DIH. For this example, the child servers are stand-alone Content components.

- Configure DAH and DIH separately.

  - Use the `[DistributionSettings]` section of the `idolserver.cfg` file to enter the configuration options that normally appear in the `[Server]` sections of the `dah.cfg` and `dih.cfg` files for a stand-alone configuration.

  - Use the `[DAHEngines]` and `[DIHEngines]` sections to configure DAH and DIH child servers respectively. Refer to the IDOL Server Administration Guide and the Distributed Index Handler (DIH) Administration Guide.

  In this type of configuration, you can configure different child servers to perform indexing or actions exclusively, which permits greater flexibility in administering your system. For example, the DIH can distribute index actions to DIH child servers in a chained distribution setup while the DAH distributes actions directly to stand-alone Content servers.

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

© 2016 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close We welcome your comments! To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm