Open topic with navigation
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
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 three ways to configure the DAH child servers,
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 IDOL Server configuration, the section that you use depends on your system setup:
If you use identical child servers for the DIH and the DAH, use
[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
[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
[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.