Grouper Users - Open Discussion List

[Chris Hyzer <>]

Is it that you don't want the grouper jobs to run because other things are 
processing, and you want it to be in serial, or is it that you want the data 
from the jobs to be intact in grouper in case they affect the grouper jobs?

If it is the former, then I think you want all jobs to run manually.  If it 
is the latter, then I think we can pick and choose which ones matter.  I say 
this since not all of them have a GSH command.  Here are examples of jobs:

- Rules job: this is mainly to clean up inconsistencies, the rules fire when 
things happen
- Log cleaner job: I don't think this depends on loader jobs
- Daily report: I could see how you would want to run this manually, if so, 
call this from GSH:
new 
GrouperReport().findBadMemberships(isRunBadMember).findUnresolvables(isRunUsdu).runReport()

- Enabled/disabled: If the loader isn't setting enabled disabled dates, then 
I don't think it matters when this runs.  This was intended to be at the date 
granularity... so it should schedule just after midnight

- Group sync job: If you are syncing a group to another grouper, you should 
do incremental in which case this is just to fix inconsistencies

- change log jobs which run every minute or so

- esb listener I think runs once and listens

Anyways, which jobs are important to you to run at a certain time?  I can try 
to expose a method for those at some point.

Thanks,
Chris




-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Peter DiCamillo
Sent: Tuesday, August 02, 2011 11:27 PM
To: 

Subject: [grouper-users] Running daily Grouper Loader jobs with a command?

I'm working on implementing the Grouper Loader at Brown, and fitting it 
into our daily provisioning. We need the Loader mainly for the change 
log, and do Grouper provisioning using local code. We provision Grouper 
and other systems using programs that run overnight. The starting time 
for overnight provisioning is fixed (1:30 am). However, after that the 
times are variable: each step runs when previous steps it depends on 
have completed. The starting and ending times of the steps can vary 
considerably during the year. For instance, course group updating can 
take much longer than usual during a registration period.

I see that the Grouper Loader schedules jobs which run continuously, 
such as for the change log, and jobs which would normally be run daily, 
and run at a scheduled time. Instead of running the daily jobs at a 
fixed time, I'd like to be able to run them as a step in overnight 
provisioning, after Grouper updating has completed. Is there a way to 
run those daily jobs using a gsh command or some other command, rather 
than having them scheduled with Quartz?

Peter