| |
|
| |
Migration
Architecture |
| |
|
| |
The Architecture of the migrated application consists of a number of objects, including migrated objects and standard objects (framework). Migrated objects are application specific and are created while migrating the application. The framework objects are common for all applications and packaged along with the migrated application. This document explains the details of both the types of objects. |
| |
|
| |
|
|
|
| |
The
above diagram illustrates the architecture of the migrated
application and the application is structured into the
following three layers |
| |
|
| |
Presentation
layer |
| |
|
| |
This
layer covers the details of User Interface of the application.
It consists of the following objects: |
| |
|
| |
Web
Pages - Represents the GUI portion of the application.
|
| |
|
| |
Common
JS - These standard objects perform the common task
for string, date and numeric manipulation. |
| |
|
| |
Component
Manager - These objects interact with the middle
tier component to serve the request from the client. |
| |
|
| |
Event
Handler - This handles the front-end events and invoke
the defined methods in the middle tier component. |
| |
|
| |
Reports
- They are application reports, which are similar
to the client/server reports. |
| |
|
| |
Application
Layer |
| |
|
| |
This
layer caters to the standard and business logic of the
application. It consists of the following types of objects:
|
| |
|
| |
Framework
Object - These are standard objects packaged with
the application, containing common routines and validations
to run the web application. It has the following objects
and functionality. |
| |
|
| |
Client
Request Handler - This object handles the request
from the browser client. It invokes the required methods
in the business objects based on the actions initiated
from the client browser, like retrieving data, updating
data, page navigation and sorting etc. It also receives
the data from the browser client and submits to the business
object for data update. It also receives the data from
the business or query objects and returns the html with
the help of HTML Generator object. It handles the request
both as a single and multiple html datawindow pages. |
| |
|
| |
HTML
Generator/Parser - This object generates the html from the datawindow object and parses the html before it returns to the client request handler object. Generally the html datawindow does not support any graphic objects in the datawindow like, line and group box. So the generator will create equivalent html scripts to display these objects. It Also processes the generated html to bring the same look and feel of datawindow object in the web, like the border size, colors etc. |
| |
|
| |
DWO
HTML Services - This object is a common service object
to enhance the html generation, like enabling the java
cache. For example, the generated html contains more java
scripts, which has the standard functionality, and it
can be eliminated from the html generation each time,
thus reducing the size of the html. |
| |
|
| |
Graph
Generator - This object generates the multiple type
graphs to display in the browser. It accepts the data
retrieved from the component and will generate the required
graph in HTML format and returns to the browser client.
|
| |
|
| |
Lookup
Manager - This object processes the request from
the client and generates the lookup page to display in
the browser using the key data created by the lookup manager.
These key data will be packaged along with the application
at the time of deployment. . |
| |
|
| |
Query
Manager - Similar to the lookup, this object processes
the request from the client and generates query result
page to display in the browser using the key data created.
These key data will be packaged along with the application
at the time of deployment. This contains, query columns,
criteria selections pages to get the input from the browser
client and pass the request to the component to generate
and return the html result. |
| |
|
| |
Security
Manager - This object implements the role base security
in the web application. The application menu options can
be assigned to each role and role to the users. Based
on the login, the menu options can be displayed. It uses
key data to maintain the roles. These key data will be
packaged with the application. |
| |
|
| |
Report
Manager - This object is to process the report in
batch. The processed report will be placed in the report
in-tray, where user can download the same in to local
machine to view the report. |
| |
|
| |
Application
Object - These are objects handles the data retrieve,
validation and update to implement the business logic. |
| |
|
| |
Storage
layer |
| |
|
| |
This
layer consists of user specified database with database
schema and the application data. |
| |
|
| |
|
| |
|
| |
|
| |
|
