WebsphereToolkit for Oracle Forms

Session Objective
Overview of Forms migration
Converting Forms using WTOF.
Deploying Migrated Files in WebSphere (or) Tomcat
What IBM Migration Resources are Available
Four steps of migration
Oracle Forms
Builder
*.XMI
Websphere
*.WAR
(*.html, *.js, *.class)
Oracle
Forms
(binary: *.fmb)
Oracle
Forms
(Text: *.fmt)
Oracle
DB v7.x & 8.x
IBM DB2 UDB v7.2
1
2
3
4
Four Steps of Migration
Convert the Oracle database to DB2 using MTK.
Convert the Oracle Forms to text format
Use the Oracle Forms builder tool.
Convert the Forms to 3-tiers application using
WTOF
Steps detailed in this presentation.
Deploy to Websphere
Steps detailed in this presentation.
Database Migration
Migrate the Oracle database to DB2 using MTK
In MTK Convert >>Advanced Options, select Add ROWID column
in every table.
If tables, columns, procedures or functions are renamed, either
automatically or on users demand, WTOF will need the XMI file
generated during the conversion of the renamed objects..
To convert only forms, WTOF does not need connection to the Oracle
database nor the DB2 database.
WTOF Overview
Source Files
Forms 3.0 .inp
Forms 4.5, 5.0, 6.0 & 6i .fmt
Library Files Linked to Source
Menu .mmt
Object Libraries .olt
Program Libraries .pld
WTOF Overview
Text Format Migration
.fmb
.mmb
.olb
.pll
Oracle
Forms
Convert
Utility
.fmt
(.mmt
.olt
.pld)*
Input -
Binary
format
* .mmt, .olt and .pld are library files linked to .fmt
WTOF Overview
Application Migration
Application Migration
.inp
.fmt
W
T
O
F
J ava
HTML
J avaScript
Output
Input
WTOF Overview
WTOF Migration
Migration of Presentation Layer
User Interface to HTML
Validation to J avaScript
Migration of Business Logic
Business Logic to Java class files
Form, Block and Items are represented as different
classes
Form level PL/SQL are migrated to J ava method
Database Migration
While WTOF has migration capability, we strongly
recommend using MTK to migrate the database.
WTOF Overview
Forms To Java Mapping
Forms Data Type J ava Data Type
Char String
Date Date
DateTime Date
Integer Int
Money Double
WTOF Overview
Forms To Java Mapping
Form Objects J ava Objects
Triggers J ava Methods
Libraries J ava Packages
Program Units J ava Classes
Property Classes Cascading Style Sheets
Record Group Record set
WTOF Overview
Tool Standard Directory Structure
WTOF Overview
Create a project
Add files for migration to the project
Add XMI files from MTK conversion
Click Convert to migrate files
View output files - HTML, J ava and J avaScript
Compile the J ava file through Compile generated J ava file
option in the tool.
Migration Process
Migration Process
WTOF Overview
Application Startup
Application Startup
WTOF Overview
Create/Open Project
Create/Open Project
User can either create or open a project and connect to a database
Input files to be migrated must be added to a project with the reference
and the library files in the same directory as the input file
For application migration, source database information is mandatory
WTOF Overview
Create a new Project and identify a path to save it
WTOF Overview
Application Migration
Application Migration
Project created under the
application directory
Add files to the Project
WTOF Overview
File Selection
File Selection
Input files can be added as individual files or as multiple files
WTOF Overview
File Added
File Added
Project node with source files added
WTOF Overview
Source File Objects
Source File Objects
List of objects in each source file added
WTOF Overview
Using MTK XMI files
Using MTK XMI files
This step is necessary if
some Oracle objects have
been renamed when
converted to DB2.
WTOF Overview
Using MTK XMI files
Using MTK XMI files
Click Add XMI File.
The files are located in:
MTK_ora\projects\mtk_project_name
The name of the file is the same as the name of the DB2 file
generated by MTK.
WTOF Overview
Using MTK XMI files
Using MTK XMI files
WTOF Overview
Using MTK XMI files
Using MTK XMI files
Press Classifier Map
to see the object
name mappings
Press OK to return to
WTOF
WTOF Overview
File Migration Process
File Migration Process
Individual source files are migrated as follows -
Choose a file from Project tree
Select Tools Convert Application from menu
WTOF Overview
Single file is migrated to HTML, JavaScript and Java
WTOF Overview
File Migration Process
File Migration Process
-
-
Batch
Batch
Multiple files are migrated in batch as follows -
Select Project from directory tree node
Choose Tools Convert Application in Batch Mode from
menu
WTOF Overview
Select file for migration and click MIGRATEbutton.
The output will be .html, .js, .java files for each source file.
WTOF Overview
Compilation
Compilation
Migrated file is compiled as follows -
Select file from the directory tree node
Choose Tools Compile Generated J ava File from menu
Deployment
WebSphere (or) Tomcat Deployment
Using
WTOF deployment interface
WebSphere Deployment through WTOF
Runtime files are deployed -
Select Options Deploy Runtime Files from menu
WTOF Runtime Deployment
This creates a file WTOF_project_name.war in the indicated
directory.
The DB2 connection information will be used by the
application server at runtime.
WebSphere Invocation
To start WebSphere
Invoke the startServer.bat file that is available under <WebSphere
Root>\WebSphere\AppServer\Bin OR
Go to Start Menu and choose Program Files ->IBM HTTP Server ->
Start HTTP Server.
To stop WebSphere
Invoke the stopServer.bat file that is available under <WebSphere
Root>\WebSphere\AppServer\Bin OR
Go to Start Menu and choose Program Files ->IBM HTTP Server ->
Stop HTTP Server.
Tomcat Deployment through WTOF
To deploy with TomCat:
Rename the *.war file to *.zip and unzip the file in
C:\tomcat_instal_dir\webapps\ROOT
Copy the file Dbprop.properties to
C:\tomcat_instal_dir\webapps
Runtime log is C:\tomcat_instal_dir\bin\WTOFLog*.txt
Tomcat Invocation
To start Tomcat
Get into Tomcat bin folder
C:\tomcat\bin
Issues the below command
Tomcat start
To stop Tomcat
Get into Tomcat bin folder
C:\tomcat\bin
Issues the below command
Tomcat stop
DB2 ODBC Configuration
Running in Client Environment
Go to Start ->Programs ->IBM DB2 ->Client Configuration Assistant.
Click Add to map a database to the client.
Select the Search the network option radio button.
Click Next
Select the desired database either from Known Systems or Other Systems.
Click Next
Enter an alias name against the Database alias field and description against
Comment.
Click Next
Check the option Register this database for ODBC and click the option As a
system data source radio button.
Click Finish to finish the Client Configuration Assistant Wizard.
DB2 ODBC Configuration
Running in Server
Go to Start ->Programs ->IBM DB2 ->Client Configuration Assistant.
Verify the ODBC name against the database selected.
Click Properties
Check the Register this database for ODBC check box and the option As a system
data source.
Click OK to end the setup.
Post Migration
Output deployed on WebSphere
Compiled J ava Files on WebSphere Application Server
virtual directory
HTML, J avaScript on HTTP Server virtual directory
Output viewed through browser
Internet Explorer
Support
WW DM Solutions Team, Kevin Decker krdecker@us.ibm.com, Phone #
303-224-0797
Technical problems supported by e-mail at mtk@us.ibm.com