<
From version < 9.4 >
edited by Manuel Smeria
on 2012/12/10
To version < 9.5 >
edited by Vincent Massol
on 2015/03/13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ManuelSmeria
1 +XWiki.VincentMassol
Content
... ... @@ -12,9 +12,10 @@
12 12  * You can use a remote HSQLDB database instead of embedding it. To do this, just use a URL like ##jdbc:hsqldb:hsql:HOSTNAME...## instead of the ##jdbcc:hsqldb:file:..## URL. The major version of the hsqldb jar file must match the major version that the HSQLDB server is using.
13 13  * If you want to use your app server facilities to manage your data sources (generally a better strategy), then you must follow these steps:
14 14  ** Put the ##hsqldb*.jar## file into your app server class path instead of in your web app (like in ##$CATALINA_HOME/common/lib##)
15 -** In ##hibernate.cfg.xml##, use the following settings in place of the HSQLDB block in the sample file. Specifically, do not set the url, user, etc. here and leave the provider_class unset (i.e. use the default value), since XWiki's implementation does not handle container-managed data sources:
15 +** In ##hibernate.cfg.xml##, use the following settings in place of the HSQLDB block in the sample file. Specifically, do not set the url, user, etc. here and leave the provider_class unset (i.e. use the default value), since XWiki's implementation does not handle container-managed data sources:(((
16 16  {{code}}
17 17  <property name="connection.datasource">java:/comp/env/jdbc/xwiki</property>
18 18  <property name="dialect">org.hibernate.dialect.HSQLDialect</property>
19 19  {{/code}}
20 +)))
20 20  ** the final step is to manage the data source using app server facilities. With Tomcat, for example, you would map the //resource link// ##jcbc/xwikiDs## to a container-managed data source using the Admin web app or by editing the file ##conf/Catalina/*/xwiki.xml## (i.e. webapp-name + ".xml").

Get Connected