# Configuring an automated/file-based deployment

The installer script provides a file-based configuration option to simplify the deployment and installation of the Deployment Template. This may be especially useful during development, when the same deployment process must be repeated many times.

A sample configuration file is provided in the conf subdirectory of the deploymentTemplate-[VERSION] install directory. The install configuration file should specify the deployment type, application name and deployment path. The following example specifies the installation of a Dgraph deployment with Workbench integration enabled:

    <install app-name="MyApp" >
      <deployment-path>C:\Endeca</deployment-path>
      <base-module type="dgraph" />
      <options>
        <option name="eac-port">8888</option>
        <option name="workbench-enabled">true</option>
        <option name="workbench-port">8006</option>
        <option name="dgraph1Port">15000</option>
        <option name="dgraph2Port">15001</option>
        <option name="logserverPort">15010</option>
      </options>
    </install>

The following example specifies the installation of an Agraph deployment with Parallel Forge enabled and Workbench integration disabled:

    <install app-name="MyApp" >
      <deployment-path>C:\Endeca</deployment-path>
      <base-module type="agraph" />
      <options>
        <option name="eac-port">8888</option>
        <option name="workbench-enabled">false</option>
        <option name="parallel-forge">true</option>
        <option name="dgraph1Port">15000</option>
        <option name="dgraph2Port">15001</option>
        <option name="agraph1Port">14000</option>
        <option name="agraph2Port">14001</option>
        <option name="forgeServerPort">14099</option>
        <option name="logserverPort">15010</option>
      </options>
    </install>

To specify an install configuration file:

Specify the `--install-config` flag to the deploy batch or shell script to specify the location of an install configuration file. The following example specifies that argument to the Windows installation script:

    deploymentTemplate-[VERSION]\bin\deploy.bat --install-config ..\conf\install_config.xml

When a configuration file is specified for the installer, the deployment attempts to retrieve and validate required information from the document before proceeding. If any information is missing or invalid, the installer prompts for that information, as described in previous sections. To truly automate the install process, the -`-no-prompt` flag may be passed to the installer, instructing it to fail (with error messages) if any information is missing and to bypass interactive verification of the Oracle Endeca version.