Flynet Viewer Installation

This course covers the installation process for both Flynet Viewer Server and Flynet Viewer Studio

Flynet Viewer Server

Flynet Viewer Server - Introduction

The Flynet Viewer Server contains the core Flynet Viewer Emulation Service. This is the service that manages all sessions, screen protocols, and supports the base Flynet Viewer API. All Flynet Viewer solutions are built upon this core service and API.

In addition to this, the Server also includes the Terminal in a Browser*, as well as a whole assortment of other useful tools.

*Subject to licence.

Installing Flynet Viewer Server


Now we will look at installing Flynet Viewer, and the files that are installed.

If you don't have the installer file it can be downloaded here:

64-bit Download https://www.flynetviewer.com/sites/default/files/fvsetup64.exe

OR

32-bit Download https://www.flynetviewer.com/sites/default/files/fvsetup.exe

If you are not sure which you should use, try the 64-bit version first.

Prerequisites

 

The Flynet Viewer Server installer automatically activates Windows roles and features, or prompts you to download components if required.

Flynet Viewer Server installer will scan the local machine, looking for missing components. If any are missing, the installer will prompt to install them.

Flynet Viewer Installer prompting to install missing Windows components.

Older versions of Windows will require you to install Microsoft .NET Framework version 4.0. More up to date versions of Windows has a version of .NET 4.x included as a role or feature.

For reference, the following roles and features are activated/installed by the Flynet Viewer Server installer:

 

  • .NET 4.x
  • ASP.NET 4.x
  • IIS
    • Web Management Tools
    • World Wide Web Services
      • .NET Extensibility 4.x
      • ASP.NET 4.x
      • ISAPI Extensions
      • ISAPI Filters
      • WebSocket Protocol (Windows 8 / Server 2012 upwards)
    • Common HTTP Features
      • Default Document
      • Directory Browsing
      • HTTP Errors
      • Static Content

Starting The Installer

 

The Flynet Viewer Server is a normal Windows wizard style installer.

Your start the process by double-clicking on the installer file. Please note that there are 32-bit and 64-bit version of Flynet Viewer Server. Please make sure you are using the correct installer for your target machine.

The installer will scan and offer to install any missing components, as described on the previous page. An older Windows system may offer a URL to download Microsoft .NET Framework 4.x.

You are asked to review and agree to the Licence Agreement.

Flynet Viewer Server installer requesting the agreement of the Licence Agreement.

After accepting the Licence Agreement, you will be asked to enter your Access Code (key).

Flynet Viewer Server installer prompting for the Access Code.

Target Host

Next you provide the target host IP and port for the first host that you wish to set up with Flynet Viewer.

Flynet Viewer Server installer prompting for the host address and port.

 

Connecting to hosts using SSL/TLS and SSH will need further configuration after the installer has completed.

Host Terminal Emulation Type

 

Here we have the choice of three terminal type families.

Flynet Viewer Server installer prompting for host terminal type.

 

  • Select TN3270 for IBM Mainframe.
  • Select TN5250 for IBM AS/400 or iSeries.
  • Select VT100/VT220/SCO-ANSI/ViewPoint/Wyse for the Character Mode hosts. This includes VT, xterm, Wyse, ViewPoint, MultiValue, and more.

You will then see the standard Select Destination Folder steps, and a then Flynet Viewer will install.

End of Installation


Congratulations, you have now successfully installed Flynet View Server. Next, we will cover details about the installed file locations and Applications

Flynet Viewer Server is available for what versions of Windows ?

  • 32 bit only
  • 64 bit only
  • Both

Installed File Locations and Applications

Files and Components

We will start off looking at the locations of the files, and what their purpose is.

Secondly, we'll have a high-level look at the installed applications and components.

File Locations


Default Flynet Viewer file locations are:C:\Program Files\flynet\viewer

The main folder for Flynet Viewer. We will look into this folder in more depth on the next page.

C:\inetpub\wwwroot\FVTerm

The Flynet Viewer Web Terminal Emulation application.

C:\Windows\Microsoft.NET\assembly

Flynet Viewer API files stored in the Microsoft .NET GAC.

C:\ProgramData\Flynet

Standard settings and storage for web applications. This is used by the Flynet Viewer Web Terminal Emulation application.

