The Production Directory
This information is not applicable to Primo VE environments. For more details on Primo VE configuration, see Primo VE.
The production directory includes configuration and data files that play a role in the production environment. This directory is not overwritten when the system is upgraded. Since the production directory can be very large, it can be moved to another location. The location of the production directory is defined in the installation configuration files.
The following table lists the subdirectory structure of the production directory (home/profile/publish/publish/production).
| Path (relative to the production directory) | Description |
|---|---|
|
conf
|
Contains the production configuration files used by all pipes, including the PNX XSD and deduplication matching rules. These configuration files are copied from another directory during the installation.
|
|
conf/normalizationExport
|
When a normalization set is deployed, the XML files used by the normalization process are created in this directory. There is a subdirectory for every normalization set.
|
|
log
|
Contains the Tomcat and general Primo log files.
|
|
pipes
|
Contains all the directories created per pipe. The directory name is the name of the pipe.
Alias: be_pipes
|
|
pipes/<pipe-name>
|
When a new pipe is created, a directory with the pipe name is created with the following subdirectories: conf and <source_code>.
|
|
pipes/<pipe-name>/conf
|
Contains two configuration files:
|
|
pipes/<job-name>/<source_code>
|
Contains subdirectories for every run of the pipe. The directory name includes the date and time of the pipe run in the YYYY-MM-DD@HH:MM:SS format. For example:
2006-07-25@20.37.07
For additional information about the structure of the pipe run directory, refer to The Pipe Run Directory.
|
|
processes
|
Contains subdirectories for each process. Within each process there are subdirectories, in the date/time format, for every run. The log files for each run are stored in these subdirectories.
|