Show/Hide Toolbars

How to Implement Extended Logging in FVTerm

Navigation: » No topics above this level «

Introduction

Scroll Prev Top Next More

This document provides assistance in the implementation of custom logging and control/data replication for the Flynet FVTerm Web Terminal Emulator.

 

By implementing a custom logging extension assembly, user interactions with screens while using the Flynet Web Terminal emulator (FVTerm) can be controlled at the server as well as logged to a file or a database.

 

Possible uses include:

 

Single or Custom Signon Implementation

Access control for web users to sensitive data not otherwise possible with existing host security definitions

Audit-trail implementation for tracking user access and data entry

Data replication: every change made by a user to a host-based terminal application can be immediately updated in a database for use by client-server or web applications

 

To log by specific field name, the screens and fields involved must be mapped to a standard Flynet definitions file, either with the Mapper utility or Flynet Viewer Studio.

 

Once screen identification information is available (along with field locations and names within the screens), the custom logging assembly can log each and every add or update of the identified field data by users.