Installation (XWiki.org)

1

#startfloatingbox()

2

*Contents*

#toc ("2" "3" "")

#endfloatingbox()

1 Installation

XWiki is a Java-based wiki and runs on a Servlet Container such as Tomcat, Jetty, JBoss, WebLogic, WebSphere, etc. It also uses a relational database to store its content. It can run on almost any database (HSQL, MySQL, etc) but XWiki and the database need to be setup correctly.

9

10

There are 2 solutions when installing XWiki:

11

12

* Use the [Standalone distribution>xwiki:Main.Download] which already packages a Servlet Container (Jetty) and a database (HSQL). This is the recommended option for first time XWiki users and for users who wish to quickly try out XWiki.

13

* Use the [WAR distribution>xwiki:Main.Download] and configure both your container and your database to work with it.

14

15

If you're instead upgrading an existing XWiki install check the [Upgrade instructions>#HUpgradinganXWikiInstallation] below.

16

17

#info("There's a [nice tutorial>http://agoncalves.developpez.com/tutoriels/xwiki/creer-un-site-associatif/] (in French) contributed by an XWiki user for getting started with XWiki with step by step instructions for installing it.")

18

19

Pick one of the following trails:

20

#toc("" "" "")

21

22

Once you've finished the installation check the other topics in the [Admin Guide>AdminGuide.WebHome] for configuring and [securing>Security] your wiki.

23

24

#info("If you want to make manual installation or need to migrate an existing XWiki installation, check the [Release Notes>xwiki:Main.ReleaseNotes].")

1.1 Prerequisites

You'll need to have Java 5 installed.

29

30

1.1 Installing the Standalone distribution

31

32

This is by far the easiest way to install XWiki. We are offering 3 packaging for ease of installation:

33

* A Windows exe. Simply execute it and follow the instructions

34

* A generic Installer that works on all platforms. It requires Java to be installed on your system. Simply double-click on it and follow the instructions.

35

* A zip version. Unzip it in any <tt>\[XWIKIHOME\]</tt> directory of your choice.

36

37

The Windows installer creates shortcuts to start and stop XWiki. If you've used the zip file or generic Installer, go to the directory where you've installed XWiki (~~\[XWIKIHOME\]~~) and run ~~start_xwiki.bat~~ in Windows or ~~start_xwiki.sh~~ on Unix. To stop it, run the ~~stop_xwiki.bat~~ script on Windows and ~~stop_xwiki.sh~~ on Unix.

38

39

Once XWiki is started point your browser to http://localhost:8080/xwiki/bin/view/Main/WebHome and the go to the [User's Guide>enterprise:UserGuide.WebHome] to learn how to use XWiki. To change the port, edit the start script and replace 8080 by the number you want.

40

41

#info("You can log in using the default Admin user (first letter is capitalized). The default password is 'admin' (lowercase).")

42

1.1 Installing the XWiki WAR manually

43

44

You'll need to perform 2 mandatory steps:

45

46

* Install and configure a Servlet Container

47

* Install and configure a relational database

48

49

#info("If your database is empty this will result in a minimal empty wiki installation. You may want to use the [Import/Export tool>AdminGuide.ImportExport] to import some pages in your wiki. We recommend that you import the [provided default XAR>xwiki:Main.Download]. If you're upgrading from an existing installation your database should already contain the pages you had before. If you're using the new XWiki 1.0 skin you might want to install the [Panels Application>code:Applications.PanelsApplication].")

50

51

#info("If you are installing in a linux/unix environment you have to setup the ~~xwiki.upload.tempdir~~ parameter as explained in the JIRA entry (http://jira.xwiki.org/jira/browse/XWIKI-530) *before* importing anything into XWiki.")

52

53

1.1.1 Install and configure a Servlet Container

54

55

XWiki will work with any Servlet Container. We're only listing instructions for a few containers but you can adapt these instructions for your favorite container.

56

57

* [Tomcat installation>AdminGuide.InstallationTomcat]

58

* [Jetty installation>AdminGuide.InstallationJetty]

59

* [GlassFish installation>AdminGuide.InstallationGlassFish]

60

* [WebSphere installation>AdminGuide.InstallationWebSphere]

61

* [JBoss Installation>AdminGuide.InstallationJBoss]

62

* [Oracle OC4J Installation>AdminGuide.InstallationOC4J]

63

64

You're now ready to install and configure your relational database.

65

66

1.1.1 Install and configure a Relational Database

67

68

XWiki can work with a lot of relational databases. We're only listed those that we have tested it on.

69

70

The general strategy is the following:

