About the sample pipelines

For testing purposes, the Deployment Template includes two sets of pipelines and configuration files.

The two sets of pipelines and configuration files are located in two sub-directories of the [appdir]/config directory:

The pipeline directory contains configuration files from the sample_wine_data reference project that ships with Oracle Endeca Guided Search. The corresponding source data is in the [appdir]/test_data directory.
Note: This guide assumes that you will be placing the configuration files for your pipeline in this directory.
The cas_crawl_pipeline directory contains a delta update pipeline that is tailored for Oracle Endeca CAS Server file system and CMS crawls. No source data is provided, so you will have to run a crawl.

While these sample pipelines facilitate testing of the deployment template, these files are intended to be replaced with project-specific files immediately after a deployment template has been properly configured.

This document describes how to modify or create a pipeline that is designed for integration within the deployment template operational structure. This includes pipeline naming requirements, common errors encountered, etc.

This document assumes that the reader has created a new deployment template application in the [appdir] directory, and has run the deployment script (deploy.bat or deploy.sh). Note that the usage guide also documents how to configure and run CAS crawls using the deployment scripts.