Inventu Viewer Service and Runtime Applications
The emulation core service (FlyServer.exe) runs as a standard Windows 32 or 64 bit service on Windows Servers 2003, 2008, 2012 and Windows Server 2016; For evaluation: Windows/XP, Vista, Windows 7, Windows 8 and Windows 10 PC's.
There are separate installers for 32 bit and 64 bit systems, with a native 64 bit Service and API Assembly to enable direct integration with applications requiring 64 bit compatibility.
It provides:
•Multi threaded protocol manager for each connected session (up to hundreds can run on a single server depending on processor speed)
•HTTP port that processes XML-based requests from Administrator's Window to start/stop sessions, update configuration and provide emulation for a specific session
•Shared memory and event management architecture for efficient (fast) interfacing between applications and active terminal sessions
ViewerLib4 .NET Class Libraries
The ViewerLib4 .NET Assembly is for .NET 4.0 and 4.5 Framework environments. It provides high-performance access to screen sessions managed by the service.
The FSCProLib and ViewerLib .NET Class library are also still available for older .NET Framework 1.1, 2.0 and 3.5 and supports all the existing methods and properties as the FlyScreen COM interface. As a .NET managed code library, all of the Intellisense and other features of Visual Studio .NET and other .NET Compatible IDE's are available.
The primary API objects and methods include:
| HostConnection: | sessionOptions, connect(), getScreen(), disconnect() |
| HostScreen: | getText(), setText(), mappedGet(), mappedSet(), putCommand(), waitForScreen() |
Viewer Studio not only generates the same Screen I/O helper assembly as the older Mapper tool; it also includes a complete code generation framework that can create complete .NET solutions compatible with Visual Studio 2003, 2005, 2008, 2010, 2012, 2013, 2015, 2017 and Visual Studio 2019.
The Screen Mapper, a VB application only available for 32 bit installations, is for basic server-only development and includes a .NET assembly generation feature which removes much of the tedium in creating robust, highly maintainable screen integration modules. The generated module contains enumerations, methods and properties which leverage the Intellisense feature in Visual Studio, bringing 4GL productivity to the production of screen integration applications.
Screen Definition Files
The screen definition files are stored in special folder (c:\program files\[inventu/Flynet]\viewer\definitions) accessible to the ViewerLib API. They enable a separation between the logic in your applications and the layout and appearance of host screens. This enables the rapid construction of tools for importing screen definitions while facilitating change management for the targeted screens.
