Open topic with navigation
DIH is generally installed and operated as a stand-alone component, where you use a separate
dih.cfg file to configure the DIH. However, in simple testing and training setups you can configure the DIH 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.
In a unified configuration, use the
[DistributionSettings] section of the
IDOLserver.cfg file to enter configuration options that normally appear in the
[Server] section of the
dih.cfg file for a stand-alone configuration. All other section names are the same in both configuration files.
There are two options for configuring DIH child servers,
In a stand-alone DIH with its own configuration file, you can use either option. 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 section, and some in the other).
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, in this case you might have DIH and DAH both sending actions directly to the Content component.
If you use different child server configurations for the DIH and the DAH, use
[DIHEngineN] child server configuration sections. For example, in this case you might be using a tiered DIH set up, so that the DIH child servers are child DIH components, while the DAH child servers are child DAH components.
In this case, you configure the DAH by using the
[DAHEngineN] sections. For more information, refer to the Distributed Action Handler Administration Guide.
The configuration examples in this guide generally consider DIH as a stand-alone component, with its own configuration file.