71

72

* Install your favorite RDBMS

73

* Create a xwiki database

74

* Create a user with all privileges on that xwiki database

75

* Copy your RDBMS Java drivers to the XWiki webapp's <tt>WEB-INF/lib</tt> directory

76

* Configure XWiki to use the created database. This involves modifying the <tt>WEB-INF/hibernate.cfg.xml</tt> file as is described in the tutorials for each database below. Also make sure that your <tt>xwiki.cfg</tt> file has an entry that points to your <tt>WEB-INF/hibernate.cfg.xml</tt> file (<tt>xwiki.store.hibernate.path=/WEB-INF/hibernate.cfg.xml</tt>) as otherwise your settings won't be used.

77

78

Install and configure the database you wish to use:

79

80

* [HSQL Installation>AdminGuide.InstallationHSQL]

81

* [MySQL Installation>AdminGuide.InstallationMySQL]

82

* [PostgreSQL Installation>AdminGuide.InstallationPostgreSQL]

83

* [Oracle Installation>AdminGuide.InstallationOracle]

84

* [DB2 Installation>AdminGuide.InstallationDB2]

85

* [Derby Installation>AdminGuide.InstallationDerby]

86

* [Microsoft SQL Server Installation>AdminGuide.InstallationMSSQL]

87

88

1.1.1 Concluding Step

89

90

At this stage you have finished configuration XWiki. If you start your database and container and point your browser to http://localhost:8080/xwiki/ you'll have a working, albeit minimal, wiki (without any page loaded). The next step is either to create new pages by hand or import the default Wiki that we are providing as a [XAR file>xwiki:Main.Download], by using the [Import feature>AdminGuide.ImportExport].

1.1.1 Tutorials

