Semantic Web Company PoolParty - Thesaurus Manager Upgrade PPT 3.0.2 - 3.1.0 (Windows) Files Available in Upgrade Package (PP-3.0.2.zip) openrdf-sesame-2.6.3-onejar.jar PoolParty-3.1.0.war punkt-commons-bindableLRM-1.1.jar punkt-commons-openrdfutils-api-1.1.jar punkt-commons-openrdfutils-rio-1.1.jar punkt-commons-vocabulary-1.1.jar ROOT.war README.Windows.txt NB: 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 3.0.0 and you want to end up at 3.0.2, you must perform the upgrade to 3.0.1 and then to 3.0.2. Upgrade Procedure To upgrade your PoolParty installation, follow the steps described below. Before you upgrade, make sure you stopped your PoolParty server and that you have a working backup of your existing installation. These instructions assume you are upgrading a PoolParty default installation for Windows with Apache Tomcat installed at C:/Programs/Apache Software Foundation/Tomcat 6.0/ and PoolParty's data-files residing at C:/Users/poolparty/PoolParty/. It is recommended to delete the contents of PoolParty's working directory (but not the working directory itself!) whenever you upgrade PoolParty. You can find the working directory under C:/Programs/Apache Software Foundation/Tomcat 6.0/work/. STEP 1: Replace Tomcat libraries Remove the following libs from your tomcat libs directory (C:/Programs/Apache Software Foundation/Tomcat 6.0/libs): punkt-commons-bindableLRM-1.0.jar punkt-commons-openrdfutils-api-1.0.jar sesame-onejar-2.3.1.jar © 2012, Semantic Web Company (SWC) 2 Add the following libs from the update package to your libs directory: openrdf-sesame-2.6.3-onejar.jar punkt-commons-bindableLRM-1.1.jar punkt-commons-openrdfutils-api-1.1.jar punkt-commons-openrdfutils-rio-1.1.jar Add the punkt-commons-vocabulary-1.1.jar only if a punkt-commons-vocabulary-1.0.jar has already been available in your libs directory. In this case you must also remove the punkt-commons-vocabulary-1.0.jar. STEP 2: Replace the Tomcat webapps Replace the following webapps from your tomcat webapps directory (C:/Programs/Apache Software Foundation/Tomcat 6.0/webapps) with the ones in the update package and remove the respective folders: PoolParty.war ROOT.war STEP 3: Adapt your User Configuration Add the 'PoolPartySuperAdmin' and the 'WikiEditor' role to the tomcat-user.xml file and assign the 'PoolPartySuperAdmin' role to at least one user. The file can be found here: C:/Programs/Apache Software Foundation/Tomcat 6.0/conf <tomcat-users> <role rolename="Public"/> <role rolename="manager-gui"/> <role rolename="manager"/> <role rolename="PoolPartyUser"/> <role rolename="PoolPartyAdmin"/> <role rolename="PoolPartySuperAdmin"/> <role rolename="WikiEditor"/> <role rolename="SolrServiceUser"/> <user username="admin" password="md354EY7" roles="Public,PoolPartySuperAdmin,PoolPartyUser,PoolPartyAdmin,manager,mana ger-gui"/> <user username="solr" password="WDZa6kpET4hykaZu" roles="SolrServiceUser"/> </tomcat-users> © 2012, Semantic Web Company (SWC) 3 STEP 3: Adapt your Server Configuration Add readonly="false" to your UserDatabase definition in the server.xml file. The file can be found here: C:/Programs/Apache Software Foundation/Tomcat 6.0/conf <Resource name="UserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/tomcat-users.xml" readonly="false"/> STEP 4: Adapt your ConfigPath Setup Add the following code to your ConfigPathSetup.xml file. The file can be found in the config directory of your data directory (default, C:\Users\poolparty\PoolParty\data) <children> <backupable>false</backupable> <clearOnProjectDelete>false</clearOnProjectDelete> <id>projectuploads</id> <isRoot>false</isRoot> <path>C:/Users/poolparty/PoolParty/data/fileuploadRoot/projects</path> </children> You have to add the code as a child in the 'fileuploadroot' node. <children> <backupable>true</backupable> <clearOnProjectDelete>true</clearOnProjectDelete> <id>fileuploadroot</id> <isRoot>false</isRoot> <path>C:/Users/poolparty/PoolParty/data/fileuploadRoot</path> <children> <backupable>false</backupable> <clearOnProjectDelete>false</clearOnProjectDelete> <id>projectuploads</id> <isRoot>false</isRoot> <path>C:/Users/poolparty/PoolParty/data/fileuploadRoot/projects</path> </children> </children> © 2012, Semantic Web Company (SWC) 4 STEP 5: Remove the following properties from your server configuration file (SesameSetup.xml). The file can be found in the config directory of your data directory (default, C:\Users\poolparty\PoolParty\data) … <googleMapsKey>...</googleMapsKey> … <useDCTOnly>...</useDCTOnly> STEP 6: Update to the new solr schema Replace the solr schema files with the ones in the solr.tgz archive from the update package. The solr files can be found in the following directory: C:\Users\poolparty\PoolParty\data\solr\ppx\conf You should refresh your extraction models after updating the solr schema. STEP 7: Start the PoolParty server Run Post Update Scripts After you login into PoolParty for the first time after the update, you have to run the following updates scripts: http://<your-serverurl>/PoolParty/templates/dialogs/admin/TopConceptOfMaker.jsp Adds all skos:topConceptOf relations to Top Concepts in your projects. http://<your-serverurl>/PoolParty/templates/dialogs/admin/DeprecatedMigrator.jsp Changes all owl:depreatedProperties properties to owl2:deprecated properties. http://<your-serverurl>/PoolParty/templates/dialogs/admin/DCTermsMigrator.jsp Changes all metadata in your projects to DCterms. © 2012, Semantic Web Company (SWC) 5
© Copyright 2026 Paperzz