blob: d50f263fa1ce631a8a213ab2046e0a739a7516d2 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<document xmlns="http://maven.apache.org/XDOC/2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
<properties>
<title>H2 Configuration</title>
<author email="dev@openmeetings.apache.org">Apache OpenMeetings Team</author>
</properties>
<body>
<section name="H2 Configuration">
<p>
OpenMeetings default configuration is to use H2.
</p>
<p>
It is recommended for production environments and high
availibility to change to an usual relational database like Oracle, MySQL,
Postgres, MSSQL or DB2.
</p>
<p>
For more information about H2 see
<a href="https://www.h2database.com">https://www.h2database.com</a>
</p>
<p>
There is a sample configuration for H2 that ships with
every release in:
<br />
/webapps/openmeetings/WEB-INF/classes/META-INF/h2_persistence.xml
</p>
<p>
If you encounter issues, you can drop the db and then run the web
based installer again
</p>
</section>
</body>
</document>