Service Module

The service module is the main difference between the Standard Edition and the Enterprise Edition.  It adds many advanced features to Navarre Report Scheduler.

• NT service based schedule processing
• Automatic system startup
• No user logon required
• Simultaneous multi report processing
• Background job processing
• Overlapping job schedules

NT Service based schedule processing:
A windows NT service is basically an application with no user interface, runs totally behind the screens and it needs no user interaction.  For Navarre Report Scheduler this is the main scheduling engine.  It is the program that decides when it is time to process a job and tracks all processing engines.

Automatic system startup:
You can set the service to automatically start when the server or workstation does. This means if the is ever a power outage or your system is shut down, when it resumes the Service Module will automatically start and start processing jobs.

No user logon required:
Since the Service Module starts when your system does no user is required to logon and then start the application to process the schedule of jobs.  Please note: depending on your network security you may need to set a user name and password for the Service Module

Simultaneous multi report processing:
The Service Module has the ability to process up to 20 Crystal Reports at one time.

Background job processing:
All jobs a processed in the background the user is not required to run any applications, confirm any logon settings or enter any parameters.  The Service Module handles all the job processing for you.

Overlapping job schedules:
The Standard Edition is a forward looking schedule engine. This means that if the processing time of a group of jobs is longer than the gap between the next group of jobs, this second group would be skipped and be reported as being “late” to the user interface. This is due to the way in which the engine in the Standard Edition processes groups of jobs.  Once a groups next run date has been reached the schedule engine stop looking at the database for jobs next run dates and only works on processing the group of jobs.  Once this group is completed the schedule engine will return to the database and look to see what jobs are due to run from the current date looking forward.  If the scheduled time for a group has since passed it will not be able to see the jobs.

The Service Module does NOT have this issue.  The Service Module handles a group in the same way, it stops looking at the database while processing a group, but once it completes the processing of the first group it looks back at the database and looks at what jobs should have been run while it was busy running the first group.  If jobs are found it will start the processing and then repeat the process until it catches up.