...
Configuration key | Description | Version | Default value | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
sitestats.db | Whether to use internal Sakai database or external database (same or different server) for SiteStats tables. Possible values: internal, external | 1.2+ | internal | ||||||||
sitestats.externalDb.auto.ddl | Set whether to execute a schema update after SessionFactory initialization | 1.2+ | true | ||||||||
sitestats.externalDb.hibernate.dialect | Hibernate dialect for external db | 1.2+ | org.hibernate.dialect.HSQLDialect | ||||||||
driverClassName@org.sakaiproject.sitestats.externalDbDataSource | Fully qualified Java class name of the JDBC driver for external db | 1.2+ | org.hsqldb.jdbcDriver | ||||||||
url@org.sakaiproject.sitestats.externalDbDataSource | Connection URL to be passed to JDBC driver for external db connection | 1.2+ | jdbc:hsqldb:mem:sitestats_db | ||||||||
username@org.sakaiproject.sitestats.externalDbDataSource | Username for external db | 1.2+ | sa | ||||||||
password@org.sakaiproject.sitestats.externalDbDataSource | Password for external db | 1.2+ |
| ||||||||
sitestats.externalDb.name | Server wide stats require this additional setting so that they are able to query both the main Sakai database and the external Sitestats database. There are caveats though: The database must be on the same URL as the main Sakai database and the user for the main Sakai DB must have read access. Essentially, the two databases need to be side by side. See:
| 2.3.2+ |
By default, the datasource connection pool is configured as follows:
...