Browse Prior Art Database

A Process for Migration of Database Application to Enterprise Java Environment

IP.com Disclosure Number: IPCOM000015128D
Original Publication Date: 2001-Aug-28
Included in the Prior Art Database: 2003-Jun-20
Document File: 4 page(s) / 105K

Publishing Venue

IBM

Abstract

A process is disclosed in which information in a enterprise system can be linked up and processed in a certain innovative way, such that when the process and its algorithms are used, or when (a suite of) tools are built for that purpose, they offer users the advantage of productively designing and writing software to move database applications over to an Enterprise Java Bean environment. It analyses a program in the source system containing source database operation (the SQL statements) and identifies to the programmer-user the corresponding EJB objects and methods.

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 33% of the total text.

Page 1 of 4

A Process for Migration of Database Application to Enterprise Java Environment

A process is disclosed in which information in a enterprise system can be linked up and processed in a certain innovative way, such that when the process and its algorithms are used, or when (a suite of) tools are built for that purpose, they offer users the advantage of productively designing and writing software to move database applications over to an Enterprise Java Bean environment. It analyses a program in the source system containing source database operation (the SQL statements) and identifies to the programmer-user the corresponding EJB objects and methods.

When a database application with direct database SQL access is to be converted to a new EJB environment, the old SQL mechanism is to be replaced by the new EJB object and databean access mechanism. (Databean is an EJB technique to "wrap" an object so that it can be easier in programming and more efficient in actual performance.) In doing so, the programmer needs to know, for each old SQL database access, what are the corresponding databeans in the new environment and what corresponding access methods are to be used. This old-new correspondence often involves complex relationship between the old database schema, new database schema, the new databeans object, their underlying database tables and columns, the access methods and any parent-child hierarchy. Besides being complex, these relationships are often difficult to be documented in printed form, and are often hidden inside the source codes. Therefore, it could become very time-consuming for the programmers to find out these relationship in order to do the proper planning, design, and programming. The disclosure describes a process and algorithm, based on which tools can be built to facilitate programmers in this conversion task.

The process is first summarised below and then described in details in Figure 1, which depicts the various subprocesses, and how the information in a source system and a target system are extracted, processed and linked up. The process when taken as a whole, provides an effective and productive means to migrate software from the source system to the target system.

Summary of the process The process is comprised of two phases:

Phase (A): Collection of information The following information is collected and set up.

Source-to-target database mapping information


1.


2.


3.


4.


5.

Phase (B): Analysis of Net.Data (or similar application) and recommendation

A Net.Data file (or similar application) is parsed and coverted into a representation of SQL

statements. Each SQL statement is analyzed and the information about the source system database tables

extracted. Identify the pertinent target tables using the information from (A1)

Identify the pertinent target EJB (Accessbean) information using the information from (A3) and the

result of (B3) Identify the pertinent databeans using the information from (A4) and the result of (B4)...