...
SakaiAdminX uses an embedded Derby database to store some configuration information, as well as acting as a cache for the heaviest queries. It runs in embedded mode which is very lightweight.
You could, however, use MySQL or Oracle if you prefer and you will just ened to adjust your settings and use the appropriate drivers in place of the Derby onesMySQL or Oracle if you prefer and you will just need to adjust your settings and use the appropriate drivers in place of the Derby ones. SakaiAdminX ships with DB scripts for both Derby and MySQL. If you want to run SakaiAdminX on Oracle, you might need to tweak the scripts - if you do, send them to me for inclusion in the release. All SQL in SakaiAdminX should be database independent.
| Note | ||
|---|---|---|
| ||
You will need to create your database using either the MySQL console or your favourite database editor. You should create your database with the UTF-8 character set, ie 'create database sakaiadminx default character set utf8;' |
The following is for those who wish to use Derby, if you are using MySQL/Oracle, you can skip this section - BUT, make sure you populate your database with the included scripts.
Download, install and configure Apache Derby
...
| Code Block |
|---|
ij> run 'SAKAIADMINX-SRC/sql/derby-sakaiadminx-v1.0.sql';
ij> exit;
|
| Tip | ||
|---|---|---|
| ||
You will also need to run any database upgrade scripts via this same method abovesame method above. Note that for a first time installation, you can either run the creation script then the upgrade script, or the combined script to do it in one go. |
Add the Derby DB driver to Tomcat:
...
If you have not changed any of the roles then these should all be fine and can be ommitted omitted or added to sakai.properties as is. One point to note is that the list of special sites are the sites that you do not want the quartz jobs SakaiAdminX Quartz Jobs to ever touch. You could expand this to include other sites if you wish.
...
Output from these jobs is written to catalina.out however only warnings or errors will normally be present unless you change your Sakai log level to include INFO messages.
Do this by adding this to your sakai.properties (amend if you already have one of these blocks):
| Code Block |
|---|
log.config.count=1 log.config.1=INFO.uk.ac.lancs.e_science.sakaiadminx.jobs |
You absolutely need to configure the SuperHelpdeskUserSync job to run every few hours at least, otherwise the users that you add as Super Helpdesk users will have a large delay in getting access.
...