|
|
# Job Classes
|
|
|
|
|
|
Job classes have several purposes. They can be triggered by events or by a schedule. There are some job classes that ship with the application, but you can also have your own, by extending the interface `edu.kit.scc.webreg.job.ExecutableJob`. For a list of existing job classes and their properties see [below](#list-of-job-classes). To test a job class, you can click the "execute job" button. This probably won't work for event driven jobs, because the object, which triggered the event is missing. Watch the server log for output.
|
|
|
|
|
|
# Schedules
|
|
|
|
|
|
Create a schedule if you want a job executed on a regular basis. You can choose the name of a schedule freely. The drop down list job class, has to point to the job class you want to be triggered. The time, when a schedule is executing is according to the jee6 `@Schedule` annotation. See [here](https://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html) for a description of possible values.
|
|
|
|
|
|
When a schedule is changed, it may take up to one minute until the change is propagated to every cluster node.
|
|
|
|
|
|
# List of Job Classes
|
|
|
|
|
|
The name of a job class can normally be chosen freely, if not otherwise stated here.
|
|
|
|
|
|
| Job class | Description |
|
|
|
| --- | --- |
|
|
|
| [edu.kit.scc.webreg.job.UpdateAllFederationMetadata](UpdateAllFederationMetadata) | Triggers an update to alle federation metadata |
|
|
|
| [edu.kit.scc.webreg.job.LogPing](LogPing) | Prints one line in the logfile |
|
|
|
| [edu.kit.scc.webreg.job.UpdateAllUserFromIdp](UpdateAllUserFromIdp) | Update user data from home organization |
|
|
|
| [edu.kit.scc.webreg.job.ClearAuditLogs](ClearAuditLogs)| Deletes old audit log entries from database |
|
|
|
|||
|
|
|
||| |