open up your legacy and integrate with the...

Bull Summit 2006, Phoenix Arizona

Open up your legacy and Open up your legacy and integrate with the futureintegrate with the future

Summit 2006, Summit 2006, Michael SandMichael Sandøøyy

It is always a pleasure coming here to the Bull Summit conferences. They are well organized and we get an opportunity to meet our valued customers and our close partner Bull in a warm and pleasant environment.

My presentation will show you how some of G&R’s products can help you to open up your legacy and integrate it with the future, i.e. take advantage of new presentation techniques and integrate it with other information sources.

You will get an overview of our current web-access and mainframe integration product offer. G&R’s objective is to provide efficient, reliable and scalable solutions on affordable platforms. To achieve that we have had a strong focus on standards, open systems and cross platform technologies.

Gallagher & Robertson is committed to open systems and standards. Since its founding in 1982, G&R has always been an independent software provider with focus on open systems. G&R specializes in products that allow workstations, browsers, open system clients and e-Business applications to connect to mainframe applications on Bull GCOS, IBM OS/390 and UNIX systems.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re

Bull Summit, Phoenix Arizona May 2006Bull Summit, Phoenix Arizona May 2006

Access to corporate information todayAccess to corporate information todayMission critical data on your mainframeNo or limited integration with other IT systemsData entry and retrieval by trained staff– ‘customers’ at the counter– ‘customers’ on the phone– requests by fax, mail/e-mail or web-forms

Using an old-fashioned terminal display– Can be a very efficient user interface for the

experienced user, but not for a new employee or the infrequent user

In today’s business environment access to information is a key competitive advantage. Corporate information must be made available to an expanding population of employees, partners, suppliers and customers.

Over the years you have invested heavily in your legacy Bull or IBM mainframe, and most of your enterprise data resides on your mainframe. Some of your staff are trained to update or look up information stored on the mainframe based on verbal or written input from other employees, customers or suppliers.

These tasks are performed using an old-fashioned terminal display that is limited by presentation techniques available 20-30 years ago. The terminal users may be lucky and have Glink on their workstation and Ggate on their server. These are G&R products that provide GCOS users with the most efficient link to legacy GCOS applications, but even though Glink in itself is a guarantee that the enterprise information is presented exactly as intended by the legacy applications - this is not a suitable solution for the new populations of users that will access your corporate data in the future.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Maybe you have compact screens like this?Maybe you have compact screens like this?

AUTOSYS administrates all Norwegian cars and driver’s licenses

This screen displays all the technical data of a car registered in the AUTOSYS application. AUTOSYS is a GCOS8 application that administrates all the cars and driver’s licenses registered in Norway. Anybody that has used or seen a demonstration of data retrieval from AUTOSYS has to be impressed by the speed of the application and by the knowledge of the user handling the keyboard. Many of the screens are very busy, and designed to present as much information as possible within each screen and in as few transactions as possible.

Very often legacy mainframe applications require transaction codes and parameters that are very cryptic and that require extensive training for new users.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


What you want is What you want is ……..

Customers and suppliers to take part in the data-entry / data-retrieval processTo give more internal users access to corporate dataTo modernize the user interface to your mainframe dataTo integrate information from multiple sourcesTo capitalize on your investment in reliable and responsive data storageAnd …

You want it NOW!

You want to meet the new demand for information access by enterprise intranets and extranets based on Internet’s TCP/IP and Web technology.

You would like to make your operation more efficient by letting more of your employees and your partners, suppliers or customers access your enterprise data directly. It would be much better if students could register for classes and check their grades, customers check your stock and order your products or look up details of their electricity bill, and the general public read their tax-returns, all directly.

In the past you have considered placing mainframe hardware terminals, installing terminal emulation software or installing other client software at new internal and external locations, but the maintenance cost of these solutions has been high compared to what you have gained.

It would be better to base a new solution on a client component that everybody has and knows -the web browser.

You don’t really want to re-design and re-implement your mission critical application with new tools that your developers don’t know, and you don’t want to touch the very efficient data storage you have built on GCOS. You know that such a process will take years, will be expensive and you have no guarantees that the response times will be acceptable.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Glink Professional EditionGlink Professional EditionVersion 8 with new look released in April 2005Supported on 32-bit and 64-bit Windows XP and Windows 2003Glink API, Glink scripts and Glink macros allow you to automate dialogs and improve the user interfaceBUT it is installed and run on the Windows workstations

