Upgrade PP 5.2 - 5.3 (Linux)
Upgrade PP 5.2 - 5.3 (Linux)
To upgrade your PoolParty installation, follow the steps described below.
Note
In order to upgrade to a specific PoolParty release, you must ensure that your current PoolParty installation is at the immediate previous release. In other words, you cannot skip any intermediate releases when upgrading PoolParty. For example, if your PoolParty installation is at version 5.1 and you want to end up at 5.3, you must perform the upgrade to 5.2 and then to 5.3. PoolParty's automated upgrade process for GNU/Linux hosts makes this process a breeze.
Note that with release 5.3 a 64bit build of the Sun/Oracle Java 7 or Java 8 Runtime Environment is required for running a PoolParty server.
These instructions assume you are upgrading a PoolParty default installation for GNU/Linux with PoolParty installed at /opt/poolparty, unless otherwise stated.
Upgrade Procedure
STEP 1: Stop your PoolParty server
Before you upgrade, make sure that you have a working backup of your existing installation.
STEP 2: Run the update script
Extract the archive containing the PoolParty Upgrade files on your system, change to the resulting directory, and run ./pp-update-5.3.1.bash from there.
Note
If you chose to install PoolParty at another location than the default (/opt/poolparty), supply the full path to your PoolParty installation directory as the first argument to the script, like, e. g., so: ./pp-update-5.3.1.bash /usr/local/poolparty.
If you are running your PPT instance under another user or group (default: poolparty) supply the owner and group as the second and third argument to the script e.g. ./pp-update-5.3.1.bash installpath owner group.
Additionally it is now possible to run the update script with different PoolParty installation and data directories, for this to work you need to specify the full path to your PoolParty data directory as a fourth argument to the script e.g. ./pp-update-5.3.1-bash installpath owner group datapath
Note
This upgrade includes an upgrade of Apache Tomcat to version 7.0.68. The old tomcat folder will be moved to backup.tomcat in your PoolParty installation folder.
If you have a custom configuration in your Tomcat server.xml or tomcat-users.xml configuration files, we try to migrate your configuration to the new Tomcat installation. It is recommended to double check the configuration before you start the server.
If you have configured a remote graph database (remoteRepository.spring.xml) we try to migrate your configuration to poolparty.properties. It is recommended to double check the configuration before you start the server.
STEP 3: Start your PoolParty Server again
Post migration tasks
You have to clear your browser cache after the upgrade as changes to css and java script used in the PoolParty UI have been done.
After you login into PoolParty for the first time after the update, you have to run the PoolParty migration script:
http://<your-serverurl>/PoolParty/!/migrate/upgrade
The script lists all updates that will be done. The migration is triggered clicking the Start Migration button. A progress bar and an info box show the progress and status of the migration. When the process has been finished an overview of the migration steps per project is provided.
Changes to to the configuration of the PoolParty extraction model have been done. You have to recalculate all extraction models after the upgrade.
Note
You need to have the Superadministrator role assigned to be able to run those scripts.
This upgrade includes an upgrade of Apache Tomcat to version 7.0.68. The old tomcat folder will be moved to backup.tomcat in your PoolParty installation folder. You can safely remove it after verifying that the upgrade went fine.