| |
|
| |
Migration
Approach PowerMigrator™ - The Seven Step Process
to the Web |
| |
|
| |
|
| |
|
| |
PowerMigrator™ is an automated tool, which makes the migration
process to the web easy. The following are the seven easy
steps for moving the Client Server application to the
web. |
| |
|
| |
 |
Step 1: Gathering
requirements
|
|
| |
This
is a very important process in the migration path. In
the initial phase, If the code had been written in earlier
versions of Power Builder (Version 6.5 and below) the
code has to be migrated to Power Builder Version 8.0 or
Higher for Web compatibility reasons. During the migration
process there may an occurrence of some of the objects
being incompatible. Those problems need to be resolved
before commencing the migration process. Ewak's consultants
will assist the client in this process to enable this
process to be completed quickly and prepare the code to
be migrated to the web. |
| |
|
| |
|
Step 2: Generate JSP
|
|
| |
This
is the most cumbersome task while rewriting. PowerMigrator™
makes this process very simple and automatic. The entire
JSP generation will happen within minutes eliminating
the time taken by the web designer in designing the forms,
buttons, tab sheets etc that contributes the major portion
of the Web Application. |
| |
|
| |
|
Step 3: Generate component
Templates.
|
|
| |
Here
the common methodologies and inherited objects are taken
to a component template, so that the process and methodologies
can be reused frequently. While generating the template
any further additions to be made, can be done. |
| |
|
| |
|
Step 4: Select, Slice
and Move
|
|
| |
PowerMigrator™ will help to identify the Business Logic
and Data logic, which will be converted as Power Builder
NVO's (Non Visual Objects) and subsequently these NVO's
will be moved to the Application server as components.
These Components can be invoked by JSP's from the Web
server. Any unnecessary code can be removed as that code
plays no part in the migrated application. |
| |
|
| |
|
Step 5: Testing
|
|
| |
The
migrated application is now deployed into the respective
servers and is now tested for functionalities in a test
box, which should be assigned for this purpose. |
| |
|
| |
|
Step 6: Debug
|
|
| |
The
developer will check the minimum functionality of the
software by running the original application in parallel |
| |
|
| |
|
Step 7: Deploy
|
|
| |
The
tested migrated application is finally deployed to the
production servers. |
| |
|
| |
|