Freestanding, independent, managed by userNeed no server for license or configuration managementThe Glink API is available for workstation applicationsRuns as a native 32bit Windows applicationMore than 600,000 licenses sold


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Glink for Java Glink for Java —— Applet, Web Start or ApplicationApplet, Web Start or ApplicationPlatform independent and on-demandGlink API, Glink scripts and Glink macros allow you to automate dialogs and improve the user interfaceBUT it is installed and run on the workstations

Glink for Java is a 100% Java implementation of Glink, including most features of our immensely successful Glink for Windows product. It allows you to access applications running on IBM, Bull, UNIX, Linux and DEC mainframes directly from your Java enabled web browser or workstation.

Glink for Java:• is multi-platform, multi-mode• can be a workstation client or supply emulation services to client applications• can be downloaded on demand as an applet from a Web server to a browser or as a desktop Java application (Windows, UNIX, Linux, Mac OS X)• can supply emulation services to applications on a Web server or application server• API can be used by your applets, workstation applications or server applications

With Glink for Java you can:• reduce software administration and maintenance costs because it is one single program that is installed and set up centrally, then downloaded on-demand over Intranet, Extranet or Internet • choose to download as an applet to browsers running under any workstation operating system or download as a Java application. Both applet and application log on to the central server to collect configuration data• use the Glink script language or Glink Java API to automate and customize user operations and even redesign/facelift the user interface of your applications• install Glink on a server and develop new server applications in Java that use the Glink Java API to communicate with the mainframe applications

In Glink for Java we have carefully ported decades of experience, as well as proven emulation and communication code, from Glink for Windows to Java. We have also ported the popular and powerful script language that all the Glink users know and appreciate. With Glink for Java we provide you with reliable software that you install and administer centrally, but run anywhere: inside a browser or directly on your desktop under UNIX, Linux, Mac OS X or Windows.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


The solution is GlinkWebThe solution is GlinkWebIncluded in the Glink Enterprise Edition packageWeb-enables your mainframe applicationsNo changes to your mainframe hardware or softwareNothing but a standard browser on the users workstations or mobile devicesInstalls on a Windows, Linux or UNIX serverNo programming of any kind required anywhere

… but you can do that too!

With the following requirements:• user access from a standard browser• to existing legacy applications• little or no Web-specific development• new applications using existing mainframe development tools

The solution is GlinkWeb!

GlinkWeb is a fully functional mainframe access product that utilizes proven and reliable G&R technology for emulating mainframe terminals, but it replaces the old-fashioned terminal display device with a browser.GlinkWeb is a true plug and play solution available for Microsoft Windows and Java enabled web servers. After installation and setup of a network connection to your mainframe, your applications are accessible from a browser!


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Glink inside Glink inside -- Windows or Java, your choiceWindows or Java, your choiceMicrosoft Windows– Glink for Windows, Microsoft IIS and ASP.NET– Web Forms (ASP.NET): HTML and Visual Basic, C# or

JscriptJava enabled server– Glink for Java, Servlet on Tomcat, BEA or equivalent– Java Server Pages: HTML and Java

Shared– Methodology– Forms assistant– Forms database– Both integrated with standard, affordable tools

GlinkWeb is based on Glink. It uses the Glink API to communicate with Glink and has Glink inside. It is Glink that performs the communication with the hosts, that performs the terminal emulation and builds virtual screens that are accessed by GlinkWeb thru the Glink API. This means that although GlinkWeb is the latest product in the Glink product set, it is from the beginning a mature, stable and well-proven product that has been exposed to all kinds of Bull and IBM screens and communication scenarios. GlinkWeb.NET is based on Glink for Windows and GlinkWeb for Java is based on Glink for Java.

The .NET version requires a Microsoft IIS server with ASP.NET, and the presentation layer is built with ASP.NET pages

The Java version requires a Web server with Servlet support, like Tomcat or Bea WebLogic Server.

The methodology, Forms Assistant and forms database is the same.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


GlinkWeb, plain emulationGlinkWeb, plain emulationMakes legacy applications instantly available to a wide audienceGlinkWeb maps to HTML on-the-fly

GlinkWeb Glink for Windows

