<HTML><H3>Job Queue Entries</H3></HTML>
All Sprinkler operations are executed by scheduled Job Queue Entries.
For Sprinkler to operate it is mandatory to have Scheduled Tasks active on Dynamics 365 Business Central; please check the official Microsoft documentation about this configuration.
Three different scheduled Job Queue Entries are requested for Sprinkler operations:
CORE: this is the main process, handling all data incoming and outgoing.
This Job is normally running, until next error, and will be restarted automatically in case of error.
WSHANDLER: every Target Peer needs a specific WSHANDLER Job; this Job calls the remote Web Service via SOAP.
SENTRY: two scheduled jobs are created to restart the main CORE Job.
All Job Queue Entries belonging to Sprinkler structure must run with the user Data Distribution Service User.
If you run the Setup Wizard, all Job Queue Entries are created automatically. Anyway, as a reference, this is the configuration of all involved Job Queue Entries:
CORE Process (only one)
Object Type to Run: Codeunit
Object ID to Run: 3072560
Parameter String: CORE
User ID: corresponding to [Data Distribution Service User]
Recurrence: every day
No. of Minutes Between Runs: 1
SENTRY Processes (Two)
Object Type to Run: Codeunit
Object ID to Run: 3072560
Parameter String: SENTRY
User ID: corresponding to [Data Distribution Service User]
Recurrence: every day
No. of Minutes Between Runs: 10
NOTE: both SENTRY processes will alternate every 4-5 minutes automatically; it is not needed a manual alignment
WSHANDLER Processes (one for every Target Peer)
Object Type to Run: Codeunit
Object ID to Run: 3072560
Parameter String: WSHANDLER,{22200002-0000-0000-0000-000000000000}
(dove tra parentesi graffe deve essere indicato il Peer ID corrispondente al Peer di destinazione)
User ID: corresponding to [Data Distribution Service User]
Recurrence: every day
No. of Minutes Between Runs: 1