System Configuration

Polypheny offers a streamlined system, facilitating rapid setups by minimizing administrative overhead.

System Requirements

Ensure optimal operation of Polypheny by adhering to the following minimum system requirements:

Ports

Polypheny primarily utilizes the following ports for its operations:

All ports and additional system capabilities can be configured centrally.

Configuration File

Deployments of Polypheny are managed through a configuration file, formatted in HOCON and parsed internally using GSON.

Polypheny maintains all configuration data as part of the server deployment. Upon initial deployment, Polypheny autonomously generates a new configuration file (default: polypheny.conf) within ${POLYPHENY_HOME}/config/. Configuration alterations can be implemented at runtime via the Web UI, SQL, or directly within the configuration file prior to launching Polypheny.

Below is a sample configuration:

"runtime/webuiServerPort"=7659

"docker/defaultContainerRegistry"="docker.registry.io"

"runtime/dockerInstances" {
    dockerConfig01 {
        alias=localhost
        communicationPort="7001"
        handshakePort="7002"
        host=localhost
        id="25"
        proxyPort="7003"
        registry=""
    }
}

Data Folder

Polypheny utilizes the local file system for storage, defaulting to a specialized folder named .polypheny within the executing user’s home directory. This location can be modified by defining a system environment variable, POLYPHENY_HOME, to indicate the preferred location before initiating Polypheny.

Utilizing systemd on Linux Systems

For initiating and autonomously operating Polypheny on Linux systems, utilizing systemd is recommended. Establish a systemd service by creating a polypheny.service Unit-File within /etc/systemd/system.

[Unit]
Description=Polypheny-DB - A self-adaptive Polystore providing cost- and workload-aware access to heterogeneous data
After=multi-user.target

[Service]
Environment=POLYPHENY_HOME=/path/to/data/
ExecStart=/opt/polypheny/bin/Polypheny -daemon
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process

Upon file creation, reload the configuration:

systemctl daemon-reload polypheny.service

Subsequently, initiate the service:

systemctl start polypheny.service

Previous

Docker Integration

Next

Different Data Sources