GlinkWeb executes on the web server, and the GlinkAPI view of the mainframe screens is mapped directly to HTML 'on-the-fly'. The users see automatically facelifted screens in their browser window, giving them 'terminal like' access to the mainframe applications. A set of client side Java scripts activates the HTML forms to do user field input control, and provide terminal-like keyboard functionality ported from Gweb. No changes are needed in the core business applications on the mainframe. GlinkWeb web-enables the applications immediately, and at no cost other than the Glink Enterprise Edition license.

Use of a browser as the display device allows a more attractive presentation of the mainframe screens.

GlinkWeb is a way of decreasing ‘cost of ownership’ by standardizing all communication using the Web browser interface. By making applications accessible from a browser the user can be provided with a seamless transition from static information retrieval (surfing in HTML pages) to real time data access.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


GlinkWeb with automatic web presentationGlinkWeb with automatic web presentation

Makes legacy applications instantly available to a wide audienceNo work on the presentation layer necessaryNothing to install on the client sideAll configuration and administration is done centrallyOptionally set up a private, encrypted connection between Web server and browserAppropriate for simple applications with user-friendly formsWeb-friendly forms can be added to existing host applications using host programming tools and host programmers!

It is important to remember that GlinkWeb provides ‘browser access’, and that a power user would not be satisfied with it. These users and the high volume data entry applications users require products like Glink for Windows or Glink for Java. As GlinkWeb is included in the Glink Enterprise Edition package, these users may use Glink in web-controlled workstation mode. In this mode Glink is licensed by concurrent usage and shares a license with GlinkWeb and server-side applications built on top of Glink API.

However for the purpose described GlinkWeb gives all of the above advantages.

GlinkWeb also offers a face-lifting capability with the product, allowing users to customize the HTML delivered to the browser for each individual screen in an application. This is described in the following pages.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


GlinkWeb, faceGlinkWeb, face--lifting by program lifting by program Forms Assistant and API for custom face-lifting Windows version– Web Forms pages (ASP.NET), .NET programming

Java version– Java Server Pages (JSP) and Java programming

GlinkWeb provides basic face-lifting of the emulation screen, suitable for presentation in a browser.

You can customize the log-on page which is displayed when offering the users the choice ofconnections available to them. Of course you can also bypass the log-on page completely, by making custom web pages that include URLs that start a specific mainframe session with a single click.

You can customize the disconnect page which is displayed whenever a mainframe session is terminated. You can offer your users the option of reconnecting, or you can use any HTML technique to pass them to another region of your web server.

You can customize the master application screen template that controls the basic appearance of the screens displayed by a given mainframe application. You can choose wallpaper to enhance the cohesion of your core business applications, or to emphasize the identity of a given application. You can add a custom header with a company logo, and a custom footer with a URL to application information, or perhaps for sending an e-mail message.

The GlinkWeb Forms Assistant will assist you in identifying and customizing the individual screens that are delivered by the mainframe application.

Web-enabling and face-lifting of the core business applications on your mainframe systems need no changes to the applications, and no workstation software other than a standard browser. A GlinkWeb installation on your web server is the only requirement.

Customers who want to migrate away from the GL.Visual, Net.Visual or Eyesys products should note that we have a new GlinkVisual Forms Assistant product for forms capture and forms management available as an optional product to Glink Professional Edition.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


The GlinkWeb Forms AssistantThe GlinkWeb Forms Assistant

With the GlinkWeb Forms Assistant you can step through your business application, and identify screens that you would like to facelift.

With the GlinkWeb Forms Assistant you can step through your business application, and identify screens that you would like to facelift.

First stepselect

application

The GlinkWeb Forms Assistant is your friend and helper

With the GlinkWeb Forms Assistant you can step through your legacy application identifying the screens you would like to use in your new service oriented application. Then, either on-line or off-line, assign logical names to input fields and screen areas that you will use. You have a Glink screen in the left pane of the Assistant, and you select fields and areas by simply marking the area on the screen.

A Web Forms page (ASP.NET) or Java Server Page (Java) is created for each screen you identify. By default they generate the standard HTML output, but you can load them into your editor and modify them to give a custom view of the application, quite divorced from the look and feel of the original.

The Forms Assistant will produce a web page for each screen; either a Java Server Page or an ASP.NET page depending on your development environment. Now all you have to do is to configure GlinkWeb in your Integrated Developer Environment (IDE), and the pages can be customized to give your new presentation.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Identify a screenIdentify a screenMark one or morescreen areas

