Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

Edit the four bedework*-ds.xml files to connect Bedework to your database

If you have based your configuration on one of the samples, you need to edit these four configuration files:

  1. bwbuild/myconfig/bedework-ds.xml: contains information about how to access your Bedework calendar server database
  2. bwbuild/myconfig/bedework-tz-ds.xml: contains information about how to access your Bedework timezone server database
  3. bwbuild/myconfig/bedework-synch-ds.xml: contains information about how to access your Bedework synchronization server database
  4. bwbuild/myconfig/bedework-card-ds.xml: contains information about how to access your Bedework carddav server database

In each case, within the <datasource> stanza:

  1. edit <connection-url>  to set the database host, port number, and database name.  
  2. edit <user-name> (the database user) and <password> (the database user's password).

Add JDBC Drivers to JBoss (in most cases, done for you)

Again, if you've based your configuration on one of the samples, you should have an appropriate JDBC driver in bwbuild/myconfig/lib/server.   During the build, that driver will be copied into <quickstart>/jboss-5.1.0.GA/server/default/lib.   If you'd like to update that driver, replace the one in bwbuild/myconfig/lib/server, then rebuild.

Non-standard configurations

The following steps will help you configure a non-standard / unsupported database with Bedework.

Configure Hibernate to work with your database's SQL dialect

Configuring Hibernate to use the appropriate dialect is done in bwbuild/myconfig/cal.properties. You need to set a few properties

org.bedework.global.hibernate.dialect=yourDialect

The value yourDialect is a defined Hibernate SQL dialect such as org.hibernate.dialect.HSQLDialect or org.hibernate.dialect.MySQL5Dialect. The dialect is a class defined on the class path. Hibernate defines a number of ‘standard’ dialects.

For example, the global property if using MySQL5 would be

org.bedework.global.hibernate.dialect=org.hibernate.dialect.MySQL5Dialect

A list of dialects understood by Hibernate can be found at:

http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configuration.html#configuration-optional-dialects

You can also look at the org.hibernate.dialect classes in the Hibernate jar file (for example, to use MySQL 5 which is not currently listed in the on-line Hibernate documentation, use org.hibernate.dialect.MySQL5Dialect ).

  • No labels