Wiki source code of Installation

Last modified by Vincent Massol on 2023/03/31

Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
5 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 (MySQL, PostgreSQL, etc) but XWiki and the database need to be setup correctly.
7 If you're upgrading an existing XWiki install check the [[Upgrade instructions page>>Documentation.AdminGuide.Upgrade]].
9 Pick one of the [[installation methods>>#HInstallationMethods]] to begin installing XWiki.
11 Once you've finished the installation check the other topics in the [[Admin Guide>>Documentation.AdminGuide.WebHome]] for configuring and [[securing>>Documentation.AdminGuide.Security]] your wiki.
13 {{id name="Prerequisites"/}}
15 = Hardware and Software requirements =
17 * A [[supported Java version>>dev:Community.SupportStrategy.JavaSupportStrategy.WebHome]]. Note that a JRE is enough and you don't need a JDK.
18 * A Servlet Container supporting Servlet 3.1 (Servlet 3.0.1 for XWiki version < 12). Check the [[Servlet Containers officially supported by XWiki devs>>dev:Community.ServletContainerSupportStrategy.WebHome]].
19 * A Database and a JDBC 4.2 Driver for your database (JDBC 4 was required for XWiki versions < 11.5). Check the [[databases offically supported by XWiki devs>>dev:Community.DatabaseSupportStrategy]].
20 * A supported browser to access XWiki. Check the [[browsers offically supported by XWiki devs>>dev:Community.BrowserSupportStrategy]].
21 * Enough memory, check the [[Memory section>>Documentation.AdminGuide.Performances.WebHome#HMemory]] of the [[Performance Guide>>Documentation.AdminGuide.Performances.WebHome]].
22 * Enough [[CPU and RAM>>Documentation.AdminGuide.Performances.WebHome#HSizing]]
23 * Check the [[release notes>>xwiki:ReleaseNotes.WebHome]] for the version you're installing to see what browsers and databases have been tested for it, and to see specific requirements/installation steps. You can also check our [[general support strategy>>dev:Community.SupportStrategy]].
24 * If you're running XWiki on a server without a display, pass the following Java System Property to the JVM running your Servlet Container: ##-Djava.awt.headless=true##.
26 = Installation Methods =
28 For testing XWiki, we highly recommend one of the following installation method:
30 * [[Using XWiki in the cloud>>Hosted.WebHome]]: This is by far the simplest to try XWiki since you don't need to install anything.
31 * [[Using a standalone distribution >>Documentation.AdminGuide.InstallationStandalone]]: Provides a built-in XWiki, with a portable database (HSQLDB) and a lightweight Java container (Jetty). This standalone distribution is not recommended in a production environment (check the [[DB limitations>>Documentation.AdminGuide.Installation.InstallationWAR.InstallationHSQL.WebHome]]). If you need to use it in a production basis, you may look at the other options.
32 * [[Using an official XWiki Docker image>>]]: Provides an easy solution to test XWiki, with a configuration very close to a production setup. You can also use this method in production if you're used to putting Docker images in production.
34 For production installations, we recommend the following installation method:
36 * [[Using .deb package (usable for production)>>Documentation.AdminGuide.InstallationViaAPT]]: Provides a .deb package that can be used on a Debian-based operating system. It can be installed with ##dpkg## or ##apt##; installation is thus automated.
38 Last, you could manually deploy XWiki as a WAR into the Servlet Container of your choice and on the Database of your choice, if the previous methods were not good enough for your needs. Beware that this requires some technical knowledge about Servlet Container and Databses:
40 * [[Using .war package (usable for production)>>Documentation.AdminGuide.InstallationWAR]]: Provides a Java application package that has to be installed in a Java container (such as Tomcat). This can be used on almost any operating system.
42 {{warning}}
43 Whatever the installation method, you should make sure to [[create the database indexes manually for indexes that are not created automatically>>Documentation.AdminGuide.Performances.Database Administration.WebHome]].
44 {{/warning}}
46 = Other Installation Methods =
48 This section is about other, non-official ways of installing XWiki that have been contributed by the community.
50 {{warning}}
51 Tutorials external to the site have not been validated for correctness by the XWiki Development Team and it's also possible that they are out of date or even not working.
52 {{/warning}}
54 * [[How to Install XWiki on Your Synology NAS>>]]
55 * [[How to install XWiki on Debian 9>>]]
56 * [[Ansible playbook for installing XWiki>>]]
57 * [[XWiki On OpenShift (Platform-as-a-Service)>>]]
58 * [[XWiki On Debian 4 (Etch) - Tomcat - PostgreSQL (or MySQL)>>]] (German)
59 * [[XWiki On Windows - GlassFish - Oracle>>]] (Russian)
60 * [[Install XWiki using Docker compose>>]] (French)
61 * [[XWiki in Windows - PostgreSQL - Tomcat 9 - Waffle>>]] (English, video)
62 * [[XWiki 10.9 with LDAP/SSO/MSSQL on Windows>>]]
63 * [[XWiki Installation on AWS>>.XWiki Installation on AWS.WebHome]]
64 ** [[Deployment using CDK code>>.XWiki Installation on AWS.Deployment Using CDK Code.WebHome]]
65 ** [[Deployment Using Cloudformation Template>>.XWiki Installation on AWS.Deployment Using Cloudformation Template.WebHome]]
67 = Accessing your wiki =
69 Once you've installed XWiki using one of the methods defined above, you can access it by pointing your web browser to {{code language="none"}}http://localhost:8080/xwiki{{/code}}.
71 = HTTP Proxy =
73 You now have a working XWiki instance but it's often a good idea to access it trough an HTTP proxy especially when you plan to access it through the standard HTTP/HTTPS port instead of 8080.
75 * [[Apache HTTPD>>Documentation.AdminGuide.Installation.ApacheHTTPD]]
76 * [[NginX>>Documentation.AdminGuide.Installation.NginX]]
78 = Troubleshooting =
80 You can verify some basic settings of your XWiki installation (on Tomcat, MySQL) using the [[Admin Tools application>>extensions:Extension.Admin Tools Application]]. Keep in mind that some of these tools only work in a Linux environment.
82 == What to do with an empty XWiki? ==
84 == Running multiple instances of XWiki in the same container ==
86 If you get this error:
88 {{code}}
89 com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context
90 Wrapped Exception: Failed to get cache factory component
91 ...
92 Caused by:
93 org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.xwiki.infinispan
94 {{/code}}
96 You need to edit ##WEB-INF/cache/infinispan/config.xml## for each instance of XWiki.
98 1. For Infinispan up till version 6, change the ##jmxDomain## value (found under the ##globalJmxStatistics## tag) to have a unique name, or add ##allowDuplicateDomains="true"## attribute for ##globalJmxStatistics## element.
99 1. For Infinispan version 7, add ##<jmx duplicate-domains="true"/>## element in ##<cache-container...## element.
102 == Running XWiki behind a proxy server ==
104 The extension manager relies on remote repositories for finding and fetching available extensions. If your XWiki is installed in a network which requires accessing the internet through a proxy server, most likely searching for extensions will fail and log files will contain ##connection refused## exceptions.
106 In such cases, you can configure XWiki to use the proxy server.
108 XWiki uses default Java proxy configuration through Apache httpclient. See the [[Java Networking and Proxies documentation>>]] for more details.
109 The main idea is to add a set of proxy-related properties to the system scope.
111 For an installation using Tomcat 6 it could be done in the following way: modify ##/<tomcat-home>/bin/ and added proxies to the ##JAVA_OPTS## variable definition:
113 {{code}}
114 JAVA_OPTS="$JAVA_OPTS -Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME -Dhttp.proxyPort=7777 -Dhttps.proxyPort=7777 -Xmx512m -XX:MaxPermSize=196m $XWIKI_OPTS"
115 {{/code}}
117 For an installation of the HSQLDB demo package you could do it by adding something like this to ##/xwiki-platform-distribution-flavor-jetty-hsqldb-x.y/
119 {{code}}
120 XWIKI_OPTS="$XWIKI_OPTS -Dhttp.proxyPort=7777 -Dhttps.proxyPort=7777"
121 {{/code}}
123 Note: If your proxy server only allows partial access to the internet you need to make sure that the sites, and (note that one is .##com## and the others are can be accessed.
125 If your proxy server require authentication you can use ##-Dhttps.proxyUser## and ##-Dhttps.proxyPassword## (and the http alteratives).
127 === Debugging proxy configuration issues ===
129 If you are having trouble with debugging whether or not the proxy configuration you've just made is properly read by XWiki, you could drop the following groovy script in a new page on your XWiki instance and look for the values of the (proxy) properties you're trying to change:
131 {{code language="groovy"}}
132 {{groovy}}
133 println "== Environment Variables =="
134 System.getenv().each { name, value -> println "Name: {{{$name}}} = Value {{{$value}}}" }
135 println ""
136 println "== Java System Properties =="
137 System.getProperties().each { name, value -> println "Name: {{{$name}}} = Value {{{$value}}}" }
138 {{/groovy}}
139 {{/code}}
141 Additionally, you could also include this test content that actually tests if your XWiki instance is able to access the Internet (using the "httpbin" service; you can use anything else, including, for both HTTP and HTTPs:
143 {{code language="velocity"}}
144 == Test HTTP Access ==
145 Your XWiki server's IP is:
146 {{velocity}}
147 $xwiki.getURLContent("")
148 {{/velocity}}
150 == Test HTTPS Access ==
151 Your XWiki server's IP is:
152 {{velocity}}
153 $xwiki.getURLContent("")
154 {{/velocity}}
155 {{/code}}
157 == Unsupported major.minor version 51.0 ==
159 This is because starting with version 6.0, XWiki requires Java 7 and you're using Java 6. You need to upgrade your Java version.
161 {{include reference="Documentation.AdminGuide.Installation.InstallationConcludingSteps.WebHome" section="HInstallingwithoutinternetconnection"/}}
163 == Getting an error about SSL certificate ==
165 If you get an error in the log telling you that it fail to access some some https website it usually means you have a too old version of Java 8 (older that update 101) and you should upgrade it (does not need to be upgraded to next major version of Java, just make sure you have at least Java 8 update 101).
167 {{code language="none"}}
168 2017-03-14 20:40:17,494 [http://dwswiki10:8080/xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin&section=XWiki.AddExtensions] ERROR aultExtensionRepositoryManager - Failed to search on repository [] with query []. Ignore and go to next repository.
169 Failed to search extensions based on pattern []
170 at
171 ...
172 Caused by: Failed to request []
173 at org.xwiki.extension.repository.xwiki.internal.XWikiExtensionRepository.getRESTResource(
174 ...
175 Caused by: PKIX path building failed: unable to find valid certification path to requested target
176 at
177 ...
178 Caused by: PKIX path building failed: unable to find valid certification path to requested target
179 at
180 ...
181 Caused by: unable to find valid certification path to requested target
182 at
183 ...
184 {{/code}}
186 == "File path too long" on Windows when unzipping ==
188 The Windows Operating System imposes a [[file path limit to around 260 characters>>]]. XWiki's zip file can, in some cases, reach paths as long a 182 characters, or even longer. To avoid such errors you could do one of the following:
190 * Install in a folder that is as close to the root of the drive as possible and uses a small name, e.g. ##C:\xwiki##
191 * Install XWiki using the [[cygwin>>]] environment that overcomes this limitation
192 * Starting with Windows 10, you can set or create the ##EnableLongPaths## with a value of ##1## in the in the ##HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem## Windows Registry in order to activate support for long paths. More details and step-by-step instructions are available in various online tutorials such as [[this one>>]].
193 * As Windows Unarchiver cannot unzip files with long paths, [[7-Zip>>]]can be used instead.

Get Connected