Changes for page Upgrading

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • XWiki.XWikiComments[6]

Details

Page properties

Content

...	...	@@ -2,6 +2,14 @@
2	2
3	3	{{toc/}}
4	4
	5	+= Upgrading the standard distribution =
	6	+
	7	+If you've installed the standard distribution (##exe##, ##zip## or ##jar## distribution) and you wish to upgrade it, the simplest is to download the new version and install it as you did the first time. Just make sure you don't install the new version over the old one (both installations need to exist).
	8	+
	9	+Then copy [[the configuration files and the permanent directory>>AdminGuide.Backup]] from the old installation to the new one. Ideally you should not copy over the configuration files exactly since the new version could have added new configuration options and thus ideally you should do a merge instead of a pure copy. Another strategy is to use the new configuration files, not copy over the old configuration files and instead manually edit the new configuration to make the same changes as you have may done before (If you've never touched the configuration files then there's nothing to do obviously!).
	10	+
	11	+{{include reference="UpgradeDatabase"/}}
	12	+
5	5	= Upgrading the webapp =
6	6
7	7	The general strategy is to [[download the WAR distribution>>xwiki:Main.Download]] and to replace your current installed WAR. Make sure you don't copy on top since this could leave some old files around which would make XWiki fail (like if old JARs are lying around in ##WEB-INF/lib##).
...	...	@@ -10,29 +10,8 @@
10	10
11	11	Some additional operations may be required for upgrading and you must check the [[release notes>>xwiki:ReleaseNotes.WebHome]] for all the versions from the version you're upgrading from up to the new version you're installing. It's also possible that new features are available and that some configuration files need to be modified. If this is the case then it'll be specified in the release notes.
12	12
13		-Note that the database schema is automatically upgraded when needed. All you need to do is to ensure your ##xwiki.cfg## file is correctly configured to perform the migration. Here's a relevant excerpt from the ##xwiki.cfg## file:
	21	+{{include reference="UpgradeDatabase"/}}
14	14
15		-{{code language="none"}}
16		-#-# Whether migrations are enabled or not. Should be enabled when upgrading, but for a better startup time it is better to
17		-#-# disable them in production.
18		-xwiki.store.migration=1
19		-
20		-#-# Whether to exit after migration. Useful when a server should handle migrations for a large database, without going
21		-#-# live afterwards.
22		-# xwiki.store.migration.exitAfterEnd=0
23		-
24		-#-# Indicate the list of databases to migrate.
25		-#-# to upgrade all wikis database set xwiki.store.migration.databases=all
26		-#-# to upgrade just some wikis databases set xwiki.store.migration.databases=xwiki,wiki1,wiki2
27		-#-# Note: the main wiki is always migrated whatever the configuration.
28		-# xwiki.store.migration.databases=
29		-{{/code}}
30		-
31		-{{warning}}
32		-From a failed migration the database tables **DATABASECHANGELOG** and **DATABASECHANGELOGLOCK** may be left over.
33		-Ensure that these tables are dropped before restarting a failed migration.
34		-{{/warning}}
35		-
36	36	== Invalid Extensions ==
37	37
38	38	Also note that when you upgrade, some extensions that were previously valid may become invalid (for example they may have been renamed, removed or have versions that do not match the version of the WAR you've installed as is the case with the example below). In this case you'll see in the console messages such as:

XWiki.XWikiComments[6]

Date

...	...	@@ -1,1 +1,1 @@
1		-2014-08-29 10:05:13.414
	1	+2014-08-29 10:05:13.0