Sample Configuration

A full sample configuration is supplied in the Examples\Configuration subfolder of the program directory. Once you have adjusted system-specific properties (e.g., file paths, server names and passwords), you can run this sample configuration on any system. For example, it can be used for texting purposes.

The most important elements of the sample configuration are explained in the following sections. To better understand the explanations, we recommend that you place the content of the configuration files in a text editor alongside the explanations.

The sample configuration provides for the use of two program instances that are running separately. One program instance hosts the web services required for monitoring and configuration. The other is responsible for executing the processing scenario. When creating and testing a scenario configuration that was changed in the configuration phase, this separation has the advantage of only requiring you to restart the specific instance to which the scenario is assigned. The instance that executes the Config Web Service, on the other hand, can continue to run. You will not have to reload the Configurator and reopen the scenario after each restart.

In productive use, the separation into two program instances reduces the risk of monitoring activities and the actual processing slowing each other down (e.g., when calling up extensive log tables and when executing compute-intensive OCR or file conversion functions). The sample configuration only covers a single scenario. In practice, however, subdividing the processing into additional program instances might make sense if many scenarios are to be executed in parallel, or if certain worker instances execute resource-intensive actions that are to be decoupled from the other workers. For special use cases such as the xSuite Helix Proxy, it also makes sense to use a dedicated program instance so that the data throughput of the proxy is affected as little as possible by the rest of the processing.