Glink: GCOS e-business in an application server architecture Summit 2000, Jim Gallagher

Glink for Windows 32bit

>

Versions DOS  new functionality suspended at 6.0 level  error correction on an as-needed basis Windows 16/32 dual version  new functionality suspended at 6.2 level  error correction on an as-needed basis Windows 32 only version  new functionality goes into 'Professional Edition'

Glink Professional future Windows 32 bit version has a future……. ……with Microsoft….  Windows 98  Windows NT  Windows 2000 What about: UNIX OS/2 Mac

Java is an answer Java is a cross-platform language

DKU VIP7700 VIP7760 VIP7800 IBM3270 IBM5250 VT320 ANSI Glink for Java

Appearance  3D effects for variable fields  Function toolbar  Keyboard toolbar  Wallpaper

Configurable number of scrollback pages 3D effects in Scrollback Copy from scrollback pages to clipboard Scrollback window

Glink script support Starting a script  Configure a startup script  The session profile may point to a startup script  From file menu  Execute script file  Execute script  From a macro  scripts may be assigned to keyboard macros

Uses a graphical user interface Configurations are stored centrally Glink administration

Glink as an applet Java applications can be written as applets, and delivered on demand Applets are delivered from a web server to the browser, and execute inside the JVM of the browser

Web Server Glink Applet Startup BULL, IBM UNIX, Minitel The Glink applet collects the configuration details from the server Launched from an HTML page The browser downloads the applet Browser Java virtual machine Glink for Java applet Glink Server Glink connects.....you are in direct communication with your host application

Glink application version Glink and the administration program  included as Java applications that can be installed on the desktop  They escape the limitations of the browser  Applications are faster  no browser overhead  no browser memory limits  choice of JVM No more memory for you mister And no, you can’t bring your own VM!!

Delivery, any Web server Glink is downloaded by your browser from your web site as an automatically installable desktop Java application... ….and runs as an independent application on your desktop

Glink Application Startup BULL, IBM UNIX, Minitel The Glink application collects the configuration details from the server Launched from an icon on your desktop Desktop Java virtual machine Glink for Java application Glink Server Glink connects.....you are in direct communication with your host application At your convenience Glink is downloaded from the web server and automatically installed on the workstation

What about an API? You want the host data…. Buy, Buy, Buy Credit card: ______________ ….but not the host presentation Glink professional edition gives you the API

Desktop Java virtual machine Glink Java API Java application Glink API Startup BULL, IBM UNIX, Minitel The Glink application collects the configuration details from the server Launched from a Java applet or Java application on your desktop Glink Server Glink connects......your application is in direct communication with the host application Or they are supplied by the Java application Buy, Buy, Buy Credit card: ______________

What about e-business? The need for legacy application access moves from the workstation to the application server The good news is that both APIs run on the server Glink COM Glink Java API Application server Applications Databases Glink enterprise edition for many simultaneous sessions

Component model architecture The architecture formalizes the components of an e-business application Presentation logic Business Logic http Thin Client Web server Application server Applications Databases HTML Java Script Java applet

Going the Microsoft way Windows only, Intel only COM+ Take the Glink for Windows API, make a COM+ object Already delivered pre-beta Ready for beta end June

Going another way Multiple platforms, multiple OS Java API Take Glink for Java Already delivered pre-beta Ready for beta end June Take the Java API Produce Enterprise Java Beans

In terms of J2EE standards Glink for Java API becomes a tool for developing connectors Connectors encapsulate heterogeneous Enterprise Information System access in a standardized way Bull and G&R will in cooperation develop a connector for GCOS

Other J2EE standards  JNDI  Java Naming and Directory Interface  IDL  Interface Definition Language  JDBC  Java Database Connection  JMS  Java Message Service  JTA  Java Transaction API  JTS  Java Transaction Service  JavaMail  Abstract model of a mail system  RMI  Remote Method Invocation

The Bull/G&R connector JCA Bean Tool Connection Glink for Java API Emulation layer VipDKUVTMinitelIBM Communications layer GTEAGgateTNVIPTN3270TN5250 Telnet HOSTS

EJB generation (4Q00) Using a tool that drives Glink for Java via the API, step manually through the application The tool records the calls to the API that are used….. Compile the recorded Java code as an Enterprise Java bean …and remembers the input fields that are needed, and the output fields marked as the desired result The bean duplicates the host access sequence, using parameters for the input fields, and delivers the output fields as the result

G&R become a BEA Technology Partner Dedicated AIX platform in place in house WebLogic installed Web Server Plug-In State Data Servlet/ JSP EJB WebLogic Server Presentation/ Navigation Business Logic

Thank you for listening to... Glink: GCOS e-business in an application server architecture Summit 2000, Jim Gallagher ….. and welcome to the Penthouse Hospitality Suite at 5pm today