* [XWiki On Debian 4 (Etch) - Tomcat - MySQL > http://www.howtoforge.com/xwiki-tomcat-mysql-debian-etch]

95

96

1.1 Installing the eXo Enterprise WebOS integration WAR

97

98

#warning("The integration with eXo is still very experimental and the instructions below are not finalized yet. Proceed with caution!")

99

100

1.1.1 Install eXo WebOS

101

102

* Download the latest version of eXo Portal on http://forge.objectweb.org/projects/exoplatform/ (version 2.0-Alpha-2 or greater is required).

103

* Follow the eXo installation instructions located inside the Portal ZIP and try to login in the portal.

104

105

1.1.1 Install XWiki inside eXo

106

107

* Stop eXo Portal.

108

* Download the [latest XWiki eXo WAR>xwiki:Main.Download]. You'll need version 1.0-beta-6 or above.

109

* Create a directory ~~exo-tomcat/webapps/xwiki~~.

110

* Unzip the WAR in ~~exo-tomcat/webapps/xwiki~~ and rename the exploded directory to "xwiki".

111

* Move the ~~ehcache.jar~~ from ~~xwiki/WEB-INF/lib~~ to ~~exo-tomcat/common/lib~~ (There are some conflicts with it that both XWiki/eXo will need to fix in future versions).

112

* Remove all the eXo jars from ~~xwiki/WEB-INF/lib~~

113

* Configure XWiki's database as explained [above>#HInstallandconfigureaRelationalDatabase].

114

* Change in ~~xwiki.cfg~~: xwiki.exo=1 to xwiki.exo=0. TODO: Explain why this is required as it is very counter-intuitive!

115

* Restart eXo Portal.

116

* You can now either import XWiki as a Portlet inside the Portal as described below or access XWiki directly by using the usual URL.

117

* [Change the skin to use the XWiki 1.0 skin>AdminGuide.Skins#HChangingtheskin]. This skin is compatible with the Portlet mode and specifically with eXo WebOS.

118

* Import the [default wiki XAR>xwiki:Main.Download] or use your own XWiki database.

119

* Give the admin right to XWikiGuest

120

* To be continued...

121

122

1.1.1 Use XWiki inside the WebOS

123

124

Inside the WebOS, XWiki is seen as a Portlet and therefore must be imported in eXo through the PortletRegistry application. To do so you need to login as exoadmin / exo in eXo and go to the Administration desktop and use the PortletRegistry application. Click on the "Import Portlet Category" icon, you should now see XWiki in the list. You can now add the Portlet in your desktop page though the "Add Application" icon in the desktop dock.

125

126

1.1 Installing the Default Wiki XAR

127

128

The default wiki is a fully configured wiki that you can use as a starting point for creating your own wiki content. It provides the following:

* A Blog

* Photo albums

* A What's New page

* The [Panels Application>code:Applications.PanelsApplication]

133

* Search

134

* Administration page (Access rights, Group and users management, etc)

135

* ... and much more

136

137

*It comes configured with an "Admin" user (password is "admin" in lowercase). You'll need that username/password to log in once you've imported the default wiki.*

138

139

To install the XAR, use the [Import/Export tool>AdminGuide.ImportExport].

140

141

#warning("If you're upgrading an existing wiki be careful that the XAR import operation will replace the content of the existing pages of your wiki with the content of the XAR (New pages that you have created will not be modified). As a consequence it's critical that you [perform a backup>platform:AdminGuide.Backup] first.")

142

143

1.1 Upgrading an XWiki Installation

144

145

There are different parts of XWiki that you may want to upgrade:

146

147

* [XWiki Core>#HUpgradingXWikiCore]

148

* [Documents provided with the default XWiki XAR>#HUpgradingwikidocuments]

149

150

#info("If you're upgrading an XWiki 0.9 installation refer to [this guide>UpgradeXWiki09Installation].")

151

152

1.1.1 Upgrading XWiki Core

153

154

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). Before replacing your current WAR, make sure you back it up and more specifically that you copy the hibernate.cfg.xml and xwiki.cfg files which you'll need to copy in your newly installed WAR since they container your XWiki configuration. Make sure you also copy any plugins you may have added or any template files you may have modified.

155

156

Some additional operations may be required for upgrading and you must check the [release notes>xwiki:Main.ReleaseNotes] for all the versions from the version you're upgrading from up to the new version you're installing.

157

158

1.1.1 Upgrading wiki documents

159

160

You may want to upgrade to a newer version of the Default Wiki XAR in order to benefit from the latest changes. As mentioned above in the ["Installing the Default Wiki XAR" section>#HInstallingtheDefaultWikiXAR] you should be very careful and when doing the import make sure you selectively decide what pages you wish to import. More specifically the following pages should be imported with great care:

161

162

* XWiki.XWikiPreferences: This page contains the configuration of your wiki (it overrides the configuration defined in xwiki.cfg). If you import a new version of this page you'll loose any customization you may have made such as the skin to use, the rights for your wiki, etc.

163

* XWiki.WebPreferences, Main.WebPreferences, and all other spaces WebPreferences pages: Same as XWiki.XWikiPreferences but at the level of a space.

164

* XWiki.XWikiAllGroup (list of registered users) and XWiki.AdminGroup (list of Admins): If you have existing users and import a new version of these pages, you'll find that your users do not belong to these groups anymore and thus may not be able to edit pages, log in, etc. You'll need to add them again to the right groups.

165

* Any other page you have modified, such as Main.WebHome, a modified Panel, etc.

166

167

1.1.1.1 Let's clean it up

168

169

* Expand the XWiki WAR that you installed in your servlet container (the one that contains the JDBC drivers to access your database) into a new folder, using {style:type=span|font-family=courier new,courier}jar xvf xwiki-1.1-enterprise.war{style}, or avoid this step if you performed an export/import data migration (you already expanded it)

170

* Copy your old {style:type=span|font-family=courier new,courier}xwiki.cfg{style} and {style:type=span|font-family=courier new,courier}hibernate.cfg.xml{style} file to the WEB-INF folder. Take care that if some changes were already made (probably because of database configuration when you installed the JDBC drivers) could be lost, so take car to add these changes

171

* Rename the skins/albatross folder to albatross.original, and copy the skins/default folder from XWiki 0.9 to skin/albatross. (~~*WARNING:* this is an optional step, in case you don't want to use the default skin for 1.1x and want to retain your current skin in the new version~~)

172

* Install this new folder as the xwiki application in your servlet container (may be by copying the folder to the servlet filesystem space or by packing it in a WAR file and deploying it)

173

174

\\

175

At this point all is set, you can experience our old wiki data over the new XWiki core !!!

1.1 Troubleshooting

1.1.1 Field 'XWD_ARCHIVE' doesn't have a default value

188

189

If you get an error like the one below it probably means you had an old XWiki version installed (most likely a 0.9 version) which had a wrong schema. We're normally automatically fixing schemas at startup when you set the <tt>xwiki.store.hibernate.updateschema</tt> configuration parameter in <tt>xwiki.cfg</tt> (it's set to on by default). However it's currently not done for this error.

190

191

{code:none}

192

Wrapped Exception: Could not execute JDBC batch update

193

[...]

194

Wrapped Exception:

195

java.sql.BatchUpdateException: Field 'XWD_ARCHIVE' doesn't have a default value

196