- PoolParty Semantic Suite Documentation
- Administrator Guide
- PoolParty Installation
- Preparing the PoolParty Installation & Upgrade
- Upgrading PoolParty 2025 Release 1 to PoolParty 2025 Release 2
Upgrading PoolParty 2025 Release 1 to PoolParty 2025 Release 2
16/09/2025
Note
The migration and upgrade process are the same as for PoolParty 2025 Release 1 (9.5). It is assumed that you are using Elasticsearch as the index as Solr support has been discontinued from PoolParty 2024 Release 2 (9.4.x).
Unpack the
{compressed_PoolParty_file_name}.tar.gz
file. Unpacking this file will create a folder calledENV_PATH_POOLPARTY_INSTALLATION/poolparty_setup
containing all required files.tar -xf PoolParty_Integrator_9.5.0.tar.gz
Check and when required edit the variables in the
.env
file located in the/poolparty_setup/
directory.ENV_PATH_POOLPARTY_INSTALLATION="/opt/poolparty" ENV_PATH_POOLPARTY_DATA="/opt/poolparty/data" ENV_USER="poolparty" ENV_GROUP="poolparty" ENV_URL_POOLPARTY_BASE_SCHEME="<scheme.server.com>" ENV_URL_POOLPARTY_BASE_VOCABULARY="<vocabulary.server.com>" ENV_URL_POOLPARTY_BASE_CONTEXT="<data.server.com>" ENV_URL_POOLPARTY_BASE_USER="<resource.server.com>/user" ENV_PORT_POOLPARTY_TOMCAT="8081" ENV_URL_KEYCLOAK="<server.com>:8181/auth"
Then go to the
ENV_PATH_POOLPARTY_INSTALLATION/poolparty_setup/
directory and start the upgrade by running the./setup.sh
script.
When updating a PoolParty instance it is sufficient to set the
ENV_PATH_POOLPARTY_INSTALLATION
variable since the other mandatory variables set in the.env
file should be correct. When all these variables are correctly set the installation will complete without any interaction from you.Note
If this file contains an error or a typo for instance, the installation will be aborted. To see why the installation process has been aborted, open the log file where you find all details required to make any corrections to the respective entry in the
.env
file.
After successful completion of the upgrade process you will see all the credentials printed on the screen:
/opt/poolparty/poolparty_setup$ ./setup.sh [ Note ] PoolParty installation script for version 9.5.0 has started. [ Note ] The upgrade process has been initialized. [ Note ] The Tomcat update has been successfully completed. [ Note ] The Elasticsearch update has been successfully completed. [ Note ] The Keycloak update has been successfully completed. [ Note ] PoolParty was updated from 9.4.3 to 9.5.0 [ Note ] Running PoolParty with root user privileges is not recommended.
The installation logs are located in the following directory:
ENV_PATH_POOLPARTY_INSTALLATION/poolparty_setup/pp-installation.log
.
Normally, you will not have to provide the license when updating your PoolParty instance. If however you are granted a new license file, then add it to the license directory located at ENV_PATH_POOLPARTY_INSTALLATION/config/licenses
.
Start the PoolParty by executing the
start
command from theENV_PATH_POOLPARTY_INSTALLATION/bin
folder../poolparty start
Check that the application is up.
tail -f /opt/poolparty/tomcat/logs/catalina.out
The following should appear at the end of the log:
INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [121433] milliseconds
If everything is fine, you can delete the PoolParty installation files from the
poolparty_setup
directory and the*.tar
installer.Tip
It is recommendable to keep a copy of the
.env
file for reference.