Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Follow us
Facebook    Twitter    LinkedIn

G&R » About G&R » News » Gargen, the Java Bean Generator from G&R  

Gargen, the Java Bean Generator from G&R

G&R's Glink for Java offers an optional Java Bean Generator, Gargen, that allows the user to step through existing 'forms mode' mainframe transactions as a normal terminal, and then automatically generate either Standard Java Beans, or Enterprise Java Beans that encapsulate the transactions, and are able to repeat them as needed. There are absolutely no changes needed to the mainframe system. The generation process is speedy, requires no knowledge of programming at all, and produces components that fit right into the component library of a Java developer.

Gargen host access components completely obviate any necessity for your Java developers to be familiar with the mainframe implementation of the transactional components that they use, and reuse, when building new e-business systems that cooperate with those mainframe applications. Gargen is the easy, quick way for you to encapsulate your existing mainframe functionality in a series of Java components that free your Java developers to work on new e-business systems.

Gargen is available as an optional product for use in all Java development environments using Glink for Java API. The Java Beans that Gargen generates may be used from a Java program on your workstation, from an applet within your browser, from a Java servlet on a Web server or from a Java application on a J2EE compliant Application Server. Gargen generates an example Java servlet that shows how to use the Java bean in a normal Web server environment. Gargen also generates an example of how you could deploy and use the Enterprise Java Bean in an Application Server environment using Gconnect, the G&R J2EE Connector (see separate announcement).

Bull customers purchasing the HooX product receive the Gargen technology as part of HooX, together with Gconnect. Within HooX they will use Gargen for generation of Enterprise Java Beans for use on a J2EE compliant Application server connecting to GCOS mainframes with the help of Gconnect. Gconnect for accessing GCOS is not offered except as part of Hoox. Gargen for generating Enterprise Java Beans for use with Gconnect to access GCOS is not offered except as part of HooX.

Gargen is an application component generator. Its purpose is to allow a user to step through an interaction with an existing application on a mainframe system, and then automatically generate a Java component (Bean) that is able to repeat that interaction when used by a Java application.

Gargen is useful for anyone interested in generating standard Java beans that can be used with the Glink API to connect to 'forms mode' applications on Bull or IBM mainframes from workstation applications, applets or server side applications running as servlets under the control of a Web server. Gargen is also offered to IBM customers for generation of Enterprise Java Beans for use when connecting to 3270 or 5250 applications with the help of Gconnect.

Most existing host applications are designed to communicate with some kind of terminal using a 'forms mode' dialog. Gargen uses a development copy of Glink for Java Professional Edition to do the host communications, using the appropriate terminal type. These include Bull mainframe applications written for VIP7700, VIP7760, VIP7800, Questar DKU7107 and DKU7211 terminals, and IBM mainframe applications written for IBM3270 and IBM5250 terminals.

Gargen drives a copy of Glink using the Glink for Java Application Programming Interface. Programming of host communication Java Beans can be time-consuming, because of the trivial programmatical details of checking that the expected screen has been received, of selecting the data on the screen that you would like to be an output from your Java Bean and identifying the input that you want to enter, as constants for every execution of the Bean, or as variables to be taken from the input parameters to your Bean. You can automate programming of these host communication Java Beans using Gargen, and free your Java programmers for productive tasks.

Gargen is itself an example of the Glink API. Gargen is in control of the user interface, but uses the Glink API to drive a copy of Glink to do the interaction with the host application, while recording the necessary information that a Java Bean will need in order to repeat the same function. Gargen allows you to step through a mainframe transaction sequence, and generates the source code of a Java Bean or Enterprise Java Bean that uses the Glink API for host communication and forms processing. The Java source code generated is available to your Java developers for study, and enhancement or customization. The final phase packs the Java source as a Standard or Enterprise Java Bean for deployment in a Java development environment, and use as a component in a Java application.

Gargen is the win/win way to encapsulate mainframe transactional functionality in standard reusable components that your Java developers can use, and reuse, with no thought to the mainframe application behind them.

(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/about/news/2002-02-06
 
PARTNERS