Mark one or morescreen areas

Name thescreen

Name thescreen Assign an

ASP.NET page/JSPto the screen

Assign anASP.NET page/JSPto the screen

Identify a screen

You start the facelifting process by identifying the current screen. Mark an area that uniquely identifies this screen and then use the Add button to include the marked area in the list. If necessary you can repeat the action and mark several areas that together uniquely identify the screen.

Glink supports two modes of marking; line-by-line and rectangular (see the Glink Edit menu in the Glink pane).

When you have sufficiently identified the screen, you must give it a name, and name the Web Forms pages/Java Server pages that will handle it. The names are mostly for your own use, choose names that you associate with the screen. Each screen identified must have a unique name, but several screens can be handled by the same Web Forms page/Java Server page if you supply the same page name. In this case the Web Forms page/Java Server page can then use the screen name to find out from which screen it was activated.

Select

If GlinkWeb does not recognize the current screen due to changes to the mainframe application, you can use the Select button to copy the screen definitions from your version, and then modify them as appropriate so that GlinkWeb recognizes the new version. In the same way, if the current screen is similar to a screen you have already identified you can copy the definitions of that screen, and then modify them to recognize and process the new screen.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Define screen output areasDefine screen output areasFrom an ASP.NET page or JSP a screen area may be referenced by a logical name

From an ASP.NET page or JSP a screen area may be referenced by a logical name

Define screen output areas

Your Web Forms page/Java Server page handling the screen, can pick up mainframe output from an area on the current screen using a logical name, rather than using screen coordinates to access the same data. To make this possible you must first mark the area and then give it a logical name.

Mark a screen area and use the Add button. A new entry is added to the Named areas list box and the cursor is placed in the Name column of this entry. You give a name to the screen area by entering it in the Name column followed by the Enter key. You can define several areas by repeating the operation.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Name input fieldsName input fieldsFrom an ASP.NET page or JSP an input field may be referenced using a logical name

Field 1 CountryCode

From an ASP.NET page or JSP an input field may be referenced using a logical name

Field 1 CountryCode

Name input fields

In this dialog box you can give a logical name to one or more of the input fields in the current screen. The Web Forms page/Java Server page handling the screen can then reference input fields with a logical name rather than the field index number.

The fields in the form are listed. To give a field a name, select the field in the list box and enter a name in the Name column followed by the Enter key. To remove a name, select the name by double-clicking it in the name column then delete it, and finish with the Enter key.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Final stepsFinal steps

List of screensidentified

List of screensidentified

Customize the ASP.NET pages/JSPsCustomize the ASP.NET pages/JSPs

Final steps

When all the screens are identified, output information and input fields marked and named, you can customize the ASP.NET/JSP pages in an editor or developer environment of your choice before deploying to the web server.

The Web Forms pages/Java Server pages you defined to handle the screens you identified must be deployed on your Web server to make them accessible. The first time a page is accessed it is compiled by the Web server and then activated. If a page error is detected, the client (browser) accessing it will get an error report.

The screen definitions are saved in the screen.dat file. GlinkWeb uses the screen definitions to check screens received from the mainframe application. If a screen is recognized, GlinkWeb activates the Web Forms page/Java Server page you defined to handle it. You must deploy the screen.dat file to give GlinkWeb access to it.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Forms database management offForms database management off--lineline

The GlinkWeb Forms Assistant allows on-line and off-line lookup. The look-up window uses Glink itself to display the mainframe screen. This is done by loading the saved screen context from that screen. Each screen area or input field is high-lighted in the Glink pane as you select their item in the Assistant’s list boxes. Defining new screen areas is done by simply selecting the ’mark’ function in the Forms Assistant and then marking the area in the Glink pane as if you where marking to copy text. The Forms Assistant allows marking line or rectangular areas.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


The Visual Studio/ Visual Web Developer EnvironmentThe Visual Studio/ Visual Web Developer Environment

Sees GlinkWeb files as a web-siteEdit, test and debug your ASP.NET pages

In Visual Studio or Visual Web Developer 2005 you simply open the GlinkWeb directory as a Web site. GlinkWeb and the screens you have identified appear in the Solution Explorer as folders, and you can simply open the folder corresponding to the application you are working on, and go to work modifying the ASP.NET pages.

