Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -78,10 +78,6 @@
78	78	* [[Microsoft SQL Server Installation>>AdminGuide.InstallationMSSQL]]
79	79	* [[H2 Installation>>AdminGuide.InstallationH2]]
80	80
81		-{{info}}
82		-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.
83		-{{/info}}
84		-
85	85	== Using a Data Source ==
86	86
87	87	A more scalable and J2EE-conformant tactic is to use the Servlet Container to manage your data source. You modify the web app as little as possible.
...	...	@@ -90,7 +90,7 @@
90	90	* Do not set user, url, etc., nor ##connection.provider_class## in ##hibernate.cfg.xml##. The critical settings are ##connection.datasource## (with JNDI name like ##java:/comp/env/jdbc/XWikiDS##) and the dialect class for your DB vendor. Do not comment out ##<mapping resource="..."/>## elements, hibernate needs them. Note that you should leave the ##provider_class## unset, since XWiki's implementation doesn't handle container-managed data sources.
91	91	* Manage all database access settings using your container facilities, for example Tomcat admin webapp or ##server.xml## + ##APPNAME.xml##. Uncommenting the ##<resource-ref>## element inside ##WEB-INF/web.xml## that matches the above JNDI name and looks like ##<res-ref-name>jdbc/XWikiDS</res-ref-name>## could be a good idea.
92	92
93		-= Concluding Step =
	89	+= Install the XWiki UI =
94	94
95	95	{{include reference="AdminGuide.InstallationConcludingSteps"/}}
96	96