18 Jan
2013
18 Jan
'13
8:06 p.m.
Currently i wonder if it's possible to convert a XEM Wiki Farm to a simple XE
instance and select one of the subwikis as the new base for the instance?
My naive try wasn't successful: Set db.virtual = 1, change db name in
hibernate.cfg.xml to one of the subwikis.
Currenty I'm thinking about the long migration way. Export all needed Spaces
and Documents from the target subwiki and disable the virtual mode. Then
drop all tables in the main database and start with a new fresh instance to
import the packaged pages.
First way will be fast, last a bit painful and error-prone.
Greetings
Jan
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Converting-XEM-to-XE-with-specific-subwik…
Sent from the XWiki- Users mailing list archive at Nabble.com.
18 Jan
18 Jan
11:01 p.m.
Hi, Jan,
If you have relatively small amount of data - standard export-import is the best solution,
IMHO.
If DB is huge - try one of the extensions for this
http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ExtensionSearch?sp…
As far as I understand XWiki, direct DB manipulations may bring inconsistency and data
loss, so better use standard means to keep data safe. hibernate.cfg.xml is not the only
place to change DB name: there are xwiki.cfg parameters also. But be sure, that some
application may stop working in this case. E.g. as far as I definitly know: problems were
found with DB prefix XWIKI-8672 and some Admin Tools. So, better use standard name for
the DB, or check everything and tell us if any problem found :-)
Probably, renaming sub-wiki DB to 'xwiki' will help. But I'm not sure. Never
tried this.
I just wonder: WHY XEM -> XE migration is necessary? From user point of view, subwiki
is completely independent wiki and (almost) has no differences form XE. Moreover, XEM is
much more flexible in building infrastracture, even with a small amount of data.
As the example: it was one wiki with all customers, projects and internal information
inside divided by spaces. It was quite difficult to manage this, especially access rights
for some business processes logic. Everything was moved to XEM. Now there are 30+ subwikis
(two of them are public wikis), 100+ users on board and no problems for further growth
:-)
As for me, I'm nearly always prefer XEM. It is especially useful for all kind of
experiments :-)
Пятница, 18 января 2013, 11:06 -08:00 от Jan-Philip Loos <maxdaten(a)gmail.com>om>:
Currently i wonder if it's possible to convert a
XEM Wiki Farm to a simple XE
instance and select one of the subwikis as the new base for the instance?
My naive try wasn't successful: Set db.virtual = 1, change db name in
hibernate.cfg.xml to one of the subwikis.
Currenty I'm thinking about the long migration way. Export all needed Spaces
and Documents from the target subwiki and disable the virtual mode. Then
drop all tables in the main database and start with a new fresh instance to
import the packaged pages.
First way will be fast, last a bit painful and error-prone.
Greetings
Jan
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Converting-XEM-to-XE-with-specific-subwik…
Sent from the XWiki- Users mailing list archive at Nabble.com.
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Kind regards,
Dmitry
11:54 p.m.
Hi Dmitry,
our DB is not really huge. It was enough to rise the mysql package size to
64M ;)
Renaming the sub-wiki to "xwiki" didn't worked for me. I've got this
StackOverflow:
java.lang.StackOverflowError: null
at java.util.regex.Pattern$Slice.match(Pattern.java:3496)
~[na:1.6.0_18]
at java.util.regex.Pattern$Start.match(Pattern.java:3072)
~[na:1.6.0_18]
at java.util.regex.Matcher.search(Matcher.java:1116) ~[na:1.6.0_18]
at java.util.regex.Matcher.find(Matcher.java:552) ~[na:1.6.0_18]
at java.util.regex.Matcher.replaceAll(Matcher.java:819)
~[na:1.6.0_18]
at java.lang.String.replace(String.java:2219) ~[na:1.6.0_18]
at
org.xwiki.model.internal.reference.DefaultStringEntityReferenceSerializer.serializeEntityReference(DefaultStringEntityReferenceSerializer.java:65)
~[xwiki-platform-model-4.4.jar:na]
at
org.xwiki.model.internal.reference.AbstractStringEntityReferenceSerializer.serialize(AbstractStringEntityReferenceSerializer.java:44)
~[xwiki-platform-model-4.4.jar:na]
at
org.xwiki.model.internal.reference.AbstractStringEntityReferenceSerializer.serialize(AbstractStringEntityReferenceSerializer.java:32)
~[xwiki-platform-model-4.4.jar:na]
at
com.xpn.xwiki.user.impl.xwiki.XWikiRightServiceImpl.checkRight(XWikiRightServiceImpl.java:326)
~[xwiki-platform-legacy-oldcore-4.4.jar:na]
at
com.xpn.xwiki.user.impl.xwiki.XWikiRightServiceImpl.checkRight(XWikiRightServiceImpl.java:442)
~[xwiki-platform-legacy-oldcore-4.4.jar:na]
I figured it out that the XWiki.XWikiAllGroup caused the problem. Maybe some
rights or users from the main wiki, i'm not sure about that.
But yes, XEM is nice to manage multiple wikis, and our project will benefit
of XEM. But we have some serve problems with XEM: see this thread:
http://xwiki.475771.n2.nabble.com/severe-trouble-with-web-crawlers-tp744216…
Currently im working with partial space exports / imports. But its hard to
get only the pages which not leave the xwiki in a unrecoverable state (with
the exception).
Greetings
Jan
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Converting-XEM-to-XE-with-specific-subwik…
Sent from the XWiki- Users mailing list archive at Nabble.com.
4312
days inactive
4312
days old
2 comments
2 participants
participants (2)
-
Haru -
Jan-Philip Loos