forms converting

39
Websphere Toolkit for Oracle Forms

Upload: slobce1967

Post on 28-Dec-2015

67 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Forms Converting

Websphere Toolkit for Oracle Forms

Page 2: Forms Converting

Session Objective

Overview of Forms migration

Converting Forms using WTOF.

Deploying Migrated Files in WebSphere (or) Tomcat

What IBM Migration Resources are Available

Page 3: Forms Converting

Four steps of migration

Oracle Forms Builder

*.XMI

Websphere

*.WAR (*.html, *.js, *.class)

Oracle Forms

(binary: *.fmb)

Oracle Forms

(Text: *.fmt)

OracleDB v7.x & 8.x IBM DB2 UDB v7.2

1

2

3

4

Page 4: Forms Converting

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 WebsphereSteps detailed in this presentation.

Page 5: Forms Converting

Database Migration

Migrate the Oracle database to DB2 using MTKIn MTK Convert >> Advanced Options, select “Add ROWID column in every table”. If tables, columns, procedures or functions are renamed, either automatically or on user’s 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.

Page 6: Forms Converting

WTOF Overview

Source Files

Forms 3.0 .inp Forms 4.5, 5.0, 6.0 & 6i .fmt

Library Files Linked to Source

Menu .mmtObject Libraries .oltProgram Libraries .pld

Page 7: Forms Converting

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

Page 8: Forms Converting

WTOF Overview

Application MigrationApplication Migration

.inp

.fmt

W

T

O

F

Java

HTML

JavaScript

Output

Input

Page 9: Forms Converting

WTOF Overview

WTOF Migration

Migration of Presentation LayerUser Interface to HTMLValidation to JavaScript

Migration of Business LogicBusiness Logic to Java class files

Form, Block and Items are represented as different classesForm level PL/SQL are migrated to Java method

Database MigrationWhile WTOF has migration capability, we strongly

recommend using MTK to migrate the database.

Page 10: Forms Converting

WTOF Overview

Forms To Java Mapping

Forms Data Type Java Data Type

Char String

Date Date

DateTime Date

Integer Int

Money Double

Page 11: Forms Converting

WTOF Overview

Forms To Java Mapping

Form Objects Java Objects

Triggers Java Methods

Libraries Java Packages

Program Units Java Classes

Property Classes Cascading Style Sheets

Record Group Record set

Page 12: Forms Converting

WTOF Overview

Tool Standard Directory Structure

Page 13: Forms Converting

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, Java and JavaScriptCompile the Java file through ‘Compile generated Java file’option in the tool.

Migration ProcessMigration Process

Page 14: Forms Converting

WTOF Overview

Application StartupApplication Startup

Page 15: Forms Converting

WTOF Overview

Create/Open ProjectCreate/Open Project

User can either create or open a project and connect to a databaseInput files to be migrated must be added to a project with the reference and the library files in the same directory as the input fileFor application migration, source database information is mandatory

Page 16: Forms Converting

WTOF Overview

Create a new Project and identify a path to save it

Page 17: Forms Converting

WTOF Overview

Application MigrationApplication Migration

Project created under the application directory

Add files to the Project

Page 18: Forms Converting

WTOF Overview

File SelectionFile Selection

Input files can be added as individual files or as multiple files

Page 19: Forms Converting

WTOF Overview

File AddedFile AddedProject node with source files added

Page 20: Forms Converting

WTOF Overview

Source File ObjectsSource File ObjectsList of objects in each source file added

Page 21: Forms Converting

WTOF Overview

Using MTK XMI filesUsing MTK XMI files

This step is necessary if some Oracle objects have been renamed when converted to DB2.

Page 22: Forms Converting

WTOF Overview

Using MTK XMI filesUsing 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.

Page 23: Forms Converting

WTOF Overview

Using MTK XMI filesUsing MTK XMI files

Page 24: Forms Converting

WTOF Overview

Using MTK XMI filesUsing MTK XMI files

Press Classifier Map to see the object name mappings

Press OK to return to WTOF

Page 25: Forms Converting

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

Page 26: Forms Converting

WTOF Overview

Single file is migrated to HTML, JavaScript and Java

Page 27: Forms Converting

WTOF Overview

File Migration Process File Migration Process -- BatchBatchMultiple files are migrated in batch as follows -

Select Project from directory tree nodeChoose Tools → ‘Convert Application in Batch Mode’ from menu

Page 28: Forms Converting

WTOF OverviewSelect file for migration and click “MIGRATE” button.The output will be .html, .js, .java files for each source file.

Page 29: Forms Converting

WTOF Overview

Compilation Compilation Migrated file is compiled as follows -

Select file from the directory tree nodeChoose Tools →‘Compile Generated Java File’ from menu

Page 30: Forms Converting

Deployment

WebSphere (or) Tomcat Deployment Using

WTOF deployment interface

Page 31: Forms Converting

WebSphere Deployment through WTOF

Runtime files are deployed -Select Options → Deploy Runtime Files from menu

Page 32: Forms Converting

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.

Page 33: Forms Converting

WebSphere Invocation

To start WebSphereInvoke 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 WebSphereInvoke 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.

Page 34: Forms Converting

Tomcat Deployment through WTOF

To deploy with TomCat:Rename the *.war file to *.zip and unzip the file in C:\tomcat_instal_dir\webapps\ROOTCopy the file Dbprop.properties to C:\tomcat_instal_dir\webappsRuntime log is C:\tomcat_instal_dir\bin\WTOFLog*.txt

Page 35: Forms Converting

Tomcat Invocation

To start TomcatGet into Tomcat bin folder

“C:\tomcat\bin”

Issues the below command

Tomcat start

To stop TomcatGet into Tomcat bin folder

“C:\tomcat\bin”

Issues the below command

Tomcat stop

Page 36: Forms Converting

DB2 ODBC ConfigurationRunning 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.

Page 37: Forms Converting

DB2 ODBC ConfigurationRunning 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.

Page 38: Forms Converting

Post Migration

Output deployed on WebSphereCompiled Java Files on WebSphere Application Server virtual directoryHTML, JavaScript on HTTP Server virtual directory

Output viewed through browserInternet Explorer

Page 39: Forms Converting

SupportWW DM Solutions Team, Kevin Decker [email protected], Phone # 303-224-0797Technical problems supported by e-mail at [email protected]