Demonstration of Infologica Job Scheduling Service

Designed as a member of Infologica Fusion Family Suite the Job Scheduler is just another trigger which implements the Infologica Fusion message-based invocation and logging interfaces. This means that Job Scheduler can reuse any existing component service from the Infologica Fusion component container without extra coding.
This also means that any new component service with implemented Infologica Fusion IRequestHandler interface can be immediatelly registered with any Infologica Fusion Enterprise Service.
The current tutorial covers the full development cycle of the component service and its registration with the Job Scheduling Service using Microsoft Visual Studio 2005, Infologica Fusion Framework SDK and Infologica Job Scheduler Administration Console.
We begin from the creation of the new project in the Visual Studio 2005 using Infologica Fusion Application Service Template. Once the project is created we add the New Item to the project by selecting the Fusion Operation from the Visual Studio Installed Template Dialog and renaming it as a "JobSchedulerTask".
Operation template provides the basic implementation of the Infologica Fusion component service public interface and contains the generic code for logging, performance monitoring, message parsing and exception handling.

The special "Developer code Area" in the Infologica Fusion operation template is allocated for code customisation. This is the region where developer writes the message processing code and invokes infrastructure service adapters. For the current demonstration we are going to rewrite this region with the simple iteration logic. We will use the Application Context object to write to the Infologica Fusion Log System and apply XPath query to retrieve the custom parameters from the inbound message:

We are ready to debug our service using Infologica Application Service Test Bench. The testbench should be registered with the Visual Studio project as a start external programm. The test bench uses reflection to dynamically list all operations implementing the Infologica Fusion IRequestHandler interface. Infologica Fusion Framework architecture allows developers to create multiple test scenarious using test bench and debug their application services locally while invoking all back-end infrastructure services using the .NET Remoting.
It is important that Infologica Application Test Bench implements the same component invocation interfaces as any other Infologica Fusion Service. Once the test is successfull we can recompile our component service for release and safely move on to the task registration stage.
All further steps should be done by the Infologica Fusion Administrator using Job Scheduling Admin Console.
Job Scheduler visual interface allows to register any Fusion component service as a Task Provider. Administrator uses the component browser to select the "Sample" component service with the "JobSchedulerTask" operation we've just implemented
...and maps the above component to the newly created task provider "Demo Task Provider".
The next step is to define the job unit which could consist of any number of logical steps or tasks.
Once the job is created the Administrator configures the tasks representing the lowest business abstraction in the Job Scheduler hierarchy. Each task is further mapped to the previously configured Task Provider.
Administrator continues editing each task, configuring the number of retries, retry interval, action on failure (quit the job or proceed with the next task) and customises input task parameters.
Sophisticated scheduler interface allows Administrator to define the time and frequency of execution.
Finally Administrator can create the task notification groups and define the notification conditions.
The Job Scheduler Administration Console gives us an option to run the job on demand, so we could test our configuration immediatelly.
The Job Scheduler Console provides the Infologica Fusion Administrator with the real time monitoring of the job execution status.
Administrator can browse the task history and custom logs generated by component service:
The Infologica Job Definition Export Tool provides the Intuitive Graphical interface which helps to serialise the job logical instructions in the structured XML document format...
...and seamlessly redeploy it to any environment using Infologica Job Definition Import Tool.
Back to demos and tutorials