3 Scheduler configuration
Scheduler requires a properly configured MOS. One Scheduler instance is automatically instantiated into each Environment MOS.
3.1 HOPEX installations without Scheduler
Some standard features (as provided standard Workflow Definitions) require a Scheduler instance. But Scheduler needs MOS and RDBMS repository.
For features relying on Scheduler to be executed, an option enables to deactivate the Scheduler so that all Scheduler operations calls are ignored.
To deactivate dependencies with Scheduler:
1. Go to HOPEX Options: Installation > Scheduler.
2. In the right pane, set the Client to scheduler connect mode option value to “No connection”.
3.2 Traceability
The Scheduler Tracking Level option enables to log the Scheduler activity into the MEGA error log (ssperrYYYYmmDD.txt file).
All the lines regarding the scheduler activity contain [Scheduler: .
The Scheduler tracking levels are:
0: no information logged
1: global scheduler actions
o Scheduler start
o Scheduler stop
o Scheduler Triggers reload from repository
2: updates and all client side calls
o Add Trigger
o Remove Trigger
o Update Trigger
o Get Trigger
o All client side calls
3 : job executions
o Job triggering
o Job execution
To follow up Scheduler activity:
1. Access HOPEX Options.
2. Check that your Option level is “Extended” (right-click Options and select “Extended”).
3. Expand Installation folder and select Scheduler.
4. In the right pane, select the Scheduler Tracking Level option value.
5. Reboot the SSP for this option to be taken into account.
The scheduler activity is written into the ssperrYYYYmmDD.txt file.
Example :
PID(2764);Thread(4448);Time(00:10:03);Session(SysMA A);[PID(0x00000ACC),Thread(0x00001160),Time(00:10:03)] [Scheduler:TriggerJob] [TriggerId(7BBA7C5F528C36D4):JobId(7BBA7C83528C3705):JobMacroId(7BBA7C23528C363F):JobExecUserId(0D510D8B2E210068):JobExecProfileId(0000000000000000):JobExecBaseId(0000000000000000):NextDateTime(2017/06/14 22:10:00):NbRepeat(15)]
PID(2764);Thread(4448);Time(00:10:03);Session(SysMA A);[PID(0x00000ACC),Thread(0x00001160),Time(00:10:03)] [Scheduler:CallExternalProcessToExecuteJob] [TriggerName(Indexing Automaton):TriggerId(7BBA7C5F528C36D4):JobId(7BBA7C83528C3705):JobMacroId(7BBA7C23528C363F):JobExecUserId(0D510D8B2E210068):JobExecProfileId(0000000000000000):JobExecBaseId(0000000000000000):NextDateTime(2017/06/14 22:10:00):NbRepeat(15):ExecutionMode(INDEXATION):ReadWriteMode(W)]
PID(2764);Thread(4448);Time(00:10:03);Session(SysMA A);[PID(0x00000ACC),Thread(0x00001160),Time(00:10:03)] [Scheduler:CallExternalProcessToExecuteJob:Result] [OK(1)] [TriggerName(Indexing Automaton):TriggerId(7BBA7C5F528C36D4):JobId(7BBA7C83528C3705):JobMacroId(7BBA7C23528C363F):JobExecUserId(0D510D8B2E210068):JobExecProfileId(0000000000000000):JobExecBaseId(0000000000000000):NextDateTime(2017/06/14 22:10:00):NbRepeat(15):ExecutionMode(INDEXATION):ReadWriteMode(W)]
PID(9308);Thread(19496);Time(00:10:03);Session(SysMA A (System Base closed));[PID(0x0000245C),Thread(0x00004C28),Time(00:10:03)] [Scheduler:ExecuteJob] [TriggerName(Indexing Automaton):TriggerId(7BBA7C5F528C36D4):JobId(7BBA7C83528C3705):JobMacroId(7BBA7C23528C363F):JobExecUserId(0D510D8B2E210068):JobExecProfileId(0000000000000000):JobExecBaseId(0000000000000000):NextDateTime(2017/06/14 22:10:00):NbRepeat(15):ExecutionMode(INDEXATION):ReadWriteMode(W)]
PID(2764);Thread(4448);Time(00:10:03);Session(SysMA A);[PID(0x00000ACC),Thread(0x00001160),Time(00:10:03)] [Scheduler:TriggerJob:Result] [OK(1):NextDateTime(2017/06/14 22:20:00)]
PID(9308);Thread(19496);Time(00:10:03);Session(SysMA A);[PID(0x0000245C),Thread(0x00004C28),Time(00:10:03)] [SchedulerClient:HandleScheduledJobEvent(SSP Connection)]