Directories created by the Deployment Template

The Deployment Template creates the following default directory structure. For each Endeca implementation that is deployed with the Deployment Template, look into these directories to identify currently used configuration options and scripts.

The Deployment Template is designed to support operations with the MDEX Engine in the production environment. This means it must support a variety of possible configurations and their modifications. Therefore, its AppConfig.xml file contains all the possible blocks and directories that you may need on your production servers.

For example, the Deployment Template has separate directories to ensure that the MDEX Engine operations are safely accessing only the information they need. Further, the default Deployment Template allows for configuring multiple Dgraphs, so additional directories are created to facilitate this task.

Directory Contents
config/lib Subdirectories to store any custom scripts or code for your Deployment Template project.
config/pipeline The Developer Studio pipeline file and XML configuration files.
config/report_templates Files required to generate an application's reports.
config/script The AppConfig.xml file and related Deployment Template scripts responsible for defining the baseline update workflow and communication of different Endeca components with the EAC Central Server.
control Shell (UNIX) or batch (Windows) scripts responsible for running different operations defined within AppConfig.xml.
data/incoming The premodified incoming data files that are ready acquisition by the Endeca pipeline and should be processed.
data/processing Temporary data and configuration files created and stored during the baseline update process.
data/forge_output The data and configuration files that are output from the Forge process to the Dgidx process.
data/dgidx_output The index files that are output from the Dgidx process.
data/dgraphs The copy of the index files used by an instance of the MDEX Engine.
data/state Autogenerated dimensions files.
data/complete_index_config

Merged configuration (that is, Developer Studio files from config/pipeline, with any Workbench- maintained files specified in the Deployment Template's ConfigManager component overwritten by files downloaded from the Workbench instance).

data/web_studio/config

Configuration files extracted from Workbench by the Deployment Template's ConfigManager component.

logs Various log files within subdirectories, such as Dgidx logs.
reports Generated reports.