Your heading text goes here

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.

The flynet\viewer Folder


The flynet\viewer folder contains the following files and folders

admin

The Admin Console and Trace Viewer.

bin

The binary folder contains the server installations executable files. These include the Flynet Viewer core emulation service (FlyServer.exe), the Flynet Viewer System Tray Control (SCControl.exe) and the Simulated Host (SimHost.exe).

bin\FW4.0 and bin\Win32

These sub folders contain the Flynet Viewer APIs as library and assembly files.

CodePages

The code-page translations files, such as US/Canada, UK etc.

Definitions

Location of XML definition files used for high-speed recognition of screens.

data

Default location for log files.

HelpMMCSnapIn

The standard Microsoft Management Console Snap-In for Flynet Viewer.

Recorder

The location of the Recorder used for capture screens for development.

Recordings

The default location for recordings created by the Recorder.

SimHostScripts

The location of simulated host scripts.

ssh

Configuration files for SSH connections for UNIX-style hosts.

sspi

Configuration for SSL / TLS connections for iSeries and Mainframe.

Applications and Components

 

A screen shot of the Flynet Viewer folder on the Windows Start Menu.The Flynet Viewer folder on the Start Menu gives access to administrative and development tools.

Key items being:

Access Code Management

A tool used for activating Flynet Viewer installations.

Admin Console

The main server configuration app. 

Flynet Viewer Main Help

Flynet Viewer MMC

A standard Microsoft Management Console snap-in for managing Flynet Viewer servers.

Taskbar Control

A handy tool for access to quick actions while developing with Flynet Viewer.

Trace Viewer

A tool for viewing trace files created by the server (features needs to be enabled in server before traces appear).

Viewer Recorder 2.0

A tool used to record screens for development purposes.

 

< The flynet\viewer Folder

 

End of Lesson >

End of File Locations and Applications

Add a Host Definition to Flynet Viewer Server

Open the Flynet Viewer Admin Console

It is important that you follow these steps exactly. The host definition will be used later in this course. If you have set it up differently, the guidance may not make sense, and you may have to go back and update the settings to what is here.

 

  1. Open the Admin Console: Windows Start Menu -> All Programs -> Flynet Viewer -> Admin Console.

The Flynet Viewer Admin Console

Service Settings

 

 

  1. Open the 'Service Settings', found on the menu at the top left hand side of the Admin Console.

Flynet Viewer Admin Console Service Settings.

Add a Host Definition

 

 

  1. Click on the blue right-arrow (action icon) next to 'Hosts'.
  2. Click 'Add a Host Definition'.

Flynet Viewer Admin Console Add a Host Definition.

Host Settings

 

Update the following host settings:

 
Host Identifier MainframeWS
Host Address 127.0.0.1
Connect Text* Input box 1: SWITCHIT
Input box 2: 10
Input box 3: 3
Code Page File CP850 (Multilingual)

*The location and value of text that can be found on the screen that indicates the host has reached a good connection state.

Host Settings for Activity

Apply the Settings

 

 

  1. Press the [Apply] button at the bottom left of the Service Settings window.
  2. Flynet Viewer Administration Pop-upPress [Cancel] button on the 'Flynet Viewer Administration' pop-up. This is for setting up the Flynet Viewer Terminal in a Browser, which we are not going to configure in this course.
  3. Press [Close] on the 'Flynet Viewer Service Settings Changes'.

End of Section

Congratulations, you have reached the end of the section and will now move on to cover the "Insure Simulated Host". When setup this will simulate a connection to a mainframe hosted application that you will be able to interact with.

The Insure Simulated Host

The Insure Simulated Host - Introduction


In this topic, we learn how to use the Flynet Viewer Simulated Host, and the Insure script. The Insure script simulates an insurance application running on a mainframe. We are going to use this simulated mainframe throughout our training.

The Simulated Host is useful for safely designing and developing Flynet Viewer solutions while offline from a host. It is also useful for training and testing. The Simulated Host runs as a Windows Service, and by default listens on the standard Telnet port. You can script TN3270 and TN5250 applications, and play back captures of other terminal types.

Flynet Viewer Studio Installation

Flynet Viewer Studio - Introduction


Flynet Viewer Studio is the design and development environment for building Web Services and Web UIs.