Would you like to replace terminal emulators for your non-specialist users, extend access to your legacy applications to occasional users within your business, and provide access to external users such as your suppliers, customers or subscribers? The answer is to web-enable your legacy applications.
We offer two products to meet the need for web-enabling of legacy applications. They are quite similar; both connect browser users to legacy applications with the look and feel of a terminal, without any changes to the legacy applications. The difference is in the Web server technologies they utilize and the facilities they offer for facelifting the user interface.
GlinkWeb is a server-side version of Glink. It combines a browser front-end with the Glink terminal emulation engines. You install GlinkWeb on a .NET enabled Windows server, or on a Servlet-enabled Web server, and with no further effort it makes your legacy applications accessible from browsers. When you move on to facelifting you use the GlinkWeb Forms Assistant to produce a web page for each screen to facelift, either a Java Server Page or an ASP.NET Web Forms page depending on your environment. You then open the GlinkWeb project in your Integrated Developer Environment to customize the web pages in question. You use GlinkWeb API-calls to get access to screen content and interact with the legacy application. That way you can implement modern and efficient web-pages either with a one-to-one mapping to the legacy application screens or with a one-to-many mapping where you automate part of the dialog and collect information from many legacy screens before you present the result to the user.
Gweb provides its own Web server and is therefore ready for use right after installation. It can also run under any Web server on UNIX, Linux and Windows platforms. When you move on to facelifting Gweb builds a library of the legacy screens, Web pages, with an interface to Web designers. The library of Web pages can be edited using any Web page development tool on a screen by screen basis. When customizing the Web pages you use Gweb macros/tags to extract screen content or to update input fields in the legacy screens. The Gweb macros can also be used to automate the dialog with the legacy system in order to collect information from many legacy screens before presenting the result to the user or to provide hot-keys to frequently used functions.