...
The downloaded Confluence package is powered by Tomcat. You can specify Tomcat use a specific java directory by creating a setenv modifying the Confluence setenv.sh file as described at Running Tomcat with a specific JRE version.
...
| Code Block | ||
|---|---|---|
| ||
kill #### where #### is the process id |
Future Upgrade Notes
s part of planning for future upgrades listed here are the key files to keep in mind,
- \bin\setevn.sh
- \bin\shutdown.sh
- \bin\startup.sh
- \bin\conf\server.xml
- confluence\WEB-INF\classes\confluence-init.properties
- opt\confluence-3.2.1_01-std\postgresql-8.4-701.jdbc4.jar - add
- opt\confluence-3.2.1_01-std\postgresql-8.4-701.jdbc3.jar - remove
The package dependencies change between confluence versions. You should check if there are differences. For example look at the difference between 3.1 and 3.2 ,
confluence-3.1
- libice-dev - nolonger used
- libsm-dev - nolonger used
- libx11-dev - used
- libxext-dev - nolonger used
- libxp-dev - nolonger used
- libxt-dev - nolonger used
- libxtst-dev - used
confluence-3.2
- libx11-6 - new
- libx11-dev - carry over
- libxt6 - new
- libxt6-dbg - new
- libxext6 -new
- libxtst-dev - carry over
- libxtst6 - new
- xlibs-dbg - new
- xlibs-dev - new
Also, keep a page listing any plugins you install. Upgrades generally do not require you to reinstall the plugins but they might be deprecated so make that after the upgrade is done, login as Administrator on Confluence and ensure plug-ins are up to date.