
18
G&
GLIN
TM
GlinkWeb, Glink on the web server
GlinkWeb
The Enterprise Edition of Glink includes GlinkWeb. GlinkWeb is a separate package that is installed and
executes on the web server. Application screens are mapped to HTML 'on-the-fly'. Browser users see
automatically facelifted screens in their browser window, giving them 'terminal like' access to legacy
applications. Web enabling using GlinkWeb needs no changes whatsoever to the legacy applications. Once
GlinkWeb is installed on the web server, browser users can be given access to any legacy application.
GlinkWeb
Glink for Windows
A set of client side Java scripts activates the HTML forms to do user input editing field controls such as
numeric only, must enter, and must fill. Additionally they provide automatic tabulation to the next field when
the current field is filled. The Java scripts also provide terminal-like keyboard functionality, giving the
expected functions to keys such as HOME, TAB, cursor up and cursor down, rather than the default actions
of the browser.
GlinkWeb facelifting
You do simple facelifting with parameters; for a given application you can design a login page, disconnect
page and a master template for presentation of the legacy application screens, setting your own headers,
footers, wallpaper and the function keys you would like as pushbuttons in the page. You do advanced
facelifting using the GlinkWeb Forms Assistant to generate an ASP.NET Web Form (ASPX) for each legacy
application screen. You then use the Interactive Development Environment (IDE) of your choice to modify
these pages to completely change the look and feel of your legacy systems. You can produce simplified
views of complex legacy applications, or combine functions from several legacy applications into a new web
application. Using the functionality of ASP.NET Web Services support, you can even transform legacy
applications into Web services.
Com
letel
transform a le
ac
a
lication
Commenti su questo manuale