Specifying a pipeline to run in AppConfig.xml (for Record Store output)

The devStudioConfigDir attribute in the ConfigManager custom component specifies the Forge pipeline to run. By default, the Deployment Template checks the [appdir]/config/pipeline for the Forge pipeline to run. This includes baseline updates and partial updates. It is simplest to put your pipeline files in this directory.

You specify the Forge pipeline that you configured to read from one or more Record Store instances. (For details about creating a Forge pipeline, see the Oracle Endeca CAS Developer's Guide.)

To specify a Forge pipeline to run in AppConfig.xml:

Ensure that your Forge pipeline files are located in [appdir]/config/pipeline.
Alternatively, modify the devStudioConfigDir property in the ConfigManager custom component to reference the pipeline directory. Also, modify the configDir property in the Partial update Forge section to reference the pipeline directory. In this example, the Forge pipeline is stored in the pipeline directory:
```
<custom-component id="ConfigManager" host-id="ITLHost"
  class="com.Endeca.soleng.eac.toolkit.component.ConfigManagerComponent">
  <properties>
  ...
  </properties>
  <directories>
    <directory
      name="devStudioConfigDir">./config/pipeline
    </directory>
    ...
  </directories>
```