Skip to main content

    The poolparty.properties File

    Abstract

    The poolparty.properties File

    Find the poolparty.properties file in these paths:

    • Linux: <PPAppDir>/config

    • Windows: drive>:\<PPAppDir>\config\

    It allows to define basic parameters for the PoolParty setup.

    Setup of the PoolParty Solr or Elasticsearch Instance:

    index.type=SOLR
index.username=solr
index.password=poolparty
index.host=http://localhost:8983/solr

    Pattern for Date and Date & Time used in PoolParty:

    The settings for date and time you define here are used for display 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.

    date.format.pattern=dd.MM.yyyy
datetime.format.pattern=dd.MM.yyyy - HH:mm

    PoolParty URL Relevant Setting for the Linked Data Frontend and the Suggest API Method:

    (Default: http://localhost/PoolParty)

    ppt.url=http://localhost/PoolParty

    Enable Enhanced HTTP/HTTPS Resolution for the LD Frontend

    A parameter affects the LD frontend and enabling the enhanced HTTP/HTTPS resolution of resources for it.

    Add this parameter to the file:

    ld.frontend.http.https.conversion

    LOD Cache Used for All Linked Data Functionalities in PoolParty:

    (Default: http://lod.semantic-web.at/sparql)

    lod.cache.endpoint=http://lod.semantic-web.at/sparql

    Base URL for Custom Schemes / Ontologies, Projects and Users:

    This is the URI used per default when creating projects or custom schemes / ontologies.

    # base url for custom schemes
url.base.scheme=http://schema.yourdomain.com
# base url for Thesauri
url.base.vocabulary=http://vocabulary.yourdomain.com
# base url for Users
url.base.user=http://poolparty.local/user
# base url for graph namespaces (as of version 7.2.0)
url.base.context=url.base.scheme

    Note

    The key url.base.context is mandatory as of version 7.2.0.

    User Object Security Hash

    In order to have PoolParty correctly create security hashes for user objects, the following parameter has to be present in the file:

    #user security hash
hmac.secret=

    Optional Parameters

    The following parameters can be set optionally in the poolperty.properties file:

    • poolparty.session.timeout

      This parameter allows to change the default timeout for a PoolParty session. (Default: 30min)

    • feed.url

      Defines the URL of a custom RSS feed to be used in PoolParty.

    • feed.entries

      Defines the number of RSS feed entries to be displayed. Default is 5.

    • feed.timeout

      Defines the timeout of feed fetch requests in ms. Default is 5000.

    • pwd.mode.secure

      This parameter allows to enable a stronger password policy for the PoolParty server. (Default: false)

    • pwd.min.length

      Using this parameter you can set the minimum required password length to an individual value. (Default: 8, optional)

    • 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. Default connection timeout is 2000 ms.

    • ldf.timeout.request.msec

      Sets the request timeout for generic HTTP requests to resolve labels in PoolParty's Linked Data Frontend in milliseconds. Default request timeout is 20000 ms.

    • security.password.expiration

      Sets the expiration interval for PoolParty user passwords, in days. (Default=0, optional) Details find here: Configure PoolParty to Use Stronger Passwords

    • security.password.log

      Reuse of passwords prevented by a history, the value sets the number of already used passwords to be excluded. (Default = 0, optional) Details find here: Configure PoolParty to Use Stronger Passwords

    • security.account.failed.attempts

      Sets the maximum number of stored failed login attempts.

    • security.account.lock

      This parameter specifies the number of failed login attempts, after which the account is locked and cannot be accessed even if the correct password is entered.

    • security.captcha.secret / security.captcha.site

      For enabling ReCaptchas for PoolParty, add these two keys to the poolparty.properties file. This makes sure that users have to check the 'I am not a robot' checkbox before they can log in. Even users with a locked account can then log into PoolParty (the lock will be removed after successful login). To register a new instance, follow this link: https://www.google.com/recaptcha/admin#list

    In this section: