Impact Scheduler 2.0
Programmatically control your transportation and transformation of EDI files, with the Impact Scheduler. (Or, invoke any .NET class by implementing the provided Interface.)
Provides fully configurable triggers, using a straightforward Timer Trigger (every <n> seconds, minutes, hours, etc.) as well as a Date and Time "pattern" (UNIX-style cron trigger), allowing complex triggers such as at 4am on Monday, Wednesday, Friday, or at 9:00 or 17:00 on the 1st of May, etc.
The Impact Scheduler provides the ability to define a set of Jobs, each of which being comprised of Triggers (as described above) and Actions. Each Trigger has independent actions associated with it. Actions are reusable, and are specified by their class name and assembly name pairs. Each Trigger can invoke an action with different parameters.
Examples of the kinds of actions you can trigger with the Impact Scheduler:
- Execute reports
- Validate/monitor servers
- Transfer/move files
- Perform database queries
- Validate MSMQ queues
- Invoke web services
- etc. etc. etc. Any action that can be coded in .NET can be invoked!
The Impact Scheduler can be embedded within your own .NET applications, or run as a standalone server, or as a Windows Service. All logging from the Scheduler is stored in the Windows EventLog, for later review/perusal.
Miminal changes to your code, allows any .NET object, in any .NET language, to be invoked from the Impact Scheduler.
Defining Triggers, Actions and Jobs
Creating an Action
.