This topic describes the directories that are created in the Platform Services installation.
The
PlatformServices directory is the top-level
directory for the Platform Services software. It has three sub-directories,
which are described below.
The
PlatformServices/<version> directory is the
root directory for the Platform Services software. This is the directory to
which the
ENDECA_ROOT variable is set.
The directory contains files and software modules for all the Platform Services components.
|
Directory |
Contents |
|---|---|
|
|
Executables for the Platform Services programs and utilities, such as Forge, Log Server, and Report Generator. |
|
|
Components of the Content Acquisition Development Kit. |
|
|
Configuration files, such as the DTDs used by Guided Search components (such as Forge) and the product configuration file. |
|
|
The Licensing Guide. |
|
|
Version 7 of the Java 2 Platform Standard Edition Development Kit (JDK). |
|
|
Java and .NET versions of the Presentation and Logging APIs, as well as libraries for various Platform Services components (such as the Endeca Application Controller). |
|
|
Shared libraries used by various Guided Search components. This directory is created only on UNIX platforms. |
|
|
Binaries for Perl utilities. |
|
|
Internal configuration file for the installer. |
|
|
Directories and files for the HTTP Service. |
|
|
The program to uninstall Platform Services. |
|
|
Utility programs used by Guided Search programs. |
|
|
Templates of the
|
The
workspace directory is the directory to which the
ENDECA_CONF variable is set.
|
Directory |
Contents |
|---|---|
|
|
Configuration files for the Endeca Application Controller and the HTTP Service. |
|
|
Configuration files for the JCD and the Endeca Access Control System, as well as report generation style sheets. |
|
|
Log directory for the HTTP Service. |
|
|
Reports generated from Log Server files. |
|
|
The
|
|
|
State information maintained by the Endeca Application Controller. |
|
|
Temporary files written out by the Endeca Application Controller. |
|
|
Working directory of the HTTP Service. |
The
reference directory contains the sample wine data
project (which can be used as a template for the back-end project you create
with Developer Studio) and JSP/.NET versions of a front-end UI for the MDEX
engine . This is the directory to which the
ENDECA_REFERENCE_DIR variable is set. Note that this
directory is available only if you installed the Reference Implementation
feature.
