Browse Prior Art Database

Methodology to Federate a Legacy Console in a Central Console

IP.com Disclosure Number: IPCOM000124656D
Original Publication Date: 2005-May-03
Included in the Prior Art Database: 2005-May-03
Document File: 6 page(s) / 327K

Publishing Venue

IBM

Abstract

The invention uses a servlet filter on the legacy console side in conjunction with an HTML iFrame to allow the federation. The filter allows us to become part of a legacy console event flow without having to modify the legacy console.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 44% of the total text.

Page 1 of 6

Methodology to Federate a Legacy Console in a Central Console

The invention describes a mechanism that allows one to federate a legacy console in to a central console without modifying the legacy technology.

Background on the Two Consoles

In this case, the legacy and central console have certain fundamental differences, which the invention masks. The legacy console is designed to handle a single task at a time and uses HTML framesets to display various content (see Figure 1).

Navigation Area

Menu Bar

Banner Area

Breadcrumb

Status Area

Work Area

1

[This page contains 2 pictures or other non-text objects]

Page 2 of 6

Figure 1: The legacy console.

The central console allows the user to work with multiple tasks at once, but does not support HTML framesets. (See Figure 2)

Tabs for Task Switching

An iFrame referencing legacy console's work area

Figure 2: The central console.

The legacy console has no need to handle and store data for multiple tasks unlike the central console. Usage of framesets allows the various areas (see Figure 1) of the legacy console to be protected from data loss. If the navigation area of the legacy console needed to be refreshed then only that frame is affected. However, in the central console any kind of refresh affects the entire console view.

2

[This page contains 1 picture or other non-text object]

Page 3 of 6

Federation of the Legacy Console

The federation of the legacy console is achieved by using an HTML iFrame. The iFrame allows us to provide a url to the legacy console work area frame. The central console's objective is to display the work area frame of the legacy console (see Figure 1) for multiple tasks. The legacy console is easily federated in the central console since the workarea frame is accessible by a url. However, the problem lies within the handling of the federated request. For each task launched within the central console, the legacy console handles the request as if it was launched within the legacy console. Due to the single task design of the legacy console, the legacy console would lose track of Task A as soon as Task B is launched thus resulting in task data and state loss. Furthermore, the central console does not have the authority to keep track of data for the legacy console due to the browser's security implementation.

The Filter

The invention uses a servlet filter on the legacy console side to intercept the events from the central console. The filter becomes part of the legacy console's event flow (see Figure 3), allowing the filter to enhance the console without modifying its technology. The filter is activated for each request and performs any data handling needed if, and only if, the request came from the central console. Then it passes the request on for normal processing, thus there is no apparent difference when one interacts with legacy console.

3

Page 4 of 6

Legacy console ...

Legacy console C

Legacy console B

Central console

Legacy console A

Filter

 iFrame... iFrame C

iFra...