- Graphwise Documentation - General
- How to Install & Manage Graphwise Components
- PoolParty Configuration
- PoolParty Configuration Properties
PoolParty Configuration Properties
20/10/2025
This guide summarizes all configuration properties for your PoolParty instance, including settings for security, connection details, and external service integrations.
PoolParty uses a unified mechanism to load and apply configuration values consistently across all layers of the application—from early Tomcat startup to Spring-managed components. This ensures predictable behavior regardless of where the setting is consumed.
The configuration system resolves properties by checking a standard set of locations. The first source found (highest precedence) overrides any values found in subsequent sources. PoolParty resolves properties according to the following precedence:
Java System Properties: Passed directly to the Java Virtual Machine (JVM). Useful for dynamic or one-off changes.
Example:
-Dpoolparty.some.setting=valueEnvironment Variables: Useful for containerized deployments (e.g., Docker, Kubernetes). The last section on this page explains the rules for setting PoolParty properties as environment variables.
Example:
POOLPARTY_BASE_URI=https://new.server.comThe
poolparty.propertiesfile: The traditional location for custom PoolParty settings. The default location of thepoolparty.propertiesfile is specified inpoolparty.configRoot. Its default is${poolparty.home}/config.Static defaults: Default values provided in static property files packaged on the classpath:
application.properties: Contains internal metadata (e.g., version, build timestamp).poolparty-default.properties: Contains various default values for standard properties.
Note
If PoolParty was deployed using Helm Charts then properties can be configured in the Configurations section in the values.yaml file.
The settings you define here are used to display date and time in lists and tables throughout the interface. All other instances of date and date-time formats in PoolParty are by default formatted and stored according to the UTC standard.
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Format in which dates are displayed. |
| Optional |
| Format in which date & time is displayed. |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Encryption password for encrypted passwords stored in the system repository. | Mandatory | |
| Encryption salt. | Mandatory | |
| Encryption key strength. | Mandatory |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| The URL of the GraphDB instance or a comma-delimited list of GraphDB cluster nodes. | Mandatory | |
| Basic authentication username. | Optional | |
| Basic authentication password. | Optional | |
| Authorization header (alternative to basic authentication). | Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| The Keycloak auth URL. | Mandatory | |
| Realm for the admin client. |
| Optional |
| Client ID for the admin client. | Mandatory | |
| Username for the admin client. | Optional (alternative to | |
| Password for the admin client. | Optional (alternative to | |
| Client secret for the admin client (alternative to username/password). | Optional (Alternative to username/password) | |
| Realm for the login client. |
| Optional |
| Client ID for the login client. | Mandatory | |
| Client secret for the login client. | Mandatory | |
| Field that contains the principal (username). |
| Optional |
| Boolean value determining whether to enable basic authentication for login. |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| The type of index (currently only Elasticsearch is supported). | Mandatory | |
| URL of the index server. | Mandatory | |
| Username to access the index. | Optional | |
| Password to access the index. | Optional | |
| Path to keystore file (for SSL connections). | Optional | |
| Password for the keystore file (for SSL connections). | Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Address to bind to (binds to all network interfaces if set to |
| Optional |
| Port to listen to. |
| Optional |
| Defines the external (public) base URL that other services or clients should use when connecting to the PoolParty server. |
| Optional |
For more information, refer to CORS Configuration for PoolParty.
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| A comma-separated list of allowed CORS origins (may NOT contain | Optional | |
| A comma-separated list of allowed CORS origin patterns (may contain | Optional | |
| A comma-separated list of allowed CORS methods. |
| Optional |
| A comma-separated list of allowed CORS headers. |
| Optional |
| A comma-separated list of exposed CORS headers. | Optional | |
| Sets whether user credentials are supported with CORS. |
| Optional |
| Sets how long, in seconds, the response from a pre-flight request can be cached by clients. |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Set to enable external Spark or modify local Spark settings. | Optional | |
| Set the Spark memory to use per executor process (e.g., | Optional | |
| Set the external Spark driver core usage. Do not set higher than what your external Spark Cluster can provide. | Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Whether Spark authenticates its internal connections. |
| Optional |
| The secret key used for authentication. | Optional | |
| Overrides the location the Spark driver reads to load the secret. Requires | Optional | |
| Overrides the location the Spark executors read to load the secret. Requires | Optional | |
| Enable AES-based RPC encryption. |
| Optional |
| Cipher mode to use for AES-based RPC encryption. | Optional | |
| Version of AES-based RPC encryption to use (1 or 2). | Optional | |
| Enable local disk I/O encryption. Strongly recommended that RPC encryption be enabled when using this feature. |
| Optional |
| IO encryption key size in bits (128, 192, or 256). | Optional | |
| The algorithm to use when generating the IO encryption key. | Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Enables RPC SSL. |
| Optional |
| Sets the SSL protocol. |
| Optional |
| The password to the private key in the key store. | Optional | |
| Path to the key store file (absolute or relative). | Optional | |
| Password to the key store. | Optional | |
| Path to the trust store file (absolute or relative). | Optional | |
| Password for the trust store. | Optional | |
| Whether the trust store should be reloaded periodically. |
| Optional |
| The interval at which the trust store should be reloaded, in milliseconds. |
| Optional |
| A comma-separated list of ciphers supported by the JVM. If not set, the JRE's default cipher suite will be used. | Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| The location of the |
| Optional |
| The PoolParty home directory. Defaults to the distribution directory. Used to derive defaults for other directories. | Distribution directory | Optional |
| The PoolParty data directory. |
| Optional |
| The PoolParty logs directory. |
| Optional |
| A comma-separated list of applications to start. Available applications are thesaurus (includes LDF), graphsearch, and extractor. |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| PoolParty URL Relevant Setting for the Linked Data Frontend and the Suggest API Method |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| LOD cache used for all Linked Data functionalities in PoolParty. |
| Optional |
Property | Description | Default | Mandatory or Optional? |
|---|---|---|---|
| Base URL for custom schemes. |
| Optional |
| Base URL for thesauri. |
| Optional |
| Base URL for users. |
| Optional |
| Base URL for graph namespaces. |
| Optional |
The following parameters can be optionally set in the poolparty.properties file:
poolparty.session.timeout
This parameter allows you to change the default timeout of a PoolParty session. (Default: 30min)
ld.frontend.http.https.conversion
This parameter allows you to enable or disable the enhanced LD frontend HTTP/HTTPS resource resolving. (Default: true)
ldf.timeout.connect.msec
Sets the connection timeout for generic HTTP requests to resolve labels in PoolParty's Linked Data Frontend in milliseconds. The default connection timeout is 2000 ms.PoolParty's Linked Data Frontend
ldf.timeout.request.msec
Sets the request timeout for generic HTTP requests to resolve labels in PoolParty's Linked Data Frontend in milliseconds. The default request timeout is 20000 ms.PoolParty's Linked Data Frontend
poolparty.analytics.enabled
If set to
true, PoolParty may send anonymous data about the features used. The data sent complies with the privacy policy specified in your contract. This helps us improve our product. By default, the analytics is disabled on all on-premise installations.poolparty.analytics.siteid
ID of the site to where PoolParty uploads the analytics data. Will be provided by your Customer Success representative. Only relevant if
poolparty.analytics.enabledis set totrue.
Memory allocation for the Java Virtual Machine (JVM) can be configured in one of two ways:
Set the environment variable
PP_HEAP_SIZEto define the heap size directly.Provide the memory setting (e.g.,
-Xmx4g) using the environment variableJAVA_TOOL_OPTIONS.
From PoolParty 2022 Release 1 the following parameters are no longer used:
feed.url
Legacy parameter that defines the URL of a custom RSS feed to be used in PoolParty.
feed.entries
Legacy parameter that defines the number of RSS feed entries to be displayed.
feed.timeout
Legacy parameter that defines the timeout of feed fetch requests in ms.
From PoolParty 2025 Release 2 (9.6.1) the following optional parameters have been removed from the poolparty.properties file:
ppgs.max.title.length
The maximum number of characters in the
titleparameter in Web Service Method: Create Indexed Document and Web Service Method: Update or Create an Indexed Document. Default value was 1,250 characters.ppgs.max.text.length
The maximum number of characters in the
textparameter in Web Service Method: Create Indexed Document and Web Service Method: Update or Create an Indexed Document. The default character limit was 12,048 characters.
The configuration system supports the following property types:
Prefixed properties, such as
poolparty.base.uriNon-prefixed properties, such as
some.custom.setting
Important
To avoid ambiguity and ensure safe resolution, non-prefixed properties must follow a special convention when provided via environment variables.
When specifying environment variables, non-prefixed properties must be treated as if prefixed with _POOLPARTY.. This ensures that names like some.setting do not clash with unrelated environment variables. For example:
Property Name | Expected Environment Variable |
|---|---|
|
|
|
|
This unified configuration mechanism applies consistently across all components of the PoolParty application, including:
Tomcat Startup Code: For parsing XML definitions before Spring initialization.
Non-Spring Utility Classes and core services.
Spring-managed beans, components, and XML configuration.
This ensures predictable behavior regardless of the execution context.