Apache OpenMeetings - Apache Derby Configuration

Demo | Download | Installation | Wiki

General

Home
License
ASF
Downloads
Commercial Support

Installation and Upgrade

Installation
Upgrade
Tutorials
Command Line Admin

Community

Get Involved
Committers
Mailing Lists
Wiki

Development

Source Code
Bugs / Issues (JIRA)
Dependencies
Build Instructions
JUnit Testing
Manual Testing
Release Guide
Website Guide

Integration

SOAP/REST API
REST API Sample
Ldap and ADS
OAuth2
VoIP and SIP
Errors table

Plugins

Moodle Plugin
Sakai Plugin
Jira Plugin
Joomla Plugin
Drupal Plugin
Bitrix Plugin
Confluence Plugin
SugarCRM Plugin
Redmine Plugin

DB Sample Configurations
Apache Derby
IBM DB2
Oracle
MySQL
Postgres
MSSQL
Localization and languages
Internationalisation
LanguageEditor
TimeZoneHandling
EditTemplates
NAT Port Settings
Port settings
Performance
JVM performance tuning
User Interface
Themes
Dashboard
Webcam resolutions
Room layout options
Hot Keys
Customization
Webapp name/path
Navigation
Calendar and timezone
Custom room type
Custom ctypt mechanism
General Configuration
Security
Restricted Access
RTMPS and HTTPS
Converters
OpenOffice Converter
FFMPEG Version Switch
Clustering
Clustering
Misc
Get version info

Apache Derby Configuration

OpenMeetings default configuration is to use Apache Derby.

It is recommended for production environments and high availibility to change to an usual relational database like MySQL, Postgres or DB2.

For more information about Apache Derby see http://db.apache.org/derby/

There is a sample configuration for Apache Derby that ships with every release in:
/webapps/openmeetings/WEB-INF/classes/META-INF/derby_persistence.xml

If you encounter issues, you can drop the db again and delete the file /webapps/openmeetings/conf/install.xml and then run the web based installer again