...
- The current release of evaluation is 1.24.10
- Requires Sakai 2.46.x or higher
- Requires Hierarchy 1.2.4 or higher
- Requires EntityBroker 1.3.3 5 or higher (1.3.3 5 is included in Sakai 2.56.x)
- The previous release of evaluation is 1.23.0
- Requires Sakai 2.25.x or higher
- Requires Hierarchy 1.02.24
- Requires EntityBroker 1.23.0 3 or higher higher (1.23.0 3 is included in Sakai 2.45.x)
- I am hoping to simplify this process by building a war file which includes most everything in a single file sometime in the future but the way Sakai is structured makes this quite difficult at the present time.
...
- Checkout jobscheduler into your sakai source directory (use subclipse or the command below)
svn co https://source.sakaiproject.org/svn/jobscheduler/branches/aaronz_2-4-x jobscheduler - Build job scheduler using maven (mvn clean install sakai:deploy / maven sakai) from within the jobscheduler folder
See notes below related to the polling job.
- Checkout jobscheduler into your sakai source directory (use subclipse or the command below)
- Add entity broker project (required for Sakai versions older than 2.6, otherwise, you already have it)
- Checkout entity broker 1.3.3+ into your sakai source directory (use subclipse or the command below)
svn co https://source.sakaiproject.org/svn/entitybroker/tags/entitybroker-1.3.6/ entity-broker - Build entity broker using maven (mvn clean install sakai:deploy / maven sakai) from within the entity-broker folder
- Checkout entity broker 1.3.3+ into your sakai source directory (use subclipse or the command below)
- Add hierarchy project (required for trunk and eval 1.2+)
- Checkout hierarchy into your sakai source directory (use subclipse or the command below)
svn co https://source.sakaiproject.org/contrib/caret/hierarchy/tags/hierarchy-1.2.4/ hierarchy - Build hierarchy using maven (mvn clean install sakai:deploy / maven sakai) from within the hierarchy folder
- (maybe not necessary, but works for Sakai 2.6.2 and hierarchy 1.2.4) Adapt the parent version tag in hierarchy/pom.xml to your current Sakai version.
- Checkout hierarchy into your sakai source directory (use subclipse or the command below)
- If using trunk revision <= 67204 (maybe even for higher revisions) and Sakai 2.6.2. Do this also if you get some strange "dependencies.dependency.version missing" errors.
- Run the Kernel K1 conversion scripts from the evaluation directory: http://confluence.sakaiproject.org/display/DOC/Sakai+2.6+Contrib+Tool+Migration+Tips
- (maybe not necessary) Adapt the master and parent version tags in evaluation/pom.xml to 2.6.2 (or your current 2.6 version)
- evaluation/pom.xml: <sakai.version>2.6.2</sakai.version>
- evaluation/pom.xml: <version>2.6.2</version>
- As the evaluation system currently depends on Sakai 2.5.4, you may need to update the pom.xml files to reflect the sakai version you are using.
- Run maven sakai from within the evaluationfolder
- This will download all needed jars and compile the source code
- Maven 1 users: You may need to add the following repositories to your maven 1 build.properties to get all needed jars:
For example: Your build.properties should have this line (or something like it)
No Format maven.repo.remote = http://source.sakaiproject.org/maven/,http://www2.caret.cam.ac.uk/maven/,http://repo1.maven.org/maven/
- Start tomcat and check the log for errors, there should be none if all jars were downloaded and installed correctly
...
- Job Scheduler - Email notification and evaluation state change based on the passage of time uses a new job scheduler service that depends on polling. Andrew Poland was working on configurable and automatic polling, but last I heard this had not been checked in. (Update: May 9 - Andrew wrote the code to automatically register the job but there is a bug. If it is fixed the code will go in the 015 tag.) Update: Andrew got this done for 2.4.
- With the 2.4 version of jobscheduler there is no need to use the jobscheduler tool to schedule running of the ScheduledInvocationRunner.* The job automatically registers itself on startup. It runs every 10 mins by default.
- To change that timer you can set:
- jobscheduler.invocation.interval=600
Where 600 is the number of seconds between runs.
- jobscheduler.invocation.interval=600
- To change that timer you can set:
- Evaluation email and scheduling jobs that are created go into a table SCHEDULER_DELAYED_INVOCATION.
- When the Scheduled Invocation Runner runs, it looks for entries in that table and executed those that have a date equal to or before the current date. When a job is run the Scheduled Invocation Manager will removed its entry in the SCHEDULER_DELAYED_INVOCATION table.
- Note: A patch attached to SAK-10611 is needed to prevent multiple instances of Scheduled Invocation Runner running the same command multiple times. This can happen if the polling interval is shorter than the job completion time. EVALSYS-202 and EVALSYS-133 relate to this. Andrew Poland will apply the patch (it changes Scheduled Invocation Runner to a StatefulJob) to trunk and 2.4.x but has not done so as of Jul 19 07.
Note:The Sakai EmailService requires unauthenticated SMTP. If unauthenticated SMTP is not available in the development environment, email can be logged by adding in sakai.properties:
No Format # log email rather than send it testMode@org.sakaiproject.email.api.EmailService=true