You are here: Products Glink for Java Operating Modes  
 GLINK FOR JAVA
Introduction
History
Releases
Supported Environments
Operating Modes
Download
 PRODUCTS
Glink for Windows
Glink for Java
GlinkWeb
Gargen
Gconnect
Gweb
GlinkVisual
Ggate

OPERATING MODES
 

Starting with release 6.5 Glink for Java is available in several versions, and can be run in several different modes. The following short definitions will help you to understand the versions and possibilities.

 
Glink as an applet
Glink for Java can be run as an applet. This requires a server mode installation, and means that the user starts by accessing web pages from a browser, and downloads the Glink for Java applet from a web page as needed to make a mainframe connection. The applet downloaded is always the latest version. The Glink applet that is downloaded will by default connect to a Glink for Java server running on the same system as the Web server, and obtain a license and configuration files from it.  

Glink as a Java Web Start application
Glink for Java can run as a Java application using the Java Web Start technology. This mode is quite similar to the applet mode and requires a server mode installation. In addition the clients must have Java Web Start installed. Java Web Start 1.4.2 is shipped as part of the Java 2 Platform, Standard Edition 1.4.2 release. The user starts by accessing web pages from a browser, and on the very first access downloads the Glink for Java application from a web page as needed to make a mainframe connection. Thereafter the application is only downloaded if the user does not have the latest version. The Glink application downloaded will by default connect to a Glink for Java server running on the same system as the Web server, and obtain a license and configuration files from it.
The main difference from the applet mode is that a Java Web Start Glink runs independently of the browser, which can be terminated or used for other purposes, leaving Glink running. Web Start also gives you the option of making start up icons for Glink that Web Start Glink without using the browser.  

Glink as an application
Glink for Java can be installed as a Java application. The application version may be installed stand-alone, using its own license and configuration information or be configured to obtain licenses and configuration information from a Glink for Java server.  

Glink Application Programming Interface
Glink for Java Professional and Enterprise Edition licenses enable an integrated Application Programming Interface (API), allowing you to control the emulator from your own Java applets, applications or Java beans. Your applications can engage in dialog with the mainframes and extract data to be combined and displayed using your own presentation format. A Professional Edition license enables 5 simultaneous sessions for workstation applications or applets. An Enterprise Edition license enables as many simultaneous sessions as are licensed for use by server side applications.  

GlinkWeb, Glink in web mode
GlinkWeb, Glink as a web server application, is an extension to the Glink product family that gives web users access to mainframe applications from their browsers, without the need for additional software on the client workstation.
GlinkWeb is implemented as a Java servlet, and installation is a separate activity, using a package that installs and deploys GlinkWeb on a web server with support for running Java servlets. It requires an Enterprise Edition license. GlinkWeb allows you to facelift the mainframe screens, and includes a Forms Assistant that helps you to identify and catalog the screens.  

GlinkWeb Forms Assistant
This is included in the Enterprise Edition license. It is a tool for facelifting the screens presented by GlinkWeb using Java Server pages (JSP). Using the GlinkWeb Forms Assistant you can step through your business application and identify screens that you would like to facelift. The Assistant generates a JSP for each screen identified. The JSP then becomes responsible for generating HTML output to the client. The JSP can be read into the JSP editor of your choice, and modified to give a custom view of the application, quite divorced from the look and feel of the original screens.  

Glink for Java server
Central configuration and license management require a Glink for Java server. The server must be running in order to be able to start Glink clients configured to use the server. Clients can be Glink applets, GlinkWeb servlets, Glink application versions or user applications using the Glink API and running on workstations or an application server. The configurations that are distributed to the clients are built using the Glink Administration program.