The full power of the environment is available to you, including the ability to launch GlinkWeb from the environment, and test your new application, using the debugging tools.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


The GlinkWeb Eclipse plugThe GlinkWeb Eclipse plug--ininadd GlinkWeb nature to EclipseDynamic Web projectsrun Glink for Java, the Administratorprogram and FormsAssistant insidethe Eclipse workbenchcreate, facelift, test and debug entiremainframe applications inside Eclipseuse Eclipse facilities: JSP editor,debugger, embedded Servlet containerruntimedeploy your finished applications toexternal Web serverscustomize the look and feel of all yourapplications by modifiying suppliedstyle sheets / HTML pagesmaintain the Glink for Java configdatabase from within Eclipseplug-in installation is just an unzipof the plug-in archivesupports the servers supported byEclipseruns under Eclipse 3.1.2 and the WebTools Project v. 1.0.x.

Eclipse is free and available from http://www.eclipse.org.

The plug-in requires Eclipse 3.1.2 or newer and the Web Tools Project 1.0.1 or newer.

The plug-in creates a full GlinkWeb environment within an Eclipse project, allowing you to run everything locally: Glink for Java, the Admin program, Forms Assistant.

The full set of Eclipse facilities is available: HTML, XML and JSP editors, Java development tools, help pages for the plug-in, a runtime environment for testing the applications on an embedded Servlet container, and the Eclipse debugging environment.

Using the plug-in requires that GlinkWeb has been installed locally first, along with a local servlet-enabled Web server such as Tomcat or JOnAS.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


A rich and powerful development environmentA rich and powerful development environment

threads and variables

JSP structureJSP source stopped at breakpoint

server console

The Eclipse debugger is a powerful tool for testing and developing facelifted Java Server Pages. Breakpoints can be set, variables inspected and the server log viewed while the application is running. Thus the development cycle is speeded up considerably compared to performing the same tasks outside Eclipse.

Applications are tested locally, on the embedded Web server runtime running inside the Eclipse workbench, and using the Eclipse embedded web browser.

Breakpoints can be set both in JSP and regular Java code. When running the application in Debug mode, Eclipse can be configured to automatically switch to the Debug perspective, enabling all the available debugging tools.

Normally the plug-in operates within the J2EE perspective. The GlinkWeb project nature can be added to (and removed from) any Dynamic Web project available in the Project Explorer.

A single GlinkWeb project will typically be used to host several Web applications, each residing in its own subdirectory under the project’s Web Content directory.

Once your applications are tested and debugged you can use the Deploy function of the plug-in to deploy the fruits of your labours to either a local production Web server or to the GlinkWeb installation directory for offline deployment elsewhere.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


GlinkWeb ASP.NET/JSP faceGlinkWeb ASP.NET/JSP face--liftinglifting

Web serverWeb server

ASP.NETASP.NET

ASP Session

GlinkEE GlinkApi

GlinkSession

YesI know this

screen

selectCountry.aspx

Customized face-liftingCustomized face-lifting

GlinkWeb includes a screen recognition engine which consults the screen database where ASP.NET/JSP files can be configured to be executed when mainframe forms are recognized. The executed ASP.NET/JSP pages inherits access to a GlinkPage object which allows the program to retrieve information from the defined screen. The GlinkWeb Forms Assistant tool allows you to create and maintain the screen definition database.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Glink API, middle tier developmentGlink API, middle tier developmentA different approach with Glink Enterprise Edition on your application server

Use the Glink API for Windows or Java– Glink for Windows API, Windows IIS – Glink for Java API, Java 2 platform

Connection Pool Manager included in Enterprise EditionPublish mainframe applications as Web servicesGargen optionally available for Java bean generation

If you intend going beyond face-lifting, and adding a middle tier application with business logic, then Glink Enterprise Edition is the right tool for the job. The API it offers will have a familiar look and feel to programmers who work with the Component Object Model of development.

Gargen is a Java bean generator, which can be used to encapsulate a series of dialog steps with a mainframe application as a single Java Bean that accepts some parameters, and returns a result, such as a bank balance or stock on hand.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


GCPM, G&R Connection Pool ManagerGCPM, G&R Connection Pool ManagerFrees applications from session managementManages multiple pools with multiple sessionsApplication requests, uses and releases working connections to GCPM

