[xwiki-users] Migrating XE from 2.4.3 to 2.7.1 and 3.0
Hi XWiki Team, Sorry if this is a recurring thread, but can't find more details on it. I'm using XE 2.4.30451 in production enviromnent on my company, and due to the numerous new functionalities of the new XWiki versions, I'm planning to migrate to 2.7.1, and after to 3.0. My question is: can I upgrade it as easy as just replacing the entire old war file with the new one (of course, with the tunings I've made on it, such as WYSIWYG macros, footnotes etc, setting the schema migration flag on xwiki.cfg? Won't I lose any of my documents, pages, attachments, comments etc at all? Of course I'll test it first, outside the production, but I would like to gather as much information I can to plan the entire migration process. We have a very large set of pages already on the wiki, and I wouldn't like to face big problems :-) Thanks in advance, Ramon Gomes Brandão
On 03/11/2011 08:03 PM, Ramon Gomes Brandão - SERINT wrote:
Hi XWiki Team,
Sorry if this is a recurring thread, but can't find more details on it. I'm using XE 2.4.30451 in production enviromnent on my company, and due to the numerous new functionalities of the new XWiki versions, I'm planning to migrate to 2.7.1, and after to 3.0.
My question is: can I upgrade it as easy as just replacing the entire old war file with the new one (of course, with the tunings I've made on it, such as WYSIWYG macros, footnotes etc, setting the schema migration flag on xwiki.cfg? Won't I lose any of my documents, pages, attachments, comments etc at all? Of course I'll test it first, outside the production, but I would like to gather as much information I can to plan the entire migration process. We have a very large set of pages already on the wiki, and I wouldn't like to face big problems :-)
Normally, yes. All the documents are in the database, so all that's important in the war is: - the xwiki.cfg and xwiki.properties configuration files - the database connector jar - any other jars you added, or files you manually changed Then you should import some of the documents from the new XAR, since many features come inside wiki pages. This is a bit more difficult, since you don't want to override changed configuration documents (like XWikiAdminGroup or XWikiPreferences), or documents you have changed (like Main.WebHome or Panels.QuickLinks). What can break things is changed APIs or behavior changes caused by bugfixing (which means that some code was exploiting a bug). For example, you might get deprecation warnings in the server logs. If you properly upgrade the entire war, and you import the new xar, there should be no headaches. More detailed instructions at: http://platform.xwiki.org/xwiki/bin/AdminGuide/Installation#HUpgradinganXWik... -- Sergiu Dumitriu http://purl.org/net/sergiu/
On 03/11/2011 11:56 AM, Sergiu Dumitriu wrote:
On 03/11/2011 08:03 PM, Ramon Gomes Brandão - SERINT wrote:
Hi XWiki Team,
Sorry if this is a recurring thread, but can't find more details on it. I'm using XE 2.4.30451 in production enviromnent on my company, and due to the numerous new functionalities of the new XWiki versions, I'm planning to migrate to 2.7.1, and after to 3.0.
My question is: can I upgrade it as easy as just replacing the entire old war file with the new one (of course, with the tunings I've made on it, such as WYSIWYG macros, footnotes etc, setting the schema migration flag on xwiki.cfg? Won't I lose any of my documents, pages, attachments, comments etc at all? Of course I'll test it first, outside the production, but I would like to gather as much information I can to plan the entire migration process. We have a very large set of pages already on the wiki, and I wouldn't like to face big problems :-)
Normally, yes. All the documents are in the database, so all that's important in the war is: - the xwiki.cfg and xwiki.properties configuration files - the database connector jar - any other jars you added, or files you manually changed
Then you should import some of the documents from the new XAR, since many features come inside wiki pages. This is a bit more difficult, since you don't want to override changed configuration documents (like XWikiAdminGroup or XWikiPreferences), or documents you have changed (like Main.WebHome or Panels.QuickLinks).
If I do not import some documents (like XWikiAdminGroup or XWikiPreferences), could I be missing out on changes that are contained in the newer versions of those documents?
What can break things is changed APIs or behavior changes caused by bugfixing (which means that some code was exploiting a bug). For example, you might get deprecation warnings in the server logs. If you properly upgrade the entire war, and you import the new xar, there should be no headaches.
More detailed instructions at:
http://platform.xwiki.org/xwiki/bin/AdminGuide/Installation#HUpgradinganXWik...
On 03/11/2011 11:41 PM, Dennis Rasey wrote:
On 03/11/2011 11:56 AM, Sergiu Dumitriu wrote:
On 03/11/2011 08:03 PM, Ramon Gomes Brandão - SERINT wrote:
Hi XWiki Team,
Sorry if this is a recurring thread, but can't find more details on it. I'm using XE 2.4.30451 in production enviromnent on my company, and due to the numerous new functionalities of the new XWiki versions, I'm planning to migrate to 2.7.1, and after to 3.0.
My question is: can I upgrade it as easy as just replacing the entire old war file with the new one (of course, with the tunings I've made on it, such as WYSIWYG macros, footnotes etc, setting the schema migration flag on xwiki.cfg? Won't I lose any of my documents, pages, attachments, comments etc at all? Of course I'll test it first, outside the production, but I would like to gather as much information I can to plan the entire migration process. We have a very large set of pages already on the wiki, and I wouldn't like to face big problems :-)
Normally, yes. All the documents are in the database, so all that's important in the war is: - the xwiki.cfg and xwiki.properties configuration files - the database connector jar - any other jars you added, or files you manually changed
Then you should import some of the documents from the new XAR, since many features come inside wiki pages. This is a bit more difficult, since you don't want to override changed configuration documents (like XWikiAdminGroup or XWikiPreferences), or documents you have changed (like Main.WebHome or Panels.QuickLinks).
If I do not import some documents (like XWikiAdminGroup or XWikiPreferences), could I be missing out on changes that are contained in the newer versions of those documents?
XWikiAdminGroup no, since it's just a data container, the UI is generated by a sheet, XWiki.XWikiGroupSheet, which you should import. XWikiPreferences is a bit more problematic. It contains both data (the configuration) and metadata (the definition of the XWiki.XWikiPreferences class). The UI is again defined in a sheet, XWiki.AdminSheet, which you should import, so the improved administration (in 3.0) will be included, but some of the fields will be missing since they are defined in XWiki.XWikiPreferences itself. This is a wrong design in the software, but it will take some time to improve.
What can break things is changed APIs or behavior changes caused by bugfixing (which means that some code was exploiting a bug). For example, you might get deprecation warnings in the server logs. If you properly upgrade the entire war, and you import the new xar, there should be no headaches.
More detailed instructions at:
http://platform.xwiki.org/xwiki/bin/AdminGuide/Installation#HUpgradinganXWik...
-- Sergiu Dumitriu http://purl.org/net/sergiu/
participants (3)
-
Dennis Rasey -
Ramon Gomes Brandão - SERINT -
Sergiu Dumitriu