Closed GoogleCodeExporter closed 9 years ago
Original comment by jrivard
on 4 Sep 2012 at 5:28
Has an answer been furnished to this request?
Original comment by steve.pa...@gmail.com
on 26 Sep 2012 at 11:40
The short version:
* backup the internal database and PwmConfiguration.xml and any custom files
* deploy the war
* put back the internal database and PwmConfiguration.xml and any custom files
The long version still needs to be documented properly.
Original comment by menno.pi...@gmail.com
on 26 Sep 2012 at 12:05
Upgrade instructions have been added to the development documentation; need to
be added to the published version, though.
Upgrading
To upgrade PWM on Apache Tomcat, the following steps need to be performed:
Stop the PWM application or entire application server;
Make a backup of the file WEB-INF/PwmConfiguration.xml.
Make a backup of the folder WEB-INF/pwmDB.
Undeploy the old war file by removing both the war file and the extracted directory.
Deploy the new war file.
Clean the work and temp directories of the Tomcat application server.
If the application server is stopped, start it to make sure it will expand the war file; if Tomcat is running it will automatically do so.
Restore WEB-INF/pwmDB
Restore WEB-INF/PwmConfiguration.xml.
Remark: it is possible to place the pwmDB outside of the web application. In
that case restoration of the pwmDB can be skipped. A backup should nevertheless
be made, in case a roll back to the previous version is required, or something
goes wrong.
Original comment by menno.pi...@gmail.com
on 26 Sep 2012 at 12:38
Original comment by menno.pi...@gmail.com
on 26 Sep 2012 at 12:39
Original issue reported on code.google.com by
jeverl...@bshp.edu
on 29 Aug 2012 at 4:16