The following list gives a brief overview of the directory structure in a PoolParty on Windows, following the default installation in the installation guide for Windows.
We will only list files and folders relevant for the installation or configuration of PoolParty
Access configuration file for the PoolParty APIs.
Definition of pathnames used for saving data produced by PoolParty (e.g. repositories, files etc.) at runtime.
Includes all license files of your PoolParty components.
Configuration of tomcat server specific startup parameters for PoolParty.
Main configuration file for the PoolParty Semantic Suite.
Configuration file for PPT specific settings.
Graph database that can be connected to your PoolParty server as Remote Repository. See also How to Set Up a Remote Graph Database Configuration
This directory includes all project exports stored on the server. Exports are stored in one folder per project. The folder name is created from the projects UUID.
Files uploaded by the PoolParty import/export function. Uploads are stored in one folder per project. The folder name is created from the projects UUID.
This directory holds all additional configuration files and files created by PPT (e.g. namespace.ttln -> Namespaces used in PoolParty at runtime. You can also place templates used for custom reports here.
This includes the Sesamegraph database used by PPT and all repositories created by PPT.
The PoolParty snapshot function stores snapshots of all projects as defined in this directory.
Includes all Solr configuration and cores used by the PoolParty Semantic Suite.
- Includes the built in Apache Solr 5 server.
C:\Programs\Apache Software Foundation\Tomcat 7.0\
Here you can set the user and password for the Tomcat Manager.
Changing the Port Used by the PoolParty Server
Logging configuration for the Tomcat and the PoolParty server.
Here's where you look for log-files related to Apache Tomcat and PoolParty.
The PoolParty Extractor web application.
The PoolParty Thesaurus Server web application.
The web application handling the LD Frontend.