The inter-application files manager

Differentiate your functional dependencies from your scheduling dependencies

Download Product PDF

 

Manage your files at greater ease

eFile, a data sink, allows an asynchronous file management exchange between batch processes.

Consumers, as well as creators can now benefit from a functional link (content of the file), without having to be constrained by a technical dependency (or scheduling constraint)...

The creator can load the files within the data sink under a label, to be later extracted by one or more readers.

When several files are loaded under the same identifier, they can be merged during extraction.

A flexible and convenient interface

Accessibility

•Through batch and user interface
•Types of user profiles:
◊Admin:Defining parameters, and overall variables
◊Exploit: Defining extraction criterias/rules
◊Tracking: Access to file tracking screens to data sink, through log.
•Multi-criteria filtering
•Contextual navigation

Multi-criteria file tracking

•By identifier/deposit or extraction number, job name, jobid, date, status,...

 

 

 

 

Blocking an identifier (extraction)

•Unique, or by association (ex: block all extraction identifiers using a loading identifier).

Handling file status

• Unitary, by extraction ID or loading ID
• Restoration,suspension, deletion.

Custom queries

•Creation of specific requests (SELECT) by the administrator and setting description parameters.

•Execution of on demand queries per user to the “tracking profile” (result presented in the user interface, and exportable in csv)

Events log

•Log mapping all actions performed to data sink via interface, or by batch

•Specific log for all error handling.

 

Key features

  • The one which deposits the file in the data sink, does not need to know its consumer. Similarly, adding a consumer does not require any alterations by the issuer.
  • The consumer's scheduling may be completely independent from the creator's scheduling
  • An identifier can be best described as "optional"; the absence of deposit will not cause a consumer error: the file will be created empty. However a "mandatory" identifier will cause a consumer interruption (error), if no deposit has been made.
  • Loading a file can generate an event, whose coverage can group multiple identifiers. For example: the release of an application, or an exterior transfer when a set of identifiers receive a file...

 

 


 

Additional  features

 

 

 

 


 

diagram e-file additional features