12
Enabling Your Mainframe Application Screens on Mobile The pitfalls of choosing a weak Terminal Emulator copyright Flynet Limited 2014 Flynet Limited www1.flynetviewer.com

Not all terminal emulators are equal

Embed Size (px)

Citation preview

Page 1: Not all terminal emulators are equal

Enabling Your Mainframe Application Screens on Mobile

The pitfalls of choosing a weak Terminal Emulator

copyright Flynet Limited 2014

Flynet Limited

www1.flynetviewer.com

Page 2: Not all terminal emulators are equal

● What is modern Terminal Emulation?

● Modern Terminal Emulation is key to success

● Not all offerings are born equal

● Which has the best approach?

Focus of Presentation

copyright Flynet Limited 2014

Page 3: Not all terminal emulators are equal

● Easy and quick to install at reasonable total project cost and lowest risk

● Easy to maintain - with no code to change on server or multiple changing client devices

● Runs on any browser on widest range of devices now + future

● Fastest possible performance and response times

● Delivers enterprise benefits quicker and to highest level of productivity and efficiency

Read our slideshow on benefits of Terminal Emulation

What do Enterprises and Users Want?

copyright Flynet Limited 2014

Page 4: Not all terminal emulators are equal

The Three Levels of Terminal Emulation

Central Application

copyright Flynet Limited 2014

Terminal Emulation

(TE)Server User

Device/Mobile

Level 1 = EnableShow the application screen on the user device

FIREWALL

1 to 1

Page 5: Not all terminal emulators are equal

The Three Levels of Terminal Emulation

Central Application

FIREWALL

copyright Flynet Limited 2014

Terminal Emulation

(TE)Server User

Device/Mobile

Level 2 = EnhanceCombine and modernise application screens on the user device

Many to 1

Page 6: Not all terminal emulators are equal

The Three Levels of Terminal Emulation

Central Application

FIREWALL

copyright Flynet Limited 2014

Terminal Emulation

(TE)Server User

Device/Mobile

Level 3 = EvolveCombine updated screens with other web services and process flow

Many to 1

WebWeb

Web Many to 1

Page 7: Not all terminal emulators are equal

Why Most Terminal Emulators are bad for You

Central Application

TEServer

User Device???

ProprietaryApplet

This isHarder and longer to implementHard to maintainA security riskNeeds coders

Not available for all devices now and future-proof

A checklist for all suppliers

FIREWALL

● Many send image/HTML5 of whole screen every time key is pressed = slow responses + high bandwidth needed

● Not good for fast/remote users on slow lines

● Not many support PF Keys

Does not use standard security and SSL encryption modules for end-to-end process at all times

● Not based on standard Microsoft Web-Services platform

● Was first written for a PC GUI then try to make available to view on mobile and can lose knowledge of underlying data fields and entry checks

● Proprietary software stack

● Harder to code, test, debug

copyright Flynet Limited 2014

Page 8: Not all terminal emulators are equal

1. Require application changes on server or client device = high risk on server and complex and risky on many varied and changing client devices.

2. This needs ongoing maintenance (coders) and code management on thousands of devices and takes a long time to test and deploy.

3. Not all user devices are supported day1 or into future.

4. Need a high level of Java or proprietary macro language in supplier modules

5. Use a method that sends lots of data to/from clienta. This needs higher network speeds (not always there for client)b. Significantly slows down fast data entry screensc. Puts more load on servers

6. Are not based on standard code and Web Services platforms supported by Microsoft

7. Do not use International standards and code for security and encryption

What do Most Terminal Emulators do Wrong?

copyright Flynet Limited 2014

Page 9: Not all terminal emulators are equal

● Short project setup

● Minimal risk to IT

● Maintain data integrity

● Use international standards for security and encryption

● Work on the widest range of current and future user devices

What Would a Good Terminal Emulator Have?

● Based entirely on worlds biggest Web-Services platform from Microsoft

● No code on user devices

● Lowest load on networks

● Fastest response times for users

● Minimum coding skills and workload required

copyright Flynet Limited 2014

Page 10: Not all terminal emulators are equal

Why the Flynet Viewer Offering is the Best

Central Application

TEServer

User DeviceAny device with a browser supporting HTML5

● Android● Windows ● Apple

Devices● Chrome

FIREWALL

● Only sends data/field changes as they happen

● Compressed data stream● Very good for fast/remote

users with low connection speeds

● Supports PF Keys

Uses standard security and SSL encryption modules for end-to-end process at all times

● Based on standard Microsoft Web-Services platform

● Builds standardised web services

● Can create an offline version of your data streams as a simulator to build and test user view against

● Built on the standard Microsoft Web Services stack

● Strong functions to code, test, debug

● No code on device

● Lower risk● No maintenance

or versions needed for device support

copyright Flynet Limited 2014

Page 11: Not all terminal emulators are equal

● What type of project are you thinking of?

● What do you want to achieve?

● What are the timescales and resources available?

● Arrange a live online demo

● How can we help?

● Watch video now

Come and talk with us at Flynet

Contact Flynet Limited (UK)copyright Flynet Limited 2014

Page 12: Not all terminal emulators are equal

End