I have a "housekeeping" BPM process that needs to execute once a week.
Currently, my team has developed a long-running BPM process containing a loop that never terminates. The BPM process diagram has a timer at the end of the loop to reschedule when to start the next loop iteration. If the jbpm server is shutdown and restarted, we are
depending on this active process instance to automatically get restarted by jbpm runtimes and resume the timer looping behavior.
Is this an appropriate use of a timer?
Are there other BPM mechanisms that would allow the BPM diagram to contain a clean start and end node? Perhaps there is a event-based BPM start node that I have overlooked?
Or is it better to have the BPM process contain a "standard" start and terminate node and use the Operating System task scheduler to initiate each new execution of the housekeeping process?