Demonstration of Infologica File Watching System

Infologica File Watcher Service operates as a multithreaded windows service providing event-driven task automation based on the arrival of files in the configurable watched directory.
The Infologica File Watcher visual interface allows to register any Infologica Fusion component service as an Execution Provider(File Processor) and further map it to the file arrival event via the task unit, which represents the lowest business abstraction in the File Watcher hierarchy. The task contains the configurable set of conditions defining the file proccesing event, like file directory and file extension. It also defines the logging, archiving, retry and notification rules as well as alows to customise input task parameters.
The current tutorial covers the full development cycle of the component service and its registration with the File Watching System using Microsoft Visual Studio 2005, Infologica Fusion Framework SDK and Infologica File Watching 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 "FileProcessor".
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 file name, path and custom parameters from the inbound message simulating the FileProcessor task definition:

We are ready to debug our service using Infologica Application Service Test Bench. The test bench 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 File Watcher Admin Console.
File Watcher Admin Console visual interface allows to register any Fusion component service as a File Processor. Administrator uses the component browser to select the "Sample" component service with the "FileProcessor" operation we've just implemented
... and maps the above component to the newly created File Processor "DemoFileProcessor"
The next step is to define the FileProcessor task, select the log level and choose the archive mode.
Once the task is created the Administrator configures the File Watching Directory and File Filters if any.
Administrator maps the task to the previously configured FileProcessor and continues task editing, configuring the number of retries, retry interval, and customises the input task parameters.
Finally Administrator creates the task notification groups and defines the notification conditions.
Administrator can manipulate with the file Watcher Admin Console adjusting the file processing status refresh interval and the history timeslot for the processed files.
We assume that the file watching service is up and running so we can proceed with the test. We create the FileWatcherTest.txt file and drop it into the previously configured C:\Temp directory. Now we can monitor the current activity of the File Watching Service using our File Watching Admin Console.
Double clicking on the task opens the Task Detailed Status.
Once the file is picked up by the File Watching Service it is renamed and moved to the preconfigured folder where it is processed by the Infologica Component Service. The processed files are being compressed and stored in the special configurable archive folder.
Navigating to the Tools/Definitions/Export starts the Infologica Definition Export Tool which helps to serialise the file processing instructions into the structured XML document format...
...and seamlessly redeploy it to any environment using Infologica FileProcessor Definition Import Tool.
Back to demos and tutorials