The G&R Connection Pool Manager, GCPM, is a component of Glink for Java™ Enterprise Edition that offers connection setup and pooling to Glink for Java™ API applications. Instead of clients needing to know about the Glink for Java™ configuration - and having to set up and manage Glink sessions themselves - the Pool Manager offers a simple high-level API whereby clients can request working connections, use them, and release them back to the Pool Manager when finished with them.

The Pool Manager can manage any number of pools with any number of connections, within memory, CPU, network bandwidth and license restraints


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Gargen makes component generation easyGargen makes component generation easyStandard JavaBean for use with Servlets, JSP, Java applications or Java appletsYou can use standard JavaBeans together with GCPM, the G&R Connection Pool ManagerEnterprise JavaBean for use with Gconnect

What is Gargen?

Gargen is a tool that allows you to step through a screen driven function of a legacy application and then generate a component that replicates that function whenever called. The function can consist of one or many interactions with the legacy system. The component can have one or many input parameters for screen input fields, and can collect output from one or more areas in one or more output screens.

Why do you need Gargen?

• A large part of your Enterprise data is managed by legacy systems that you need to keep running smoothly for business continuity

• You need to streamline development of new services in a service-oriented architecture on standardized platforms

• You need to make your Enterprise data available to these new services, without touching a line of code in the legacy systems

Programming of JavaBeans for communication with legacy systems 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 JavaBean 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 communication JavaBeans using Gargen


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Gconnect, the G&R J2EE ConnectorGconnect, the G&R J2EE Connector

Gconnect is a J2EE compliant connectorGargen for Enterprise bean generationGconnect and Gargen are components of Bull’s HooXPublish mainframe applications as Web services

•Legacy system

•Application server

•Web server

•Servlet,•JSP

•J2EE container

•EJB

•Gconnect

•Mobile devices

•PC

•PDA

Here is the J2EE development environment.

The thin client (usually a browser) communicates using HTTP with any web server that has support for servlets. The servlet starts Enterprise Java Beans in the J2EE bean container. These beans can use the Glink API to communicate via Gconnect with a mainframe application.

Gconnect for Bull mainframes is included as a standard component in the Bull HooX product. It is licensed separately for IBM connections.

Gargen is a Java bean generator, which can be used to encapsulate a series of dialog steps with a mainframe application as a single Java Bean that accepts some parameters, and returns a result, such as a bank balance or stock on hand.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Summary Summary -- Business benefitsBusiness benefitsYou leave the legacy code absolutely unchanged– The G&R software handles the original forms driven interface, which still

can be used from terminal emulators by power usersYou preserve and capitalize on your investment in your legacy applicationsYou don’t have to install anything on the client devices, whether they are desktops, laptops, PDAs, SmartPhones or other mobile devicesYou save time and money by unifying and simplifying the user interface and by automating time-consuming manual operationsYou lower training costsYou save development time and costs moving to state of the art Open systems using state of the art toolsYou increase employee, customer and business partner satisfaction by giving your applications a uniform look and feelYou make huge savings in transaction costs when customers or business partners can access your new services themselves

Your business benefits

• You preserve your investment in your legacy applications by using the functionality in new ways for new user groups.

• You leave the legacy code absolutely unchanged. The original screen driven interface can still be used from terminals or emulators.

• You lower training costs, because new services make your Enterprise data available to employees who are familiar with browser-based applications.

• You save development time and costs by moving to state of the art platforms, using state of the art tools.

• You increase customer and business partner satisfaction, because new services make your legacy data available to them in a form that is customized to their needs.

• You make huge savings in transaction costs when customers or business partners can access your new services themselves, rather than calling trained employees.

• You increase employee, customer and business partner satisfaction by giving your applications a uniform look and feel.

• You save time and money by automating time-consuming manual operations.


Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

reOp

en u

p yo

ur le

gacy

and

inte

grat

e wi

th th

e fu

ture

Open

up

your

lega

cy a

nd in

tegr

ate

with

the

futu

re


Thank you for listening...Thank you for listening...

... and welcome to the Presidential Casita Hospitality Suite #3073 at 4:30 for demonstrations and informal discussions

We will be pleased to answer your questions and discuss your specific needs in depth. We will also be able to run live demonstrations of most products mentioned in this presentation.

open up your legacy and integrate with the...

Documents