This section provides a more technical description of the product, including specific features.
High Performance Windows Service
The core emulation engine runs as a standard Win32 service, providing control through the system services applet as well as event reporting using the standard Windows Event Log. This service provides up to hundreds of concurrent emulation sessions that persist independently of client processes, such as an Internet Information Services Active Server Page (IIS-ASP) or .NET object.
The core emulation engine is written in highly optimized C and C++, ensuring efficient use of resources and the fastest possible handling of the terminal data streams.
Separating Screen Mapping from the Logic
Screen interfaces all need to accommodate changing screen layouts: fields are moved on a regular basis, for example, to accommodate new or changing requirements. Utilizing a simple XML file design, developers describe screen recognition criteria as well as data field mapping.
In the developer's logic (implemented in the language of choice, such as Visual Basic, Delphi or Javascript), screens are recognized with simple methods, and data is read and written by name rather than screen row and column values. This avoids maintenance problems during the life of the application since all screen mapping is maintained in one place rather than scattered throughout the code.
Since the screen definitions are maintained in a simple, easily understood XML data interchange format, it facilitates the implementation of custom imports from other screen definition formats such as CICS BMS maps or AS400 SDF files.
In addition, the Screen Workflow Viewer can generate both full screen definition XML as well as individual screen definitions to the clipboard. This provides a clean, simple method of rapidly producing screen specifications for use in your applications.
Rapid Application Recording
After years of developing screen-based application interfaces, Inventu Corporation have learned that one of the biggest issues with productivity is lack of information on how to actually run the screen-based applications being interfaced to. In many cases, a user provides a quick demonstration and then goes away...leaving the developer to figure-out an interface that is usually not that easy (or it would not need replacing!).
The Screen Workflow Screen Recorder provides a dynamic documentation capability that enables analysts and users to assist in the detailed documentation of existing screen-based workflows. Examples might include "how to find order status information" or "how to calculate total premium and late fees due". Using a built-in emulator, the user follows the correct screens, commenting in an integrated rich text description field.
After a screen workflow has been recorded, the Screen Workflow Viewer is provided that indexes the screens viewed as well as provides animation of keystrokes to assist in learning how the application is navigated. Additional comments and information can be added over time so that each recording becomes a valuable asset through the full application life cycle.
Inventu Studio
Inventu Studio is an Integrated Development Environment (IDE) that manages the import of Recordings, identification of screens and mapping of screen data fields. Along with this high-level, graphical approach to managing the screen assets of the host application, Inventu Studio additionally provides modeling of Web Services, Enhanced User Interfaces and a custom-generated SharePoint 2010 Web Part. For more information see the Inventu Studio section.
Advanced .NET Frameworks for Screen Integration
The solutions generated by Inventu Studio include robust, production-ready classes that include both environmental interfaces to configuration and the ASP.NET environment as well as a full, customized navigation and screen read/write set of classes based on the screen assets modeled in Inventu Studio.
Optimized .NET Library (Assembly)
The Inventu Viewer .NET library ViewerLib4.dll (framework 4.0+) provides a comprehensive set of objects, methods and properties to encapsulate the difficult areas of screen interfacing into a few core methods and properties. With the screen interface encapsulated in a .NET Assembly, developers are able to use the language of their choice in any .NET supportive environment. However, this still has high productivity, as the screen interface elements have been separated from the logic through the use of the screen definition class.
The screen definition class (one of the .NET classes) controls the loading of the separate screen definition XML files, used to define screens, their recognition and field location mappings. With the screen definitions loaded, only a few methods and properties are needed to update screens, navigate between them and handle any exceptions that may occur.
Administration and Control
Provided with the Inventu Viewer Service is a set of administration applications that may be separately installed on any machine from which access to the live Inventu Viewer Service is desired (such as an administrator's desktop). These applications then access the service through a configurable HTTP port to enable remote administration.
Included in the Administration Applications are the following functions:
•View active or available sessions and status
•Start/Stop a session
•View a live session in a special administrator's emulation window -- enables both debugging as well as help desk capabilities
•Configure the service using tree-view property sheets
•Start/Stop/Clear Application Tracing
•View Application trace file which optionally includes buffers, screens, API calls and internals
Simulated Telnet Host
Another provided component, valuable during initial learning as well as development, is the Screen Simulator service, a scriptable TN3270 (or TN5250, VT100) host.
Screen Simulator comes with a sample TN3270 Insurance application which enables new users to practice without touching a "real" host system. By navigating the complex logon sequence (similar to those found in most mainframe shops), a developer can practice under controlled circumstances.
Screen Simulator also can read the trace files and recordings created from using the primary Inventu Viewer Service to connect to and exercise host sessions. In this mode, Screen Simulator will mimic the exact screens as displayed during the emulation session or recording. This is extremely useful for initial development, where screen mapping and simplistic navigation will work in the same fashion against the simulated host as the real host.
By using the Screen Simulator for initial development, developers do not require a connection to the host system and do not have to worry about test recycling or the impact of production system testing.
